Bug#1020486: marked as done (libffi-dev: Error in `/usr/share/doc-base/libffi-dev.libffi', line 18: all `Format' sections are invalid)
Your message dated Mon, 24 Oct 2022 09:58:24 +0200 with message-id <853820aa-ee68-d2d5-e450-062305db6...@debian.org> and subject line closing as requested by the bug submitter has caused the Debian Bug report #1020486, regarding libffi-dev: Error in `/usr/share/doc-base/libffi-dev.libffi', line 18: all `Format' sections are invalid 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.) -- 1020486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020486 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libffi-dev Version: 3.4.3-1 Severity: normal Dear Maintainer, on upgrade of libffi-dev 3.4.2-4 dpkg interrupts the configuration: " dpkg: error processing package libffi-dev:amd64 (--configure): dependency problems - leaving unconfigured Processing triggers for install-info (6.8-6) ... Processing triggers for doc-base (0.11.1) ... Processing 3 changed doc-base files... Error in `/usr/share/doc-base/libffi-dev.libffi', line 18: all `Format' sections are invalid. Note: `install-docs --verbose --check file_name' may give more details about the above error. " Thank you for your attention. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.10-deb64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libffi-dev depends on: iu libffi8 3.4.3-1 libffi-dev recommends no packages. libffi-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- closing as requested by the bug submitter--- End Message ---
Bug#1019535: gcc-12: please change the default hash style to both
Control: tags -1 +wontfix For about nine years we didn't see any issues with the default --hash-style=gnu. The trigger to expose that is the glibc change. That should be changed on the glibc side, either upstream, or in the glibc packaging. I don't see a benefit to change that on the GCC side after doing some Debian releases with these defaults.
Processed: Re: Bug#1019535: gcc-12: please change the default hash style to both
Processing control commands: > tags -1 +wontfix Bug #1019535 [src:gcc-12] gcc-12: please change the default hash style to both Bug #1020705 [src:gcc-12] glibc: Keep DT_HASH Added tag(s) wontfix. Added tag(s) wontfix. -- 1019535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019535 1020705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of libffi_3.4.4-1_source.changes
libffi_3.4.4-1_source.changes uploaded successfully to localhost along with the files: libffi_3.4.4-1.dsc libffi_3.4.4.orig.tar.gz libffi_3.4.4-1.debian.tar.xz libffi_3.4.4-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
libffi_3.4.4-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Oct 2022 10:26:41 +0200 Source: libffi Architecture: source Version: 3.4.4-1 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Changes: libffi (3.4.4-1) unstable; urgency=medium . * New upstream version. * Remove upstream fixes, now in the 3.4.4 release. Checksums-Sha1: dfcbb65ff9a96e2c3d6f9ea51b28ca5d74649e89 1951 libffi_3.4.4-1.dsc ecc58fb89aac4329b34dd019fe337d291b47c799 1362394 libffi_3.4.4.orig.tar.gz 02dbc0ec9926900ff91538a73a73b4d501eed68c 10380 libffi_3.4.4-1.debian.tar.xz 36275c6d00c90e2b5c68abf9d68ef45c7deef3c5 6960 libffi_3.4.4-1_source.buildinfo Checksums-Sha256: 21c9ef156b6766535cb014e0765142c8104ffbcd73f003ecfa80cfb314baa4f0 1951 libffi_3.4.4-1.dsc d66c56ad259a82cf2a9dfc408b32bf5da52371500b84745f7fb8b645712df676 1362394 libffi_3.4.4.orig.tar.gz 161b210bfd2ada0b15b0d2a2a98ffc779cd4a68661a7fdf46f61732493db0895 10380 libffi_3.4.4-1.debian.tar.xz 649a75ffb88719124af060b6d9657f01c84171405035382a1f5c5a31ff4daf18 6960 libffi_3.4.4-1_source.buildinfo Files: 2d1f0a4ba836a47e869607035d663426 1951 libs optional libffi_3.4.4-1.dsc 0da1a5ed7786ac12dcbaf0d499d8a049 1362394 libs optional libffi_3.4.4.orig.tar.gz f200c7e5ae99612f14955288a04ce1ad 10380 libs optional libffi_3.4.4-1.debian.tar.xz 1180c37301adb8e45cbd1708224b89b8 6960 libs optional libffi_3.4.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmNWTIcQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9ZNsEAC6Yb3fsoJSmmJ/ZV8nmD0Hj8uEXBwmfjr1 ym4V7sUKKL+yxILQOuG/iIGOO1U98VC493VmH8VtKSMWtUH6DmwuU2c6FQNzwyJ8 3uzplFRzM8pbsrz5oHeijZOaWSz0ioBwyzi2JSiqas9QMG2odjyikgilnZKddRV8 McKl4GpxijDbUBwbYVNy7GU+36MfWnjhvDBeAgZ/PqUBoxHhSEgJiEkAr+lbzWN4 cCM5cZJFioco4mzBfdEGUDWvuH/96a6jTskB8hs8GF7uSyKqkVDPUwOMKNUWifUM aOL0/dpn5Zk9aons+ewDpJhRkHxtWlBbbirbMnVaFGeP4bGta50+qqOfidzRiBJ2 EaTZ6fI0q7EM1HiS5zoa0MLAtxFy+E1E8Y+qA4hWQiTPlWjKoe5HjlrapIQfhPDI rGPZpYFT51ny5mRuVCPaUKFPRnAAlxiAk1mEE08wl1LdKPcZKWNMyaQbQkia513A cRmbPOssv0fgNssEKQqrTnCE1OqPR8+OCAZDVSLGIpi/9tDBAywa6vz1D9feSvlC YKsxXdk2Zagdgk4zk1iiswzCeF/RVGhR2qTgrWGY3jDMDuVLlJd2/2Bfa+9wCOD8 89JUWMMKw2xGoaCEwY6D5sIYiWMgKJWjs+xX0+quXDY9L3EZRsBvDLsb0fIgi34a jnoZCOjyJA== =07VI -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#1017141: marked as done (gcc-10-cross-mipsen: FTBFS: conftest.c:80: undefined reference to `fprintf_unlocked')
Your message dated Mon, 24 Oct 2022 20:50:36 +0200 with message-id and subject line no longer fails, closing has caused the Debian Bug report #1017141, regarding gcc-10-cross-mipsen: FTBFS: conftest.c:80: undefined reference to `fprintf_unlocked' 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.) -- 1017141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-10-cross-mipsen Version: 3+c5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /tmp/ccQguDRA.o: in function `main': > /<>/gcc/build/libcpp/conftest.c:80: undefined reference to > `fprintf_unlocked' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2022/08/13/gcc-10-cross-mipsen_3+c5_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Hi In the same build conditions, this package does not fail to build anymore, so closing. Lucas--- End Message ---
