Bug#1000652: marked as done (/usr/bin/iconv: bus error iconv -f CP1251 -t UTF-8 wmsal.h -o wmsal.h)
Your message dated Tue, 24 Sep 2024 20:35:54 + with message-id and subject line Bug#1000652: fixed in glibc 2.40-3 has caused the Debian Bug report #1000652, regarding /usr/bin/iconv: bus error iconv -f CP1251 -t UTF-8 wmsal.h -o wmsal.h 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.) -- 1000652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc-bin Version: 2.31-13+deb11u2 Severity: normal File: /usr/bin/iconv Dear Maintainer, Steps: % wget https://raw.githubusercontent.com/4creators/jxrlib/master/common/include/wmsal.h % iconv -f CP1251 -t UTF-8 wmsal.h -o wmsal.h zsh: bus error iconv -f CP1251 -t UTF-8 wmsal.h -o wmsal.h I see this documented as well known error: https://myotragusbalearicus.wordpress.com/2010/03/10/batch-convert-files-to-utf-8/ For reference: Program received signal SIGBUS, Bus error. 0x77fc0578 in from_gap (irreversible=0x7fff5990, outend=0x5556dfc0 "", outptrp=, inend=0x77fbe69e , inptrp=0x7fff5ad8, step_data=0x55565fd0, step=0x55565800) at ../iconv/loop.c:336 336 BODY (gdb) bt #0 0x77fc0578 in from_gap (irreversible=0x7fff5990, outend=0x5556dfc0 "", outptrp=, inend=0x77fbe69e , inptrp=0x7fff5ad8, step_data=0x55565fd0, step=0x55565800) at ../iconv/loop.c:336 #1 gconv (step=0x55565800, data=0x55565fd0, inptrp=0x7fff5ad8, inend=0x77fbe69e , outbufstart=0x0, irreversible=0x7fff5a70, do_flush=0, consume_incomplete=0) at ../iconv/skeleton.c:620 #2 0x77dd56bf in __gconv (cd=0x55565fc0, inbuf=inbuf@entry=0x7fff5ad8, inbufend=0x77fbe69e , outbuf=outbuf@entry=0x7fff5ae0, outbufend=, irreversible=irreversible@entry=0x7fff5a70) at gconv.c:78 #3 0x77dd50e7 in iconv (cd=, inbuf=0x7fff5ad8, inbytesleft=0x7fff5ad0, outbuf=0x7fff5ae0, outbytesleft=0x7fff5ae8) at iconv.c:52 #4 0x8274 in ?? () #5 0x780b in ?? () #6 0x77dd4d0a in __libc_start_main (main=0x75a0, argc=8, argv=0x7fffdd58, init=, fini=, rtld_fini=, stack_end=0x7fffdd48) at ../csu/libc-start.c:308 #7 0x7d1a in ?? () (gdb) list 331 332 /* Here comes the body the user provides. It can stop with 333 RESULT set to GCONV_INCOMPLETE_INPUT (if the size of the 334 input characters vary in size), GCONV_ILLEGAL_INPUT, or 335 GCONV_FULL_OUTPUT (if the output characters vary in size). */ 336 BODY 337 } 338 339 /* Update the pointers pointed to by the parameters. */ 340 *inptrp = inptr; (gdb) Thanks -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-0.bpo.2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libc-bin depends on: ii libc6 2.31-13+deb11u2 Versions of packages libc-bin recommends: ii manpages 5.10-1 libc-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.40-3 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 1000...@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: Tue, 24 Sep 2024 21:46:16 +0200 Source: glibc Architecture: source Version: 2.40-3 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 328303 1000652 Cha
Bug#328303: marked as done (iconv breaks on piped input, because it tries to read whole input into a buffer)
Your message dated Tue, 24 Sep 2024 20:35:54 + with message-id and subject line Bug#328303: fixed in glibc 2.40-3 has caused the Debian Bug report #328303, regarding iconv breaks on piped input, because it tries to read whole input into a buffer 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.) -- 328303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=328303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6 Version: 2.3.2.ds1-22 iconv(1) tries to read in its whole input before doing conversion. This is no good if you want to use it in a pipe. Example: yes | iconv -f utf-8 -t iso-8859-1 expected result: ten lines of `y' actual result: iconv runs out of memory As a more serious example, consider zcat dump-of-wikipedia.xml.gz | iconv -f utf-8 -t $charset | ... -- ``The Strategic Railway Authority is not in the business of railway lines.'' (Cambridgeshire County Councillor Shona Johnstone) --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.40-3 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 328...@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: Tue, 24 Sep 2024 21:46:16 +0200 Source: glibc Architecture: source Version: 2.40-3 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 328303 1000652 Changes: glibc (2.40-3) unstable; urgency=medium . [ Samuel Thibault ] * debian/testsuite-xfail-debian.mk: Avoid tests overflowing memory. * debian/testsuite-xfail-debian.mk: Update hurd xfails. . [ Aurelien Jarno ] * debian/rules: build with gcc-14. * debian/control.in/main: adjust g++-for-host version on arm64 to ensure PAC/BTI support. * debian/patches/git-updates.diff: update from upstream stable branch. * debian/patches/any/git-iconv-*: backport iconv fixes and improvement from upstream master. Closes: #328303, #1000652. Checksums-Sha1: d96378d7546e6f73183ba9a56cf20860f34a1e78 7550 glibc_2.40-3.dsc 09a651e8f3e07c2eb71922b855248db1fdc079ff 417288 glibc_2.40-3.debian.tar.xz cf383b3d306bafbcc58caf2294dbe6b061acd159 11229 glibc_2.40-3_source.buildinfo Checksums-Sha256: ad595e37545bf472d2ce8de51712121c88ca960d2e5617af6359d795d7d35f84 7550 glibc_2.40-3.dsc 1a30c14bc68422b6085c0a4d9f0db2be82dffd7da0bf3090307bbbe237c08f73 417288 glibc_2.40-3.debian.tar.xz 408085bbc892ad3df04ff48c1665d94d868f69f35cae96e5e008ce8b39539542 11229 glibc_2.40-3_source.buildinfo Files: 3965b42ac0ddd5751115bfca56465804 7550 libs required glibc_2.40-3.dsc 6eedbba101473dd163b516a6d9d5a013 417288 libs required glibc_2.40-3.debian.tar.xz 4cbca4b6a5480e8295e32094693461f2 11229 libs required glibc_2.40-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmbzGPgACgkQE4jA+Jno M2tOmw//UBasQYrGcw6S4XdO1wqAqu6T2DAORQXSJdlMjsHGT7O+2xcRydEIXJhx dASmgTt66apsZKOCy/Ew+V8WrdQ6riaZyxF7rMxxPwu7Mg5tms1T+xf9tEqD/zJH Qnn22/ZVT2U8pRNZ9Dgq/sIYVbIQSZLuQso56+Q3YYGAdnhi4KJlhZHX4NTMCHlu pcCM411BMHgqvMm05GdE1iZnR9QW50eyM4c73v+lZxhMIubPcksOKMTMKEbJG9rL 6BYpegDSQ22j41+ffTjNu7fkyjdwG0zHQP2i81kWEyjIqBB+gv/CXnRgGSZCWFRO oaWda0hk/kowcH8E35pDrPusA8jlbMsB3EBBVcOKat2TcWyrCD3A8MtEWeiCFa8r 3zEbvKaGg3RANcuGQk5upulchHssG8wn2jDvEswG2Kq5P7VBN9Lt7uM2iG3FoXGj DDEj0E8JpLvSodzit4PRueZyGJmINN9sAmYqyBgXBXXHO3DBJakamNwV1s9uho/T wjBkD9dP64p5rd/30k9eFNXIyTHz61rveKYYuFv8g1DoZOVhwOvmt00P2+lh2gXK OPv55tdZjEtp4PTuZshZKfiSUXkLLuUSc57bB4wDC2Jr5Hrw/o6Z5TCOSDKQSI3j iGUIW3CImucJuJOGlzqx55F3xdhNpFr/0/RwVu5UlQ81GyAyPHg= =l0zl -END PGP SIGNATURE- pgpfMoek9IoPR.pgp Description: PGP signature --- End Message ---
Bug#531188: marked as done (iconvconfig has a misaligned pointer access on arm)
Your message dated Tue, 24 Sep 2024 21:31:22 +0200 with message-id and subject line Re: Bug#531188: iconvconfig has a misaligned pointer access on arm has caused the Debian Bug report #531188, regarding iconvconfig has a misaligned pointer access on arm 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.) -- 531188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6 Version: 2.7-18 Severity: minor While apt-get upgrading an arm-lenny system I see the following: - Checking init scripts... /var/lib/dpkg/info/libc6.postinst: line 343: 2254 Bus error iconvconfig - This occurs because I have detection of misaligned word accesses enabled on my arm box (echo 5 > /proc/cpu/alignment) whereas such accesses normally give garbage results, returning the word from *(addr & ~3) rotated so that the byte at *(char *)addr is in the least significant position. The offending instruction is (gdb) x/i 0x989c 0x989c : ldr r2, [r5] where r5 0x5875e 362334 (should be a multiple of 4). With libc6-dbg installed: Program received signal SIGBUS, Bus error. 0x989c in write_output () (gdb) bt #0 0x989c in write_output () #1 0xa7dc in main () which suggests that on most Debian ARM machines some piece(s) of 4-byte data are being written to somewhere half-word-swapped. Strangely enough, the same symptom does not occur with the same version of libc6 on armel-lenny (only arm-lenny) on the same machine. Repeat-by: # iconvconfig Bus error # --- End Message --- --- Begin Message --- Hi, On 2009-05-30 16:46, Martin Guy wrote: > Package: libc6 > Version: 2.7-18 > Severity: minor > > While apt-get upgrading an arm-lenny system I see the following: > - > Checking init scripts... > > /var/lib/dpkg/info/libc6.postinst: line 343: 2254 Bus error > iconvconfig > - > This occurs because I have detection of misaligned word accesses > enabled on my arm box > (echo 5 > /proc/cpu/alignment) whereas such accesses normally give > garbage results, returning the word from *(addr & ~3) rotated so that > the byte at *(char *)addr is in the least significant position. > > The offending instruction is > (gdb) x/i 0x989c > 0x989c : ldr r2, [r5] > where > r5 0x5875e 362334 > (should be a multiple of 4). > > With libc6-dbg installed: > > Program received signal SIGBUS, Bus error. > 0x989c in write_output () > (gdb) bt > #0 0x989c in write_output () > #1 0xa7dc in main () > > which suggests that on most Debian ARM machines some piece(s) of > 4-byte data are being written to somewhere half-word-swapped. This looks like more a compiler problem than a glibc issue. > Strangely enough, the same symptom does not occur with the same > version of libc6 on armel-lenny (only arm-lenny) on the same machine. The arm architecture has been removed from debian for many many years, and replaced by armel and later armhf, which are not affected. I am therefore closing the bug. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net--- End Message ---
Processed: [bts-link] source package glibc
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package glibc > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #328303 (http://bugs.debian.org/328303) > # Bug title: iconv breaks on piped input, because it tries to read whole > input into a buffer > # * http://sourceware.org/bugzilla/show_bug.cgi?id=6050 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 328303 + fixed-upstream Bug #328303 [libc6] iconv breaks on piped input, because it tries to read whole input into a buffer Added tag(s) fixed-upstream. > usertags 328303 - status-NEW Usertags were: status-NEW. There are now no usertags set. > usertags 328303 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #1000652 (http://bugs.debian.org/1000652) > # Bug title: /usr/bin/iconv: bus error iconv -f CP1251 -t UTF-8 wmsal.h -o > wmsal.h > # * http://sourceware.org/bugzilla/show_bug.cgi?id=10460 > # * remote status changed: REOPENED -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 1000652 + fixed-upstream Bug #1000652 [libc-bin] /usr/bin/iconv: bus error iconv -f CP1251 -t UTF-8 wmsal.h -o wmsal.h Added tag(s) fixed-upstream. > usertags 1000652 - status-REOPENED Usertags were: status-REOPENED. There are now no usertags set. > usertags 1000652 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000652 328303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=328303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1081201: marked as done (libc6-dev:amd64 : Breaks: libc6-dev-amd64-cross (< 2.40~) but 2.39-4cross1 is to be installed)
Your message dated Sun, 22 Sep 2024 16:49:29 + with message-id and subject line Bug#1081201: fixed in cross-toolchain-base 71 has caused the Debian Bug report #1081201, regarding libc6-dev:amd64 : Breaks: libc6-dev-amd64-cross (< 2.40~) but 2.39-4cross1 is to be installed 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.) -- 1081201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6-dev-amd64-cross Version: 2.39-4cross1 Severity: serious X-Debbugs-Cc: debian-cr...@lists.debian.org Hi, while trying to cross-build the next upload of my source package pico-sdk for amd64 on my arm64 box in a clean unstable chroot with sbuild, I ran into the following problem: Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Execute external solver... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libc6-dev:amd64 : Breaks: libc6-dev-amd64-cross (< 2.40~) but 2.39-4cross1 is to be installed E: Broken packages apt-get failed. E: Package installation failed On salsa-ci, the problem is even more weird. The test-crossbuild-arm64 job ends up installing the native architecture compilers: The following NEW packages will be installed: binutils-aarch64-linux-gnu:arm64 binutils-common:arm64 cpp-14-aarch64-linux-gnu:arm64 cpp-aarch64-linux-gnu cross-config crossbuild-essential-arm64 dpkg-cross file g++-14-aarch64-linux-gnu:arm64 g++-aarch64-linux-gnu gcc-14-aarch64-linux-gnu:arm64 gcc-14-base:arm64 gcc-aarch64-linux-gnu libasan8:arm64 libatomic1:arm64 libbinutils:arm64 libc6:arm64 libc6-dev:arm64 libcc1-0:arm64 libconfig-auto-perl libconfig-inifiles-perl libcrypt-dev:arm64 libcrypt1:arm64 libctf-nobfd0:arm64 libctf0:arm64 libdebian-dpkgcross-perl libfile-homedir-perl libfile-which-perl libgcc-14-dev:arm64 libgcc-s1:arm64 libgmp10:arm64 libgomp1:arm64 libgprofng0:arm64 libhwasan0:arm64 libicu72 libio-string-perl libisl23:arm64 libitm1:arm64 libjansson4:arm64 liblocale-gettext-perl liblsan0:arm64 libmagic-mgc libmagic1t64 libmpc3:arm64 libmpfr6:arm64 libsframe1:arm64 libstdc++-14-dev:arm64 libstdc++6:arm64 libtsan2:arm64 libubsan1:arm64 libxml-libxml-perl libxml-namespacesupport-perl libxml-sax-base-perl libxml-sax-perl libxml-simple-perl libxml2 libyaml-perl libzstd1:arm64 sensible-utils ucf zlib1g:arm64 This means that the build later fails with: /usr/lib/ccache/aarch64-linux-gnu-g++ -g -O2 -ffile-prefix-map=/builds/debian/pico-sdk/debian/output/source_dir=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/cmTC_e5da0.dir/testCXXCompiler.cxx.o -c /builds/debian/pico-sdk/debian/output/source_dir/pioasm-obj-aarch64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-fi0q8w/testCXXCompiler.cxx ccache: error: execute_noreturn of /usr/bin/aarch64-linux-gnu-g++ failed: Exec format error Because obviously, the compiler binary from g++-14-aarch64-linux-gnu:arm64 cannot be executed on amd64. Full log here: https://salsa.debian.org/debian/pico-sdk/-/jobs/6250227/raw The problem does not seem to be limited to my package pico-sdk, hence the severity. Thanks! cheers, josch --- End Message --- --- Begin Message --- Source: cross-toolchain-base Source-Version: 71 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of cross-toolchain-base, 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 1081...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated cross-toolchain-base 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: Sun, 22 Sep 2
Processed: bug 1080244 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=32148
Processing commands for cont...@bugs.debian.org: > forwarded 1080244 https://sourceware.org/bugzilla/show_bug.cgi?id=32148 Bug #1080244 [libc6] Memory corruption with ancient i386 binaries using stdio Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=32148'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1080244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1078127: libc6: mcheck(NULL) fails even at the beginning of a program
Processing control commands: > tags -1 upstream Bug #1078127 [libc6] libc6: mcheck(NULL) fails even at the beginning of a program Added tag(s) upstream. > forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=32156 Bug #1078127 [libc6] libc6: mcheck(NULL) fails even at the beginning of a program Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=32156'. -- 1078127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#154401: marked as done (locales: Insert french manpages locale.gen.5, locale-gen.8 and locale.alias.5)
Your message dated Sat, 31 Aug 2024 18:39:38 + with message-id and subject line Re: locales: Insert french manpages locale.gen.5, locale-gen.8 and locale.alias.5 has caused the Debian Bug report #154401, regarding locales: Insert french manpages locale.gen.5, locale-gen.8 and locale.alias.5 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.) -- 154401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=154401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: locales Version: 2.2.5-12 Severity: wishlist I made french translations for this three manpages it will be useful for french users:-) -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux debian 2.4.18 #1 SMP lun jun 10 09:21:16 CEST 2002 i686 Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set) Versions of packages locales depends on: ii debconf 1.1.18 Debian configuration management sy ii libc6 [glibc-2.2.5-12]2.2.5-12 GNU C Library: Shared libraries an -- debconf information: * locales/default_environment_locale: C * locales/locales_to_be_generated: fr_FR@euro ISO-8859-15, fr_FR ISO-8859-1, fr_FR.UTF-8 UTF-8 --- End Message --- --- Begin Message --- Hello Julien, thanks for your contribution to Debian. Am Fri, Jul 26, 2002 at 08:15:40PM +0200 schrieb Julien Louis: > Package: locales > Version: 2.2.5-12 > Severity: wishlist > > I made french translations for this three manpages > it will be useful for french users:-) locale.gen.5 and locale-gen.8 are shipped by manpages-fr (part of manpages-l10n) for quite some time. locale.alias.5 no longer exists (at least in Debian). If you are interested in further translations, contact debian-l10-fre...@lists.debian.org or join manpages-l10n. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature --- End Message ---
Processed: Re: Bug#1079443: Processed: Re: dracut-install ... -m =drivers/XXX is ignored
Processing control commands: > unmerge 1079443 Bug #1079443 [src:glibc] fts_build() calling __getdents breaks 32bit on 64bit Bug #916276 [src:glibc] glibc: Please add prelimenary patch to fix regression on qemu-user Bug #1002699 [src:glibc] libc6: m68k,s390 readdir not returning filled in dirent pointer Disconnected #1079443 from all other report(s). > retitle 1079443 fts_* calling non-LFS __readdir Bug #1079443 [src:glibc] fts_build() calling __getdents breaks 32bit on 64bit Changed Bug title to 'fts_* calling non-LFS __readdir' from 'fts_build() calling __getdents breaks 32bit on 64bit'. -- 1002699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002699 1079443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079443 916276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Processed (with 1 error): Re: Processed: Re: dracut-install ... -m =drivers/XXX is ignored
Processing commands for cont...@bugs.debian.org: > reassign 1079443 src:glibc Bug #1079443 [glibc] fts_build() calling __getdents breaks 32bit on 64bit Bug reassigned from package 'glibc' to 'src:glibc'. Ignoring request to alter found versions of bug #1079443 to the same values previously set Ignoring request to alter fixed versions of bug #1079443 to the same values previously set > forcemerge 916276 1079443 Bug #916276 [src:glibc] glibc: Please add prelimenary patch to fix regression on qemu-user Bug #1002699 [src:glibc] libc6: m68k,s390 readdir not returning filled in dirent pointer Bug #1079443 [src:glibc] fts_build() calling __getdents breaks 32bit on 64bit Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=23960'. Severity set to 'normal' from 'important' Removed indication that 1079443 affects qemu, debvm, and glibc Marked as found in versions glibc/2.28-2. Added tag(s) patch. Bug #1002699 [src:glibc] libc6: m68k,s390 readdir not returning filled in dirent pointer Merged 916276 1002699 1079443 > thanks Stopping processing here. Please contact me if you need assistance. -- 1002699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002699 1079443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079443 916276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Processed: Re: dracut-install ... -m =drivers/XXX is ignored
Processing control commands: > forcemerge 916276 1079443 Bug #916276 [src:glibc] glibc: Please add prelimenary patch to fix regression on qemu-user Bug #1002699 [src:glibc] libc6: m68k,s390 readdir not returning filled in dirent pointer Unable to merge bugs because: package of #1079443 is 'glibc' not 'src:glibc' Failed to forcibly merge 916276: Did not alter merged bugs. -- 1002699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002699 1079443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079443 916276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: glibc: Change bug title
Processing control commands: > retitle -1 fts_build() calling __getdents breaks 32bit on 64bit Bug #1079443 [glibc] dracut-install ... -m =drivers/XXX is ignored Changed Bug title to 'fts_build() calling __getdents breaks 32bit on 64bit' from 'dracut-install ... -m =drivers/XXX is ignored'. -- 1079443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: dracut-install ... -m =drivers/XXX is ignored
Processing control commands: > reassign -1 glibc Bug #1079443 [dracut-install] dracut-install ... -m =drivers/XXX is ignored Bug reassigned from package 'dracut-install' to 'glibc'. No longer marked as found in versions dracut/103-1.1. Ignoring request to alter fixed versions of bug #1079443 to the same values previously set -- 1079443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073916: marked as done (libc6: aio cleanup function __aio_freemem reads uninitialized memory)
Your message dated Fri, 16 Aug 2024 20:47:09 +
with message-id
and subject line Bug#1073916: fixed in glibc 2.36-9+deb12u8
has caused the Debian Bug report #1073916,
regarding libc6: aio cleanup function __aio_freemem reads uninitialized memory
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.)
--
1073916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.36-9+deb12u7
Severity: normal
Tags: patch
Dear Maintainer,
not sure how exploitable this is, but running programs that use aio_write
causes uninitialized memory access on exit.
This has been fixed upstream about a year ago, but the patch has seemingly not
be integrated in Debian bookworm:
<https://sourceware.org/git/?p=glibc.git;a=blobdiff;f=rt/aio_misc.c;h=4b850b1ab602a2ef9575c3313a979d88574024d6;hp=49ec0aa293d8b36a16ecc951b71d3f98d5e254b1;hb=0cee4aa92f5b9b213856c8ba1ab84c34d73c943b;hpb=5473a1747a7bd10a7a271c7e01e942711a707bb8>
<https://sourceware.org/git/?p=glibc.git;a=commit;h=0cee4aa92f5b9b213856c8ba1ab84c34d73c943b>
>From a look at the patch, and the code in version 2.36 that's used to build the
package, it should be trivial to apply the patch also in stable, since the
affected loop is identical and the variable names still the same.
Kind regards, Thomas
-- System Information:
Debian Release: 12.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 6.1.0-21-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libc6 depends on:
ii libgcc-s1 12.2.0-14
Versions of packages libc6 recommends:
ii libidn2-0 2.3.3-1+b1
Versions of packages libc6 suggests:
ii debconf [debconf-2.0] 1.5.82
ii glibc-doc 2.36-9+deb12u7
ii libc-l10n 2.36-9+deb12u7
ii libnss-nis 3.1-4
ii libnss-nisplus 1.3-4
ii locales2.36-9+deb12u7
-- debconf information excluded
>From 0cee4aa92f5b9b213856c8ba1ab84c34d73c943b Mon Sep 17 00:00:00 2001
From: Samuel Thibault
Date: Wed, 12 Apr 2023 00:12:02 +0200
Subject: [PATCH] aio: Fix freeing memory
The content of the pool array is initialized only until pool_size,
pointers between pool_size and pool_max_size were not initialized by the
realloc call in get_elem so they should not be freed.
This fixes aio tests crashing at their termination on GNU/Hurd.
---
rt/aio_misc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rt/aio_misc.c b/rt/aio_misc.c
index 49ec0aa293..4b850b1ab6 100644
--- a/rt/aio_misc.c
+++ b/rt/aio_misc.c
@@ -702,7 +702,7 @@ __aio_freemem (void)
{
size_t row;
- for (row = 0; row < pool_max_size; ++row)
+ for (row = 0; row < pool_size; ++row)
free (pool[row]);
free (pool);
--
2.43.0
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.36-9+deb12u8
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 1073...@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: Thu, 15 Aug 2024 11:10:46 +0200
Source: glibc
Architecture: source
Version: 2.36-9+deb12u8
Distribution: bookworm
Urgency: medium
Maintainer: GNU Libc Maintainers
Changed-By: Aurelien Jarno
Closes: 1073916
Changes:
glibc (2.36-9+deb12u8) bookworm; urgency=medium
.
* debian/patches/git-updates.diff: update from upstream stable branch:
- debian/patches/kfreebsd/submitted-auxv.diff: refreshed.
- debian/patches/any/local-CVE-2024-2961-iso-2022-cn-ext.diff: upstreame
Processed: reassign 1054412 to src:cross-toolchain-base-ports
Processing commands for cont...@bugs.debian.org: > reassign 1054412 src:cross-toolchain-base-ports Bug #1054412 [libc6.1-dev-alpha-cross] cross-toolchain-base-ports: Stable update request to include latest glibc Bug reassigned from package 'libc6.1-dev-alpha-cross' to 'src:cross-toolchain-base-ports'. Ignoring request to alter found versions of bug #1054412 to the same values previously set Ignoring request to alter fixed versions of bug #1054412 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1054412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: request is for bookworm only
Processing commands for cont...@bugs.debian.org: > tags 1054412 bookworm Bug #1054412 [libc6.1-dev-alpha-cross] cross-toolchain-base-ports: Stable update request to include latest glibc Added tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 684134 is normal
Processing commands for cont...@bugs.debian.org: > severity 684134 normal Bug #684134 [locales] Package 'locales' resets pre-set debconf variable 'default_environment_locale' on install Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 684134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 684134 is serious
Processing commands for cont...@bugs.debian.org: > severity 684134 serious Bug #684134 [locales] Package 'locales' resets pre-set debconf variable 'default_environment_locale' on install Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 684134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1076512: marked as done (glibc: FTBFS on hppa - stdlib/tst-swapcontext2 test fails)
Your message dated Mon, 22 Jul 2024 21:21:31 + with message-id and subject line Bug#1076512: fixed in glibc 2.39-5 has caused the Debian Bug report #1076512, regarding glibc: FTBFS on hppa - stdlib/tst-swapcontext2 test fails 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.) -- 1076512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glibc Version: 2.39-4 Severity: normal Tags: ftbfs Dear Maintainer, Build filas here: -- FAIL: stdlib/tst-swapcontext2 original exit status 1 [31mfunc1: func3(&uctx_func1, &uctx_main, str1)[0m [31mfunc3: func4(uocp, ucp, str)[0m [31mfunc4: [31mswapcontext(&uctx_func1, &uctx_main)[0m[0m [35mmain: swapcontext(&uctx_main, &uctx_func2) [0m [34mfunc2: func3(&uctx_func2, &uctx_main, str2)[0m [34mfunc3: func4(uocp, ucp, str)[0m [34mfunc4: [34mswapcontext(&uctx_func2, &uctx_main)[0m[0m [35mmain: swapcontext(&uctx_main, &uctx_func1) [0m [31mfunc4: returning[0m [31mfunc3: returning[0m [31mfunc1: func3(&uctx_func1, &uctx_main, str1)[0m [31mfunc3: func4(uocp, ucp, str)[0m [31mfunc4: [31mswapcontext(&uctx_func1, &uctx_main)[0m[0m [35mmain: swapcontext(&uctx_main, &uctx_func2) [0m [34mfunc4: returning[0m [34mfunc3: returning[0m [34mfunc2: calling longjmp[0m Didn't expect signal from child: got `Aborted' -- +-+ | Encountered regressions that don't match expected failures. | +-+ FAIL: stdlib/tst-swapcontext2 touch /<>/stamp-dir/check_libc CHECK SUMMARY check for check_libc failed Full log is here: https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=hppa&ver=2.39-4&stamp=1721152208&raw=0 dave@atlas:~/gnu/glibc/objdir/stdlib$ ./tst-swapcontext2 func1: func3(&uctx_func1, &uctx_main, str1) func3: func4(uocp, ucp, str) func4: swapcontext(&uctx_func1, &uctx_main) main: swapcontext(&uctx_main, &uctx_func2) func2: func3(&uctx_func2, &uctx_main, str2) func3: func4(uocp, ucp, str) func4: swapcontext(&uctx_func2, &uctx_main) main: swapcontext(&uctx_main, &uctx_func1) func4: returning func3: returning func1: func3(&uctx_func1, &uctx_main, str1) func3: func4(uocp, ucp, str) func4: swapcontext(&uctx_func1, &uctx_main) main: swapcontext(&uctx_main, &uctx_func2) func4: returning func3: returning func2: calling longjmp *** longjmp causes uninitialized stack frame ***: terminated Didn't expect signal from child: got `Aborted' This bug is enabled by the --enable-fortify-source configure option. This needs more research to determine whether this fail is caused by a real problem (hppa is the only architecure where the stack grows upward). I think for now we should xfail the test. Regards, Dave Anglin -- System Information: Debian Release: trixie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 6.9.9-dirty (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.39-5 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 1076...@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: Mon, 22 Jul 2024 22:58:49 +0200 Source: glibc Architecture: source Version: 2.39-5 Distribution: unstable Urgency: medium Maintainer: GNU
Bug#1063515: marked as done (glibc: Please build with -mbranch-protection=standard on arm64 to enable PAC/BTI support)
Your message dated Mon, 22 Jul 2024 21:21:31 +
with message-id
and subject line Bug#1063515: fixed in glibc 2.39-5
has caused the Debian Bug report #1063515,
regarding glibc: Please build with -mbranch-protection=standard on arm64 to
enable PAC/BTI 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.)
--
1063515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.37-15
Severity: wishlist
Tags: patch
User: debian-...@lists.debian.org
Usertags: arm64
Control: block -1 by 1057469
Hi,
As discussed on the debian-glibc mailing list [1], please consider
building glibc on arm64 with -mbranch-protection=standard to enable
support for the PAC/BTI security features in Debian.
The discussion on the mailing list ended up with an agreement on the
attached patch proposed by Aurelien Jarno which works fine in my tests.
In order to properly support PAC/BTI in Debian we need first GCC to
enable support for the feature, and that has not happened yet. For this
reason I'm marking this bug as blocked-by the relevant issue filed
against gcc-12: #1057469.
[1] https://lists.debian.org/debian-glibc/2023/12/msg00022.html
--- glibc-2.37/debian/sysdeps/arm64.mk
+++ glibc-2.37/debian/sysdeps/arm64.mk
@@ -1,2 +1,5 @@
# configuration options for all flavours
extra_config_options = --enable-multi-arch --enable-memory-tagging
+
+CC = $(DEB_HOST_GNU_TYPE)-$(BASE_CC)$(DEB_GCC_VERSION) -mbranch-protection=standard
+CXX = $(DEB_HOST_GNU_TYPE)-$(BASE_CXX)$(DEB_GCC_VERSION) -mbranch-protection=standard
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.39-5
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: Mon, 22 Jul 2024 22:58:49 +0200
Source: glibc
Architecture: source
Version: 2.39-5
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers
Changed-By: Aurelien Jarno
Closes: 1063515 1076512
Changes:
glibc (2.39-5) unstable; urgency=medium
.
[ Samuel Thibault ]
* debian/patches/hurd-i386/git-pthread_self{,.2}.diff: Fix pthread_self()
without libpthread.
.
[ Aurelien Jarno ]
* debian/patches/git-updates.diff: update from upstream stable branch:
- Fixes stdlib/tst-swapcontext2 test on hppa. Closes: #1076512.
* debian/rules.d/tarball.mk: remove useless code.
* debian/sysdeps/arm64.mk: compile with -mbranch-protection=standard on
arm64 to enable PAC/BTI support. Closes: #1063515.
* debian/control.in/main: build-depends on g++13-for-host (>= 13.3.0-3) on
arm64 to ensure PAC/BTI support in GCC.
Checksums-Sha1:
e06c4b84243c276c0773273f805c063ec6d20ded 7550 glibc_2.39-5.dsc
a0a254d55bd1af93aaf68596babe5e3ba6eb0cea 451712 glibc_2.39-5.debian.tar.xz
1d81324b13aae5a85842135933d282f25ddb035b 10995 glibc_2.39-5_source.buildinfo
Checksums-Sha256:
a4457c0ee747e243d3c303dfa6c3b2319dee158661f53008914ba1fd5efcaf26 7550
glibc_2.39-5.dsc
16fa415e66f58f0a39798993c731362c895aeee791f237d6193dd02f37dbb7ab 451712
glibc_2.39-5.debian.tar.xz
48f7dd4cfe1915727a688aa24810d18bec838e33bd0918272adea7a35f3e646b 10995
glibc_2.39-5_source.buildinfo
Files:
3a5abec6dc04f2c68a0355c0599bf6db 7550 libs required glibc_2.39-5.dsc
0fb3b514346624eb8d34b86c79949a9c 451712 libs required
glibc_2.39-5.debian.tar.xz
eb032a22da7cfd5795bed0c3fea07c96 10995 libs required
glibc_2.39-5_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmaeyLUACgkQE4jA+Jno
M2vPsA//bLlRA9YgEjonVi5QCTnbizCnIDn3yBV0zywUVF6Q5BZjyWFN6vnshnb4
03y6kUUzylBWHu/87j4DmB/GH7yP5Vp9TtpLlEiXqKdqzGB0all5vS/iBuWGkA0b
KGK+dZ/0rsP79kr24Yya9qgF4FhGvUWkK8wGXwYEZpcHShE0D2j5dA7koGCbWFaj
atYYTWr2b8s6sfuTq6eDuhMI8vZqvnXwf+5Ens45YfyihVBD0nTmhgglGK5I5tMQ
Q7zWZ3d7u/0NRMdxAghAFZTzQZw+cBictabSpaw0utE6D5JYkdbp2MlxlJ67/Cmq
YArnsoV8R9NXCBP3AuM
Processed: Bug#1063515 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1063515 [src:glibc] glibc: Please build with -mbranch-protection=standard on arm64 to enable PAC/BTI support Added tag(s) pending. -- 1063515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1063515 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1063515 [src:glibc] glibc: Please build with -mbranch-protection=standard on arm64 to enable PAC/BTI support Ignoring request to alter tags of bug #1063515 to the same tags previously set -- 1063515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071172: marked as done (libc6-dev omits the bits directory)
Your message dated Sun, 21 Jul 2024 18:50:15 +0200 with message-id and subject line Re: Bug#1071172: libc6-dev omits the bits directory has caused the Debian Bug report #1071172, regarding libc6-dev omits the bits directory 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.) -- 1071172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package:libc6-dev version: 2.36 Libc6 omits thr ‘bits’ directory, rendering glibc inoperable after sucessfull apt-get install libc6 libc6-dev : When compiling gcc, the process halts at : In file included from ../.././libgcc/../gcc/tsystem.h:95, from ../.././libgcc/libgcc2.c:27: /usr/include/stdio.h:27:10: fatal error: bits/libc-header-start.h: No such file or directory 27 | #include | ^~ compilation terminated. make[2]: *** [Makefile:508: _muldi3.o] Error 1 make[2]: Leaving directory '/home/joris/src/gcc-14.1.0/aarch64-unknown-linux-gnu/libgcc' make[1]: *** [Makefile:14517: all-target-libgcc] Error 2 make[1]: Leaving directory '/home/joris/src/gcc-14.1.0' make: *** [Makefile:1050: all] Error 2 --- End Message --- --- Begin Message --- On 2024-06-01 22:14, Aurelien Jarno wrote: > Hi, > > On 2024-05-15 19:10, Aurelien Jarno wrote: > > Hi, > > > > On 2024-05-15 22:10, Joris van der Geer wrote: > > > package:libc6-dev > > > version: 2.36 > > > > Please provide a more accurate version than this. In the rest of this > > email i will therefore consider the latest glibc version, in sid, ie > > 2.38-11: > > > > > Libc6 omits thr ‘bits’ directory, rendering glibc inoperable > > > > The bits directory is not omitted, it is provided in > > /usr/include/aarch64-linux-gnu following the multiarch path convention. > > > > > after sucessfull apt-get install libc6 libc6-dev : > > > > > > When compiling gcc, the process halts at : > > > > > > In file included from ../.././libgcc/../gcc/tsystem.h:95, > > > from ../.././libgcc/libgcc2.c:27: > > > /usr/include/stdio.h:27:10: fatal error: bits/libc-header-start.h: No > > > such file or directory > > >27 | #include > > > | ^~ > > > compilation terminated. > > > make[2]: *** [Makefile:508: _muldi3.o] Error 1 > > > make[2]: Leaving directory > > > '/home/joris/src/gcc-14.1.0/aarch64-unknown-linux-gnu/libgcc' > > > make[1]: *** [Makefile:14517: all-target-libgcc] Error 2 > > > make[1]: Leaving directory '/home/joris/src/gcc-14.1.0' > > > make: *** [Makefile:1050: all] Error 2 > > > > I guess you are building gcc from source. For using the multiarch path > > convention, you should configure it with --enable-multiarch. > > Any news on that, can we close the bug? > Closing it now, feel free to reopen it if you wan to provide more details. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net--- End Message ---
Processed: Bug#1076512 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1076512 [src:glibc] glibc: FTBFS on hppa - stdlib/tst-swapcontext2 test fails Added tag(s) pending. -- 1076512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1076385: marked as done (tzdata: Wrong time conversion between IST and CEST timezone, using /usr/bin/date.)
Your message dated Tue, 16 Jul 2024 18:59:02 +0200 with message-id and subject line Re: Bug#1076385: tzdata: Wrong time conversion between IST and CEST timezone, using /usr/bin/date. has caused the Debian Bug report #1076385, regarding tzdata: Wrong time conversion between IST and CEST timezone, using /usr/bin/date. 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.) -- 1076385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tzdata Version: 2024a-0+deb12u1 Severity: normal Tags: upstream l10n Package: coreutils Version: 9.1-1, 9.4-3.1 Hello, I noticed that thew `date -d ...` utility converts time between EST and CEST timezone in wrong way. The time is shifted by 1 hour later: # cat /etc/timezone Europe/Prague # date -d '7:00AM EST' Po 15. července 2024, 14:00:00 CEST Env. LANG and LC_* does not change result, just not localised: # date -d '07:00 EST' Mon Jul 15 14:00:00 CEST 2024 The expected time is 13:00 CEST. The problem is observed across all available versions of tzdata or coreutils in actual Debian releases (tzdata 2024a-4 too). I am not sure, if a bug sits in tzdata or inside the date from coreutils, so I attached details about coreutils too... Thank you and have a nice day, Michal Heppler -- System Information: Debian Release: 12.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-16-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.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 Versions of packages tzdata depends on: ii debconf [debconf-2.0] 1.5.82 tzdata recommends no packages. tzdata suggests no packages. -- debconf information: tzdata/Zones/Antarctica: * tzdata/Zones/Etc: UTC tzdata/Zones/Australia: tzdata/Zones/SystemV: tzdata/Zones/US: tzdata/Zones/Pacific: tzdata/Zones/Indian: * tzdata/Zones/Europe: Prague * tzdata/Areas: Europe tzdata/Zones/Asia: tzdata/Zones/America: tzdata/Zones/Arctic: tzdata/Zones/Africa: tzdata/Zones/Atlantic: --- End Message --- --- Begin Message --- Hi, On 2024-07-16 15:20, Michal Heppler wrote: > Hi, > > I opened a discussion with colleague again, based on your answer. And > result is - he think that he is in EST timezone, but in real, it is EDT > timezone now (he is in Toronto). > > And in the online results it is correct too: > - https://duckduckgo.com/?q=convert+EST+time+to+CEST&t=ffab&ia=web > > It is just hidden... Between what I asked for and what wanted to know. > > So, it looks tzdata are correct and I got perfectly correct answer to my > wrong question... > > Thank you, you can close this ticket with peace in mind... Thanks for your feedback, closing the bug. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net--- End Message ---
Processed: Re: Bug#1076217: locales,gosa-dev: install program with same name (update-locale)
Processing control commands: > reassign -1 gosa-dev Bug #1076217 [locales,gosa-dev] locales,gosa-dev: install program with same name (update-locale) Bug reassigned from package 'locales,gosa-dev' to 'gosa-dev'. Ignoring request to alter found versions of bug #1076217 to the same values previously set Ignoring request to alter fixed versions of bug #1076217 to the same values previously set -- 1076217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: locales,gosa-dev: install program with same name (update-locale)
Processing control commands: > block 1075856 by -1 Bug #1075856 [debian-policy] Clarify filename conflicts for programs 1075856 was blocked by: 1076215 1076216 1075856 was not blocking any bugs. Added blocking bug(s) of 1075856: 1076217 -- 1075856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075856 1076217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1063515 by 1055711
Processing commands for cont...@bugs.debian.org: > unblock 1063515 by 1057469 Bug #1063515 [src:glibc] glibc: Please build with -mbranch-protection=standard on arm64 to enable PAC/BTI support 1063515 was blocked by: 1057469 1063515 was not blocking any bugs. Removed blocking bug(s) of 1063515: 1057469 > block 1063515 by 1055711 Bug #1063515 [src:glibc] glibc: Please build with -mbranch-protection=standard on arm64 to enable PAC/BTI support 1063515 was not blocked by any bugs. 1063515 was not blocking any bugs. Added blocking bug(s) of 1063515: 1055711 > thanks Stopping processing here. Please contact me if you need assistance. -- 1063515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074607: marked as done (Error: Could not restart systemd, systemd binary not working)
Your message dated Thu, 04 Jul 2024 20:51:14 + with message-id and subject line Bug#1074607: fixed in glibc 2.38-14 has caused the Debian Bug report #1074607, regarding Error: Could not restart systemd, systemd binary not working 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.) -- 1074607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6 Version: 2.38-13 Severity: normal Seen this scary message on a few upgrades. It seems that the postinst tries to run "systemd --help", but systemd no longer provides a systemd command. ii systemd256.1-2 amd64system and service manager -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.8.12-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libc6 depends on: ii libgcc-s1 14.1.0-3 Versions of packages libc6 recommends: ii libidn2-0 2.3.7-2 Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.86 pn glibc-doc ii libc-l10n 2.38-13 pn libnss-nis pn libnss-nisplus ii locales2.38-13 -- debconf information excluded -- see shy jo signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.38-14 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 1074...@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: Thu, 04 Jul 2024 21:53:20 +0200 Source: glibc Architecture: source Version: 2.38-14 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1074368 1074607 Changes: glibc (2.38-14) unstable; urgency=medium . [ Aurelien Jarno ] * debian/debhelper.in/libc.postinst: drop code to restart init systems. Closes: #1074607. * debian/control.in/libc: add breaks against systemd and sysvinit versions not using the libc-upgrade trigger. * debian/control.in/libc: add breaks against base-files version not providing /usr-merge aliasing symlinks. Closes: #1074368. Checksums-Sha1: 6905c4e7b067f7da19309f5bad96347bf2d3889c 7535 glibc_2.38-14.dsc 7e24167dc1f31a23a21cf76e37f30bb12d5b9121 431776 glibc_2.38-14.debian.tar.xz edfcabf946fe42778861e9d7c47eed1dcb69cd95 9616 glibc_2.38-14_source.buildinfo Checksums-Sha256: a702ffd739e9acdbeb5e1e1a8fdf703e3983520eed79b19f927e3af4057d7eaa 7535 glibc_2.38-14.dsc 61332c6c084e950aa150b4208e44e11ff64baffc70a7b7cb6c53715633388364 431776 glibc_2.38-14.debian.tar.xz 12038abd2db2637a350c0c008a0bfe2d23e8bbbe38760272bc5d068503698b8c 9616 glibc_2.38-14_source.buildinfo Files: c59863c24c33105c63258120b42d9afb 7535 libs required glibc_2.38-14.dsc 0b20104e2d5d69aee364bc2635c82b1b 431776 libs required glibc_2.38-14.debian.tar.xz a2a4183ac46bb3714328e422082099c0 9616 libs required glibc_2.38-14_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmaG/wcACgkQE4jA+Jno M2u5hw/7BVHg+mzpCr/zqADvcnXePPTPVKQVS58uw0Z6PVtE7AD6wZ0kfNLjzKYu FQ6dWami+wWHiee0RjuThI1x37/Hbe0e8SeZWIqEhuv+Umj0pDl+zlRWsrvxVMG+ yfUE8IrW+lo2LE9g6IL4H+BMT/QCTbd/ej24ohtUg5GaWdtm3/C7Pm6v7y3ohWX1 e2UuGPdF5gAWTZXeiznI/xuXjWOrXUYbVCTCGrqJgbHePpjZa58C85c69dxrBp0x brEGOjIgx8whf5WCd2ElWmhlIFyPusgncduYMvZCzzHrMZ3D3nLcKoPVUnO7ce6S PH1KwSTz8R1WntCGieyEr2Rmco812uHdOXFIkzdMfZmrapr/lj6DpAqagrqVRueN Z1RUuMFPt1ICyn+62FZpFrh6IdnDqMOhBgyj2W0/1HWwsw1QVmcjAVc7Kx6UU+vj L/DZAu7o02XbpBymq7q6J+Y8BquVApjc8+j8KwTChw5fCQtzgC6i0mLD4uSaP5TC kTfWC/QAo29MmSspvZP+j0Iud
Bug#1074368: marked as done (libc6: libguestfs-test-tool fails on 2.38.13 libc6)
Your message dated Thu, 04 Jul 2024 20:51:14 + with message-id and subject line Bug#1074368: fixed in glibc 2.38-14 has caused the Debian Bug report #1074368, regarding libc6: libguestfs-test-tool fails on 2.38.13 libc6 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.) -- 1074368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6 Version: 2.38-13 Severity: important X-Debbugs-Cc: vishalb...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrading libc6 on testing has caused libguestfs usage. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-41-generic (SMP w/22 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages libc6 depends on: ii libgcc-s1 14-20240330-1 Versions of packages libc6 recommends: ii libidn2-0 2.3.7-2 Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.86 pn glibc-doc pn libc-l10n pn libnss-nis pn libnss-nisplus pn locales -- debconf information excluded --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.38-14 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 1074...@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: Thu, 04 Jul 2024 21:53:20 +0200 Source: glibc Architecture: source Version: 2.38-14 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1074368 1074607 Changes: glibc (2.38-14) unstable; urgency=medium . [ Aurelien Jarno ] * debian/debhelper.in/libc.postinst: drop code to restart init systems. Closes: #1074607. * debian/control.in/libc: add breaks against systemd and sysvinit versions not using the libc-upgrade trigger. * debian/control.in/libc: add breaks against base-files version not providing /usr-merge aliasing symlinks. Closes: #1074368. Checksums-Sha1: 6905c4e7b067f7da19309f5bad96347bf2d3889c 7535 glibc_2.38-14.dsc 7e24167dc1f31a23a21cf76e37f30bb12d5b9121 431776 glibc_2.38-14.debian.tar.xz edfcabf946fe42778861e9d7c47eed1dcb69cd95 9616 glibc_2.38-14_source.buildinfo Checksums-Sha256: a702ffd739e9acdbeb5e1e1a8fdf703e3983520eed79b19f927e3af4057d7eaa 7535 glibc_2.38-14.dsc 61332c6c084e950aa150b4208e44e11ff64baffc70a7b7cb6c53715633388364 431776 glibc_2.38-14.debian.tar.xz 12038abd2db2637a350c0c008a0bfe2d23e8bbbe38760272bc5d068503698b8c 9616 glibc_2.38-14_source.buildinfo Files: c59863c24c33105c63258120b42d9afb 7535 libs required glibc_2.38-14.dsc 0b20104e2d5d69aee364bc2635c82b1b 431776 libs required glibc_2.38-14.debian.tar.xz a2a4183ac46bb3714328e422082099c0 9616 libs required glibc_2.38-14_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmaG/wcACgkQE4jA+Jno M2u5hw/7BVHg+mzpCr/zqADvcnXePPTPVKQVS58uw0Z6PVtE7AD6wZ0kfNLjzKYu FQ6dWami+wWHiee0RjuThI1x37/Hbe0e8SeZWIqEhuv+Umj0pDl+zlRWsrvxVMG+ yfUE8IrW+lo2LE9g6IL4H+BMT/QCTbd/ej24ohtUg5GaWdtm3/C7Pm6v7y3ohWX1 e2UuGPdF5gAWTZXeiznI/xuXjWOrXUYbVCTCGrqJgbHePpjZa58C85c69dxrBp0x brEGOjIgx8whf5WCd2ElWmhlIFyPusgncduYMvZCzzHrMZ3D3nLcKoPVUnO7ce6S PH1KwSTz8R1WntCGieyEr2Rmco812uHdOXFIkzdMfZmrapr/lj6DpAqagrqVRueN Z1RUuMFPt1ICyn+62FZpFrh6IdnDqMOhBgyj2W0/1HWwsw1QVmcjAVc7Kx6UU+vj L/DZAu7o02XbpBymq7q6J+Y8BquVApjc8+j8KwTChw5fCQtzgC6i0mLD4uSaP5TC kTfWC/QAo29MmSspvZP+j0Iudx
Processed: Bug#1074607 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1074607 [libc6] Error: Could not restart systemd, systemd binary not working Ignoring request to alter tags of bug #1074607 to the same tags previously set -- 1074607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1074607 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1074607 [libc6] Error: Could not restart systemd, systemd binary not working Added tag(s) pending. -- 1074607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1074368 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1074368 [libc6] libc6: libguestfs-test-tool fails on 2.38.13 libc6 Added tag(s) pending. -- 1074368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074590: marked as done (libc6-dev: Fails to update)
Your message dated Tue, 2 Jul 2024 22:42:09 +0200 with message-id and subject line Re: Bug#1074590: libc6-dev: Fails to update has caused the Debian Bug report #1074590, regarding libc6-dev: Fails to update 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.) -- 1074590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6-dev Version: 2.28-10+rpt2+rpi1+deb10u2 Severity: normal Dear Maintainer, # apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. -- System Information: Distributor ID: Raspbian Description:Raspbian GNU/Linux 12 (bookworm) Release:12 Codename: bookworm Architecture: armv7l Kernel: Linux 5.10.103-v7+ (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libc6-dev depends on: ii libc-dev-bin2.28-10+rpt2+rpi1+deb10u2 ii libc6 2.28-10+rpt2+rpi1+deb10u2 ii linux-libc-dev 1:1.20230509~buster-1 libc6-dev recommends no packages. Versions of packages libc6-dev suggests: pn glibc-doc ii manpages-dev 6.03-2 -- no debconf information --- End Message --- --- Begin Message --- Hi, On 2024-07-01 13:41, Nigel Horne wrote: > Package: libc6-dev > Version: 2.28-10+rpt2+rpi1+deb10u2 > Severity: normal > > Dear Maintainer, > > # apt dist-upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Error! > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be > installed > E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by > held packages. From a quick look, it seems that you are trying to upgrade directly from buster to bookworm, without passing by bullseye. This is not supported by Debian. Your system is a Raspbian one, I have no idea if such an upgrade is supposed to be supported, in any case you should report the issue there instead. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net--- End Message ---
Processed: Reassign 123999 to glibc-doc package
Processing commands for cont...@bugs.debian.org: > reassign 123999 glibc-doc Bug #123999 [gnulib] [WANTED] obstack_*(3) Bug reassigned from package 'gnulib' to 'glibc-doc'. Ignoring request to alter found versions of bug #123999 to the same values previously set Ignoring request to alter fixed versions of bug #123999 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 123999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=123999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#816833: marked as done ("LD_TRACE_LOADED_OBJECTS=1 LD_WARN=1 LD_BIND_NOW=1 /lib/ld-linux.so.2" segfaults on some Go programs)
Your message dated Sun, 30 Jun 2024 22:17:51 +0200 with message-id and subject line same as #710521 has caused the Debian Bug report #816833, regarding "LD_TRACE_LOADED_OBJECTS=1 LD_WARN=1 LD_BIND_NOW=1 /lib/ld-linux.so.2" segfaults on some Go programs 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.) -- 816833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6 Version: 2.21-9 Control: affects -1 + adequate (This might be the same as #710521...) $ dpkg-query -W minica ratt minica 1.0-1 ratt0.0~git20150816.0.b060319-1 $ LD_TRACE_LOADED_OBJECTS=1 LD_WARN=1 LD_BIND_NOW=1 /lib/ld-linux.so.2 /usr/bin/minica linux-gate.so.1 (0xf7786000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7763000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf75e6000) /lib/ld-linux.so.2 (0x56628000) Segmentation fault $ LD_TRACE_LOADED_OBJECTS=1 LD_WARN=1 LD_BIND_NOW=1 /lib/ld-linux.so.2 /usr/bin/ratt linux-gate.so.1 (0xf773d000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf771a000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf759d000) /lib/ld-linux.so.2 (0x565b) Segmentation fault -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libc6 depends on: ii libgcc1 1:5.3.1-10 Versions of packages libc6 recommends: pn libc6-i686 Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.58 pn glibc-doc pn libc-l10n pn locales -- Jakub Wilk --- End Message --- --- Begin Message --- signature.asc Description: PGP signature --- End Message ---
Processed: notfixed 1061248 in palo/2.25
Processing commands for cont...@bugs.debian.org:
> notfixed 1061248 palo/2.25
Bug #1061248 {Done: Helge Deller } [src:glibc] glibc: DEP17:
move most files but rtld to /usr
No longer marked as fixed in versions palo/2.25.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1061248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1061248: marked as done (glibc: DEP17: move most files but rtld to /usr)
Your message dated Tue, 18 Jun 2024 19:04:43 + with message-id and subject line Bug#1061248: fixed in palo 2.25 has caused the Debian Bug report #1061248, regarding glibc: DEP17: move most files but rtld to /usr 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.) -- 1061248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glibc Version: 2.37-13 Tags: patch User: helm...@debian.org Usertags: dep17m2 Hi Aurelien, thanks for your answers on IRC to my design question. As promised here comes a patch that moves most files in binary packages built from glibc from aliased locations to /usr. This excludes the runtime dynamic linker for native libc packages (i.e. not multilib), because moving it would break filesystem bootstrap unless base-files installs the aliasing symlinks at the same time. That move is a later step and is what I asked for in https://lists.debian.org/20230912181509.ga2588...@subdivi.de. What I'm asking for here is staging the changes to glibc in two phases where the majority of the move happens before that coordinated upload. This patch is that majority move. Regarding the implementation, I asked whether you'd prefer to change slibdir or not and you answered that you'd rather not change it as e.g. Fedora is not changing it either. My first implementation changed slibdir and this second iteration that does not change slibdir is quite a bit simpler. I also asked about how to deal with symbolic links that point at aliased locations. Your answer felt a little inconclusive to me, but fixing them practically is a requirement: During filesystem bootstrap, libc6 needs to briefly operate in an unmerged state (temporarily until that coordinated move) and therefore those symlinks in libc6 cannot rely on the aliasing symlinks having been set up. Hence, I added code for fixing those links before letting dh_link perform their canonicalization according to Debian policy. In practice, this turns most of the links (but runtime dynamic linker links) into relative ones. We may be able to drop this after the coordinated move if you disagree about the approach taken here, but I think it is best to accept this temporarily at least. Are you also comfortable with keeping this link fixing permanently? The change at hand requires significant testing, because there is a significant risk of breaking stuff and doing so is very annoying to many developers. I've performed the following steps: * Reviewed the file lists of created .debs to see that all files but runtime dynamic linkers have moved out of aliased locations. * Reviewed all symbolic links in created .debs. * Ran piuparts. It complained about /lib32 and /libx32 not being cleaned up after removal of multilib packages. I think this is vaguely fine. Do you agree? If not, I can add postrm code that checks whether /usr/lib32 and /usr/libx32 vanished and removes the aliasing links in those cases. * I set up a custom reprepro repository with these packages and ran a number of filesystem bootstraps: * debootstrap * debootstrap --variant=minbase * cdebootstrap --flavour=standard * cdebootstrap --flavour=minimal * mmdebstrap --variant=debootstrap * mmdebstrap --variant=minbase * mmdebstrap --variant=apt All of these bootstraps do not contain any glibc-owned files in aliased locations with the exception of the runtime dynamic linker. * I compiled a minimal C program in chroot both with -m32 and without and verified that the embedded location of the runtime dynamic linker still is aliased and that the resulting program still runs. * In addition to testing on amd64, I performed a i386 build. I note that my builds are nocheck builds, due to failing tests unrelated to my changes. I did not bother figuring out what local configuration causes those the test failures. Do you miss any testing here? Helmut diff --minimal -Nru glibc-2.37/debian/changelog glibc-2.37/debian/changelog --- glibc-2.37/debian/changelog 2023-12-03 14:23:52.0 +0100 +++ glibc-2.37/debian/changelog 2024-01-19 15:56:06.0 +0100 @@ -1,3 +1,10 @@ +glibc (2.37-13.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * DEP17: Move most files but rtld to /usr. (Closes: #-1) + + -- Helmut Grohne Fri, 19 Jan 2024 15:56:06 +0100 + glibc (2.37-13) unstable; urgency=medium [ Aurelien Jarno ] diff --minimal -Nru glibc-2.37/debian/debhelper.in/libc-alt.install glibc-2.37/debian/debhelper.in/libc-alt.install -
Processed (with 1 error): reassign 1072748 to src:upower, reassign 1072947 to src:dropbear ..., tagging 1072532 ...
ersions gcc-14/14-20240429-1.
> affects 1064426 + src:evolver
Bug #1064426 {Done: Matthias Klose } [src:gcc-14] evolver
fails the last two autopkg tests with glibc 2.39 on amd64
Added indication that 1064426 affects src:evolver
> reassign 1068380 src:debci
Bug #1068380 {Done: Antonio Terceiro } [autopkgtest]
autopkgtest: new --lxcpath option doesn't seem to work on ci.d.n workers
Bug reassigned from package 'autopkgtest' to 'src:debci'.
No longer marked as found in versions autopkgtest/5.34.
No longer marked as fixed in versions debci/3.10.
> fixed 1068380 3.10
Bug #1068380 {Done: Antonio Terceiro } [src:debci]
autopkgtest: new --lxcpath option doesn't seem to work on ci.d.n workers
Marked as fixed in versions debci/3.10.
> reassign 1056992 src:freerdp3
Bug #1056992 {Done: Jeremy Bícha } [src:freerdp2] freerdp2:
Please package version 3
Bug reassigned from package 'src:freerdp2' to 'src:freerdp3'.
No longer marked as found in versions freerdp2/2.11.2+dfsg1-1.
No longer marked as fixed in versions freerdp3/3.3.0+dfsg1-1 and
freerdp3/3.5.0+dfsg1-1.
> fixed 1056992 3.3.0+dfsg1-1
Bug #1056992 {Done: Jeremy Bícha } [src:freerdp3] freerdp2:
Please package version 3
Marked as fixed in versions freerdp3/3.3.0+dfsg1-1.
> fixed 1056992 3.5.0+dfsg1-1
Bug #1056992 {Done: Jeremy Bícha } [src:freerdp3] freerdp2:
Please package version 3
Marked as fixed in versions freerdp3/3.5.0+dfsg1-1.
> fixed 1068188 2.38-7
Bug #1068188 {Done: Aurelien Jarno } [glibc-doc]
pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1
Marked as fixed in versions glibc/2.38-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056496
1056992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056992
1064426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064426
1064480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064480
1068188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068188
1068380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068380
1069052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069052
1070692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070692
1072532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072532
1072682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072682
1072690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072690
1072748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072748
1072806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072806
1072807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072807
1072858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072858
1072913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072913
1072947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072947
898536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1061248: marked as done (glibc: DEP17: move most files but rtld to /usr)
Your message dated Thu, 06 Jun 2024 08:38:15 + with message-id and subject line Bug#1061248: fixed in glibc 2.39-3.1 has caused the Debian Bug report #1061248, regarding glibc: DEP17: move most files but rtld to /usr 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.) -- 1061248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glibc Version: 2.37-13 Tags: patch User: helm...@debian.org Usertags: dep17m2 Hi Aurelien, thanks for your answers on IRC to my design question. As promised here comes a patch that moves most files in binary packages built from glibc from aliased locations to /usr. This excludes the runtime dynamic linker for native libc packages (i.e. not multilib), because moving it would break filesystem bootstrap unless base-files installs the aliasing symlinks at the same time. That move is a later step and is what I asked for in https://lists.debian.org/20230912181509.ga2588...@subdivi.de. What I'm asking for here is staging the changes to glibc in two phases where the majority of the move happens before that coordinated upload. This patch is that majority move. Regarding the implementation, I asked whether you'd prefer to change slibdir or not and you answered that you'd rather not change it as e.g. Fedora is not changing it either. My first implementation changed slibdir and this second iteration that does not change slibdir is quite a bit simpler. I also asked about how to deal with symbolic links that point at aliased locations. Your answer felt a little inconclusive to me, but fixing them practically is a requirement: During filesystem bootstrap, libc6 needs to briefly operate in an unmerged state (temporarily until that coordinated move) and therefore those symlinks in libc6 cannot rely on the aliasing symlinks having been set up. Hence, I added code for fixing those links before letting dh_link perform their canonicalization according to Debian policy. In practice, this turns most of the links (but runtime dynamic linker links) into relative ones. We may be able to drop this after the coordinated move if you disagree about the approach taken here, but I think it is best to accept this temporarily at least. Are you also comfortable with keeping this link fixing permanently? The change at hand requires significant testing, because there is a significant risk of breaking stuff and doing so is very annoying to many developers. I've performed the following steps: * Reviewed the file lists of created .debs to see that all files but runtime dynamic linkers have moved out of aliased locations. * Reviewed all symbolic links in created .debs. * Ran piuparts. It complained about /lib32 and /libx32 not being cleaned up after removal of multilib packages. I think this is vaguely fine. Do you agree? If not, I can add postrm code that checks whether /usr/lib32 and /usr/libx32 vanished and removes the aliasing links in those cases. * I set up a custom reprepro repository with these packages and ran a number of filesystem bootstraps: * debootstrap * debootstrap --variant=minbase * cdebootstrap --flavour=standard * cdebootstrap --flavour=minimal * mmdebstrap --variant=debootstrap * mmdebstrap --variant=minbase * mmdebstrap --variant=apt All of these bootstraps do not contain any glibc-owned files in aliased locations with the exception of the runtime dynamic linker. * I compiled a minimal C program in chroot both with -m32 and without and verified that the embedded location of the runtime dynamic linker still is aliased and that the resulting program still runs. * In addition to testing on amd64, I performed a i386 build. I note that my builds are nocheck builds, due to failing tests unrelated to my changes. I did not bother figuring out what local configuration causes those the test failures. Do you miss any testing here? Helmut diff --minimal -Nru glibc-2.37/debian/changelog glibc-2.37/debian/changelog --- glibc-2.37/debian/changelog 2023-12-03 14:23:52.0 +0100 +++ glibc-2.37/debian/changelog 2024-01-19 15:56:06.0 +0100 @@ -1,3 +1,10 @@ +glibc (2.37-13.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * DEP17: Move most files but rtld to /usr. (Closes: #-1) + + -- Helmut Grohne Fri, 19 Jan 2024 15:56:06 +0100 + glibc (2.37-13) unstable; urgency=medium [ Aurelien Jarno ] diff --minimal -Nru glibc-2.37/debian/debhelper.in/libc-alt.install glibc-2.37/debian/debhelper.in/libc-alt.in
Bug#1061248: marked as done (glibc: DEP17: move most files but rtld to /usr)
Your message dated Thu, 06 Jun 2024 07:36:03 + with message-id and subject line Bug#1061248: fixed in glibc 2.38-12.1 has caused the Debian Bug report #1061248, regarding glibc: DEP17: move most files but rtld to /usr 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.) -- 1061248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glibc Version: 2.37-13 Tags: patch User: helm...@debian.org Usertags: dep17m2 Hi Aurelien, thanks for your answers on IRC to my design question. As promised here comes a patch that moves most files in binary packages built from glibc from aliased locations to /usr. This excludes the runtime dynamic linker for native libc packages (i.e. not multilib), because moving it would break filesystem bootstrap unless base-files installs the aliasing symlinks at the same time. That move is a later step and is what I asked for in https://lists.debian.org/20230912181509.ga2588...@subdivi.de. What I'm asking for here is staging the changes to glibc in two phases where the majority of the move happens before that coordinated upload. This patch is that majority move. Regarding the implementation, I asked whether you'd prefer to change slibdir or not and you answered that you'd rather not change it as e.g. Fedora is not changing it either. My first implementation changed slibdir and this second iteration that does not change slibdir is quite a bit simpler. I also asked about how to deal with symbolic links that point at aliased locations. Your answer felt a little inconclusive to me, but fixing them practically is a requirement: During filesystem bootstrap, libc6 needs to briefly operate in an unmerged state (temporarily until that coordinated move) and therefore those symlinks in libc6 cannot rely on the aliasing symlinks having been set up. Hence, I added code for fixing those links before letting dh_link perform their canonicalization according to Debian policy. In practice, this turns most of the links (but runtime dynamic linker links) into relative ones. We may be able to drop this after the coordinated move if you disagree about the approach taken here, but I think it is best to accept this temporarily at least. Are you also comfortable with keeping this link fixing permanently? The change at hand requires significant testing, because there is a significant risk of breaking stuff and doing so is very annoying to many developers. I've performed the following steps: * Reviewed the file lists of created .debs to see that all files but runtime dynamic linkers have moved out of aliased locations. * Reviewed all symbolic links in created .debs. * Ran piuparts. It complained about /lib32 and /libx32 not being cleaned up after removal of multilib packages. I think this is vaguely fine. Do you agree? If not, I can add postrm code that checks whether /usr/lib32 and /usr/libx32 vanished and removes the aliasing links in those cases. * I set up a custom reprepro repository with these packages and ran a number of filesystem bootstraps: * debootstrap * debootstrap --variant=minbase * cdebootstrap --flavour=standard * cdebootstrap --flavour=minimal * mmdebstrap --variant=debootstrap * mmdebstrap --variant=minbase * mmdebstrap --variant=apt All of these bootstraps do not contain any glibc-owned files in aliased locations with the exception of the runtime dynamic linker. * I compiled a minimal C program in chroot both with -m32 and without and verified that the embedded location of the runtime dynamic linker still is aliased and that the resulting program still runs. * In addition to testing on amd64, I performed a i386 build. I note that my builds are nocheck builds, due to failing tests unrelated to my changes. I did not bother figuring out what local configuration causes those the test failures. Do you miss any testing here? Helmut diff --minimal -Nru glibc-2.37/debian/changelog glibc-2.37/debian/changelog --- glibc-2.37/debian/changelog 2023-12-03 14:23:52.0 +0100 +++ glibc-2.37/debian/changelog 2024-01-19 15:56:06.0 +0100 @@ -1,3 +1,10 @@ +glibc (2.37-13.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * DEP17: Move most files but rtld to /usr. (Closes: #-1) + + -- Helmut Grohne Fri, 19 Jan 2024 15:56:06 +0100 + glibc (2.37-13) unstable; urgency=medium [ Aurelien Jarno ] diff --minimal -Nru glibc-2.37/debian/debhelper.in/libc-alt.install glibc-2.37/debian/debhelper.in/libc-alt.in
Bug#1071462: marked as done (installing/upgrading libc6 does not work in sbuild when systemd is installed as ischroot declines)
Your message dated Sat, 01 Jun 2024 21:35:59 +
with message-id
and subject line Bug#1071462: fixed in glibc 2.38-12
has caused the Debian Bug report #1071462,
regarding installing/upgrading libc6 does not work in sbuild when systemd is
installed as ischroot declines
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.)
--
1071462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sbuild,debianutils,libc6,systemd-sysv
Severity: important
Hello lots of maintainers,
I am faced with a very crazy interaction bug. Roughly speaking, when you
use sbuild to build a package and your build-depends happen to include
systemd-sysv and you happen to install (cross building) or upgrade
libc6, installing build-depends reliably fails. Since upgrading libc6 is
a thing, I guess that this now affects buildds and is why I file this at
important severity. Regenerating buildd chroots, will "heal" buildds, so
it is self-recovering there.
Without further ado, let's dive into the details. The issue is
reproducible using mmdebstrap:
mmdebstrap unstable --verbose --architectures amd64,arm64 --variant=apt
/dev/null --include=systemd-sysv,libc6:arm64 --essential-hook='ln -sf
/bin/false $1/usr/bin/ischroot'
This is using a cross build setting, because libc6 is installed early
during bootstrap and reproducing the bug takes configuring libc6 after
systemd-sysv has been unpacked. So I simply install a foreign libc6 and
apt happens to configure it late enough in my tests. So we now look into
libc6.postinst. We take the "$1" = "configure" branch. We eventually run
into:
| # Restart init. Currently handles chroots, systemd and upstart, and
| # assumes anything else is going to not fail at behaving like
| # sysvinit:
| TELINIT=yes
| if ischroot 2>/dev/null; then
| # Don't bother trying to re-exec init from a chroot:
| TELINIT=no
I note that mmdebstrap creates a number of namespaces and then
externally runs apt. If I understand things correctly, it also runs an
external dpkg --root ... without --force-scripts-chrootless. Hence dpkg
performs a chroot for every maintainer script and ischroot correctly
detects this, so we would be setting TELINIT=no if I were not replacing
it in the --essential-hook.
In sbuild, the namespace setup is different. apt is entirely run inside
the namespace. ischroot compares /proc/1/mountinfo to
/proc/self/mountinfo. If both are readable and equal, it concludes that
we're not in a chroot. If they differ, it concludes that we are in a
chroot. For mmdebstrap, pid 1 happens to be a mmdebstrap process in the
initial namespace and the ischroot process sees fewer mounts. Hence it
concludes success there. For sbuild, pid 1 is a runuser process already
running chrooted. Hence the mountinfo files equal and ischroot concludes
that we are not running in a chroot.
| elif [ -n "${DPKG_ROOT:-}" ]; then
| # Do not re-exec init if we are operating on a chroot from outside:
| TELINIT=no
In neither case DPKG_ROOT is non-empty.
| elif [ -d /run/systemd/system ]; then
| # Restart systemd on upgrade, but carefully.
| # The restart is wanted because of LP: #1942276 and Bug: #993821
| # The care is needed because of https://bugs.debian.org/753725
| # (if systemd --help fails the system might still be quite broken but
| # that seems better than the kernel panic that results if systemd
| # cannot reexec itself).
| TELINIT=no
In neither case /run/systemd/system exists.
| if systemd --help >/dev/null 2>/dev/null; then
| systemctl daemon-reexec
| else
| echo "Error: Could not restart systemd, systemd binary not
working" >&2
| fi
| fi
| if [ "$TELINIT" = "yes" ]; then
| telinit u 2>/dev/null || true ; sleep 1
| fi
And finally we run telinit u when running inside sbuild or faking
ischroot in mmdebstrap. Running telinit u doesn't go well. This actually
has been a known problem with different symptoms recently. Earlier,
cross build nodes would get stuck in libc6.postinst hanging in telinit
forever. The reason was that telinit was re-executing itself over and
over again attempting to forward to another init system but always
returning back to itself. This has been fixed by Luca Boccassi:
https://github.com/systemd/systemd/pull/31251 and #1063147
telin
Bug#1071549: marked as done (gencat.1: some remarks and editorial changes for this man page)
Your message dated Sat, 01 Jun 2024 21:35:59 +
with message-id
and subject line Bug#1071549: fixed in glibc 2.38-12
has caused the Debian Bug report #1071549,
regarding gencat.1: some remarks and editorial changes for this man page
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.)
--
1071549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc-dev-bin
Version: 2.38-11
Severity: minor
Tags: patch
Dear Maintainer,
here are some notes and editorial fixes for the manual.
The patch is in the attachment.
-.-
The difference between the formatted outputs can be seen with:
nroff -man >
nroff -man >
diff -u
and for groff, using
"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -man -Z - "
instead of "nroff -man"
Add the option "-t", if the file contains a table.
Read the output of "diff -u" with "less -R" or similar.
-.-.
If "man" (man-db) is used to check the manual for warnings,
the following must be set:
The option "-warnings=w"
The environmental variable:
export MAN_KEEP_STDERR=yes (or any non-empty value)
or
(produce only warnings):
export MANROFFOPT="-ww -z"
export MAN_KEEP_STDERR=yes (or any non-empty value)
-.-.
Output from "mandoc -T lint gencat.1": (possibly shortened list)
mandoc: gencat.1:97:14: STYLE: whitespace at end of input line
mandoc: gencat.1:99:19: STYLE: whitespace at end of input line
mandoc: gencat.1:214:2: WARNING: skipping paragraph macro: PP empty
-.-.
Remove space characters at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".
97:.\" TH Title
99:.\" Sh Subsection
-.-.
Mark a full stop (.) and the exclamation mark (!) with "\&",
if it does not mean an end of a sentence.
This is a preventive action,
the paragraph could be reshaped, e.g., after changes.
When typing, one does not always notice when the line wraps after the
period.
There are too many examples of input lines in manual pages,
that end with an abbreviation point.
This marking is robust, and independent of the position on the line.
It corresponds to "\ " in TeX, and to "@:" in Texinfo.
208:gencat [OPTION...] -o OUTPUT-FILE [INPUT-FILE]...
-.-.
Change -- in x--y to \(em (em-dash), or, if an
option, to \-\-
216:\fB-H\fR, \fB--header\fR \fINAME\fR
219:\fB--new\fR
222:\fB-o\fR, \fB--output\fR \fINAME\fR
-.-.
Add a backslash, if it is missing after \{ at the end of a line.
104:.if \nF \{
-.-.
Wrong distance between sentences.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
212:correctly formed input files. Additionally some extension are implemented
-.-.
Do not use "\s0" in a string definition but an absolute number,
as the size of the string could be changed.
Then a situation of "\s+X...\s+Y...\s0...\s0" could emerge.
Type size changes have an effect in "groff", but not in "nroff".
115:.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
169:.ds v
\\k:\h'-(\\n(.wu*9/10-\*(#H)'\v'-\*(#V'\*(#[\s-4v\s0\v'\*(#V'\h'|\\n:u'\*(#]
172:.ds 3 \*(#[\v'.2m'\s-2\&3\s0\v'-.2m'\*(#]
-.-.
Add a zero (0) in front of a decimal fraction that begins with a period
(.)
30:.if t .sp .5v
131:. ds #V .8m
132:. ds #F .3m
138:. ds #V .6m
-.-.
Output from "test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -t -w w -z
-rCHECKSTYLE=0":
Bad use of \s0 in a string definition, the string could be resized.
115:.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-
Bug#1071084: marked as done (locales: update-locale hides error information when invoking 'locale charmap')
Your message dated Sat, 01 Jun 2024 21:35:59 +
with message-id
and subject line Bug#1071084: fixed in glibc 2.38-12
has caused the Debian Bug report #1071084,
regarding locales: update-locale hides error information when invoking 'locale
charmap'
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.)
--
1071084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: locales
Version: 2.38-10
Severity: normal
Tags: newcomer, patch
The perl script update-local internally invokes 'locale charmap' to perform
additional checks.
However if this call fails for some reason, update-locale always only prints
"Error: invalid locale settings: LANG=" which can be very misleading when
the root-cause is actually different.
I.e. sample output of "sudo /usr/sbin/update-locale LANG=de_AT.UTF-8" on Debian
Trixie:
*** update-locale: Error: invalid locale settings: LANG=de_AT.UTF-8
After applying the following patch:
==
--- /usr/update-locale 2024-05-13 23:42:46.584127893 +0200
+++ /usr/sbin/update-locale 2024-05-13 23:40:25.160121142 +0200
@@ -88,7 +88,7 @@
{
# Check that this locale does exist
my $charset = `LANG= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE=
LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE=
LC_MEASUREMENT= LC_IDENTIFICATION= LC_ALL= $env locale charmap 2>&1`;
- die "*** $progname: Error: invalid locale settings: $env\n"
+ die "*** $progname: Error: invalid locale settings:
$env\n\n--$charset--\n"
if ($charset =~ m/Cannot set/);
# If LANGUAGE is set, its first value must be compatible with
LC_MESSAGES
if (defined $arg{LANGUAGE})
==
The output contains the actual information why the call to "locale chaarmap"
failed, thus making it possible to investigate why the call actually failed:
===
*** update-locale: Error: invalid locale settings: LANG=de_AT.UTF-8
--locale: Cannot set LC_CTYPE to default locale: No such file or
directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968
--
===
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-2-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set
LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages locales depends on:
ii debconf [debconf-2.0] 1.5.86
ii libc-bin 2.38-10
ii libc-l10n 2.38-10
locales recommends no packages.
locales suggests no packages.
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_TIME = "de_AT.UTF-8",
LC_MONETARY = "de_AT.UTF-8",
LC_CTYPE = "C.UTF-8",
LC_ADDRESS = "de_AT.UTF-8",
LC_TELEPHONE = "de_AT.UTF-8",
LC_NAME = "de_AT.UTF-8",
LC_MEASUREMENT = "de_AT.UTF-8",
LC_IDENTIFICATION = "de_AT.UTF-8",
LC_NUMERIC = "de_AT.UTF-8",
LC_PAPER = "de_AT.UTF-8",
LANG = "de_AT.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locales/locales_to_be_generated:
locales/default_environment_locale: None
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.38-12
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 1071...@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)
Processed: Bug#1071462 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1071462 [sbuild,debianutils,libc6,systemd-sysv] installing/upgrading libc6 does not work in sbuild when systemd is installed as ischroot declines Ignoring request to alter tags of bug #1071462 to the same tags previously set -- 1071462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1071549 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1071549 [libc-dev-bin] gencat.1: some remarks and editorial changes for this man page Ignoring request to alter tags of bug #1071549 to the same tags previously set -- 1071549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1071084 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1071084 [locales] locales: update-locale hides error information when invoking 'locale charmap' Ignoring request to alter tags of bug #1071084 to the same tags previously set -- 1071084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1071549 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1071549 [libc-dev-bin] gencat.1: some remarks and editorial changes for this man page Added tag(s) pending. -- 1071549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1071084 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1071084 [locales] locales: update-locale hides error information when invoking 'locale charmap' Added tag(s) pending. -- 1071084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1071462 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1071462 [sbuild,debianutils,libc6,systemd-sysv] installing/upgrading libc6 does not work in sbuild when systemd is installed as ischroot declines Added tag(s) pending. -- 1071462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: raise remaining usrmerge normal bugs to important
ug 1063458 to the same value. > severity 1063455 important Bug #1063455 [open-infrastructure-compute-tools] open-infrastructure-compute-tools: move files to /usr for DEP17 Ignoring request to change severity of Bug 1063455 to the same value. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054013 1054084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054084 1054086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054086 1054088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054088 1054089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054089 1054090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054090 1054093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054093 1054191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054191 1055514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055514 1061238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061238 1061245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061245 1061248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061248 1061259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061259 1061332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061332 1061337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061337 1061342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061342 1061352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061352 1061353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061353 1061489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061489 1061491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061491 1061527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061527 1061702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061702 1061849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061849 1061851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061851 1061855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061855 1061865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061865 1063455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063455 1063458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063458 1063552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063552 1063571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063571 1063572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063572 1063620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063620 1063622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063622 1063692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063692 1063693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063693 1063694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063694 1063696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063696 1063699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063699 1063876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063876 1063878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063878 1064045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064045 1064046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064046 1064125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064125 1064126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064126 1064237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064237 1064238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064238 1064299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064299 1064315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064315 1064316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064316 1064396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064396 1064400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064400 1064408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064408 1064430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064430 1064449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064449 1064459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064459 1064887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064887 1064888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064888 1071119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1070666: util-linux: last(1) is broken on i386 since 2.40-8
Processing commands for cont...@bugs.debian.org: > fixed 1070666 glibc/2.38-7 Bug #1070666 [glibc] util-linux: last(1) is broken on i386 since 2.40-8 Marked as fixed in versions glibc/2.38-7. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070666: marked as done (util-linux: last(1) is broken on i386 since 2.40-8)
Your message dated Thu, 16 May 2024 22:08:32 +0200 with message-id and subject line Re: Bug#1070666: util-linux: last(1) is broken on i386 since 2.40-8 has caused the Debian Bug report #1070666, regarding util-linux: last(1) is broken on i386 since 2.40-8 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.) -- 1070666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: util-linux Version: 2.40-8 Severity: normal Hello. Upgrade of util-linux from 2.39.3-6 to 2.40-8 on i386 systems breaks last(1), while the same upgrade on amd64 systems does not break it. Examples on my hosts running in 32-bit mode: -- root@citrine # /usr/bin/last -3 last: unrecognized ut_type: 22985 last: preallocation size exceeded -- root@typhoon # /usr/bin/last -3 last: unrecognized ut_type: 3640 last: unrecognized ut_type: 52 6.5.0-1- 3 Thu Jan 1 03:00gone - no logout last: unrecognized ut_type: -14908 amd64evel Sat Jul 6 11:21 - down (586103921+18:44) last: preallocation size exceeded -- root@passat # /usr/bin/last -3 last: unrecognized ut_type: -13985 last: unrecognized ut_type: 53 6.5.0-1- 2 Thu Jan 1 03:00gone - no logout last: unrecognized ut_type: 15714 last: unrecognized ut_type: -4407 amd64evel Sat Jul 6 11:21gone - no logout last: unrecognized ut_type: -31324 last: unrecognized ut_type: 29555 6.5.0-1- b9Thu Jan 1 03:00gone - no logout last: unrecognized ut_type: 2583 last: unrecognized ut_type: 29556 last: unrecognized ut_type: -18676 last: unrecognized ut_type: 19843 last: unrecognized ut_type: 14690 192.168. ts/9root Thu Jan 1 03:00gone - no logout last: preallocation size exceeded -- Running binary extracted from util-linux 2.39.3-6 package (as /tmp/last) always produce right results: -- root@citrine # /tmp/last -3 root pts/9192.168.27.27Mon May 6 22:40 still logged in root pts/9192.168.27.7 Mon May 6 10:19 - 13:20 (03:01) root pts/10 192.168.27.17Fri May 3 16:12 - 19:10 (02:57) wtmp begins Sun Apr 14 11:18:49 2024 -- Package info: ||/ Name Version Architecture Description +++-==---= ii util-linux 2.40-8 i386 miscellaneous system utilities ii libc-bin 2.37-18 i386 GNU C Library: Binaries ii libc-l10n 2.37-18 all GNU C Library: localization files ii libc6:i386 2.37-18 i386 GNU C Library: Shared libraries -- Eugene Berdnikov --- End Message --- --- Begin Message --- fixed 1070666 glibc/2.38-7 thanks Hi, On Thu, May 16, 2024 at 10:46:28PM +0300, Eugene Berdnikov wrote: > Installation of util-linux 2.40.1-1 (and accompanied libmount1, > libuuid1, libblkid1, libsmartcols1 of the same version) solves > the problem, output of "last" is correct. Thanks for reporting back with the good news! > Thank you, guys! Chris--- End Message ---
Processed: Re: Bug#1071172: libc6-dev omits the bits directory
Processing control commands: > tags -1 + moreinfo Bug #1071172 [libc6-dev] libc6-dev omits the bits directory Added tag(s) moreinfo. -- 1071172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1071093: libc6: [adequate] undefined-symbol
Processing control commands: > reassign -1 adequate Bug #1071093 [libc6] libc6:i386: [adequate] undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1 Bug reassigned from package 'libc6' to 'adequate'. No longer marked as found in versions glibc/2.38-11. Ignoring request to alter fixed versions of bug #1071093 to the same values previously set > retitle -1 false positive detected in in libthread_db.so.1 Bug #1071093 [adequate] libc6:i386: [adequate] undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1 Changed Bug title to 'false positive detected in in libthread_db.so.1' from 'libc6:i386: [adequate] undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1'. -- 1071093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1071093 to libc6:i386: [adequate] undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1
Processing commands for cont...@bugs.debian.org: > retitle 1071093 libc6:i386: [adequate] undefined-symbol > /lib/i386-linux-gnu/libthread_db.so.1 Bug #1071093 [libc6] libc6: [adequate] undefined-symbol Changed Bug title to 'libc6:i386: [adequate] undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1' from 'libc6: [adequate] undefined-symbol'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1070666: util-linux: last(1) is broken on i386 since 2.40-8
Processing control commands: > reassign 1070666 glibc Bug #1070666 [util-linux] util-linux: last(1) is broken on i386 since 2.40-8 Bug reassigned from package 'util-linux' to 'glibc'. No longer marked as found in versions util-linux/2.40-8. Ignoring request to alter fixed versions of bug #1070666 to the same values previously set > affects 1070666 util-linux Bug #1070666 [glibc] util-linux: last(1) is broken on i386 since 2.40-8 Added indication that 1070666 affects util-linux -- 1070666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070875: marked as done (glibc: FTBFS on hppa - Encountered regressions that don't match expected failures)
Your message dated Sat, 11 May 2024 21:35:43 + with message-id and subject line Bug#1070875: fixed in glibc 2.38-11 has caused the Debian Bug report #1070875, regarding glibc: FTBFS on hppa - Encountered regressions that don't match expected failures 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.) -- 1070875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glibc Version: 2.38-10 Severity: normal Tags: ftbfs Dear Maintainer, The following tests are known to fail on hppa when glibc is built with gcc-13 or later: FAIL: math/test-double-fma FAIL: math/test-double-ldouble-fma FAIL: math/test-float32x-float64-fma FAIL: math/test-float32x-fma FAIL: math/test-float64-fma FAIL: math/test-ldouble-fma The tests do not fail when glibc is built with gcc-12. See following gcc bug report: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709 Full build log is here: https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=hppa&ver=2.38-10&stamp=1715383873&raw=0 Things get worse with gcc-14. I suspect this is an issue with nan representation. Please change the above tests to xfails. Thanks, Dave Anglin -- System Information: Debian Release: trixie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 6.1.90+ (SMP w/4 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.38-11 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 1070...@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: Sat, 11 May 2024 23:17:18 +0200 Source: glibc Architecture: source Version: 2.38-11 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1070872 1070875 Changes: glibc (2.38-11) unstable; urgency=medium . [ Aurelien Jarno ] * debian/testsuite-xfail-debian.mk: ignore a few math failures due to GCC 13 on hppa. Closes: #1070875. * debian/patches/any/submitted-static-*.diff: add proposed patches to fix various missing math function in libm.a. Closes: #1070872. * debian/testsuite-xfail-debian.mk: mark tst-support_descriptors as XFAIL, due to sbuild bug #1070003. Checksums-Sha1: cb16f1fe7d3a90116921dfec258d9b1686b894d0 7535 glibc_2.38-11.dsc cc793377025830f66fb937ad2b6316f630c11bfc 429076 glibc_2.38-11.debian.tar.xz 2c283e082e8a33880c389204e658e0d97a5c5e6a 9945 glibc_2.38-11_source.buildinfo Checksums-Sha256: e3673f0f0f7371335ed6d9ac1221d33c62604af8171686282a481da8e7a4aa80 7535 glibc_2.38-11.dsc 336d41903e4c2b12a71bb646b68c9c295c980a4a7f22a43da70aadbcfa80a825 429076 glibc_2.38-11.debian.tar.xz c8f760e85c32c0d5ec7d97431213e67682fc285dbc0d58aaf2812482746624e6 9945 glibc_2.38-11_source.buildinfo Files: a811ef2a956ad933930fc7eebfeff191 7535 libs required glibc_2.38-11.dsc f28787622972a7abf9410e185856 429076 libs required glibc_2.38-11.debian.tar.xz 8107fceff977128d94b922275a6a3f3a 9945 libs required glibc_2.38-11_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmY/4XoACgkQE4jA+Jno M2uXFg//Yje3QGX/t1bfLHjnkWHCdUm+YttbET18bsbObuT4jdGgv4aDUgEmhXB3 ncB+BAJI6mJiaRjLu6E9eaHlVyMhzpMSVlJ40O12XVo45W3gxtjZ5RxrO8HEso4b 8HFWwtpt6wa2VnQqmneaoNdHA/ZYpPI9dDvELlanvvIc7u6pzQ7606A3oTd+O/Aw RnXaRWrREPKi305+1bEzShymgcM+uDxlQ1w6PhXiEPlbROg6Qg+Oz8CbJHM9UAMJ T984QNwTfJRSLtkSmxl1bv8dOoaNJop8qiXdlEGgavs87cEACB7e5RObzZNzNTXl f09sHzdc1NIpjuNXGUYr5V7RcKl0A59rvk1mWHcR3PHPtbvKUHpRJumhxmzWioDc h6pNxj0NnUomWNNgvBnhzykpxzSGkWAtrqi6lEdh8HQMt5FsFwNKOZaj7ytRYjNO a3h0FdD4lGKupJKe2nwgpurT91Oc/C0TwobYvxuyrPMEgp7pkzhQrc5UXvH4kWMA tih7Da6qhHZk/
Bug#1070872: marked as done (libm.a lost fmod + fmodf on i386 + m68k)
Your message dated Sat, 11 May 2024 21:35:43 + with message-id and subject line Bug#1070872: fixed in glibc 2.38-11 has caused the Debian Bug report #1070872, regarding libm.a lost fmod + fmodf on i386 + m68k 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.) -- 1070872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6-dev Version: 2.38-7 Severity: serious Tags: ftbfs Control: affects -1 src:zsh https://buildd.debian.org/status/logs.php?pkg=zsh&ver=5.9-6%2Bb1 ... gcc -static -o zsh main.o `cat stamp-modobjs` -lpcre2-8 -lgdbm -lcap -lncursesw -ltinfo -ltinfo -lrt -lm -lc ... ./obj-static/Src/../../Src/math.c:1260:(.text+0x1d8e): undefined reference to `fmod' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:228: zsh] Error 1 $ objdump -t /usr/lib/i386-linux-gnu/libm.a | grep fmod w_fmodl_compat.o: file format elf32-i386 w_fmod_compat.o: file format elf32-i386 w_fmodf_compat.o: file format elf32-i386 e_fmodl.o: file format elf32-i386 g F .text 0013 __ieee754_fmodl w_fmodl.o: file format elf32-i386 g F .text 0085 __fmodl *UND* __ieee754_fmodl wF .text 0085 fmodf64x wF .text 0085 fmodl e_fmod.o: file format elf32-i386 g F .text 0013 __ieee754_fmod w_fmod.o: file format elf32-i386 e_fmodf.o: file format elf32-i386 g F .text 0013 __ieee754_fmodf w_fmodf.o: file format elf32-i386 e_fmodf128.o: file format elf32-i386 g F .text 0c9b __ieee754_fmodf128 *UND* __ieee754_fmodf128 *UND* __ieee754_fmodf128 w_fmodf128.o: file format elf32-i386 g F .text 0237 __fmodf128 *UND* __ieee754_fmodf128 wF .text 0237 fmodf128 $ With 2.37-13 this is instead: $ objdump -t /usr/lib/i386-linux-gnu/libm.a | grep fmod w_fmodl_compat.o: file format elf32-i386 w_fmod_compat.o: file format elf32-i386 w_fmodf_compat.o: file format elf32-i386 e_fmodl.o: file format elf32-i386 g F .text 0013 __ieee754_fmodl w_fmodl.o: file format elf32-i386 g F .text 0085 __fmodl *UND* __ieee754_fmodl wF .text 0085 fmodf64x wF .text 0085 fmodl e_fmod.o: file format elf32-i386 g F .text 0013 __ieee754_fmod w_fmod.o: file format elf32-i386 g F .text 006b __fmod *UND* __ieee754_fmod wF .text 006b fmodf32x wF .text 006b fmodf64 wF .text 006b fmod e_fmodf.o: file format elf32-i386 g F .text 0013 __ieee754_fmodf w_fmodf.o: file format elf32-i386 g F .text 0063 __fmodf *UND* __ieee754_fmodf wF .text 0063 fmodf32 wF .text 0063 fmodf e_fmodf128.o: file format elf32-i386 g F .text 0cc5 __ieee754_fmodf128 *UND* __ieee754_fmodf128 *UND* __ieee754_fmodf128 w_fmodf128.o: file format elf32-i386 g F .text 0237 __fmodf128 *UND* __ieee754_fmodf128 wF .text 0237 fmodf128 $ --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.38-11 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 1070...@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: Sat, 11 May 2024 23:17:18 +0200 Source: glibc Architecture: source Version: 2.38-11 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1070872 107087
Bug#1053241: marked as done (glibc: please apply upstream patch to fix slow fstat)
Your message dated Sat, 11 May 2024 22:36:07 +0200 with message-id and subject line Re: Bug#1053241: glibc: please apply upstream patch to fix slow fstat has caused the Debian Bug report #1053241, regarding glibc: please apply upstream patch to fix slow fstat 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.) -- 1053241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: glibc Version: 2.36-9+deb12u1 Severity: normal X-Debbugs-Cc: pedretti.fa...@gmail.com Dear Maintainer, glibc uses a slow version of fstat. Details are documented here: https://lwn.net/Articles/944214/ A patch to fix this was merged in glibc: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=551101e8240b7514fc646d1722f8b79c90362b8f The patch applies cleanly and builds fine also on bookworm glibc. Please consider apply it to fix slow fstat. Thanks. --- End Message --- --- Begin Message --- Version: 2.39-1 On 2023-11-26 18:19, Fabio Pedretti wrote: > Il giorno dom 26 nov 2023 alle ore 16:28 Aurelien Jarno > ha scritto: > > > > Hi, > > > > On 2023-09-29 21:52, Fabio Pedretti wrote: > > > Package: glibc > > > Version: 2.36-9+deb12u1 > > > Severity: normal > > > X-Debbugs-Cc: pedretti.fa...@gmail.com > > > > > > Dear Maintainer, > > > > > > glibc uses a slow version of fstat. Details are documented > > > here: https://lwn.net/Articles/944214/ > > > > > > A patch to fix this was merged in glibc: > > > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=551101e8240b7514fc646d1722f8b79c90362b8f > > > > > > The patch applies cleanly and builds fine also on bookworm glibc. > > > Please consider apply it to fix slow fstat. > > > > This patch changes the syscall used by binaries, so it has to be > > considered with a lot of care in a stable release, it could break > > existing seccomp filters. In any case it has to live a few months in > > testing/unstable first. > > > > Note that the kernel patch that improves the performance of fstatat, has > > not been merge to the upstream stable tree, nor to bookworm. > > > > In order to better understand the need for this patch in bookworm, could > > you please give some details about your workload and the performance > > impact it has? > > I did some test with my use case, borg backup with many unchanged > files, see https://github.com/borgbackup/borg/issues/4498 for some > background and system calls impact, where borg 1.2 slow downs a lot > vs. borg 1.1. > > I checked using strace the patch, it did the job (newfstatat calls > were replaced with fstat), and I'd hoped that it would improve > performance, however my use case improved just marginally (difficult > to have reproducible data in my case, but it was like 5%). > > I didn't notice any other regression, however. > > I see the glibc patch is still only on 2.39, while even Debian > experimental has just 2.38. Debian experimental now has version 2.39, closing the bug accordingly. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net--- End Message ---
Processed: Bug#1070875 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1070875 [src:glibc] glibc: FTBFS on hppa - Encountered regressions that don't match expected failures Added tag(s) pending. -- 1070875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1070872 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1070872 [libc6-dev] libm.a lost fmod + fmodf on i386 + m68k Added tag(s) pending. -- 1070872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1070872 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=31488
Processing commands for cont...@bugs.debian.org: > forwarded 1070872 https://sourceware.org/bugzilla/show_bug.cgi?id=31488 Bug #1070872 [libc6-dev] libm.a lost fmod + fmodf on i386 + m68k Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=31488'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1070875 is forwarded to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
Processing commands for cont...@bugs.debian.org: > forwarded 1070875 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709 Bug #1070875 [src:glibc] glibc: FTBFS on hppa - Encountered regressions that don't match expected failures Set Bug forwarded-to-address to 'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libm.a lost fmod + fmodf on i386 + m68k
Processing control commands: > affects -1 src:zsh Bug #1070872 [libc6-dev] libm.a lost fmod + fmodf on i386 + m68k Added indication that 1070872 affects src:zsh -- 1070872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066887: marked as done (locales/locale-gen: Locales Cannot Copy from Locales in /usr/local/share/i18n/locales)
Your message dated Fri, 10 May 2024 14:55:49 +
with message-id
and subject line Bug#1066887: fixed in glibc 2.38-9
has caused the Debian Bug report #1066887,
regarding locales/locale-gen: Locales Cannot Copy from Locales in
/usr/local/share/i18n/locales
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.)
--
1066887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: locales
Version: 2.36-9+deb12u4
Severity: important
Tags: l10n
X-Debbugs-Cc: maddes+deb...@maddes.net
Dear Maintainer,
referencing a custom locale that resides in /usr/local/share/i18n/loaces/ via
"copy" doesn't work.
`dpkg-reconfigure locales` gives the following error message:
en_GB.UTF-8@INTL...[error] cannot open locale definition file `en_US@INTL': No
such file or directory
Both locales will get attached to the bug, so you can be reproduce.
* What led up to the situation?
Created custom locales in /usr/local/share/i18n/locales/ and wanted
to copy from one those custome locales: en_GB@INTL shall copy LC_TIME from
en_US@INTL.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Looked around and recognized that locale-gen doesn't pass any I18NPATH to
localedef. So only the compiled-in single path /usr/share/i18n/locales/ is
referenced.
* What was the outcome of this action?
Referencing custom locales without I18NPATH does not work (see error message
above).
* What outcome did you expect instead?
Referencing a custom locale should work out of the box.
* Workarounds?
This worked: `I18NPATH=/usr/local/share/i18n dpkg-reconfigure locales`
* Possible solutions?
Option #1: Enhance `locale-gen` to set I18NPATH when calling localedef
TESTED and working, allows to set I18NPATH also from the outside.
/usr/sbin/locale-gen:
...
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
...
I18NPATH="${I18NPATH}" localedef ...
...
done
Option #2: Enhance `localedef` upstream to allow collon separated list of paths
via LOCSRCDIR macro
There are no changes since glibc 2.36 in function locfile_read() of
locale/programs/locfile.c and no debian patches for this function.
Something like this should work (UNTESTED!):
int
locfile_read (struct localedef_t *result, const struct charmap_t *charmap)
{
...
/* Test in the default directories. */
if (ldfile == NULL)
{
char *locpath = LOCSRCDIR;
const size_t pathlen = strlen (locpath);
char locpathbuf[pathlen + 1];
char path[strlen (filename) + 1 + pathlen];
char *next;
locpath = memcpy (locpathbuf, locpath, pathlen + 1);
while (ldfile == NULL
&& (next = strsep (&locpath, ":")) != NULL)
{
stpcpy (stpcpy (path, next), filename);
ldfile = lr_open (path, locfile_hash);
if (ldfile == NULL)
{
stpcpy (stpcpy (stpcpy (path, next), "/"), filename);
ldfile = lr_open (path, locfile_hash);
}
}
}
...
-- System Information:
Debian Release: 12.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-9-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8@INTL, LC_CTYPE=en_US.UTF-8@INTL (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages locales depends on:
ii debconf [debconf-2.0] 1.5.82
ii libc-bin 2.36-9+deb12u4
ii libc-l10n 2.36-9+deb12u4
locales recommends no packages.
locales suggests no packages.
-- debconf information:
* locales/locales_to_be_generated: en_DE.UTF-8@INTL UTF-8, en_US.UTF-8 UTF-8,
en_US.UTF-8@INTL UTF-8
* locales/default_environment_locale: en_US.UTF-8@INTL
comment_char %
escape_char /
% INTL English locale for US
% This is a modified copy of "en_US"
% Modifications done for internationally working people: ISO date, 24h clock,
comma as decimal separator, A4 paper, metric system, etc.
% Most settings are either directly c
Processed: Bug#1066887 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1066887 [locales] locales/locale-gen: Locales Cannot Copy from Locales in /usr/local/share/i18n/locales Added tag(s) pending. -- 1066887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: FTBFS due to /usr/include/aarch64-linux-gnu/bits/math-vector.h
Processing control commands:
> severity 1070441 important
Bug #1070441 [src:cbmc] cmbc: arm64 FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070441 to the same value.
> block 1070668 by 1070441
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
> severity 1070443 important
Bug #1070443 [src:aspectc++] aspectc++: arm64 FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070443 to the same value.
> block 1070668 by 1070443
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
> severity 1070444 important
Bug #1070444 {Done: Camm Maguire } [src:cxref] cxref: arm64
FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070444 to the same value.
> block 1070668 by 1070444
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
> severity 1070446 important
Bug #1070446 [src:rocm-hipamd] rocm-hipamd: arm64 FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070446 to the same value.
> block 1070668 by 1070446
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
--
1070441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070441
1070443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070443
1070444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070444
1070446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070446
1070668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: FTBFS due to /usr/include/aarch64-linux-gnu/bits/math-vector.h
Processing control commands:
> severity 1070441 important
Bug #1070441 [src:cbmc] cmbc: arm64 FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070441 to the same value.
> block 1070668 by 1070441
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
> severity 1070443 important
Bug #1070443 [src:aspectc++] aspectc++: arm64 FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070443 to the same value.
> block 1070668 by 1070443
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
> severity 1070444 important
Bug #1070444 {Done: Camm Maguire } [src:cxref] cxref: arm64
FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070444 to the same value.
> block 1070668 by 1070444
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
> severity 1070446 important
Bug #1070446 [src:rocm-hipamd] rocm-hipamd: arm64 FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070446 to the same value.
> block 1070668 by 1070446
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
--
1070441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070441
1070443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070443
1070444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070444
1070446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070446
1070668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: FTBFS due to /usr/include/aarch64-linux-gnu/bits/math-vector.h
Processing control commands:
> severity 1070441 important
Bug #1070441 [src:cbmc] cmbc: arm64 FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070441 to the same value.
> block 1070668 by 1070441
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
> severity 1070443 important
Bug #1070443 [src:aspectc++] aspectc++: arm64 FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070443 to the same value.
> block 1070668 by 1070443
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
> severity 1070444 important
Bug #1070444 {Done: Camm Maguire } [src:cxref] cxref: arm64
FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070444 to the same value.
> block 1070668 by 1070444
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
> severity 1070446 important
Bug #1070446 [src:rocm-hipamd] rocm-hipamd: arm64 FTBFS with glibc 2.38
Ignoring request to change severity of Bug 1070446 to the same value.
> block 1070668 by 1070446
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070443 1070444 1070446 1070441
1070668 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1070668 to the same blocks
previously set
--
1070441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070441
1070443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070443
1070444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070444
1070446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070446
1070668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: FTBFS due to /usr/include/aarch64-linux-gnu/bits/math-vector.h
Processing control commands:
> severity 1070441 important
Bug #1070441 [src:cbmc] cmbc: arm64 FTBFS with glibc 2.38
Severity set to 'important' from 'serious'
> block 1070668 by 1070441
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was not blocked by any bugs.
1070668 was not blocking any bugs.
Added blocking bug(s) of 1070668: 1070441
> severity 1070443 important
Bug #1070443 [src:aspectc++] aspectc++: arm64 FTBFS with glibc 2.38
Severity set to 'important' from 'serious'
> block 1070668 by 1070443
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070441
1070668 was not blocking any bugs.
Added blocking bug(s) of 1070668: 1070443
> severity 1070444 important
Bug #1070444 {Done: Camm Maguire } [src:cxref] cxref: arm64
FTBFS with glibc 2.38
Severity set to 'important' from 'serious'
> block 1070668 by 1070444
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070441 1070443
1070668 was not blocking any bugs.
Added blocking bug(s) of 1070668: 1070444
> severity 1070446 important
Bug #1070446 [src:rocm-hipamd] rocm-hipamd: arm64 FTBFS with glibc 2.38
Severity set to 'important' from 'serious'
> block 1070668 by 1070446
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was blocked by: 1070441 1070444 1070443
1070668 was not blocking any bugs.
Added blocking bug(s) of 1070668: 1070446
--
1070441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070441
1070443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070443
1070444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070444
1070446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070446
1070668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1070668
Processing commands for cont...@bugs.debian.org: > tags 1070668 + help Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library header on arm64 Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1070668
Processing commands for cont...@bugs.debian.org: > affects 1070668 cbmc aspectc++ cxref rocm-hipamd Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library header on arm64 Added indication that 1070668 affects cbmc, aspectc++, cxref, and rocm-hipamd > thanks Stopping processing here. Please contact me if you need assistance. -- 1070668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: glibc: packages FTBFS caused by vector math library header on arm64
Processing control commands: > forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=30909 Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library header on arm64 Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=30909'. -- 1070668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041415: marked as done (libc6: fchmodat emulation fails in the absence of /proc)
Your message dated Fri, 03 May 2024 22:51:07 +
with message-id
and subject line Bug#1041415: fixed in glibc 2.39-1
has caused the Debian Bug report #1041415,
regarding libc6: fchmodat emulation fails in the absence of /proc
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.)
--
1041415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs
Version: 1:28.2+1-15
Severity: serious
Dear Maintainer,
in a sid chroot:
root@debian:~# apt install emacs
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
emacs-bin-common emacs-common emacs-el emacs-gtk fonts-noto-color-emoji
libgccjit0 libm17n-0 libotf1 m17n-db
Suggested packages:
emacs-common-non-dfsg ncurses-term m17n-docs
The following NEW packages will be installed:
emacs emacs-bin-common emacs-common emacs-el emacs-gtk fonts-noto-color-emoji
libgccjit0 libm17n-0 libotf1 m17n-db
0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/57.4 MB of archives.
After this operation, 179 MB of additional disk space will be used.
Do you want to continue? [Y/n]
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
Selecting previously unselected package emacs-el.
(Reading database ... 243178 files and directories currently installed.)
Preparing to unpack .../0-emacs-el_1%3a28.2+1-15_all.deb ...
Unpacking emacs-el (1:28.2+1-15) ...
Selecting previously unselected package emacs-common.
Preparing to unpack .../1-emacs-common_1%3a28.2+1-15_all.deb ...
Unpacking emacs-common (1:28.2+1-15) ...
Selecting previously unselected package emacs-bin-common.
Preparing to unpack .../2-emacs-bin-common_1%3a28.2+1-15_amd64.deb ...
Unpacking emacs-bin-common (1:28.2+1-15) ...
Selecting previously unselected package libgccjit0:amd64.
Preparing to unpack .../3-libgccjit0_13.1.0-8_amd64.deb ...
Unpacking libgccjit0:amd64 (13.1.0-8) ...
Selecting previously unselected package m17n-db.
Preparing to unpack .../4-m17n-db_1.8.2-1_all.deb ...
Unpacking m17n-db (1.8.2-1) ...
Selecting previously unselected package libotf1:amd64.
Preparing to unpack .../5-libotf1_0.9.16-4_amd64.deb ...
Unpacking libotf1:amd64 (0.9.16-4) ...
Selecting previously unselected package libm17n-0:amd64.
Preparing to unpack .../6-libm17n-0_1.8.2-1_amd64.deb ...
Unpacking libm17n-0:amd64 (1.8.2-1) ...
Selecting previously unselected package emacs-gtk.
Preparing to unpack .../7-emacs-gtk_1%3a28.2+1-15_amd64.deb ...
Unpacking emacs-gtk (1:28.2+1-15) ...
Selecting previously unselected package emacs.
Preparing to unpack .../8-emacs_1%3a28.2+1-15_all.deb ...
Unpacking emacs (1:28.2+1-15) ...
Selecting previously unselected package fonts-noto-color-emoji.
Preparing to unpack .../9-fonts-noto-color-emoji_2.038-1_all.deb ...
Unpacking fonts-noto-color-emoji (2.038-1) ...
Setting up libotf1:amd64 (0.9.16-4) ...
Setting up fonts-noto-color-emoji (2.038-1) ...
Setting up m17n-db (1.8.2-1) ...
Setting up libm17n-0:amd64 (1.8.2-1) ...
Setting up libgccjit0:amd64 (13.1.0-8) ...
Setting up emacs-el (1:28.2+1-15) ...
Setting up emacs-common (1:28.2+1-15) ...
Setting up emacs-bin-common (1:28.2+1-15) ...
update-alternatives: using /usr/bin/ctags.emacs to provide /usr/bin/ctags
(ctags) in auto mode
update-alternatives: using /usr/bin/ebrowse.emacs to provide /usr/bin/ebrowse
(ebrowse) in auto mode
update-alternatives: using /usr/bin/emacsclient.emacs to provide
/usr/bin/emacsclient (emacsclient) in auto mode
update-alternatives: using /usr/bin/etags.emacs to provide /usr/bin/etags
(etags) in auto mode
Setting up emacs-gtk (1:28.2+1-15) ...
update-alternatives: using /usr/bin/emacs-gtk to provide /usr/bin/emacs (emacs)
in auto mode
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
>>Error occurred processing /usr/share/emacs/site-lisp/debian-startup.el: File
>>error (("Doing chmod" "Operation not supported"
>>"/usr/share/emacs/site-lisp/debian-startup.elcxkbhIA"))
ERROR: install script from emacsen-common package failed
dpkg: error processing package emacs-gtk (--configure):
installed emacs-gtk package post-installation script subprocess returned error
exit status 1
dpkg: dependency problems prevent configuration of emacs:
emacs depends on emacs-gtk (>= 1:27.1) | emacs-lucid (>= 1:27.1) | emacs-nox
(>= 1:27.1); however:
Package emacs-gtk is not configured yet.
Package emacs-lucid is not inst
Bug#1042562: marked as done (libc6: broken utmp handling in 32-bit programs with 64-bit time_t)
Your message dated Fri, 03 May 2024 20:49:31 +
with message-id
and subject line Bug#1042562: fixed in glibc 2.38-7
has caused the Debian Bug report #1042562,
regarding libc6: broken utmp handling in 32-bit programs with 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.)
--
1042562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.37-6
Tags: upstream
The utmp(5) interface has broken its compatibility in 32-bit programs
built with -D_TIME_BITS=64. In bits/utmpx.h we see this:
,
| /* The fields ut_session and ut_tv must be the same size when compiled
|32- and 64-bit. This allows files and shared memory to be shared
|between 32- and 64-bit applications. */
| #if __WORDSIZE_TIME64_COMPAT32
| __int32_t ut_session; /* Session ID, used for windowing. */
| struct
| {
| __int32_t tv_sec; /* Seconds. */
| __int32_t tv_usec;/* Microseconds. */
| } ut_tv;/* Time entry was made. */
| #else
| long int ut_session;/* Session ID, used for windowing. */
| struct timeval ut_tv; /* Time entry was made. */
| #endif
`
The definition of __WORDSIZE_TIME64_COMPAT32 can be found in bits/wordsize.h:
,
| #ifdef __x86_64__
| # define __WORDSIZE_TIME64_COMPAT32 1
| /* Both x86-64 and x32 use the 64-bit system call interface. */
| # define __SYSCALL_WORDSIZE 64
| #else
| # define __WORDSIZE_TIME64_COMPAT32 0
| #endif
`
So on i386 (and I suppose on other 32-bit architectures except x32)
ut_tv is of struct timeval, and ut_tv.tv_sec is of time_t, which is
actually a 64-bit integer in programs built with -D_TIME_BITS=64.
One example where this already has caused problems is the who(1) program
which has opted in for -D_TIME_BITS=64, see #1027135. Once programs
start to _write_ utmp entries with a 64-bit ut_tv.tv_sec rather than
merely reading them, things could become more interesting. :-(
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.38-7
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 1042...@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: Fri, 03 May 2024 21:55:28 +0200
Source: glibc
Architecture: source
Version: 2.38-7
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers
Changed-By: Aurelien Jarno
Closes: 1042562
Changes:
glibc (2.38-7) unstable; urgency=medium
.
[ Samuel Thibault ]
* debian/patches/hurd-i386/git-context.diff: Add hurd-amd64 version of
*context.
* debian/testsuite-xfail-debian.mk: Update hurd-amd64-specific xfails
accordingly.
* debian/patches/hurd-i386/local-no-bootstrap-fs-access.2.diff: Also update
localplt.data on hurd-amd64.
* debian/patches/hurd-i386/local-stack_chk_guard.diff: Also update
ld.abilist on hurd-amd64.
* debian/patches/hurd-i386/local-exec_filename.diff: Also update
libc.abilist on hurd-amd64.
* debian/patches/hurd-i386/local-usr.diff: Also update libc.abilist on
hurd-amd64.
.
[ Aurelien Jarno ]
* debian/patches/any/git-test-epoll.diff: improve test-epoll robustness
improvements from upstream, useful when running the testsuite on
overloaded hosts.
* debian/patches/git-updates.diff: update from upstream stable branch:
- Fix utmp handling in 32-bit programs when using -D_TIME_BITS=64.
Closes: #1042562.
Checksums-Sha1:
2cc660b009ea9028c240a88064b05740237ff860 9079 glibc_2.38-7.dsc
32442f4ebdcf7cabbd9fab979c7db6b47fa4f6ae 426224 glibc_2.38-7.debian.tar.xz
560e43e1a854511e54ea90052979ecae44a90189 10084 glibc_2.3
Processed: Bug#1042562 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1042562 [libc6] libc6: broken utmp handling in 32-bit programs with 64-bit time_t Added tag(s) pending. -- 1042562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: host.conf: "multi on" appears to be default
Processing commands for cont...@bugs.debian.org: > reassign 459664 src:glibc Bug #459664 [base-files] host.conf: "multi on" appears to be default Bug reassigned from package 'base-files' to 'src:glibc'. No longer marked as found in versions base-files/4. Ignoring request to alter fixed versions of bug #459664 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 459664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1041415
Processing commands for cont...@bugs.debian.org: > affects 1041415 emacs Bug #1041415 [libc6] libc6: fchmodat emulation fails in the absence of /proc Added indication that 1041415 affects emacs > thanks Stopping processing here. Please contact me if you need assistance. -- 1041415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1041415: details
Processing control commands: > tag -1 + fixed-upstream Bug #1041415 [libc6] libc6: fchmodat emulation fails in the absence of /proc Added tag(s) fixed-upstream. -- 1041415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign emacs bug to libc
Processing commands for cont...@bugs.debian.org: > reassign 1041415 libc6 Bug #1041415 [emacs] emacs: fails to install: post-installation script subprocess returned error exit status 1 Bug reassigned from package 'emacs' to 'libc6'. No longer marked as found in versions emacs/1:28.2+1-15. Ignoring request to alter fixed versions of bug #1041415 to the same values previously set > retitle 1041415 libc6: fchmodat emulation fails in the absence of /proc Bug #1041415 [libc6] emacs: fails to install: post-installation script subprocess returned error exit status 1 Changed Bug title to 'libc6: fchmodat emulation fails in the absence of /proc' from 'emacs: fails to install: post-installation script subprocess returned error exit status 1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069191: marked as done (glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence)
Your message dated Tue, 23 Apr 2024 16:47:50 + with message-id and subject line Bug#1069191: fixed in glibc 2.31-13+deb11u9 has caused the Debian Bug report #1069191, regarding glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence 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.) -- 1069191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glibc Version: 2.37-17 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 2.37-15 Control: found -1 2.36-9+deb12u5 Control: found -1 2.36-9+deb12u4 Control: found -1 2.36-9 Control: found -1 2.31-13+deb11u8 Control: found -1 2.31-13 Hi, The following vulnerability was published for glibc. CVE-2024-2961[0]: | The iconv() function in the GNU C Library versions 2.39 and older | may overflow the output buffer passed to it by up to 4 bytes when | converting strings to the ISO-2022-CN-EXT character set, which may | be used to crash an application or overwrite a neighbouring | variable. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-2961 https://www.cve.org/CVERecord?id=CVE-2024-2961 [1] https://www.openwall.com/lists/oss-security/2024/04/17/9 Regards, Salvatore --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.31-13+deb11u9 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 1069...@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: Fri, 19 Apr 2024 22:40:26 +0200 Source: glibc Architecture: source Version: 2.31-13+deb11u9 Distribution: bullseye-security Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1069191 Changes: glibc (2.31-13+deb11u9) bullseye-security; urgency=medium . * debian/patches/any/local-CVE-2024-2961-iso-2022-cn-ext.patch: Fix out-of-bound writes when writing escape sequence in iconv ISO-2022-CN-EXT module (CVE-2024-2961). Closes: #1069191. Checksums-Sha1: d555a20390c7fba05a2cd1f5419bf973c1e9a969 8347 glibc_2.31-13+deb11u9.dsc 60fc288d2351b8b8c2b6ad23aa1f8f65c795249c 961928 glibc_2.31-13+deb11u9.debian.tar.xz 42ef9addd34cfe89709a746373618fcea2ea8d11 9270 glibc_2.31-13+deb11u9_source.buildinfo Checksums-Sha256: d434d56ceee9b81ca36558abdf21fe95ce96dd0be5f296c4d1394a53aac3bdce 8347 glibc_2.31-13+deb11u9.dsc c57f8a2e9bfbedeb110cfe35f9aa387337464ab1233de37f520a802f828a2b97 961928 glibc_2.31-13+deb11u9.debian.tar.xz cd4f7494c0cb52b6f0d8b001cffb111b21f8d33515f43321103b41224e6b2dba 9270 glibc_2.31-13+deb11u9_source.buildinfo Files: 1380cc777ac43126bbdd4897ee61b795 8347 libs required glibc_2.31-13+deb11u9.dsc 1d4c2a4a8ac6df5fa8aa09d321aed75b 961928 libs required glibc_2.31-13+deb11u9.debian.tar.xz b5e0bcd9c0e7954c897758490d5647ad 9270 libs required glibc_2.31-13+deb11u9_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmYi2KcACgkQE4jA+Jno M2tKbBAAiAu+/4xAq5ZQxjpEcxESNsgZomD1Wz0z17IuvkQD1+bUYAkFu/Bkxz+k hSA7COEzXSO8xEp2fmkRPrL711MR2USsDde0muZFHHYpcBQXgGJdRwSDnFJ9HE/l nGgaBHJSQyi/li8lGuGLjiRECCzLZF6pw0mAggEkULwnjN0FG7kMW39EBcZAABpX WmZacAJOozUDTYNEowx4V+lwDujMUKr6nxrtL1xUUsMnY7wcU7Kd/hOCXgcU37VO fjYQkDw5XBLCP/sDgxjAtsv5Ep4qLcsbm23SAycv00JUygyL4/OolQWSU8vSt8Bs Pdfdd1CaTSY+LdjrxtHXxFbKsNcjXI+2u2GNQ8m8jzvYEB4j2yX6dyE1zOugxOBo EOZNu13+/8Tn6XFm7gsQmo4CBju9je3CpgrWAa+XGUP3KKWe+XotmqlkEJwZDn3X XXZaGYNtb5HebmUgQhs+H56J/qpcv2Cb4CM4K7mF/e3YKzwAb53qHsisjYN+krMC QEfdEqUl9i1ip8f2z6ME8WB+92mfCg/i3YOk5NfdBS6BQWXeDAtkALyxxWRZgIsa 4vPDc0poYFTpUj6QrqbymlSnC/iKVUydrmjrok6XhxuJUrE+vcM7EK0lfChyVP17 rm8hcN2/xVHOebJFPTC9+jWr4VQHoBFND2unKHib2xH+2lkJVFg= =tfsn -END PGP SIGNA
Bug#1069191: marked as done (glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence)
Your message dated Tue, 23 Apr 2024 16:47:08 + with message-id and subject line Bug#1069191: fixed in glibc 2.36-9+deb12u6 has caused the Debian Bug report #1069191, regarding glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence 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.) -- 1069191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glibc Version: 2.37-17 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 2.37-15 Control: found -1 2.36-9+deb12u5 Control: found -1 2.36-9+deb12u4 Control: found -1 2.36-9 Control: found -1 2.31-13+deb11u8 Control: found -1 2.31-13 Hi, The following vulnerability was published for glibc. CVE-2024-2961[0]: | The iconv() function in the GNU C Library versions 2.39 and older | may overflow the output buffer passed to it by up to 4 bytes when | converting strings to the ISO-2022-CN-EXT character set, which may | be used to crash an application or overwrite a neighbouring | variable. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-2961 https://www.cve.org/CVERecord?id=CVE-2024-2961 [1] https://www.openwall.com/lists/oss-security/2024/04/17/9 Regards, Salvatore --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.36-9+deb12u6 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 1069...@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: Fri, 19 Apr 2024 18:34:04 +0200 Source: glibc Architecture: source Version: 2.36-9+deb12u6 Distribution: bookworm-security Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1069191 Changes: glibc (2.36-9+deb12u6) bookworm-security; urgency=medium . * debian/patches/any/local-CVE-2024-2961-iso-2022-cn-ext.diff: Fix out-of-bound writes when writing escape sequence in iconv ISO-2022-CN-EXT module (CVE-2024-2961). Closes: #1069191. Checksums-Sha1: 89201c9a3dc4b12a21085158cc671e65ef2cd2d2 9761 glibc_2.36-9+deb12u6.dsc ce2b34137062a0ddba922d5b34a80770737bb59c 858672 glibc_2.36-9+deb12u6.debian.tar.xz a44d3239eba25b6c7f4ce2756457d71ae0b857ac 9744 glibc_2.36-9+deb12u6_source.buildinfo Checksums-Sha256: fbd6a3b34c8019bc677c1aa3c55a7cdd2fac0f5226151d408cbf107e89002c10 9761 glibc_2.36-9+deb12u6.dsc dab8173d6a6393b50ed0737bd32ff993a3fa7bf4a837573eab8c67f1391ecb12 858672 glibc_2.36-9+deb12u6.debian.tar.xz 7ee850a9b13f43b44460b82fd59ca548b22123dd500bf942c3af4acbbb957bf6 9744 glibc_2.36-9+deb12u6_source.buildinfo Files: d98990edb6c22014e5b8c48aa43152c9 9761 libs required glibc_2.36-9+deb12u6.dsc 65d05b6e083f7e0d364a30fa0349efd9 858672 libs required glibc_2.36-9+deb12u6.debian.tar.xz 1cdb197b7714c8fd5c6e9ca7d19aa569 9744 libs required glibc_2.36-9+deb12u6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmYirqMACgkQE4jA+Jno M2sPNQ/+LTclWWW5JsLlpFpI1n0eCno6yzVxuU7nW31IffIRQ/eNYPqKa2iM+Wi+ q41DfI/0KV8yLdVkGiTofVK4RnFAAwN7FIzX0NBazCNlhr3cgBOR33YS8ep0bOfN EjXAS0PYsUwCB1Rf5ozKja6j0Lt8oWoodhRYayL29/WA8yf7oJru/Xaho0bVj68B lP29vRFEtNeBcG+s9iR617jlnUrbyY+1qCP5CwtRH6cBTKM6RozK8hCcNiw/BSwx S9wK+62oMNOpUJaOJLfuIygJH0nwaHzKQU+MQkQhI97ROeJJkGOhzBjAZK44CjkZ HYsizViEUO2Qjq5stTuExD6uYeLK9lcmlhwRgQVqqyQTRKoUOssQDeiNY/SyYscH 3f/HbUJ4QYQ5mlnpYrP3i7EQ2qHbzHEy6qgnmhhnoiPBr7vFQ7/CijIzt7RF78E8 B3XWTiWFuy5SCouXtEoJHhWrE2XNU/w5Ucpe+e2R23mnu5362ECGGvT+WHU2maaD TBdCwNYqw1oA5iy5XwF/FdlRqSEQk88vohl73EFPHl9HTyYiKcxlocQgRFRumv7x NFPHMxk27kGm7kXJb0FtBT7XOX+XUOjbCYRiNqWMlT/mH8bFg/Ey5KXI9TKXUjHB +fQKMYdXSn9O1waG9XFkDmz5TmrbP2+4vv9iahgXoanYnezUKCY= =p/cK -END PGP SIGNATURE- pgpJxbA8Mzw_d
Bug#1069191: marked as done (glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence)
Your message dated Fri, 19 Apr 2024 05:20:35 + with message-id and subject line Bug#1069191: fixed in glibc 2.37-18 has caused the Debian Bug report #1069191, regarding glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence 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.) -- 1069191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glibc Version: 2.37-17 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 2.37-15 Control: found -1 2.36-9+deb12u5 Control: found -1 2.36-9+deb12u4 Control: found -1 2.36-9 Control: found -1 2.31-13+deb11u8 Control: found -1 2.31-13 Hi, The following vulnerability was published for glibc. CVE-2024-2961[0]: | The iconv() function in the GNU C Library versions 2.39 and older | may overflow the output buffer passed to it by up to 4 bytes when | converting strings to the ISO-2022-CN-EXT character set, which may | be used to crash an application or overwrite a neighbouring | variable. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-2961 https://www.cve.org/CVERecord?id=CVE-2024-2961 [1] https://www.openwall.com/lists/oss-security/2024/04/17/9 Regards, Salvatore --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.37-18 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 1069...@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: Fri, 19 Apr 2024 07:10:32 +0200 Source: glibc Architecture: source Version: 2.37-18 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1069191 Changes: glibc (2.37-18) unstable; urgency=medium . * debian/patches/git-updates.diff: update from upstream stable branch: - Fix fix out-of-bound writes when writing escape sequence in iconv ISO-2022-CN-EXT module (CVE-2024-2961). Closes: #1069191. Checksums-Sha1: 55a2d32004c64d219b2c24802cc30e5a7aa02729 9043 glibc_2.37-18.dsc 6e6a9646c9296dc7de9b321f2a07a432472ff27b 422556 glibc_2.37-18.debian.tar.xz 1b076043374ce74f757b97bf54b4dca9705b9a33 10084 glibc_2.37-18_source.buildinfo Checksums-Sha256: 53fec1eca4e1c6e7ccb36a533eeb3e6b76c6ba5ecfb6ad0e66ee251ae356b638 9043 glibc_2.37-18.dsc 2d04ca854821da8d1a414d0afa20812cba5e3cfb9e10da7d824f9d8215acccad 422556 glibc_2.37-18.debian.tar.xz c8e98dd7add508db574499a2543b7d6f425dde3bee4de28502977dac0392f0c0 10084 glibc_2.37-18_source.buildinfo Files: 7f6b5b38d801a916027c292fedf6c6af 9043 libs required glibc_2.37-18.dsc 62a072981057354cea926396dd00c0ff 422556 libs required glibc_2.37-18.debian.tar.xz 87335394d5cf6b840689e187a8b591e7 10084 libs required glibc_2.37-18_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmYh/VUACgkQE4jA+Jno M2s+5w//SZHS7bFkz8VPpL2HrkP1cYgMuCswNIyLtf9h3533u9V4LU/XfEIh6OGV 7WnGDMO3HGUr2RvrgN5JqYRIP0YO5XaYJtkZrr9Tgy4QshTf8KZxxML2nKYJW62h GSEH8rPyHGjWwOgIOZ1tlMUp2Io+l15SEfMotOmDfjIoc5epwlXqdp1pgZaAlxZn i72jTm+Bj7/BlfTjYmrl1VDKJUw6fJmN+GOhEhl1eOsLWl1QN3S+d/pwtaPbgscF rCN18d9r1IodH8wpUmAKosgZ7hDuEIlL/+Z5f1YwcquE5+UtzVv7VfCor289Xi1i rKSTy7Eyurfh/zvfBvl9gdgmN66Y+Ey4h8ks1HkItQS53R6QjFaFqiNOjDNF1VKv MOvsqENoARp3fS/gcbL53mEi53pSvPWIiaiZygQ/2aonwIFEJSKC6s4QQ96OIjSs AJVCKjVYFU1Kht5kAr5yhUEg0fdcj11jLLF5UD7ZXABx4fFU+aKffnBd4qfiNRsY 4l/3hxKv6gsxaBVEAINCXJZmuMv7xz/Ir6YcKATQdiGNgTRijxJ6teqr+uUrxgqt k5DxrVntZwL8Xoy20gIejYwRGx4MlhSW5eYGWXyygyG8rnt6T+rR8eo+/WF0Blnq fzImbXtNf+vHkOpgAGmk7iIuG8MJZcFIEIRn/3vrYsghAqsq56U= =EcGb -END PGP SIGNATURE- pgpnpA4A7sfFs.pgp Description: PGP signature --- End Message ---
Processed: Bug#1069191 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1069191 [src:glibc] glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence Added tag(s) pending. -- 1069191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1069265 to tzdata: Upgrade from 2023c-2 to 2024a-0+deb10u1 corrupts zoneinfo files
Processing commands for cont...@bugs.debian.org: > retitle 1069265 tzdata: Upgrade from 2023c-2 to 2024a-0+deb10u1 corrupts > zoneinfo files Bug #1069265 [tzdata] tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files Changed Bug title to 'tzdata: Upgrade from 2023c-2 to 2024a-0+deb10u1 corrupts zoneinfo files' from 'tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1069265
Processing commands for cont...@bugs.debian.org: > tags 1069265 - upstream Bug #1069265 [tzdata] tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files Removed tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1069265
Processing commands for cont...@bugs.debian.org: > tags 1069265 - d-i Bug #1069265 [tzdata] tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files Removed tag(s) d-i. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 1069265 in tzdata/2023c-2
Processing commands for cont...@bugs.debian.org: > notfound 1069265 tzdata/2023c-2 Bug #1069265 [tzdata] tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files No longer marked as found in versions tzdata/2023c-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1069265 in tzdata/2024a-0+deb10u1
Processing commands for cont...@bugs.debian.org: > found 1069265 tzdata/2024a-0+deb10u1 Bug #1069265 [tzdata] tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files The source tzdata and version 2024a-0+deb10u1 do not appear to match any binary packages Marked as found in versions tzdata/2024a-0+deb10u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1069191 is grave
Processing commands for cont...@bugs.debian.org: > # make it RC with https://www.openwall.com/lists/oss-security/2024/04/18/4 > severity 1069191 grave Bug #1069191 [src:glibc] glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1069191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence
Processing control commands: > found -1 2.37-15 Bug #1069191 [src:glibc] glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence Marked as found in versions glibc/2.37-15. > found -1 2.36-9+deb12u5 Bug #1069191 [src:glibc] glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence Marked as found in versions glibc/2.36-9+deb12u5. > found -1 2.36-9+deb12u4 Bug #1069191 [src:glibc] glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence Marked as found in versions glibc/2.36-9+deb12u4. > found -1 2.36-9 Bug #1069191 [src:glibc] glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence Marked as found in versions glibc/2.36-9. > found -1 2.31-13+deb11u8 Bug #1069191 [src:glibc] glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence Marked as found in versions glibc/2.31-13+deb11u8. > found -1 2.31-13 Bug #1069191 [src:glibc] glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence Marked as found in versions glibc/2.31-13. -- 1069191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068737: marked as done (locales fails to install: locales failed to preconfigure, with exit status 2)
Your message dated Wed, 10 Apr 2024 22:07:02 + with message-id and subject line Bug#1068737: fixed in glibc 2.37-17 has caused the Debian Bug report #1068737, regarding locales fails to install: locales failed to preconfigure, with exit status 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 ow...@bugs.debian.org immediately.) -- 1068737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: locales Version: 2.37-16 Severity: grave A fresh `debootstrap unstable' chroot plus `apt install locales`: Preconfiguring packages ... locales failed to preconfigure, with exit status 2 dpkg: error processing package locales (--configure): installed locales package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: locales This is coming from this line in locales.config: DEFAULT_ENVIRONMENT="$(sed -En -e '/^LANG="?([^"]+)"?/h; g; $s//\1/p' /etc/default/locale /etc/locale.conf 2>/dev/null)" /etc/locale.conf does not exist (and it doesn't exist on my regular system too), so sed fails with "can't read: No such file or directory" error message (which is sent to /dev/null), and since whole script is run under `set -e', it exits here. This is caused by "debian/debhelper.in/locales.config: Extract default environment LANG using only sed" change in 2.37-16. Do we really need /etc/locale.conf at this time? I think it's unused for a very long time. Also see EE= assignment at the very beginning of this script. --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.37-17 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 23:43:53 +0200 Source: glibc Architecture: source Version: 2.37-17 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1068737 Changes: glibc (2.37-17) unstable; urgency=medium . * debian/debhelper.in/locales.config: revert to the version that has been working for 20+ years. Closes: #1068737. * debian/debhelper.in/locales.config: define LEGACY_EE and use $EE and $LEGACY_EE to refer the the locales config files, as done in the postinst. Checksums-Sha1: c6b0873331a62e1d020bb2c5d8c008fe13ce8803 9043 glibc_2.37-17.dsc 836d0a57a9dc91bc583dd9f094a7b71f8a70b6c7 412292 glibc_2.37-17.debian.tar.xz b8f3f13f1f4e182ba4690fd332dd248ae85a0596 10094 glibc_2.37-17_source.buildinfo Checksums-Sha256: 1b05b94f0d7bbdd79e4bb622d459fab83c65efbf01d0415125bc0c9db00c7030 9043 glibc_2.37-17.dsc e9f78eb7d437ab7fc8a45524099b3965f43ca93fa9000253984f47877d99a282 412292 glibc_2.37-17.debian.tar.xz 392433642da88f48ee16431be541d24a1dfd3c03425e3a827a9355dc9761b41d 10094 glibc_2.37-17_source.buildinfo Files: 0f29d810e9f5fdf01482379c2f55a22b 9043 libs required glibc_2.37-17.dsc feed3e116b0b58b0a0b57205bd3008d6 412292 libs required glibc_2.37-17.debian.tar.xz 581368f9aba9658640a4c57de370d518 10094 libs required glibc_2.37-17_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmYXCWYACgkQE4jA+Jno M2uJ9hAAhOlv3P0UzDdkwZByg9OIo5Bkj8AhOwjnbX+GDCp+TSn4yguu5nEV/Tmk GRiX5YrsCUZekIoZuxXQ+POK0XqDZZB23eRHJjC/VlXDwbVMJzg4UA+jXfPNwhq9 JAATMsAojW96yjcsvS//d5fOwus8jT964zAzZfxTYBy1VHxIspbEq9+/VLkjQEr8 KQgSTBhJEoqR/9+/O736N1zMVT7l0POzOosdKV3s9JXbf4QDenaxkZ5VIy9bE+Pb bXjIr73TxM5jC9lnRfB/W1Naf2uy2pjXnE3I1P4lfNnskRlH5oKQxv4Kj6vnEtmJ JU5Qos030JTySc8Ygq+SeEKbigWDPh/Pmvf7T63y5MVBNwBz84Bn3QkB5H2pCwrN vP08TxI8GFE4gk5iOPTww0CB0zOqz2VuGHKdB/CBpl3sOgai8etT0ZPze7Y/BFqm ATsd8jFXMWNWTO0pHXjedzWws8kIJcUS6TKVXOlw8HSjkncdxZ9VeIXXoYfP23QW oMGVOttlaiXcYRvzZc8wR/74qM8q/ax5WXRHZoiPpLlRsk5uaYoaG0UiptAtuIK9 ByhPnORyT/zAWGsM8LyZaLHf6L0pOpoD8YrbnJ9qxNCZNtohx
Processed: Bug#1068737 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1068737 [locales] locales fails to install: locales failed to preconfigure, with exit status 2 Added tag(s) pending. -- 1068737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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 |
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/bui
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.
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
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
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
