On Sat, Jan 25, 2020 at 01:00:16PM +0100, Laurent Bigonville wrote: > Le 25/01/20 à 12:26, Ricardo Mones a écrit : > > On Fri, Jan 24, 2020 at 01:04:08PM +0100, Laurent Bigonville wrote: > > > Le 24/01/20 à 12:13, Ricardo Mones a écrit : > > > > Hi Laurent, > > > > > > > > On Fri, Jan 24, 2020 at 10:50:51AM +0100, Laurent Bigonville wrote: > > > > > Control: tags 949720 + patch > > > > > Control: tags 949720 + pending > > > > > > > > > > > > > > > Dear maintainer, > > > > > > > > > > I've prepared an NMU for sylpheed (versioned as 3.7.0-5.1) and > > > > > uploaded it to DELAYED/3. Please feel free to tell me if I > > > > > should delay it longer. > > > > Thanks for the patch! Given it's not even a RC bug I don't understand > > > > such a hurry, am I missing something? > > > sylpheed is marked as lowNMU I believe > > Indeed, but if you really think lowNMU means you can do NMUs like this > > one I'd suggest you to read again what lowNMU means. > https://wiki.debian.org/LowThresholdNmu describes what it is: > > > > The maintainers and maintainer groups listed below declare that their > > packages (all, or the ones listed specifically below) may be fixed and > > uploaded without delay, at any time, as long as the NMU procedure > > <http://www.debian.org/doc/developers-reference/pkgs.html#nmu> in the > > Debian Developer's Reference is otherwise followed. You don't need to > > contact the maintainers beforehand, and you don't need to use a delayed > > upload queue. If the package maintainer or maintainer group is active, > > it is polite to let them have a stab at fixing the problem first. > > > > Every change should be to fix a reported bug. Changes should not be > > frivolous. For example, don't change from debhelper to cdbs just because > > you prefer it that way; if you really want to make such big changes to > > the package, talk with the maintainer or maintainer group first, and > > maybe offer to adopt the package. > > The NMU procedure describes: > > > Unless you have an excellent reason not to do so, you must then give > > some time to the maintainer to react (for example, by uploading to the > > |DELAYED| queue). Here are some recommended values to use for delays: > > > > * Upload fixing only release-critical bugs older than 7 days, with > > no maintainer activity on the bug for 7 days and no indication > > that a fix is in progress: 0 days > > * Upload fixing only release-critical bugs older than 7 days: 2 days > > * Upload fixing only release-critical and important bugs: 5 days > > * Other NMUs: 10 days > > > Ergo any bugs (including important bugs and "Other NMU") can be uploaded > without delay if the package is marked as LowThresholdNmu > > Well this is at least my understanding.
You must be using some more info because given the examples cited in the
NMU procedure I fail to conclude that in a package which is actively
maintained, an important bug which is just a few _hours_ old can be NMUed
to the 3 day queue.
> >
> > > and I'm not sure about the real consequences of having the 2 libraries
> > > loaded at the same time, so I prefer to see this fixed rapidly.
> > I don't think that could eat your homework, but I agree it's better to
> > have this fixed soon :)
>
> I've canceled my NMU
Thanks, just uploaded the packages. Unfortunately had to leave the town
yesterday because a late-notified funeral and could not do it earlier.
regards,
--
Ricardo Mones
~
Quantity derives from measurement, figures from quantities,
comparisons from figures, and victories from comparisons.
Sun Tzu
signature.asc
Description: PGP signature
