Hi Alexander, On Thu, May 19, 2005 at 03:48:23AM +0200, Alexander Schmehl wrote: > * Adrian Bunk <[EMAIL PROTECTED]> [050518 22:20]: > > Package: tuxracer > > Version: 0.61-6.4 > > Severity: serious > > Tags: sarge > > > > This might technically not be a RC bug, but for not forgetting it: > > > > I don't see any reason for shipping sarge with the obsolete > > package in sarge instead of the transition package in unstable.
> I would agree (specialy, since I asked -release for it [1] and fucked up > the transition when getting sick and missing freeze), but: One day > the transition package, tuxracer 0.61-7, hit sid, I got several mails > (Uh... four I think), asking, why they can't stay with tuxracer. > Three of them pointed out, that ppracer, the inofficial successor of > tuxracer, runs quite slow on their hardware, while tuxracer still runs > fine. > And since tuxracer still compiles and runs, I tend to close this > bugreport, but it would be okay for me, to move tuxracer 0.61-7 to > sarge, if a release manger agrees to remove old software with dead > upstream. > But please note, that you then should push tuxracer-extras 0.5-2 into sarge, > too. I'm going to go ahead and push the tuxracer dummy packages into sarge, since AIUI this is still your preference as the maintainer. Cheers, -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
