El 31/08/21 a las 19:01, Jakub Ru啪i膷ka escribi贸: > > I've opened transition bug #993027 > > Got ack from RT, I've uploaded knot-3.1.1-4 into unstable to start the > transition. > > Do I need to wait until the new knot built on all archs before uploading > depending knot-resolver-5.4.1-2 or is there a smart mechanism ensuring > build against correct/latest version?
Well, I am not sure of that. I'd wait to have it built on all archs (and ping debian-buildd if needed), as it is the case right now. But I think also that such smart mechanism exists if you don't want to wait. > > Yes, that I should fix the issue with the next (first) bullseye-point > > release after it's been fixed in unstable. ACK. > > I've prepared knot-resolver-5.3.1-2+deb11u1 with the backport of > upstream fix in new debian/bullseye salsa branch: > > https://salsa.debian.org/dns-team/knot-resolver/-/commits/debian/bullseye > > Please review my changes before I attempt the bullseye upload as I'm new > to this process. > diff --git a/debian/changelog b/debian/changelog index a38aa258..0cf5bc71 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +knot-resolver (5.3.1-2+deb11u1) bullseye; urgency=medium Version in stable is 5.3.1-1, so it would be 5.3.1-1+deb11u1. You shouldn't bump the debian revision number. It will be longer the case for kresd, but suppose you upload a more recent revision to testing or unstable. If you 5.3.1-2 would be < 5.3.1-2+deb11u1, and user would have a problem to upgrade it. > > 馃悰, > Jakub 馃敤, -- S
signature.asc
Description: PGP signature
