Processed: Re: Bug#1003666: php-horde-crypt-blowfish: (autopkgtest) needs update for php8.1: deprecation warnings on stderr
Processing control commands:
> close -1
Bug #1003666 [src:php-horde-crypt-blowfish] php-horde-crypt-blowfish:
(autopkgtest) needs update for php8.1: deprecation warnings on stderr
Marked Bug as done
> fixed -1 1.1.4-1
Bug #1003666 {Done: Mike Gabriel }
[src:php-horde-crypt-blowfish] php-horde-crypt-blowfish: (autopkgtest) needs
update for php8.1: deprecation warnings on stderr
Marked as fixed in versions php-horde-crypt-blowfish/1.1.4-1.
--
1003666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1003652: php-horde-compress: (autopkgtest) needs update for php8.1: deprecation warnings on stderr
Processing control commands:
> close -1
Bug #1003652 [src:php-horde-compress] php-horde-compress: (autopkgtest) needs
update for php8.1: deprecation warnings on stderr
Marked Bug as done
> fixed -1 2.2.4-2
Bug #1003652 {Done: Mike Gabriel }
[src:php-horde-compress] php-horde-compress: (autopkgtest) needs update for
php8.1: deprecation warnings on stderr
Marked as fixed in versions php-horde-compress/2.2.4-2.
--
1003652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1003667: php-horde-data: (autopkgtest) needs update for php8.1: deprecation warnings on stderr
Processing control commands:
> close -1
Bug #1003667 [src:php-horde-data] php-horde-data: (autopkgtest) needs update
for php8.1: deprecation warnings on stderr
Marked Bug as done
> fixed -1 2.1.5-3
Bug #1003667 {Done: Mike Gabriel }
[src:php-horde-data] php-horde-data: (autopkgtest) needs update for php8.1:
deprecation warnings on stderr
Marked as fixed in versions php-horde-data/2.1.5-3.
--
1003667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1014768: marked as done (gnuradio: FTBFS on mipsel: undefined reference to `__atomic_load_8')
Your message dated Fri, 15 Jul 2022 02:48:27 + with message-id and subject line Bug#1014768: fixed in gnuradio 3.10.3.0-2 has caused the Debian Bug report #1014768, regarding gnuradio: FTBFS on mipsel: undefined reference to `__atomic_load_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.) -- 1014768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnuradio Version: 3.10.3.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=gnuradio=mipsel=3.10.3.0-1=1657488517=0 FAILED: gr-blocks/lib/blocks_qa_block_tags.cc : && /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized -fcx-limited-range -O3 -DNDEBUG -Wl,-z,relro gr-blocks/lib/CMakeFiles/blocks_qa_block_tags.cc.dir/qa_block_tags.cc.o -o gr-blocks/lib/blocks_qa_block_tags.cc -Wl,-rpath,/<>/obj-mipsel-linux-gnu/gr-blocks/lib:/<>/obj-mipsel-linux-gnu/gnuradio-runtime/lib:/<>/obj-mipsel-linux-gnu/gnuradio-runtime/lib/pmt gr-blocks/lib/libgnuradio-blocks.so.3.10.3.0 /usr/lib/mipsel-linux-gnu/libboost_unit_test_framework.so.1.74.0 gnuradio-runtime/lib/libgnuradio-runtime.so.3.10.3.0 gnuradio-runtime/lib/pmt/libgnuradio-pmt.so.3.10.3.0 /usr/lib/mipsel-linux-gnu/libboost_program_options.so.1.74.0 /usr/lib/mipsel-linux-gnu/libboost_thread.so.1.74.0 /usr/lib/mipsel-linux-gnu/libboost_atomic.so.1.74.0 /usr/lib/mipsel-linux-gnu/libspdlog.so.1.9.2 -lpthread /usr/lib/mipsel-linux-gnu/libfmt.so.8.1.1 -Wl,--as-needed /usr/lib/mipsel-linux-gnu/libgmpxx.so /usr/lib/mipsel-linux-gnu/libgmp.so -lrt /usr/lib/mipsel-linux-gnu/libvolk.so.2.5.1 -ldl -lm /usr/lib/mipsel-linux-gnu/libsndfile.so && : /usr/bin/ld: gr-blocks/lib/libgnuradio-blocks.so.3.10.3.0: undefined reference to `__atomic_load_8' /usr/bin/ld: gr-blocks/lib/libgnuradio-blocks.so.3.10.3.0: undefined reference to `__atomic_store_8' collect2: error: ld returned 1 exit status [403/1743] /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_TEST_DYN_LINK -DBOOST_TEST_MAIN -DBOOST_THREAD_DYN_LINK -DBOOST_UNIT_TEST_FRAMEWORK_DYN_LINK -DFMT_LOCALE -DFMT_SHARED -DGR_MPLIB_GMP -DGR_PERFORMANCE_COUNTERS -DHAVE_SF_FORMAT_OPUS -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB -I/<>/gr-blocks/lib/../include -I/<>/gnuradio-runtime/lib/../include -I/<>/obj-mipsel-linux-gnu/gnuradio-runtime/lib/../include -I/<>/gnuradio-runtime/lib/pmt/../../include -isystem /usr/include/python3.10 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized -fcx-limited-range -O3 -DNDEBUG -std=c++17 -MD -MT gr-blocks/lib/CMakeFiles/blocks_qa_gr_flowgraph.cc.dir/qa_gr_flowgraph.cc.o -MF gr-blocks/lib/CMakeFiles/blocks_qa_gr_flowgraph.cc.dir/qa_gr_flowgraph.cc.o.d -o gr-blocks/lib/CMakeFiles/blocks_qa_gr_flowgraph.cc.dir/qa_gr_flowgraph.cc.o -c /<>/gr-blocks/lib/qa_gr_flowgraph.cc [404/1743] /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_TEST_DYN_LINK -DBOOST_TEST_MAIN -DBOOST_THREAD_DYN_LINK -DBOOST_UNIT_TEST_FRAMEWORK_DYN_LINK -DFMT_LOCALE -DFMT_SHARED -DGR_MPLIB_GMP -DGR_PERFORMANCE_COUNTERS -DHAVE_SF_FORMAT_OPUS -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB -I/<>/gr-blocks/lib/../include -I/<>/gnuradio-runtime/lib/../include -I/<>/obj-mipsel-linux-gnu/gnuradio-runtime/lib/../include -I/<>/gnuradio-runtime/lib/pmt/../../include -isystem /usr/include/python3.10 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized -fcx-limited-range -O3 -DNDEBUG -std=c++17 -MD -MT gr-blocks/lib/CMakeFiles/blocks_qa_gr_hier_block2_derived.cc.dir/qa_gr_hier_block2_derived.cc.o -MF gr-blocks/lib/CMakeFiles/blocks_qa_gr_hier_block2_derived.cc.dir/qa_gr_hier_block2_derived.cc.o.d -o gr-blocks/lib/CMakeFiles/blocks_qa_gr_hier_block2_derived.cc.dir/qa_gr_hier_block2_derived.cc.o -c /<>/gr-blocks/lib/qa_gr_hier_block2_derived.cc [405/1743] /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_TEST_DYN_LINK -DBOOST_TEST_MAIN
Processed: tagging 1000932
Processing commands for cont...@bugs.debian.org: > tags 1000932 - patch pending Bug #1000932 [src:doxygen] doxygen: Please upgrade to llvm-toolchain-13 or 14 Removed tag(s) patch and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000932: doxygen: diff for NMU version 1.9.1-2.1
On 2022-07-14 16:23:16 +0200, Paolo Greppi wrote: > Hi Sebastian! > > Il 14/07/22 11:22, Sebastian Ramacher ha scritto: > > Control: tags 1000932 + patch > > Control: tags 1000932 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for doxygen (versioned as 1.9.1-2.1) and > > uploaded it to DELAYED/7. Please feel free to tell me if I > > should delay it longer. > > > > Cheers > > thanks for the quick patch; alas your fix will break this logic: > https://salsa.debian.org/debian/doxygen/-/blob/master/debian/rules#L23 > which was contributed by Norbert Lange to fix > https://bugs.debian.org/945427. > > At this point I am unsure what effects this may cause, I only vaguely > remember that the Clang_DIR and LLVM_DIR env vars plug into cmake somehow. > > So I'd propose to skip this NMU, as I'd rather address this as part of the > new upstream release (https://bugs.debian.org/1013636). > With each upstream release, I usually run massive archive rebuilds with ratt > which helps pinpoint which of the ~700 paackages that reverse-build-dep on > doxygen might fail when the new version is pushed through. ACK, I've canceled the NMU. Please consider that doxygen is a key package and thus effectively keeping llvm-toolchain-11 in testing. A timely fix for this issue would be much appreciated. Cheers -- Sebastian Ramacher
Processed: closing 1013502
Processing commands for cont...@bugs.debian.org: > # Fixed by src:python-django-compressor-4.0-1. > close 1013502 Bug #1013502 [src:python-django-libsass] python-django-libsass: FTBFS: ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/lib/python3/dist-packages/django/utils/encoding.py) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1013502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938351: marked as pending in renpy
Am Donnerstag, dem 14.07.2022 um 22:43 +0200 schrieb Moritz Mühlenhoff: > The latest 8.0.0 release now supports Python 3-based games: > https://www.renpy.org/release/8.0.0?mode=release-8=8.0.0 Hi Moritz, That's great news. Thanks for pointing it out. signature.asc Description: This is a digitally signed message part
Bug#1014736: marked as done (python3-hug,python3-hug-doc: both ship /usr/share/man/man1/hug.1.gz)
Your message dated Thu, 14 Jul 2022 20:49:32 + with message-id and subject line Bug#1014736: fixed in python-hug 2.6.0-2.4 has caused the Debian Bug report #1014736, regarding python3-hug,python3-hug-doc: both ship /usr/share/man/man1/hug.1.gz 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.) -- 1014736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-hug,python3-hug-doc Version: 2.6.0-2.3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-hug-doc_2.6.0-2.3_all.deb ... Unpacking python3-hug-doc (2.6.0-2.3) ... dpkg: error processing archive /var/cache/apt/archives/python3-hug-doc_2.6.0-2.3_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/hug.1.gz', which is also in package python3-hug 2.6.0-2.3 Errors were encountered while processing: /var/cache/apt/archives/python3-hug-doc_2.6.0-2.3_all.deb cheers, Andreas python3-hug=2.6.0-2.3_python3-hug-doc=2.6.0-2.3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-hug Source-Version: 2.6.0-2.4 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of python-hug, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated python-hug 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, 14 Jul 2022 15:48:12 -0400 Source: python-hug Architecture: source Version: 2.6.0-2.4 Distribution: unstable Urgency: high Maintainer: Federico Ceratto Changed-By: Boyuan Yang Closes: 1014736 Changes: python-hug (2.6.0-2.4) unstable; urgency=high . * Non-maintainer upload. * debian/rules: Only install hug.1 man page into python3-hug package. (Closes: #1014736) Checksums-Sha1: 3f35ce4106cb97d80333b51a53c864589e9daee7 2185 python-hug_2.6.0-2.4.dsc ca24f8203bcf4dd49ffa523394497d8b98d0f41c 2280727 python-hug_2.6.0.orig.tar.gz 1cb93c8af36c7d2402ed7cfd415c14141043f975 3476 python-hug_2.6.0-2.4.debian.tar.xz fde6ae9062f3434e016f11208352bb590fe98786 9149 python-hug_2.6.0-2.4_amd64.buildinfo Checksums-Sha256: 33d09bba028543685f97a7fcc2064570b36cc8be9f29fb2d75b494a56e7d96c7 2185 python-hug_2.6.0-2.4.dsc c54b04ed5ce0e436ddf9e8e00f838b4ed740a914cf3af9bef055e11375fc1ebe 2280727 python-hug_2.6.0.orig.tar.gz 0cae2ca32aa3ddb9399debb7b174f7cc924fb109ac4d7e9d5e999cac8c274266 3476 python-hug_2.6.0-2.4.debian.tar.xz 080b3830cdf2a1818d7ee5a9f3750f1410a131d5b262730a02f0e56ed59c2610 9149 python-hug_2.6.0-2.4_amd64.buildinfo Files: 67b0a7096a16ca9768d4ddb7cc3b9be3 2185 python optional python-hug_2.6.0-2.4.dsc fcf8b515fd1abb3045669518438e77dc 2280727 python optional python-hug_2.6.0.orig.tar.gz d77247b9662282617dff8ab9892941cc 3476 python optional python-hug_2.6.0-2.4.debian.tar.xz 950f7e1fb81f3d40830063aa6476324c 9149 python optional python-hug_2.6.0-2.4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmLQdDIACgkQwpPntGGC Ws4K5hAAwx6bc9bCc6nRqBVmrzQ0jqGZFN5JIYLawAHc3qArZCh3rEnpolP0CWtc DXs8agiBdJ0yTFOP/qo0RxoS7hXEuo7hjY4MX4kSfEV8UHvCjOSs+nvuVUKROsaT v01u8AFcG5mGIAZkNG/yDbDBo3ztRX1yUa5HbwpJaJ+PwX7AVmMAeIFtOkOK+1LS QflSADN+F1TklJRujcFGa2WCLNy5lhFFTI7msavp/S66HS07t0N6EEnh31UJnIzM t3n17w74SsQb1tE2MfWwohyDVG64KEzn5QAGjJLkJ67wBdzP1YSlylU9NCW4tYD2 LYDg2DRVsuH6wwJDXQ6+4xZEVfiZtNNS6/PhTiDhen+BGajN3SKVsZwk+DPBR/8o SJc/aFbyL0cWfjBaqAmg0uBJZMmdVwenv58ZiCPsyrKHOKNgXqSHEyL6Kgn7EWvt JZdHARg4N0m98qZ0zasXRMAkr/5Qx1kCdbHO96bQPonU4MQNqtMT2irEGEq9WCzm 7eCJKmdFbDcj2Zo3p6tMtBUW6yk3b62gszXRyniRTxbcuhEUwRDabuAc1Oahqxrd 6pBxWRsLo7d5dYjxyPd+0z9LoyR1cjoeR9eA1eD/WWCnevgxLsBNMZc0aRGNswr7 5uVL8NZWM1eoU06hhJ1TubSOFLPp0Wunpz0HStT8vdQzlP/X8D8= =0/ma -END PGP SIGNATURE End Message ---
Bug#938351: marked as pending in renpy
Am Sat, Dec 18, 2021 at 03:46:28PM +0100 schrieb Markus Koschany: > Renpy still has not been ported to Python 3 yet. The status of renpy and other > Python 2 games was previously discussed on debian-devel-games. > > https://lists.debian.org/debian-devel-games/2020/12/msg00013.html > > A removal request was filed: > > https://bugs.debian.org/1001888 > > > I don't think a removal is necessary at the moment. If we remove the game and > the Python 3 port would be finished in time, we had to go through NEW again. > This is just extra work for all involved parties. I intend to request the > removal at the end of 2022, if there is no visible upstream progress though. The latest 8.0.0 release now supports Python 3-based games: https://www.renpy.org/release/8.0.0?mode=release-8=8.0.0 Cheers, Moritz
Bug#1014846: marked as done (rush: FTBFS on s390x)
Your message dated Thu, 14 Jul 2022 19:50:23 + with message-id and subject line Bug#1014846: fixed in rush 2.2-2 has caused the Debian Bug report #1014846, regarding rush: FTBFS on s390x 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.) -- 1014846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rush Severity: serious Version: 2.2-1 rush does not build on s390x due to a test error: 45: remopt FAILED (remopt.at:53) See https://buildd.debian.org/status/fetch.php?pkg=rush=s390x=2.2-1=1657661702=0 This keeps the package from migrating to testing. --- End Message --- --- Begin Message --- Source: rush Source-Version: 2.2-2 Done: Bo YU We believe that the bug you reported is fixed in the latest version of rush, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bo YU (supplier of updated rush 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, 14 Jul 2022 15:30:00 +0800 Source: rush Architecture: source Version: 2.2-2 Distribution: unstable Urgency: medium Maintainer: Bo YU Changed-By: Bo YU Closes: 1014846 Changes: rush (2.2-2) unstable; urgency=medium . * Fix ftbfs on s390x (Closes: #1014846) * Update upstream metafile Checksums-Sha1: eca541ab9ef8ca9a5926a0f6a71d73e6b85fe76a 1630 rush_2.2-2.dsc 57f522eff70b3223a5b0f7d685d8db255ec633df 22592 rush_2.2-2.debian.tar.xz 3100fab3b12c9d40794f150cb1c1d6575fe17e6c 5729 rush_2.2-2_source.buildinfo Checksums-Sha256: 67d6c34203e1a4042ffae46e41ea1dbedf3a195fcadd61ba9180038c0ef30bdc 1630 rush_2.2-2.dsc 8cb30da72c80a2fb2dc108293fdc7d878224a26b76602e8e82a7ce618f223d4f 22592 rush_2.2-2.debian.tar.xz 95cab31487e021a55e232e3c5a7a77c3102e64648c6acdd0383f4f05f2f9b4f1 5729 rush_2.2-2_source.buildinfo Files: f7671c4109d637cdba8e69479b225e34 1630 shells optional rush_2.2-2.dsc 75c2479275fbf02706c6a5abdda732ea 22592 shells optional rush_2.2-2.debian.tar.xz 9cda3d1055e3fc0266e06b203d2ffc6a 5729 shells optional rush_2.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmLQch4QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFEhUC/4k6HDOnnlK27T/7xW1/9mOLZPDpixSyCNG iuNAkUUj7PbmqECq4nIW8nGSqnrGtbD/oaj24/VcmqTuENQdU7ox+9x1XoDBiBla MfU/q2SQ2nWCvbvv2SlPtRqdWnM6U+x9+Dws5D4q9P6x2Sqcme4C9NRfN/vEa3u0 +2Rsgqq41GreiapC6aF4OHFyhL0jk/w7rwVbzzJeMcmTJQD6JwGH0ITg9g3FwIV9 IswKzDRc0RlAY31USH6IW2WakvDSJA0u52E+cyFsjeM0cyw+k7gPkLAtQ+yD6zT2 0WxlTq8uN/7zagv9c5Rw6ocsRu88WxfvEk5OaZeLtc5e7M6JvfgEOnitwGmVMUe2 UQy78cWVDgGhqkv16Pw2meC7lZXQVdqrAV5Tlf2E4TkO3TxkZ2M/P4ETtZBjb15G A32lzot7WRNcm4RVSpmqyuxcnhMDgnt146wQegxWCg878cobzWTMZyWbIZUxEdEr IcLEs2nYzIRRlYEp86YuYLpTJDMHGxY= =L5P6 -END PGP SIGNATURE End Message ---
Processed: closing 1013497
Processing commands for cont...@bugs.debian.org: > # Resolved in #1013742. > close 1013497 Bug #1013497 [src:djangorestframework] django-countries: FTBFS: ModuleNotFoundError: No module named 'pytz' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1013497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1013497
Processing commands for cont...@bugs.debian.org:
> # Resolved in #1013742.
> close 1013497
Bug #1013497 {Done: Michael Fladischer }
[src:djangorestframework] django-countries: FTBFS: ModuleNotFoundError: No
module named 'pytz'
Bug 1013497 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1013527
Processing commands for cont...@bugs.debian.org:
> # Resolved in #1013742.
> close 1013527
Bug #1013527 [src:djangorestframework] djangorestframework: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9
3.10" returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1013471
Processing commands for cont...@bugs.debian.org: > # Resolved in #1013742. > close 1013471 Bug #1013471 [src:drf-extensions] drf-extensions: FTBFS: ModuleNotFoundError: No module named 'pytz' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1013471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014933: gnome-user-share: needs to be ported to gtk4
Source: gnome-user-share Version: 3.34.0-5 Severity: serious gnome-user-share will need to be ported to gtk4 because nautilus 43 will be using gtk4 Thank you, Jeremy Bicha
Bug#1014919: marked as done (libflint17 is incorrectly marked Multi-Arch: same)
Your message dated Thu, 14 Jul 2022 19:19:54 + with message-id and subject line Bug#1014919: fixed in flint 2.9.0-4 has caused the Debian Bug report #1014919, regarding libflint17 is incorrectly marked Multi-Arch: same 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.) -- 1014919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libflint17 Version: 2.9.0-2 Severity: serious /usr/lib/x86_64-linux-gnu/libflint-2.8.5.so.16.1.5 -> /usr/lib/libflint.so.17.0.0 It was likely unintentional that the library moved to a non-multiarch location in https://salsa.debian.org/math-team/flint/-/commit/5cee4678c1eb7699283418f9b48b2b59ac1c35f0 --- End Message --- --- Begin Message --- Source: flint Source-Version: 2.9.0-4 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of flint, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated flint 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, 14 Jul 2022 20:58:01 +0200 Source: flint Architecture: source Version: 2.9.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Math Team Changed-By: Julien Puydt Closes: 1014919 Changes: flint (2.9.0-4) unstable; urgency=medium . * Fix multiarch (Closes: #1014919). * Add patch to remove rpath linking switch. Checksums-Sha1: fb8cb823c7e9e9b5fdf50ec58f40b5fd8b54c6ff 2194 flint_2.9.0-4.dsc 43d569d05c59228f97b81e16dde8d41327e4be3c 8652 flint_2.9.0-4.debian.tar.xz 6b4cf891974053df18ba3126e6a10b45c8f9cfea 9692 flint_2.9.0-4_source.buildinfo Checksums-Sha256: ad658433bfb3482a3c543a730aa81a708a5676771228efb96424c8ee9c1323cf 2194 flint_2.9.0-4.dsc 09cebdae370967a0c109ff2a08ec2ecb058e23ae2b2ed4549eb1a9c2ff40c4ba 8652 flint_2.9.0-4.debian.tar.xz 4fdd6b7885b83c3c8019090fbf36b9d1adccea7425dec83be548e29af85fce4c 9692 flint_2.9.0-4_source.buildinfo Files: 7f53d39d378042144d38dc88e5d9d96e 2194 math optional flint_2.9.0-4.dsc 115389f428ffa6cbde70f9c6139d09ff 8652 math optional flint_2.9.0-4.debian.tar.xz 9521cef836993a494cd1387faf2f9841 9692 math optional flint_2.9.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmLQZ38SHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRqWkP/RaFBlM1CAHH5mW0uVZsFvxpet7zNpFJ 9ygt8I1gwlVWbkwMtwuKZsEzNCOE7ZGW6JQaomkIXNVjq8gOVpb2acPkqY5bH4al 74+W0S4yBzOJKZmuI3tA6tT8CZzbYq7VzAdZqsX/UTFPYiZgmZMxObhb6y46crYA cB1LJlFjT5PjQeTLd9YWIhzrssBDKsK5dyrEEdxQ3HqVr/uWTjxy9iRehOZSyH6X PRaQJGwEPiSVpeja7fbq6X0hF7GlvAOPo7fEH3GFRerdEr8HiwwV22CzX5yHbcdl upi6IMmJaePGnZzfhT1Vtvw08aLsGUVGHCITsVn4Z2f14emlEUHj0d+4/a/3TTIP Vhm3ppP3FSKBnO+9g2Yxk5M51c7nRxsCxeK85KV7qbl9K6Jx5r/iSnawnqP8b5Gd DmZ0In0aKEdta3q4aJr7dmTnUPEv5mSat1AD362jsxAWsbYKPKOrE7SJicGeIaDh WGpiXHFaTLr/BCbLcCvbgrUpW/L/HXFR8HIxQyiWXFTm84IewV2XwSiGkAw6QJvw WsAY4hWUTKlKibPS3UMSWyBd+0UaCm/hipCp4Hyzm0MI3NMoU8iqJkCqY1XEj75+ VaaLlJ0DeKIgjyl7bPpUhBR7ySYjFKOwNejLjyR8N7qMgGVkxKezVJ/teCgYyKTs OgCb81dEPfou =Fl77 -END PGP SIGNATURE End Message ---
Processed: severity of 1014928 is serious
Processing commands for cont...@bugs.debian.org: > severity 1014928 serious Bug #1014928 [fcitx5-config-qt] fcitx5-config-qt: Unneeded/unwanted/bloating dependency on libkf5plasma5 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1014928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006505: marked as done (libsecp256k1: FTBFS with OpenSSL 3.0)
Your message dated Thu, 14 Jul 2022 18:20:14 + with message-id and subject line Bug#1006505: fixed in libsecp256k1 0.1~20220711-1 has caused the Debian Bug report #1006505, regarding libsecp256k1: FTBFS with OpenSSL 3.0 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.) -- 1006505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libsecp256k1 Version: 0.1~20210825-2 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Your package is failing to build using OpenSSL 3.0 with the following error: |dh_auto_test | make -j1 check VERBOSE=1 | make[1]: Entering directory '/<>' | make check-TESTS | make[2]: Entering directory '/<>' | make[3]: Entering directory '/<>' | ./build-aux/test-driver: line 112: 3364063 Aborted "$@" >> "$log_file" 2>&1 | FAIL: tests | PASS: exhaustive_tests | |libsecp256k1 0.1: ./test-suite.log | | | # TOTAL: 2 | # PASS: 1 | # SKIP: 0 | # XFAIL: 0 | # FAIL: 1 | # XPASS: 0 | # ERROR: 0 | | .. contents:: :depth: 2 | | FAIL: tests | === | | test count = 64 | random seed = a7f0a08ee8e02ae3d0de647dc2d533f1 | Failure 10 on 30 30 02 1b 00 c7 ff ff ff fd ff ff ff ff 8e 5c ff ff f9 f0 00 00 00 80 15 ef ff ff ff ff ff 02 11 f9 ff ff ff 03 00 00 00 00 f0 ff ff ef ff 01 e7 00 | src/tests.c:6015: test condition failed: ret == 0 | FAIL tests (exit status: 134) | | | Testsuite summary for libsecp256k1 0.1 | | # TOTAL: 2 | # PASS: 1 | # SKIP: 0 | # XFAIL: 0 | # FAIL: 1 | # XPASS: 0 | # ERROR: 0 | | See ./test-suite.log | | make[3]: *** [Makefile:1307: test-suite.log] Error 1 | make[3]: Leaving directory '/<>' | make[2]: *** [Makefile:1415: check-TESTS] Error 2 | make[2]: Leaving directory '/<>' For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Sebastian --- End Message --- --- Begin Message --- Source: libsecp256k1 Source-Version: 0.1~20220711-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of libsecp256k1, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated libsecp256k1 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, 14 Jul 2022 19:33:49 +0200 Source: libsecp256k1 Architecture: source Version: 0.1~20220711-1 Distribution: unstable Urgency: medium Maintainer: Debian Cryptocoin Team Changed-By: Bastian Germann Closes: 1006505 Changes: libsecp256k1 (0.1~20220711-1) unstable; urgency=medium . * Team upload * New upstream version 0.1~20220711 (Closes: #1006505) * symbols: Add new secp256k1_schnorrsig_sign32 Checksums-Sha1: e34c93126ffae762fe69250fbfa30d8f606c1791 2005 libsecp256k1_0.1~20220711-1.dsc d828cb35aaa1f36e8cd5d9023226eb352a612487 2201956 libsecp256k1_0.1~20220711.orig.tar.xz 9b68795ef10705355191f7a60a0591db6edf2e9e 8352 libsecp256k1_0.1~20220711-1.debian.tar.xz e142c8f52ec0f460c8a7bc7af1f5f0e2306b3c69 6690 libsecp256k1_0.1~20220711-1_source.buildinfo Checksums-Sha256: c8b0054d4c8f7dba1d1dcbe65650066575179471f4b185b78c2cd42b5cf15722 2005 libsecp256k1_0.1~20220711-1.dsc 1e350c1d66b304525e2534d4501749d9524e55d71719ca843ea87a3594f6ae8b 2201956 libsecp256k1_0.1~20220711.orig.tar.xz c910c15ee81698df6c3b8744f59e2520f87a574501693e2c25c5a51ddc6cc954 8352 libsecp256k1_0.1~20220711-1.debian.tar.xz 7b2c3c5f71a3939871af8e3f1880f16c59169bb8a22eff01f058f9f62874de6e 6690 libsecp256k1_0.1~20220711-1_source.buildinfo Files: 8916d92279b0f59c74cfa679f6759e2c 2005 libs optional libsecp256k1_0.1~20220711-1.dsc 283c2a5fb5bae4c51da28529af808575
Processed: [bts-link] source package thunderbird
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package thunderbird > # 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 #1014675 (http://bugs.debian.org/1014675) > # Bug title: thunderbird: Upgrade breaks NNTP > # * https://bugzilla.mozilla.org/show_bug.cgi?id=1745033 > # * remote status changed: (?) -> REOPENED > usertags 1014675 + status-REOPENED There were no usertags set. Usertags are now: status-REOPENED. > # remote status report for #1014745 (http://bugs.debian.org/1014745) > # Bug title: thunderbird: Using "Reply All" is sometimes removing all Cc > recipients > # * https://bugzilla.mozilla.org/show_bug.cgi?id=1777683 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 1014745 + fixed-upstream Bug #1014745 [thunderbird] thunderbird: Using "Reply All" is sometimes removing all Cc recipients Added tag(s) fixed-upstream. > usertags 1014745 + 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. -- 1014745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:dlt-daemon
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:dlt-daemon > # 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 #1014534 (http://bugs.debian.org/1014534) > # Bug title: dlt-daemon: CVE-2022-31291 > # * https://github.com/COVESA/dlt-daemon/pull/376 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1014534 + fixed-upstream Bug #1014534 [src:dlt-daemon] dlt-daemon: CVE-2022-31291 Added tag(s) fixed-upstream. > usertags 1014534 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:ruby-webauthn
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ruby-webauthn > # 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 #1005444 (http://bugs.debian.org/1005444) > # Bug title: ruby-webauthn: FTBFS: ERROR: Test "ruby3.0" failed: > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `rescue in block > in activate_dependencies': Could not find 'openssl' (~> 2.0) among 104 total > gem(s) (Gem::MissingSpecError) > # * https://github.com/cedarcode/webauthn-ruby/issues/359 > # * remote status changed: open -> closed > # * closed upstream > tags 1005444 + fixed-upstream Bug #1005444 [src:ruby-webauthn] ruby-webauthn: FTBFS: ERROR: Test "ruby3.0" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `rescue in block in activate_dependencies': Could not find 'openssl' (~> 2.0) among 104 total gem(s) (Gem::MissingSpecError) Added tag(s) fixed-upstream. > usertags 1005444 - status-open Usertags were: status-open. There are now no usertags set. > usertags 1005444 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1005444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014690: llvmlite breaks numba autopkgtest: segmentation fault
On Thu, 2022-07-14 at 10:10 +0200, Paul Gevers wrote: > Control: reassign 1014690 src:llvmlite 0.38.1-2 > Control: affects 1014690 src:numba > Control: fixed 1014690 0.38.1-3 > > Hi Diane, > > On 14-07-2022 05:26, Diane Trout wrote: > > I know there's some problems with some of numba's autopkgtests but > > I > > couldn't reproduce the segmentation fault. > > That's because Mo reverted the change to use llvm-toolchain-13 in > llvmlite. > > > llvmlite's tracker suggests that the tests are passing now? > > > > Did you find a solution or is this likely to be a random problem? > > Well, reverting reopened another issue we have which is that we want > to > drop llvm-toolchain-11 from testing. In that case what about submitting the llvm-toolchain-13 version of llvmlite to experimental to start the process of trying to fix what it breaks? Diane signature.asc Description: This is a digitally signed message part
Bug#1014841: workaround
Since this has persisted for a couple days and prevents any security updates, here's a workaround (for people who find this bug report after a web search): dpkg --purge --force-all libguvcview-2.0-2 apt --fix-broken install
Processed: bug 1014768 is forwarded to https://salsa.debian.org/bottoms/pkg-gnuradio/-/merge_requests/2
Processing commands for cont...@bugs.debian.org: > forwarded 1014768 > https://salsa.debian.org/bottoms/pkg-gnuradio/-/merge_requests/2 Bug #1014768 [src:gnuradio] gnuradio: FTBFS on mipsel: undefined reference to `__atomic_load_8' Set Bug forwarded-to-address to 'https://salsa.debian.org/bottoms/pkg-gnuradio/-/merge_requests/2'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014917: marked as done (libflint17 lacks SONAME)
Your message dated Thu, 14 Jul 2022 15:34:13 + with message-id and subject line Bug#1014917: fixed in flint 2.9.0-3 has caused the Debian Bug report #1014917, regarding libflint17 lacks SONAME 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.) -- 1014917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libflint17 Version: 2.9.0-2 Severity: grave Tags: ftbfs Control: affects src:antic src:flint-arb src:linbox src:calcium src:e-antic src:gyoto src:normaliz src:singular src:macaulay2 src:polymake src:sagemath $ objdump -p /usr/lib/x86_64-linux-gnu/libflint-2.8.5.so.16.1.5 | grep SONAME SONAME libflint-2.8.5.so $ objdump -p /usr/lib/libflint.so.17.0.0 | grep SONAME $ One of the problems this causes is that reverse dependencies do not get a shlibs-generated dependency on libflint17. debian/rules sets EXTRA_SHARED_FLAGS (to avoid the rpath?), but upstream configure also uses it to set -soname and https://salsa.debian.org/math-team/flint/-/commit/ea3ae82694953d6386898f051dd9b1b2f111dfaa removed the code correcting that. --- End Message --- --- Begin Message --- Source: flint Source-Version: 2.9.0-3 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of flint, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated flint 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, 14 Jul 2022 17:08:12 +0200 Source: flint Architecture: source Version: 2.9.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Math Team Changed-By: Julien Puydt Closes: 1014917 Changes: flint (2.9.0-3) unstable; urgency=medium . * Drop references to EXTRA_SHARED_FLAGS from d/rules (Closes: #1014917). Checksums-Sha1: b978f455c22e83472b9b890f9c8b827be7f092fa 2194 flint_2.9.0-3.dsc 66790716794ea43f8e0dd5eaacca5f7cf04ae91c 8332 flint_2.9.0-3.debian.tar.xz cde949f65bcb0702d36c2aae7aeff93c34925302 9692 flint_2.9.0-3_source.buildinfo Checksums-Sha256: 5aa85b9d67bd3e8fc8bea48df89e28d819eddd3f5023ec61ca64452d1cf93b71 2194 flint_2.9.0-3.dsc eb3bb37c3b091e09c04824c9924d1bec507d728f43fbbeba174971206a9263d1 8332 flint_2.9.0-3.debian.tar.xz 9e589302a5907c479ad1aa067ce33ebe4eb109495d032c5ca49b01cc39d38c8f 9692 flint_2.9.0-3_source.buildinfo Files: f424152995f1e142972575ae0f35c0cb 2194 math optional flint_2.9.0-3.dsc 86a55cdc539b55893ba1abd2b1afb030 8332 math optional flint_2.9.0-3.debian.tar.xz 988fcfad60c8b0da768f67d13547e1ed 9692 math optional flint_2.9.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmLQMaMSHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRMuAQAIxn9Q8Vf4IwvNHA3efcRQ9ObIutn6Kq kt6LqkfL6qit2oUYsxRpEx3xN9r/RCz9yZoZ9jKNsxB1oREbByZfg7EcIy8GugXN kJoKPTI1hpt7iL2fs5tsSRanuf9vSRTpVs1hfoNSaNN+P5fd77Z+1yJMpEOP52PI PJF1OFqYfaXwTW0k7yZ8SU3PWWBfqlDUKMUoXHBbVJq86xuFodv5j5j69SBo+ZJP F68Itb77Mh5x7yiZ0MaUN10E5OsQUx/vjLCGiQVPbXJ2i9lQOSdQCZLjxluCrnwp wXAvU8PO+jIo3afVFBujLyXXPn342qFDB2YXiIaJh0MYZ6di/iPsXmYXTLj+mgwo +gOm2TbZh9PefkzEOrOlt432r1LLvMPM9FEs4RIAOBLrAlO7mhCratXYDa4VCaBU QcyeqH6H1W/07kZqLhC3xptlN28RECtXdznWKOvTKP7nQh5sClsUV5ZC5WxNHBNg 4cepWUy+z9rj9tsGuEeFane0CSL7XfFQKJ9Oe5hX/JO+q1UJ93CrpDq1o2L3bMDN P4YhqhJSDj1IDAnYfcXHAO3J0FiM7Sx4WjZyShE0uDb5ow1W+9ZJALm8ByKftFTe 4NY9YrMRtOymFww3P2+mKM7YuTOiQk/HgJJsRrru/lX0OhBhYl84r77UH+FdgNzI rdQqK1+pKuLy =A0D2 -END PGP SIGNATURE End Message ---
Bug#1014924: gtk-gnutella: FTBFS with glibc >= 2.34
Package: gtk-gnutella
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Hi,
This is technically not a problem in Debian yet, since sid is on glibc
2.33. But, once glibc >= 2.34 is in place, this package will FTBFS. The
cause is that gtk-gnutella uses preprocessor directives to check
PTHREAD_STACK_MIN at compile time, but in glibc >= 2.34,
PTHREAD_STACK_MIN may be dynamic and cannot be checked at compile time.
In Ubuntu, we pulled an upstream patch to fix compilation with newer
glibc:
* debian/patches/0001-Fix-compilation-with-newest-glibc.patch: Fix FTBFS
against glibc >= 2.34 by checking dynamically-defined PTHREAD_STACK_MIN
at run time instead of compile time (LP: #1981474).
This patch should be safe for glibc < 2.34 as well.
Thanks,
Nick
diff -Nru
gtk-gnutella-1.1.15/debian/patches/0001-Fix-compilation-with-newest-glibc.patch
gtk-gnutella-1.1.15/debian/patches/0001-Fix-compilation-with-newest-glibc.patch
---
gtk-gnutella-1.1.15/debian/patches/0001-Fix-compilation-with-newest-glibc.patch
1969-12-31 19:00:00.0 -0500
+++
gtk-gnutella-1.1.15/debian/patches/0001-Fix-compilation-with-newest-glibc.patch
2022-07-12 14:20:53.0 -0400
@@ -0,0 +1,63 @@
+Description: Fix compilation with newest glibc
+ The PTHREAD_STACK_MIN value is no longer a constant but rather
+ defined as sysconf(_SC_THREAD_STACK_MIN).
+Author: Raphael Manfredi
+Origin: upstream,
https://github.com/gtk-gnutella/gtk-gnutella/commit/31d06cecac572852c6e5e8d85cea641883cbe4c6
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gtk-gnutella/+bug/1981474
+Last-Update: 2022-07-12
+---
+From: Raphael Manfredi
+Date: Mon, 9 Aug 2021 09:36:00 +0200
+Subject: [PATCH] Fix compilation with newest glibc.
+
+The PTHREAD_STACK_MIN value is no longer a constant but rather
+defined as sysconf(_SC_THREAD_STACK_MIN).
+
+Therefore, we must avoid using cpp computations on that value.
+---
+ src/lib/thread.c | 7 +--
+ src/lib/thread.h | 2 +-
+ 2 files changed, 2 insertions(+), 7 deletions(-)
+
+diff --git a/src/lib/thread.c b/src/lib/thread.c
+index 178c09794..e7a702029 100644
+--- a/src/lib/thread.c
b/src/lib/thread.c
+@@ -9705,7 +9705,7 @@ thread_launch_trampoline(void *arg)
+ * In case PTHREAD_STACK_MIN is not defined by .
+ */
+ #ifndef PTHREAD_STACK_MIN
+-#define PTHREAD_STACK_MIN 0
++#define PTHREAD_STACK_MIN 1024U
+ #endif
+
+ /**
+@@ -9737,12 +9737,7 @@ thread_launch(struct thread_element *te,
+ pthread_attr_init();
+
+ if (stack != 0) {
+- /* Avoid compiler warning when PTHREAD_STACK_MIN == 0 */
+-#if PTHREAD_STACK_MIN != 0
+ stacksize = MAX(PTHREAD_STACK_MIN, stack);
+-#else
+- stacksize = stack;
+-#endif
+ stacksize = MAX(stacksize, THREAD_STACK_MIN);
+ } else {
+ stacksize = MAX(THREAD_STACK_DFLT, PTHREAD_STACK_MIN);
+diff --git a/src/lib/thread.h b/src/lib/thread.h
+index 73e15fa36..740f3a6f9 100644
+--- a/src/lib/thread.h
b/src/lib/thread.h
+@@ -63,7 +63,7 @@ typedef size_t thread_qid_t; /* Quasi Thread ID */
+ typedef unsigned int thread_key_t;/* Local thread storage key */
+
+ #define THREAD_MAX64 /**< Max amount of
threads we can track */
+-#define THREAD_STACK_DFLT (65536 * PTRSIZE) /**< Default stack
requested */
++#define THREAD_STACK_DFLT (65536U * PTRSIZE) /**< Default stack
requested */
+ #define THREAD_LOCAL_MAX 1024/**< Max amount of thread-local keys */
+
+ #define THREAD_SUSPEND_TIMEOUT90 /**< secs: thread max
suspension time */
+--
+2.34.1
+
diff -Nru gtk-gnutella-1.1.15/debian/patches/series
gtk-gnutella-1.1.15/debian/patches/series
--- gtk-gnutella-1.1.15/debian/patches/series 2020-02-26 04:01:31.0
-0500
+++ gtk-gnutella-1.1.15/debian/patches/series 2022-07-12 14:17:33.0
-0400
@@ -1 +1,2 @@
# Auto-applied patches
+0001-Fix-compilation-with-newest-glibc.patch
Processed: fix severity
Processing commands for cont...@bugs.debian.org: > severity 1014663 serious Bug #1014663 [vkd3d] vk3d - build-dependencies not satisfiable on most architectures. Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1014663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000932: doxygen: diff for NMU version 1.9.1-2.1
Hi Sebastian! Il 14/07/22 11:22, Sebastian Ramacher ha scritto: Control: tags 1000932 + patch Control: tags 1000932 + pending Dear maintainer, I've prepared an NMU for doxygen (versioned as 1.9.1-2.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Cheers thanks for the quick patch; alas your fix will break this logic: https://salsa.debian.org/debian/doxygen/-/blob/master/debian/rules#L23 which was contributed by Norbert Lange to fix https://bugs.debian.org/945427. At this point I am unsure what effects this may cause, I only vaguely remember that the Clang_DIR and LLVM_DIR env vars plug into cmake somehow. So I'd propose to skip this NMU, as I'd rather address this as part of the new upstream release (https://bugs.debian.org/1013636). With each upstream release, I usually run massive archive rebuilds with ratt which helps pinpoint which of the ~700 paackages that reverse-build-dep on doxygen might fail when the new version is pushed through. Having said that, if you feel confident this will not break too many things, feel free to let it go. Otherwise I'm more than happy if you are inspired to contribute in any way to doxygen maintenance; for me the preferred way is by means of Merge Requests on salsa. MfG, Paolo P.S. I also tried reviving the salsa gitlab CI: https://salsa.debian.org/debian/doxygen/-/commits/bugfix/sramacher/1000932 but ATM the pipeline is failing for unrelated reasons: https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/358
Bug#1013532: marked as done (monero: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 "ARGS+=--output-on-failure -E 'functional_tests_rpc|core_tests|cnv
Your message dated Thu, 14 Jul 2022 16:13:28 +0200 with message-id <50705cac-0edc-3dcc-df63-be25af149...@debian.org> and subject line Re: Bug#1013532: fixed in monero 0.17.3.2+~0+20200826-1 has caused the Debian Bug report #1013532, regarding monero: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 "ARGS+=--output-on-failure -E 'functional_tests_rpc|core_tests|cnv4-jit|hash-slow-4'" returned exit code 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.) -- 1013532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: monero Version: 0.17.3.0+~0+20200826-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process --verbose -j8 --output-on-failure -E > 'functional_tests_rpc|core_tests|cnv4-jit|hash-slow-4' > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Test project /<>/obj-x86_64-linux-gnu > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: hash-target > > 1: Test command: /<>/obj-x86_64-linux-gnu/tests/hash-target-tests > 1: Test timeout computed to be: 1000 > test 2 > Start 2: wallet-crypto-bench > > 2: Test command: > /<>/obj-x86_64-linux-gnu/tests/monero-wallet-crypto-bench > 2: Test timeout computed to be: 1000 > test 3 > Start 3: cncrypto > > 3: Test command: > /<>/obj-x86_64-linux-gnu/tests/crypto/cncrypto-tests > "/<>/tests/crypto/tests.txt" > 3: Test timeout computed to be: 1000 > test 4 > Start 4: check_missing_rpc_methods > > 4: Test command: /usr/bin/python3 > "/<>/tests/functional_tests/check_missing_rpc_methods.py" > "/<>" > 4: Test timeout computed to be: 1000 > test 5 > Start 5: unit_tests > > 5: Test command: > /<>/obj-x86_64-linux-gnu/tests/unit_tests/unit_tests > "--data-dir" "/<>/tests/data" > 5: Test timeout computed to be: 1000 > test 6 > Start 6: difficulty > > 6: Test command: > /<>/obj-x86_64-linux-gnu/tests/difficulty/difficulty-tests > "/<>/tests/difficulty/data.txt" > 6: Test timeout computed to be: 1000 > test 7 > Start 7: wide_difficulty > > 7: Test command: /usr/bin/python3 > "/<>/tests/difficulty/wide_difficulty.py" "/usr/bin/python3" > "/<>/tests/difficulty/gen_wide_data.py" > "/<>/obj-x86_64-linux-gnu/tests/difficulty/difficulty-tests" > "/<>/obj-x86_64-linux-gnu/tests/difficulty/wide_data.txt" > 7: Test timeout computed to be: 1000 > test 8 > Start 8: block_weight > > 8: Test command: /usr/bin/python3 > "/<>/tests/block_weight/compare.py" "/usr/bin/python3" > "/<>/tests/block_weight/block_weight.py" > "/<>/obj-x86_64-linux-gnu/tests/block_weight/block_weight" > 8: Test timeout computed to be: 1000 > 2: Running benchmark using 1000 iterations > 2: Transaction Component Benchmarks > 2: > 1/18 Test #6: difficulty ... Passed0.06 sec > test 9 > Start 9: hash-fast > > 9: Test command: /<>/obj-x86_64-linux-gnu/tests/hash/hash-tests > "fast" "/<>/tests/hash/tests-fast.txt" > 9: Test timeout computed to be: 1000 > 2/18 Test #9: hash-fast Passed0.03 sec > test 10 > Start 10: hash-slow > > 10: Test command: /<>/obj-x86_64-linux-gnu/tests/hash/hash-tests > "slow" "/<>/tests/hash/tests-slow.txt" > 10: Test timeout computed to be: 1000 > 3/18 Test #4: check_missing_rpc_methods Passed0.42 sec > test 11 > Start 11: hash-slow-1 > > 11: Test command: /<>/obj-x86_64-linux-gnu/tests/hash/hash-tests > "slow-1" "/<>/tests/hash/tests-slow-1.txt" > 11: Test timeout computed to be: 1000 > 4/18 Test #10: hash-slow Passed0.74 sec > test 12 > Start 12: hash-slow-2 > > 12: Test command: /<>/obj-x86_64-linux-gnu/tests/hash/hash-tests > "slow-2" "/<>/tests/hash/tests-slow-2.txt" > 12: Test timeout computed to be: 1000 > 5: Note: Google Test filter =
Bug#1012789: marked as done (linuxcnc-uspace: Linux CNC will not start)
Your message dated Thu, 14 Jul 2022 16:06:18 +0200 with message-id and subject line solved by update to libtiff has caused the Debian Bug report #1012789, regarding linuxcnc-uspace: Linux CNC will not start 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.) -- 1012789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linuxcnc-uspace Version: 2.9.0~pre0+git20220402.2500863908-4 Severity: grave Justification: renders package unusable X-Debbugs-Cc: vectorhast...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I installed the package from respository with sudo apt-get install * What exactly did you do (or not do) that was effective (or ineffective)? Tried to understand from the error message if there was a missing package, but could not find one. * What was the outcome of this action? It did not help * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: arm64 (aarch64) Kernel: Linux 4.19.0-20-rt-arm64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linuxcnc-uspace depends on: ii blt2.5.3+dfsg-4.1 ii bwidget1.9.15-1 ii iptables 1.8.8-1 ii libboost-python1.74.0 1.74.0-16 ii libc6 2.33-7 ii libcairo2 1.16.0-5 ii libedit2 3.1-20210910-1 ii libepoxy0 1.5.10-1 ii libgcc-s1 12.1.0-2 ii libglib2.0-0 2.72.2-2 ii libgtk-3-0 3.24.34-1 ii libgtk2.0-02.24.33-2 ii libgtksourceview-3.0-dev 3.24.11-2+b1 ii libmodbus5 3.1.6-2 ii libpango-1.0-0 1.50.7+ds-1 ii libpangocairo-1.0-01.50.7+ds-1 ii libpython3.10 3.10.5-1 ii libstdc++6 12.1.0-2 ii libtirpc3 1.3.2-2 ii libtk-img 1:1.4.13+dfsg-1 ii libtk8.6 8.6.12-1 ii libudev-dev251.2-5 ii libudev1 251.2-5 ii libusb-1.0-0 2:1.0.26-1 ii libx11-6 2:1.7.5-1 ii libxinerama1 2:1.1.4-3 ii libxmu62:1.1.3-3 ii mesa-utils 8.5.0-1 ii procps 2:3.3.17-7+b1 ii psmisc 23.5-1 ii python33.10.4-1+b1 ii python3-cairo 1.20.1-3 ii python3-configobj 5.0.6-5 ii python3-gi-cairo 3.42.1-1 ii python3-numpy 1:1.21.5-1 ii python3-opengl 3.1.5+dfsg-1 ii python3-tk 3.10.5-1 ii python3-xlib 0.29-1 ii tcl-tclreadline [tclreadline] 2.3.8-1 ii tcl8.6 8.6.12+dfsg-1 ii tclx8.4 [tclx] 8.4.1-4 ii tk8.6 8.6.12-1 ii udev 251.2-5 Versions of packages linuxcnc-uspace recommends: ii espeak 1.48.15+dfsg-3 ii espeak-ng 1.51+dfsg-7 ii gstreamer1.0-tools 1.20.2-1 pn hostmot2-firmware-all ii librsvg2-dev2.54.3+dfsg-1 ii linuxcnc-doc-en [linuxcnc-doc] 2.9.0~pre0+git20220402.2500863908-4 ii pyqt5-dev-tools 5.15.6+dfsg-1+b2 ii python3-dbus1.2.18-3+b1 ii python3-dbus.mainloop.pyqt5 5.15.6+dfsg-1+b2 ii python3-espeak 0.5-4+b1 ii python3-opencv 4.5.4+dfsg-9+b7 ii python3-pil 9.1.1-1 ii python3-pil.imagetk 9.1.1-1 ii python3-pyqt5 5.15.6+dfsg-1+b2 ii python3-pyqt5.qsci 2.11.6+dfsg-4+b1 ii python3-pyqt5.qtopengl 5.15.6+dfsg-1+b2 ii python3-pyqt5.qtsvg 5.15.6+dfsg-1+b2 ii python3-pyqt5.qtwebkit 5.15.6+dfsg-1+b2 ii sound-theme-freedesktop 0.8-2 Versions of packages linuxcnc-uspace suggests: pn mesaflash -- no debconf
Bug#1014492: guzzle: CVE-2022-31090 CVE-2022-31091
Hi Katharina, On Thu, 7 Jul 2022 10:56:06 +0200 Katharina Drexel wrote: > thanks for the hints. I pushed a new version in the repo > (https://salsa.debian.org/php-team/pear/php-guzzlehttp-guzzle). > TBD: someone should upload it in the debian repo. Is it OK if I upload guzzle? By the way, debian/changelog contains two Debian versions for 7.4.5: 7.4.5-1 and 7.4.5-2. It does not seem 7.4.5-1 has been uploaded yet, could you merge both of them to be 7.4.5-1? Best, Andrius
Bug#1014749: marked as done (openvswitch-test,python3-openvswitch: both ship /usr/lib/python3/dist-packages/ovstest/*.py)
Your message dated Thu, 14 Jul 2022 13:34:43 + with message-id and subject line Bug#1014749: fixed in openvswitch 2.17.2-2 has caused the Debian Bug report #1014749, regarding openvswitch-test,python3-openvswitch: both ship /usr/lib/python3/dist-packages/ovstest/*.py 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.) -- 1014749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openvswitch-test,python3-openvswitch Version: 2.17.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package python3-openvswitch. Preparing to unpack .../python3-openvswitch_2.17.2-1_all.deb ... Unpacking python3-openvswitch (2.17.2-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-openvswitch_2.17.2-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/ovstest/__init__.py', which is also in package openvswitch-test 2.17.2-1 Errors were encountered while processing: /var/cache/apt/archives/python3-openvswitch_2.17.2-1_all.deb cheers, Andreas openvswitch-test=2.17.2-1_python3-openvswitch=2.17.2-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: openvswitch Source-Version: 2.17.2-2 Done: Luca Boccassi We believe that the bug you reported is fixed in the latest version of openvswitch, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Boccassi (supplier of updated openvswitch 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, 14 Jul 2022 14:16:53 +0100 Source: openvswitch Architecture: source Version: 2.17.2-2 Distribution: experimental Urgency: medium Maintainer: Debian OpenStack Changed-By: Luca Boccassi Closes: 1009969 1014749 Changes: openvswitch (2.17.2-2) experimental; urgency=medium . * d/rules: exclude new tests that are failing on hppa * d/rules: exclude new tests that are failing on riscv64 (Closes: #1009969) * d/rules: exclude new tests that are failing on sparc64 * d/clean: add trailing slash to directories * Do not install python3/ovtest in two packages (Closes: #1014749) * d/rules: simplify Python handling Checksums-Sha1: bab9df4eb7e1f699de5615425a09b4b7c1067a85 3440 openvswitch_2.17.2-2.dsc db044728cbea348df10b67acbe880cec6526bdad 65428 openvswitch_2.17.2-2.debian.tar.xz d7301aa6293505758c7febb1dcc5f542fa13267e 10325 openvswitch_2.17.2-2_source.buildinfo Checksums-Sha256: 731616194eb3cf282b0857a2047a404063b49be902bec309ff386fd6a907e618 3440 openvswitch_2.17.2-2.dsc c007c781dffeb58a081b1796e59f58f00cbf0670c9b49ad7eca73891b66482d8 65428 openvswitch_2.17.2-2.debian.tar.xz c8986197e230e4943b2661c2bc751b16fc71247c2ad95e0b29a5157fdb4c5bff 10325 openvswitch_2.17.2-2_source.buildinfo Files: 9ef5f390f07eb41d56085f7afbd18eed 3440 net optional openvswitch_2.17.2-2.dsc f821c804d51bce5d978f178270b07756 65428 net optional openvswitch_2.17.2-2.debian.tar.xz ec85dee18c3a5dac3ad87012bedec18e 10325 net optional openvswitch_2.17.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmLQF/YRHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB57BhAAu43sXwqIlWOG7TRgMezcd4YnqCnYYBJH 9dNSiMw8kQ6mlK9ixOhISuZb64S40wcgTEr3qKxYtDaGVSxiOjtK6SJNvHAQPfF4 ky2Vvq6FstZ1SkJVGUf2JZdN7Wx551cckFqZ3gwOhArQS4OkRGD6FtDKgsLNz0A7 x9oWC8ugOC8wSjjymfZtj3Vn8fmI/vSkD9V16H8DYe503D9p+h6Le6AWiM5kA0A3 wm0j5TpeB4sB437qqWmnA4ughV0BKp+wD18RDSCb+W/QdNGqxjqv/XD/O863AxAo W1b+gTj5neMaocOYSR7zznOwZSSapQcoF2I7MJ7RWMw7dM6YOrLNATbLeK2Wsvie qEGHjIoRSFN3nCcWmCWfs04YgTIp4DvVWETrJVdXVk8xz27ADvlbhhbzv78U1TGV jX5ZeaOsxRLDfQAro1PSpD7A/DQ4bEKhTbobeJ889j20zJzv5MTk5XDS9BU0hTCT KlZwjB9VyGAnsEw+CQ3Rv1KYVBaA7huUd/uEUhi6JWE4c1MPkVBL11R+dqXdET4A RO0/FesgcyqzXqeuGTR4/Zt61U3JMODsOtt6zWAGzTCbcX4VmFliJsRN25CLllyY
Bug#1014919: libflint17 is incorrectly marked Multi-Arch: same
Package: libflint17 Version: 2.9.0-2 Severity: serious /usr/lib/x86_64-linux-gnu/libflint-2.8.5.so.16.1.5 -> /usr/lib/libflint.so.17.0.0 It was likely unintentional that the library moved to a non-multiarch location in https://salsa.debian.org/math-team/flint/-/commit/5cee4678c1eb7699283418f9b48b2b59ac1c35f0
Processed: affects 1014917
Processing commands for cont...@bugs.debian.org: > affects 1014917 src:antic src:flint-arb src:linbox src:calcium src:e-antic > src:gyoto src:normaliz src:singular src:macaulay2 src:polymake src:sagemath Bug #1014917 [libflint17] libflint17 lacks SONAME Added indication that 1014917 affects src:antic, src:flint-arb, src:linbox, src:calcium, src:e-antic, src:gyoto, src:normaliz, src:singular, src:macaulay2, src:polymake, and src:sagemath > thanks Stopping processing here. Please contact me if you need assistance. -- 1014917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:nrepl-clojure: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 0.9.0-1
Bug #1014918 [src:nrepl-clojure] src:nrepl-clojure: fails to migrate to testing
for too long: autopkgtest regression
Marked as fixed in versions nrepl-clojure/0.9.0-1.
Bug #1014918 [src:nrepl-clojure] src:nrepl-clojure: fails to migrate to testing
for too long: autopkgtest regression
Marked Bug as done
> block -1 by 1011970
Bug #1014918 {Done: Paul Gevers } [src:nrepl-clojure]
src:nrepl-clojure: fails to migrate to testing for too long: autopkgtest
regression
1014918 was not blocked by any bugs.
1014918 was not blocking any bugs.
Added blocking bug(s) of 1014918: 1011970
--
1014918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1014918: src:nrepl-clojure: fails to migrate to testing for too long: autopkgtest regression
Source: nrepl-clojure Version: 0.6.0-2 Severity: serious Control: close -1 0.9.0-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1011970 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:nrepl-clojure has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package has an autopkgtest regression that I reported some time ago in bug #1011970. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=nrepl-clojure OpenPGP_signature Description: OpenPGP digital signature
Bug#1014917: libflint17 lacks SONAME
Package: libflint17 Version: 2.9.0-2 Severity: grave Tags: ftbfs Control: affects src:antic src:flint-arb src:linbox src:calcium src:e-antic src:gyoto src:normaliz src:singular src:macaulay2 src:polymake src:sagemath $ objdump -p /usr/lib/x86_64-linux-gnu/libflint-2.8.5.so.16.1.5 | grep SONAME SONAME libflint-2.8.5.so $ objdump -p /usr/lib/libflint.so.17.0.0 | grep SONAME $ One of the problems this causes is that reverse dependencies do not get a shlibs-generated dependency on libflint17. debian/rules sets EXTRA_SHARED_FLAGS (to avoid the rpath?), but upstream configure also uses it to set -soname and https://salsa.debian.org/math-team/flint/-/commit/ea3ae82694953d6386898f051dd9b1b2f111dfaa removed the code correcting that.
Processed: Re: Bug#1013916: missing dependency
Processing control commands: > tags -1 patch Bug #1013916 [cron-daemon-common] missing dependency Added tag(s) patch. -- 1013916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013916: missing dependency
Control: tags -1 patch
Georges,
I have bumped into this issue as well.
A patch to fix is below.
Thanks,
Mark
>From 88e5b316d6ad0587226e17b010d7c43e75d4815d Mon Sep 17 00:00:00 2001
From: Mark Hindley
Date: Thu, 14 Jul 2022 12:50:18 +0100
Subject: [PATCH] d/control: move adduser dependency to cron-daemon-common
(Closes: #1013916).
d/cron-daemon-common.postinst uses addgroup. When the -common package was
created, moving the adduser dependency was overlooked.
---
debian/control | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/debian/control b/debian/control
index 8f00824..a7f2bab 100644
--- a/debian/control
+++ b/debian/control
@@ -24,7 +24,6 @@ Depends:
${shlibs:Depends},
${misc:Depends},
sensible-utils,
-adduser,
lsb-base,
libpam-runtime
Recommends:
@@ -58,7 +57,8 @@ Description: process scheduling daemon
Package: cron-daemon-common
Architecture: all
-Depends: ${misc:Depends}
+Depends: ${misc:Depends},
+adduser,
Conflicts:
cron (<< 3.0pl1-140),
cronie (<< 1.6.1-4),
--
2.35.1
Bug#1014745: thunderbird: Reply all remove Cc participants
On 14/07/2022 12:04, Carsten Schoenert wrote: Hello Eric, Am 14.07.22 um 11:48 schrieb eric: I had the same problem on a specific exchnage account. Reply all did not copy the content and did remove all the CC. you could try out TB 1:103.0~b5-1 from experimental which should have included the fix which issue here is about. Keep in mind that the configuration will get bumped to the new main version and isn't backward compatible, so please make a backup of your config before starting the installed version from experimental. That's exactly why I will not do this. I want to be on the next esr branch and test more deeply as I will have to use it on my professionnal account as well. If it is fixed in 103, I bet it will be backported (ESR after all). I cannot afford to break my main setup even more. It did happen everytime on .1, did not manage to reproduce it with the broken mail on .2. Thanks for the support anyway. --eric
Bug#1014745: thunderbird: Reply all remove Cc participants
Hello Eric, Am 14.07.22 um 11:48 schrieb eric: I had the same problem on a specific exchnage account. Reply all did not copy the content and did remove all the CC. you could try out TB 1:103.0~b5-1 from experimental which should have included the fix which issue here is about. Keep in mind that the configuration will get bumped to the new main version and isn't backward compatible, so please make a backup of your config before starting the installed version from experimental. -- Regards Carsten
Bug#1014745: thunderbird: confirmed here
Package: thunderbird Version: 1:102.0.2-1 Followup-For: Bug #1014745 I had the same problem on a specific exchnage account. Reply all did not copy the content and did remove all the CC. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.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 thunderbird depends on: ii debianutils 5.7-0.2 ii fontconfig 2.13.1-4.4 ii kdialog 4:21.12.3-1 ii libasound2 1.2.7.1-1 ii libatk1.0-0 2.45.1-1 ii libc62.34-0experimental5 ii libcairo-gobject21.16.0-6 ii libcairo21.16.0-6 ii libdbus-1-3 1.14.0-1 ii libdbus-glib-1-2 0.112-2 ii libevent-2.1-7 2.1.12-stable-5+b1 ii libffi8 3.4.2-4 ii libfontconfig1 2.13.1-4.4 ii libfreetype6 2.12.1+dfsg-3 ii libgcc-s112.1.0-5 ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1 ii libglib2.0-0 2.73.2-1 ii libgtk-3-0 3.24.34-1 ii libicu71 71.1-3 ii libnspr4 2:4.34-1 ii libnss3 2:3.79-1 ii libpango-1.0-0 1.50.7+ds-1 ii librnp0 0.17.0~git20220428-1 ii libstdc++6 12.1.0-5 ii libvpx7 1.12.0-1 ii libx11-6 2:1.7.5-1 ii libx11-xcb1 2:1.7.5-1 ii libxcb-shm0 1.14-3 ii libxcb1 1.14-3 ii libxext6 2:1.3.4-1 ii libxrandr2 2:1.5.2-2+b1 ii psmisc 23.5-1 ii x11-utils7.7+5 ii zenity 3.42.1-2 ii zlib1g 1:1.2.11.dfsg-4 Versions of packages thunderbird recommends: ii hunspell-en-us [hunspell-dictionary] 1:2020.12.07-2 ii hunspell-fr-classical [hunspell-dictionary] 1:7.0-1 Versions of packages thunderbird suggests: ii apparmor 3.0.4-3 ii fonts-lyx 2.3.6.1-1 ii libgssapi-krb5-2 1.20~beta1-1 -- no debconf information
Processed: doxygen: diff for NMU version 1.9.1-2.1
Processing control commands: > tags 1000932 + patch Bug #1000932 [src:doxygen] doxygen: Please upgrade to llvm-toolchain-13 or 14 Added tag(s) patch. > tags 1000932 + pending Bug #1000932 [src:doxygen] doxygen: Please upgrade to llvm-toolchain-13 or 14 Added tag(s) pending. -- 1000932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000932: doxygen: diff for NMU version 1.9.1-2.1
Control: tags 1000932 + patch Control: tags 1000932 + pending Dear maintainer, I've prepared an NMU for doxygen (versioned as 1.9.1-2.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru doxygen-1.9.1/debian/changelog doxygen-1.9.1/debian/changelog --- doxygen-1.9.1/debian/changelog 2021-03-22 00:04:01.0 +0100 +++ doxygen-1.9.1/debian/changelog 2022-07-14 11:12:01.0 +0200 @@ -1,3 +1,10 @@ +doxygen (1.9.1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/control: Switch to unversioned llvm dependencies (Closes: #1000932) + + -- Sebastian Ramacher Thu, 14 Jul 2022 11:12:01 +0200 + doxygen (1.9.1-2) unstable; urgency=medium * Build with LLVM support on riscv64. Closes: #985587. diff -Nru doxygen-1.9.1/debian/control doxygen-1.9.1/debian/control --- doxygen-1.9.1/debian/control 2021-03-21 11:06:46.0 +0100 +++ doxygen-1.9.1/debian/control 2022-07-14 11:11:30.0 +0200 @@ -10,9 +10,9 @@ zlib1g-dev, libxapian-dev (>= 1.2.21-1.2), cmake, - llvm-11-dev [amd64 armel armhf arm64 i386 mips mipsel mips64el ppc64 ppc64el riscv64 s390x sparc64], - libclang-11-dev [amd64 armel armhf arm64 i386 mips mipsel mips64el ppc64 ppc64el riscv64 s390x sparc64], - clang-11[amd64 armel armhf arm64 i386 mips mipsel mips64el ppc64 ppc64el riscv64 s390x sparc64], + llvm-dev [amd64 armel armhf arm64 i386 mips mipsel mips64el ppc64 ppc64el riscv64 s390x sparc64], + libclang-dev [amd64 armel armhf arm64 i386 mips mipsel mips64el ppc64 ppc64el riscv64 s390x sparc64], + clang[amd64 armel armhf arm64 i386 mips mipsel mips64el ppc64 ppc64el riscv64 s390x sparc64], sassc, faketime, mat2
Processed: severity of 1012329 is serious
Processing commands for cont...@bugs.debian.org: > severity 1012329 serious Bug #1012329 [src:intel-vc-intrinsics] intel-vc-intrinsics: Please upgrade to llvm-toolchain-13 or 14 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1012329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1004883 is serious
Processing commands for cont...@bugs.debian.org: > severity 1004883 serious Bug #1004883 [src:intel-graphics-compiler] intel-graphics-compiler: Please upgrade to llvm-toolchain-13 or 14 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1004883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014906: opencl-clang-11: do not release with bookworm
Source: opencl-clang-11 Version: 11.0.0-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org Bookworm will be released with llvm-toolchains 13, 14 and 15. llvm-toolchain-11 won't be part of bookworm. So opencl-clang-11 will also not be part of bookworm. Cheers -- Sebastian Ramacher
Bug#1014905: spirv-llvm-translator-11: do not release with bookworm
Source: spirv-llvm-translator-11 Version: 11.0.0-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org Bookworm will be released with llvm-toolchains 13, 14 and 15. llvm-toolchain-11 won't be part of bookworm. So spirv-llvm-translator-11 will also not be part of bookworm. Cheers -- Sebastian Ramacher
Processed: Re: Bug#1000932: doxygen: Please upgrade to llvm-toolchain-12 or 13
Processing control commands: > severity -1 serious Bug #1000932 [src:doxygen] doxygen: Please upgrade to llvm-toolchain-13 or 14 Severity set to 'serious' from 'important' -- 1000932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1000916 closed by Debian FTP Masters (reply to Sophie Brun ) (Bug#1000916: fixed in vboot-utils 0~R99-14469.B-1)
Processing control commands:
> reopen -1
Bug #1000916 {Done: Sophie Brun }
[src:vboot-utils] vboot-utils: Please upgrade to llvm-toolchain-12 or 13
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions vboot-utils/0~R99-14469.B-1.
> severity -1 serious
Bug #1000916 [src:vboot-utils] vboot-utils: Please upgrade to llvm-toolchain-12
or 13
Severity set to 'serious' from 'important'
--
1000916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1014903: xorg-server: CVE-2022-2319 CVE-2022-2320
Source: xorg-server Version: 2:21.1.3-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for xorg-server. CVE-2022-2319[0]: | ZDI-CAN-16062: X.Org Server ProcXkbSetGeometry Out-Of-Bounds Access CVE-2022-2320[1]: | ZDI-CAN-16070: X.Org Server ProcXkbSetDeviceInfo Out-Of-Bounds Access If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-2319 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2319 [1] https://security-tracker.debian.org/tracker/CVE-2022-2320 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2320 [2] https://www.openwall.com/lists/oss-security/2022/07/12/1 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Processed: Re: Bug#1014690: llvmlite breaks numba autopkgtest: segmentation fault
Processing control commands:
> reassign 1014690 src:llvmlite 0.38.1-2
Bug #1014690 {Done: Mo Zhou } [src:llvmlite, src:numba]
llvmlite breaks numba autopkgtest: segmentation fault
Bug reassigned from package 'src:llvmlite, src:numba' to 'src:llvmlite'.
No longer marked as found in versions numba/0.55.2+dfsg-1 and llvmlite/0.38.1-2.
No longer marked as fixed in versions llvmlite/0.38.1-3.
Bug #1014690 {Done: Mo Zhou } [src:llvmlite] llvmlite breaks
numba autopkgtest: segmentation fault
Marked as found in versions llvmlite/0.38.1-2.
> affects 1014690 src:numba
Bug #1014690 {Done: Mo Zhou } [src:llvmlite] llvmlite breaks
numba autopkgtest: segmentation fault
Added indication that 1014690 affects src:numba
> fixed 1014690 0.38.1-3
Bug #1014690 {Done: Mo Zhou } [src:llvmlite] llvmlite breaks
numba autopkgtest: segmentation fault
Marked as fixed in versions llvmlite/0.38.1-3.
--
1014690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1014690: llvmlite breaks numba autopkgtest: segmentation fault
Control: reassign 1014690 src:llvmlite 0.38.1-2 Control: affects 1014690 src:numba Control: fixed 1014690 0.38.1-3 Hi Diane, On 14-07-2022 05:26, Diane Trout wrote: I know there's some problems with some of numba's autopkgtests but I couldn't reproduce the segmentation fault. That's because Mo reverted the change to use llvm-toolchain-13 in llvmlite. llvmlite's tracker suggests that the tests are passing now? Did you find a solution or is this likely to be a random problem? Well, reverting reopened another issue we have which is that we want to drop llvm-toolchain-11 from testing. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1000922: llvmlite: Please upgrade to llvm-toolchain-13 or 14
Hi, On Sun, 10 Jul 2022 22:54:58 +0200 Sylvestre Ledru wrote: Could you please try with 12? llvm-toolchain-12 is already removed from testing and will not migrate back, so I don't think that's a solution. Or do you think it makes sense for troubleshooting? Paul OpenPGP_signature Description: OpenPGP digital signature
