Re: Is bug #399214 release critical? (Upgrade from version not in debian currently)
severity 399214 important thanks On Mon, Dec 18, 2006 at 12:24:01PM +0100, Tom Cato Amundsen wrote: > Is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399214 release > critical? > The version of solfege in etch fails to upgrade from a version that does > _not exist_ in neither stable, testing or sid now. It was a version that > earlier was in testing, but has been replaced by a more recent version. Nope, upgrades from unreleased packages are not release-critical. Especially not in this case, where the bug is in the old package being upgraded from. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Is bug #399214 release critical? (Upgrade from version not in debian currently)
Daniel J. Priem wrote: > > I think such bugs can be easily closed. The bug is closed with the last upload to sid, the question is whether it should be considered as RC and if the release team will approve the fix for Etch. When upgrading from Sarge to Etch there is no issue, but for users like me (that particular machine is running testing) it is a real PITA. I intend to upgrade and remain on Etch (stable) when it is released, so I'll have a broken package. There's no way to remove/purge or upgrade it (well, there is, but it would be difficult for the average user). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Is bug #399214 release critical? (Upgrade from version not in debian currently)
On Mon, Dec 18, 2006 at 12:55:47PM +0100, Daniel J. Priem wrote: > I think such bugs can be easily closed. > I disagree. If it was previously in testing, it could conceivably have been removed without the user noticing. In which case, it would be acceptable for the user to expect that the upgrade would be handled. Now, if there were a way to notify users of packages removed for buginess or whatever and advising them to remove the packages, you might have a point. However, the user at no time, AFAICT, was notified that removal of the package would be a good idea. Regards, -Roberto -- Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: Is bug #399214 release critical? (Upgrade from version not in debian currently)
I think such bugs can be easily closed. Regards Daniel Tom Cato Amundsen <[EMAIL PROTECTED]> writes: > Is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399214 release > critical? > > The version of solfege in etch fails to upgrade from a version that does > _not exist_ in neither stable, testing or sid now. It was a version that > earlier was in testing, but has been replaced by a more recent version. > -- > Tom Cato Amundsen <[EMAIL PROTECTED]> http://www.solfege.org/ > GNU Solfege - free ear traininghttp://www.gnu.org/software/solfege/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
