Hi Feri On 05-03-2019 10:39, wf...@niif.hu wrote: >> upload 2.0.1-1 to unstable after that > > Without a definite ACK from you?
If that changes meet the requirements, yes: https://release.debian.org/buster/freeze_policy.html >> provide us with a debdiff between 2.0.1~rc5-1 and 2.0.1-1 in this bug >> report > > That's what I submitted in the first place, so already done. A, missed that then. > I'm tragic at simulating archive maintenance in my head. :) Upload time > of day certainly is a factor in such computations, and I don't know the > timing of the cron jobs. If you happen to know offhand: which was the > last second for uploads targeting buster to not need a manual unblock? No, I don't, as it also depends on the moment we actually make the change. But as far as I counted, the package had to be installed on 2 March 19:00 UTC (that is when a new day starts for britney), assuming we will deploy the full freeze before the final full britney run on 12 March of 22:00 UTC. Paul
signature.asc
Description: OpenPGP digital signature
