[DRE-maint] Bug#495320: rubygems1.8: Package name change causes data loss

Matijs van Zuijlen Matijs.van.Zuijlen at xs4all.nl
Sat Aug 16 08:22:00 UTC 2008

Package: rubygems1.8
Version: 1.2.0-2
Severity: grave
Justification: causes non-serious data loss

Steps to reproduce the problem:

1. Note new rubygems1.8 package
2. Install new rubygems1.8 package
3. Note that rubygems is now gone from debian
4. Purge rubygems package

Expected result: old gems are still installed and ready to use

Actual result: old gems are gone

You may chalk it up to user error, but I like to purge packages that have
completely vanished from debian: No need to keep configuration around that
I'm never going to use again.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages rubygems1.8 depends on:
ii  rdoc1.8              Generate documentation from Ruby s
ii  ruby1.8              Interpreter of object-oriented scr

rubygems1.8 recommends no packages.

Versions of packages rubygems1.8 suggests:
ii  build-essential               11.4       Informational list of build-essent
ii  ruby1.8-dev          Header files for compiling extensi
pn  rubygems-doc                  <none>     (no description available)

-- no debconf information

More information about the Pkg-ruby-extras-maintainers mailing list