Bug#931118: unblock: debian-keyring/2019.06.25
On Sun, Jun 30, 2019 at 10:12:32PM +0200, Mattia Rizzolo wrote: > On Sun, Jun 30, 2019 at 08:38:52PM +0200, Paul Gevers wrote: > > On 26-06-2019 16:10, Mattia Rizzolo wrote: > > > The last upload of debian-keyring done yesterday updates the > > > security team key. See #928222 for more context. > > > > > > I think it would be good if this change could find its way into > > > buster. With this package providing data only, there are no > > > regression potentials, imho. Also, with it shipping mostly binary > > > files, a debdiff is quite useless. > > > > The time for unblocks for buster has come and gone. The deadline was > > last Tuesday, we are now in deep freeze and we were not able to > > process your unblock request and give it an exception. I assume this > > could be fixed via a stable release update targeting buster, such > > that this can be fixed in the first point release. If that doesn't > > work for you and I am wrong, please just close this bug. > > Sure, it can be done, it just feels incredibly silly from my point of > view (with this package being data only, and either way I'd suspect a > pu upload being less "tested" in a case like this). > > Not to mention that I personally have little interest in doing this > work (I just recalled the security team opening that bug, then it > being fixed very late, so I asked an explicit unblock). keyring-maint have historically tried to do a keyring update as close to the release as possible, and this has always had an unblock in the past; jessie has 2015.04.10 (release date: 2014-04-26) and stretch has 2017.05.28 (release date: 2017-06-17). If we've missed it this time then so be it. J. -- Revd Jonathan McDowell, ULC | Don't hit the keys so hard, it hurts.
Bug#931118: unblock: debian-keyring/2019.06.25
On Sun, Jun 30, 2019 at 08:38:52PM +0200, Paul Gevers wrote: > On 26-06-2019 16:10, Mattia Rizzolo wrote: > > The last upload of debian-keyring done yesterday updates the security > > team key. See #928222 for more context. > > > > I think it would be good if this change could find its way into buster. > > With this package providing data only, there are no regression > > potentials, imho. Also, with it shipping mostly binary files, a debdiff > > is quite useless. > > The time for unblocks for buster has come and gone. The deadline was > last Tuesday, we are now in deep freeze and we were not able to process > your unblock request and give it an exception. I assume this could be > fixed via a stable release update targeting buster, such that this can > be fixed in the first point release. If that doesn't work for you and I > am wrong, please just close this bug. Sure, it can be done, it just feels incredibly silly from my point of view (with this package being data only, and either way I'd suspect a pu upload being less "tested" in a case like this). Not to mention that I personally have little interest in doing this work (I just recalled the security team opening that bug, then it being fixed very late, so I asked an explicit unblock). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Bug#931118: unblock: debian-keyring/2019.06.25
retitle 931118 buster-pu: package debian-keyring/2019.06.25~deb10u1 user release.debian@packages.debian.org usertags 931118 - unblock usertags 931118 pu tags 931118 buster thanks Hi Mattia, On 26-06-2019 16:10, Mattia Rizzolo wrote: > The last upload of debian-keyring done yesterday updates the security > team key. See #928222 for more context. > > I think it would be good if this change could find its way into buster. > With this package providing data only, there are no regression > potentials, imho. Also, with it shipping mostly binary files, a debdiff > is quite useless. The time for unblocks for buster has come and gone. The deadline was last Tuesday, we are now in deep freeze and we were not able to process your unblock request and give it an exception. I assume this could be fixed via a stable release update targeting buster, such that this can be fixed in the first point release. If that doesn't work for you and I am wrong, please just close this bug. Sorry. Paul signature.asc Description: OpenPGP digital signature
Bug#931118: unblock: debian-keyring/2019.06.25
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: debian-keyr...@packages.debian.org Dear RT, The last upload of debian-keyring done yesterday updates the security team key. See #928222 for more context. I think it would be good if this change could find its way into buster. With this package providing data only, there are no regression potentials, imho. Also, with it shipping mostly binary files, a debdiff is quite useless. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
