Your message dated Wed, 8 Mar 2023 21:02:38 +0100
with message-id <c1290b84-57f5-33e0-2f9d-e4945ac12...@debian.org>
and subject line Re: Bug#1031910: [pre-approval] unblock: dpkg/1.21.21
has caused the Debian Bug report #1031910,
regarding [pre-approval] unblock: dpkg/1.21.21
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1031910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: d...@packages.debian.org
Control: affects -1 + src:dpkg
Hi!
Please pre-approve the dpkg 1.21.21 upload.
[ Reason ]
The loong64 arch support got reverted as there was a bug filed
requesting to change its GNU triplet and multiarch tuple after this
had been agreed on previously. Clarification was requested and as that
was blocking the previous pre-approval, it was decided that the best
would be to temporarily revert it until and if things had been cleared
out. Upstream now has decided to go back to the previous triplets and
tuples (what was already in dpkg), so this reverts that revert.
There are also a couple of translation updates included. One was a
fix for an issue that made the CI checks fail that slipped in due
to a release script deficiency, the other is a translation update
received after the last upload.
[ Impact ]
Not including this means the port cannot easily be added into the
infra as it requires for the stable dpkg to support it. And its
addition would end up being requested as part of a stable update
(as has happened with other ports in the past).
[ Tests ]
The arch change already had tests, and it's in any case a data file
change.
[ Risks ]
Very minimal, and the change has already been part of several dpkg
releases before it got reverted.
[ Checklist ]
[√] all changes are documented in the d/changelog
[√] I reviewed all changes and I approve them
[√] attach debdiff against the package in testing
[ Other info ]
Attached the unfiltered debdiff, you might want to filterdiff with:
xzcat dpkg-1.21.20-1.21.21.debdiff.xz |
filterdiff --exclude '*.po' --exclude '*.pot' \
--exclude '*/man/*/*.pod' \
--exclude '*/testsuite' --exclude '*/at/*.m4' \
--exclude '*/configure'
unblock dpkg/1.21.21
Thanks,
Guillem
dpkg-1.21.20-1.21.21.debdiff.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Hi,
On 25-02-2023 13:32, Sebastian Ramacher wrote:
Control: tags -1 confirmed
$ rmadison dpkg -s unstable,testing
dpkg | 1.21.21 | testing | source, amd64, arm64, armel,
armhf, i386, mips64el, mipsel, ppc64el, s390x
dpkg | 1.21.21 | unstable | source, amd64, arm64, armel,
armhf, i386, mips64el, mipsel, ppc64el, s390x
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
