On Fri 2022-08-05 20:36:24 +0100, Adam D. Barratt wrote: > On Mon, 2021-11-29 at 20:45 +0000, Adam D. Barratt wrote: >> Control: tags -1 + confirmed >> >> On Wed, 2021-11-10 at 16:31 -0500, Daniel Kahn Gillmor wrote: >> > Please consider an update to publicsuffix in debian buster. >> > >> > This package reflects the state of the network, and keeping it >> > current is useful for all the packages that depend on it. >> > >> >> Please go ahead. > > Ping? We're in the process of organising the final point release for > buster, as support for it transitions over to the LTS team, so if you > would still like to fix it via pu then the upload needs to happen soon.
Sorry, I'm a bit confused by this. afaict, #999430 refers to a version of publicsuffix that is already shipping in buster, 20211109.1735-0+deb10u1: 0 dkg@alice:~$ rmadison publicsuffix -s buster publicsuffix | 20211109.1735-0+deb10u1 | oldstable | source, all 0 dkg@alice:~$ So i think this can be closed. On the basis that https://www.debian.org/News/2022/ doesn't show any recent final point release for buster, i'll go ahead and open a new request for the latest publicsuffix as an update, though. Thanks for handling the debian point releases! I know they're complicated to coordinate. fwiw, i'm handling the generation of publicsuffix point releases in an automated way these days, so that they should only ever include updates of this central file. If there's any way to get a blanket OK for upload of this type of narrowly-targeted update, it would help me in maintenance to not have to wait for a response and followup after the debdiff, at which point the update might no longer be the latest version. I understand the cost of making exceptions, though, so if that doesn't work for you, i will continue as i have been. All the best, --dkg
signature.asc
Description: PGP signature
