--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: debian-keyring@packages.debian.org, keyring-maint@debian.org
Control: affects -1 + src:debian-keyring
User: release.debian.org@packages.debian.org
Usertags: unblock
Please unblock package debian-keyring
The debian-keyring package consists of only data, not of any executable
code, nor anything related to executable code. It is not used by Debian
infrastructure, but only provided as a convenience for users to know
which developer/maintainer keys are valid at a given point in time.
We (the keyring-maint team) always try to provide an updated package
just before a stable package release; in this case, the upload I did
yesterday includes the latest changes to have in the keyring –barring
any unforseen emergency uploads we need to take care of– before the
release of Trixie.
No packages should rely on debian-keyring's data. This package update
does not incur in any possible breaking changes.
I understand packages must be accompanied by autopkgtests. We have this
as a pending bit to implement soon; the package does have a fair bit of
testing, which we always do (via "make test") before pushing to the
Debian servers, and which I did before building th package; I guess we
should include said test as an autopkgtest, but it's not the right time
to do so right now.
Please consider allowing it to migrate to Trixie.
[ Checklist ]
[✓] all changes are documented in the d/changelog
[✓] I reviewed all changes and I approve them
[ ] attach debdiff against the package in testing
I'm not attaching the debdiff as changes are completely in binary format
(OpenPGP packets added to a couple dozen files). Their nature is
detailed in debian/changelog.
Thanks a lot,
– Gunnar.
unblock debian-keyring/2025.07.26
--- End Message ---