Hi! On Mon, 2025-05-19 at 15:40:47 +0200, Marc Haber wrote: > On Mon, May 19, 2025 at 12:35:56PM +0000, Holger Levsen wrote: > > On Mon, May 19, 2025 at 01:56:42PM +0200, Marc Haber wrote: > > > the release team points people to the tracker to find out about a > > > package's migration status. I would be nice to know what would happen to > > > a package when it gets uploaded during a freeze. Maybe it is possible to > > > indicate things like "this is a key package and needs a manual unblock > > > to migrate at this time during the freeze" or "this package only has > > > superficial autopkgtests and needs a manual unblock to migrate" etc. > > > > https://tracker.debian.org/pkg/devscripts says > > ∙ ∙ blocked by freeze: is a key package (Follow the freeze policy when > > applying for an unblock) > > > > https://tracker.debian.org/pkg/diffoscope says > > ∙ ∙ not blocked: has successful autopkgtest > > > > https://tracker.debian.org/pkg/debian-security-support says > > ∙ ∙ Ignoring block request by freeze, due to unblock request by sramacher > > (and before that it said it was blocked by the freeze...) > > > > so I think most of what you want is there already? > > As Far as I know, this informtion only displays when a package is > actually waiting to migrate. I'd like to know how much pain I am > likely to feel when I do a new unstable upload.
And that changes depending on the stage of the freeze we are in. For example I uploaded a package with minor routine updates for the release, several days before the hard freeze, and thought it would get in even if crossing over the hard-freeze (as it has autopkgtests), as I had forgotten (as I usually do in these cases) that it was a key package. Having this information available in the tracker and the DDPO would probably have helped me in that case. (This particular case is not a big deal, because if there are migration worthy changes I'd need to do, I can always revert and request an unblock, but it's not ideal.) Thanks, Guillem
