Your message dated Mon, 06 Jul 2026 07:34:06 +0000
with message-id <[email protected]>
and subject line Bug#1141464: fixed in umockdev 0.19.8-1
has caused the Debian Bug report #1141464,
regarding umockdev FTBFS on Alpha; incorrect versioning of libc in dlopen
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.)


-- 
1141464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141464
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: umockdev
Version: 0.19.7-1
Tags: ftbfs patch
User: [email protected]
Usertags: alpha
Severity: important

umockdev FTBFS on Alpha with the test suite hanging [1]:

Summary of Failures:

1/7 umockdev:umockdev                         TIMEOUT        150.85s   killed 
by signal 9 SIGKILL
4/7 umockdev:umockdev-run                     TIMEOUT        150.73s   killed 
by signal 9 SIGKILL
2/7 fails-valgrind - umockdev:umockdev-vala   TIMEOUT        150.93s   killed 
by signal 9 SIGKILL
3/7 umockdev:ioctl-tree                       TIMEOUT        150.90s   killed 
by signal 9 SIGKILL
6/7 umockdev:static-code                      TIMEOUT        150.75s   killed 
by signal 9 SIGKILL
5/7 fails-valgrind - umockdev:umockdev-record TIMEOUT        150.81s   killed 
by signal 9 SIGKILL
7/7 fails-valgrind - umockdev:umockdev.py     TIMEOUT        150.70s   killed 
by signal 9 SIGKILL

The reason for the hang is that the libumockdev-preload library
attempts to open libc as "libc.so.6" whereas on Alpha it is
"libc.so.6.1" so the dlopen() call fails of which libumockdev
does not even bother to check has succeeded before proceeding.

I attach a patch that detects if libumockdev-preload is being
compiled on Alpha and then uses the correct libc name. With that
umockdev builds to completion on Alpha.

Cheers,
Michael

[1] 
https://buildd.debian.org/status/fetch.php?pkg=umockdev&arch=alpha&ver=0.19.7-1&stamp=1774524459&raw=0
--- a/src/libumockdev-preload.c
+++ b/src/libumockdev-preload.c
@@ -119,8 +119,13 @@
     void *fp;
     static void *nextlib;
 
-    if (nextlib == NULL)
+    if (nextlib == NULL) {
+#ifdef __alpha
+       nextlib = dlopen("libc.so.6.1", RTLD_LAZY);
+#else
        nextlib = dlopen("libc.so.6", RTLD_LAZY);
+#endif
+    }
 
     fp = dlsym(nextlib, f);
 

--- End Message ---
--- Begin Message ---
Source: umockdev
Source-Version: 0.19.8-1
Done: Martin Pitt <[email protected]>

We believe that the bug you reported is fixed in the latest version of
umockdev, 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.
Martin Pitt <[email protected]> (supplier of updated umockdev 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: Mon, 06 Jul 2026 09:18:31 +0200
Source: umockdev
Architecture: source
Version: 0.19.8-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Pitt <[email protected]>
Changed-By: Martin Pitt <[email protected]>
Closes: 1141464
Changes:
 umockdev (0.19.8-1) unstable; urgency=medium
 .
   * New upstream bug fix release:
     - preload: Fix libc name on alpha architecture (Thanks Michael Cree!)
       (Closes: #1141464)
     - preload: Check dlopen(libc) failure
     - ioctl: Fix array.resize(0) to work with gcc 16 static analyzer
   * Bump Standards-Version to 4.7.4.  No changes necessary.
Checksums-Sha1:
 e6dd130bcc7907e2eb117f1e1aec8f7180f6c77a 2495 umockdev_0.19.8-1.dsc
 e99f6e688845ab3d718691ee5c2024927847f171 499460 umockdev_0.19.8.orig.tar.xz
 08d0a9a2d93c49d7aacc0f3d30d199468de584b6 10332 umockdev_0.19.8-1.debian.tar.xz
 6d9f910ec064d01f58729030d5e8ead29428de77 8821 
umockdev_0.19.8-1_source.buildinfo
Checksums-Sha256:
 00692f2ff27f149176b48e4d6d9b2cca5edace754dede29adbeddff2efd9430e 2495 
umockdev_0.19.8-1.dsc
 9d57c917a32dc696877ab525eb510971a8109899d5b92d986e7bac32573125b0 499460 
umockdev_0.19.8.orig.tar.xz
 81ebb35df8621cd2ee228d89be638f2afa912902ca3897107ce708e048a00831 10332 
umockdev_0.19.8-1.debian.tar.xz
 afa5bd831f1f04f68f1cb2a57f00d433eecbfd98cb7fb95501e97f8230501fb4 8821 
umockdev_0.19.8-1_source.buildinfo
Files:
 4ee51ad239b804194a5657d58fa2ecee 2495 devel optional umockdev_0.19.8-1.dsc
 7f94b1bc1bcb16165ebe4773a40642d6 499460 devel optional 
umockdev_0.19.8.orig.tar.xz
 eddad279b5db7345ecf75f16b0eb3752 10332 devel optional 
umockdev_0.19.8-1.debian.tar.xz
 3c43203e85c4eb3c6a1071a808bb539f 8821 devel optional 
umockdev_0.19.8-1_source.buildinfo

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

iQIzBAEBCgAdFiEEbEuHi35jHxYFV8PN7nvd5LhrVxMFAmpLV2cACgkQ7nvd5Lhr
VxMRZg/8DpC6P30e1rXcXRNyURFBMSnLUK++fnh7yiwgw+oPaNAoSF12aw5lpl4E
u/1y3yG7jzp9iuERQR89R0wNUxpTK1P7PAUIuJhBZpcoE1sIIqpZuPjMP3sY14MP
UOrlnKiXStJhcuTuRmDqxGXvkdi8SBvUxtn3VBITf/E48Zqaln7tOEtypzB+6PAo
tcxxFzoghidlcMmQsNhlYpQY99xNxFG37Zz70Ix+PnQW4/QoQ+Rmh3SJ5Es81aIb
J1TTBv1RdW0rOJbt9WTKcnacSrkqxpAEIiYGCj7M8xaF7MleSdde1tm7j0g3us71
RA51KnzBfExJ8Kh6MDadSpyPFw7QumDHFyF3OAqGiSdnafSSEQ5/7IA0OmHt+4Dd
+pcxoWcAdrs6ZWz9P/EZACPTsB4k4ICYVM/NnHQ59GMlh+2htj+57WUyEfthEHTR
71jj87Gu4dwueeHwDztGmolNGjiZrbivuQMLFCFjvpp96hkpqEuzLxiG7OjFQdRj
AlqrXM/F+Fn6Ic8+tARi23cru2Hkw4/7TeMwCrtBaq7p42j6xxK6VIjEj4/AUCP7
WhBSJwweUzpeqv3kKI5lqwB87F2F3MQYx4pbMgAaqA9NHSKCuSCvk/QmYq2D9Z08
drJcbDPRYBuSlEbJg+X88m71lwM3EaXFj6WLSVDS3v/SbOl5fG4=
=R1ds
-----END PGP SIGNATURE-----

Attachment: pgpLTfyMg7fhq.pgp
Description: PGP signature


--- End Message ---

Reply via email to