Bug#671066: ftp.debian.org: upload urgencies should not accumulate
On Tue, 1 May 2012, Cyril Brulebois wrote:
> Adam D. Barratt <adam@adam-barratt.org.uk> (01/05/2012):
> > It's been that way for at least four years; I suspect a good deal
> > longer but don't have the evidence immediately available. The start
> > of the release team's britney1 repository, when we took over direct
> > running of it rather than ftp-master doing so on our behalf, already
> > includes urgencies being "sticky".
>
> Thanks for the confirmation, closing as not a bug accordingly.
Hmm, "not a bug accordingly?". It may not be a bug in the sense that
"it follows the specifications", but I was not reporting it as a
misbehaviour with respect to the specifications, but as *design flaw*.
Design flaws do not get fixed magically by saying that "behaviour
follow the specifications".
It is not the changes who have urgencies, it is uploads who have them.
If a package in unstable does not propagate to testing and there is a
new upload, the maintainer is fully aware that the upload supersedes
the previous version in unstable *for all purposes*, and this should
mean that the urgency of the new upload should supersede as well the
urgency of the current version at unstable for consistency.
Whether the new package is based on the "same" branch or on "another"
branch is not something britney should try to guess, because it will
often fail at doing so.
Anyway, I'm afraid you guys are now so used to the new behaviour that
there is no room for debate here, which is sad, so I'll stop here.
BTW: I'm curious: Am I really the very first maintainer to complain
about this behaviour? That would be really surprising.
Reply to: