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
On 16/08/08 at 15:30 +0200, Michael Schutte wrote:
On Sat, Aug 16, 2008 at 02:36:51PM +0200, Paul van Tilburg wrote:
Hi!
This is a small update. I removed the parts that I flagged as to be
ignored for now in the previous summary.
Note that I am leaving for a conference with a few
On Sat, 16 Aug 2008, Michael Schutte wrote:
On Sat, Aug 16, 2008 at 02:36:51PM +0200, Paul van Tilburg wrote:
Finally, I have noticed there are a few packages of our that should get
a release block exception, but I haven't created a script to determine
which of our packages have a newer
Paul van Tilburg dijo [Sat, Aug 16, 2008 at 02:36:51PM +0200]:
Hi!
This is a small update. I removed the parts that I flagged as to be
ignored for now in the previous summary.
Note that I am leaving for a conference with a few hours and I won't be
able to deal with the still pending
On Sat, 16 Aug 2008, Michael Schutte wrote:
[…]
| libcairo-ruby 487204
ruby1.9/hppa again, but we’ll force it in then (see Lucas’ mail).
Failed on alpha too. I’ll have it given back.
| libgems-ruby493309 [new upstream release]
False alarm on this one. The
