Bug#1066887: ENhance Patch for local-gen
On 2024-04-09 23:49, Aurelien Jarno wrote:
Hi,
On 2024-03-15 16:13, M. Buecher wrote:
Adding / back to end of the path, so that a locale file is immediately
found.
diff --git a/debian/local/usr_sbin/locale-gen b/debian/local/usr_sbin/locale-gen
index 7fa3d772..1711a4f0 100755
--- a/debian/local/usr_sbin/locale-gen
+++ b/debian/local/usr_sbin/locale-gen
@@ -23,6 +23,12 @@ is_entry_ok() {
fi
}
+if [ -z "${I18NPATH:-}" ]; then
+ if [ -d "${USER_LOCALES}" ]; then
+I18NPATH="${USER_LOCALES%%/locales*}/"
+ fi
+fi
+
echo "Generating locales (this might take a while)..."
while read -r locale charset; do
if [ -z "$locale" ] || [ "${locale#\#}" != "$locale" ]; then continue;
fi
@@ -46,7 +52,7 @@ while read -r locale charset; do
input="$USER_LOCALES/$input"
fi
fi
- localedef -i "$input" -c -f "$charset" -A /usr/share/locale/locale.alias
"$locale" || :
+ I18NPATH="${I18NPATH}" localedef -i "$input" -c -f "$charset" -A
/usr/share/locale/locale.alias "$locale" || :
echo " done"
done < "$LOCALEGEN"
echo "Generation complete."
Thanks for your bug report and for even proposing a patch which looks
good to me.
That said as I18NPATH could actually contains a list of directory, I
wonder if the behaviour would be more consistent if the user locales
directory is always prepended to I18NPATH if it exists. What do you
think?
Regards
Aurelien
My thought was: if someone already specified I18NPATH explicitly, then
he knows what he is doing and the script should not mess with his setup.
Maddes
Bug#1068251: marked as done (glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t)
Your message dated Tue, 09 Apr 2024 22:35:39 + with message-id and subject line Bug#1068251: fixed in glibc 2.37-16 has caused the Debian Bug report #1068251, regarding glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t 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 ow...@bugs.debian.org immediately.) -- 1068251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glibc Version: 2.37-15.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-...@lists.debian.org Starting with gcc-12 version 12.3.0-15, -D_TIME_BITS=64 together with -D_FILE_OFFSET_BITS=64 are passed by default on 32-bit architectures except i386. This has been partially fixed in the 2.37-15.1 NMU by adding -U_TIME_BITS to CFLAGS, however it causes failures in the testsuite: | +-+ | | Encountered regressions that don't match expected failures. | | +-+ | FAIL: conform/ISO/stdio.h/linknamespace | FAIL: conform/ISO11/stdio.h/linknamespace | FAIL: conform/ISO99/stdio.h/linknamespace | FAIL: conform/POSIX/aio.h/linknamespace | FAIL: conform/POSIX/dirent.h/linknamespace | FAIL: conform/POSIX/fcntl.h/conform | FAIL: conform/POSIX/fcntl.h/linknamespace | FAIL: conform/POSIX/glob.h/conform | FAIL: conform/POSIX/mqueue.h/conform | FAIL: conform/POSIX/mqueue.h/linknamespace | FAIL: conform/POSIX/stdio.h/linknamespace | FAIL: conform/POSIX/sys/mman.h/linknamespace | FAIL: conform/POSIX/sys/stat.h/conform | FAIL: conform/POSIX/unistd.h/conform | FAIL: conform/POSIX/unistd.h/linknamespace | FAIL: conform/POSIX/utime.h/conform | FAIL: conform/POSIX2008/aio.h/linknamespace | FAIL: conform/POSIX2008/dirent.h/linknamespace | FAIL: conform/POSIX2008/fcntl.h/conform | FAIL: conform/POSIX2008/fcntl.h/linknamespace | FAIL: conform/POSIX2008/glob.h/conform | FAIL: conform/POSIX2008/mqueue.h/conform | FAIL: conform/POSIX2008/mqueue.h/linknamespace | FAIL: conform/POSIX2008/signal.h/conform | FAIL: conform/POSIX2008/stdio.h/linknamespace | FAIL: conform/POSIX2008/stdlib.h/linknamespace | FAIL: conform/POSIX2008/sys/mman.h/linknamespace | FAIL: conform/POSIX2008/sys/select.h/conform | FAIL: conform/POSIX2008/sys/stat.h/conform | FAIL: conform/POSIX2008/sys/statvfs.h/linknamespace | FAIL: conform/POSIX2008/unistd.h/linknamespace | FAIL: conform/UNIX98/aio.h/linknamespace | FAIL: conform/UNIX98/dirent.h/linknamespace | FAIL: conform/UNIX98/fcntl.h/conform | FAIL: conform/UNIX98/fcntl.h/linknamespace | FAIL: conform/UNIX98/glob.h/conform | FAIL: conform/UNIX98/mqueue.h/conform | FAIL: conform/UNIX98/mqueue.h/linknamespace | FAIL: conform/UNIX98/stdio.h/linknamespace | FAIL: conform/UNIX98/stdlib.h/linknamespace | FAIL: conform/UNIX98/sys/mman.h/linknamespace | FAIL: conform/UNIX98/sys/resource.h/linknamespace | FAIL: conform/UNIX98/sys/statvfs.h/linknamespace | FAIL: conform/UNIX98/sys/time.h/conform | FAIL: conform/UNIX98/unistd.h/linknamespace | FAIL: conform/UNIX98/utmpx.h/conform | FAIL: conform/XOPEN2K/aio.h/linknamespace | FAIL: conform/XOPEN2K/dirent.h/linknamespace | FAIL: conform/XOPEN2K/fcntl.h/conform | FAIL: conform/XOPEN2K/fcntl.h/linknamespace | FAIL: conform/XOPEN2K/glob.h/conform | FAIL: conform/XOPEN2K/mqueue.h/conform | FAIL: conform/XOPEN2K/mqueue.h/linknamespace | FAIL: conform/XOPEN2K/stdio.h/linknamespace | FAIL: conform/XOPEN2K/stdlib.h/linknamespace | FAIL: conform/XOPEN2K/sys/mman.h/linknamespace | FAIL: conform/XOPEN2K/sys/resource.h/linknamespace | FAIL: conform/XOPEN2K/sys/select.h/conform | FAIL: conform/XOPEN2K/sys/statvfs.h/linknamespace | FAIL: conform/XOPEN2K/sys/time.h/conform | FAIL: conform/XOPEN2K/unistd.h/linknamespace | FAIL: conform/XOPEN2K/utmpx.h/conform | FAIL: conform/XOPEN2K8/aio.h/linknamespace | FAIL: conform/XOPEN2K8/dirent.h/linknamespace | FAIL: conform/XOPEN2K8/fcntl.h/conform | FAIL: conform/XOPEN2K8/fcntl.h/linknamespace | FAIL: conform/XOPEN2K8/ftw.h/conform | FAIL: conform/XOPEN2K8/glob.h/conform | FAIL: conform/XOPEN2K8/mqueue.h/conform | FAIL: conform/XOPEN2K8/mqueue.h/linknamespace | FAIL: conform/XOPEN2K8/signal.h/conform | FAIL: conform/XOPEN2K8/stdio.h/linknamespace | FAIL: conform/XOPEN2K8/stdlib.h/linknamespace | FAIL: conform/XOPEN2K8/sys/mman.h/linknamespace | FAIL: conform/XOPEN2K8/sys/resource.h/linknamespace | FAIL: conform/XOPEN2K8/sys/select.h/conform | FAIL: conform/XOPEN2K8/sys/stat.h/conform | FAIL:
Bug#1068188: marked as done (pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1)
Your message dated Tue, 09 Apr 2024 22:35:39 + with message-id and subject line Bug#1068188: fixed in glibc 2.37-16 has caused the Debian Bug report #1068188, regarding pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1 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 ow...@bugs.debian.org immediately.) -- 1068188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: glibc-doc Version: 2.38-6 Severity: serious Justification: Policy 7.4 X-Debbugs-Cc: a...@kernel.org, mar...@debian.org Dear Maintainer, The Linux man-pages project has recently added the pthread_*(3) manual pages that were provided by glibc-doc. The first upstream version of the Linux man-pages that includes these pages is man-pages-6.06. Here's what was added: $ git diff --stat b06cd070f..128a3ae35 man3/pthread_cond_init.3| 264 man3/pthread_condattr_init.3| 48 man3/pthread_key_create.3 | 178 + man3/pthread_mutex_init.3 | 241 ++ man3/pthread_mutexattr_setkind_np.3 | 52 man3/pthread_once.3 | 44 6 files changed, 827 insertions(+) Debian's manpages-dev_6.7-1_all.deb has been the first package since that happened, and I've noticed that dpkg(1) (via apt-get(8)) refuses to upgrade manpages-dev due to a conflict with glibc-doc. $ sudo apt-get upgrade -V; [...] Do you want to continue? [Y/n] y Reading changelogs... Done (Reading database ... 404853 files and directories currently installed.) Preparing to unpack .../manpages-dev_6.7-1_all.deb ... Unpacking manpages-dev (6.7-1) over (6.05.01-1) ... dpkg: error processing archive /var/cache/apt/archives/manpages-dev_6.7-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/pthread_cond_init.3.gz', which is also in package glibc-doc 2.38-6 Errors were encountered while processing: /var/cache/apt/archives/manpages-dev_6.7-1_all.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Please, remove from glibc-doc those manual pages that conflict with manpages-dev. Marcos, you'll also need to specify a breaks with glibc-doc versions up to (and including) 6.38-6 in the next revision of manpages-dev, and drop 6.7-1. Have a lovely day! Alex -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.0-rc7-alx-dirty (SMP w/24 CPU threads; PREEMPT) Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled glibc-doc depends on no packages. glibc-doc recommends no packages. Versions of packages glibc-doc suggests: ii glibc-doc-reference 2.38-1 -- no debconf information --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.37-16 Done: Aurelien Jarno We believe that the bug you reported is fixed in the latest version of glibc, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno (supplier of updated glibc 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Apr 2024 00:15:44 +0200 Source: glibc Architecture: source Version: 2.37-16 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1063624 1063937 1067909 1068188 1068251 Changes: glibc (2.37-16) unstable; urgency=medium . [ Samuel Thibault ] * debian/patches/hurd-i386/submitted-AF_ROUTE.diff: Also comment out PF_ROUTE/AF_ROUTE. * debian/patches/hurd-i386/git-proc_getchildren_rusage.diff: Implement RUSAGE_CHILDREN, should fix the grep testsuite. . [ Aurelien Jarno ] * debian/rules.d/build.mk: present glibc with a compiler that does not
Bug#1067909: marked as done (libc-devtools: please relax Depends on libgd3)
Your message dated Tue, 09 Apr 2024 22:35:39 +
with message-id
and subject line Bug#1067909: fixed in glibc 2.37-16
has caused the Debian Bug report #1067909,
regarding libc-devtools: please relax Depends on libgd3
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 ow...@bugs.debian.org
immediately.)
--
1067909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc-devtools
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
libgd3 pulls an excessive amount of dependencies, including fonts. It would
thus be desirable to downgrade it to a mere Recommends.
Martin-Éric
- -- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (900, 'unstable')
Architecture: i386 (x86_64)
Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
Versions of packages libc-devtools depends on:
ii libc6 2.37-15.1
pn libgd3
Versions of packages libc-devtools recommends:
ii manpages 6.05.01-1
ii manpages-dev 6.05.01-1
libc-devtools suggests no packages.
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmYFuH0ACgkQrh+Cd8S0
17ayNw/+KowbskIoaRqYApa3kOPNWPtLD/rvbEOISdjvJKBz9chs7cYImdtQdd7h
9Z+R6U9AGnxrOTUXxO2a1lfGtpgxVFMemiHIN361zV3kA7IdqX62e1kvAT2dympy
Gselwg1Jr5PULghzDAdBcYlZ82S7roYnbh7lhd0vcS90xjCatL4Hk7+/bwCgISvB
2wgICAeXV5YrYxx4pX8FfeLUfGbsCRxzW0sKnG61a+RxGRykP5p+hiccSG2IACyL
Wks1Jymf5jLO3Qk3hzYykN3iCikx/dM6wMscDXp36olD+kliD+0I6YDAFHXFIcrb
FeL97pqFvNhoz8Q81IbML2BfZfMAEoAlSp5ROqqxyGuqo9BYzc9tDUkwaacPEJCY
9R2sAB1SHgwObOITueTRynfm1kIbemwi/ydiOBT7jjnYNTV3I52DdAdRaqqhSeUM
hbCxk960xqF/v2IcMjc92wNepwI8dj4FGmQPgGwJ3JYuVa4y5IncFhf3N93KK00V
bduJya6sT/2vR0PtsLnXnAQzh71SyEnqPGGvgQ8031JJ5zivqHZuLx0Huf/ZcjWY
CMBmTI2WRByOwqGgA3kpSh5fc7gozb2to/XHTuS7vWFS03KNwZTe+oacHJaVEYTW
rL04tKeCZD5t4e4rvrjKABFgheH/Q+TQPS0VfA2NrSYk76qfIeY=
=mkEr
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.37-16
Done: Aurelien Jarno
We believe that the bug you reported is fixed in the latest version of
glibc, 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 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aurelien Jarno (supplier of updated glibc 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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 10 Apr 2024 00:15:44 +0200
Source: glibc
Architecture: source
Version: 2.37-16
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers
Changed-By: Aurelien Jarno
Closes: 1063624 1063937 1067909 1068188 1068251
Changes:
glibc (2.37-16) unstable; urgency=medium
.
[ Samuel Thibault ]
* debian/patches/hurd-i386/submitted-AF_ROUTE.diff: Also comment out
PF_ROUTE/AF_ROUTE.
* debian/patches/hurd-i386/git-proc_getchildren_rusage.diff: Implement
RUSAGE_CHILDREN, should fix the grep testsuite.
.
[ Aurelien Jarno ]
* debian/rules.d/build.mk: present glibc with a compiler that does not
default to -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64, as upstream doesn't
support this configuration. This has the consequence of hiding real issues
found by the testsuite, but there is a consensus that this is the way to
go for now. Thanks to Helmut Grohne for the hint and starting the
discussion. Closes: #1068251.
* debian/debhelper.in/glibc-doc.{links,manpages},
debian/local/manpages/pthread_*: drop the man pages for libpthread
functions, as they are now included in manpages-dev. Closes: #1068188.
* debian/control.in/main: update glibc-doc description following the removal
of the pthread manpages.
* debian/control.in/main: downgrade the Recommends from libc-dev-bin to
libc-devtools to a Suggests. Closes: #1067909.
* debian/patches/git-updates.diff: update from upstream stable branch.
* debian/patches/sparc/submitted-sparc-clone.diff: pull patch from the
upstream BTS to workaround issues with the clone syscall on sparc.
Closes: #1063937.
.
[ Johannes
Bug#1063937: marked as done (glibc: Please add workaround to fix posix_spawn() on sparc64)
Your message dated Tue, 09 Apr 2024 22:35:39 +
with message-id
and subject line Bug#1063937: fixed in glibc 2.37-16
has caused the Debian Bug report #1063937,
regarding glibc: Please add workaround to fix posix_spawn() on sparc64
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 ow...@bugs.debian.org
immediately.)
--
1063937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.37-15
Severity: important
Tags: patch
User: debian-sp...@lists.debian.org
Usertags: sparc64
X-Debbugs-Cc:
debian-sp...@lists.debian.org,ker...@mkarcher.dialup.fu-berlin.de,s...@gentoo.org
Hello,
there is currently a nasty bug on sparc64 that breaks posix_spawn() [1]
and potentially any package that uses gcc since libiberty switched to
using posix_spawn() with gcc-14.
The attached patch comes from Michael Karcher (CC'ed) and unbreaks
posix_spawn() so that gcc works again without posix_spawn() failing
with "Bad Address".
Since this patch is just a workaround and we're not even sure whether
the bug is in the kernel or glibc, it's not been pushed upstream yet.
Adrian
> [1]
> https://lore.kernel.org/sparclinux/fe5cc47167430007560501aabb28ba154985b661.ca...@physik.fu-berlin.de
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--- glibc-2.37.orig/sysdeps/unix/sysv/linux/sparc/sparc32/clone.S
+++ glibc-2.37/sysdeps/unix/sysv/linux/sparc/sparc32/clone.S
@@ -28,6 +28,9 @@
.text
ENTRY (__clone)
save%sp,-96,%sp
+ save%sp,-96,%sp
+ flushw
+ restore
cfi_def_cfa_register(%fp)
cfi_window_save
cfi_register(%o7, %i7)
--- glibc-2.37.orig/sysdeps/unix/sysv/linux/sparc/sparc64/clone.S
+++ glibc-2.37/sysdeps/unix/sysv/linux/sparc/sparc64/clone.S
@@ -32,6 +32,9 @@
ENTRY (__clone)
save%sp, -192, %sp
+ save%sp, -192, %sp
+ flushw
+ restore
cfi_def_cfa_register(%fp)
cfi_window_save
cfi_register(%o7, %i7)
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.37-16
Done: Aurelien Jarno
We believe that the bug you reported is fixed in the latest version of
glibc, 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 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aurelien Jarno (supplier of updated glibc 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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 10 Apr 2024 00:15:44 +0200
Source: glibc
Architecture: source
Version: 2.37-16
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers
Changed-By: Aurelien Jarno
Closes: 1063624 1063937 1067909 1068188 1068251
Changes:
glibc (2.37-16) unstable; urgency=medium
.
[ Samuel Thibault ]
* debian/patches/hurd-i386/submitted-AF_ROUTE.diff: Also comment out
PF_ROUTE/AF_ROUTE.
* debian/patches/hurd-i386/git-proc_getchildren_rusage.diff: Implement
RUSAGE_CHILDREN, should fix the grep testsuite.
.
[ Aurelien Jarno ]
* debian/rules.d/build.mk: present glibc with a compiler that does not
default to -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64, as upstream doesn't
support this configuration. This has the consequence of hiding real issues
found by the testsuite, but there is a consensus that this is the way to
go for now. Thanks to Helmut Grohne for the hint and starting the
discussion. Closes: #1068251.
* debian/debhelper.in/glibc-doc.{links,manpages},
debian/local/manpages/pthread_*: drop the man pages for libpthread
functions, as they are now included in manpages-dev. Closes: #1068188.
* debian/control.in/main: update glibc-doc description following the removal
of the pthread manpages.
* debian/control.in/main: downgrade the Recommends from libc-dev-bin to
libc-devtools to a Suggests. Closes: #1067909.
* debian/patches/git-updates.diff: update from upstream stable branch.
* debian/patches/sparc/submitted-sparc-clone.diff: pull patch from the
upstream BTS to workaround issues with the clone syscall on sparc.
Bug#1063624: marked as done (libc.preinst: please skip kernel check via uname when DPKG_ROOT is not empty for gnu hurd support)
Your message dated Tue, 09 Apr 2024 22:35:39 +
with message-id
and subject line Bug#1063624: fixed in glibc 2.37-16
has caused the Debian Bug report #1063624,
regarding libc.preinst: please skip kernel check via uname when DPKG_ROOT is
not empty for gnu hurd support
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 ow...@bugs.debian.org
immediately.)
--
1063624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.37-15
Severity: normal
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
X-Debbugs-Cc: debian-h...@lists.debian.org, debian-cr...@lists.debian.org
Hi,
one of the reasons for DPKG_ROOT support in packages close to the essential and
build-essential set is to build chroots for architectures that do not have
qemu-user support. Building chroots for hurd from linux is one such scenario
where qemu-user emulation will never allow running hurd binaries from the
chroot on the linux system creating that chroot and thus the only way to create
it (short of running the whole thing inside a full virtual machine) is to use
chrootless mode.
In our last round of DPKG_ROOT related patches we built chroots for other linux
architectures on linux. Now we try building chroots for foreign kernels. In
this case: hurd on linux. In the process we discovered another problem class:
maintainer scripts running uname. This is a problem because "uname -s" will
print "Linux" and thus the linux-specific parts of the maintainer script get
executed but we want to build a hurd chroot and need the hurd-specific bits
instead.
In case of libc.preinst, its use of "uname -s" and "uname -r" can be avoided by
adding another condition on $DPKG_ROOT being empty, i.e to only check the
kernel version for normal installations but not when glibc is installed with
dpkg --force-script-chrootless as in that case, there exists no way for the
script to know what kernel version will be running on the final system where
the chroot will be deployed. So if "$DPKG_ROOT" is not empty, the kernel
version checks just get skipped.
I submitted a patch as a merge request here:
https://salsa.debian.org/glibc-team/glibc/-/merge_requests/20
Please consider applying it to close this bug.
What do you think?
Thanks!
cheers, josch
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.37-16
Done: Aurelien Jarno
We believe that the bug you reported is fixed in the latest version of
glibc, 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 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aurelien Jarno (supplier of updated glibc 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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 10 Apr 2024 00:15:44 +0200
Source: glibc
Architecture: source
Version: 2.37-16
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers
Changed-By: Aurelien Jarno
Closes: 1063624 1063937 1067909 1068188 1068251
Changes:
glibc (2.37-16) unstable; urgency=medium
.
[ Samuel Thibault ]
* debian/patches/hurd-i386/submitted-AF_ROUTE.diff: Also comment out
PF_ROUTE/AF_ROUTE.
* debian/patches/hurd-i386/git-proc_getchildren_rusage.diff: Implement
RUSAGE_CHILDREN, should fix the grep testsuite.
.
[ Aurelien Jarno ]
* debian/rules.d/build.mk: present glibc with a compiler that does not
default to -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64, as upstream doesn't
support this configuration. This has the consequence of hiding real issues
found by the testsuite, but there is a consensus that this is the way to
go for now. Thanks to Helmut Grohne for the hint and starting the
discussion. Closes: #1068251.
* debian/debhelper.in/glibc-doc.{links,manpages},
debian/local/manpages/pthread_*: drop the man pages for libpthread
functions, as they are now included in manpages-dev. Closes: #1068188.
* debian/control.in/main: update glibc-doc description following the removal
of the pthread manpages.
* debian/control.in/main: downgrade the Recommends from libc-dev-bin to
libc-devtools to a Suggests. Closes: #1067909.
*
Processing of glibc_2.37-16_source.changes
glibc_2.37-16_source.changes uploaded successfully to localhost along with the files: glibc_2.37-16.dsc glibc_2.37-16.debian.tar.xz glibc_2.37-16_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
glibc_2.37-16_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 10 Apr 2024 00:15:44 +0200
Source: glibc
Architecture: source
Version: 2.37-16
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers
Changed-By: Aurelien Jarno
Closes: 1063624 1063937 1067909 1068188 1068251
Changes:
glibc (2.37-16) unstable; urgency=medium
.
[ Samuel Thibault ]
* debian/patches/hurd-i386/submitted-AF_ROUTE.diff: Also comment out
PF_ROUTE/AF_ROUTE.
* debian/patches/hurd-i386/git-proc_getchildren_rusage.diff: Implement
RUSAGE_CHILDREN, should fix the grep testsuite.
.
[ Aurelien Jarno ]
* debian/rules.d/build.mk: present glibc with a compiler that does not
default to -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64, as upstream doesn't
support this configuration. This has the consequence of hiding real issues
found by the testsuite, but there is a consensus that this is the way to
go for now. Thanks to Helmut Grohne for the hint and starting the
discussion. Closes: #1068251.
* debian/debhelper.in/glibc-doc.{links,manpages},
debian/local/manpages/pthread_*: drop the man pages for libpthread
functions, as they are now included in manpages-dev. Closes: #1068188.
* debian/control.in/main: update glibc-doc description following the removal
of the pthread manpages.
* debian/control.in/main: downgrade the Recommends from libc-dev-bin to
libc-devtools to a Suggests. Closes: #1067909.
* debian/patches/git-updates.diff: update from upstream stable branch.
* debian/patches/sparc/submitted-sparc-clone.diff: pull patch from the
upstream BTS to workaround issues with the clone syscall on sparc.
Closes: #1063937.
.
[ Johannes Schauer Marin Rodrigues]
* debian/debhelper.in/libc.preinst: skip kernel check in chrootless mode.
Closes: #1063624.
.
[ Steve Langasek ]
* Drop transitional dependency from libc6-dev to libnsl-dev.
.
[ Gioele Barabucci ]
* debian/debhelper.in/locales.config: Extract default environment LANG using
only sed.
Checksums-Sha1:
eaea3d56f7a38679550c9aed687e94b4ee06e26d 9043 glibc_2.37-16.dsc
b049cfcbfdf698174f8edd5f57d6a0d197d2db8b 412544 glibc_2.37-16.debian.tar.xz
c52c4a023fe835c6a0de5a61e88f8e43a8ef46e9 10134 glibc_2.37-16_source.buildinfo
Checksums-Sha256:
d51319d515d3c5e41a7a02c6f38fabb0f80e4d171f7171a85cafb9b9f3c78d3b 9043
glibc_2.37-16.dsc
9ba0e7da8897e4e6f35b85d45dc52ef9e991a6ed9561e47a749bd6421577 412544
glibc_2.37-16.debian.tar.xz
3b6db197b8f3c64c2b6967f6b619a7ba87c0608b9eb6e2fc36622152ccb0a7cf 10134
glibc_2.37-16_source.buildinfo
Files:
48ee58919315243ff3360c8bc1e8e16c 9043 libs required glibc_2.37-16.dsc
7a6a64b3f2993c269dd94d1926f674a9 412544 libs required
glibc_2.37-16.debian.tar.xz
5b147d415a0154c41630f2447b7ceac8 10134 libs required
glibc_2.37-16_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmYVvuAACgkQE4jA+Jno
M2vB6A/+PLMCij5yZepiubXkghOsfPRsg7XOWqGJ6qswaFSKdK9RmKl3xO+C3INI
ylEH5GINvdCG/9QxWWTnybAzOltbRTrmBA7Fi9bsuB9VDaw18j4pUH7zW2f3fNgN
OifWBWTgneM/bazbXz1w2PoiXLGsOc+8Ai1DrwohOVgLGAlr9tBiZ8w4jHJZDXYb
EJhWloDQx4GtsH5eANS0ISoL4++VB0AQPNhH3vzWsFb064r126eZyXKLPbijmt4x
xxJRTIiPGMlPe+LDYprWoyWL17qwtmESZBWIIV/yuCuk1s0WBj8rfztX0nK3FSOW
e5IzjujID8evUyzPHWPumhSUp1Xo1OE40kx2dRKVxXLppweG9sUgj77xi05R/Ruq
QJYNQKdqQrwVS72XVEvhuF1/eKpk7lKzgYC0JkkWzejXEHomZlkHyQkqOtMWYDId
q15B6MfwW39Q7D7T+yCbsxwAsOBgIlDwnGgGcOXxB2lVy8dEFiIjO0fhGOnUZx3c
7A8+YF/x7GNARHzJEYrChLkzQY9xuPeQuaMGedae1f84MFOU9cV0scQgi2w3bheb
epRFcZQrzRG8YG1u5ozjbD5hLBacYUfDJLxOC0Yc/nEHTMJ4/DLramJ63tujGy6e
HC4E2mvhN99MFz8NSlw9E3VgNc3s/O6b4xyeXUGCaKMjF3ceviQ=
=uzJ0
-END PGP SIGNATURE-
pgpjTCG7fzcQx.pgp
Description: PGP signature
[Git][glibc-team/glibc] Pushed new tag debian/2.37-16
Aurelien Jarno pushed new tag debian/2.37-16 at GNU Libc Maintainers / glibc -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.37-16 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc][sid] releasing package glibc version 2.37-16
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: 7cc8417d by Aurelien Jarno at 2024-04-10T00:16:43+02:00 releasing package glibc version 2.37-16 - - - - - 1 changed file: - debian/changelog View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/7cc8417d3df414ecb37dd2b45053580aee77c3de -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/7cc8417d3df414ecb37dd2b45053580aee77c3de You're receiving this email because of your account on salsa.debian.org.
Processed: Bug#1063937 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1063937 [src:glibc] glibc: Please add workaround to fix posix_spawn() on sparc64 Added tag(s) pending. -- 1063937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[Git][glibc-team/glibc][sid] debian/patches/sparc/submitted-sparc-clone.diff: pull patch from the upstream...
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: fddf20e3 by Aurelien Jarno at 2024-04-10T00:15:00+02:00 debian/patches/sparc/submitted-sparc-clone.diff: pull patch from the upstream BTS to workaround issues with the clone syscall on sparc. Closes: #1063937. - - - - - 3 changed files: - debian/changelog - debian/patches/series - + debian/patches/sparc/submitted-sparc-clone.diff View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/fddf20e3af465dfc76744242b8599148484d9c12 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/fddf20e3af465dfc76744242b8599148484d9c12 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc][sid] Add changelog entry
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: 2633f0e5 by Aurelien Jarno at 2024-04-10T00:06:58+02:00 Add changelog entry - - - - - 1 changed file: - debian/changelog View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/2633f0e59a1812692aa69468b1f00583d3a805af -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/2633f0e59a1812692aa69468b1f00583d3a805af You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc][sid] locales.config: Extract default environment LANG using only sed
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: 89d9ea27 by Gioele Barabucci at 2024-04-09T22:02:55+00:00 locales.config: Extract default environment LANG using only sed The cat + awk pipeline can be simplified into a single sed command. Originally proposed in https://salsa.debian.org/glibc-team/glibc/-/merge_requests/19#note_411469 - - - - - 1 changed file: - debian/debhelper.in/locales.config View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/89d9ea27b0ce20f6186f0f1d4be301fb12bc97ab -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/89d9ea27b0ce20f6186f0f1d4be301fb12bc97ab You're receiving this email because of your account on salsa.debian.org.
Processed: Bug#1063624 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1063624 [src:glibc] libc.preinst: please skip kernel check via uname when DPKG_ROOT is not empty for gnu hurd support Added tag(s) pending. -- 1063624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[Git][glibc-team/glibc][sid] Add changelog entry
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: bbb9f9fc by Aurelien Jarno at 2024-04-10T00:01:53+02:00 Add changelog entry - - - - - 1 changed file: - debian/changelog View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/bbb9f9fca632d55ce0c15873b269fecb53be630d -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/bbb9f9fca632d55ce0c15873b269fecb53be630d You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc][sid] debian/debhelper.in/libc.preinst: skip kernel check in chrootless mode
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: 2545f12e by Johannes Schauer Marin Rodrigues at 2024-04-09T21:56:13+00:00 debian/debhelper.in/libc.preinst: skip kernel check in chrootless mode If glibc is installed in chrootless mode (i.e. $DPKG_ROOT is not empty), then checking the currently running kernel is not useful. At the point where the chroot is created on system X, the kernel running on X can be wildly different from the system Y that the chroot is supposed to run on. This was discovered when creating hurd chroots on linux. The tools creating the chroot have no information about the kernel which might run on the system that the chroot is built for. This commits adds an additional condition to the preinst block doing the kernel checks. It is only executed if $DPKG_ROOT is empty, in other words, only if this is a normal installation. Closes: #1063624 - - - - - 1 changed file: - debian/debhelper.in/libc.preinst View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/2545f12e68b6acd712cb2e06cfe3ef5f34a62adc -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/2545f12e68b6acd712cb2e06cfe3ef5f34a62adc You're receiving this email because of your account on salsa.debian.org.
Processed: Bug#1068251 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1068251 [src:glibc] glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t Added tag(s) pending. -- 1068251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1068188 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1068188 [glibc-doc] pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1 Added tag(s) pending. -- 1068188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1067909 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1067909 [libc-devtools] libc-devtools: please relax Depends on libgd3 Added tag(s) pending. -- 1067909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[Git][glibc-team/glibc][sid] 6 commits: debian/rules.d/build.mk: present glibc with a compiler that does not default...
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc
Commits:
2aeb4303 by Aurelien Jarno at 2024-04-09T21:08:49+02:00
debian/rules.d/build.mk: present glibc with a compiler that does not default to
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64, as upstream doesnt support this
configuration. This has the consequence of hiding real issues found by the
testsuite, but there is a consensus that this is the way to go for now. Thanks
to Helmut Grohne for the hint and starting the discussion. Closes: #1068251.
- - - - -
161a1663 by Aurelien Jarno at 2024-04-09T21:44:40+02:00
debian/debhelper.in/glibc-doc.{links,manpages},
debian/local/manpages/pthread_*: drop the man pages for libpthread functions,
as they are now included in manpages-dev. Closes: #1068188.
- - - - -
5667af1c by Aurelien Jarno at 2024-04-09T22:37:21+02:00
debian/control.in/main: update glibc-doc description following the removal of
the pthread manpages.
- - - - -
5e78b9d9 by Aurelien Jarno at 2024-04-09T22:57:33+02:00
Drop transitional dependency from libc6-dev to libnsl-dev.
(Imported from 2.37-15.1 NMU)
- - - - -
0e91ab7b by Aurelien Jarno at 2024-04-09T23:06:00+02:00
debian/control.in/main: downgrade the Recommends from libc-dev-bin to
libc-devtools to a Suggests. Closes: #1067909.
- - - - -
b80adafc by Aurelien Jarno at 2024-04-09T23:06:41+02:00
debian/patches/git-updates.diff: update from upstream stable branch.
- - - - -
17 changed files:
- debian/changelog
- debian/control
- debian/control.in/libc
- debian/control.in/main
- − debian/debhelper.in/glibc-doc.links
- − debian/debhelper.in/glibc-doc.manpages
- − debian/local/manpages/pthread_atfork.3
- − debian/local/manpages/pthread_cond_init.3
- − debian/local/manpages/pthread_condattr_init.3
- − debian/local/manpages/pthread_key_create.3
- − debian/local/manpages/pthread_mutex_init.3
- − debian/local/manpages/pthread_mutexattr_init.3
- − debian/local/manpages/pthread_mutexattr_setkind_np.3
- − debian/local/manpages/pthread_once.3
- debian/patches/git-updates.diff
- debian/rules.d/build.mk
- debian/rules.d/debhelper.mk
View it on GitLab:
https://salsa.debian.org/glibc-team/glibc/-/compare/e165102f56d8e841d839561ef2d7ce9133bfa169...b80adafc52c1ab1818b8b2221c67fabae4473041
--
View it on GitLab:
https://salsa.debian.org/glibc-team/glibc/-/compare/e165102f56d8e841d839561ef2d7ce9133bfa169...b80adafc52c1ab1818b8b2221c67fabae4473041
You're receiving this email because of your account on salsa.debian.org.
Bug#1066887: ENhance Patch for local-gen
Hi,
On 2024-03-15 16:13, M. Buecher wrote:
> Adding / back to end of the path, so that a locale file is immediately
> found.
> diff --git a/debian/local/usr_sbin/locale-gen
> b/debian/local/usr_sbin/locale-gen
> index 7fa3d772..1711a4f0 100755
> --- a/debian/local/usr_sbin/locale-gen
> +++ b/debian/local/usr_sbin/locale-gen
> @@ -23,6 +23,12 @@ is_entry_ok() {
> fi
> }
>
> +if [ -z "${I18NPATH:-}" ]; then
> + if [ -d "${USER_LOCALES}" ]; then
> +I18NPATH="${USER_LOCALES%%/locales*}/"
> + fi
> +fi
> +
> echo "Generating locales (this might take a while)..."
> while read -r locale charset; do
> if [ -z "$locale" ] || [ "${locale#\#}" != "$locale" ]; then continue;
> fi
> @@ -46,7 +52,7 @@ while read -r locale charset; do
> input="$USER_LOCALES/$input"
> fi
> fi
> - localedef -i "$input" -c -f "$charset" -A
> /usr/share/locale/locale.alias "$locale" || :
> + I18NPATH="${I18NPATH}" localedef -i "$input" -c -f "$charset" -A
> /usr/share/locale/locale.alias "$locale" || :
> echo " done"
> done < "$LOCALEGEN"
> echo "Generation complete."
Thanks for your bug report and for even proposing a patch which looks
good to me.
That said as I18NPATH could actually contains a list of directory, I
wonder if the behaviour would be more consistent if the user locales
directory is always prepended to I18NPATH if it exists. What do you
think?
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net
Bug#1067505: libc-bin: iconv: misleading error "illegal input sequence"
Hi, On 2024-03-22 16:42, Frank Heckenbach wrote: > - I tried to report it upstream, but that's also broken. According to > https://www.gnu.org/software/libc/manual/html_node/Reporting-Bugs.html, bugs > should be reported at https://www.gnu.org/software/libc/bugs.html, but this > page redirects to https://www.gnu.org/savannah-checkouts/gnu/libc/index.html > which does not mention reporting bugs. Please see this page for reporting bug upstream: https://sourceware.org/glibc/bugs.html Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1068251: glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t
Hi,
On 2024-04-09 07:56, Helmut Grohne wrote:
> Hi Aurelien,
>
> On Mon, Apr 08, 2024 at 11:24:40PM +0200, Aurelien Jarno wrote:
> > Thanks for you analysis and your patch. In short your proposal is to
> > extend the initial patch from Steve to fully hide the fact that the
> > compiler default to -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64.
> >
> > This indeed works and fixes the FTBFS. However it seems that, at least
> > for some of the issues, it just hides them. For instance the wrong type
> > for timeval.tv_usec, reported by Simon upstream [1], was detected by the
> > conformance tests. Quoting utmpx.h/conform.out:
>
> I think this needs a more nuanced look. From the comments in the
> conformance test suite, it is evident that it expects to be run without
> _FILE_OFFSET_BITS and _TIME_BITS. Many of the symbols it requires to
> exist only exist when these macros are unset. The conformance test suite
> has a comment saying that it should be testing the case where
> _FILE_OFFSET_BITS is defined, but it currently does not provide
> expectations for that case.
>
> Before we can reasonably run the conformance test suite with these
> macros set (and really, the test suite should be in control of these
> macros), we cannot reasonably use it with them set. Let us now imagine a
> future where the conformance test suite has been extended to provide
> expectations (which in lots of cases means that *64 symbols disappear
> when -D_FILE_OFFSET_BITS=64). Then what still remains is Simon's issue:
>
> > | /tmp/tmp98wzaavx/test.c:4:35: error: conflicting types for ‘b2_10’; have
> > ‘__suseconds64_t’ {aka ‘long long int’}
> > | 4 | extern __typeof__ (a2_10.tv_usec) b2_10;
> > | | ^
> > | /tmp/tmp98wzaavx/test.c:3:20: note: previous declaration of ‘b2_10’ with
> > type ‘suseconds_t’ {aka ‘long int’}
> > | 3 | extern suseconds_t b2_10;
> > | |^
> > | FAIL: Type of member tv_usec
>
> Indeed, this is not something that can easily be fixed and where
> upstream is still debating on what the correct solution should be. It
> also is an issue that existed for a long time. If you head over to a
> bookworm glibc and enable -D_TIME_BITS=64 there, you'll also notice that
> tv_usec and suseconds_t have different sizes. So yes, this is a bug, but
> it is not one that is directly related to Debian changing the default.
> We merely increased the visibility of this problem that existed earlier
> already.
I agree that this is an existing issue. My point there was mostly that
your solution is just hiding a real issue that is found by the
testsuite, and basically the testsuite runs in a different configuration
than the one used on the system. We might just miss new issues for new
upstream versions, which is not something very comfortable for a base
library.
> Given that
> * the issue is already present in bookworm,
> * there are two mutually exclusive solutions and
> * upstream is still discussing the best solution
> I recommend deferring this aspect.
While the issue is already present in bookworm, it is not visible
because the toolchain has different defaults.
> > And we know it is the reason for the FTBFS of libflorist [2], so should
> > we just ignore that issue anyway?
>
> The libflorist issue likely is a consequence. It arises from
> gnat_to_gnu_field where GNAT verifies that the value (of type
> suseconds_t) to be assigned to a field (tv_usec) has the matching size.
> This is directly based on the POSIX expectation and will be fixed with
> the glibc issue.
>
> How about filing a separate bug with glibc that tracks this POSIX
> divergence and mark the libflorist bug as being blocked by this other
> glibc bug? It can be RC or not, but since it affects bookworm, it won't
> block testing migration.
Yes we can do that. That said I am not sure we can claim the issue
affects bookworm, as again the toolchain does not have the same defaults
and therefore libflorist does not FTBFS in bookworm.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net
signature.asc
Description: PGP signature
Bug#1068251: glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t
Hi Aurelien,
On Mon, Apr 08, 2024 at 11:24:40PM +0200, Aurelien Jarno wrote:
> Thanks for you analysis and your patch. In short your proposal is to
> extend the initial patch from Steve to fully hide the fact that the
> compiler default to -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64.
>
> This indeed works and fixes the FTBFS. However it seems that, at least
> for some of the issues, it just hides them. For instance the wrong type
> for timeval.tv_usec, reported by Simon upstream [1], was detected by the
> conformance tests. Quoting utmpx.h/conform.out:
I think this needs a more nuanced look. From the comments in the
conformance test suite, it is evident that it expects to be run without
_FILE_OFFSET_BITS and _TIME_BITS. Many of the symbols it requires to
exist only exist when these macros are unset. The conformance test suite
has a comment saying that it should be testing the case where
_FILE_OFFSET_BITS is defined, but it currently does not provide
expectations for that case.
Before we can reasonably run the conformance test suite with these
macros set (and really, the test suite should be in control of these
macros), we cannot reasonably use it with them set. Let us now imagine a
future where the conformance test suite has been extended to provide
expectations (which in lots of cases means that *64 symbols disappear
when -D_FILE_OFFSET_BITS=64). Then what still remains is Simon's issue:
> | /tmp/tmp98wzaavx/test.c:4:35: error: conflicting types for ‘b2_10’; have
> ‘__suseconds64_t’ {aka ‘long long int’}
> | 4 | extern __typeof__ (a2_10.tv_usec) b2_10;
> | | ^
> | /tmp/tmp98wzaavx/test.c:3:20: note: previous declaration of ‘b2_10’ with
> type ‘suseconds_t’ {aka ‘long int’}
> | 3 | extern suseconds_t b2_10;
> | |^
> | FAIL: Type of member tv_usec
Indeed, this is not something that can easily be fixed and where
upstream is still debating on what the correct solution should be. It
also is an issue that existed for a long time. If you head over to a
bookworm glibc and enable -D_TIME_BITS=64 there, you'll also notice that
tv_usec and suseconds_t have different sizes. So yes, this is a bug, but
it is not one that is directly related to Debian changing the default.
We merely increased the visibility of this problem that existed earlier
already.
Given that
* the issue is already present in bookworm,
* there are two mutually exclusive solutions and
* upstream is still discussing the best solution
I recommend deferring this aspect.
> And we know it is the reason for the FTBFS of libflorist [2], so should
> we just ignore that issue anyway?
The libflorist issue likely is a consequence. It arises from
gnat_to_gnu_field where GNAT verifies that the value (of type
suseconds_t) to be assigned to a field (tv_usec) has the matching size.
This is directly based on the POSIX expectation and will be fixed with
the glibc issue.
How about filing a separate bug with glibc that tracks this POSIX
divergence and mark the libflorist bug as being blocked by this other
glibc bug? It can be RC or not, but since it affects bookworm, it won't
block testing migration.
Helmut
