Your message dated Wed, 07 May 2025 16:19:13 +0000
with message-id <[email protected]>
and subject line Bug#1103787: fixed in gpgme1.0 1.24.2-3
has caused the Debian Bug report #1103787,
regarding gpgme1.0: Testsuite error on 32bit archs with 64bit time (FAIL with 
gnupg 2.4, SKIP with 2.2)
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.)


-- 
1103787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103787
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gpgme1.0
Version: 1.24.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: [email protected], [email protected]
User: [email protected]
Usertags: armel armhf

Hello,

upgrading gpg from 2.2 to 2.4 changed the outcome of
t-addexistingsubkey5 (and ..6) from
********* Start testing of AddExistingSubkeyJobTest *********
Config: Using QtTest library 5.15.15, Qt 5.15.15 
(arm-little_endian-ilp32-eabi-hardfloat shared (dynamic) release build; by GCC 
14.2.0), debian unknown
PASS   : AddExistingSubkeyJobTest::initTestCase()
SKIP   : AddExistingSubkeyJobTest::testAddExistingSubkeyAsync() gpg does not 
yet support adding an existing subkey to another key via the command API
   Loc: [../../../../lang/qt/tests/t-addexistingsubkey.cpp(137)]
SKIP   : AddExistingSubkeyJobTest::testAddExistingSubkeySync() gpg does not yet 
support adding an existing subkey to another key via the command API
   Loc: [../../../../lang/qt/tests/t-addexistingsubkey.cpp(137)]
SKIP   : AddExistingSubkeyJobTest::testAddExistingSubkeyWithExpiration() gpg 
does not yet support adding an existing subkey to another key via the command 
API
   Loc: [../../../../lang/qt/tests/t-addexistingsubkey.cpp(137)]
PASS   : AddExistingSubkeyJobTest::cleanupTestCase()
Totals: 2 passed, 0 failed, 3 skipped, 0 blacklisted, 164ms
********* Finished testing of AddExistingSubkeyJobTest *********

to 

********* Start testing of AddExistingSubkeyJobTest *********
Config: Using QtTest library 5.15.15, Qt 5.15.15 
(arm-little_endian-ilp32-eabi-hardfloat shared (dynamic) release build; by GCC 
14.2.0), debian unknown
PASS   : AddExistingSubkeyJobTest::initTestCase()
PASS   : AddExistingSubkeyJobTest::testAddExistingSubkeyAsync()
PASS   : AddExistingSubkeyJobTest::testAddExistingSubkeySync()
FAIL!  : AddExistingSubkeyJobTest::testAddExistingSubkeyWithExpiration() 
Compared values are not the same
   Actual   (result.code())                     : 0
   Expected (static_cast<int>(GPG_ERR_INV_TIME)): 161
   Loc: [../../../../lang/qt/tests/t-addexistingsubkey.cpp(238)]
PASS   : AddExistingSubkeyJobTest::cleanupTestCase()
Totals: 4 passed, 1 failed, 0 skipped, 0 blacklisted, 3564ms
********* Finished testing of AddExistingSubkeyJobTest *********

This shows up on all 32 bit archs with 64bit time that had the build-deps
(armhf, armel and as non-relase arch powerpc).

It is not Debian specific, it also shows up against vanilla gnupg 2.4.7 or
2.5.5.

cu Andreas

--- End Message ---
--- Begin Message ---
Source: gpgme1.0
Source-Version: 1.24.2-3
Done: Andreas Metzler <[email protected]>

We believe that the bug you reported is fixed in the latest version of
gpgme1.0, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Metzler <[email protected]> (supplier of updated gpgme1.0 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 07 May 2025 17:49:48 +0200
Source: gpgme1.0
Architecture: source
Version: 1.24.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers <[email protected]>
Changed-By: Andreas Metzler <[email protected]>
Closes: 1103787
Changes:
 gpgme1.0 (1.24.2-3) unstable; urgency=medium
 .
   * Fix hanging state machine.
     https://dev.gnupg.org/T7600 Fix picked from gpgme-1.24-branch
   * Fix 64bit time_t overflow bug on 32 bit archs (Closes: #1103787) (Also
     from upstream gpgme-1.24-branch)
Checksums-Sha1: 
 837e2ac78308ba18c1ff41335e838761bc3eb099 3255 gpgme1.0_1.24.2-3.dsc
 a41da81981db277ccc0a9b21960517feb9edc019 27984 gpgme1.0_1.24.2-3.debian.tar.xz
Checksums-Sha256: 
 822672941458bfd0953527b53899fd88e38f84b16220bbade2bab598f8435d46 3255 
gpgme1.0_1.24.2-3.dsc
 c4afd253b39b51cf8af26d6a87e18017ef79a27d4c02048f66b572c6dcb2fe11 27984 
gpgme1.0_1.24.2-3.debian.tar.xz
Files: 
 badd9391ea980bff0132377d4087ad25 3255 libs optional gpgme1.0_1.24.2-3.dsc
 3fe4cfdba93ee8f1f5193b2809f55d22 27984 libs optional 
gpgme1.0_1.24.2-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmgbg5MACgkQpU8BhUOC
FIT/gg/9FLdRU0CaOm+y0zxY4LuEQGQVbmdvvV+yPXJ47G1gdBltpW4AlR9cb6aq
GT6d8BI4Km4qzo3ToXKffB8tSmREAcocvUH22LKv2+ylXN1vaYD/1BVMjUn2z95J
agdmI7GBvmKtjQWsXYoCqMJW8Y/y1F1aLnMeFV28+7VOLD+eIVHRYJAqRrZc02p4
KcPvomzX1R56t1mkMyp2L37aSg8T9QeAl1IzOK+lMxmpbaN3lFHe6Nyg6iQt0XtE
ZaEZQ49Zv0JgR86lDHfl8WTntpz7QlExd4wQOinibs0P7HiIY9zriPI2N9JWGikf
zLeFrIYpoz5VjjU9LEWQEJKDJhWynzbiEelNt56kBvPToFiAKnH7ZOGKqRkcATtp
NIloUUjSLmBBaXwPmpwNwM08Yti2YpKsfT9Zhov1k8SQGcU5tGuTjYct2Dm/FBU4
jG8NczudZhTSQDR/DgilbtnYKxqXyBJ/6cIJ5SiUBpFK9NGpGp1t1FXNHhszmiW3
SBmdy4rxa7cRjyBScN99tp0q8k3EyrEIiYmdQrHM1epTIMJZJpdx7gmbdUrJBAlN
ffa6rJbCZfi02OwfzTVObbHWr996CRpOYdMy/kJweOGQ+JWqUHpXzEU9w2w51EQ2
zw7GxFIFUi5onipX7fvZf9P/z0cCPdN+QpqhwdqYcZW3k2r6XJ4=
=lZ6D
-----END PGP SIGNATURE-----

Attachment: pgpSSLAJMHx7K.pgp
Description: PGP signature


--- End Message ---

Reply via email to