Source: aptly Version: 1.6.1+ds1-1 Severity: normal X-Debbugs-Cc: gnu...@packages.debian.org
Hello, aptly throws a strange CI error against gnupg 2.4.7: t06_publish ➔ PublishSnapshot38Test ... FAIL 17s running command: aptly -architectures=s390x mirror create -keyring=aptlytest.gpg -filter='installer' -with-installer stretch http://repo.aptly.info/system-tests/archive.debian.org/debian-archive/debian/ stretch main fixture Output: [...] Snapshot stretch successfully created. You can run 'aptly publish snapshot stretch' to publish snapshot as Debian repository. running command: aptly publish snapshot -keyring=/tmp/tmp.hop2hu7ReX/src/github.com/aptly-dev/aptly/system/files/aptly.pub -secret-keyring=/tmp/tmp.hop2hu7ReX/src/github.com/aptly-dev/aptly/system/files/aptly.sec stretch Verifying gold file: /tmp/tmp.hop2hu7ReX/src/github.com/aptly-dev/aptly/system/t06_publish/PublishSnapshot38Test_gold Traceback (most recent call last): File "/tmp/tmp.hop2hu7ReX/src/github.com/aptly-dev/aptly/system/run.py", line 129, in run t.test() ~~~~~~^^ File "/tmp/tmp.hop2hu7ReX/src/github.com/aptly-dev/aptly/system/lib.py", line 168, in test raise exc File "/tmp/tmp.hop2hu7ReX/src/github.com/aptly-dev/aptly/system/lib.py", line 164, in test self.check() ~~~~~~~~~~^^ File "/tmp/tmp.hop2hu7ReX/src/github.com/aptly-dev/aptly/system/t06_publish/snapshot.py", line 1167, in check super(PublishSnapshot38Test, self).check() ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/tmp/tmp.hop2hu7ReX/src/github.com/aptly-dev/aptly/system/lib.py", line 381, in check_output self.verify_match(self.get_gold(), self.output, ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ match_prepare=self.outputMatchPrepare) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/tmp.hop2hu7ReX/src/github.com/aptly-dev/aptly/system/lib.py", line 513, in verify_match raise Exception("content doesn't match:\n" + diff + "\n") Exception: content doesn't match: --- +++ @@ -1,7 +1,7 @@ +Signing file 'main_installer-s390x_current_images_SHA256SUMS' with gpg, please enter your passphrase when prompted: Loading packages... Generating metadata files and linking package files... Finalizing metadata files... -Signing file 'main_installer-s390x_current_images_SHA256SUMS' with gpg, please enter your passphrase when prompted: Signing file 'Release' with gpg, please enter your passphrase when prompted: Clearsigning file 'Release' with gpg, please enter your passphrase when prompted: --------------------------------------- Afaict the message "Signing file 'main_installer-s390x_current_images_SHA256SUMS' with gpg [...]" shows up a little bit earlier and the testsuite is unhappy with that. Is this really an issue on the gpg side? TIA, cu Andreas -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.12.17-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
