Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
Santiago Vila [EMAIL PROTECTED] writes: Robert Bihlmeyer wrote: (b) it's dubious whether another potato point release will be done at all. How can you be so certain about the dubiousness of that? :-) Where in my sentence is there any notion of certainity? We should consider *all* the possibilities, including (but not limited to) that the release of woody will be delayed and there will be more potato point releases. Sure that's possible, but in the light of a new release to work on, rather than updates to an old one, I don't think its probable. Doing a large backport that perhaps won't be used at all ... I wouldn't do that. Releasing a potato update that included the appropriate don't do that, then warning in the docs ... that's another thing. -- Robbe signature.ng
Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
On Tue, 10 Jul 2001 15:57, Robert Bihlmeyer wrote: Matt Zimmerman [EMAIL PROTECTED] writes: The bug is not serious enough to justify an update to stable, especially not when we are preparing for a new release. You could of course upload a potato package anyway, and punt the decision to the release managers. AFAIK the package will end up in Adrian Bunk [EMAIL PROTECTED] runs a repository of packages back-ported to Potato (mainly for 2.4.x kernels and associated things). The repository is on http://www.fs.tum.de/~bunk/kernel-24.html . Why not ask to put your package on the same site? Or why not just put it on your own web page and tell anyone who asks about it (also tell one of the lists so that people who search the web can find it). -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
Santiago Vila [EMAIL PROTECTED] writes: Robert Bihlmeyer wrote: (b) it's dubious whether another potato point release will be done at all. How can you be so certain about the dubiousness of that? :-) Where in my sentence is there any notion of certainity? We should consider *all* the possibilities, including (but not limited to) that the release of woody will be delayed and there will be more potato point releases. Sure that's possible, but in the light of a new release to work on, rather than updates to an old one, I don't think its probable. Doing a large backport that perhaps won't be used at all ... I wouldn't do that. Releasing a potato update that included the appropriate don't do that, then warning in the docs ... that's another thing. -- Robbe signature.ng Description: PGP signature
Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
On Tue, 10 Jul 2001 15:57, Robert Bihlmeyer wrote: Matt Zimmerman [EMAIL PROTECTED] writes: The bug is not serious enough to justify an update to stable, especially not when we are preparing for a new release. You could of course upload a potato package anyway, and punt the decision to the release managers. AFAIK the package will end up in Adrian Bunk [EMAIL PROTECTED] runs a repository of packages back-ported to Potato (mainly for 2.4.x kernels and associated things). The repository is on http://www.fs.tum.de/~bunk/kernel-24.html . Why not ask to put your package on the same site? Or why not just put it on your own web page and tell anyone who asks about it (also tell one of the lists so that people who search the web can find it). -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page
Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
Matt Zimmerman [EMAIL PROTECTED] writes: The bug is not serious enough to justify an update to stable, especially not when we are preparing for a new release. You could of course upload a potato package anyway, and punt the decision to the release managers. AFAIK the package will end up in potato-proposed-updates where interested users of stable can get it. The chances of it appearing in potato are pretty slim, of course, because (a) it sounds like a big enough change, that even a backport (should you take this work on you) is probably too destabilizing, (b) it's dubious whether another potato point release will be done at all. Explain to the user that the fixed version is already in 'testing', and will be included in the next stable release. If you wish, you can leave the bug open (and downgrade it, it doesn't qualify as important) so that users know that they can fetch the latest version from testing. You should definitely tag it with potato if you keep it open. -- Robbe signature.ng
Re: Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
On Wed, 11 Jul 2001 00:17:43 +0200 (CEST), Santiago Vila [EMAIL PROTECTED] wrote: Robert Bihlmeyer wrote: (b) it's dubious whether another potato point release will be done at all. How can you be so certain about the dubiousness of that? :-) We should consider *all* the possibilities, including (but not limited to) that the release of woody will be delayed and there will be more potato point releases. hello, I'd like to suggest renaming it to grub1 or something and moving the woody version to potato, so we still have the chance to use both of them. regards, -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
On Tue, Jul 10, 2001 at 01:25:08PM +1000, Jason Thomas wrote: was wondering if anyone could suggest how to handle this bug. It is fixed in new versions of grub. The bug is not serious enough to justify an update to stable, especially not when we are preparing for a new release. It's certainly not necessary to remove grub from stable, as many people use it with no problems (I use grub on my potato system). Explain to the user that the fixed version is already in 'testing', and will be included in the next stable release. If you wish, you can leave the bug open (and downgrade it, it doesn't qualify as important) so that users know that they can fetch the latest version from testing. However, the bug is fixed, and the usual policy for fixed bugs is to close them. Some people use the 'fixed' tag for this purpose, but it only seems to cause confusion, since the BTS reports such bugs as 'fixed in NMU'. -- - mdz
Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
Matt Zimmerman [EMAIL PROTECTED] writes: The bug is not serious enough to justify an update to stable, especially not when we are preparing for a new release. You could of course upload a potato package anyway, and punt the decision to the release managers. AFAIK the package will end up in potato-proposed-updates where interested users of stable can get it. The chances of it appearing in potato are pretty slim, of course, because (a) it sounds like a big enough change, that even a backport (should you take this work on you) is probably too destabilizing, (b) it's dubious whether another potato point release will be done at all. Explain to the user that the fixed version is already in 'testing', and will be included in the next stable release. If you wish, you can leave the bug open (and downgrade it, it doesn't qualify as important) so that users know that they can fetch the latest version from testing. You should definitely tag it with potato if you keep it open. -- Robbe signature.ng Description: PGP signature
Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
Robert Bihlmeyer wrote: (b) it's dubious whether another potato point release will be done at all. How can you be so certain about the dubiousness of that? :-) We should consider *all* the possibilities, including (but not limited to) that the release of woody will be delayed and there will be more potato point releases.
Re: Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
On Wed, 11 Jul 2001 00:17:43 +0200 (CEST), Santiago Vila [EMAIL PROTECTED] wrote: Robert Bihlmeyer wrote: (b) it's dubious whether another potato point release will be done at all. How can you be so certain about the dubiousness of that? :-) We should consider *all* the possibilities, including (but not limited to) that the release of woody will be delayed and there will be more potato point releases. hello, I'd like to suggest renaming it to grub1 or something and moving the woody version to potato, so we still have the chance to use both of them. regards, -- Robert Millan Debian GNU (Hurd) user zeratul2 wanadoo es http://getyouriso.org/
Re: [zeratul2@wanadoo.es: Bug#102811: grub: cannot access newer ext2 filesystems]
On Tue, Jul 10, 2001 at 01:25:08PM +1000, Jason Thomas wrote: was wondering if anyone could suggest how to handle this bug. It is fixed in new versions of grub. The bug is not serious enough to justify an update to stable, especially not when we are preparing for a new release. It's certainly not necessary to remove grub from stable, as many people use it with no problems (I use grub on my potato system). Explain to the user that the fixed version is already in 'testing', and will be included in the next stable release. If you wish, you can leave the bug open (and downgrade it, it doesn't qualify as important) so that users know that they can fetch the latest version from testing. However, the bug is fixed, and the usual policy for fixed bugs is to close them. Some people use the 'fixed' tag for this purpose, but it only seems to cause confusion, since the BTS reports such bugs as 'fixed in NMU'. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
