Bug#977409: marked as done (libgm2-17: contains only libraries with SOVERSION 15)
Your message dated Wed, 16 Dec 2020 18:03:29 + with message-id and subject line Bug#977409: fixed in gcc-11 11-20201216-1 has caused the Debian Bug report #977409, regarding libgm2-17: contains only libraries with SOVERSION 15 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.) -- 977409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgm2-17 Version: 11-20201208-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships -rw-r--r-- root/root 31064 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2cor.so.15.0.0 -rw-r--r-- root/root189592 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2iso.so.15.0.0 -rw-r--r-- root/root 56168 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2log.so.15.0.0 -rw-r--r-- root/root 13968 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2min.so.15.0.0 -rw-r--r-- root/root172720 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2pim.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2cor.so.15 -> libm2cor.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2iso.so.15 -> libm2iso.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2log.so.15 -> libm2log.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2min.so.15 -> libm2min.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2pim.so.15 -> libm2pim.so.15.0.0 which is inconsistent with being renamed to libgm2-17. It also causes file conflicts with libgm2-15 in sid. Andreas --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 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: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 18:38:05 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-1 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-1) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GCC 10. Closes: #977408. * Don't install the lto-dump binary in the hppa64 package. Closes: #977461. * Let the gcn offload compilers conflict, both shipping the linker tools,
Bug#977461: marked as done (gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping unversioned binaries causes file conflicts)
Your message dated Wed, 16 Dec 2020 18:03:29 + with message-id and subject line Bug#977461: fixed in gcc-11 11-20201216-1 has caused the Debian Bug report #977461, regarding gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping unversioned binaries causes file conflicts 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.) -- 977461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcc-10-offload-amdgcn,gcc-11-offload-amdgcn,gcc-10-hppa64-linux-gnu,gcc-11-hppa64-linux-gnu Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 10.2.1-1 Control: found -1 11-20201208-1 Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../gcc-11-offload-amdgcn_11-20201208-1_amd64.deb ... Unpacking gcc-11-offload-amdgcn (11-20201208-1) ... dpkg: error processing archive /var/cache/apt/archives/gcc-11-offload-amdgcn_11-20201208-1_amd64.deb (--unpack): trying to overwrite '/usr/amdgcn-amdhsa/bin/ar', which is also in package gcc-10-offload-amdgcn 10.2.1-1 Errors were encountered while processing: /var/cache/apt/archives/gcc-11-offload-amdgcn_11-20201208-1_amd64.deb These unversioned files are in conflict between the gcc versions: usr/amdgcn-amdhsa/bin/ar usr/amdgcn-amdhsa/bin/as usr/amdgcn-amdhsa/bin/ld usr/amdgcn-amdhsa/bin/nm usr/amdgcn-amdhsa/bin/ranlib usr/bin/hppa64-linux-gnu-lto-dump Maybe the unversioned binaries should be managed by unversioned packages from gcc-defaults instead. cheers, Andreas gcc-10-offload-amdgcn=10.2.1-1_gcc-11-offload-amdgcn=11-20201208-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 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: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 18:38:05 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-1 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-1) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GC
Bug#977408: marked as done (libstdc++-11-doc: missing Conflicts: libstdc++-10-doc)
Your message dated Wed, 16 Dec 2020 18:03:29 + with message-id and subject line Bug#977408: fixed in gcc-11 11-20201216-1 has caused the Debian Bug report #977408, regarding libstdc++-11-doc: missing Conflicts: libstdc++-10-doc 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.) -- 977408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libstdc++-11-doc Version: 11-20201208-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libstdc++-11-doc_11-20201208-1_all.deb ... Unpacking libstdc++-11-doc (11-20201208-1) ... dpkg: error processing archive /var/cache/apt/archives/libstdc++-11-doc_11-20201208-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/C++Intro.3cxx.gz', which is also in package libstdc++-10-doc 10.2.1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libstdc++-11-doc_11-20201208-1_all.deb You should consider adding Conflicts+Replaces+Provides on some (internally used) virtual package to avoid running into this problem again in the future. cheers, Andreas libstdc++-10-doc=10.2.1-1_libstdc++-11-doc=11-20201208-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 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: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 18:38:05 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-1 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-1) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GCC 10. Closes: #977408. * Don't install the lto-dump binary in the hppa64 package. Closes: #977461. * Let the g
Processing of gcc-11_11-20201216-1_source.changes
gcc-11_11-20201216-1_source.changes uploaded successfully to localhost along with the files: gcc-11_11-20201216-1.dsc gcc-11_11-20201216.orig.tar.gz gcc-11_11-20201216-1.debian.tar.xz gcc-11_11-20201216-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
gcc-11_11-20201216-1_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 18:38:05 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-1 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-1) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GCC 10. Closes: #977408. * Don't install the lto-dump binary in the hppa64 package. Closes: #977461. * Let the gcn offload compilers conflict, both shipping the linker tools, which should be split out into a separate package. Addresses: #977461. * Regenerate libgm2/configure. Closes: #977409. * Install hwasan lib in libgcc-dev (arm64 only). Checksums-Sha1: 2ec3b284e1ea12503490e4cbd99ccc992f806699 27483 gcc-11_11-20201216-1.dsc a8c0f3092bb8e3ea0e0c3c5391da8aa956216a67 91182982 gcc-11_11-20201216.orig.tar.gz 2dc7b75178b160ca12d6689400e51c11f522ee42 521412 gcc-11_11-20201216-1.debian.tar.xz dff48f006843938c4986c91ffc2da65e255178d7 9403 gcc-11_11-20201216-1_source.buildinfo Checksums-Sha256: 5eb28f6d7f6fb2f8fbb28522a05a1737415337a44c69675c0525fcd975ce713c 27483 gcc-11_11-20201216-1.dsc 9b23fc23d5dbae41c18026134ca6e924ddc94f255f6c36a2efae8f3d3802ec4e 91182982 gcc-11_11-20201216.orig.tar.gz 786c167f426ae3456056cfc49d0c2fa260d679a42017210a6f84019f6a970675 521412 gcc-11_11-20201216-1.debian.tar.xz 1e75a780de132786fcba0ae3a31d280d0e1c2f98c69bd31361a980bd26705023 9403 gcc-11_11-20201216-1_source.buildinfo Files: 24c162f61c348d18acc4d3b6cf3e2146 27483 devel optional gcc-11_11-20201216-1.dsc 42f8393312b53b702af909517f09cd91 91182982 devel optional gcc-11_11-20201216.orig.tar.gz b8e3b5341cb3957ba981c6ff005ca63f 521412 devel optional gcc-11_11-20201216-1.debian.tar.xz 676699e6235d142c6a8faaf51a8acf53 9403 devel optional gcc-11_11-20201216-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl/aRisQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9Z/qEADWmmrpZADWoiTbsbsJ2ytqm3RbXeUKZJv+ f0VLW8lkBHfoERTxplVh8JTV06TzB3IMjS2ImLRo8LbLH4Fvp9LJrc3EdSNr7x3I Pg5BYnkR2m9Q73CvFYXZW8rbkKzVx/tuUhwn6sEpnUgrDs8icu5E5IeUC324+3gF 2zW0KufgayVcBo4VHSkRyuIFawGtb0maUB22G89UrGB2F7w5qjaTC7zerEWtQYCD v5vz+fae4ElZz2SUsbmBStrRFy1JG8Px3fmolYtUWWM1sYmfcXXobu4jukNwNPWm sDOelQPZXzksX1K2EX4RE4Gi4ez06mzoYbYnWj7/MoUs1+sAzD09GW3hhBrYjY1w jn3n5JxrcfSz7MVS/u2pjc3mvJrPWCmRFxtuP0jy/qxeGWa2AjYzqqlyu3QRzdhd 9uHbTaOQ5Jr+T438LyktSJc/YmvphaGfaDtHhvzVSILRIpVyAE5iYf+a0/F/dtkd lbpNNwRmU0m4btFbEh81h8NdOsopTwUEttMwYFWO1I8wsQsoAmHnCr8rOZMzXstX btWhYTMRqY0+ZefTcxfZjtTFfPpuZnmzmTOrFtpha7OegiMXL4XKKE9nq2+LgUKM sY1ktO1cMIFFP7JXv+DG+BTvwM4GnOIyMaAbZgoGFrWl8vWZCFZgTzPl1I+FHGBC AcnUds009g== =lDK/ -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#977560: dwz fails with .debug_line reference above end of section
Package: gcc-10 Version: 10.2.1-1 Severity: normal Affects: src:globus-rsl I recently updates some packages I maintain to compat level 13. Since they previously were on compat level 10, this meant that the dh_dwz that was added to the default sequence is now run for these packages. For most packages this did not create a problem. But for one of the packages the dh_dwz failed miserably. In the update for this package I added an empty override_dh_dwz rule to work around the problem. I don't know it the problem is with gcc producing broken debug information that is correctly rejected by dwz, or if it is dwz that fails to parse valid debug information generated by gcc. Please reassign the bug if appropriate. Steps to reproduce: Download affected package: $ dget https://deb.debian.org/debian/pool/main/g/globus-rsl/globus-rsl_11.2-1.dsc Enter the directory: $ cd globus-rsl-11.2 Edit the debian/rules file. Comment out the empty override_dh_dwz rule. $ emacs debian/rules Then build the package: $ dpkg-buildpackage The build ends in a failure: dh_dwz -a dwz: debian/libglobus-rsl2/usr/lib/debug/.dwz/x86_64-linux- gnu/libglobus-rsl2.debug: .debug_line reference above end of section dh_dwz: error: dwz -mdebian/libglobus-rsl2/usr/lib/debug/.dwz/x86_64- linux-gnu/libglobus-rsl2.debug -M/usr/lib/debug/.dwz/x86_64-linux- gnu/libglobus-rsl2.debug -- debian/libglobus-rsl2/usr/lib/x86_64-linux- gnu/libglobus_rsl.so.2.9.2 debian/libglobus-rsl2/usr/lib/x86_64-linux- gnu/libglobus_rsl_assist.so.2.9.2 returned exit code 1 make: *** [debian/rules:13: binary] Fel 1 dpkg-buildpackage: fel: fakeroot debian/rules binary subprocess returned exit status 2 $ dpkg-query -W gcc gcc-10 dwz binutils binutils2.35.1-4 dwz 0.13+20201015-2 gcc 4:10.2.0-1 gcc-10 10.2.1-1 signature.asc Description: This is a digitally signed message part
Processed: your mail
Processing commands for cont...@bugs.debian.org: > retitle 977560 gcc-10: dwz fails with .debug_line reference above end of > section Bug #977560 [gcc-10] dwz fails with .debug_line reference above end of section Changed Bug title to 'gcc-10: dwz fails with .debug_line reference above end of section' from 'dwz fails with .debug_line reference above end of section'. > retitle 977543 soundkonverter: Can't select two folders Bug #977543 [soundkonverter] soundkonverter: Can’t select two folders Changed Bug title to 'soundkonverter: Can't select two folders' from 'soundkonverter: Can’t select two folders'. > retitle 977542 golang-github-revel-revel: Depends on network in tests Bug #977542 [golang-github-revel-revel] golang-github-revel-revel - Depends on network in tests Changed Bug title to 'golang-github-revel-revel: Depends on network in tests' from 'golang-github-revel-revel - Depends on network in tests'. > retitle 977539 pkg-js-tools: use cp -rL for extcopies (needed for symlinks) Bug #977539 [pkg-js-tools] use cp -rL for extcopies (needed for symlinks) Changed Bug title to 'pkg-js-tools: use cp -rL for extcopies (needed for symlinks)' from 'use cp -rL for extcopies (needed for symlinks)'. > End of message, stopping processing here. Please contact me if you need assistance. -- 977539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977539 977542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977542 977543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977543 977560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977408: marked as done (libstdc++-11-doc: missing Conflicts: libstdc++-10-doc)
Your message dated Wed, 16 Dec 2020 20:48:46 + with message-id and subject line Bug#977408: fixed in gcc-11 11-20201216-2 has caused the Debian Bug report #977408, regarding libstdc++-11-doc: missing Conflicts: libstdc++-10-doc 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.) -- 977408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libstdc++-11-doc Version: 11-20201208-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libstdc++-11-doc_11-20201208-1_all.deb ... Unpacking libstdc++-11-doc (11-20201208-1) ... dpkg: error processing archive /var/cache/apt/archives/libstdc++-11-doc_11-20201208-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/C++Intro.3cxx.gz', which is also in package libstdc++-10-doc 10.2.1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libstdc++-11-doc_11-20201208-1_all.deb You should consider adding Conflicts+Replaces+Provides on some (internally used) virtual package to avoid running into this problem again in the future. cheers, Andreas libstdc++-10-doc=10.2.1-1_libstdc++-11-doc=11-20201208-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-2 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 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: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 21:28:34 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-2 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-2) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GCC 10. Closes: #977408. * Don't install the lto-dump binary in the hppa64 package. Closes: #977461. * Let the g
Bug#977409: marked as done (libgm2-17: contains only libraries with SOVERSION 15)
Your message dated Wed, 16 Dec 2020 20:48:46 + with message-id and subject line Bug#977409: fixed in gcc-11 11-20201216-2 has caused the Debian Bug report #977409, regarding libgm2-17: contains only libraries with SOVERSION 15 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.) -- 977409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgm2-17 Version: 11-20201208-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships -rw-r--r-- root/root 31064 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2cor.so.15.0.0 -rw-r--r-- root/root189592 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2iso.so.15.0.0 -rw-r--r-- root/root 56168 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2log.so.15.0.0 -rw-r--r-- root/root 13968 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2min.so.15.0.0 -rw-r--r-- root/root172720 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2pim.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2cor.so.15 -> libm2cor.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2iso.so.15 -> libm2iso.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2log.so.15 -> libm2log.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2min.so.15 -> libm2min.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2pim.so.15 -> libm2pim.so.15.0.0 which is inconsistent with being renamed to libgm2-17. It also causes file conflicts with libgm2-15 in sid. Andreas --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-2 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 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: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 21:28:34 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-2 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-2) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GCC 10. Closes: #977408. * Don't install the lto-dump binary in the hppa64 package. Closes: #977461. * Let the gcn offload compilers conflict, both shipping the linker tools,
Bug#977461: marked as done (gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping unversioned binaries causes file conflicts)
Your message dated Wed, 16 Dec 2020 20:48:46 + with message-id and subject line Bug#977461: fixed in gcc-11 11-20201216-2 has caused the Debian Bug report #977461, regarding gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping unversioned binaries causes file conflicts 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.) -- 977461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcc-10-offload-amdgcn,gcc-11-offload-amdgcn,gcc-10-hppa64-linux-gnu,gcc-11-hppa64-linux-gnu Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 10.2.1-1 Control: found -1 11-20201208-1 Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../gcc-11-offload-amdgcn_11-20201208-1_amd64.deb ... Unpacking gcc-11-offload-amdgcn (11-20201208-1) ... dpkg: error processing archive /var/cache/apt/archives/gcc-11-offload-amdgcn_11-20201208-1_amd64.deb (--unpack): trying to overwrite '/usr/amdgcn-amdhsa/bin/ar', which is also in package gcc-10-offload-amdgcn 10.2.1-1 Errors were encountered while processing: /var/cache/apt/archives/gcc-11-offload-amdgcn_11-20201208-1_amd64.deb These unversioned files are in conflict between the gcc versions: usr/amdgcn-amdhsa/bin/ar usr/amdgcn-amdhsa/bin/as usr/amdgcn-amdhsa/bin/ld usr/amdgcn-amdhsa/bin/nm usr/amdgcn-amdhsa/bin/ranlib usr/bin/hppa64-linux-gnu-lto-dump Maybe the unversioned binaries should be managed by unversioned packages from gcc-defaults instead. cheers, Andreas gcc-10-offload-amdgcn=10.2.1-1_gcc-11-offload-amdgcn=11-20201208-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-2 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 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: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 21:28:34 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-2 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-2) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GC
Processing of gcc-11_11-20201216-2_source.changes
gcc-11_11-20201216-2_source.changes uploaded successfully to localhost along with the files: gcc-11_11-20201216-2.dsc gcc-11_11-20201216-2.debian.tar.xz gcc-11_11-20201216-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
gcc-11_11-20201216-2_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 21:28:34 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-2 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-2) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GCC 10. Closes: #977408. * Don't install the lto-dump binary in the hppa64 package. Closes: #977461. * Let the gcn offload compilers conflict, both shipping the linker tools, which should be split out into a separate package. Addresses: #977461. * Regenerate libgm2/configure. Closes: #977409. * Install hwasan lib in libgcc-dev (arm64 only). Checksums-Sha1: 98014807ecca37c4b46e306c385602212e5982dd 27483 gcc-11_11-20201216-2.dsc 89aa93171e1aeb4aed585a7a7b77a81a90212d7c 521348 gcc-11_11-20201216-2.debian.tar.xz 901e558d4705962f01ee16f5d200262de39bcc8f 9403 gcc-11_11-20201216-2_source.buildinfo Checksums-Sha256: aac99ae64f76235669b49bbe2d52a04663b995dfada17e56dbdc06081d2b47a2 27483 gcc-11_11-20201216-2.dsc 4f7766079236fa6bf2ef08b1532b9f9792015ad0d91211641e7eddb08272d71b 521348 gcc-11_11-20201216-2.debian.tar.xz b5952cf0e1fe968ae330d2b8be644fb2b1e99b180af48cd62a336c2bc987b16a 9403 gcc-11_11-20201216-2_source.buildinfo Files: f5284d1cf48b4ab6b7fa41ff92a69702 27483 devel optional gcc-11_11-20201216-2.dsc 33744ed3bbaef2da705625f996b379c1 521348 devel optional gcc-11_11-20201216-2.debian.tar.xz b05357912d02136ce3ba7f21ed528d04 9403 devel optional gcc-11_11-20201216-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl/abjEQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9dn2D/973HttSa8lVp1dDuK6leo0kji0lrGTZzrZ eSmNeOIpv+OrsO+7/ureTjauDH4QuucOfCFIfWl/zKMIrqvdg/vwciz76jifv0GU LW1YW1iw3nBfM09VpOj/K/oui3nKcWxbbQ7LvZKm2s7xIAph54eR4MeMrhFIoZV7 E8M9vtZJJMirH6d0mQqpa3SRhYMdQjHqaucqYW/SSV4XeShWNYqf74MtyTZMyECO UdRNc7VunH2NMIq/5HRHBd9gHs67KvQubmU1+9f2sI0N87/I/aT7s/IWU7JXSPgb +4SyvakS1YwQAlcO+o6IuKjvXz3iBZyp3z69kNaAt0qCnjERXQ8sekjK6iDnhnzI 3TT/Ehglp/q3f7rG4zf9oyR2neIxKvVu1CZJgsdB4bQexDwFWSAddaAFWfPl6Uqf McMFC3WGMdi94AfkVQHf2CzfKavUvBSAR/Evhs7stvsV2JEYK5kfU8DcWkQIaNNR r5jZHXricWj+mdRA1uJnHqxNUWInQoIw7+s+pO+u0lTMJDShGwC9ZzNqpQWfrwU3 4wAf3KHYfyM0m7HDbLy8mLOXifT5jQDRZjLFlRr1OYR76EBLvz4aUVaRe6GfCCPw 653ets90Wpqg97i5ohdkyFSDsnXWrHdZm5Y6NeRZaoboRlrNjgI06tVCBJ47J1b/ SVe0U2EbtQ== =ZX1Y -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processed: Set affects properly
Processing commands for cont...@bugs.debian.org: > affects 977560 = src:globus-rsl Bug #977560 [gcc-10] gcc-10: dwz fails with .debug_line reference above end of section Added indication that 977560 affects src:globus-rsl > End of message, stopping processing here. Please contact me if you need assistance. -- 977560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
