ruby-image-science 1.2.1-4 source package in Ubuntu

Changelog

ruby-image-science (1.2.1-4) unstable; urgency=low


  * Use a temporary directory for the Inline files used during the test.
    Thanks to Christian Hofstaedtler for the insight! (Closes: #652802)
  * Standards-version 3.9.2→3.9.3 (No changes)
  * Transitional packages should go to the "extra" section

 -- Gunnar Wolf <email address hidden>  Thu, 15 Mar 2012 13:17:14 -0600

Upload details

Uploaded by:
Debian Ruby Extras Maintainers on 2012-03-16
Uploaded to:
Sid
Original maintainer:
Debian Ruby Extras Maintainers
Architectures:
all
Section:
ruby
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Precise release on 2012-03-16 universe ruby

Builds

Precise: [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
ruby-image-science_1.2.1-4.dsc 2.3 KiB c1820bd47b6dd253ba746b1bc9e4cd3889c186646166a5bf8c4fe421067c0c1f
ruby-image-science_1.2.1.orig.tar.gz 8.2 KiB 97573140ef237666e9f9256b6d39213712e4089b2e4f8598979bf332ed1003fe
ruby-image-science_1.2.1-4.debian.tar.gz 4.6 KiB 44a6f8f96355e125547bcf08b0c6399645702266fb61ae0ae03c36404cd1541b

Available diffs

No changes file available.

Binary packages built by this source

libimage-science-ruby: No summary available for libimage-science-ruby in ubuntu quantal.

No description available for libimage-science-ruby in ubuntu quantal.

libimage-science-ruby-doc: Transitional package for ruby-image-science

 This is a transitional package to ease upgrades to the ruby-image-science
 package. It can safely be removed.

libimage-science-ruby1.8: No summary available for libimage-science-ruby1.8 in ubuntu quantal.

No description available for libimage-science-ruby1.8 in ubuntu quantal.

ruby-image-science: Clean Ruby library to provide simple transformations on images

 ImageScience is a clean Ruby library allowing for simple
 transformations on images, mainly geared towards generating thumbnails
 - The provided functions aim at scaling and cropping images.
 .
 Emphasis is made on keeping the code as lean as possible (at less than
 200 LoC), and on correctness to avoid memory leaks and similar
 problems that often accompany similar libraries.