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

Bug#1107255: marked as done (pre-approval/unblock: dpkg/1.22.20)

Your message dated Fri, 06 Jun 2025 15:50:30 +0000
with message-id <E1uNZKw-008Os1-0D@respighi.debian.org>
and subject line unblock dpkg
has caused the Debian Bug report #1107255,
regarding pre-approval/unblock: dpkg/1.22.20
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.)


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

Please pre-approve/unblock package dpkg.

[ Reason ]

This is a minor update including:

  - Translation updates.
  - A couple of fixes for the sqv and sq OpenPGP backends, one to
    gracefully handle absent keyrings on disk with both tools, the
    other to make sq operate in stateless mode (like all other
    backends).

(For ref, more detail was provided in the 1.22.19 pre-approval/unblock
request, including the proposed changes.)

[ Impact ]

The absent keyrings issue affects current minimal chroots that have
no keyring package installed (debian-keyring nor
debian-tag2upload-keyring) such as on buildds, and generate very
alarming error messages (which are only warning level from dpkg-source
PoV).

The stateless fix avoids relying on certificates from the sq certstore,
unlike all other OpenPGP backends, which would produce different results.

[ Tests ]

Unpacking a source package with no debian-keyring installed, no longer
emits the sqv error messages, and now only generates the expected
dpkg-source warnings.

[ Risks ]

The changes are rather minimal, and the risks seem low. The keyrings
fixes do not really change the semantics of the operations, just
suppress the alarming messages.

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

I've included the entire debdiff (compressed) against the previous
version, the following is the recipe that filters all auto-generated
and translation changes:

  $ xzcat dpkg-1.22.19-1.22.20.debdiff.xz \
    | filterdiff \
      -x '*.po' -x '*.pot' -x '*/man/*/*.pod' \
      -x '*.in' -x '*/configure' -x '*/build-aux/*' -x '*/src/at/*' \
    # EOC

I'd expect this to be the last dpkg release targeting Debian trixie.


unblock dpkg/1.22.20

Thanks,
Guillem

Attachment: dpkg-1.22.19-1.22.20.debdiff.xz
Description: application/xz


--- End Message ---
--- Begin Message --- 
Unblocked dpkg.

--- End Message ---
Reply to: