Your message dated Wed, 11 Mar 2026 20:47:39 +0000
with message-id <[email protected]>
and subject line Fixed in 1.0.0
has caused the Debian Bug report #1127667,
regarding dulwich: autopkgtests fail: UNEXPECTED SUCCESS:
test_verify_invalid_signature
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 [email protected]
immediately.)
--
1127667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127667
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: dulwich
Version: 0.24.10-1
Severity: serious
https://ci.debian.net/packages/d/dulwich/testing/amd64/68554341/ shows:
UNEXPECTED SUCCESS: test_verify_invalid_signature
(tests.test_signature.GPGSignatureVendorTests.test_verify_invalid_signature)
Test that verify raises an error for invalid signatures.
Looking at
https://salsa.debian.org/python-team/packages/dulwich/-/blob/debian/main/debian/patches/03_fix_gpg_signature_verification_test,
the second paragraph of the description ("This patch also ensures that
all GPGMEError exceptions (not just BadSignatures) are properly caught
and wrapped in BadSignature exceptions") doesn't seem to match the
actual patch. Jelmer, is it possible you forgot to add part of the
patch?
Thanks,
--
Colin Watson (he/him) [[email protected]]
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64
Kernel: Linux 6.18.5+deb14-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 1.0.0-1
This was fixed in 1.0.0
--- End Message ---
