[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

rubygems_1.8.15-1~bpo60+1_amd64.changes is NEW



(new) rubygems-doc_1.8.15-1~bpo60+1_all.deb extra oldlibs
Transitional package for rubygems
 This is a transitional package to ease upgrades to the rubygems
 package. It can safely be removed.
(new) rubygems1.8_1.8.15-1~bpo60+1_all.deb extra oldlibs
Transitional package for rubygems
 This is a transitional package to ease upgrades to the rubygems
 package. It can safely be removed.
(new) rubygems_1.8.15-1~bpo60+1.debian.tar.gz optional ruby
(new) rubygems_1.8.15-1~bpo60+1.dsc optional ruby
(new) rubygems_1.8.15-1~bpo60+1_all.deb optional ruby
package management framework for Ruby libraries/applications
 This is a way to package Ruby libraries/applications for distribution.
 RubyGems provides the ability to manage concurrent versions of libraries and
 dependencies between those libraries. Using RubyGems, you can:
   * download and install Ruby libraries easily
   * not worry about libraries A and B depending on different versions of
     library C
   * easily remove libraries you no longer use
 .
 This package provides Rubygems for Ruby 1.8. In Ruby 1.9.X, Rubygems is
 provided with the interpreter.
(new) rubygems_1.8.15.orig.tar.gz optional ruby


Changes:
rubygems (1.8.15-1~bpo60+1) squeeze-backports; urgency=low
 .
  * Backport to squeeze-backports.
  * Updated build-dep on debhelper to pull in proper version from BPO
  * Add myself to Uploaders.
 .
rubygems (1.8.15-1) unstable; urgency=low
 .
  * New upstream release.
 .
rubygems (1.8.12-2) unstable; urgency=low
 .
  * debian/control: Build-Depends netbase as well to pass test cases.
    Thanks to Daniel Schepler for reporting and resolving this issue.
    (Closes: #655549)
  * debian/control: Priority's of rubygems1.8 and rubygems-doc are now
    extra, fixing lintian warnings.
  * debian/copyright: Fixed lintian warnings.
 .
rubygems (1.8.12-1) unstable; urgency=low
 .
  * New upstream release.
 .
rubygems (1.8.10-1) unstable; urgency=low
 .
  * debian/watch: point to rubygems.org
  * debian/copyright: change to a working url in Format: field
  * Add build-dependency on ruby-minitest.
  * switch to my @d.o email.
  * Refresh patches:
    + 08_tighter_search_regex.diff: drop.
    + 01_default_gem_path.diff: refresh.
    + disable-failing-tests.diff: refresh.
    + disable-tests-failing-as-root.diff: refresh.
  * Bump standards-version to 3.9.2. No changes needed.
  * disable-failing-tests.diff: add more failing tests.
 .
rubygems (1.7.2-1) unstable; urgency=low
 .
  [ Lucas Nussbaum ]
  * New upstream release.
  * Switch to gem2deb-based packaging. Rename source and binary packages.
  * Drop 50_add_missing_require_yaml.diff: fixed upstream.
  * Change 01_default_gem_path.diff:
    + executables are now installed to /usr/local/bin.
    + but the other files created by rubygems stay in /var/lib/gems/1.8.
    Several commenters in #448639 and #403407 argued in favor of the switch to
    /usr/local/bin. Those two bugs can therefore be closed. However, the issue
    is not completely solved, as rubygems still installs files in /var/lib/gems.
    Nobody in the bug logs explained why that was an issue. If you care about
    it, please open a new bug. Closes: #448639, #403407
  * Add disable-failing-tests.diff: disable tests that are failing due to
    Debian-specific changes to rubygems.
 .
  [ Daigo Moriwaki ]
  * Switched the build framework from cdbs to dh. (thanks to Lucas)
 .
libgems-ruby (1.6.2-1) unstable; urgency=low
 .
  * New upstream release
  * debian/control:
    - Bumped up Standards-Version to 3.9.1.
    - The rubygems package recommends ruby-dev
      (Closes: #466189, #600165)
    - Ruby 1.8.7 or later is required by the upstream.
    - ruby1.9.1 is no longer required for build.
  * debian/changelog: Replaced the 'debianize' word.


Override entries for your package:

Announcing to debian-backports-changes@lists.debian.org


Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.


Reply to: