On 2017-04-13 11:03, Michael Prokop wrote:
* Emilio Pozuelo Monfort [Thu Apr 13, 2017 at 11:48:56AM +0200]:On 13/04/17 11:43, Adam D. Barratt wrote:
[...]
> Publishing things via -updates is not zero-effort so is not necessarily done > for every update.Completely understandable.ACK, and thanks for mentioning that, Adam. Just to clarify: Publishing things via *-updates is a manual task, which explains the different times in this situation until it's "fixed"? And this process won't change in the foreseeable future and people affected by this should take different actions to avoid running into this?
The process is unlikely to change, no. Even in the best case, the packages need to be uploaded and accepted into proposed-updates (the accept being a manual action), then copied over to -updates (again being a manual action, involving an ssh trigger to ftp-master) and an announcement mail written and sent / approved to coincide with the dinstall (well, mirror push) in which users will start to see the package.
The timing of the announcement sometimes adds to the delay in getting the packages released. Changes to -updates require a dinstall / mirror update to be visible to users, and experience with point releases suggests that some users will get confused / concerned if updates appear without an announcement; similarly, we don't want to send the announcement out too soon and have users not be able to find the update.
PS: jessie-updates still has tzdata 2017a-0+deb8u1, is 2017b-0+deb8u1 now going in only with the upcoming point release on 6th of May or is there any chance to have this fixed via -updates sooner (if so let me know whom I own a drink then. :))?
See my follow-up to Emilio's mail. It'll hopefully be sorted in the next few days.
Regards, Adam