[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1029585: marked as done ([pre-approval] unblock: dpkg/1.21.19)

Your message dated Wed, 25 Jan 2023 21:11:35 +0100
with message-id <7241f0a9-c6ae-7fd9-12a1-4923894c8684@debian.org>
and subject line Re: Bug#1029585: [pre-approval] unblock: dpkg/1.21.19
has caused the Debian Bug report #1029585,
regarding [pre-approval] unblock: dpkg/1.21.19
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 owner@bugs.debian.org
immediately.)


-- 
1029585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029585
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: dpkg@packages.debian.org
Control: affects -1 + src:dpkg

Hi!

(Even though I've noticed no blocking hints, given that the package
is supposed to be frozen, I'm requesting this pre-approval explicitly
anyway through the normal procedures as usual and expected.)

[ Reason ]

This dpkg release fixes several regressions. Reverts the loong64 arch
support given the uncertain status with its changing ABI. And updates
few translations.

[ Tests ]

The lto regression fix includes unit tests. The rest were tested
manually, the reproducible one by messing with the file perms of the
source, the GnuPG ones by creating fresh keys in a clean user home.

[ Risks ]

The changes seem targeted and small to me.

[ 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 ]

The attached debdiff is unfiltered, you might want to filterdiff with:

  xzcat dpkg-1.21.18-1.21.19.debdiff.xz |
    filterdiff --exclude '*.po' --exclude '*.pot' \
               --exclude '*/man/*/*.pod' \
               --exclude '*/testsuite' --exclude '*/at/*.m4' \
               --exclude '*/configure'

Once (and iff) I get an approval, I'll upload to sid. I don't think
there's a need for an actual unblock hint though? :) But in any case:

unblock dpkg/1.21.19

Thanks,
Guillem

Attachment: dpkg-1.21.18-1.21.19.debdiff.xz
Description: application/xz


--- End Message ---
--- Begin Message --- 
confirmed

Hi Guillem,

On 25-01-2023 00:31, Guillem Jover wrote:

(Even though I've noticed no blocking hints, given that the package
is supposed to be frozen, I'm requesting this pre-approval explicitly
anyway through the normal procedures as usual and expected.)
Thanks, that's indeed intended. Blocking would only prevent migration to testing, while for toolchain packages, the damage can already be done. We haven't agreed with ftp-master to use our power to block uploads to unstable. 


This dpkg release fixes several regressions. Reverts the loong64 arch
support given the uncertain status with its changing ABI. And updates
few translations.


Assuming the upload happens within a week or so, please go ahead.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: