Bug#1058589: developers-reference: please mention urgency=critical/emergency for completeness

2023-12-13 Thread Daniel Gröber
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 ar

Bug#1058589: developers-reference: please mention urgency=critical/emergency for completeness

2023-12-13 Thread Daniel Gröber
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

Bug#1058589: developers-reference: please mention urgency=critical/emergency for completeness

2023-12-13 Thread Daniel Gröber
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

Re: Does iproute2 moving config files to /usr/lib violate section 10.7.2?

2023-09-16 Thread Daniel Gröber
Sam, Russ, Bill, Thanks for your input. To be quite frank I still don't see how the interpretation of allowing configuration files outside of /etc can be supported based on the policy text. Ultimately I'm just concerned about the UX aspects of admins suddenly having to go hunting for config

Does iproute2 moving config files to /usr/lib violate section 10.7.2?

2023-09-14 Thread Daniel Gröber
Hello debian-policy, iproute2 has moved it's config files that were traditionally at /etc/iproute2 to /usr/lib/iproute2 due to an upstream change. I've tried to convince the maintainer(s) that this is a bad idea in Bug#1051577, when this was shot down I filed Bug#1051847 as severity:serious on