On 2014-01-02 17:01, Theodore Ts'o wrote:
On Thu, Jan 02, 2014 at 04:58:12PM +0000, Adam D. Barratt wrote:Urgencies for new packages are ignored iff they are "higher" than the default urgency configured in britney. The default was recently changed to "medium", meaning that a high or critical urgency package is forced to wait for five days; packages uploaded as "medium" or "low" will migrate after five or 10 days, as appropriate.So it still seems to me this message is misleading. "Ignoring high urgency setting for NEW package" The xzgv package did not have a "high" urgency setting.
It did, although I appreciate that it might not be immediately obvious.The list of urgencies britney processes is originally provided by ftp-master (as part of each process-upload run) and contains a record of the source package name, version number and urgency setting for each source upload. That list contains _all_ uploads which are seen by dak on ftp-master, whether they are to unstable, experimental or (old)stable. In the case of xzgv, it therefore includes the urgency=high security upload.
Urgencies are "sticky", meaning that for any given migration the effective urgency used is the highest of all uploads with version numbers higher than the package in testing - i.e. if 1.0-1 is uploaded at "high", and -2 at "medium", then -2 will be eligible to migrate after two days. In the case of a "new" package, there is no version of the package in testing, so all versions in the urgency record are considered (as britney has no concept of what version used to be in testing).
Maybe itmeant to say "higher than low", but if the default default uregency in britney is now "medium", then that message is even more wrong, as wellas being misleading. Am I missing something?
Yes. :-) Regards, Adam