Sebastian, > On 24. 6. 2021, at 10:43, Sebastian Ramacher <sramac...@debian.org> wrote: > > Control: severity -1 serious > > On 2021-06-24 10:35:15, Ondřej Surý wrote: >> Control: severity -1 important >> >> Hi, >> >>> I've prepared an NMU for libyang (versioned as 1.0.225-1.1) and >>> uploaded it to DELAYED/2. Please feel free to tell me if I >>> should delay it longer. >> >> The NMU won't work in this case, because we need to prepare update for the >> testing. I am going to temporarily downgrade the severity to important to >> prevent the removal from testing. > > libyang isn't a key package, so once the autopkgtests pass, the NMU will > be a candidate for migration. If there's not enough time for it to > migrate before the start of of the full freeze, I will ask to age it > appropriately.
Well, somehow I thought we are already in full freeze. Please upload your NMU directly in the archive. My 16-port switch had died just today and I don’t have > Please don't play severity ping pong. Sorry, but the severity is a **maintainers** decision. You are the one playing the severity ping-pong. I am not going to lower it again. > Failing autopkgtests are considered a regression by the release team > and are therefore serious. And it’s perfectly ok to temporarily lower the priority, so the package doesn’t get kicked out (I know the activity on the bug would also reset the timer). Ondrej -- Ondřej Surý (He/Him) ond...@sury.org
