Processed: tagging 1012918
Processing commands for cont...@bugs.debian.org: > tags 1012918 + patch Bug #1012918 [src:edb-debugger] edb-debugger: ftbfs with GCC-12 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1017215 in 0.19.6-1
Processing commands for cont...@bugs.debian.org: > found 1017215 0.19.6-1 Bug #1017215 [src:haskell-shake] libghc-shake-dev and libghc-shake-data both ship /usr/lib/haskell-packages/extra-packages/shake-0.19.6 Marked as found in versions haskell-shake/0.19.6-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1017215: pkg-haskell-tools: FTBFS: Errors while processing: /tmp/apt-dpkg-install-dX7M5d/169-libghc-shake-dev_0.19.6-1_amd64.deb
Processing control commands: > reassign -1 src:haskell-shake Bug #1017215 [src:pkg-haskell-tools] pkg-haskell-tools: FTBFS: Errors while processing: /tmp/apt-dpkg-install-dX7M5d/169-libghc-shake-dev_0.19.6-1_amd64.deb Bug reassigned from package 'src:pkg-haskell-tools' to 'src:haskell-shake'. No longer marked as found in versions pkg-haskell-tools/0.12.3. Ignoring request to alter fixed versions of bug #1017215 to the same values previously set > affects -1 libghc-shake-dev libghc-shake-data src:pkg-haskell-tools Bug #1017215 [src:haskell-shake] pkg-haskell-tools: FTBFS: Errors while processing: /tmp/apt-dpkg-install-dX7M5d/169-libghc-shake-dev_0.19.6-1_amd64.deb Added indication that 1017215 affects libghc-shake-dev, libghc-shake-data, and src:pkg-haskell-tools > retitle -1 libghc-shake-dev and libghc-shake-data both ship > /usr/lib/haskell-packages/extra-packages/shake-0.19.6 Bug #1017215 [src:haskell-shake] pkg-haskell-tools: FTBFS: Errors while processing: /tmp/apt-dpkg-install-dX7M5d/169-libghc-shake-dev_0.19.6-1_amd64.deb Changed Bug title to 'libghc-shake-dev and libghc-shake-data both ship /usr/lib/haskell-packages/extra-packages/shake-0.19.6' from 'pkg-haskell-tools: FTBFS: Errors while processing: /tmp/apt-dpkg-install-dX7M5d/169-libghc-shake-dev_0.19.6-1_amd64.deb'. -- 1017215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017215: pkg-haskell-tools: FTBFS: Errors while processing: /tmp/apt-dpkg-install-dX7M5d/169-libghc-shake-dev_0.19.6-1_amd64.deb
Control: reassign -1 src:haskell-shake Control: affects -1 libghc-shake-dev libghc-shake-data src:pkg-haskell-tools Control: retitle -1 libghc-shake-dev and libghc-shake-data both ship /usr/lib/haskell-packages/extra-packages/shake-0.19.6 On Sun, Aug 14, 2022 at 09:31:02AM +0200, Lucas Nussbaum wrote: > Source: pkg-haskell-tools > Version: 0.12.3 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220813 ftbfs-bookworm >... > > Selecting previously unselected package libghc-shake-data. > > Preparing to unpack .../168-libghc-shake-data_0.19.6-1_all.deb ... > > Unpacking libghc-shake-data (0.19.6-1) ... > > Selecting previously unselected package libghc-shake-dev. > > Preparing to unpack .../169-libghc-shake-dev_0.19.6-1_amd64.deb ... > > Unpacking libghc-shake-dev (0.19.6-1) ... > > dpkg: error processing archive > > /tmp/apt-dpkg-install-dX7M5d/169-libghc-shake-dev_0.19.6-1_amd64.deb > > (--unpack): > > trying to overwrite > > '/usr/lib/haskell-packages/extra-packages/shake-0.19.6', which is also in > > package libghc-shake-data 0.19.6-1 > > dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) >... Reassigning to the correct package. cu Adrian
Bug#984298: psensor: diff for NMU version 1.1.5-1.4
Control: tags 984298 + patch Control: tags 984298 + pending -- Dear maintainer, I've prepared an NMU for psensor (versioned as 1.1.5-1.4) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. -- Regards Sudip diff -Nru psensor-1.1.5/debian/changelog psensor-1.1.5/debian/changelog --- psensor-1.1.5/debian/changelog 2021-02-06 19:50:55.0 + +++ psensor-1.1.5/debian/changelog 2022-09-02 23:33:53.0 +0100 @@ -1,3 +1,10 @@ +psensor (1.1.5-1.4) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with gcc-11. (Closes: #984298) + + -- Sudip Mukherjee Fri, 02 Sep 2022 23:33:53 +0100 + psensor (1.1.5-1.3) unstable; urgency=medium * Non-maintainer upload. diff -Nru psensor-1.1.5/debian/patches/fix-ftbfs.patch psensor-1.1.5/debian/patches/fix-ftbfs.patch --- psensor-1.1.5/debian/patches/fix-ftbfs.patch1970-01-01 01:00:00.0 +0100 +++ psensor-1.1.5/debian/patches/fix-ftbfs.patch2022-09-02 23:32:48.0 +0100 @@ -0,0 +1,20 @@ +Description: Fix FTBFS with gcc-11 + Fix the indentation while keeping the logic same as before. + +Author: Sudip Mukherjee +--- + +Bug-Debian: https://bugs.debian.org/984298 +Forwarded: no + +--- psensor-1.1.5.orig/src/lib/pudisks2.c psensor-1.1.5/src/lib/pudisks2.c +@@ -83,7 +83,7 @@ static void smart_update(struct psensor + PROVIDER_NAME, + data->path); + +- data->last_smart_update = t; ++ data->last_smart_update = t; + } + + void udisks2_psensor_list_update(struct psensor **sensors) diff -Nru psensor-1.1.5/debian/patches/series psensor-1.1.5/debian/patches/series --- psensor-1.1.5/debian/patches/series 2021-02-06 19:50:55.0 + +++ psensor-1.1.5/debian/patches/series 2022-09-02 23:33:02.0 +0100 @@ -1,3 +1,4 @@ 0001-Update-rsensor.c-drop-is_error-macro-definition.patch 14.patch ayatana-appindicator.patch +fix-ftbfs.patch
Processed: psensor: diff for NMU version 1.1.5-1.4
Processing control commands: > tags 984298 + patch Bug #984298 [src:psensor] psensor: ftbfs with GCC-11 Added tag(s) patch. > tags 984298 + pending Bug #984298 [src:psensor] psensor: ftbfs with GCC-11 Added tag(s) pending. -- 984298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993014: cifs-utils non-parallel FTBFS
Hi. Could we have this fixed in stable for the next point release (11.5), please? (The window for uploads closes this weekend). Please tell me if you need help (for example, doing an upload and/or submitting a bug to release.debian.org asking for the upload to be accepted). Thanks.
Bug#1018842: marked as done (telegram-destop: FTBFS with libabsl20220623)
Your message dated Fri, 2 Sep 2022 18:16:57 -0400 with message-id and subject line Re: Bug#1018842: telegram-destop: FTBFS with libabsl20220623 has caused the Debian Bug report #1018842, regarding telegram-destop: FTBFS with libabsl20220623 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.) -- 1018842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: telegram-desktop Version: 4.1.1+ds-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=telegram-desktop=amd64=4.1.1%2Bds-1%2Bb1=1661970826=0 (.text+0x912): undefined reference to `absl::debian2::optional_internal::throw_bad_optional_access()' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libtg_owt.a(var_int.cc.o): in function `webrtc::DecodeVarInt(absl::debian2::string_view, unsigned long*)': (.text+0x2b4): undefined reference to `absl::debian2::base_internal::ThrowStdOutOfRange(char const*)' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libtg_owt.a(video_codec.cc.o): in function `webrtc::PayloadStringToCodecType(std::__cxx11::basic_string, std::allocator > const&)': (.text+0x521): undefined reference to `absl::debian2::EqualsIgnoreCase(absl::debian2::string_view, absl::debian2::string_view)' /usr/bin/ld: (.text+0x54a): undefined reference to `absl::debian2::EqualsIgnoreCase(absl::debian2::string_view, absl::debian2::string_view)' /usr/bin/ld: (.text+0x573): undefined reference to `absl::debian2::EqualsIgnoreCase(absl::debian2::string_view, absl::debian2::string_view)' /usr/bin/ld: (.text+0x59c): undefined reference to `absl::debian2::EqualsIgnoreCase(absl::debian2::string_view, absl::debian2::string_view)' /usr/bin/ld: (.text+0x5c1): undefined reference to `absl::debian2::EqualsIgnoreCase(absl::debian2::string_view, absl::debian2::string_view)' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libtg_owt.a(video_codec.cc.o):(.text+0x5e2): more undefined references to `absl::debian2::EqualsIgnoreCase(absl::debian2::string_view, absl::debian2::string_view)' follow /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libtg_owt.a(rtp_header_extensions.cc.o): in function `webrtc::AbsoluteCaptureTimeExtension::Write(rtc::ArrayView, webrtc::AbsoluteCaptureTime const&)': (.text+0x1b7): undefined reference to `absl::debian2::optional_internal::throw_bad_optional_access()' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libtg_owt.a(media_protocol_names.cc.o): in function `cricket::IsRtpProtocol(absl::debian2::string_view)': (.text+0xf2): undefined reference to `absl::debian2::string_view::find(absl::debian2::string_view, unsigned long) const' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libtg_owt.a(link_capacity_estimator.cc.o): in function `webrtc::LinkCapacityEstimator::deviation_estimate_kbps() const': (.text+0x595): undefined reference to `absl::debian2::optional_internal::throw_bad_optional_access()' /usr/bin/ld: warning: creating DT_TEXTREL in a PIE collect2: error: ld returned 1 exit status make[3]: *** [Telegram/CMakeFiles/Telegram.dir/build.make:10757: telegram-desktop] Error 1 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:1267: Telegram/CMakeFiles/Telegram.dir/all] Error 2 make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[1]: *** [Makefile:139: all] Error 2 make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j4 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:90: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Build finished at 2022-08-31T18:33:35Z Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Thanks, rebuilding libtgowt first worked: https://buildd.debian.org/status/package.php?p=telegram-desktop Jeremy Bicha--- End Message ---
Processed: tagging 1015027, block 1015027 with 1018980
Processing commands for cont...@bugs.debian.org: > tags 1015027 + pending Bug #1015027 [src:php-dragonmantank-cron-expression] php-dragonmantank-cron-expression: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1 Added tag(s) pending. > block 1015027 with 1018980 Bug #1015027 [src:php-dragonmantank-cron-expression] php-dragonmantank-cron-expression: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1 1015027 was not blocked by any bugs. 1015027 was not blocking any bugs. Added blocking bug(s) of 1015027: 1018980 > thanks Stopping processing here. Please contact me if you need assistance. -- 1015027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016779: marked as done (golang-github-lucas-clemente-quic-go: FTBFS with go1.19)
Your message dated Fri, 02 Sep 2022 21:22:43 + with message-id and subject line Bug#1016779: fixed in golang-github-lucas-clemente-quic-go 0.29.0-1 has caused the Debian Bug report #1016779, regarding golang-github-lucas-clemente-quic-go: FTBFS with go1.19 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.) -- 1016779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-lucas-clemente-quic-go Version: 0.26.0-1 Severity: serious X-Debbugs-Cc: z...@debian.org As usual, this package FTBFS every time when golang-defaults bumps Go version... # github.com/lucas-clemente/quic-go/internal/qtls src/github.com/lucas-clemente/quic-go/internal/qtls/go119.go:6:13: cannot use "quic-go doesn't build on Go 1.19 yet." (untyped string constant) as int value in variable declaration expvar --- End Message --- --- Begin Message --- Source: golang-github-lucas-clemente-quic-go Source-Version: 0.29.0-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of golang-github-lucas-clemente-quic-go, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated golang-github-lucas-clemente-quic-go package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Sep 2022 01:13:04 +0530 Source: golang-github-lucas-clemente-quic-go Architecture: source Version: 0.29.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Nilesh Patra Closes: 1016779 Changes: golang-github-lucas-clemente-quic-go (0.29.0-1) unstable; urgency=medium . * Team Upload. * New upstream version 0.29.0 * Refresh/Re-diff patches with new version * Bump Standards-Version to 4.6.1 (no changes needed) * Skip test needing to read ipv4 and ipv6 packet data which can cause problems on buildd * Change section to golang (which was devel earlier) * Update d/copyright year * Add B-D and depends on golang-golang-x-exp-dev (new dep) * Change B-D and Depends to qtls-go1-19-dev since go-1.19 is the default go version now (Closes: #1016779) Checksums-Sha1: c8c17dae9bf7a795ad925c772a9de476c4d9fc0b 2873 golang-github-lucas-clemente-quic-go_0.29.0-1.dsc 6c651bd614c87bf1276387ea24db9cd76ca12ab5 534503 golang-github-lucas-clemente-quic-go_0.29.0.orig.tar.gz 650704134a2138cd6463495b991c31b0806f1637 4220 golang-github-lucas-clemente-quic-go_0.29.0-1.debian.tar.xz 0208c4470c7cabdb50378309452f985fba874660 9826 golang-github-lucas-clemente-quic-go_0.29.0-1_amd64.buildinfo Checksums-Sha256: 1daeadc4292b08478d6639dd500ffdf6c1ed8c21e18b6d9daad664df1907dcfd 2873 golang-github-lucas-clemente-quic-go_0.29.0-1.dsc 7d007632aa2d6c9cc1edd2eb19f1df4b1c954a5ccd7d8168a09ae77fda3cfe78 534503 golang-github-lucas-clemente-quic-go_0.29.0.orig.tar.gz 26a2709b48c69870491a3d998bbce1d0898e4cb7c95e24725671b189f1fd1e64 4220 golang-github-lucas-clemente-quic-go_0.29.0-1.debian.tar.xz 4808fc1ee5e6b811f980f9a6bbba2a22596b5260bb7b91e30d751b208f4a8cfb 9826 golang-github-lucas-clemente-quic-go_0.29.0-1_amd64.buildinfo Files: 8bbdcb02ab4a145c7ef1a783dc83a069 2873 golang optional golang-github-lucas-clemente-quic-go_0.29.0-1.dsc 3e058510dc21d83398a6292f5632197c 534503 golang optional golang-github-lucas-clemente-quic-go_0.29.0.orig.tar.gz 0ca449f5ff1f014a9629b4a24d340831 4220 golang optional golang-github-lucas-clemente-quic-go_0.29.0-1.debian.tar.xz 7d4eb02c566417f15659e3cc13183560 9826 golang optional golang-github-lucas-clemente-quic-go_0.29.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmMScXASHG5pbGVzaEBk ZWJpYW4ub3JnAAoJEAC650s0M2nxh6cP/iUSXXtntE3PdbLeq4Xadf3+EYlaYcBc 7dzt8o6xquGdMCGofyohZWmm0OErtwDr0SWLhRItWKLhcyJBlZyLH6Nwjt8/P6hZ L9K6+T2jW27g4cCWQWk3OtZUuWs3LyiCrTAoFlInIcRM64XtNnJxsR4xCXUWixDl rdZN+179rcnzKxqbu//bUnE41GH09OM38HHLnNAWKTd95Dy2wAFQK6ginawC//AD jnfmm7g+Buv3MTKlxl6Ch468AXkuNQoLTSL+8mLmaaP7+991ySNZiFWr/j/JnzAH
Bug#998097: marked as done (ruby-eventmachine FTBFS on IPV6-only buildds and accesses the internet during the build)
Your message dated Fri, 02 Sep 2022 21:07:05 + with message-id and subject line Bug#998097: fixed in ruby-eventmachine 1.3~pre20201020-b50c135-6 has caused the Debian Bug report #998097, regarding ruby-eventmachine FTBFS on IPV6-only buildds and accesses the internet during the build 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.) -- 998097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-eventmachine Severity: serious Tags: ftbfs FTBFS on IPV6-only buildds: https://buildd.debian.org/status/fetch.php?pkg=ruby-eventmachine=amd64=1.3~pre20201020-b50c135-3=1633500476=0 https://buildd.debian.org/status/fetch.php?pkg=ruby-eventmachine=i386=1.3~pre20201020-b50c135-4%2Bb1=1635578996=0 FTBFS due to attempted DNS: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-eventmachine.html ... === Failure: test_nameserver(TestResolver): was expected to be kind_of? but was . /build/1st/ruby-eventmachine-1.3~pre20201020-b50c135/tests/test_resolver.rb:19:in `test_nameserver' 16: end 17: 18: def test_nameserver => 19: assert_kind_of(String, EM::DNS::Resolver.nameserver) 20: end 21: 22: def test_nameservers === ... --- End Message --- --- Begin Message --- Source: ruby-eventmachine Source-Version: 1.3~pre20201020-b50c135-6 Done: Lucas Kanashiro We believe that the bug you reported is fixed in the latest version of ruby-eventmachine, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lucas Kanashiro (supplier of updated ruby-eventmachine 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: Fri, 02 Sep 2022 17:20:43 -0300 Source: ruby-eventmachine Architecture: source Version: 1.3~pre20201020-b50c135-6 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Lucas Kanashiro Closes: 998097 Changes: ruby-eventmachine (1.3~pre20201020-b50c135-6) unstable; urgency=medium . * Team upload. * Add patch to skip tests which require non-empty resolv.conf (Closes: #998097). * Declare compliance with Debian Policy 4.6.1. Checksums-Sha1: fd2edca1ddf204ad3dffd56dc00766146467d44a 2371 ruby-eventmachine_1.3~pre20201020-b50c135-6.dsc f0d133d9ea988c846fe6c295819ec18c9ce5595a 14380 ruby-eventmachine_1.3~pre20201020-b50c135-6.debian.tar.xz Checksums-Sha256: e145198268974a62818f6dcfa6e62defd70a619f905a7e778cd251904c35d27a 2371 ruby-eventmachine_1.3~pre20201020-b50c135-6.dsc ca08b6f46be3d0ccdf32b09a5365d7accdb03d20323070b8b55a35e7e8e00a6d 14380 ruby-eventmachine_1.3~pre20201020-b50c135-6.debian.tar.xz Files: e22f82c2fcdaf74a07f5667ac5108770 2371 ruby optional ruby-eventmachine_1.3~pre20201020-b50c135-6.dsc 599cbdf844b9b77f24b22f6d910458c0 14380 ruby optional ruby-eventmachine_1.3~pre20201020-b50c135-6.debian.tar.xz -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAmMSZ64VHGthbmFzaGly b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l820MQALTcQwBLtNDcoGPHVXQ48Eal4CjS w08E4gS6NZ8VIPLCNxwjspJ1H98yDoWwUcntteb11EpWAmopWFn8rea4wgw+CRVY 4D/xJgl75VSua79QWt9H5IS91/5mTlEo8X0mENkk61ZaVNYwcleUZ5Sxj2/XSlTw cu5ljD+9B9Y/M581gCHCQmewKvHfQidAAw9aoSHENcVO2mX/9AOTEge9I6O7gU3O kGHKzGiGOnDZfLW4NFhQ0HnD7Y8Co1FOncqJAFUvH8HDDVeGDYTd6UN8QG/x6561 2kSAbiTaimmMBENCTgRUgfxZ/IAPP2gAsIkVvFXpFJYiiI87XdxThSCVdevWk89c iY75D8xxUBkrcNbnz7iDyAm7h9g8/aS7dhnVZbnhGLpSN/7AQRCbUyqbaWmHYa+/ DrhmHoK2m58JUb3/4Aunl7rxYUIspGxAjKJWgf49F243zrGCgCci8Xx2n2x5AwAN zTUhOlCpMKPRxw/g015J5Fn2vMJ0RW4KA5PxwnllIHMY90BwjmFuXBSyXayxve9D wlleK6JZJdeCMDCHVtZ5KWlasdNlgD1b9QLbnX/6mwN3BSw5U8nQS3yi1sb8S9Qg 8QIcr+SiVbIQa5ghL/hzyYQDiNo9NihkWwqN9DyLSoSFHKuFQxdifmzfV7530leW yrXhmdrPF3BmZ7ie =YKFG -END PGP SIGNATURE End Message ---
Bug#1018776: marked as done (linux-image-5.18.0-4-686-pae Kernel panic on Pentium 3 and Athlon XP)
Your message dated Fri, 02 Sep 2022 21:02:09 + with message-id and subject line Bug#1017425: fixed in linux 5.10.140-1 has caused the Debian Bug report #1017425, regarding linux-image-5.18.0-4-686-pae Kernel panic on Pentium 3 and Athlon XP 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.) -- 1017425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.18.16-1 Severity: important X-Debbugs-Cc: m...@posteo.de Dear Maintainer, * What led up to the situation? Booting Kernel linux-image-5.18.0-4-686-pae on a Pentium 3 600 (Coppermine) or an Athlon XP (I can find out the exact model number if you need). Older kernel versions work. The current kernel works on a Pentium 4 3 GHz (I can find out the exact model number if you need). Error message: https://picr.eu/images/2022/08/29/qUlKO.jpg German discussion in a newsgroup: https://de.comp.os.unix.linux.misc.narkive.com/JzfZxhgj/kernelpanic-5-18-0-4-686-pae-attempted-to-kill-the-idle-task * What exactly did you do (or not do) that was effective (or ineffective)? Booting this specific kernel, older kernels work. * What was the outcome of this action? Kernel panic, can't boot system. * What outcome did you expect instead? Booting the system the nromal way on the specified hardware. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge [8086:7191] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- Reset- FastB2B+ PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:10.0 Ethernet controller [0200]: 3Com Corporation 3c905C-TX/TX-M [Tornado] [10b7:9200] (rev 78) Subsystem: 3Com Corporation 3C905CX-TX/TX-M Fast Etherlink for PC Management NIC [10b7:1000] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: 3c59x Kernel modules: 3c59x 00:14.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: mgag200 Kernel modules: matroxfb_base, mgag200 ** USB devices: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 5.18.0-3-686-pae (SMP w/1 CPU thread; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-5.18.0-4-686-pae depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod30+20220630-3 ii linux-base 4.9 Versions of packages linux-image-5.18.0-4-686-pae recommends: pn apparmor ii firmware-linux-free 20200122-1 Versions of packages linux-image-5.18.0-4-686-pae suggests: pn debian-kernel-handbook ii grub-pc 2.06-3 pn linux-doc-5.18 Versions of packages linux-image-5.18.0-4-686-pae is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn
Bug#1017425: marked as done ([i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER)
Your message dated Fri, 02 Sep 2022 21:02:09 + with message-id and subject line Bug#1017425: fixed in linux 5.10.140-1 has caused the Debian Bug report #1017425, regarding [i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1017425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.10.136-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 5.10.0-17-686-pae cannot boot on this Pentium III. The fan goes to full speed during initrd loading and the host reboots at that point. There is no screenshot to attach since there is no screen output after the "Loading initrd..." message from GRUB2. Reverting to 5.10.0-16-686-pae, the fan runs at low speed and the host boots normally. Martin-Éric - -- Package-specific info: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 8 model name : Pentium III (Coppermine) stepping: 6 microcode : 0x8 cpu MHz : 865.440 cache size : 256 KB physical id : 0 siblings: 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 mmx fxsr sse cpuid pti bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips: 1730.88 clflush size: 32 cache_alignment : 32 address sizes : 36 bits physical, 32 bits virtual power management: ** Kernel log: boot messages should be attached ** Model information ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub [8086:1130] (rev 02) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 82815 815 Chipset AGP Bridge [8086:1131] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1f.0 ISA bridge [0601]: Intel Corporation 82801BA ISA Bridge (LPC) [8086:2440] (rev 01) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: nouveau Kernel modules: nouveau 02:04.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller [10ec:8169] (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC [10ec:8169] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: r8169 Kernel modules: r8169 02:08.0 Ethernet controller [0200]: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller [8086:2449] (rev 01) Subsystem: Compaq Computer Corporation EtherExpress PRO/100 VM [0e11:0012] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: e100 Kernel modules: e100 02:09.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller [10ec:8169] (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit
Bug#1014787: marked as done (paraview: no render view created)
Your message dated Fri, 02 Sep 2022 20:41:40 + with message-id and subject line Bug#1014787: fixed in paraview 5.11.0~rc1+dfsg-1 has caused the Debian Bug report #1014787, regarding paraview: no render view created 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.) -- 1014787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: paraview Version: 5.10.1-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Paraview 5.10.1-2 upon launch should display the visualization window (a "Layout"). Then, after loading external data or using any data source, it should be rendered in the main layout window. Instead, nothing happens, no rendering is shown, using other views (such as spreadsheet, etc.) is also impossible, Paraview windows is no longer refreshed, making it completely unusable. I will add I'm on a Thinkpad T14, gen1, AMD. I can anclose the lspci etc., for now it suffices to say the video card is shown as, (lspci): 07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev d1) regards WA - -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages paraview depends on: ii libavcodec59 7:5.0.1-3 ii libavformat59 7:5.0.1-3 ii libavutil577:5.0.1-3 ii libc6 2.33-7 ii libdouble-conversion3 3.1.7-4 ii libexpat1 2.4.8-1 ii libfreetype6 2.12.1+dfsg-3 ii libgcc-s1 12.1.0-2 ii libgdal31 3.5.0+dfsg-1+b1 ii libgl2ps1.41.4.2+dfsg1-2 ii libglew2.2 2.2.0-4 ii libglx01.4.0-1 ii libhdf5-103-1 1.10.7+repack-4+b1 ii libjpeg62-turbo1:2.1.2-1 ii liblz4-1 1.9.3-2 ii liblzma5 5.2.5-2.1 ii libnetcdf191:4.9.0-2 ii libogg01.3.5-1 ii libopengl0 1.4.0-1 ii libopenmpi34.1.4-1 ii libpng16-161.6.37-5 ii libpython3.10 3.10.5-1 ii libpython3.9 3.9.13-1 ii libqt5core5a 5.15.4+dfsg-3 ii libqt5gui5 5.15.4+dfsg-3 ii libqt5help55.15.4-2 ii libqt5network5 5.15.4+dfsg-3 ii libqt5widgets5 5.15.4+dfsg-3 ii libstdc++6 12.1.0-2 ii libswscale67:5.0.1-3 ii libtheora0 1.1.1+dfsg.1-16 ii libtiff5 4.4.0-2 ii libx11-6 2:1.7.5-1 ii libxcursor11:1.2.1-1 ii libxml22.9.14+dfsg-1 ii python3-autobahn 22.1.1+dfsg1-2 ii python3-matplotlib 3.5.2-1 ii python3-mpi4py 3.1.3-2 ii python3-six1.16.0-3 ii python3-twisted22.4.0-2 ii tcl [tclsh]8.6.11+1 ii zlib1g 1:1.2.11.dfsg-4 Versions of packages paraview recommends: ii mpi-default-bin 1.14 ii paraview-doc 5.10.1-2 ii python3-paraview [python3-paraview] 5.10.1-2 Versions of packages paraview suggests: ii h5utils 1.13.1-4 ii hdf5-tools 1.10.7+repack-4+b1 - -- no debconf information -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEENHZ/67ZMjPXjhgdLxBIgNKxmSF4FAmLMgewACgkQxBIgNKxm SF4mQgf+PyAScbQMwrMi/95gbK2hWhXsi4FJy0SD6PdMXPXUiTAyh8KDW1ufx9XB CG6+vQnUzZ8LrbxeIvHplZx+n8QN3PTgRNLrGidum7rpaetXd9359FjSQpLwnuWI nAqa0KxM0HnD9e5o847QZz2/3EBgzcuOVAYrMQeqY4BBo01D2XTs+Dfgt1dd+cLf /ZJFGubcS8eFRwMzSeimOsUk07LFTKOP2GnSwqsHoL5sHOZUZs+Op+Pi9reGBdjA KRqPSJFM+KQRpTeE9QRFr47t1unlQq7b+e7TeeQejHYLcu5Kuo/5PrAsWoCjfByo gJSkruQZgMjJovaktKnTZIdA1eDpjQ== =OP7V -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: paraview Source-Version: 5.11.0~rc1+dfsg-1 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of paraview, which is due to be installed in
Bug#1007000: marked as done (thin FTBFS on IPV6-only buildds)
Your message dated Fri, 2 Sep 2022 17:36:09 -0300 with message-id and subject line Re: thin FTBFS on IPV6-only buildds has caused the Debian Bug report #1007000, regarding thin FTBFS on IPV6-only buildds 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.) -- 1007000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: thin Version: 1.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=thin=amd64=1.8.0-1%2Bb2=1646907946=0 ... Thin::Server robustness #>/spec/spec_helper.rb:191 run> terminated with exception (report_on_exception is true): /usr/lib/ruby/vendor_ruby/eventmachine.rb:532:in `start_tcp_server': no acceptor (port is in use or requires root privileges) (RuntimeError) from /usr/lib/ruby/vendor_ruby/eventmachine.rb:532:in `start_server' from /<>/lib/thin/backends/tcp_server.rb:16:in `connect' from /<>/lib/thin/backends/base.rb:65:in `block in start' from /usr/lib/ruby/vendor_ruby/eventmachine.rb:196:in `run_machine' from /usr/lib/ruby/vendor_ruby/eventmachine.rb:196:in `run' from /<>/lib/thin/backends/base.rb:75:in `start' from /<>/lib/thin/server.rb:162:in `start' from /<>/spec/spec_helper.rb:191:in `block in start_server' E: Build killed with signal TERM after 150 minutes of inactivity --- End Message --- --- Begin Message --- On Thu, 1 Sep 2022 15:36:43 -0300 Lucas Kanashiro wrote: > This is a consequence of this bug filed against ruby-eventmachine: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998097 > The bug mentioned above was already fixed. -- Lucas Kanashiro--- End Message ---
Processed: Bug#995387 in package dpkg marked as pending
Processing control commands:
> tag 995387 pending
Bug #995387 {Done: Guillem Jover } [dpkg] dpkg:
remove-on-upgrade deletes symlink targets owned by another package
Added tag(s) pending.
--
995387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#995387: in package dpkg marked as pending
Control: tag 995387 pending Hi! Bug #995387 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=741d474aa --- dpkg: Fix conffile removal-on-upgrade handling We need to check for file conflicts during conffile removal, otherwise we might end up removing files from any other packages that has started owning them since we targeted the pathname for removal. We remove the conffiles during upgrade, as configure is a local action that does not load all file lists files, so we cannot check for file conflicts. Closes: #995387 Stable-Candidate: 1.20.x (cherry picked from commit 20e181fc2030385488e3db2d4cc3ce4114f0a498)
Processed: Bug#1008478 in package dpkg marked as pending
Processing control commands:
> tag 1008478 pending
Bug #1008478 {Done: Guillem Jover } [dpkg]
dpkg-fsys-usrunmess depends on umask 022
Added tag(s) pending.
--
1008478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1008478: in package dpkg marked as pending
Control: tag 1008478 pending Hi! Bug #1008478 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=699c417f5 --- dpkg-fsys-usrunmess: Explicitly set user/group and mode for created dirs We should explicitly set the user/group and mode for the newly created directories, to make sure they end up with the expected values, instead of assuming a good environment (umask and user/group). We will still be setting a known umask in a subsequent commit as a defensive measure. Closes: #1008478 (cherry picked from commit 77756084e9e50d7a8578259ee56e64dcf4f6f9a0)
Bug#1008316: in package dpkg marked as pending
Control: tag 1008316 pending Hi! Bug #1008316 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=7086b1b62 --- dpkg-fsys-usrunmess: Special case untracked kernel module files Kernel module files are required as part of the system boot, so we need to make sure any such files gets moved or the system might end up not being able to boot, once the initramfs images get regenerated. In particular, kernel module files are easily found on systems as untracked pathnames in the filesystem, either from custom built kernels, or as part of modules built via machinery such as DKMS. One complication is that there appears to be some documentation referencing /usr/lib/modules/ pathnames for at least apache, python and ruby module locations. Which we do not want to be moving. To limit these unknowns, and as we are dealing with untracked pathnames, we will restrict moving subdirectories that start with a digit, which matches Linux and kFreeBSD module locations, in addition to the modprobe.conf filename. Closes: #1008316 (cherry picked from commit 48e33c40691596b3bf91b86b50a8aa164b585639) (cherry picked from commit b1898b812b71f64082107d4e2f98ccf020d18b70)
Bug#1000421: in package dpkg marked as pending
Control: tag 1000421 pending Hi! Bug #1000421 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=5a9f336dc --- Dpkg::Shlibs::Objdump: Fix apply_relocations to work with versioned symbols Since binutils 2.26 (commit bb4d2ac2cc637c61232624d9d359b8d3f031e3e9) versioned symbols in copy relocations are output as «symbol@@version» when they are in an undefined section (otherwise they use «@»). We were not taking this into account which meant these did not match and did not get marked as undefined, and got ignored for symbol dependency calculation. Try both the version qualified symbol and the bare symbol name to cope with old and new formats. Known to be affected are at least any-amd64, hppa and m68k architectures. Closes: #1000421 (cherry picked from commit ecbd9f1b1f248fb5be182b3a78bc613591dba865)
Processed: Bug#1008316 in package dpkg marked as pending
Processing control commands:
> tag 1008316 pending
Bug #1008316 {Done: Guillem Jover } [dpkg]
dpkg-fsys-usrunmess: Does not deal with untracked kernel modules
Ignoring request to alter tags of bug #1008316 to the same tags previously set
--
1008316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#1000421 in package dpkg marked as pending
Processing control commands:
> tag 1000421 pending
Bug #1000421 {Done: Guillem Jover } [dpkg-dev]
dpkg-shlibdeps: Wrong minimum version requirement on libc6
Added tag(s) pending.
--
1000421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998097: marked as pending in ruby-eventmachine
Control: tag -1 pending Hello, Bug #998097 in ruby-eventmachine reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-eventmachine/-/commit/32a494c56ff57e33f963e4642e6ae949fe926f86 Add patch to skip tests which require non-empty resolv.conf (Closes: #998097) (this message was generated automatically) -- Greetings https://bugs.debian.org/998097
Processed: Bug#998097 marked as pending in ruby-eventmachine
Processing control commands: > tag -1 pending Bug #998097 [src:ruby-eventmachine] ruby-eventmachine FTBFS on IPV6-only buildds and accesses the internet during the build Added tag(s) pending. -- 998097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018972: blasr autopkgtest regression with pbbam 2.1.0
Source: pbbam Version: 2.1.0+dfsg-1 Severity: serious Affects: blasr 5.3.5+dfsg-4 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic Hi Andreas, blasr's autopkgtests fail on amd64 when blasr is rebuilt against pbbam 2.1.0: [...] autopkgtest [11:27:53]: test run-unit-test: [--- [INFO] 2022-08-28T11:27:53 [blasr] started. [INFO] 2022-08-28T11:27:53 [blasr] ended. [INFO] 2022-08-28T11:27:53 [blasr] started. [INFO] 2022-08-28T11:27:53 [blasr] ended. output: OK md5sum: alignment.sam.check: FAILED WARNING: 1 computed checksum did NOT match autopkgtest [11:27:54]: test run-unit-test: ---] [...] (https://ci.debian.net/packages/b/blasr/unstable/amd64/) Unfortunately, Debian's autopkgtest infrastructure does not appropriately handle autopkgtests for binNMUs, which means this regression did not block pbbam and the new blasr from entering testing. I am not sure what the severity of this regression is, but since an autopkgtest regression would normally block testing promotion, I have filed this bug as 'serious'. If it's determined that the impact on blasr doesn't make blasr unreleasable, feel free to downgrade. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1017015: gnome-console: bugs after switch to GTK4
Control: forwarded -1 https://gitlab.gnome.org/GNOME/vte/-/issues/2584 The Open Link bug is fixed in the latest vte2.91. I'm setting the forwarded link to the end of line selection bug which is really annoying to me. Thank you, Jeremy Bicha
Processed: Re: Bug#1017015: gnome-console: bugs after switch to GTK4
Processing control commands: > forwarded -1 https://gitlab.gnome.org/GNOME/vte/-/issues/2584 Bug #1017015 [src:gnome-console] gnome-console: bugs after switch to GTK4 Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/vte/-/issues/2584'. -- 1017015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#716386: [Mayhem] Bug report on tetradraw: tetraview crashes with exit status 139
On Fri, Feb 18, 2022 at 03:12:14PM +0100, Rhonda D'Vine wrote:
> Dear Lee,
>
> * Lee Garrett [2022-02-09 18:27:38 CET]:
> > Package: tetradraw
> > Version: 2.0.3-9+b2
> > Followup-For: Bug #716386
> > X-Debbugs-Cc: deb...@rocketjump.eu
> >
> > Hi Rhonda,
> >
> > sorry to grave dig this bug report, but it seems that tetradraw might be
> > broken
> > for a couple of releases now. On bullseye it segfaults with rc 139. A few
> > people
> > in #debian reported the same issue, so it looks like it's 100% reproducible.
> > Since I'd love to make some nice ascii art for my /etc/motd, it would be
> > nice if
> > you could find the time to fix it. Thanks in advance!
>
> You are definitely right on that. I think in one of the bugs there is
> a workaround for the issue: It runs smoothly on a virtual console
> instead of within a terminal in Xorg. So if that's possible, I suggest
> to go that path.
>
> What also works is starting it with TERM=linux. This gives a hint in
> what area the issue may lie. I am unfortunately not a well enough coder
> to dig further into it, but those are the workarounds that I am aware
> of, and might give people a hint on where to look into for fixing this.
I was looking at this and the segfault is from src/term.c, line 205.
The part of the code is:
for(count = 1; count < COLOR_PAIRS; count++) {
init_pair(count, count % COLORS, count / COLORS);
colours[count % COLORS][count / COLORS] = count;
}
Further debugging showed COLOR_PAIRS was 65536, so the value of count can be
65535, and COLORS is defined as 256. So, colours[count % COLORS][count / COLORS]
can become colours[65535 % 256][65535 / 256] which means the max array location
it can try to access of colours[0][255]. But colours is declared as
colours[8][8],
so its trying to access memory locations beyond what has been allocated to it.
The following patch will stop the segfault but I dont know what tetradraw is
supposed
to do to check if it has other impact or not.
--- tetradraw-2.0.3.orig/src/global.h
+++ tetradraw-2.0.3/src/global.h
@@ -5,7 +5,7 @@
extern coordinate td_maxx;
extern coordinate td_maxy;
-extern colour colours[COLOURS][COLOURS];
+extern colour colours[256][256];
extern int remote;
extern int pagecnt;
extern char default_highascii[20][10];
--- tetradraw-2.0.3.orig/src/tetradraw.c
+++ tetradraw-2.0.3/src/tetradraw.c
@@ -45,7 +45,7 @@ void load_options();
coordinate td_maxx = 0;
coordinate td_maxy = 0;
-colour colours[COLOURS][COLOURS];
+colour colours[256][256];
canvas *pages[9] = {
NULL,
NULL,
--- tetradraw-2.0.3.orig/src/tetraview.c
+++ tetradraw-2.0.3/src/tetraview.c
@@ -41,7 +41,7 @@
coordinate td_maxx = 0;
coordinate td_maxy = 0;
-colour colours[COLOURS][COLOURS];
+colour colours[256][256];
int remote = 0;
--
Regards
Sudip
Bug#1018971: poppler: CVE-2022-38784
Source: poppler Version: 22.08.0-2 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for poppler. CVE-2022-38784[0]: | Poppler prior to and including 22.08.0 contains an integer overflow in | the JBIG2 decoder (JBIG2Stream::readTextRegionSeg() in JBIGStream.cc). | Processing a specially crafted PDF file or JBIG2 image could lead to a | crash or the execution of arbitrary code. This is similar to the | vulnerability described by CVE-2022-38171 in Xpdf. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-38784 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-38784 [1] https://gitlab.freedesktop.org/poppler/poppler/-/commit/27354e9d9696ee2bc063910a6c9a6b27c5184a52 [2] https://gist.github.com/zmanion/b2ed0d1a0cec163ecd07d5e3d9740dc6 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1018967: marked as done (txt2regex: autopkgtest needs update for bash 2.5)
Your message dated Fri, 02 Sep 2022 19:35:25 + with message-id and subject line Bug#1018967: fixed in txt2regex 0.9-5 has caused the Debian Bug report #1018967, regarding txt2regex: autopkgtest needs update for bash 2.5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1018967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: txt2regex Version: 0.9-4 Severity: serious Tags: ftbfs User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer Since the upload of bash 5.2~rc2-2 to unstable, txt2regex's autopkgtests have been failing [1]. I've copied what I hope is the relevant part of the log below. This change also causes txt2regex to FTBFS in unstable. Regards Graham [1] https://ci.debian.net/packages/t/txt2regex/testing/amd64/ -- [FAILED #53, line 77] txt2regex --all --history '241¤\' @@ -1,23 +1,23 @@ - Regex awk : [\\] - Regex chicken : [] + Regex awk : [\] + Regex chicken : [\\] Regex ed: [\] Regex egrep : [\] - Regex emacs : [] - Regex expect: [\\] + Regex emacs : [\\] + Regex expect: [\] Regex find : [\] - Regex gawk : [\\] + Regex gawk : [\] Regex grep : [\] - Regex javascript: [\\] - Regex lex : [\\] - Regex mawk : [\\] - Regex mysql : [] - Regex perl : [\\] - Regex php : [] - Regex postgres : [\\] + Regex javascript: [\] + Regex lex : [\] + Regex mawk : [\] + Regex mysql : [\\] + Regex perl : [\] + Regex php : [\\] + Regex postgres : [\] Regex procmail : [\] - Regex python: [\\] + Regex python: [\] Regex sed : [\] - Regex tcl : [\\] + Regex tcl : [\] Regex vi: [\] - Regex vim : [\\] + Regex vim : [\] -- --- End Message --- --- Begin Message --- Source: txt2regex Source-Version: 0.9-5 Done: Rene Engelhard We believe that the bug you reported is fixed in the latest version of txt2regex, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard (supplier of updated txt2regex package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Sep 2022 21:21:16 +0200 Source: txt2regex Architecture: source Version: 0.9-5 Distribution: unstable Urgency: medium Maintainer: Rene Engelhard Changed-By: Rene Engelhard Closes: 1018967 Changes: txt2regex (0.9-5) unstable; urgency=medium . * f88d45156ee20c1cdb1e70cb410a4d188a384341.patch: add from https://github.com/aureliojargas/txt2regex/pull/12 (thanks Graham Inggs) to fix with bash 5.2 (closes: #1018967) Checksums-Sha1: 3e755397bfdeba0d22df7c97572dddb5689f862f 1821 txt2regex_0.9-5.dsc 15d8a85dbaec6c30f7be2964dabda694bef7a966 5124 txt2regex_0.9-5.debian.tar.xz adc38d153dd3b047140dd29f4e48fdf030738913 6904 txt2regex_0.9-5_source.buildinfo Checksums-Sha256: 8d3f12993b2bdc8d778ef95c05667c11a34c6b9c53b1e4fec8d3cebe7ba89ec6 1821 txt2regex_0.9-5.dsc e28c2b5921e3088bbc1bb74bc1b88084a507bb74f8607f3851fdce083d638707 5124 txt2regex_0.9-5.debian.tar.xz ff1ef67225982d447ada33b6fd2c00e144ca78c72a4bf23cf08e5e737c120a70 6904 txt2regex_0.9-5_source.buildinfo Files: 64b4211b75a6b2e6d464a00baa6016d3 1821 utils optional txt2regex_0.9-5.dsc b701bc7f652420b8a129073bf0805b42 5124 utils optional txt2regex_0.9-5.debian.tar.xz 825e18696781b801c730175c467b3763 6904 utils optional txt2regex_0.9-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAmMSWHcQHHJlbmVAZGVi aWFuLm9yZwAKCRAKoEVx0D4+cG3GEADi8Gg+S/6Y8MUU+Jz+RIiGHx9sS4s7uqCw x+EuRotxGB87zAk6jqicAimpZDssYZ5i4dC23FXHVsZP/OmvWmuilHwshLg2k2MD qRTPUnzh7/gVP2nrCJ026wwts7OhQhT6P1YcaeVKvlUoR209ZmKxCMOP4tmoijfn 6PyzOM0FUPEIW1/5zT/y1q9W6zqZOvee2yreaKUnn3ipA/wgKchYRFEtfBz/+CJE 9b8vi0fd7EjFK12T9qKwQxiPzAieLCGoEqjKqcMaYnON2XPvH+XfNbQug+0hEK0I /+dKS4FOENKa7ZrP+Tmcdi/+/kKkccSoCl/HfOY5tMp/0Ol2nOL3jAAd86EOquTr
Bug#1018970: node-matrix-js-sdk: CVE-2022-36059
Source: node-matrix-js-sdk Version: 9.11.0+~cs9.9.16-2 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for node-matrix-js-sdk. CVE-2022-36059[0]: If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-36059 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36059 [1] https://matrix.org/blog/2022/08/31/security-releases-matrix-js-sdk-19-4-0-and-matrix-react-sdk-3-53-0/ [2] https://github.com/matrix-org/matrix-js-sdk/commit/8716c1ab9ba93659173b806097c46a2be115199f Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#966108: closing 966108
close 966108 thanks now built on the buildds.
Processed: closing 966108
Processing commands for cont...@bugs.debian.org: > close 966108 Bug #966108 [src:genesisplusgx] genesisplusgx: FTBFS with GCC 10: multiple definition of ... due to -fno-common Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 966108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018969: assaultcube-data: difficult copyright situation
X-Debbugs-CC: 935...@bugs.debian.org Package: assaultcube-data Version: 1.2.0.2.1-3 Severity: serious Justification: Policy 2.2.3 Control: affects -1 assaultcube When I was looking into updating assaultcube to the new upstream release, I was prompted by #935669#57 to look into the copyright situation.. Before diving into it, I'd like to state that I believe upstream that hey have done their due diligence to ensure that they are able to redistribute their package. Upstream tells on their license site [1[ that it is ok to distribute the package unmodified. they gave Debian specic license to repack where appropiate, but only to make packaging easier. [2] [3] however they reserve the right revoke that license *at any time*; even if they try to find a resolution before, but they explictily reserve the right to revoke. Additionally, looking in the assaultcube data files package, there are several files with unclear copyright status or file origin, a few are just "all rights reserved". I fear that above puts a risk on Debian that I'm not sure if we should take this. My proposal to resolve would be to modify assaultcube-data, so that it will directly download and install the *data* files needed to play assaultcube. (The package assaultcube -- without -data is the game engine and licensed under a zlib-like license. This engine package is not a problem at all to have in Debian) [1] https://assault.cubers.net/docs/license.html [2] https://salsa.debian.org/games-team/assaultcube-data/-/blob/master/debian/copyright#L119 [3] http://forum.cubers.net/thread-4150.html -- tobi
Processed: assaultcube-data: difficult copyright situation
Processing control commands: > affects -1 assaultcube Bug #1018969 [assaultcube-data] assaultcube-data: difficult copyright situation Added indication that 1018969 affects assaultcube -- 1018969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1012935
Processing commands for cont...@bugs.debian.org: > tags 1012935 + pending Bug #1012935 [src:gf-complete] gf-complete: ftbfs with GCC-12 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018942: marked as done (zookeeper: Can attempt to access the network during build)
Your message dated Fri, 02 Sep 2022 18:37:34 +
with message-id
and subject line Bug#1018942: fixed in zookeeper 3.8.0-8
has caused the Debian Bug report #1018942,
regarding zookeeper: Can attempt to access the network during build
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.)
--
1018942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zookeeper
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
X-Debbugs-Cc: scho...@ubuntu.com
We observed a FTBFS on amd64 in Ubuntu due to a DNS resolution error on
google.com, see https://bugs.launchpad.net/ubuntu/+source/zookeeper/+bug/1988541
for more details.
I don't exactly know why this hasn't happened during the Debian build,
but in any case, you'll find attached a debdiff to address the issue.
Cheers,
Simon
-- System Information:
Debian Release: bookworm/sid
APT prefers jammy-updates
APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'),
(100, 'jammy-backports'), (50, 'jammy-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-46-lowlatency (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru zookeeper-3.8.0/debian/patches/30-skip-tests-network.patch
zookeeper-3.8.0/debian/patches/30-skip-tests-network.patch
--- zookeeper-3.8.0/debian/patches/30-skip-tests-network.patch 2022-06-27
09:11:31.0 +0200
+++ zookeeper-3.8.0/debian/patches/30-skip-tests-network.patch 2022-09-02
11:10:51.0 +0200
@@ -456,3 +456,21 @@
@Test
public void testVersionOfDynamicFilename() throws Exception {
final int SERVER_COUNT = 5;
+---
a/zookeeper-server/src/test/java/org/apache/zookeeper/server/quorum/MultipleAddressesTest.java
b/zookeeper-server/src/test/java/org/apache/zookeeper/server/quorum/MultipleAddressesTest.java
+@@ -37,6 +37,7 @@
+ import java.util.stream.IntStream;
+ import org.apache.commons.collections4.CollectionUtils;
+ import org.apache.zookeeper.PortAssignment;
++import org.junit.jupiter.api.Disabled;
+ import org.junit.jupiter.api.Test;
+
+ public class MultipleAddressesTest {
+@@ -135,6 +136,7 @@
+ assertEquals(unreachableAddress, actualReturnedAddress);
+ }
+
++@Disabled("no network on debian buildds")
+ @Test
+ public void testRecreateSocketAddresses() throws UnknownHostException {
+ List searchedAddresses =
Arrays.stream(InetAddress.getAllByName("google.com"))
--- End Message ---
--- Begin Message ---
Source: zookeeper
Source-Version: 3.8.0-8
Done: Pierre Gruet
We believe that the bug you reported is fixed in the latest version of
zookeeper, 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 1018...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pierre Gruet (supplier of updated zookeeper package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 02 Sep 2022 18:17:29 +0200
Source: zookeeper
Architecture: source
Version: 3.8.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
Changed-By: Pierre Gruet
Closes: 1018942
Changes:
zookeeper (3.8.0-8) unstable; urgency=medium
.
* Team upload
* Skipping one more test accessing the network, thanks to Simon Chopin
(Closes: #1018942)
* Enlarging another time limit in a test
Checksums-Sha1:
530a80b433e2efa56b10ba32bfd2439c4758b3e5 3763 zookeeper_3.8.0-8.dsc
6bca39ea0c6c2048befd65008d23265c23c1a599 88916 zookeeper_3.8.0-8.debian.tar.xz
547d5238796bb156d104f6e719a3285a5574258a 19103
zookeeper_3.8.0-8_source.buildinfo
Checksums-Sha256:
42cd7edfcea5f5cf560e84995cbc2eba8a51b89bcf7d1b0db852a8b51138d82e 3763
zookeeper_3.8.0-8.dsc
Bug#1018967: txt2regex: autopkgtest needs update for bash 2.5
Source: txt2regex Version: 0.9-4 Severity: serious Tags: ftbfs User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer Since the upload of bash 5.2~rc2-2 to unstable, txt2regex's autopkgtests have been failing [1]. I've copied what I hope is the relevant part of the log below. This change also causes txt2regex to FTBFS in unstable. Regards Graham [1] https://ci.debian.net/packages/t/txt2regex/testing/amd64/ -- [FAILED #53, line 77] txt2regex --all --history '241¤\' @@ -1,23 +1,23 @@ - Regex awk : [\\] - Regex chicken : [] + Regex awk : [\] + Regex chicken : [\\] Regex ed: [\] Regex egrep : [\] - Regex emacs : [] - Regex expect: [\\] + Regex emacs : [\\] + Regex expect: [\] Regex find : [\] - Regex gawk : [\\] + Regex gawk : [\] Regex grep : [\] - Regex javascript: [\\] - Regex lex : [\\] - Regex mawk : [\\] - Regex mysql : [] - Regex perl : [\\] - Regex php : [] - Regex postgres : [\\] + Regex javascript: [\] + Regex lex : [\] + Regex mawk : [\] + Regex mysql : [\\] + Regex perl : [\] + Regex php : [\\] + Regex postgres : [\] Regex procmail : [\] - Regex python: [\\] + Regex python: [\] Regex sed : [\] - Regex tcl : [\\] + Regex tcl : [\] Regex vi: [\] - Regex vim : [\\] + Regex vim : [\] --
Bug#1015861: marked as done (bamtools: FTBFS with upcoming doxygen 1.9.4)
Your message dated Fri, 02 Sep 2022 18:18:56 + with message-id and subject line Bug#1015861: fixed in bamtools 2.5.2+dfsg-2 has caused the Debian Bug report #1015861, regarding bamtools: FTBFS with upcoming doxygen 1.9.4 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.) -- 1015861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bamtools Version: 2.5.1+dfsg-10+b1 Severity: important Tags: ftbfs X-Debbugs-Cc: paolo.gre...@libpf.com Hello, I am about to upload the current version of doxygen, before doing that I run a quick scan of build-deps of doxygen (https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.4-1_amd64-partial) and found that this package FTBFS with this error: mv: cannot stat 'docs/Doxyfile.bak': No such file or directory The error does not occur with the current version of doxygen (1.9.1). I attach the build logs. Paolo -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-16-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages bamtools depends on: ii libbamtools2.5.1 2.5.1+dfsg-10+b1 ii libc6 2.33-7 ii libgcc-s1 12.1.0-5 ii libjsoncpp25 1.9.5-4 ii libstdc++612.1.0-5 bamtools recommends no packages. bamtools suggests no packages. -- no debconf information 1_9_1.log.xz Description: application/xz 1_9_4.log.xz Description: application/xz --- End Message --- --- Begin Message --- Source: bamtools Source-Version: 2.5.2+dfsg-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of bamtools, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated bamtools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Sep 2022 19:53:29 +0200 Source: bamtools Architecture: source Version: 2.5.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1015861 Changes: bamtools (2.5.2+dfsg-2) unstable; urgency=medium . * Do not try to move Doxyfile.bak which does not exist any more in doxygen 1.9.4 Closes: #1015861 * Build-Depends: pkg-config (since cmake is asking for it) * Standards-Version: 4.6.1 (routine-update) Checksums-Sha1: b379dc1608ef92ff09dd0c7cb8b05bd361cfd513 2356 bamtools_2.5.2+dfsg-2.dsc 0eda972c5c9f265646356e628cf298f4775474d5 9980 bamtools_2.5.2+dfsg-2.debian.tar.xz 320d877876f4302027cacaf925ef83743b864d28 9263 bamtools_2.5.2+dfsg-2_amd64.buildinfo Checksums-Sha256: 21ee202eeaabd3d4032d4e3a45e1f7906133f9d31c12f7bbffc594bc49fe0883 2356 bamtools_2.5.2+dfsg-2.dsc c4b626900aea55388f4793e45a5b78f7def79e73d724475a555e458b7216642a 9980 bamtools_2.5.2+dfsg-2.debian.tar.xz c8f13da446cb5b98af7fac6f75728c3b180602690ceeabd0267959995af32789 9263 bamtools_2.5.2+dfsg-2_amd64.buildinfo Files: 5e10693daedc4a30b7666bb8bbaeaf6d 2356 science optional bamtools_2.5.2+dfsg-2.dsc 0c6c64e4e6695688f87288a5f868d4a1 9980 science optional bamtools_2.5.2+dfsg-2.debian.tar.xz 3272b653fc1838d8557cf7ae6a53798e 9263 science optional bamtools_2.5.2+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmMSQ8IWHGVtb2xsaWVy QGVtbHdrczk5OS5ldQAKCRB5PPZ+jw0R2lsSD/9//KZwCweFxl+w6/ZX3+XmuOXK MPx98T1PAa/o0ymA0JNapj7dESRoV4xF/PW68T6gMztpuDjlWAOqzoZeXrXC+6gZ gelHsnsnTe1uAeNmUIk4+y9CwLhPEe23ZsCe8BYNPOTCmnF5HIf3t31kjj04EfCv EkYSo0WTutVa+EFLBLgZkn0msil/pqIq29226c1+n8S2oPS2+DfvP0QnHywYPIEj Qakx3wK1q2UjXzJNqGySkriUkeP+DsRGUeJQ8qTMeqLNrXabKt0B+06gTp9XNaKg T12nPJhrL0UoEvVTIgKncw6LPfrwIBEhkQIOXA/+WQFa3IXB+wTNrZ8cRdUdoXxG w0ijDXA/lj3DfCwstdzNcigSR3m+TnVuxPaiDRjv+Ni6N2g/IVqm4QF/IcGX7ixJ
Processed: found 1018964 in 14.2.21-1
Processing commands for cont...@bugs.debian.org: > found 1018964 14.2.21-1 Bug #1018964 [src:ceph] ceph: sources(multiple js dependencies) are missing for ceph dashboard Marked as found in versions ceph/14.2.21-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1018964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018964: ceph: sources(multiple js dependencies) are missing for ceph dashboard
Source: ceph Version: 16.2.10+ds-2 Severity: serious In lintian-overrides you say: https://salsa.debian.org/ceph-team/ceph/-/blob/debian/16.2.10+ds-2/debian/source/lintian-overrides#L7 # pybind js source is in src/pybind/mgr/dashboard/frontend/src ceph source: source-is-missing src/pybind/mgr/dashboard/frontend/dist/*.js However this is not true. The ceph dashboard is a modern javascript project, and uses the angular framework. Ceph upstream distributes the prebuilt js files in src/pybind/mgr/dashboard/frontend/dist/*.js First, this is already problematic, since you are expected to build it from source. But it may not violate the policy. Then the source is not only src/pybind/mgr/dashboard/frontend/src, you need all sources of build-dependencies, which are listed at https://salsa.debian.org/ceph-team/ceph/-/blob/debian/16.2.10+ds-2/src/pybind/mgr/dashboard/frontend/package.json See dependencies and devDependenciessources in the package.json file. These are not included in the ceph source package. Modern javascript projects currently are difficult to build in Debian... The only _clean_ solution I can think of is to drop ceph-mgr-dashboard from Debian... But probably there are workarounds to conform our policy. -- Shengjing Zhu
Bug#1018743: squid: build failures because of -Wall -Werror
See the discussion at https://launchpad.net/bugs/1988217 which links to an upstream fix for the new build warning. Thank you, Jeremy Bicha
Bug#1009392: marked as done (flit: FTBFS: dh_usrlocal: error: debian/flit/usr/local/bin/flit is not a directory)
Your message dated Fri, 02 Sep 2022 17:34:03 + with message-id and subject line Bug#1009392: fixed in flit 3.7.1-1 has caused the Debian Bug report #1009392, regarding flit: FTBFS: dh_usrlocal: error: debian/flit/usr/local/bin/flit is not a directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1009392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flit Version: 3.6.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_python3 -p flit > make[1]: Leaving directory '/<>' >dh_lintian >dh_perl >dh_usrlocal > dh_usrlocal: error: debian/flit/usr/local/bin/flit is not a directory > make: *** [debian/rules:11: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/04/12/flit_3.6.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: flit Source-Version: 3.7.1-1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of flit, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated flit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Sep 2022 18:58:37 +0200 Source: flit Architecture: source Version: 3.7.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1009392 Changes: flit (3.7.1-1) unstable; urgency=medium . * Team upload. * New upstream release. * Refresh patches. * Build with pybuild, fixing FTBFS. (Closes: #1009392) * Patch: Build flit with the local flit_core. * Bump Standards-Version to 4.6.1, no changes needed. * Add myself to copyright. Checksums-Sha1: 61475d953b90bbfc4111feda2b1919b4aecdfd1e 1623 flit_3.7.1-1.dsc cc7db9c37d3018d9bfb4e61d860fb761634b8085 136642 flit_3.7.1.orig.tar.gz 305781dcdd824971aa20e0bf15c34e731f5737bb 12456 flit_3.7.1-1.debian.tar.xz af09a601a0faa84b51bb7e4274564111f855429e 6553 flit_3.7.1-1_source.buildinfo Checksums-Sha256: 9c372b90db6dfda3cd472e89d300720cd4c6b6c95344336ae32ba83e352730ad 1623 flit_3.7.1-1.dsc 3c9bd9c140515bfe62dd938c6610d10d6efb9e35cc647fc614fe5fb3a5036682 136642 flit_3.7.1.orig.tar.gz da55d7e37d82004db78084fad7cf72900f84a1f186350c5845fa0cc6e22d2b8e 12456 flit_3.7.1-1.debian.tar.xz 616aa071f1831667b1af1a4a1a83fb23217f2c5c3f512931dadfae52e9d53848 6553 flit_3.7.1-1_source.buildinfo Files: 1ab1d5d272642af4ef82d6f4c0d9a216 1623 python optional flit_3.7.1-1.dsc 75fd3e3c6c9f7c719dc164c05dabab4f 136642 python optional flit_3.7.1.orig.tar.gz 0d2017d423a27bab9ff01ecb1b36062f 12456 python optional flit_3.7.1-1.debian.tar.xz 825f47d75b8505d31178ecf4a5879ef8 6553 python optional flit_3.7.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYxI5tgAKCRBHew2wJjpU 2HvtAQDFFaudK1+pFTOnvPY1glD4i+sWo37Lg+9LjT7ENIYsQAEAtKHNDxiWmTuI zFQQGsvQ8YwBOQDnf+sE3tPbywj0Og0= =VFpe -END PGP SIGNATURE End Message ---
Bug#563095: marked as done (memtest86: does not install in chroot/debian-live)
Your message dated Fri, 02 Sep 2022 17:32:23 + with message-id and subject line Bug#1016189: Removed package(s) from unstable has caused the Debian Bug report #563095, regarding memtest86: does not install in chroot/debian-live 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.) -- 563095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: memtest86 Version: 3.4-2 Severity: normal Setting up memtest86 (3.5-2.1) ... /usr/sbin/grub-probe: error: cannot find a device for /. dpkg: error processing memtest86 (--configure): subprocess installed post-installation script returned error exit status 1 -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (300, 'unstable'), (290, 'stable-i386'), (280, 'testing-i386'), (270, 'unstable-i386'), (1, 'experimental-i386'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash memtest86 depends on no packages. memtest86 recommends no packages. Versions of packages memtest86 suggests: ii grub2 1.96+20080724-16 GRand Unified Bootloader, version pn hwtools(no description available) pn kernel-patch-badram(no description available) ii memtest86+ 2.01-1.1 thorough real-mode memory tester pn memtester (no description available) ii mtools 3.9.11-1 Tools for manipulating MSDOS files -- no debconf information --- End Message --- --- Begin Message --- Version: 4.3.7-4+rm Dear submitter, as the package memtest86 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1016189 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#540972: marked as done (After moving to grub-pc memtest86+ does not launch.)
Your message dated Fri, 02 Sep 2022 17:32:23 +
with message-id
and subject line Bug#1016189: Removed package(s) from unstable
has caused the Debian Bug report #540972,
regarding After moving to grub-pc memtest86+ does not launch.
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.)
--
540972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-pc
Version: 1.96+20090725-1
Severity: normal
After moving to grub-pc, memtest86+ does not launch. I tried patch from
bug report #539907 but it still does not launch: 'error: file not found'.
But the patch from #539907 does fix this:
Warning: update-grub_lib is deprecated use grub-mkconfig_lib instead
And also changes 'linux' to 'linux16'
A patch will be submitted shortly, that includes the fixes from #539907 and
a fix for this issue. Will report back once it's submitted.
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/root / ext4 rw,noatime,errors=remount-ro,barrier=1,data=ordered 0 0
/dev/hda1 /boot ext3 rw,noatime,errors=continue,data=ordered 0 0
/dev/hda4 /home ext4 rw,noatime,barrier=1,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/hda
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
set root=(hd0,2)
search --no-floppy --fs-uuid --set 1eb15a55-80d3-4049-a3a2-6a17c99237f5
if loadfont /usr/share/grub/ascii.pf2 ; then
set gfxmode=1024x768
set gfxpayload=1024x768x16
insmod gfxterm
insmod vbe
if terminal_output.gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, Linux 2.6.30.4" {
set root=(hd0,1)
search --no-floppy --fs-uuid --set 6ab54cdd-240d-4a96-8fb5-70c2c1722723
linux /vmlinuz-2.6.30.4 root=/dev/hda2 ro quiet
}
menuentry "Debian GNU/Linux, Linux 2.6.30.4 (recovery mode)" {
set root=(hd0,1)
search --no-floppy --fs-uuid --set 6ab54cdd-240d-4a96-8fb5-70c2c1722723
linux /vmlinuz-2.6.30.4 root=/dev/hda2 ro single
}
menuentry "Debian GNU/Linux, Linux 2.6.30-1-686" {
set root=(hd0,1)
search --no-floppy --fs-uuid --set 6ab54cdd-240d-4a96-8fb5-70c2c1722723
linux /vmlinuz-2.6.30-1-686
root=UUID=1eb15a55-80d3-4049-a3a2-6a17c99237f5 ro quiet
initrd /initrd.img-2.6.30-1-686
}
menuentry "Debian GNU/Linux, Linux 2.6.30-1-686 (recovery mode)" {
set root=(hd0,1)
search --no-floppy --fs-uuid --set 6ab54cdd-240d-4a96-8fb5-70c2c1722723
linux /vmlinuz-2.6.30-1-686
root=UUID=1eb15a55-80d3-4049-a3a2-6a17c99237f5 ro single
initrd /initrd.img-2.6.30-1-686
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux16 /memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
linux16 /memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###
*** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.30.4 (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0]1.5.27 Debian configuration management sy
ii grub-common 1.96+20090725-1 GRand Unified Bootloader, version
ii libc62.9-12 GNU C Library: Shared libraries
ii ucf 3.0018 Update Configuration File: preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
pn
Bug#970406: marked as done (flowcanvas build-depends unsatisfiable in testing and unstable.)
Your message dated Fri, 02 Sep 2022 17:22:34 + with message-id and subject line Bug#1018903: Removed package(s) from unstable has caused the Debian Bug report #970406, regarding flowcanvas build-depends unsatisfiable in testing and unstable. 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.) -- 970406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flowcanvas Version: 0.7.1+dfsg0-0.5 Severity: serious Tags: bullseye, sid flowcanvas build-depends on the "python" binary package which is no longer built by the "python-defaults" source package. In unstable it is present as a cruft package but said cruft package is uninstallable due to strictly versioned depdencies. In testing it is gone completely. Either way your build-dependencies are unsatisfiable. If you *really* need to stick with python2, you can build-depend on python2 instead and fix any python invocations to invoke that instead of the unversioned python. Ideally though you should be moving to python 3. --- End Message --- --- Begin Message --- Version: 0.7.1+dfsg0-0.5+rm Dear submitter, as the package flowcanvas has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1018903 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1018961: pypandoc tests fail with 2.17.1.1
Source: pypandoc
Version: 1.7.4+ds0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic
Hi Elena,
The pypandoc autopkgtests are failing against pandoc 2.17.1.1 in unstable:
[...]
==
ERROR: test_conversion_from_non_plain_text_file (tests.TestPypandoc)
--
Traceback (most recent call last):
File "/tmp/autopkgtest-lxc.jwltu_fs/downtmp/build.Zuz/src/tests.py", line
407, in test_conversion_from_non_plain_text_file
received = pypandoc.convert_text('# some title\n', to='docx', format='md',
outputfile=file_name)
File
"/tmp/autopkgtest-lxc.jwltu_fs/downtmp/build.Zuz/src/pypandoc/__init__.py",
line 113, in convert_text
return _convert_input(source, format, 'string', to, extra_args=extra_args,
File
"/tmp/autopkgtest-lxc.jwltu_fs/downtmp/build.Zuz/src/pypandoc/__init__.py",
line 372, in _convert_input
raise RuntimeError(
RuntimeError: Pandoc died with exitcode "97" during conversion: Could not find
data file data/data/docx/[Content_Types].xml
[...]
(https://ci.debian.net/packages/p/pypandoc/testing/amd64/)
I don't know if this is just a bug in the pypandoc tests or if it represents
a regression in pypandoc's usability with the new pandoc, or a regression in
pandoc itself. There is a /usr/share/pandoc/data/docx/[Content_Types].xml
in pandoc-data, perhaps this is a path issue?
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
Processed: closing 1012741
Processing commands for cont...@bugs.debian.org:
> # with the upload for bullseye-pu
> close 1012741 5.10.140+1
Bug #1012741 {Done: Salvatore Bonaccorso }
[src:linux-signed-i386] modprobe: ERROR: could not insert 'crc_itu_t': Key was
rejected by service
Bug #1012816 {Done: Salvatore Bonaccorso }
[src:linux-signed-i386] reportbug: Failed to insert module 'firewire_sbp2': Key
was rejected by service
The source 'linux-signed-i386' and version '5.10.140+1' do not appear to match
any binary packages
Marked as fixed in versions linux-signed-i386/5.10.140+1.
Marked as fixed in versions linux-signed-i386/5.10.140+1.
Bug #1012741 {Done: Salvatore Bonaccorso }
[src:linux-signed-i386] modprobe: ERROR: could not insert 'crc_itu_t': Key was
rejected by service
Bug #1012816 {Done: Salvatore Bonaccorso }
[src:linux-signed-i386] reportbug: Failed to insert module 'firewire_sbp2': Key
was rejected by service
Bug 1012741 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1012741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012741
1012816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1009392: marked as pending in flit
Control: tag -1 pending Hello, Bug #1009392 in flit reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/flit/-/commit/ba3b1cf96e4a05d6f9b2c6d259fb475752719c23 Build with pybuild, fixing FTBFS. (Closes: #1009392) (this message was generated automatically) -- Greetings https://bugs.debian.org/1009392
Processed: Bug#1009392 marked as pending in flit
Processing control commands: > tag -1 pending Bug #1009392 [src:flit] flit: FTBFS: dh_usrlocal: error: debian/flit/usr/local/bin/flit is not a directory Added tag(s) pending. -- 1009392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#694320: marked as done ([gsfonts] Fonts include copyrighted adobe fragment all right reserved)
Your message dated Fri, 02 Sep 2022 17:43:12 +0200
with message-id <5cdffb1295988623a01ff6f885c213fdf9d8e5bf.ca...@debian.org>
and subject line Re: [gsfonts] Fonts include copyrighted adobe fragment all
right reserved
has caused the Debian Bug report #694321,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
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.)
--
694321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsfonts
Version: 1:8.11+urwcyr1.0.7~pre44-4.2
Severity: serious
control: block -1 by 694308
This package include copyrighted font hinting from adobe.
For instance
t1disasm /usr/share/fonts/type1/gsfonts/n019024l.pfb | grep -i -A 10 adobe
%!PS-AdobeFont-1.0: NimbusSanL-BoldItal 1.06
%%Title: NimbusSanL-BoldItal
%Version: 1.06
%%CreationDate: Thu Aug 2 14:36:47 2007
%%Creator: frob
%Copyright: Copyright (URW)++,Copyright 1999 by (URW)++ Design &
%Copyright: Development; Cyrillic glyphs added by Valek Filippov (C)
%Copyright: 2001-2005
% Generated by FontForge 20070723 (http://fontforge.sf.net/)
%%EndComments
--
% Copyright (c) 1987-1990 Adobe Systems Incorporated.
% All Rights Reserved.
% This code to be used for Flex and hint replacement.
% Version 1.1
[ {}
{}
{}
{systemdict /internaldict known not
{pop 3}
{1183615869 systemdict /internaldict get exec
dup /startlock known
Thanks
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Version: 2:20200910-2
The gsfonts package has been replaced by fonts-urw-base35.
This package does not include any copyrighted Adobe fragments anymore.
- Fabian
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmMSJJAACgkQy+qOlwzN
Wd9VtxAAjgsI4CYYvJX/R60JfBBdm8OegVMlFU6DLsiINYwzdTrJt9Eci5VlURVk
d4bgyL0KFQwdXhY8zm5cBcpk9pKjbjw/CUWSakRWLWl5NNnPGrqrhBlOEqKagQeR
8f38ZkIs5ScIgED7cotUg7X4PARqx1Dhl63JFgeJmFxu2wGYUlbqxmSE0nRuNpf7
j5akKSkBMDv+VDWu0lVEmHL0IYH7x0sE4LxHyiurydUo0KdGDMPThTWInpyDAIuS
xcpE5aw36sBDiZp/tldqf3+X1zp/YscV4w132ZDKu3/96PyOMtkYOe0srno7BNuj
DTkEJj1nK3Yjn/Tk6P7cURAg1aAHWcXv0hro2o/xoCvos6Qs5sBGodFefF/NQUeU
vOST2pQhM002bL8J49jnGLSdb+JkwRMVlLWDVKMkEB2WzjMJ1nFMM7F+ro36bfWj
zFt7BmmvfrUz5R5d8dPhC3OKXPLjcmYHpqFuBuHGYTW7KHWzIpRQb+Rg9xRsHaML
3i+u60Fczu0BLpymBKPadMaZRH04qUoOOfjKl7BR6Gc3ww73QMQeRRq5eqYqBxqZ
0nMPkSzG4KgS8Lv+d3dH9KpJAW2U+5ob/sAD2Y0KsvkEGiNdmgS+6WSN9sBAs9iu
KOEiIEk/nmzWwwgqVVX4YeBXkNUlBf7RABMOl+tSIinFeNRVWK4=
=I4oF
-END PGP SIGNATURE End Message ---
Bug#694321: marked as done ([gsfonts] Fonts include copyrighted adobe fragment all right reserved)
Your message dated Fri, 02 Sep 2022 17:43:12 +0200
with message-id <5cdffb1295988623a01ff6f885c213fdf9d8e5bf.ca...@debian.org>
and subject line Re: [gsfonts] Fonts include copyrighted adobe fragment all
right reserved
has caused the Debian Bug report #694321,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
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.)
--
694321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsfonts
Version: 1:8.11+urwcyr1.0.7~pre44-4.2
Severity: serious
control: block -1 by 694308
This package include copyrighted font hinting from adobe.
For instance
t1disasm /usr/share/fonts/type1/gsfonts/n019024l.pfb | grep -i -A 10 adobe
%!PS-AdobeFont-1.0: NimbusSanL-BoldItal 1.06
%%Title: NimbusSanL-BoldItal
%Version: 1.06
%%CreationDate: Thu Aug 2 14:36:47 2007
%%Creator: frob
%Copyright: Copyright (URW)++,Copyright 1999 by (URW)++ Design &
%Copyright: Development; Cyrillic glyphs added by Valek Filippov (C)
%Copyright: 2001-2005
% Generated by FontForge 20070723 (http://fontforge.sf.net/)
%%EndComments
--
% Copyright (c) 1987-1990 Adobe Systems Incorporated.
% All Rights Reserved.
% This code to be used for Flex and hint replacement.
% Version 1.1
[ {}
{}
{}
{systemdict /internaldict known not
{pop 3}
{1183615869 systemdict /internaldict get exec
dup /startlock known
Thanks
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Version: 2:20200910-2
The gsfonts package has been replaced by fonts-urw-base35.
This package does not include any copyrighted Adobe fragments anymore.
- Fabian
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmMSJJAACgkQy+qOlwzN
Wd9VtxAAjgsI4CYYvJX/R60JfBBdm8OegVMlFU6DLsiINYwzdTrJt9Eci5VlURVk
d4bgyL0KFQwdXhY8zm5cBcpk9pKjbjw/CUWSakRWLWl5NNnPGrqrhBlOEqKagQeR
8f38ZkIs5ScIgED7cotUg7X4PARqx1Dhl63JFgeJmFxu2wGYUlbqxmSE0nRuNpf7
j5akKSkBMDv+VDWu0lVEmHL0IYH7x0sE4LxHyiurydUo0KdGDMPThTWInpyDAIuS
xcpE5aw36sBDiZp/tldqf3+X1zp/YscV4w132ZDKu3/96PyOMtkYOe0srno7BNuj
DTkEJj1nK3Yjn/Tk6P7cURAg1aAHWcXv0hro2o/xoCvos6Qs5sBGodFefF/NQUeU
vOST2pQhM002bL8J49jnGLSdb+JkwRMVlLWDVKMkEB2WzjMJ1nFMM7F+ro36bfWj
zFt7BmmvfrUz5R5d8dPhC3OKXPLjcmYHpqFuBuHGYTW7KHWzIpRQb+Rg9xRsHaML
3i+u60Fczu0BLpymBKPadMaZRH04qUoOOfjKl7BR6Gc3ww73QMQeRRq5eqYqBxqZ
0nMPkSzG4KgS8Lv+d3dH9KpJAW2U+5ob/sAD2Y0KsvkEGiNdmgS+6WSN9sBAs9iu
KOEiIEk/nmzWwwgqVVX4YeBXkNUlBf7RABMOl+tSIinFeNRVWK4=
=I4oF
-END PGP SIGNATURE End Message ---
Bug#694321: marked as done ([gsfonts] Fonts include copyrighted adobe fragment all right reserved)
Your message dated Fri, 02 Sep 2022 17:43:12 +0200
with message-id <5cdffb1295988623a01ff6f885c213fdf9d8e5bf.ca...@debian.org>
and subject line Re: [gsfonts] Fonts include copyrighted adobe fragment all
right reserved
has caused the Debian Bug report #694320,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
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.)
--
694320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsfonts
Version: 1:8.11+urwcyr1.0.7~pre44-4.2
Severity: serious
control: block -1 by 694308
This package include copyrighted font hinting from adobe.
For instance
t1disasm /usr/share/fonts/type1/gsfonts/n019024l.pfb | grep -i -A 10 adobe
%!PS-AdobeFont-1.0: NimbusSanL-BoldItal 1.06
%%Title: NimbusSanL-BoldItal
%Version: 1.06
%%CreationDate: Thu Aug 2 14:36:47 2007
%%Creator: frob
%Copyright: Copyright (URW)++,Copyright 1999 by (URW)++ Design &
%Copyright: Development; Cyrillic glyphs added by Valek Filippov (C)
%Copyright: 2001-2005
% Generated by FontForge 20070723 (http://fontforge.sf.net/)
%%EndComments
--
% Copyright (c) 1987-1990 Adobe Systems Incorporated.
% All Rights Reserved.
% This code to be used for Flex and hint replacement.
% Version 1.1
[ {}
{}
{}
{systemdict /internaldict known not
{pop 3}
{1183615869 systemdict /internaldict get exec
dup /startlock known
Thanks
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Version: 2:20200910-2
The gsfonts package has been replaced by fonts-urw-base35.
This package does not include any copyrighted Adobe fragments anymore.
- Fabian
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmMSJJAACgkQy+qOlwzN
Wd9VtxAAjgsI4CYYvJX/R60JfBBdm8OegVMlFU6DLsiINYwzdTrJt9Eci5VlURVk
d4bgyL0KFQwdXhY8zm5cBcpk9pKjbjw/CUWSakRWLWl5NNnPGrqrhBlOEqKagQeR
8f38ZkIs5ScIgED7cotUg7X4PARqx1Dhl63JFgeJmFxu2wGYUlbqxmSE0nRuNpf7
j5akKSkBMDv+VDWu0lVEmHL0IYH7x0sE4LxHyiurydUo0KdGDMPThTWInpyDAIuS
xcpE5aw36sBDiZp/tldqf3+X1zp/YscV4w132ZDKu3/96PyOMtkYOe0srno7BNuj
DTkEJj1nK3Yjn/Tk6P7cURAg1aAHWcXv0hro2o/xoCvos6Qs5sBGodFefF/NQUeU
vOST2pQhM002bL8J49jnGLSdb+JkwRMVlLWDVKMkEB2WzjMJ1nFMM7F+ro36bfWj
zFt7BmmvfrUz5R5d8dPhC3OKXPLjcmYHpqFuBuHGYTW7KHWzIpRQb+Rg9xRsHaML
3i+u60Fczu0BLpymBKPadMaZRH04qUoOOfjKl7BR6Gc3ww73QMQeRRq5eqYqBxqZ
0nMPkSzG4KgS8Lv+d3dH9KpJAW2U+5ob/sAD2Y0KsvkEGiNdmgS+6WSN9sBAs9iu
KOEiIEk/nmzWwwgqVVX4YeBXkNUlBf7RABMOl+tSIinFeNRVWK4=
=I4oF
-END PGP SIGNATURE End Message ---
Bug#694320: marked as done ([gsfonts] Fonts include copyrighted adobe fragment all right reserved)
Your message dated Fri, 02 Sep 2022 17:43:12 +0200
with message-id <5cdffb1295988623a01ff6f885c213fdf9d8e5bf.ca...@debian.org>
and subject line Re: [gsfonts] Fonts include copyrighted adobe fragment all
right reserved
has caused the Debian Bug report #694320,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
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.)
--
694320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsfonts
Version: 1:8.11+urwcyr1.0.7~pre44-4.2
Severity: serious
control: block -1 by 694308
This package include copyrighted font hinting from adobe.
For instance
t1disasm /usr/share/fonts/type1/gsfonts/n019024l.pfb | grep -i -A 10 adobe
%!PS-AdobeFont-1.0: NimbusSanL-BoldItal 1.06
%%Title: NimbusSanL-BoldItal
%Version: 1.06
%%CreationDate: Thu Aug 2 14:36:47 2007
%%Creator: frob
%Copyright: Copyright (URW)++,Copyright 1999 by (URW)++ Design &
%Copyright: Development; Cyrillic glyphs added by Valek Filippov (C)
%Copyright: 2001-2005
% Generated by FontForge 20070723 (http://fontforge.sf.net/)
%%EndComments
--
% Copyright (c) 1987-1990 Adobe Systems Incorporated.
% All Rights Reserved.
% This code to be used for Flex and hint replacement.
% Version 1.1
[ {}
{}
{}
{systemdict /internaldict known not
{pop 3}
{1183615869 systemdict /internaldict get exec
dup /startlock known
Thanks
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Version: 2:20200910-2
The gsfonts package has been replaced by fonts-urw-base35.
This package does not include any copyrighted Adobe fragments anymore.
- Fabian
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmMSJJAACgkQy+qOlwzN
Wd9VtxAAjgsI4CYYvJX/R60JfBBdm8OegVMlFU6DLsiINYwzdTrJt9Eci5VlURVk
d4bgyL0KFQwdXhY8zm5cBcpk9pKjbjw/CUWSakRWLWl5NNnPGrqrhBlOEqKagQeR
8f38ZkIs5ScIgED7cotUg7X4PARqx1Dhl63JFgeJmFxu2wGYUlbqxmSE0nRuNpf7
j5akKSkBMDv+VDWu0lVEmHL0IYH7x0sE4LxHyiurydUo0KdGDMPThTWInpyDAIuS
xcpE5aw36sBDiZp/tldqf3+X1zp/YscV4w132ZDKu3/96PyOMtkYOe0srno7BNuj
DTkEJj1nK3Yjn/Tk6P7cURAg1aAHWcXv0hro2o/xoCvos6Qs5sBGodFefF/NQUeU
vOST2pQhM002bL8J49jnGLSdb+JkwRMVlLWDVKMkEB2WzjMJ1nFMM7F+ro36bfWj
zFt7BmmvfrUz5R5d8dPhC3OKXPLjcmYHpqFuBuHGYTW7KHWzIpRQb+Rg9xRsHaML
3i+u60Fczu0BLpymBKPadMaZRH04qUoOOfjKl7BR6Gc3ww73QMQeRRq5eqYqBxqZ
0nMPkSzG4KgS8Lv+d3dH9KpJAW2U+5ob/sAD2Y0KsvkEGiNdmgS+6WSN9sBAs9iu
KOEiIEk/nmzWwwgqVVX4YeBXkNUlBf7RABMOl+tSIinFeNRVWK4=
=I4oF
-END PGP SIGNATURE End Message ---
Bug#1017941: greenbone-security-assistant downloads source from the network
On Fri, Sep 02, 2022 at 09:12:38AM +0200, Sophie Brun wrote: > Hello Steve, > We had already had a bug report about this issue: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=98 > To short: we moved the package to contrib because we had to download > modules during the build. > We also had a discussion on debian-devel: > https://lists.debian.org/debian-devel/2020/12/threads.html#00215 > I know it is really not an ideal solution. > If you think Debian can't keep this package in contrib, please let us know. It's ultimately a decision of the ftp team if the package can't be in contrib. However, there is an expectation that the Debian source package contains the complete source of what you're distributing in the archive, including for contrib packages. Raphael's original message in that thread suggests that "it's just impossible to write a copyright file to document the source package". But copyright files exist to document the copyright of the *binary* packages you're distributing, so if no work was done here to generate correct copyright files, that is also a bug. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1018944: marked as done (knot-dnssecutils: missing Breaks+Replaces: knot (<< 3.2), knot-dnsutils (<< 3.2))
Your message dated Fri, 02 Sep 2022 14:38:25 + with message-id and subject line Bug#1018944: fixed in knot 3.2.0-3 has caused the Debian Bug report #1018944, regarding knot-dnssecutils: missing Breaks+Replaces: knot (<< 3.2), knot-dnsutils (<< 3.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.) -- 1018944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: knot-dnssecutils Version: 3.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' 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 This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../knot-dnssecutils_3.2.0-2_amd64.deb ... Unpacking knot-dnssecutils (3.2.0-2) ... dpkg: error processing archive /var/cache/apt/archives/knot-dnssecutils_3.2.0-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/kzonecheck', which is also in package knot-dnsutils 3.0.5-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/knot-dnssecutils_3.2.0-2_amd64.deb Preparing to unpack .../knot-dnssecutils_3.2.0-2_amd64.deb ... Unpacking knot-dnssecutils (3.2.0-2) ... dpkg: error processing archive /var/cache/apt/archives/knot-dnssecutils_3.2.0-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/knsec3hash', which is also in package knot 3.0.5-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/knot-dnssecutils_3.2.0-2_amd64.deb cheers, Andreas knot=3.0.5-1_knot-dnssecutils=3.2.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: knot Source-Version: 3.2.0-3 Done: Jakub Ružička We believe that the bug you reported is fixed in the latest version of knot, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jakub Ružička (supplier of updated knot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Sep 2022 13:31:57 + Source: knot Architecture: source Version: 3.2.0-3 Distribution: unstable Urgency: medium Maintainer: knot packagers Changed-By: Jakub Ružička Closes: 1018944 Changes: knot (3.2.0-3) unstable; urgency=medium . * Add Breaks+Replaces for knot-dnssecutils (Closes: #1018944) Checksums-Sha1: f2357ce68410562370f1b73b069b1a12fc20dac8 3689 knot_3.2.0-3.dsc 18d071ffe0c517a9a6c4c4bfd379149b8dba5617 29444 knot_3.2.0-3.debian.tar.xz eba3b142ce4facd75af9d092d44413830025e9db 6280 knot_3.2.0-3_source.buildinfo Checksums-Sha256: ef5f6626566b1e23b1b0bd6c05d51bd0d46670fbf623cf99059d3f823b0c966d 3689 knot_3.2.0-3.dsc 8a690ffe9c0abd841696bd6d71100f0dbe2f6c91ed432d5b8d84ce797b57b1f3 29444 knot_3.2.0-3.debian.tar.xz 572fb62cfc00656b5b17212e6d7cb9807a142958811d9da641ad4d620711b740 6280 knot_3.2.0-3_source.buildinfo Files: 41f0a346726bd814e315a8d466d87442 3689 net optional knot_3.2.0-3.dsc 438bda1574971c1eacc8f1da35196afa 29444 net optional knot_3.2.0-3.debian.tar.xz 8d670b7cbc6192b76096ec963211909c 6280 net optional knot_3.2.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEI+vPfo/EdVZ4cQDfpCVAcuNzBCwFAmMSCEkACgkQpCVAcuNz BCya0w//WtKX4OFy5SSSaqwd366PTQJx5ocrJQ9iyuE4fXRh/2cmabLrMVc48pEL Mnnlb/j8r4dVBNVAQPDIzW8XaoThh4t+DLMqGLgWidIjY4Piyy2dSv9Zw74zABnm uhwfgFWQh/sXxGyIFfLIpm5C7loLi8RMtDXQ7G76lvVPa/4j63fYcAKfVq4Pbz1W qKewWl8ukpw6XxwhaGsjsZPYcUfIZFryh1IY2JFTrTp2HFG923TdDtey5moeFUOc 6Gt5jC/GMbsV+kGrTnjV+JLicsLOJE6VzD01UHCf/MubJ8C6yl3tHpY6TFnslMIr
Bug#1016613: marked as done (unhide-gui: missing Breaks+Replaces: unhide (<< 20210124-3))
Your message dated Fri, 02 Sep 2022 13:38:42 + with message-id and subject line Bug#1016613: fixed in unhide 20220611-1 has caused the Debian Bug report #1016613, regarding unhide-gui: missing Breaks+Replaces: unhide (<< 20210124-3) 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.) -- 1016613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unhide-gui Version: 20210124-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' 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 .../unhide-gui_20210124-3_amd64.deb ... Unpacking unhide-gui (20210124-3) ... dpkg: error processing archive /var/cache/apt/archives/unhide-gui_20210124-3_amd64.deb (--unpack): trying to overwrite '/usr/sbin/unhide-gui', which is also in package unhide 20210124-2 Errors were encountered while processing: /var/cache/apt/archives/unhide-gui_20210124-3_amd64.deb cheers, Andreas unhide=20210124-2_unhide-gui=20210124-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: unhide Source-Version: 20220611-1 Done: Fukui Daichi We believe that the bug you reported is fixed in the latest version of unhide, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fukui Daichi (supplier of updated unhide 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, 01 Sep 2022 13:21:51 + Source: unhide Architecture: source Version: 20220611-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Fukui Daichi Closes: 1016613 Changes: unhide (20220611-1) unstable; urgency=medium . * Team upload. . [ Fukui Daichi ] * New upstream release * Bumped Std-Ver to 4.6.1 * Update d/unhide.triggers to use noawait variant * Update d/copyright * Update d/patches . [ Samuel Henrique ] * d/control: Add Replaces+Breaks to unhide-gui (closes: #1016613) Checksums-Sha1: c8a7a27a3fd29a52e7f95cbd6c626bc9d68d7faf 1941 unhide_20220611-1.dsc 8a3baa498f9b3f29943ca01212dd08fc9322a4fd 80219 unhide_20220611.orig.tar.gz ef0a0d80ebf6a6af3ad45076854c1cf7004637e6 8456 unhide_20220611-1.debian.tar.xz bdf67e764f33c94875fbd9d06588018e072d0594 6869 unhide_20220611-1_amd64.buildinfo Checksums-Sha256: 01d6c7b57270cd53842751a9d95545f914c6e789f7ffa134579c4734cf6c6384 1941 unhide_20220611-1.dsc db0c29b6519982df07a9024d37b1e4618d40eaf13c2c01737ec79dcfba108eb6 80219 unhide_20220611.orig.tar.gz 8f27b434e77490fd747c1fa01c7f7d093d4c92843db6a1f06412b433fa50c9c9 8456 unhide_20220611-1.debian.tar.xz 7eedc7da35182ba946b0392b9099ef162d7f10e82411d7b0a5afbc7eba5aaeac 6869 unhide_20220611-1_amd64.buildinfo Files: fd3ba8d988588d0710e1d1a83c108726 1941 admin optional unhide_20220611-1.dsc cb0fc465ef26e907ba2166551dc27369 80219 admin optional unhide_20220611.orig.tar.gz c070c1ba884f481b54cc05cbdb0caafe 8456 admin optional unhide_20220611-1.debian.tar.xz 892efb6e3c4114d0467f8cae5e503a9b 6869 admin optional unhide_20220611-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAmMSAi0ACgkQu6n6rcz7 RweCPxAAhy87HHRX9PITb8cDpcj/p/B68ArP55AttRpIm8EhWlP0NuBf+t/4NdWv G8mPx5Zolc8dO3nm8MRM3GpIM9hzyQGWwpIZvxdIhghm+5tMiphewB14NZ6ItuI2 tBGvM+07JhPlBm4oC8CGnfbb+0otW35WzeR4m2l0FVLJng5dXnwoVKrW7Ex8CgHM vuTk+lZIkd9evwC0K+nb/cFijlQ/4Z/RJh3rdnExlFMX/+SEerEAWDmIZUUe4FqH Zt/TDsqWlmGPqJRAx+yZMSSATT6wWYI5zF7RnZPyBvsQruVbxymo7RqVMQRaxGXk Uo4Whmgb/EdSvneaGM9/rPmS7zjEs/KrYnlKCPFp3HRprJIKuvh7jwxqQfGaEqpu riSyTWbGNBSWOxy7XRRRIA1Byx94EemFEymDaXr7KpeTulUJiGTleddRlxspvUu6
Bug#919697: arcanist: file conflict with arc
On Fri, Sep 2, 2022 at 15:01:01 +0200, Sylvestre Ledru wrote: > Le 02/09/2022 à 13:18, Adrian Bunk a écrit : > > On Fri, Sep 02, 2022 at 12:12:06PM +0200, Christoph Biedl wrote: > > > Sylvestre Ledru wrote... > > > > > > > I don't think renaming is the right approach against an MS-DOS > > > > software (and I still think that Debian's policy is too binary for > > > > this). > > > > > > As there is a very small chance users would want to install *both* > > > packages, can't we just resolve this with a Breaks: on both sides, or > > > anything else that prevents co-installation from happening? > > > ... > > > > "Two different packages must not install programs with different > > functionality but with the same filenames."[1] > > > Yeah, but with that many packages in the archive, it makes less and less > sense ... > I would say it makes more and more sense, on the contrary, for the distribution to do this job to avoid arbitrary conflicts. Cheers, Julien
Bug#1016613: marked as pending in unhide
Control: tag -1 pending Hello, Bug #1016613 in unhide reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-security-team/unhide/-/commit/b2cff70b55a4ebfd9816b653736594306cd1e933 d/control: Add Replaces+Breaks to unhide-gui (closes: #1016613) (this message was generated automatically) -- Greetings https://bugs.debian.org/1016613
Processed: Bug#1016613 marked as pending in unhide
Processing control commands: > tag -1 pending Bug #1016613 [unhide-gui] unhide-gui: missing Breaks+Replaces: unhide (<< 20210124-3) Added tag(s) pending. -- 1016613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014817: marked as done (mercurial: broken fsmonitor extension in 6.2)
Your message dated Fri, 02 Sep 2022 13:13:15 + with message-id and subject line Bug#1014817: fixed in mercurial 6.2.2-1 has caused the Debian Bug report #1014817, regarding mercurial: broken fsmonitor extension in 6.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.) -- 1014817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mercurial Version: 6.2-1 Severity: serious Tags: upstream Upstream commit be9bf75a837c looks like it broke the fsmonitor extension: > File "/usr/lib/python3/dist-packages/hgext/fsmonitor/__init__.py", line > 338, in > if e._v1_state() != b"n" or e._v1_mtime() == -1 > AttributeError: 'dirstate_tuple' object has no attribute '_v1_state' Cheers, Julien --- End Message --- --- Begin Message --- Source: mercurial Source-Version: 6.2.2-1 Done: Julien Cristau We believe that the bug you reported is fixed in the latest version of mercurial, 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 Cristau (supplier of updated mercurial package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Sep 2022 14:08:12 +0200 Source: mercurial Architecture: source Version: 6.2.2-1 Distribution: sid Urgency: medium Maintainer: Debian Python Team Changed-By: Julien Cristau Closes: 1014817 Changes: mercurial (6.2.2-1) sid; urgency=medium . * New upstream bugfix release - fixed fsmonitor extension (closes: #1014817) Checksums-Sha1: c9ad1d3e8be922829ac6e1d17f157f333ab48fe6 2799 mercurial_6.2.2-1.dsc 429ccbf8ce5ccb17f76f888333ced25296213933 8057375 mercurial_6.2.2.orig.tar.gz 11f67e17e333da27247204da0707338abf8bbd89 659 mercurial_6.2.2.orig.tar.gz.asc ef513fcd24c8b670a1d60619b9f9a104c26e92ef 70016 mercurial_6.2.2-1.debian.tar.xz Checksums-Sha256: fc70ce1fadf17ffa1a811acee98a5bb4ed181425ff7449eb3d0a49b96709ba3a 2799 mercurial_6.2.2-1.dsc 9efa9da5f497a8750ac9c48fa431c4ab72209f1360180c5d4920d1311b0420df 8057375 mercurial_6.2.2.orig.tar.gz 662079f5a5d4a44b8981b5b5353f5bf030a35fca4e8a0bef100fb83fc19ec78f 659 mercurial_6.2.2.orig.tar.gz.asc 33a32d5d2809a7b5ae8b7a1447d7497d7b04046155cb76b60ea5355c099b1074 70016 mercurial_6.2.2-1.debian.tar.xz Files: e13a2a9c5697d6d7be9ef9edf457b106 2799 vcs optional mercurial_6.2.2-1.dsc 217aae3699c53894f491358af74bcdd7 8057375 vcs optional mercurial_6.2.2.orig.tar.gz 1236db84d3345a396a9dda9ad010fd51 659 vcs optional mercurial_6.2.2.orig.tar.gz.asc 28f55008cfbd12cf680bf56e505eb48f 70016 vcs optional mercurial_6.2.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAmMR868UHGpjcmlzdGF1 QGRlYmlhbi5vcmcACgkQnbAjVVb4z61E5hAAk96NYYAemz0IaLMSUVV520hg1CMg 81glUMvgf/+YeszR4Tvp8c+FnJDZD6I55Ecpz60/wPuQIPTw33bVacCGzyKC1BO/ hvWXcEJZX3cfzUp0OfXUbeKbaXmKupVc0clrvyXg4BstjONWNUGHhNPugLtVrnmr pUjsmiOqGtQ3hcmUZxup+XN6joA9wuqV+SYhxz3fX6jW9gD070ZLtPXdpI0EBjeh QBKJmuE6YibyDq1tYF8PnXM00dZ8Tyk04DMquFHklrKjpfsLczbCcvN+BvSfLP5K 9wulzNBmwcAnUr6vgZdErCYVdr1u0Wd0z4SkW5qtuGGiUPTXVUSR2rH6il/0uWSG spFomIfFc2Ev4L5mRiH+Yp53FY4EtaI9rsOSY4dQ1lxjVrH3jnMszCMtoA9FGr3R 9hvFUeOe5Rp00OqO5C30AinzWAuShrLZp2xLzIfRHk3wk9MdMt5X3urs227znI9W 5GdJtqTr26d0oobGZT5y64SM9mir27iP7z04xTzl/vgIVCb2VCgQzboTxFWH0TZX QdG14BT8YSmQFw7XVXV/DgWd++7emsRCblwwBFfV4hCn5A+lPJxbPkeG1gwk1DLo Rc8zPXwSQmzb1sNDFZcwy6jj5IcWh8zoKCwEUChz3jGsHdm2wQthkWapQ0dA9Q3b WsuFilXlBMr5jAA= =n0lM -END PGP SIGNATURE End Message ---
Processed: Re: zookeeper: Can attempt to access the network during build
Processing control commands: > tags -1 confirmed Bug #1018942 [zookeeper] zookeeper: Can attempt to access the network during build Added tag(s) confirmed. -- 1018942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018942: zookeeper: Can attempt to access the network during build
Control: tags -1 confirmed Hello Simon, On Fri, 02 Sep 2022 11:50:55 +0200 Simon Chopin wrote: > Package: zookeeper > 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 > X-Debbugs-Cc: scho...@ubuntu.com > > We observed a FTBFS on amd64 in Ubuntu due to a DNS resolution error on > google.com, see https://bugs.launchpad.net/ubuntu/+source/zookeeper/+bug/1988541 > for more details. > > I don't exactly know why this hasn't happened during the Debian build, > but in any case, you'll find attached a debdiff to address the issue. > Thanks for the bug report! A few days ago we had similar concerns with the igv package, as pointed out by someone else wo caught a FTBFS in Ubuntu. I guess the build, as we do it within Debian tools, fails to see some calls to the network while Ubuntu catches them all. I will provide a fix soon. > Cheers, > Simon > Best, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Bug#919697: arcanist: file conflict with arc
Le 02/09/2022 à 13:18, Adrian Bunk a écrit : On Fri, Sep 02, 2022 at 12:12:06PM +0200, Christoph Biedl wrote: Sylvestre Ledru wrote... I don't think renaming is the right approach against an MS-DOS software (and I still think that Debian's policy is too binary for this). As there is a very small chance users would want to install *both* packages, can't we just resolve this with a Breaks: on both sides, or anything else that prevents co-installation from happening? ... "Two different packages must not install programs with different functionality but with the same filenames."[1] Yeah, but with that many packages in the archive, it makes less and less sense ... Sylvestre
Bug#1012741: closing 1012741
close 1012741 5.19.6+1 thanks
Processed: closing 1012741
Processing commands for cont...@bugs.debian.org: > close 1012741 5.19.6+1 Bug #1012741 [src:linux-signed-i386] modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service Bug #1012816 [src:linux-signed-i386] reportbug: Failed to insert module 'firewire_sbp2': Key was rejected by service The source 'linux-signed-i386' and version '5.19.6+1' do not appear to match any binary packages Marked as fixed in versions linux-signed-i386/5.19.6+1. Marked as fixed in versions linux-signed-i386/5.19.6+1. Bug #1012741 [src:linux-signed-i386] modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service Bug #1012816 [src:linux-signed-i386] reportbug: Failed to insert module 'firewire_sbp2': Key was rejected by service Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1012741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012741 1012816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016315: marked as done (twisted: FTBFS: could not import module twisted.python._pydoctor)
Your message dated Fri, 02 Sep 2022 12:39:27 + with message-id and subject line Bug#1016315: fixed in twisted 22.4.0-3 has caused the Debian Bug report #1016315, regarding twisted: FTBFS: could not import module twisted.python._pydoctor 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.) -- 1016315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: twisted Version: 22.4.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PYTHONPATH=src python3 -m sphinx -b html -N docs/ > /<>/debian/twisted-doc/usr/share/doc/twisted-doc/html > Running Sphinx v4.5.0 > making output directory... done > Building 'main' pydoctor API docs as: > --make-html > --quiet > --quiet > --html-viewsource-base=https://github.com/twisted/twisted/tree/trunk > --project-name=Twisted > --project-url=https://twistedmatrix.com/ > --system-class=twisted.python._pydoctor.TwistedSystem > --docformat=epytext > --project-base-dir=/<>/src > --html-output=/<>/debian/twisted-doc/usr/share/doc/twisted-doc/html/api > /<>/src/twisted > could not import module twisted.python._pydoctor > make[1]: *** [debian/rules:30: override_dh_sphinxdoc] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/07/28/twisted_22.4.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: twisted Source-Version: 22.4.0-3 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of twisted, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated twisted package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Sep 2022 14:10:50 +0200 Source: twisted Architecture: source Version: 22.4.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1016315 Changes: twisted (22.4.0-3) unstable; urgency=medium . * Team upload. * Patch: Fix FTBFS with pydoctor 22.7 (Closes: #1016315) * Rebase pydoctor-22.7.patch underneath other debian-specific patches touching the same code. Checksums-Sha1: 5c079a9d644e3e19cf962602c4f152113cf89da7 1785 twisted_22.4.0-3.dsc 7abfe69c37868069744aba6b20899c6fc66ddb4a 40280 twisted_22.4.0-3.debian.tar.xz 4b2aeb93f2658dd575522f3d50c39817168d332c 6462 twisted_22.4.0-3_source.buildinfo Checksums-Sha256: bb095b02002b75be50bb1ec3acdb836840e70ec8fdebda1c924d876513963a1a 1785 twisted_22.4.0-3.dsc 861b447ae6ac40fb28a171334b06d9308a4f0937f3b612b9046ceca63e8192cc 40280 twisted_22.4.0-3.debian.tar.xz 79d10a394290bf959f445b1aa6b23145a25e0cb4554ed51352f639c384552caf 6462 twisted_22.4.0-3_source.buildinfo Files: 89c6bd64fcdb013e8b3951d7479c0d70 1785 python optional twisted_22.4.0-3.dsc 1f40f2bdccede30a3d36ae836178f6f9 40280 python optional twisted_22.4.0-3.debian.tar.xz c9a7b0791022cc15b024cb5cfca5168b 6462 python optional twisted_22.4.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYxHy9gAKCRBHew2wJjpU 2K82AP4s3AWnFGci2nk/wVI/9PXhW9UEEsn9sT9JAXxEAPdgnAEAt1lNtXd2t0Un uwOBdfkJKAE7Z8LZ46QyrbSs5Cxmfw8=
Bug#1018043: zutils: statically linked
On Fri, Sep 02, 2022 at 01:50:28PM +0200, Daniel Baumann wrote: > tag 1018043 pending > thanks ♥ > On 8/24/22 17:40, Adam Borowski wrote: > > This package has a massive size > > massive is relative.. it's 490KB. 4591 kB here... > there was a reason (see #608484), but I guess with merged-usr this isn't > a problem anymore anyway. merged-usr is unrelated here: we have dropped support for booting the system without /usr /etc /var mounted several years ago; merged usr is about moving things around replacing them with symlinks. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ʀᴜꜱꜱɪᴀɴᴇꜱ ᴇᴜɴᴛ ᴅᴏᴍᴜꜱ ⢿⡄⠘⠷⠚⠋⠀ ⠈⠳⣄
Bug#1016315: marked as pending in twisted
Control: tag -1 pending Hello, Bug #1016315 in twisted reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/twisted/-/commit/d2df657007d2b81889c97b4b0acec6e8cac097d8 Patch: Fix FTBFS with pydoctor 22.7 (Closes: #1016315) (this message was generated automatically) -- Greetings https://bugs.debian.org/1016315
Processed: Bug#1016315 marked as pending in twisted
Processing control commands: > tag -1 pending Bug #1016315 [src:twisted] twisted: FTBFS: could not import module twisted.python._pydoctor Added tag(s) pending. -- 1016315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018043: zutils: statically linked
tag 1018043 pending thanks On 8/24/22 17:40, Adam Borowski wrote: > This package has a massive size massive is relative.. it's 490KB. > as it's pointlessly statically built. there was a reason (see #608484), but I guess with merged-usr this isn't a problem anymore anyway. Regards, Daniel
Bug#1016935: marked as done (assaultcube: FTBFS with GCC 12: dwz fails)
Your message dated Fri, 02 Sep 2022 11:52:00 + with message-id and subject line Bug#1016935: fixed in assaultcube 1.2.0.2.1-4 has caused the Debian Bug report #1016935, regarding assaultcube: FTBFS with GCC 12: dwz fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: assaultcube Version: 1.2.0.2.1-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) Hi, assaultcube recently started to FTBFS, this could be related to GCC 12 becoming the default compiler. dh_dwz -O--sourcedirectory=source/src dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_client: Unknown debugging section .debug_addr dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_server: Unknown debugging section .debug_addr dwz: Too few files for multifile optimization dh_dwz: error: dwz -mdebian/assaultcube/usr/lib/debug/.dwz/x86_64-linux-gnu/assaultcube.debug -M/usr/lib/debug/.dwz/x86_64-linux-gnu/assaultcube.debug -- debian/assaultcube/usr/lib/games/assaultcube/ac_client debian/assaultcube/usr/lib/games/assaultcube/ac_server returned exit code 1 dh_dwz: error: Aborting due to earlier error make: *** [debian/rules:9: binary] Error 25 Andreas assaultcube_1.2.0.2.1-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: assaultcube Source-Version: 1.2.0.2.1-4 Done: Tobias Frost We believe that the bug you reported is fixed in the latest version of assaultcube, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated assaultcube 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: Fri, 02 Sep 2022 13:20:34 +0200 Source: assaultcube Architecture: source Version: 1.2.0.2.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Tobias Frost Closes: 1016935 Changes: assaultcube (1.2.0.2.1-4) unstable; urgency=medium . * Team upload. * Revert changes in git repository from 1.2.0.2.1-3, which was never released but tagged in the git repo: - Inappropriate change of upstream references to coriango's forks. - break/conflict changed version of break to a later version which is likely wrong note: the below changelogs for -3 are left as it, but they are not documenting what actually has been changed in -3. * Do not compile with clang, as this fails with dh_dwz (Closes: #1016935) * Remove debian/upstream/signing-key.asc. This is not upstream's, but coriango's one. * Fix overrides for renamed lintian tags. * Update d/copyright fixing some lintian warnings with it. * Bump S-V to 4.6.1 (no changes). * Specify Rules-Requires-Root. * Bump compat level to 13 (no changes). * Fix unknown-fields errors in upstream/metadata. * New patch, so that CXXFLAGS are kept during build and hardening not defeated. Checksums-Sha1: 7dc49c0f2c5e7f00660b9cd01da7ddf04de1865a 2330 assaultcube_1.2.0.2.1-4.dsc 015b6c48fd09686fa7b9ffbd4c8d152ce9170b3a 7928 assaultcube_1.2.0.2.1-4.debian.tar.xz 3efae06eb795809d837b73633d93c74f24d43950 11832 assaultcube_1.2.0.2.1-4_amd64.buildinfo Checksums-Sha256: 3accf2b2941ac1cdd2491336439c74ea9e6b6f9d50dac62ee26ab057dd0369a6 2330 assaultcube_1.2.0.2.1-4.dsc 6c60838851bb0eac6fa339d11bb65c34ff549e1b19ac5c58cb430eede5a62399 7928 assaultcube_1.2.0.2.1-4.debian.tar.xz 83bc5845a622cf67fd47a203daaae6399a68cc91da7d9ff82152b1a186017843 11832 assaultcube_1.2.0.2.1-4_amd64.buildinfo Files: b53fcf6d86ea8b6a2c0ef843c2d27637 2330 contrib/games optional assaultcube_1.2.0.2.1-4.dsc 1a54a0da392bf6d1eed70c46f9d37001 7928 contrib/games optional assaultcube_1.2.0.2.1-4.debian.tar.xz 6e8fdd0dc755be6fbc1321b9968a27ea 11832 contrib/games optional assaultcube_1.2.0.2.1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmMR53gACgkQkWT6HRe9
Processed: Re: Bug#1018043: zutils: statically linked
Processing commands for cont...@bugs.debian.org: > tag 1018043 pending Bug #1018043 [zutils] zutils: statically linked Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1018043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#919697: arcanist: file conflict with arc
Processing control commands: > reassign -1 arcanist Bug #919697 [arc,arcanist] arcanist: file conflict with arc Bug #930722 [arc,arcanist] arc, arcanist: Both ship arc binary Bug reassigned from package 'arc,arcanist' to 'arcanist'. Bug reassigned from package 'arc,arcanist' to 'arcanist'. Ignoring request to alter found versions of bug #919697 to the same values previously set Ignoring request to alter found versions of bug #930722 to the same values previously set Ignoring request to alter fixed versions of bug #919697 to the same values previously set Ignoring request to alter fixed versions of bug #930722 to the same values previously set -- 919697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919697 930722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919697: arcanist: file conflict with arc
Control: reassign -1 arcanist Hi! On Fri, 2022-09-02 at 07:46:43 +0200, Sylvestre Ledru wrote: > Le 02/09/2022 à 01:10, Guillem Jover a écrit : > > So we have reached the point at which arc is getting autoremoved from > > testing as the RC is still filed against it too. :( > > > > Could some arcanist maintainer please check this, and ideally agree to > > reassign this bug to arcanist? If necessary I'm willing to prepare a > > patch for arcanist to stop installing as bin/arc, as described above, > > if this would expedite things. > However, as: > * phabricator is dying > * Richard, Christoph and myself didn't show a strong interest to keep > it alive (it is currently broken in unstable). > > Please do what you want. ;) Thanks! Much appreciated, I've reassigned it now with this mail! On Fri, 2022-09-02 at 12:12:06 +0200, Christoph Biedl wrote: > Sylvestre Ledru wrote... > > I don't think renaming is the right approach against an MS-DOS > > software (and I still think that Debian's policy is too binary for > > this). > > As there is a very small chance users would want to install *both* > packages, can't we just resolve this with a Breaks: on both sides, or > anything else that prevents co-installation from happening? See Adrian's reply. > Else I think for the various reasons it's indeed the arcanist package > that should move. Although I have concerns here since (arcanist's) arc > program is a command line tool and therefore users will have created > scripts around it. > About the policy - I think the idea behind it is right, and colliding > file names are a problem. Can you think of a better way to handle this? See my proposal on the previous mail, quoted here for convenience: > > On Wed, 2022-08-10 at 01:29:27 +0200, Guillem Jover wrote: > > > Could you please rename the archanist /usr/bin/arc into > > > /usr/bin/arcanist? Or if that's not feasible, then stop installing the > > > symlink in PATH, and document that users might want to add the /usr/share > > > /arcanist/bin/ into their own PATH? Or do both? I think this would make the program match the package name, and at the same time make it possible for willing users to simply modify their pathname or add a symlink say under ~/bin/arc pointing to the actual program. I can take a stab at this (as gratitude :), and propose a patch during the weekend or something, if you want. Thanks, Guillem
Bug#919697: arcanist: file conflict with arc
On Fri, Sep 02, 2022 at 12:12:06PM +0200, Christoph Biedl wrote: > Sylvestre Ledru wrote... > > > I don't think renaming is the right approach against an MS-DOS > > software (and I still think that Debian's policy is too binary for > > this). > > As there is a very small chance users would want to install *both* > packages, can't we just resolve this with a Breaks: on both sides, or > anything else that prevents co-installation from happening? >... "Two different packages must not install programs with different functionality but with the same filenames."[1] > Christoph cu Adrian [1] https://www.debian.org/doc/debian-policy/ch-files.html#binaries
Bug#1015048: marked as done (mako: FTBFS: AssertionError in test)
Your message dated Fri, 02 Sep 2022 10:35:35 + with message-id and subject line Bug#1015048: fixed in mako 1.2.2+ds1-1 has caused the Debian Bug report #1015048, regarding mako: FTBFS: AssertionError in test 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.) -- 1015048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mako Version: 1.1.3+ds1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > python3.9 setup.py build_scripts --executable=/usr/bin/python3 > running build_scripts > python3.9 setup.py install \ > --root /<>/debian/python3-mako --prefix=/usr > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > running build > running build_py > creating build > creating build/lib > creating build/lib/mako > copying mako/__init__.py -> build/lib/mako > copying mako/template.py -> build/lib/mako > copying mako/codegen.py -> build/lib/mako > copying mako/ast.py -> build/lib/mako > copying mako/util.py -> build/lib/mako > copying mako/lexer.py -> build/lib/mako > copying mako/pyparser.py -> build/lib/mako > copying mako/parsetree.py -> build/lib/mako > copying mako/exceptions.py -> build/lib/mako > copying mako/_ast_util.py -> build/lib/mako > copying mako/filters.py -> build/lib/mako > copying mako/cache.py -> build/lib/mako > copying mako/lookup.py -> build/lib/mako > copying mako/pygen.py -> build/lib/mako > copying mako/compat.py -> build/lib/mako > copying mako/cmd.py -> build/lib/mako > copying mako/runtime.py -> build/lib/mako > creating build/lib/mako/ext > copying mako/ext/__init__.py -> build/lib/mako/ext > copying mako/ext/preprocessors.py -> build/lib/mako/ext > copying mako/ext/extract.py -> build/lib/mako/ext > copying mako/ext/linguaplugin.py -> build/lib/mako/ext > copying mako/ext/babelplugin.py -> build/lib/mako/ext > copying mako/ext/pygmentplugin.py -> build/lib/mako/ext > copying mako/ext/turbogears.py -> build/lib/mako/ext > copying mako/ext/beaker_cache.py -> build/lib/mako/ext > copying mako/ext/autohandler.py -> build/lib/mako/ext > running install_lib > creating /<>/debian/python3-mako > creating /<>/debian/python3-mako/usr > creating /<>/debian/python3-mako/usr/lib > creating /<>/debian/python3-mako/usr/lib/python3.9 > creating /<>/debian/python3-mako/usr/lib/python3.9/site-packages > creating > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/__init__.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/template.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/codegen.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/ast.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/util.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/lexer.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/pyparser.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/parsetree.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/exceptions.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/_ast_util.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/filters.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/cache.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/lookup.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/pygen.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/compat.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/cmd.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > copying build/lib/mako/runtime.py -> > /<>/debian/python3-mako/usr/lib/python3.9/site-packages/mako > creating >
Bug#919697: arcanist: file conflict with arc
Sylvestre Ledru wrote... > I don't think renaming is the right approach against an MS-DOS > software (and I still think that Debian's policy is too binary for > this). As there is a very small chance users would want to install *both* packages, can't we just resolve this with a Breaks: on both sides, or anything else that prevents co-installation from happening? Else I think for the various reasons it's indeed the arcanist package that should move. Although I have concerns here since (arcanist's) arc program is a command line tool and therefore users will have created scripts around it. About the policy - I think the idea behind it is right, and colliding file names are a problem. Can you think of a better way to handle this? > However, as: > * phabricator is dying > * Richard, Christoph and myself didn't show a strong interest to keep it > alive (it is currently broken in unstable). "Interest" yes, strong interest ... there's always something more important barring me from working on it :( Anyway, I'm willing to through a few brain cycles on the problem tonight. Guillem, if you or anybody else have suggestions, I'm all ears. Christoph signature.asc Description: PGP signature
Bug#1018944: knot-dnssecutils: missing Breaks+Replaces: knot (<< 3.2), knot-dnsutils (<< 3.2)
Package: knot-dnssecutils Version: 3.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' 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 This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../knot-dnssecutils_3.2.0-2_amd64.deb ... Unpacking knot-dnssecutils (3.2.0-2) ... dpkg: error processing archive /var/cache/apt/archives/knot-dnssecutils_3.2.0-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/kzonecheck', which is also in package knot-dnsutils 3.0.5-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/knot-dnssecutils_3.2.0-2_amd64.deb Preparing to unpack .../knot-dnssecutils_3.2.0-2_amd64.deb ... Unpacking knot-dnssecutils (3.2.0-2) ... dpkg: error processing archive /var/cache/apt/archives/knot-dnssecutils_3.2.0-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/knsec3hash', which is also in package knot 3.0.5-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/knot-dnssecutils_3.2.0-2_amd64.deb cheers, Andreas knot=3.0.5-1_knot-dnssecutils=3.2.0-2.log.gz Description: application/gzip
Bug#1018791: marked as done (python3-astroalign: overly generic python module name: /usr/lib/python3/dist-packages/ez_setup.py)
Your message dated Fri, 02 Sep 2022 10:04:48 + with message-id and subject line Bug#1018791: fixed in astroalign 2.4.1-3 has caused the Debian Bug report #1018791, regarding python3-astroalign: overly generic python module name: /usr/lib/python3/dist-packages/ez_setup.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.) -- 1018791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-astroalign Version: 2.4.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package uses a very generic python module name that now clashes with other packages on upgrades: /usr/lib/python3/dist-packages/ez_setup.py Andreas --- End Message --- --- Begin Message --- Source: astroalign Source-Version: 2.4.1-3 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of astroalign, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated astroalign package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Sep 2022 11:24:10 +0200 Source: astroalign Architecture: source Version: 2.4.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Ole Streicher Closes: 1018791 Changes: astroalign (2.4.1-3) unstable; urgency=medium . * Don't install ez_setup.py (Closes: #1018791) Checksums-Sha1: 3c63ee65b5c88a5503580151e687c6a4f5ca5779 2254 astroalign_2.4.1-3.dsc 4f18852556e85bd1329b516623427c97a863ae0b 3284 astroalign_2.4.1-3.debian.tar.xz Checksums-Sha256: 0fc224b142fbce9a49de45b73d5ee60125d974603eb50b58d6eaf448038d57a4 2254 astroalign_2.4.1-3.dsc 72df79f4058e58a5f5accd8a349912475bba3693512c9db2a6776de1f078f044 3284 astroalign_2.4.1-3.debian.tar.xz Files: 23277dbeece40327dde2190bf2992519 2254 python optional astroalign_2.4.1-3.dsc 12f79e9bf3b940ab4652df0032248c2c 3284 python optional astroalign_2.4.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmMRzFIACgkQcRWv0HcQ 3Pf+7hAAkiPBzHqY96OHDN7ejGPu+xx7H/ilzRsomxoTYnmJRT2FoMigxW/wkGHT V/iEElMPw9rtfO/kl0/TM+uMdM3amlf6mv1zgohA6ws9IPkw27p5FSXQbbLBvXB4 DbY541oiCylKnxi2/3QJ53ibjLmOJh6Oj0TjqF8BlR9thsZyLO8h8NqhWs0e9eGC Yo7RvN02HEXZfOpQbEnGD+slhO2pWMJctkNuHMK5VLY4pXsVeawOLIW9TYZihwqq mF2qNK1UHGwudsEkmgt34sZoX2f0rpdntiwdCZjk7W7fZKUuOpn2nYWy/gpPXAZP uySXCxZeYbzNa4H5HV+vzzz945PA7imm/XKBhV1tUzh6s4xsMiTKZNcRhIhUBljd 3/iKoQSNjU8dwLnRjHTBzGo5aSmG1ieZAIbg31RdD6479cf3u1mnvghTMNVq0MF0 Q+fvTjDusiCZE3xybi9jRYxC8BkTYWnLDoT+17cJ5Yx+zq5cWqyfkhaQ2GT2wx3A 2dFgDT7erUElDASFTUlrrNt1DQZpBA3glQO9lbcRyCH/uTGhoW+qb96tl1h56SDe z0tdEc42+OCAjmDYiHnVbZJ/zjc753qWXTosuPTtfRC1qqkJCF/zpxblD9n2FNV6 9wMWRodup9lPPByAE5DFrOfdnV00ElZe/tELRh6+A8uYQd5dr1M= =/X7J -END PGP SIGNATURE End Message ---
Bug#947518: marked as done (casparcg-server: FTBFS: xf86vmode library not found - required for GLFW)
Your message dated Fri, 2 Sep 2022 11:35:55 +0200 with message-id and subject line [Debian FTP Masters] Accepted casparcg-server 2.3.3+dfsg-1 (source) into unstable has caused the Debian Bug report #947518, regarding casparcg-server: FTBFS: xf86vmode library not found - required for GLFW 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.) -- 947518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: casparcg-server Version: 2.2.0+dfsg-2 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, casparcg-server FTBFS in a current sid pbuilder environment: CMake Error at CMakeModules/FindGLFW.cmake:150 (message): xf86vmode library not found - required for GLFW Call Stack (most recent call first): CMakeModules/Bootstrap_Linux.cmake:44 (FIND_PACKAGE) CMakeLists.txt:18 (INCLUDE) Andreas casparcg-server_2.2.0+dfsg-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 2.3.3+dfsg-1 Solved in upstream in latest upload. -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 31 Aug 2022 16:35:00 +0100 Source: casparcg-server Architecture: source Version: 2.3.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Filip Hanes Changed-By: Filip Hanes Closes: 959106 959124 1015780 Changes: casparcg-server (2.3.3+dfsg-1) unstable; urgency=medium . [Filip Hanes] * New upstream version 2.3.3+dfsg. * New maintainer (Closes: #959124) * Added 0001-fix-missing-thread-includes-1396.patch * Added 0002-ffmpeg-5.0-1419.patch (Closes: #1015780) * Added 0003-fix-boost-1.73-ftbfs-1397.patch * Added 0004-fix-shader-frag.patch * Added 1001-cmake-ftbfs.patch * Added 1002-arm64-compatibility.patch * Added missing build dependency libboost-system-dev. * Added build dependency libsimde-dev for arm64 compatibility * Remove build dependency libgconf2-dev (Closes: #959106) * Update Maintainer, Uploaders, Standards-Version in d/control * Make ffmpeg5.0 patch compatible with ffmpeg 4.3 Checksums-Sha1: e8efb060bae5f66a7e202700480b34b4e08c05c1 2790 casparcg-server_2.3.3+dfsg-1.dsc 32b5a0c2ca628a8e2d57f9768126682df427670f 703144 casparcg-server_2.3.3+dfsg.orig.tar.xz 55b1f572ed8b7c128f42d334280f204e3f377b1e 10832 casparcg-server_2.3.3+dfsg-1.debian.tar.xz 744f839f22aad22e23e6a17d91e44cfbbf3466f7 19134 casparcg-server_2.3.3+dfsg-1_source.buildinfo Checksums-Sha256: ce3a2ee865fe964d66ad059845299755a213c3c0a4c208a7dac3171ce1ef32b2 2790 casparcg-server_2.3.3+dfsg-1.dsc 2aea399c2fc04245a633298315d8dd20fbe0f83a283b062b772db208ba2b2d64 703144 casparcg-server_2.3.3+dfsg.orig.tar.xz f279dfaa9c75345bfc1b58573f58843396ee15c3fd3d4781a11d1873aeb1fa2a 10832 casparcg-server_2.3.3+dfsg-1.debian.tar.xz 603a3b632099ed7889ab66a48750ead9b37fa3b148de84741f0e83f1e5b0f6aa 19134 casparcg-server_2.3.3+dfsg-1_source.buildinfo Files: c76df133b81e57bfd7701cf0735dbb06 2790 contrib/video optional casparcg-server_2.3.3+dfsg-1.dsc 4d1432ccaed163d81dc2e02dae308d89 703144 contrib/video optional casparcg-server_2.3.3+dfsg.orig.tar.xz 9851792b8c56bcaa74a9025a04062596 10832 contrib/video optional casparcg-server_2.3.3+dfsg-1.debian.tar.xz 2e272cddfd42c12258350eafbe491dd2 19134 contrib/video optional casparcg-server_2.3.3+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmMPdhsACgkQgSgKoIe6 +w5NvRAAjxqaXrnPURVAubwaTAyyltp6ws96mFRNdt1kbYoAZzlt+nZu6FgJyCq3 D3IOsVScON8aPk4NMB7c5jAIAIEku+lNtE56k31gObrAMEga8pFvNpnoxn2gm+gZ CkBv2zoATEYl7CPASFzaJyk7ADzoQ7qgzwBorOr8XkaCH5dgRzJdDLMxqgcjbcOZ Dfae9Fw34sInP28nMbbFJdQRqef7zg7bMCouVFnCoBSDiLbN2HyAgJl33NJxMWFw ixlibV2MOyFHc/pcLCRj0QjwU3X94NiGCtDs1sGCZbf+XVp+xPfvAFZEVrq1e+ab qupSXi6ZVISswJ5WNz6QUFMV6Xy5vUF5YZzCeq951Co0M8Sa13hunEsiQpYjck0c Fu+drmp/oXH6JGFfgkc1Xvc/SnGoRXChAGeMXA0oRaagxmFwqHJyqjEQ/68oARs1 s8itr44v1wuHXdJWSsafef5wvySncEucrg+VEv8LRG6BxNbr0RNN9oYS0NMCUOnT /hieldw8QR2wECuwciwo1FOS+pfmE/GcBH1cMZ10sA4iWW/sqDQtLASQ+aUWJPnh 3MULaq8AZ/5nps6/WJAeH25X/3tkkWwnmWX7TJnqyy3fmLWc2+varnPpiOQXJVd2 M190GCcSQ8f3Qt5OMV0F04EHb/+rTKbW0EPBKdn3uSpZj8lKcLY= =nlUj -END PGP SIGNATURE End Message ---
Bug#1018942: zookeeper: Can attempt to access the network during build
Package: zookeeper
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
X-Debbugs-Cc: scho...@ubuntu.com
We observed a FTBFS on amd64 in Ubuntu due to a DNS resolution error on
google.com, see https://bugs.launchpad.net/ubuntu/+source/zookeeper/+bug/1988541
for more details.
I don't exactly know why this hasn't happened during the Debian build,
but in any case, you'll find attached a debdiff to address the issue.
Cheers,
Simon
-- System Information:
Debian Release: bookworm/sid
APT prefers jammy-updates
APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'),
(100, 'jammy-backports'), (50, 'jammy-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-46-lowlatency (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru zookeeper-3.8.0/debian/patches/30-skip-tests-network.patch
zookeeper-3.8.0/debian/patches/30-skip-tests-network.patch
--- zookeeper-3.8.0/debian/patches/30-skip-tests-network.patch 2022-06-27
09:11:31.0 +0200
+++ zookeeper-3.8.0/debian/patches/30-skip-tests-network.patch 2022-09-02
11:10:51.0 +0200
@@ -456,3 +456,21 @@
@Test
public void testVersionOfDynamicFilename() throws Exception {
final int SERVER_COUNT = 5;
+---
a/zookeeper-server/src/test/java/org/apache/zookeeper/server/quorum/MultipleAddressesTest.java
b/zookeeper-server/src/test/java/org/apache/zookeeper/server/quorum/MultipleAddressesTest.java
+@@ -37,6 +37,7 @@
+ import java.util.stream.IntStream;
+ import org.apache.commons.collections4.CollectionUtils;
+ import org.apache.zookeeper.PortAssignment;
++import org.junit.jupiter.api.Disabled;
+ import org.junit.jupiter.api.Test;
+
+ public class MultipleAddressesTest {
+@@ -135,6 +136,7 @@
+ assertEquals(unreachableAddress, actualReturnedAddress);
+ }
+
++@Disabled("no network on debian buildds")
+ @Test
+ public void testRecreateSocketAddresses() throws UnknownHostException {
+ List searchedAddresses =
Arrays.stream(InetAddress.getAllByName("google.com"))
Processed: python-xarray: autopkgtest regression on s390x
Processing control commands: > reassign -1 src:python-xarray 0.21.0-1 Bug #1004870 [pandas] python-xarray: autopkgtest regression on s390x Bug reassigned from package 'pandas' to 'src:python-xarray'. Ignoring request to alter found versions of bug #1004870 to the same values previously set Ignoring request to alter fixed versions of bug #1004870 to the same values previously set Bug #1004870 [src:python-xarray] python-xarray: autopkgtest regression on s390x Marked as found in versions python-xarray/0.21.0-1. -- 1004870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004870: python-xarray: autopkgtest regression on s390x
Control: reassign -1 src:python-xarray 0.21.0-1 Hopefully assigning back to src:python-xarray now. If you have reason to believe this issue is caused by a bug in pandas, then please file a bug against pandas with the relevant details and mark that it blocks this bug.
Bug#1002414: marked as done (brebis: FTBFS: You need at least Python 3.4 to use Brebis)
Your message dated Fri, 02 Sep 2022 08:49:03 +
with message-id
and subject line Bug#1002414: fixed in brebis 0.10-3
has caused the Debian Bug report #1002414,
regarding brebis: FTBFS: You need at least Python 3.4 to use Brebis
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.)
--
1002414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: brebis
Version: 0.10-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py config
> /<>/setup.py:16: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> from distutils.core import setup
> You need at least Python 3.4 to use Brebis
> E: pybuild pybuild:355: configure: plugin distutils failed with: exit code=1:
> python3.10 setup.py config
> dh_auto_configure: error: pybuild --configure -i python{version} -p "3.10
> 3.9" returned exit code 13
> make: *** [debian/rules:6: build] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/12/20/brebis_0.10-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: brebis
Source-Version: 0.10-3
Done: Emanuele Rocca
We believe that the bug you reported is fixed in the latest version of
brebis, 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 1002...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emanuele Rocca (supplier of updated brebis 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: Thu, 01 Sep 2022 16:32:39 +0200
Source: brebis
Architecture: source
Version: 0.10-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Emanuele Rocca
Closes: 1002414
Changes:
brebis (0.10-3) unstable; urgency=medium
.
* Team upload.
* Remove buggy check for python version. (Closes: #1002414)
* Set the Debian Python team as maintainer with Carl's permission.
* Drop unnecessary build-depend on dh-sequence-python3.
* Update Standards-Version to 4.6.1, no changes needed.
Checksums-Sha1:
c3a6aa218998d21da41564c69b80adc247f1271f 1901 brebis_0.10-3.dsc
9affa8b87b09788d5367b67a0f3b5afb61bcdb42 2776 brebis_0.10-3.debian.tar.xz
7dcedeb34ff486d2df8f7e1448c1bc099930590f 6774 brebis_0.10-3_amd64.buildinfo
Checksums-Sha256:
902ddcfd6244ab85c000f7045635254d8f76e4b59e21630a6aded70c0a33a730 1901
brebis_0.10-3.dsc
c0fbf900625efa07375c2b742bcad2e18eceab844b62831eb8bacc2de52695bf 2776
brebis_0.10-3.debian.tar.xz
ef13c3d9051235043a8a64fc2344eb5ac44375fc05d1c6a5b81f17dfe7dffe68 6774
brebis_0.10-3_amd64.buildinfo
Files:
4dd546983a305ddc7b4f5b806030d632 1901 admin optional brebis_0.10-3.dsc
7f770310b5f2ee77ebd490a7e42a1282 2776 admin optional
brebis_0.10-3.debian.tar.xz
d5acd367383fc3f21b701e0d2aee70f3 6774 admin optional
brebis_0.10-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAmMRwD0ACgkQ1QhaB1D9
t6PtEg//QBdku+byBbNEtKnI+ebAQJEJQUVcP4zvXFDeDnRNAZ92empMKRbXuiB/
qg17duLajqCQSksEAlOWau3+aG+lqRhWRElvTs7ZWjSvz855fJsXus7aiMm7J+8Q
iL/6ZoshSXo9ls44NFrFF+/gtfDmyiCPubtpFdb/OVpZqUE/xkPsjyXmiH+ymbwr
5QTkRozBeTEvgSj4KIwGlKO8pR0sDHv6Q9V2J8+GvvRGLqvD7XjRhvatrxROCuT6
Bug#1016935: assaultcube: FTBFS with GCC 12: dwz fails
On Wed, 10 Aug 2022 07:41:00 +0200 Andreas Beckmann wrote: > Source: assaultcube > Version: 1.2.0.2.1-2 > Severity: serious > Tags: ftbfs sid bookworm > Justification: fails to build from source (but built successfully in the past) > > Hi, > > assaultcube recently started to FTBFS, this could be related to GCC 12 > becoming the default compiler. > > dh_dwz -O--sourcedirectory=source/src > dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_client: Unknown > debugging section .debug_addr > dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_server: Unknown > debugging section .debug_addr > dwz: Too few files for multifile optimization > dh_dwz: error: dwz > -mdebian/assaultcube/usr/lib/debug/.dwz/x86_64-linux-gnu/assaultcube.debug > -M/usr/lib/debug/.dwz/x86_64-linux-gnu/assaultcube.debug -- debian/assaultcube/usr/lib/games/assaultcube/ac_client debian/assaultcube/usr/lib/games/assaultcube/ac_server returned exit code 1 > dh_dwz: error: Aborting due to earlier error > make: *** [debian/rules:9: binary] Error 25 > > > Andreas Upstream has hardcoded clang to be used, and it seems that clang and dh_dwz won't work together. As they say in their Makefile that they did this because there were problems with gcc in the past, and stress that those bugs have been fixed, I'll fix it by changing the compiler to gcc. -- tobi
Bug#1016935: marked as pending in assaultcube
Control: tag -1 pending Hello, Bug #1016935 in assaultcube reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/games-team/assaultcube/-/commit/1addf37f8b904acb44a7b1b5f3480410dd313167 Do not compile with clang, as this fails with dh_dwz. (Closes: #1016935) (this message was generated automatically) -- Greetings https://bugs.debian.org/1016935
Processed: Bug#1016935 marked as pending in assaultcube
Processing control commands: > tag -1 pending Bug #1016935 [src:assaultcube] assaultcube: FTBFS with GCC 12: dwz fails Added tag(s) pending. -- 1016935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018936: busco: unsatisfiable dependency on arm64
Source: busco Version: 5.4.3-1 Severity: serious Hi Maintainer Busco is unable to migrate to testing due to an unsatisfiable dependency on arm64. Britney only checks installability of arch:all packages on amd64 and arm64, so other architectures may also be affected. I noticed that the busco binary package recently gained a Depends on hmmer, which is not built everywhere. If the Depends on hmmer is really needed, then busco should become arch:any and have a Build-Depends on hmmer to prevent it from building on architectures where it will not be installable. Regards Graham
Bug#1016600: siconos: vtk[6,7] removal
On Thu, Sep 1, 2022 at 10:56 PM Adrian Bunk wrote: > > On Wed, Aug 03, 2022 at 10:42:08PM +0200, Sebastian Ramacher wrote: > > Source: siconos > > Version: 4.3.1+dfsg-2 > > Severity: serious > > X-Debbugs-Cc: sramac...@debian.org > > Tags: sid bookworm > > Control: block 1016597 by -1 > > User: gl...@debian.org > > Usertags: vtk6_vtk7_removal > > > > Based on #1013156 and similar bugs: > > > > Dear maintainer, > > > > Debian archive has now three major versions of the VTK (The > > Visualization Toolkit) package: vtk6, vtk7 and vtk9. Old vesions > > (vtk6 and vtk7) are not supported by upstream and the package itself > > is not easy for the mainance. > > > > We aim to drop old and deprecated version vtk6 and vtk7 packages before > > the freeze of the Debian 12 Bookworm. Your package depends on vtk6 or > > vtk7. Thus we ask you to migrate it to the latest vtk9 package. > > Two observations regarding the usage of VTK in siconos: > > There is WITH_VTK in siconos that does not seem to build with VTK 9, > but it's anyway not enabled. > > The only current usage of VTK is python3-vtk7 in siconos-mechanics-tools. > This might need upstrream fixes like > https://github.com/siconos/siconos/pull/437 > > > Cheers Thank you Adrian. I have an update to the package for a newer upstream version that has been under construction for a while, but I haven't been available until recently to work on it more. I'll try to get this done soon. Steve
Bug#1017941: greenbone-security-assistant downloads source from the network
Hello Steve, We had already had a bug report about this issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=98 To short: we moved the package to contrib because we had to download modules during the build. We also had a discussion on debian-devel: https://lists.debian.org/debian-devel/2020/12/threads.html#00215 I know it is really not an ideal solution. If you think Debian can't keep this package in contrib, please let us know. Thanks Sophie OpenPGP_signature Description: OpenPGP digital signature
Processed: pcs: CVE-2022-2735: Obtaining an authentication token for hacluster user leads to privilege escalation
Processing control commands: > found -1 0.10.8-1 Bug #1018930 [src:pcs] pcs: CVE-2022-2735: Obtaining an authentication token for hacluster user leads to privilege escalation Marked as found in versions pcs/0.10.8-1. -- 1018930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018930: pcs: CVE-2022-2735: Obtaining an authentication token for hacluster user leads to privilege escalation
Source: pcs Version: 0.11.3-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 0.10.8-1 Hi, The following vulnerability was published for pcs. CVE-2022-2735[0]: | Obtaining an authentication token for hacluster user leads to | privilege escalation If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-2735 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2735 [1] https://www.openwall.com/lists/oss-security/2022/09/01/4 Regards, Salvatore
