Bug#1058589: developers-reference: please mention urgency=critical/emergency for completeness
On Wed, Dec 13, 2023 at 10:27:20PM +0100, Daniel Gröber wrote: > On Wed, Dec 13, 2023 at 07:24:49PM +, Holger Levsen wrote: > > On Wed, Dec 13, 2023 at 07:04:01PM +0100, Daniel Gröber wrote: > > > That's fine, but in that case this fact should be documented instead no? > > > Right now there's confusion across the docs what criticality levels are > > > available. Britney.conf and d-policy mention critical/emergency but > > > nothing > > > else even acknowledges they exist which is just confusing. > > > > I believe Debian policy should be changed then and not mention a severity > > which is not used in practice. > > Easier said than done. I see debian-policy@d.o is already CCed on this bug > so, opinions? > > Doesn't policy document the reality that these urgency values are in fact > usable? Do you not agree that britney does in fact support these? If I go > ahead and upload a package with urgency=critical will this be REJECTed by > ftp-master? Theses urgency values are historical. Their current behaviour is not defined. A long time ago in a distro not far away, packages for non-i386 were built manually by porters that used the urgency to decide which packages to build first. I do not think this is still the case, except that the security queue is build first by the autobuilders. Cheers, -- Bill. Imagine a large red swirl here.
Bug#1058589: developers-reference: please mention urgency=critical/emergency for completeness
control: reopen -1 control: reassign -1 debian-policy control: retitle -1 please stop mentioning urgency=critical thanks On Wed, Dec 13, 2023 at 10:27:20PM +0100, Daniel Gröber wrote: > On Wed, Dec 13, 2023 at 07:24:49PM +, Holger Levsen wrote: > > I believe Debian policy should be changed then and not mention a severity > > which is not used in practice. > Easier said than done. I see debian-policy@d.o is already CCed on this bug > so, opinions? debian-policy@ has been cc: on this bug because developers-reference and debian-policy share the same mailinglist. > Doesn't policy document the reality that these urgency values are in fact > usable? Do you not agree that britney does in fact support these? If I go > ahead and upload a package with urgency=critical will this be REJECTed by > ftp-master? It will not be rejected but setting the urgency has little practical relevance these days. You could also upload with urgency=low or urgency=high and that would be the same in practice. > If not they exist so why shouldn't they be documented in devref? - because it will make people use them - because people always think their issues are critical - because using them will not have an effect - because people will then complain that they have no effect - because all of this is a waste of someones time. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ https://showyourstripes.info signature.asc Description: PGP signature
Bug#1058589: developers-reference: please mention urgency=critical/emergency for completeness
On Wed, Dec 13, 2023 at 07:24:49PM +, Holger Levsen wrote: > On Wed, Dec 13, 2023 at 07:04:01PM +0100, Daniel Gröber wrote: > > That's fine, but in that case this fact should be documented instead no? > > Right now there's confusion across the docs what criticality levels are > > available. Britney.conf and d-policy mention critical/emergency but nothing > > else even acknowledges they exist which is just confusing. > > I believe Debian policy should be changed then and not mention a severity > which is not used in practice. Easier said than done. I see debian-policy@d.o is already CCed on this bug so, opinions? Doesn't policy document the reality that these urgency values are in fact usable? Do you not agree that britney does in fact support these? If I go ahead and upload a package with urgency=critical will this be REJECTed by ftp-master? If not they exist so why shouldn't they be documented in devref? --Daniel signature.asc Description: PGP signature
Bug#1058589: developers-reference: please mention urgency=critical/emergency for completeness
On Wed, Dec 13, 2023 at 07:04:01PM +0100, Daniel Gröber wrote: > That's fine, but in that case this fact should be documented instead no? > Right now there's confusion across the docs what criticality levels are > available. Britney.conf and d-policy mention critical/emergency but nothing > else even acknowledges they exist which is just confusing. I believe Debian policy should be changed then and not mention a severity which is not used in practice. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ half the worlds poor life in resource rich countries. HOME: https://youtu.be/Eu6ieWI3yjI signature.asc Description: PGP signature
Bug#1058589: developers-reference: please mention urgency=critical/emergency for completeness
Hi Holger, On Wed, Dec 13, 2023 at 02:19:14PM +, Holger Levsen wrote: > On Wed, Dec 13, 2023 at 01:55:21PM +0100, Daniel Gröber wrote: > > > 6.3.2. Selecting the upload urgency > > mentions only high, medum and low urgency values. Britney also > > supports critical and emergency. These should be documented as well. > > thanks for filing this bug report, even with a patch, basically! > > I'm sorry I still closing this as documenting those severities has no > practical benefit, and in fact might confuse people thinking using those > severities would be encouraged or useful, which is both not the case. That's fine, but in that case this fact should be documented instead no? Right now there's confusion across the docs what criticality levels are available. Britney.conf and d-policy mention critical/emergency but nothing else even acknowledges they exist which is just confusing. Thanks, --Daniel signature.asc Description: PGP signature
Bug#1058589: developers-reference: please mention urgency=critical/emergency for completeness
Source: developers-reference Severity: normal Hi, > 6.3.2. Selecting the upload urgency mentions only high, medum and low urgency values. Britney also supports critical and emergency. These should be documented as well. Something like: - The delays are currently 2, 5 or 10 days, depending on the urgency (high, medium or low). + The delays are currently 0, 2, 5 or 10 days, depending on the urgency: critical/emergency, high, medium or low respectively. Where emergency is simply an alias for critical. Thanks, --Daniel
