Bug#1023046: zabbix: FTBFS: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
On Sat, Oct 29, 2022 at 04:51:19PM +, Mathias Gibbens wrote: > Source: zabbix > Version: 1:6.0.9+dfsg-1.1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > > While rebuilding the reverse build dependencies of another golang > package I'm updating, I noticed that zabbix fails to build in a clean > sid chroot. I suspect this was likely caused by the recent update of > the golang-golang-x-sys package, but I haven't investigated further. > > > on.compileArch=`go env GOARCH` -X main.applicationName=zabbix_web_service" > > -o bin zabbix.com/cmd/zabbix_web_service > > > > [snip] > > > > golang.org/x/text/unicode/norm > > # golang.org/x/sys/unix > > vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires go1.17 > > or later (-lang was set to go1.16; check go.mod) > > vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice requires > > go1.17 or later (-lang was set to go1.16; check go.mod) > > vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice requires > > go1.17 or later (-lang was set to go1.16; check go.mod) > > vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice requires > > go1.17 or later (-lang was set to go1.16; check go.mod) > > zabbix.com/pkg/procfs > > # golang.org/x/sys/unix > > vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires go1.17 > > or later (-lang was set to go1.16; check go.mod) > > vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice requires > > go1.17 or later (-lang was set to go1.16; check go.mod) > > vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice requires > > go1.17 or later (-lang was set to go1.16; check go.mod) > > vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice requires > > go1.17 or later (-lang was set to go1.16; check go.mod) This comes from the new version of golang-golang-x-sys, see also [1]. cu Adrian [1] https://tracker.debian.org/news/1384566/accepted-golang-golang-x-sys-010-1bpo111-source-into-bullseye-backports/
Bug#1024431: libgccjit0: missing Depends: libc6-dev
Hello gcc maintainers, I believe that you won't have seen any messages to this bug yet, if I recall correctly how reassignment works with the BTS. On Sat 19 Nov 2022 at 12:16PM +01, Andreas Beckmann wrote: > The Dependency chain is emacs-gtk -> libgccjit0 -> libgcc-12-dev > libgcc-12-dev has a Recommends: libc6-dev but that seems to be insufficient > for libgccjit0. > (one of the errors was 'libgccjit.so: error: error invoking gcc driver' so > that seems to be out of the realm of emacs. > > IMO, the real bug seems to be "libgccjit0: missing Depends: libc6-dev" > Cloning/reassigning/blocking accordingly. > > The only other user of libgccjit0 is python3-gccjit which may or may not have > the same problem. libgccjit0 already transitively recommends libc6-dev, and it looks like this needs to be upgraded to a hard dependency. This is the last remaining known RC bug before Emacs 28 can finally migrate. Could you make the change, please? Thanks. -- Sean Whitton signature.asc Description: PGP signature
Processed: Re: Bug#1010170: FTBFS: lisp/net/tramp-archive-tests.log contains unexpected results
Processing control commands: > fixed 1010170 1:28.2+1-6 Bug #1010170 [src:emacs] FTBFS: lisp/net/tramp-archive-tests.log contains unexpected results Marked as fixed in versions emacs/1:28.2+1-6. > fixed 1000744 1:28.2+1-6 Bug #1000744 [src:emacs] emacs: FTBFS on mipsel: Ran 3873 tests, 3786 results as expected, 1 unexpected, 86 skipped Marked as fixed in versions emacs/1:28.2+1-6. -- 1000744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000744 1010170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010170: FTBFS: lisp/net/tramp-archive-tests.log contains unexpected results
Control: fixed 1010170 1:28.2+1-6 Control: fixed 1000744 1:28.2+1-6 emacs FTBFS bugs seem to be already fixed in sid. Thanks, -- Tatsuya Kinoshita pgp1LLgv6B2cH.pgp Description: PGP signature
Processed: ruby-memory-profiler: diff for NMU version 0.9.14-4.1
Processing control commands: > tags 1019638 + patch Bug #1019638 [src:ruby-memory-profiler] ruby-memory-profiler: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. Added tag(s) patch. > tags 1019638 + pending Bug #1019638 [src:ruby-memory-profiler] ruby-memory-profiler: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. Added tag(s) pending. -- 1019638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019638: ruby-memory-profiler: diff for NMU version 0.9.14-4.1
Control: tags 1019638 + patch
Control: tags 1019638 + pending
Dear maintainer,
I've prepared an NMU for ruby-memory-profiler (versioned as 0.9.14-4.1)
and uploaded it to DELAYED/15. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru ruby-memory-profiler-0.9.14/debian/changelog ruby-memory-profiler-0.9.14/debian/changelog
--- ruby-memory-profiler-0.9.14/debian/changelog 2021-11-08 01:42:01.0 +0200
+++ ruby-memory-profiler-0.9.14/debian/changelog 2022-11-20 02:14:54.0 +0200
@@ -1,3 +1,10 @@
+ruby-memory-profiler (0.9.14-4.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add upstream fixes for Ruby 3.1. (Closes: #1019638)
+
+ -- Adrian Bunk Sun, 20 Nov 2022 02:14:54 +0200
+
ruby-memory-profiler (0.9.14-4) unstable; urgency=low
* Team upload.
diff -Nru ruby-memory-profiler-0.9.14/debian/patches/0001-Fix-normalize_path-and-guess_gem-to-support-Ruby-3.patch ruby-memory-profiler-0.9.14/debian/patches/0001-Fix-normalize_path-and-guess_gem-to-support-Ruby-3.patch
--- ruby-memory-profiler-0.9.14/debian/patches/0001-Fix-normalize_path-and-guess_gem-to-support-Ruby-3.patch 1970-01-01 02:00:00.0 +0200
+++ ruby-memory-profiler-0.9.14/debian/patches/0001-Fix-normalize_path-and-guess_gem-to-support-Ruby-3.patch 2022-11-20 02:14:02.0 +0200
@@ -0,0 +1,39 @@
+From dcc4464d1766046712a406b32651a00a64d7e592 Mon Sep 17 00:00:00 2001
+From: Benoit Daloze
+Date: Tue, 25 Oct 2022 15:06:10 +0200
+Subject: Fix normalize_path and guess_gem to support Ruby 3+
+
+---
+ lib/memory_profiler/helpers.rb | 2 +-
+ lib/memory_profiler/results.rb | 2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/lib/memory_profiler/helpers.rb b/lib/memory_profiler/helpers.rb
+index d894ffa..c008cd1 100644
+--- a/lib/memory_profiler/helpers.rb
b/lib/memory_profiler/helpers.rb
+@@ -16,7 +16,7 @@ module MemoryProfiler
+ gemname
+ elsif /\/rubygems[\.\/]/ =~ path
+ "rubygems"
+-elsif /ruby\/2\.[^\/]+\/(?[^\/\.]+)/ =~ path
++elsif /ruby\/\d\.[^\/]+\/(?[^\/\.]+)/ =~ path
+ stdlib
+ elsif /(?[^\/]+\/(bin|app|lib))/ =~ path
+ app
+diff --git a/lib/memory_profiler/results.rb b/lib/memory_profiler/results.rb
+index 5630977..d6fad8d 100644
+--- a/lib/memory_profiler/results.rb
b/lib/memory_profiler/results.rb
+@@ -172,7 +172,7 @@ module MemoryProfiler
+ @normalize_path[path] ||= begin
+ if %r!(/gems/.*)*/gems/(?[^/]+)(?.*)! =~ path
+ "#{gemname}#{rest}"
+-elsif %r!ruby/2\.[^/]+/(?[^/.]+)(?.*)! =~ path
++elsif %r!ruby/\d\.[^/]+/(?[^/.]+)(?.*)! =~ path
+ "ruby/lib/#{stdlib}#{rest}"
+ elsif %r!(?[^/]+/(bin|app|lib))(?.*)! =~ path
+ "#{app}#{rest}"
+--
+2.30.2
+
diff -Nru ruby-memory-profiler-0.9.14/debian/patches/0002-Adapt-tests-for-Ruby-3.0.patch ruby-memory-profiler-0.9.14/debian/patches/0002-Adapt-tests-for-Ruby-3.0.patch
--- ruby-memory-profiler-0.9.14/debian/patches/0002-Adapt-tests-for-Ruby-3.0.patch 1970-01-01 02:00:00.0 +0200
+++ ruby-memory-profiler-0.9.14/debian/patches/0002-Adapt-tests-for-Ruby-3.0.patch 2022-11-20 02:14:02.0 +0200
@@ -0,0 +1,51 @@
+From 499480ce9820f7df21a4e7ca30c1bbd78564be2e Mon Sep 17 00:00:00 2001
+From: Benoit Daloze
+Date: Tue, 25 Oct 2022 15:18:49 +0200
+Subject: Adapt tests for Ruby 3.0
+
+---
+ test/test_reporter.rb | 19 +++
+ 1 file changed, 15 insertions(+), 4 deletions(-)
+
+diff --git a/test/test_reporter.rb b/test/test_reporter.rb
+index 55c440f..c10efd6 100644
+--- a/test/test_reporter.rb
b/test/test_reporter.rb
+@@ -232,7 +232,15 @@ class TestReporter < Minitest::Test
+ end
+ end
+
+-assert_equal(45, results.total_allocated, "45 strings should be allocated")
++if RUBY_VERSION < '3'
++ # 3 times "0", 2 times for interpolated strings
++ total_allocated = 5 * (3 + 2 + 2 + 2)
++else
++ # 3 times "0", 2 times for short interpolated strings, 3 times for long interpolated strings
++ total_allocated = 5 * (3 + 2 + 3 + 3)
++end
++
++assert_equal(total_allocated, results.total_allocated, "#{total_allocated} strings should be allocated")
+ assert_equal(20, results.strings_allocated.size, "20 unique strings should be observed")
+ assert_equal(0, results.strings_retained.size, "0 unique strings should be retained")
+ end
+@@ -244,11 +252,14 @@ class TestReporter < Minitest::Test
+ string.to_sym
+ end
+
+-assert_equal(3, results.total_allocated)
+-assert_equal(0, results.total_retained)
++strings_allocated = RUBY_VERSION < '3' ? 2 : 1
++assert_equal(strings_allocated + 1, results.total_allocated)
++assert_includes(0..1, results.total_retained)
+ assert_equal(1, results.strings_allocated.size)
++
+ assert_equal('String', results.allocated_objects_by_class[0][:data])
+-assert_equal(2, results.allocated_objects_by_class[0][:count])
++
Bug#1024313: marked as done (amgcl: b-d on python3-all-dev, but not built for all supported Python3 versions)
Your message dated Sun, 20 Nov 2022 00:19:05 + with message-id and subject line Bug#1024313: fixed in amgcl 1.4.3-3 has caused the Debian Bug report #1024313, regarding amgcl: b-d on python3-all-dev, but not built for all supported Python3 versions 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.) -- 1024313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: amgcl Version: 1.4.3-2 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.11 python3-all-dev Hi Maintainer This package build-depends on python3-all-dev, but does not build extensions/libraries for all supported python3 versions. This is seen on the transition tracker for adding python3.11 support [1] and creates false positives. Please either replace the b-d python3-all-dev with python3-dev, or build for all supported Python3 versions. With the former solution you get later exposure to a new python3 version, with the latter solution you get early exposure. Regards Graham [1] https://release.debian.org/transitions/html/python3.11-add.html --- End Message --- --- Begin Message --- Source: amgcl Source-Version: 1.4.3-3 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of amgcl, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan (supplier of updated amgcl 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, 19 Nov 2022 14:47:54 -0800 Source: amgcl Architecture: source Version: 1.4.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Dima Kogan Closes: 1024313 Changes: amgcl (1.4.3-3) unstable; urgency=medium . * Build-Depends: python3-dev, not python3-all-dev (Closes: #1024313) Checksums-Sha1: 0fdb7c56681f035e461218b0e4ccab53a6dc5d71 2324 amgcl_1.4.3-3.dsc 4c62ab29c689170e12b3822893b711dc6a32c2b5 5324 amgcl_1.4.3-3.debian.tar.xz 1aad345b06defac50416ea279b231ea1c2be6397 11722 amgcl_1.4.3-3_amd64.buildinfo Checksums-Sha256: 5a06c249e08138e1599a9f328b5dbf06f10585cfb43699fdf7eab29fcf2646dd 2324 amgcl_1.4.3-3.dsc 91bf0827c5cee9746e4b99f967c63dc243d0997e0964d5f6b6a0c6ad536a79bd 5324 amgcl_1.4.3-3.debian.tar.xz 09c309eb3019c338dc14e36c65ab672c548d17a651d5c585a7694658191c7fae 11722 amgcl_1.4.3-3_amd64.buildinfo Files: 16b2730e00a8c31d4b02448e484e4adf 2324 contrib/libdevel optional amgcl_1.4.3-3.dsc 63254bbbcd0ed24be136ad221453fb70 5324 contrib/libdevel optional amgcl_1.4.3-3.debian.tar.xz 02692771ebe8b58d4b6c581d42556990 11722 contrib/libdevel optional amgcl_1.4.3-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmN5bW4ACgkQrMfCzzCU EYgnHA//TjW0XmMG/rVbf3IbbHqNNLW5injXXScfHAwiEXYASywoVitEMp0LqLSm C1zVhg6bDN60cmQQpQ3HFynsVJlwYm7Ctk3SCpyFLhOolngSGlhmOgOMh0lmTgFt elfetkoQHr50kb164rl835DSQmG13juuJXtuY/Qbjx9X+URvnHX7P42WKPqlv+Hz xpB+/IA0uhqd/CY6UQsE1AOsHqcryG7pNhC1z3evkwtwcZTM/MWfxl+z+vVa/rGT kFGzJ6ITEERb9LtHYr8E2aTGCpf8yvsMx9+bMRCIwB7+1BeOOf+fF/eaZVwshlrP Jf2Dh+kJpGvhYqg3Q/2I91fJk7ak/5hJuMRuAPmBOnjBbX+8+6IJsYuNdNkCGPse wrLUQ9F8aG/mZPE0A3VjWKLUjEhmPh0RxkgxZem7uAiZEyv4YTe55sgOA5plWEMD TXgrkfTwYFXlsLooxrDUUxrL8XuAvbPWDMlyTXti3+1BF7XU/RKPpN1Yp35AeJtA KHdEOP0oF2JRml5eLN4lj8pEeBVgrJm2I7O584fExdavWFaqcRdAGEj9fDk6I4vh Z1jAvfczxYoLjgp2le9bAd+jaAriR8XTeu+xiUEA/pUe0oy6iPo/zLPFoGn9Zspm oYOfMCIK1XLTP/hBazuaQdA4pSwJTAbjCg+sY0GBELx1dGDYOAg= =T1Xs -END PGP SIGNATURE End Message ---
Bug#1024265: marked as done (opengv: Build for all supported python3 versions or Build-Depend on python3-dev)
Your message dated Sun, 20 Nov 2022 00:06:41 + with message-id and subject line Bug#1024265: fixed in opengv 1.0+1git91f4b1-7 has caused the Debian Bug report #1024265, regarding opengv: Build for all supported python3 versions or Build-Depend on python3-dev 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.) -- 1024265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opengv Version: 1.0+1git91f4b1-6 Severity: normal User: debian-pyt...@lists.debian.org Usertags: python3.11 python3-all-dev This package build-depends on python3-all-dev, but does not build extensions/libraries for all supported python3 versions. This is seen on the transition tracker for adding python3.11 support [1] and creates false positives. Please either replace the b-d python3-all-dev with python3-dev, or build for all supported Python3 versions. With the former solution you get later exposure to a new python3 version, with the latter solution you get early exposure. https://release.debian.org/transitions/html/python3.11-add.html SR --- End Message --- --- Begin Message --- Source: opengv Source-Version: 1.0+1git91f4b1-7 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of opengv, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan (supplier of updated opengv 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, 19 Nov 2022 14:34:50 -0800 Source: opengv Architecture: source Version: 1.0+1git91f4b1-7 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Dima Kogan Closes: 1024265 Changes: opengv (1.0+1git91f4b1-7) unstable; urgency=medium . [ Stefano Rivera ] * Use pybuild to build for multiple Python versions. Thanks Tyler Weaver. (Closes: #1024265) Checksums-Sha1: b99f7c0ca665cada1299e67b34d67878aca9466a 2334 opengv_1.0+1git91f4b1-7.dsc 10557df38bd3d49414e16628018b5202c8bc8431 4732 opengv_1.0+1git91f4b1-7.debian.tar.xz 7079270d89418db43e4d1fb83a92f27903b4f13d 12325 opengv_1.0+1git91f4b1-7_amd64.buildinfo Checksums-Sha256: e3e8b9a2e3dbb28bfc7b1cbf473a5d5f1138e2c4467389e19f4acf2937ec9d90 2334 opengv_1.0+1git91f4b1-7.dsc 1bb499681d91a50c809a2bdb30f44a42de01391cdd9301305d994520e17803f5 4732 opengv_1.0+1git91f4b1-7.debian.tar.xz d318655202275bd8d82cd4d9f480e91c512bbbcaf8dad181eb91822ece79ce8e 12325 opengv_1.0+1git91f4b1-7_amd64.buildinfo Files: ac09e0e83cecde9c4592b19a52d1a17c 2334 libdevel optional opengv_1.0+1git91f4b1-7.dsc 57324b4a4e730a4bcde2270834f01c9a 4732 libdevel optional opengv_1.0+1git91f4b1-7.debian.tar.xz f718537ab8b2537102e3debba75439ee 12325 libdevel optional opengv_1.0+1git91f4b1-7_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmN5YScACgkQrMfCzzCU EYiCMBAAlhptM46Rvq0YcfgXMbJf6jJiYBTkz+feMqmJz7Ox+I05p0U1sNCfdWCc ssueqzhrzxTZmlTWkw8ZjnD/6kioiAq9urh06mJPuMxClBr2bUtv+0Evmx0XRqz0 YfRvezIzOJaApIJyYx11grAzOb/E7V71ULZNk4B8X/pGfClefeQatXjYaKtfIse/ jjTwFYrRf3jQYT1mYpTdYoH4Yu7Madv3IgdhrvqvjhyaKJpRRryeJ01tQchVoP7Q qscex/NH+4riNhhR4dbjIznp9CGdgiKAeJg2LwQLuT1Zapj/oht3EfiKie8oa+f4 Z1LQpRYmazylUJyCVNvX48HJhN1FzvNytvX6HerIXqg2/EA65iZmTvU+ypQWV0wI 7pEo3v8Jt/bhDIap1DMLV8cWzQEbjpGeMk7fOBfcyY63ohZd2p6CPQ6B18WUS+3t kN3ZbLozXUfn4JmSev98ym3r1tjv68RLskI3RjMICC8wtzYnLR8z23pJxah5xoaB BZwErQBKgqyZUvU9Y5WErHKcqC8cvc/sVc784hHCyGs/pYFf58T4cPekC4MRJYr5 K0SqVHcQedkqWMUbGlBUeEGtii3XhlI4DxMGYSn5pDXqArsEU9VuQexnEvQ2L7vK kHp7ojgHCYII09qUAzZ3w2PPjXgDsxorY8PtIToDyC0Bx8/MHoA= =wNA6 -END PGP SIGNATURE End Message ---
Bug#1022124: marked as done (libdbd-oracle-perl needs binaries uploaded for the perl 5.36 transitions)
Your message dated Sun, 20 Nov 2022 00:05:09 + with message-id and subject line Bug#1022124: fixed in libdbd-oracle-perl 1.80-4 has caused the Debian Bug report #1022124, regarding libdbd-oracle-perl needs binaries uploaded for the perl 5.36 transitions 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.) -- 1022124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdbd-oracle-perl Version: 1.80-3 Severity: serious Tags: ftbfs libdbd-oracle-perl cannot be built on the buildds, and it needs binaries uploaded for the perl 5.36 transition. --- End Message --- --- Begin Message --- Source: libdbd-oracle-perl Source-Version: 1.80-4 Done: Alex Muntada We believe that the bug you reported is fixed in the latest version of libdbd-oracle-perl, 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 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alex Muntada (supplier of updated libdbd-oracle-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Oct 2022 15:17:33 + Binary: libdbd-oracle-perl libdbd-oracle-perl-dbgsym Source: libdbd-oracle-perl Architecture: amd64 i386 source Version: 1.80-4 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Alex Muntada Closes: 1022124 Description: libdbd-oracle-perl - Perl DBI driver for Oracle Changes: libdbd-oracle-perl (1.80-4) unstable; urgency=medium . * Declare compliance with Debian Policy 4.6.1.0 * Rebuild for perl 5.36 (Closes: #1022124) Checksums-Sha1: 6c5a56bc2de91e59ec126a7c07fd0dc7fd8b2972 2178 libdbd-oracle-perl_1.80-4.dsc a25a8d211360423f8a1be247084f47a5790e62e1 7420 libdbd-oracle-perl_1.80-4.debian.tar.xz 3c13fbed4683a25d7c877d7e4007be0844e9b647 224624 libdbd-oracle-perl-dbgsym_1.80-4_amd64.deb 9f5522043daaa3843bcaab14f4f99bc82f0418fe 6497 libdbd-oracle-perl_1.80-4_amd64.buildinfo bd1d9100a63d3cbf809b77915c32d82d318d6508 360104 libdbd-oracle-perl_1.80-4_amd64.deb e8790489f2fc89fdfb05243f04fbfde2fb415fc6 199872 libdbd-oracle-perl-dbgsym_1.80-4_i386.deb 10c16950bc736e0c09fe0db926cc6914078a359e 6643 libdbd-oracle-perl_1.80-4_i386.buildinfo cf6ec796db08ec18aae0dbf79ee32c6f584b6a3d 363112 libdbd-oracle-perl_1.80-4_i386.deb Checksums-Sha256: 323325abe9333114273fab3e40cf73f2657cfbaf7f39a823262d313f153ca515 2178 libdbd-oracle-perl_1.80-4.dsc bd0da1b6e5941bf3b85fa23e001684107f76cf2a3f37c1566987b45c1936f140 7420 libdbd-oracle-perl_1.80-4.debian.tar.xz 2c8ae1b321af8bc918d438f59eb0f5313d43458b79f9350ed374ed79a5b762d3 224624 libdbd-oracle-perl-dbgsym_1.80-4_amd64.deb 6f49643caec85d408d6965122186b91bd0a9810a1f13d1f1465179c8af50e0bf 6497 libdbd-oracle-perl_1.80-4_amd64.buildinfo 0592a7c0bdcabe8e8a8a5feb146479bf16ca3e13b56afa2bcf9198fd46d08514 360104 libdbd-oracle-perl_1.80-4_amd64.deb f1a0546e8ba8595d05d0aae5e9eebdb54fbba0b038ab64bd514dec840fd15bbd 199872 libdbd-oracle-perl-dbgsym_1.80-4_i386.deb 97f15e2306dfdb7bb3e3cc3a85079d4c4fc8769ebf07deb9b41c008a033862bf 6643 libdbd-oracle-perl_1.80-4_i386.buildinfo bcbacf4c6bdf9cea9bbf2285a6d6e8238bf1d511d487a37d91608d635cfd77a0 363112 libdbd-oracle-perl_1.80-4_i386.deb Files: 76dea3ed9dd1def283ec953b0511fa5e 2178 contrib/perl optional libdbd-oracle-perl_1.80-4.dsc 8d91b59ce38f3c43f703b10cf6a94d42 7420 contrib/perl optional libdbd-oracle-perl_1.80-4.debian.tar.xz 06636c6eb2910e0c8bdb978d8e5a0bd6 224624 contrib/debug optional libdbd-oracle-perl-dbgsym_1.80-4_amd64.deb 35784eb5e6975495b34b48f9489eeb90 6497 contrib/perl optional libdbd-oracle-perl_1.80-4_amd64.buildinfo 5e95da8c936ebbdf927ad66a5c315537 360104 contrib/perl optional libdbd-oracle-perl_1.80-4_amd64.deb a0e4335df549c40b9cf7ba40f66c9b1e 199872 contrib/debug optional libdbd-oracle-perl-dbgsym_1.80-4_i386.deb e1852d56dd89539a928783a4fbd410ec 6643 contrib/perl optional libdbd-oracle-perl_1.80-4_i386.buildinfo f4eaabe118e2646720fcb1fcef5b8979 363112 contrib/perl optional libdbd-oracle-perl_1.80-4_i386.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEaUBwKsbetWW2SKTt466XjoNOXn4FAmN5Z/oACgkQ466XjoNO
Processed: block 1020258 with 1024431, reassign 1024431 to libgccjit0 ...
Processing commands for cont...@bugs.debian.org: > block 1020258 with 1024431 Bug #1020258 [emacs] emacs: elpa-*: fails to install: libgccjit.so: error: error invoking gcc driver 1020258 was not blocked by any bugs. 1020258 was blocking: 1017833 1020178 1023297 Added blocking bug(s) of 1020258: 1024431 > reassign 1024431 libgccjit0 12.2.0-9 Bug #1024431 [emacs] emacs: elpa-*: fails to install: libgccjit.so: error: error invoking gcc driver Bug reassigned from package 'emacs' to 'libgccjit0'. No longer marked as found in versions emacs/1:28.1+1-4, emacs/1:28.2+1-1, and emacs/1:28.1+1-1. Ignoring request to alter fixed versions of bug #1024431 to the same values previously set Bug #1024431 [libgccjit0] emacs: elpa-*: fails to install: libgccjit.so: error: error invoking gcc driver Marked as found in versions gcc-12/12.2.0-9. > retitle 1024431 libgccjit0: missing Depends: libc6-dev Bug #1024431 [libgccjit0] emacs: elpa-*: fails to install: libgccjit.so: error: error invoking gcc driver Changed Bug title to 'libgccjit0: missing Depends: libc6-dev' from 'emacs: elpa-*: fails to install: libgccjit.so: error: error invoking gcc driver'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1020258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020258 1024431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: pygccjit: diff for NMU version 0.4-12.1
Processing control commands: > tags 1022181 + patch Bug #1022181 [src:pygccjit] pygccjit: non-standard gcc used for build (gcc-10) Added tag(s) patch. > tags 1022181 + pending Bug #1022181 [src:pygccjit] pygccjit: non-standard gcc used for build (gcc-10) Added tag(s) pending. -- 1022181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022181: pygccjit: diff for NMU version 0.4-12.1
Control: tags 1022181 + patch Control: tags 1022181 + pending Dear maintainer, I've prepared an NMU for pygccjit (versioned as 0.4-12.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru pygccjit-0.4/debian/changelog pygccjit-0.4/debian/changelog --- pygccjit-0.4/debian/changelog 2021-09-15 14:23:21.0 +0300 +++ pygccjit-0.4/debian/changelog 2022-11-20 01:51:51.0 +0200 @@ -1,3 +1,10 @@ +pygccjit (0.4-12.1) unstable; urgency=low + + * Non-maintainer upload. + * Build using gcc 12. (Closes: #1022181) + + -- Adrian Bunk Sun, 20 Nov 2022 01:51:51 +0200 + pygccjit (0.4-12) unstable; urgency=medium * Stop building the python3-pygccjit-dbg package. Closes: #994329. diff -Nru pygccjit-0.4/debian/control pygccjit-0.4/debian/control --- pygccjit-0.4/debian/control 2021-09-15 14:22:28.0 +0300 +++ pygccjit-0.4/debian/control 2022-11-20 01:51:35.0 +0200 @@ -5,7 +5,7 @@ Build-Depends: debhelper (>= 13), dh-python, python3-all-dev, cython3, python3-setuptools, - libgccjit-10-dev, gcc-10, + libgccjit-12-dev, gcc-12, python3-sphinx Standards-Version: 4.6.0 Homepage: https://github.com/davidmalcolm/pygccjit diff -Nru pygccjit-0.4/debian/rules pygccjit-0.4/debian/rules --- pygccjit-0.4/debian/rules 2021-09-15 14:23:18.0 +0300 +++ pygccjit-0.4/debian/rules 2022-11-20 01:51:46.0 +0200 @@ -1,7 +1,7 @@ #!/usr/bin/make -f -export CC = gcc-10 -export LDSHARED = gcc-10 -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro +export CC = gcc-12 +export LDSHARED = gcc-12 -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro export PYBUILD_DESTDIR_python3=debian/python3-gccjit/
Bug#1022681: haskell-clientsession build depends on haskell-cipher-aes and haskell-cprng-aes
On Mon, Oct 24, 2022 at 01:36:11PM +0300, Adrian Bunk wrote:
> Source: haskell-clientsession
> Version: 0.9.1.2-7
> Severity: serious
> Control: affects -1 src:haskell-cipher-aes src:haskell-cprng-aes
>
> haskell-clientsession build depends on haskell-cipher-aes
> and haskell-cprng-aes that have "intend to remove" bugs.
Ilias, this bug is the reason why your removal notices for
haskell-{cipher,cprng}-aes are about to kick git-annex out
of bookworm.
To keep git-annex in bookworm, it's either applying one of the two
upstream MRs for haskell-clientsessionor postponing the removal notices
for haskell-{cipher,cprng}-aes.
cu
Adrian
Bug#1022577: marked as done (llvm-toolchain-15: Mesa on armel,armhf fails with LLVM ERROR: Cannot select)
Your message dated Sat, 19 Nov 2022 23:39:53 + with message-id and subject line Bug#1022577: fixed in llvm-toolchain-15 1:15.0.5-2 has caused the Debian Bug report #1022577, regarding llvm-toolchain-15: Mesa on armel,armhf fails with LLVM ERROR: Cannot select 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.) -- 1022577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-toolchain-15 Severity: serious Tags: ftbfs X-Debbugs-Cc: Debian X Strike Force Control: affects -1 src:mesa src:lomiri-settings-components src:clutter-1.0 src:mutter src:gtk4 src:mrpt src:sphinx Control: block 1022576 by -1 https://buildd.debian.org/status/fetch.php?pkg=mutter=armhf=43.0-3=1666029584=0 ... # Start of pipeline tests LLVM ERROR: Cannot select: 0x1300f80: v4i32 = ARMISD::VCMPZ 0x1301c70, Constant:i32<2> 0x1301c70: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0xdf9afc, 0x131c538:1, Constant:i32<4> 0x131c538: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0xdf9afc, 0x12fb7e0, Constant:i32<64> 0x12fb7e0: i32,ch = CopyFromReg 0xdf9afc, Register:i32 %23 0x12e99c0: i32 = Register %23 0x131a9a8: i32 = Constant<64> 0x1319fd0: i32 = Constant<4> 0x131a2e8: i32 = Constant<2> In function: fs_variant_partial ... Some discussion is in https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1993800 --- End Message --- --- Begin Message --- Source: llvm-toolchain-15 Source-Version: 1:15.0.5-2 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of llvm-toolchain-15, 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 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated llvm-toolchain-15 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: Sat, 19 Nov 2022 23:25:04 +0100 Source: llvm-toolchain-15 Built-For-Profiles: noudeb Architecture: source Version: 1:15.0.5-2 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Gianfranco Costamagna Closes: 1022577 1023101 Changes: llvm-toolchain-15 (1:15.0.5-2) unstable; urgency=medium . [ Gianfranco Costamagna ] * Add libomp target library to mips64el (Closes: #1023101) * Explictly depend on spirv-14 for mips64el, to ease bootstrapping on buildds (this should be dropped once we build a spirv-15 in archive) * Cherry-pick two upstream patches to unblock mesa build on arm* (Closes: #1022577) . [ Sylvestre Ledru ] * store the sccache results in /tmp/buildd/source/sccache-stats.json Checksums-Sha1: 6e077248c7ae68db21011cdb93cb16cf1160e186 7260 llvm-toolchain-15_15.0.5-2.dsc 21c5270182b32d345a07030283a0d1800f4bf3f6 162340 llvm-toolchain-15_15.0.5-2.debian.tar.xz 7c110c62bb9a899aa9988a543a88245e5099a842 11761 llvm-toolchain-15_15.0.5-2_source.buildinfo Checksums-Sha256: 0f09319f9173b6163191ae151a0a6917d2f060038153d36f57dbfeb742386c01 7260 llvm-toolchain-15_15.0.5-2.dsc 72559210a5370a736d2185786a7c88c5c2b53e435e6720d7485eaf98128e35f4 162340 llvm-toolchain-15_15.0.5-2.debian.tar.xz cfa994f21c58a083a41b60d4ddb89006679817ab563770c91952d7b7f4177854 11761 llvm-toolchain-15_15.0.5-2_source.buildinfo Files: 5719b01f10df55842e4eec002ab6ad8e 7260 devel optional llvm-toolchain-15_15.0.5-2.dsc 4c21dc4549c5a46afef1ed881f74dc00 162340 devel optional llvm-toolchain-15_15.0.5-2.debian.tar.xz 80c541325811b06bfb5bfbf8b4590f9e 11761 devel optional llvm-toolchain-15_15.0.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmN5X74ACgkQ808JdE6f XdlnJRAA0JcXXuE938VJQ0dZkFuWXoEmzPLIqqS7+k/9HxXbVIrnvn7XYxTdyXTg d1cSUDKtMOSIkv7JLq/BtI5L8HzydBveQ5iCy4hiZX3pCy+GRRFjfazvkz/JZ6Ge TOP9ZxPNWNXVOJlSsm9+j9dK7It8MN9ROQDFKWPqucYJQ239lgogbowgZ5jKAqJ5 n85mdMcQ1WB5D2/xnw6AcEAgbL4tseo5+Cd+2600jYikTuxfF+wnL6hLZk0TwS+r dynxWW4h7wVHCR23s8DpBEtU6CBjf7O+9MW2d+UCrGx6Y0dXGG7KKj+n0P+ugeBK tGF80QHZXqCEACqF3jzW5cNm3Ju7L8nedHtvEvcxDRm7wwcMdvjyyu4ZWJBKi2o4
Bug#1023101: marked as done (llvm-15 ftbfs on mips64el)
Your message dated Sat, 19 Nov 2022 23:39:53 + with message-id and subject line Bug#1023101: fixed in llvm-toolchain-15 1:15.0.5-2 has caused the Debian Bug report #1023101, regarding llvm-15 ftbfs on mips64el 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.) -- 1023101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:llvm-toolchain-15 Version: 1:15.0.3-2 Severity: serious Tags: sid bookworm [...] dh_missing: warning: usr/lib/llvm-15/lib/libomptarget.devicertl.a exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting --- End Message --- --- Begin Message --- Source: llvm-toolchain-15 Source-Version: 1:15.0.5-2 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of llvm-toolchain-15, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated llvm-toolchain-15 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: Sat, 19 Nov 2022 23:25:04 +0100 Source: llvm-toolchain-15 Built-For-Profiles: noudeb Architecture: source Version: 1:15.0.5-2 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Gianfranco Costamagna Closes: 1022577 1023101 Changes: llvm-toolchain-15 (1:15.0.5-2) unstable; urgency=medium . [ Gianfranco Costamagna ] * Add libomp target library to mips64el (Closes: #1023101) * Explictly depend on spirv-14 for mips64el, to ease bootstrapping on buildds (this should be dropped once we build a spirv-15 in archive) * Cherry-pick two upstream patches to unblock mesa build on arm* (Closes: #1022577) . [ Sylvestre Ledru ] * store the sccache results in /tmp/buildd/source/sccache-stats.json Checksums-Sha1: 6e077248c7ae68db21011cdb93cb16cf1160e186 7260 llvm-toolchain-15_15.0.5-2.dsc 21c5270182b32d345a07030283a0d1800f4bf3f6 162340 llvm-toolchain-15_15.0.5-2.debian.tar.xz 7c110c62bb9a899aa9988a543a88245e5099a842 11761 llvm-toolchain-15_15.0.5-2_source.buildinfo Checksums-Sha256: 0f09319f9173b6163191ae151a0a6917d2f060038153d36f57dbfeb742386c01 7260 llvm-toolchain-15_15.0.5-2.dsc 72559210a5370a736d2185786a7c88c5c2b53e435e6720d7485eaf98128e35f4 162340 llvm-toolchain-15_15.0.5-2.debian.tar.xz cfa994f21c58a083a41b60d4ddb89006679817ab563770c91952d7b7f4177854 11761 llvm-toolchain-15_15.0.5-2_source.buildinfo Files: 5719b01f10df55842e4eec002ab6ad8e 7260 devel optional llvm-toolchain-15_15.0.5-2.dsc 4c21dc4549c5a46afef1ed881f74dc00 162340 devel optional llvm-toolchain-15_15.0.5-2.debian.tar.xz 80c541325811b06bfb5bfbf8b4590f9e 11761 devel optional llvm-toolchain-15_15.0.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmN5X74ACgkQ808JdE6f XdlnJRAA0JcXXuE938VJQ0dZkFuWXoEmzPLIqqS7+k/9HxXbVIrnvn7XYxTdyXTg d1cSUDKtMOSIkv7JLq/BtI5L8HzydBveQ5iCy4hiZX3pCy+GRRFjfazvkz/JZ6Ge TOP9ZxPNWNXVOJlSsm9+j9dK7It8MN9ROQDFKWPqucYJQ239lgogbowgZ5jKAqJ5 n85mdMcQ1WB5D2/xnw6AcEAgbL4tseo5+Cd+2600jYikTuxfF+wnL6hLZk0TwS+r dynxWW4h7wVHCR23s8DpBEtU6CBjf7O+9MW2d+UCrGx6Y0dXGG7KKj+n0P+ugeBK tGF80QHZXqCEACqF3jzW5cNm3Ju7L8nedHtvEvcxDRm7wwcMdvjyyu4ZWJBKi2o4 hk4Q/MWuoSHmel0IlbkPGxCQ1u9lg3K2gpfyqFVyqv1Y/YXIrcqkF/qa2v7iJGhW dfDxlmzgDsBF5v4wHftTFvO1S7RXFu4eEdGvwlGYfT8weuWBPlJTActY1aFBUYHs ypPK68hERAGWOzqNE6wH6A023nvQ4ftP/y8rnbUcoUaR9DDHSLkQedNRel6pIjtj tlYAj0K68kq6VpHfkQ4r4sbWb7gMSR4qsskrwfqHJGVrTAuRe71pWYWIRpkioeFZ CqpSVEp6f/dbAO5a5etPQv44A5mFjEa6X759QlNtElgxZ3tF4Pg= =kwks -END PGP SIGNATURE End Message ---
Processed: closing 1022523
Processing commands for cont...@bugs.debian.org: > close 1022523 Bug #1022523 [src:lttnganalyses] lttnganalyses: FTBFS: AssertionError: "Error: Cannot open trace: 'utf-8' codec [53 chars]byte" != 'Timerange: [1970-01-01 00:00:01.[1221 chars]3%\n' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1022523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 1019633 ruby-actionmailer Bug #1019633 [src:ruby-invisible-captcha] ruby-invisible-captcha: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp Bug reassigned from package 'src:ruby-invisible-captcha' to 'ruby-actionmailer'. No longer marked as found in versions ruby-invisible-captcha/1.1.0-5. Ignoring request to alter fixed versions of bug #1019633 to the same values previously set > forcemerge 1019610 1019633 Bug #1019610 [ruby-actionmailer] ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError) Bug #1019633 [ruby-actionmailer] ruby-invisible-captcha: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp Added indication that 1019633 affects src:ruby-ahoy-email Marked as found in versions rails/2:6.1.7+dfsg-2. Merged 1019610 1019633 > affects 1019610 src:ruby-invisible-captcha Bug #1019610 [ruby-actionmailer] ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError) Bug #1019633 [ruby-actionmailer] ruby-invisible-captcha: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp Added indication that 1019610 affects src:ruby-invisible-captcha Added indication that 1019633 affects src:ruby-invisible-captcha > thanks Stopping processing here. Please contact me if you need assistance. -- 1019610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019610 1019633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1022343 with 1012496
Processing commands for cont...@bugs.debian.org:
> block 1022343 with 1012496
Bug #1022343 {Done: Abou Al Montacir }
[src:view3dscene] view3dscene: FTBFS: view3dscene.lpr(63,17) Fatal: Can't find
unit CastleCubeMaps used by view3dscene
1022343 was not blocked by any bugs.
1022343 was not blocking any bugs.
Added blocking bug(s) of 1022343: 1012496
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1022343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1023420: marked as done (libvirt FTBFS: missing Build-Depends: mount)
Your message dated Sat, 19 Nov 2022 23:06:08 + with message-id and subject line Bug#1023420: fixed in libvirt 8.9.0-1 has caused the Debian Bug report #1023420, regarding libvirt FTBFS: missing Build-Depends: mount 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.) -- 1023420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libvirt Version: 8.5.0-1 Severity: serious Tags: ftbfs libvirt fails to build from source in unstable on a minimal chroot. mount is no longer essential nor build-essential, so you must add it to Build-Depends explicitly. Helmut --- End Message --- --- Begin Message --- Source: libvirt Source-Version: 8.9.0-1 Done: Andrea Bolognani We believe that the bug you reported is fixed in the latest version of libvirt, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrea Bolognani (supplier of updated libvirt 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, 19 Nov 2022 23:00:34 +0100 Source: libvirt Architecture: source Version: 8.9.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Libvirt Maintainers Changed-By: Andrea Bolognani Closes: 1023420 Changes: libvirt (8.9.0-1) unstable; urgency=medium . * [981c332] New upstream version 8.9.0 * [3f29856] control: Add (build) dependency on mount - Closes: #1023420 Checksums-Sha1: 7039fdad7c6942cc94decdfb1b6346d54b170a26 5349 libvirt_8.9.0-1.dsc e3bcd057f4b78ff25f0afb23d7087f690de76803 8946352 libvirt_8.9.0.orig.tar.xz e8c0a373a242e79c121cacc5dc7dc161c46ddf9d 833 libvirt_8.9.0.orig.tar.xz.asc 5054b58a31d660995f3eed35d2a468aeaa02026f 80924 libvirt_8.9.0-1.debian.tar.xz e4201845d463b204485d92fe4366b0d2047172a1 12555 libvirt_8.9.0-1_source.buildinfo Checksums-Sha256: ac8a3e04edcade14037870a0c5a93400a0137aa017c207fb0a51b7d14a3949f4 5349 libvirt_8.9.0-1.dsc c213575aaa636d41a6011ef59e5f088643b721e1ab1ca3ea05c176c05e9579a2 8946352 libvirt_8.9.0.orig.tar.xz 0e37f3e8b8c6b3a6f682e367210b2abcdf66ae3ebbfd14601611b37a744d13bd 833 libvirt_8.9.0.orig.tar.xz.asc 96d4787a90944cccb52ec97a61fba76fc3786fc6c4f65fdb76372e7c1f3cb370 80924 libvirt_8.9.0-1.debian.tar.xz 0a071085e24469ded17126ed4b85e374ae87e27daf6dcb2773ed229693b7c9ec 12555 libvirt_8.9.0-1_source.buildinfo Files: 33e407914100e1bf3debb300db22448b 5349 libs optional libvirt_8.9.0-1.dsc a98a3044344c3f8c3b7f887436102b8f 8946352 libs optional libvirt_8.9.0.orig.tar.xz cdcc6dd30e02359865fbe00ed799c6ea 833 libs optional libvirt_8.9.0.orig.tar.xz.asc 7cb6e4309d5af9b536d0664e88353d86 80924 libs optional libvirt_8.9.0-1.debian.tar.xz 08303ac2fd02fa434375a98510a2c115 12555 libs optional libvirt_8.9.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEO48t9niVypx3EjLf954fxUKFg6wFAmN5XCUACgkQ954fxUKF g6zWtBAA6lTA6ho8xnmypXEeAp1Hril4M2BpnFKiEQd0b67W1x9qB8+/eVazfJ60 j83GoOv0YHa++9n6Vbo8r2YVrPJXcG8X+odEZQONFpzixw1xj4xzMjY3Ys/+r97R iSkyidwgbXVdUgK8BWYgWywfuVBggoDt5ykd/KN6jZUItDGsp6HW7va6OmkUfEom 8+bJVEJEo8or5F43DhbjXTTm6+c5kK9RLC2T5ZlIz/YIZlyZ4DJTcKNubjQfAphI Cr/Lk2ut912UPdeTHsot+1g74+7rRfx9swewB14Vyi/Gd1ZTvTzWndDg1sIP5Amv k0dBcebWfg7+dBhKwYAJbr+eKnC2xYPweyL86vcAnynoWKCPzAMDi3siCWpAxaHD eJ6okn07X9PHme9B6KRpUQEXYSdt2GS+vxDvNaSLKCO7Q594t0HkuaF2XR7n+xzE 1yluQLCC9BxG/foeid7eZTHXuKSbcxGexnMAnAg0iB5uIH4bQk8Xd55cyPVL883b w/HU5yLFnhQ+sQ3qx+FkJsGvjHlGfoJRbrNyhgGKtSpqpCAvJwncBfX8+f8ZTu3y L+ohFSAsaU8ZDeyAn6/kmdz/CVdIRttzSsF5H4jT1an4TgD7oghIaJRG1FnrcGBu UH8f0pMyABQSI/3f5hqJh+DBWFYhfC/wGtjqgBxGQLqLgVuYlx0= =jVaZ -END PGP SIGNATURE End Message ---
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 1022375 llvm-14-dev
Bug #1022375 [src:halide] halide: FTBFS: make[2]: *** [debian/rules:97:
perform_stage_build] Error 2
Bug reassigned from package 'src:halide' to 'llvm-14-dev'.
No longer marked as found in versions halide/14.0.0-2.
Ignoring request to alter fixed versions of bug #1022375 to the same values
previously set
> forcemerge 1021857 1022375
Bug #1021857 {Done: Sylvestre Ledru } [llvm-14-dev]
llvm-14-dev: CMake Error in LLVMExports.cmake: The imported target "sancov"
references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.
Bug #1022334 {Done: Sylvestre Ledru } [llvm-14-dev]
qtcreator: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_configure]
Error 2
Bug #1022337 {Done: Sylvestre Ledru } [llvm-14-dev]
qt6-tools: FTBFS: The imported target "sancov" references the file
"/usr/lib/llvm-14/bin/sancov" but this file does not exist.
Bug #1022349 {Done: Sylvestre Ledru } [llvm-14-dev] iwyu:
FTBFS: The imported target "sancov" references the file
"/usr/lib/llvm-14/bin/sancov" but this file does not exist
Bug #1022351 {Done: Sylvestre Ledru } [llvm-14-dev]
bpfcc: FTBFS: make[1]: *** [debian/rules:35: override_dh_auto_configure] Error 2
Bug #1022353 {Done: Sylvestre Ledru } [llvm-14-dev]
doxygen: FTBFS: The imported target "sancov" references the file
"/usr/lib/llvm-14/bin/sancov" but this file does not exist
Bug #1022366 {Done: Sylvestre Ledru } [llvm-14-dev]
irony-mode: FTBFS: make: *** [debian/rules:8: binary] Error 2
Bug #1022381 {Done: Sylvestre Ledru } [llvm-14-dev]
cvise: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 2
Bug #1022409 {Done: Sylvestre Ledru } [llvm-14-dev] ccls:
FTBFS: make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2
Bug #1022414 {Done: Sylvestre Ledru } [llvm-14-dev]
bpftrace: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_configure]
Error 2
Bug #1022337 {Done: Sylvestre Ledru } [llvm-14-dev]
qt6-tools: FTBFS: The imported target "sancov" references the file
"/usr/lib/llvm-14/bin/sancov" but this file does not exist.
Removed indication that 1022337 affects src:cvise, src:qt6-tools, src:iwyu,
src:doxygen, irony-mode, ccls, src:qtcreator, and src:bpfcc
Added indication that 1022337 affects
irony-mode,ccls,src:iwyu,src:doxygen,src:qt6-tools,src:qtcreator,src:bpfcc,src:cvise
Removed indication that 1021857 affects src:qt6-tools, src:cvise, ccls,
src:qtcreator, src:iwyu, irony-mode, src:doxygen, and src:bpfcc
Added indication that 1021857 affects
irony-mode,ccls,src:iwyu,src:doxygen,src:qt6-tools,src:qtcreator,src:bpfcc,src:cvise
Removed indication that 1022334 affects src:bpfcc, src:qtcreator, ccls,
src:doxygen, src:iwyu, irony-mode, src:qt6-tools, and src:cvise
Added indication that 1022334 affects
irony-mode,ccls,src:iwyu,src:doxygen,src:qt6-tools,src:qtcreator,src:bpfcc,src:cvise
Removed indication that 1022349 affects src:bpfcc, src:qtcreator, ccls,
src:iwyu, irony-mode, src:doxygen, src:cvise, and src:qt6-tools
Added indication that 1022349 affects
irony-mode,ccls,src:iwyu,src:doxygen,src:qt6-tools,src:qtcreator,src:bpfcc,src:cvise
Removed indication that 1022351 affects src:cvise, src:qt6-tools,
src:qtcreator, ccls, src:iwyu, irony-mode, src:doxygen, and src:bpfcc
Added indication that 1022351 affects
irony-mode,ccls,src:iwyu,src:doxygen,src:qt6-tools,src:qtcreator,src:bpfcc,src:cvise
Removed indication that 1022353 affects src:cvise, src:qt6-tools,
src:qtcreator, ccls, src:doxygen, src:iwyu, irony-mode, and src:bpfcc
Added indication that 1022353 affects
irony-mode,ccls,src:iwyu,src:doxygen,src:qt6-tools,src:qtcreator,src:bpfcc,src:cvise
Removed indication that 1022366 affects src:bpfcc, src:doxygen, irony-mode,
src:iwyu, ccls, src:qtcreator, src:qt6-tools, and src:cvise
Added indication that 1022366 affects
irony-mode,ccls,src:iwyu,src:doxygen,src:qt6-tools,src:qtcreator,src:bpfcc,src:cvise
Removed indication that 1022381 affects src:qt6-tools, src:cvise, src:iwyu,
src:doxygen, irony-mode, ccls, src:qtcreator, and src:bpfcc
Added indication that 1022381 affects
irony-mode,ccls,src:iwyu,src:doxygen,src:qt6-tools,src:qtcreator,src:bpfcc,src:cvise
Removed indication that 1022409 affects src:cvise, src:qt6-tools, src:bpfcc,
src:iwyu, src:doxygen, irony-mode, src:qtcreator, and ccls
Added indication that 1022409 affects
irony-mode,ccls,src:iwyu,src:doxygen,src:qt6-tools,src:qtcreator,src:bpfcc,src:cvise
Removed indication that 1022414 affects src:qtcreator, ccls, src:doxygen,
src:iwyu, irony-mode, src:bpfcc, src:qt6-tools, and src:cvise
Added indication that 1022414 affects
irony-mode,ccls,src:iwyu,src:doxygen,src:qt6-tools,src:qtcreator,src:bpfcc,src:cvise
Bug #1022375 [llvm-14-dev] halide: FTBFS: make[2]: *** [debian/rules:97:
perform_stage_build] Error 2
Marked Bug as done
Added indication that 1022375 affects
irony-mode,ccls,src:iwyu,src:doxygen,src:qt6-tools,src:qtcreator,src:bpfcc,src:cvise
Marked
Bug#1022551: llvm-15's cmake now requires clang-tools-15, clang-tidy-15, clangd-15, even if unused
control: fixed -1 1:15.0.5-1 control: close -1 On Mon, 24 Oct 2022 10:13:01 +0200 Matthias Klose wrote: Control: reopen -1 Control: found -1 15.0.3-1 > it is fixed in experimental no, it is not. As said on IRC, there's a reproducer to build cvise 2.6.0-1 without the extra dependencies clang-tools-15, clang-tidy-15, clangd-15 and the build fails. I downloaded cvise, installed build-deps in a sid chroot apt remove clang-tools-15 clang-tidy-15 clangd-15 dpkg-buildpackage -d dh_auto_configure -- \ -DCMAKE_PREFIX_PATH=/usr/lib/llvm-15 \ -DCLANG_FORMAT=clang-format-15 \ -DCMAKE_INSTALL_LIBEXECDIR=lib cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_PREFIX_PATH=/usr/lib/llvm-15 -DCLANG_FORMAT=clang-format-15 -DCMAKE_INSTALL_LIBEXECDIR=lib .. -- The C compiler identification is GNU 12.2.0 -- The CXX compiler identification is GNU 12.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Performing Test HAVE_FFI_CALL -- Performing Test HAVE_FFI_CALL - Success -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so -- Performing Test Terminfo_LINKABLE -- Performing Test Terminfo_LINKABLE - Success -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.14") -- Found LLVM 15.0.5 -- Using LLVMConfig.cmake in /usr/lib/llvm-15/cmake -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) -- Using ClangConfig.cmake in /usr/lib/llvm-15/lib/cmake/clang -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.10.8", minimum required is "3.6") -- Found FLEX: /usr/bin/flex (found version "2.6.4") -- Looking for dlfcn.h -- Looking for dlfcn.h - found -- Looking for inttypes.h -- Looking for inttypes.h - found -- Looking for memory.h -- Looking for memory.h - found -- Looking for stdint.h -- Looking for stdint.h - found -- Looking for stdlib.h -- Looking for stdlib.h - found -- Looking for strings.h -- Looking for strings.h - found -- Looking for string.h -- Looking for string.h - found -- Looking for sys/stat.h -- Looking for sys/stat.h - found -- Looking for sys/types.h -- Looking for sys/types.h - found -- Looking for unistd.h -- Looking for unistd.h - found -- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG -- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG - Success -- Using clang-format in /usr/bin/clang-format-15 -- Configuring done -- Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY FETCHCONTENT_FULLY_DISCONNECTED [...] cd /cvise-2.6.0/obj-x86_64-linux-gnu/clang_delta && /usr/bin/c++ -DHAVE_CONFIG_H -I/cvise-2.6.0/obj-x86_64-linux-gnu -I/cvise-2.6.0/clang_delta -I/usr/lib/llvm-15/include -g -O2 -ffile-prefix-map=/cvise-2.6.0=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -fno-rtti -fno-strict-aliasing -Wall -Wextra -Wno-unused-parameter -Werror -Wno-error=maybe-uninitialized -fvisibility-inlines-hidden -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -MD -MT clang_delta/CMakeFiles/clang_delta.dir/ExpressionDetector.cpp.o -MF CMakeFiles/clang_delta.dir/ExpressionDetector.cpp.o.d -o CMakeFiles/clang_delta.dir/ExpressionDetector.cpp.o -c /cvise-2.6.0/clang_delta/ExpressionDetector.cpp [ 13%] Building CXX object clang_delta/CMakeFiles/clang_delta.dir/InstantiateTemplateParam.cpp.o cd /cvise-2.6.0/obj-x86_64-linux-gnu/clang_delta && /usr/bin/c++ -DHAVE_CONFIG_H -I/cvise-2.6.0/obj-x86_64-linux-gnu -I/cvise-2.6.0/clang_delta -I/usr/lib/llvm-15/include -g -O2 -ffile-prefix-map=/cvise-2.6.0=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -fno-rtti -fno-strict-aliasing -Wall -Wextra -Wno-unused-parameter -Werror -Wno-error=maybe-uninitialized -fvisibility-inlines-hidden -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -MD -MT clang_delta/CMakeFiles/clang_delta.dir/InstantiateTemplateParam.cpp.o -MF
Processed: Re: llvm-15's cmake now requires clang-tools-15, clang-tidy-15, clangd-15, even if unused
Processing control commands: > fixed -1 1:15.0.5-1 Bug #1022551 [llvm-15-dev] llvm-15's cmake now requires clang-tools-15, clang-tidy-15, clangd-15, even if unused Marked as fixed in versions llvm-toolchain-15/1:15.0.5-1. > close -1 Bug #1022551 [llvm-15-dev] llvm-15's cmake now requires clang-tools-15, clang-tidy-15, clangd-15, even if unused Marked Bug as done -- 1022551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: netpanzer: diff for NMU version 0.8.7+ds-4.1
Processing control commands: > tags 1002964 + pending Bug #1002964 [src:netpanzer] netpanzer: FTBFS with SCons 4.2.0+ Bug #1022356 [src:netpanzer] netpanzer: FTBFS: AttributeError: 'SConsEnvironment' object has no attribute 'has_key': Added tag(s) pending. Added tag(s) pending. -- 1002964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002964 1022356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002964: netpanzer: diff for NMU version 0.8.7+ds-4.1
Control: tags 1002964 + pending
Dear maintainer,
I've prepared an NMU for netpanzer (versioned as 0.8.7+ds-4.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru netpanzer-0.8.7+ds/debian/changelog netpanzer-0.8.7+ds/debian/changelog
--- netpanzer-0.8.7+ds/debian/changelog 2021-10-22 00:16:42.0 +0300
+++ netpanzer-0.8.7+ds/debian/changelog 2022-11-20 00:32:24.0 +0200
@@ -1,3 +1,11 @@
+netpanzer (0.8.7+ds-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch from László Böszörményi to fix FTBFS with SCons >= 4.2.0.
+(Closes: #1002964)
+
+ -- Adrian Bunk Sun, 20 Nov 2022 00:32:24 +0200
+
netpanzer (0.8.7+ds-4) unstable; urgency=medium
* Team upload.
diff -Nru netpanzer-0.8.7+ds/debian/patches/netpanzer_SCons_fix.patch netpanzer-0.8.7+ds/debian/patches/netpanzer_SCons_fix.patch
--- netpanzer-0.8.7+ds/debian/patches/netpanzer_SCons_fix.patch 1970-01-01 02:00:00.0 +0200
+++ netpanzer-0.8.7+ds/debian/patches/netpanzer_SCons_fix.patch 2022-11-20 00:31:50.0 +0200
@@ -0,0 +1,19 @@
+Description: SCons 4.2.0 no longer has env.has_key()
+ Check env as an array.
+Author: Laszlo Boszormenyi (GCS)
+Forwarded: no
+Last-Update: 2022-01-01
+
+---
+
+--- netpanzer-0.8.7+ds.orig/SConstruct
netpanzer-0.8.7+ds/SConstruct
+@@ -237,7 +237,7 @@ npdirs = """
+ """
+
+ env.Append( NPSOURCES = globSources(env, 'src/NetPanzer', npdirs, "*.cpp") )
+-if env.has_key('WINICON'):
++if 'WINICON' in env:
+ env.Append( NPSOURCES = env['WINICON'] )
+
+ env.Prepend( LIBS = ['np2d','lua5.1','npnetwork','nplibs','physfs'] )
diff -Nru netpanzer-0.8.7+ds/debian/patches/series netpanzer-0.8.7+ds/debian/patches/series
--- netpanzer-0.8.7+ds/debian/patches/series 2021-10-22 00:16:42.0 +0300
+++ netpanzer-0.8.7+ds/debian/patches/series 2022-11-20 00:32:20.0 +0200
@@ -6,3 +6,4 @@
reproducible-build.patch
scons.patch
gcc11.patch
+netpanzer_SCons_fix.patch
Processed: bug 1022369 is forwarded to https://github.com/gpg-rs/gpgme/commit/45297384cf5461307804b82ddcca78af901c8761
Processing commands for cont...@bugs.debian.org: > forwarded 1022369 > https://github.com/gpg-rs/gpgme/commit/45297384cf5461307804b82ddcca78af901c8761 Bug #1022369 [src:rust-gpgme] rust-gpgme: FTBFS: sh: 1: gpg-error-config: not found Set Bug forwarded-to-address to 'https://github.com/gpg-rs/gpgme/commit/45297384cf5461307804b82ddcca78af901c8761'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1022356 1002964
Processing commands for cont...@bugs.debian.org: > forcemerge 1022356 1002964 Bug #1022356 [src:netpanzer] netpanzer: FTBFS: AttributeError: 'SConsEnvironment' object has no attribute 'has_key': Bug #1022356 [src:netpanzer] netpanzer: FTBFS: AttributeError: 'SConsEnvironment' object has no attribute 'has_key': Added tag(s) patch. Bug #1002964 [src:netpanzer] netpanzer: FTBFS with SCons 4.2.0+ Severity set to 'serious' from 'important' Added tag(s) sid, bookworm, and ftbfs. Merged 1002964 1022356 > thanks Stopping processing here. Please contact me if you need assistance. -- 1002964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002964 1022356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024435: dracut-core: missing Breaks+Replaces: dracut-network (<< 057+157-2)
On 19/11/2022 21.58, Thomas Lange wrote: On Sat, 19 Nov 2022 13:29:52 +0100, Andreas Beckmann said: >> From the attached log (scroll to the bottom...): > Preparing to unpack .../dracut-core_057+157-2_amd64.deb ... > Unpacking dracut-core (057+157-2) over (056-3) ... > dpkg: error processing archive /var/cache/apt/archives/dracut-core_057+157-2_amd64.deb (--unpack): >trying to overwrite '/usr/lib/dracut/modules.d/95virtfs/module-setup.sh', which is also in package dracut-network 056-3 > dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) > Errors were encountered while processing: >/var/cache/apt/archives/dracut-core_057+157-2_amd64.deb I can understand the problem (and the fix to add the breaks relation), but I wonder why I should define a replaces to dracut-network? dracut-core does not replace dracut-network. It only breaks dracut-network (<< 057+157-2). Can you please tell me what correct way is to fix it. Some files moved from -network to -core (the files that were in both packages in yesterdays bug). In order to properly handle that on upgrades, you need both versioned Breaks and Replaces. The Replaces s.t. dpkg will move file ownership if -core gets unpacked first, the Breaks to prevent partial upgrades (and subsequent partial removals or downgrades, that's where the fun usually starts) of the packages involved in the file move. Andreas
Processed: Re: Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)
Processing control commands: > reassign -1 ruby-actionmailer 2:6.1.7+dfsg-2 Bug #1019610 [src:ruby-ahoy-email] ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError) Bug reassigned from package 'src:ruby-ahoy-email' to 'ruby-actionmailer'. No longer marked as found in versions ruby-ahoy-email/1.1.1-2. Ignoring request to alter fixed versions of bug #1019610 to the same values previously set Bug #1019610 [ruby-actionmailer] ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError) Marked as found in versions rails/2:6.1.7+dfsg-2. > affects -1 src:ruby-ahoy-email Bug #1019610 [ruby-actionmailer] ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError) Added indication that 1019610 affects src:ruby-ahoy-email -- 1019610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)
Control: reassign -1 ruby-actionmailer 2:6.1.7+dfsg-2 Control: affects -1 src:ruby-ahoy-email On Sun, Nov 06, 2022 at 08:31:39PM +0200, Adrian Bunk wrote: > On Fri, Oct 07, 2022 at 02:16:35PM -0300, Antonio Terceiro wrote: > >... > > But nothing in ruby-ahoy-email codebase uses net/smtp explicitly, so > > this is a bit weird. > >... > > $ cat > /usr/share/rubygems-integration/all/gems/actionmailer-6.1.7/lib/action_mailer/mail_with_error_handling.rb > # frozen_string_literal: true > > begin > require "mail" > rescue LoadError => error > if error.message.match?(/net\/smtp/) > $stderr.puts "You don't have net-smtp installed in your application. > Please add it to your Gemfile and run bundle install" > raise > end > end > $ > > > There is also something that might be related in > https://sources.debian.org/src/rails/2%3A6.1.7%2Bdfsg-2/Gemfile/#L140 > > Is there a bug in rails? >... I am reassigning this to rails since it is likely that the problem is there. cu Adrian
Bug#1020064: marked as done (tcsh: FTBFS: | ./conftest.c:20: undefined reference to `crypt')
Your message dated Sat, 19 Nov 2022 22:10:32 +
with message-id
and subject line Bug#1020064: fixed in tcsh 6.21.00-2
has caused the Debian Bug report #1020064,
regarding tcsh: FTBFS: | ./conftest.c:20: undefined reference to `crypt'
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.)
--
1020064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tcsh
Version: 6.21.00-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> {\
> echo '# Signature of the current package.';\
> echo 'm4_define([AT_PACKAGE_NAME], [tcsh])'; \
> echo 'm4_define([AT_PACKAGE_TARNAME], [tcsh])'; \
> echo 'm4_define([AT_PACKAGE_VERSION], [6.21.00])'; \
> echo 'm4_define([AT_PACKAGE_STRING],[tcsh 6.21.00])'; \
> echo 'm4_define([AT_PACKAGE_BUGREPORT], [https://bugs.astron.com/])'; \
> } >./tests/package.m4
> autom4te --language=autotest -I ./tests \
> ./tests/testsuite.at -o tests/testsuite.tmp
> mv tests/testsuite.tmp tests/testsuite
> /bin/sh ./tests/testsuite
> ## ##
> ## tcsh 6.21.00 test suite. ##
> ## ##
> 1: beepcmd skipped (aliases.at:3)
> 2: cwdcmd ok
> 3: jobcmd skipped (aliases.at:19)
> 4: helpcommand skipped (aliases.at:20)
> 5: periodicskipped (aliases.at:21)
> 6: precmd skipped (aliases.at:22)
> 7: postcmd ok
> 8: shell ok
> 9: -b ok
> 10: -c ok
> 11: -d skipped (arguments.at:34)
> 12: -e ok
> 13: -f skipped (arguments.at:46)
> 14: -i ok
> 15: -l skipped (arguments.at:61)
> 16: -m skipped (arguments.at:65)
> 17: -q skipped (arguments.at:71)
> 18: -s ok
> 19: -t ok
> 20: -v ok
> 21: -x ok
> 22: -V skipped
> (arguments.at:126)
> 23: -X skipped
> (arguments.at:127)
> 24: --help skipped
> (arguments.at:130)
> 25: --version skipped
> (arguments.at:131)
> 26: invalid option ok
> 27: non-option argumentsok
> 28: % skipped (commands.at:3)
> 29: : ok
> 30: @ ok
> 31: alias ok
> 32: alloc skipped (commands.at:80)
> 33: bg skipped (commands.at:81)
> 34: bindkey skipped (commands.at:82)
> 35: break ok
> 36: builtinsskipped (commands.at:133)
> 37: bye skipped (commands.at:134)
> 38: cd ok
> 39: completeok
> 40: continueok
> 41: dirsok
> 42: echook
> 43: echotc skipped (commands.at:348)
> 44: evalok
> 45: execok
> 46: exit
Bug#999754: marked as done (tcsh: character class expansion is badly broken)
Your message dated Sat, 19 Nov 2022 22:10:32 + with message-id and subject line Bug#999754: fixed in tcsh 6.21.00-2 has caused the Debian Bug report #999754, regarding tcsh: character class expansion is badly broken 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.) -- 999754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tcsh Version: 6.21.00-1.1 Severity: grave Tags: newcomer Justification: causes non-serious data loss Dear Maintainer, tcsh does not respect character classes. Minimal example: $ mkdir a $ touch a/a a/B $ echo a/[a-z] a/a a/B I expect the result to simply be 'a/a' since 'B' is not in [a-z]. The behavior generalizes to character classes in wildcards - it is not just about the trivial one-character filename example seen here. This is in locale en_US.UTF-8, but switching to locale "C" has the same behavior. This behavior can result in data loss with e.g. 'rm [a-z]*' removing unexpected files, and can also result in operating on the wrong files, so I have tentatively classified it 'grave'. tcsh as packaged is unusable for my purposes. I have verified that tcsh built from the current upstream (version 6.23.00) with $ git clone g...@github.com:tcsh-org/tcsh.git $ cd tcsh $ configure && make Does NOT suffer this behavior, while tcsh built from the Debian source package with $ apt-get --build source tcsh DOES suffer this behavior. The 6.23.00 built from upstream has the same $version string options as the Debian 6.21.00 except for "nd" (NODOT). I attempted to build from the upstream repository at version 6.21.00 but could not successfully build after 'configure', so I cannot tell if this is a bug introduced by the Debian-specific changes, or a bug in the upstream 6.21.00. The differences between the Debian source package with patches applied vs. upstream 6.21.00 source are smallish and don't obviously implicate character classes but that proves nothing. Suggested resolutionn is to update the buster package to tcsh 6.23.00. I believe this will also result in elimination of a large number of warning messages during the build of form /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~ -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tcsh depends on: ii libc6 2.31-13+deb11u2 ii libcrypt1 1:4.4.18-4 ii libtinfo6 6.2+20201114-2 tcsh recommends no packages. tcsh suggests no packages. --- End Message --- --- Begin Message --- Source: tcsh Source-Version: 6.21.00-2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of tcsh, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated tcsh 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, 19 Nov 2022 23:13:18 +0200 Source: tcsh Architecture: source Version: 6.21.00-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adrian Bunk Closes: 999754 1020064 Changes: tcsh (6.21.00-2) unstable; urgency=medium . * QA upload. * Set Maintainer to Debian QA Group. (see #1019858) * Add upstream fix for FTBFS with bash 5.2. (Closes: #1020064) * Add upstream fix for range comparison bug. (Closes: #999754) Checksums-Sha1: 4ae67768a0c22ca78b7045f1f7e0a15eee003082 1802 tcsh_6.21.00-2.dsc 1f6fd47ee6e525e998068127a578234682def87c 24980 tcsh_6.21.00-2.diff.gz
Bug#1023420: marked as pending in libvirt
Control: tag -1 pending Hello, Bug #1023420 in libvirt 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/libvirt-team/libvirt/-/commit/3f2985672fd96f945e71373e477ca92b3ae2f86c control: Add (build) dependency on mount mount is no longer essential, so we need to explicitly depend on it. We should be able to drop the build dependency later, after patching out the check upstream, but the runtime dependency is here to stay. Closes: #1023420 (this message was generated automatically) -- Greetings https://bugs.debian.org/1023420
Processed: Bug#1023420 marked as pending in libvirt
Processing control commands: > tag -1 pending Bug #1023420 [src:libvirt] libvirt FTBFS: missing Build-Depends: mount Added tag(s) pending. -- 1023420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022287: poldi: diff for NMU version 0.4.2+git20161115.553060d-1.1
Control: tags 1022287 + patch Control: tags 1022287 + pending Dear maintainer, I've prepared an NMU for poldi (versioned as 0.4.2+git20161115.553060d-1.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru poldi-0.4.2+git20161115.553060d/debian/changelog poldi-0.4.2+git20161115.553060d/debian/changelog --- poldi-0.4.2+git20161115.553060d/debian/changelog 2016-11-11 09:07:45.0 +0200 +++ poldi-0.4.2+git20161115.553060d/debian/changelog 2022-11-19 23:57:43.0 +0200 @@ -1,3 +1,11 @@ +poldi (0.4.2+git20161115.553060d-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Delete m4/gpg-error.m4 to get the latest version from +libgpg-error-dev instead. (Closes: #1022287) + + -- Adrian Bunk Sat, 19 Nov 2022 23:57:43 +0200 + poldi (0.4.2+git20161115.553060d-1) unstable; urgency=medium * New upstream. diff -Nru poldi-0.4.2+git20161115.553060d/debian/clean poldi-0.4.2+git20161115.553060d/debian/clean --- poldi-0.4.2+git20161115.553060d/debian/clean 1970-01-01 02:00:00.0 +0200 +++ poldi-0.4.2+git20161115.553060d/debian/clean 2022-11-19 23:57:36.0 +0200 @@ -0,0 +1 @@ +m4/gpg-error.m4
Processed: poldi: diff for NMU version 0.4.2+git20161115.553060d-1.1
Processing control commands: > tags 1022287 + patch Bug #1022287 [src:poldi] poldi: FTBFS: configure: error: You need libgpg-error to build this program. Added tag(s) patch. > tags 1022287 + pending Bug #1022287 [src:poldi] poldi: FTBFS: configure: error: You need libgpg-error to build this program. Added tag(s) pending. -- 1022287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022283: marked as done (python-wikkid: FTBFS: ModuleNotFoundError: No module named 'breezy.merge3')
Your message dated Sat, 19 Nov 2022 21:22:02 + with message-id and subject line Bug#1022283: fixed in python-wikkid 0.4-1 has caused the Debian Bug report #1022283, regarding python-wikkid: FTBFS: ModuleNotFoundError: No module named 'breezy.merge3' 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.) -- 1022283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-wikkid Version: 0+git20211221.1.b129e3b-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.10 setup.py config > /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:264: > UserWarning: Unknown distribution option: 'test_requires' > warnings.warn(msg) > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:264: > UserWarning: Unknown distribution option: 'test_requires' > warnings.warn(msg) > running build > running build_py > creating /<>/.pybuild/cpython3_3.10/build/wikkid > copying wikkid/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid > copying wikkid/fileutils.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid > copying wikkid/app.py -> /<>/.pybuild/cpython3_3.10/build/wikkid > copying wikkid/dispatcher.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid > copying wikkid/context.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid > creating /<>/.pybuild/cpython3_3.10/build/plugin > copying plugin/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/plugin > copying plugin/commands.py -> > /<>/.pybuild/cpython3_3.10/build/plugin > creating /<>/.pybuild/cpython3_3.10/build/wikkid/formatter > copying wikkid/formatter/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/formatter > copying wikkid/formatter/registry.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/formatter > copying wikkid/formatter/pygmentsformatter.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/formatter > copying wikkid/formatter/textileformatter.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/formatter > copying wikkid/formatter/markdownformatter.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/formatter > copying wikkid/formatter/restformatter.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/formatter > creating /<>/.pybuild/cpython3_3.10/build/wikkid/skin > copying wikkid/skin/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/skin > copying wikkid/skin/loader.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/skin > creating /<>/.pybuild/cpython3_3.10/build/wikkid/interface > copying wikkid/interface/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/interface > copying wikkid/interface/resource.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/interface > copying wikkid/interface/filestore.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/interface > copying wikkid/interface/user.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/interface > copying wikkid/interface/formatter.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/interface > creating /<>/.pybuild/cpython3_3.10/build/wikkid/filestore > copying wikkid/filestore/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/filestore > copying wikkid/filestore/bzr.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/filestore > copying wikkid/filestore/basefile.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/filestore > copying wikkid/filestore/git.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/filestore > copying wikkid/filestore/volatile.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/filestore > creating /<>/.pybuild/cpython3_3.10/build/wikkid/model > copying wikkid/model/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/model > copying wikkid/model/sourcetext.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/model > copying wikkid/model/root.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/model > copying wikkid/model/textfile.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/model > copying wikkid/model/binary.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/model > copying wikkid/model/wikitext.py -> > /<>/.pybuild/cpython3_3.10/build/wikkid/model
Processed: tagging 1008502
Processing commands for cont...@bugs.debian.org: > tags 1008502 + bullseye Bug #1008502 [vdirsyncer] vdirsyncer: Unknown error occured: unmatched ')' Added tag(s) bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024457: "apt changelog" fails to display the complete changelog
Control: severity -1 important On Sat, Nov 19, 2022 at 10:42:01PM +0200, Adrian Bunk wrote: > Severity: serious Well, no. You haven't provided a reason and I fail to find an obvious one as apt's key functionality is hardly effected by a not (by default) working changelog sub-command… could Debian release with this "bug" unfixed? Certainly, given that it might/likely fails for other reasons like the online repository not actually providing changelogs. That said, severity hardly makes a difference for us anyhow as somehow assigning severity doesn't magically assign free time as well (at "best" higher values have a negative effect), so grave or wishlist doesn't really matter, but I suppose important is closer to your hope of getting that fixed before the release some way. > debhelper recently started removing older changelog entries from > binary packages, but the way to get them with apt does not work: https://salsa.debian.org/apt-team/apt/-/merge_requests/261 Best regards David Kalnischkies signature.asc Description: PGP signature
Processed: Re: Bug#1024457: "apt changelog" fails to display the complete changelog
Processing control commands: > severity -1 important Bug #1024457 [apt] "apt changelog" fails to display the complete changelog Severity set to 'important' from 'serious' -- 1024457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024462: pki-base-java depends on openjdk-11-jre-headless that will not be in bookworm
Package: pki-base-java Version: 11.0.3-4 Severity: serious Please update the dependency to default-jre-headless.
Bug#1022283: marked as pending in python-wikkid
Control: tag -1 pending Hello, Bug #1022283 in python-wikkid 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/wikkid/-/commit/81ff821dcf412ca065570df47a8ba38607690408 Switches to merge3. Closes: #1022283 (this message was generated automatically) -- Greetings https://bugs.debian.org/1022283
Processed: Bug#1022283 marked as pending in python-wikkid
Processing control commands: > tag -1 pending Bug #1022283 [src:python-wikkid] python-wikkid: FTBFS: ModuleNotFoundError: No module named 'breezy.merge3' Added tag(s) pending. -- 1022283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024435: dracut-core: missing Breaks+Replaces: dracut-network (<< 057+157-2)
> On Sat, 19 Nov 2022 13:29:52 +0100, Andreas Beckmann > said: >> From the attached log (scroll to the bottom...): > Preparing to unpack .../dracut-core_057+157-2_amd64.deb ... > Unpacking dracut-core (057+157-2) over (056-3) ... > dpkg: error processing archive /var/cache/apt/archives/dracut-core_057+157-2_amd64.deb (--unpack): >trying to overwrite '/usr/lib/dracut/modules.d/95virtfs/module-setup.sh', which is also in package dracut-network 056-3 > dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) > Errors were encountered while processing: >/var/cache/apt/archives/dracut-core_057+157-2_amd64.deb I can understand the problem (and the fix to add the breaks relation), but I wonder why I should define a replaces to dracut-network? dracut-core does not replace dracut-network. It only breaks dracut-network (<< 057+157-2). Can you please tell me what correct way is to fix it. -- regards Thomas
Bug#1024459: uwsgi: Build and runtime dependencies on openjdk-11 that will not be in bookworm
Source: uwsgi Version: 2.0.20-4 Severity: serious openjdk-11 (and therefore uwsgi) is already on the autoremoval list and will not be in bookworm (only openjdk-17 will be in bookworm). The uwsgi-plugin-*-openjdk-11 packages need removing to uwsgi-plugin-*-openjdk-17 (or removal). I also wonder whether uwsgi-plugin-*-openjdk might be an option, with a build dependency on default-jdk and a runtime dependency that is generated at build time (see the jcc package for an example). Something similar is already done for the uwsgi-plugin*-python3 packages that do not have version specific names, and the same would also make sense for uwsgi-plugin-rack-ruby3.0.
Bug#1024400: net-luminis-build-plugin: broken maintainer field
Hi Adam! On Fri, Nov 18, 2022 at 07:49:20PM +, Adam D. Barratt wrote: [...] > > I'm assuming the second line is a failed attempt at removing the > Uploaders field, as mentioned in the changelog, which originally read: > > Uploaders: Mathieu Malaterre > > Amongst other things, this breaks the scripts in the BTS which generate > lists of RC bugs in unstable and testing for britney, meaning that > those lists have not been updated since Monday morning. > First, I apologize for what happened. I was working on changing the Maintainer field of orphaned packages to QA Group. I started the work by looking at page [1] to get the list of packages. I did the change for ~166 packages. In this list, on 27 packages, I removed the Uploaders field. I checked every package and this mistake occurred on this package and the packages statcvs and closure-compiler, which were already fixed (thanks Jochen). [1] https://qa.debian.org/orphaned.html Again, very sorry for that. Best Regards, mt signature.asc Description: PGP signature
Bug#1009482: sphinxcontrib-autoprogram: diff for NMU version 0.1.7-2.1
Control: tags 1009482 + pending
Dear maintainer,
I've prepared an NMU for sphinxcontrib-autoprogram (versioned as 0.1.7-2.1)
and uploaded it to DELAYED/15. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru sphinxcontrib-autoprogram-0.1.7/debian/changelog sphinxcontrib-autoprogram-0.1.7/debian/changelog
--- sphinxcontrib-autoprogram-0.1.7/debian/changelog 2022-01-03 15:29:42.0 +0200
+++ sphinxcontrib-autoprogram-0.1.7/debian/changelog 2022-11-19 22:29:45.0 +0200
@@ -1,3 +1,11 @@
+sphinxcontrib-autoprogram (0.1.7-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add proposed fix for FTBFS with Python >= 3.10.
+(Closes: #1009482)
+
+ -- Adrian Bunk Sat, 19 Nov 2022 22:29:45 +0200
+
sphinxcontrib-autoprogram (0.1.7-2) unstable; urgency=medium
* Move package to Debian Python Team
diff -Nru sphinxcontrib-autoprogram-0.1.7/debian/patches/0001-Fix-argparse-output-for-Python-3.10-compatibility.patch sphinxcontrib-autoprogram-0.1.7/debian/patches/0001-Fix-argparse-output-for-Python-3.10-compatibility.patch
--- sphinxcontrib-autoprogram-0.1.7/debian/patches/0001-Fix-argparse-output-for-Python-3.10-compatibility.patch 1970-01-01 02:00:00.0 +0200
+++ sphinxcontrib-autoprogram-0.1.7/debian/patches/0001-Fix-argparse-output-for-Python-3.10-compatibility.patch 2022-11-19 22:00:30.0 +0200
@@ -0,0 +1,29 @@
+From 5f8cd70a0edcc804d305f360b6b6022767b2fcea Mon Sep 17 00:00:00 2001
+From: Karthikeyan Singaravelan
+Date: Thu, 28 Jan 2021 15:02:19 +
+Subject: Fix argparse output for Python 3.10 compatibility.
+
+---
+ sphinxcontrib/autoprogram.py | 6 +-
+ 1 file changed, 5 insertions(+), 1 deletion(-)
+
+diff --git a/sphinxcontrib/autoprogram.py b/sphinxcontrib/autoprogram.py
+index c60cf68..1f051bb 100644
+--- a/sphinxcontrib/autoprogram.py
b/sphinxcontrib/autoprogram.py
+@@ -476,7 +476,11 @@ class ScannerTestCase(unittest.TestCase):
+ # section: default optionals
+ program, options, group = sections[1]
+ self.assertEqual([], program)
+-self.assertEqual("optional arguments", group.title)
++# See https://github.com/sphinx-contrib/autoprogram/issues/24
++if sys.version_info >= (3, 10):
++self.assertEqual('options', group.title)
++else:
++self.assertEqual('optional arguments', group.title)
+ self.assertEqual(None, group.description)
+ self.assertEqual(2, len(options))
+ self.assertEqual(
+--
+2.30.2
+
diff -Nru sphinxcontrib-autoprogram-0.1.7/debian/patches/series sphinxcontrib-autoprogram-0.1.7/debian/patches/series
--- sphinxcontrib-autoprogram-0.1.7/debian/patches/series 1970-01-01 02:00:00.0 +0200
+++ sphinxcontrib-autoprogram-0.1.7/debian/patches/series 2022-11-19 22:29:45.0 +0200
@@ -0,0 +1 @@
+0001-Fix-argparse-output-for-Python-3.10-compatibility.patch
Processed: sphinxcontrib-autoprogram: diff for NMU version 0.1.7-2.1
Processing control commands:
> tags 1009482 + pending
Bug #1009482 [src:sphinxcontrib-autoprogram] sphinxcontrib-autoprogram: FTBFS:
dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit
code 13
Added tag(s) pending.
--
1009482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1024458: seqan-needle: binary-all FTBFS
Source: seqan-needle Version: 1.0.1.0.0.git.3011926+ds-2 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=seqan-needle=all=1.0.1.0.0.git.3011926%2Bds-2=1668618292=0 ... debian/rules override_dh_auto_build-indep make[1]: Entering directory '/<>' cd obj-* && /usr/bin/make doc /bin/sh: 1: cd: can't cd to obj-* make[1]: *** [debian/rules:26: override_dh_auto_build-indep] Error 2
Processed: notfound 1008502 in 0.18.0-6.2
Processing commands for cont...@bugs.debian.org: > notfound 1008502 0.18.0-6.2 Bug #1008502 [vdirsyncer] vdirsyncer: Unknown error occured: unmatched ')' Ignoring request to alter found versions of bug #1008502 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1008502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1008502 in 0.16.8-2
Processing commands for cont...@bugs.debian.org: > found 1008502 0.16.8-2 Bug #1008502 [vdirsyncer] vdirsyncer: Unknown error occured: unmatched ')' Ignoring request to alter found versions of bug #1008502 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1008502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024457: "apt changelog" fails to display the complete changelog
Package: apt Version: 2.5.4 Severity: serious X-Debbugs-Cc: Debhelper Maintainers debhelper recently started removing older changelog entries from binary packages, but the way to get them with apt does not work: $ zcat /usr/share/doc/apt/changelog.gz | tail -5 -- Julian Andres Klode Mon, 05 Aug 2019 21:26:10 +0200 # Older entries have been removed from this changelog. # To read the complete changelog use `apt changelog apt`. $ apt changelog apt | tail -5 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. -- Julian Andres Klode Mon, 05 Aug 2019 21:26:10 +0200 # Older entries have been removed from this changelog. # To read the complete changelog use `apt changelog apt`. Fetched 42.8 kB in 0s (0 B/s) $ Somehow apt fails to download the other 21 years of changelog entries, and performs the useless task of showing the truncated shipped changelog.
Bug#1023227: marked as done (breezy: autopkgtest regression: Non-UTF-8 code starting with '\xf2' in file /usr/bin/brz)
Your message dated Sat, 19 Nov 2022 20:37:10 + with message-id and subject line Bug#1023227: fixed in breezy 3.3.0+bzr7661-5 has caused the Debian Bug report #1023227, regarding breezy: autopkgtest regression: Non-UTF-8 code starting with '\xf2' in file /usr/bin/brz 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.) -- 1023227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: breezy Version: 3.3.0+bzr7661-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of breezy the autopkgtest of breezy fails in testing when that autopkgtest is run with the binary packages of breezy from unstable. It passes when run with only packages from testing. In tabular form: passfail breezy from testing3.3.0+bzr7661-2 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from breezy/3.3.0+bzr7661-2. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=breezy https://ci.debian.net/data/autopkgtest/testing/amd64/b/breezy/27685392/log.gz SyntaxError: Non-UTF-8 code starting with '\xf2' in file /usr/bin/brz on line 2, but no encoding declared; see https://python.org/dev/peps/pep-0263/ for details autopkgtest [23:12:42]: test testsuite3 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: breezy Source-Version: 3.3.0+bzr7661-5 Done: Jelmer Vernooij We believe that the bug you reported is fixed in the latest version of breezy, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated breezy 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, 19 Nov 2022 17:04:44 + Source: breezy Architecture: source Version: 3.3.0+bzr7661-5 Distribution: unstable Urgency: medium Maintainer: Debian Breezy Maintainers Changed-By: Jelmer Vernooij Closes: 1023227 Changes: breezy (3.3.0+bzr7661-5) unstable; urgency=medium . * Add patch 19_brz_executable: Make the brz binary a python script for the moment, to allow autopkgtest in testing to run. Closes: #1023227 Checksums-Sha1: 731707fdb394bdedc41894524d1aa86168505059 2914 breezy_3.3.0+bzr7661-5.dsc 7440e0a4a0f872b3ddeeb71843dd629b5688e93c 75752 breezy_3.3.0+bzr7661-5.debian.tar.xz 4741c16ce6b13a0605dcfe698592c69918e1dfef 16489 breezy_3.3.0+bzr7661-5_amd64.buildinfo Checksums-Sha256: 329eafa77329405bd92e547b2863a8e8afbfe339b93e11d8b87af9d69bf4d52d 2914 breezy_3.3.0+bzr7661-5.dsc 136d339631f66df48546e5a8eaeee83bcab7d98e7cbd8954590ad11f958d6aba 75752 breezy_3.3.0+bzr7661-5.debian.tar.xz 2381b8b9bd36f006ce22d4a6993c8a06aadbddcaeb1d061e5b52fc7c2afe08ac 16489 breezy_3.3.0+bzr7661-5_amd64.buildinfo Files: a32f2a89658fbd9f6ddebe048f6b1198 2914 vcs optional breezy_3.3.0+bzr7661-5.dsc 4d773452d2c48655dc811db1eb58fe51 75752 vcs optional breezy_3.3.0+bzr7661-5.debian.tar.xz 48c27308e06ecfc36773e168d9da55fb 16489 vcs optional breezy_3.3.0+bzr7661-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAmN5Oj0ACgkQV5wWDUye I+jL+A//bnKrw8rAuyNmTK1D7DDW4Qb1uDkAaIUe+cUJQMTkuHiS2cN/2j3+ZcE7 gVKGZHEYIhyJxk1CUcLDaL+z633Jzw7kHkkcODF8DwnkznwI7JW1Gq1rcENLpWLl yISn651gJ/5smlVrbc7uqZgLrlBu6Xk/h6bBQX+yZhlJJj3uE/ttarl+kmxFjAAG
Processed: block 1017950 with 950012
Processing commands for cont...@bugs.debian.org: > block 1017950 with 950012 Bug #1017950 [librust-prometheus+procfs-dev] librust-prometheus+procfs-dev depends on non-existent librust-procfs-dev 1017950 was not blocked by any bugs. 1017950 was not blocking any bugs. Added blocking bug(s) of 1017950: 950012 > thanks Stopping processing here. Please contact me if you need assistance. -- 1017950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#900821: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)
user debian-rele...@lists.debian.org
usertag 900821 + bsp-2022-11-nl-tilburg
found 900821 5.10.70-1
fixed 900821 5.10.84-1
thanks
We have/had a BSP in Tilburg today and I went to work on this bug.
With success :-)
I first created a new Bullseye VM with virt-manager using the
debian-11.5.0-amd64-netinst.iso installation media and installed only
the Standard System Utilities and SSH Server.
Upon reboot I installed vim (ofc) and followed the excellent instructions
from OP and installed the packages:
"apt-get install samba apache2 cifs-utils"
Then I added the `[ftp]` block to /etc/samba/smb.conf and created the
`/srv/ftp/100Mzero` file consisting of only zero's.
As I'd be rebooting often, I made mounting easy by adding to `/etc/fstab/`:
//localhost/ftp /var/www/html cifs
username=debian,password=root,noauto,user 0 0
Then I created the following script:
```
debian@debian-bullseye:~$ cat bug900821
#!/bin/sh
#/srv/ftp/100Mzero
SHA256_STORED="20492a4d0d84f8beb1767f6616229f85d44c2827b64bdbfb260ee12fa1109e0e"
echo "sha256sum should be:"
echo " $SHA256_STORED"
echo ""
i=0
while [ $i -ne 100 ]
do
i=$((i + 1))
#printf "$i "
printf ". "
SHA256_CALC="$(wget http://localhost/100Mzero -O - 2>/dev/null |
sha256sum | awk '{ print $1 }')"
if [ "$SHA256_CALC" != "$SHA256_STORED" ] ; then
printf "\nBug 900821 triggered! Calculated SHA256: %s\n"
"$SHA256_CALC"
exit 1
fi
done
printf "\nTest completed\n"
```
I tried it out on the installed kernel, 5.10.149-2 aka 5.10.0-19-amd64, and
found out it all worked as expected. Idem ditto for 5.10.140-1/5.10.0-18-amd64.
I then tried 5.10.28-1/5.10.0-6-amd64 and got a kernel crash \o/
I then went on to narrow down which version worked and which next lower version
did fail and it turned out 5.10.70-1 failed, while 5.10.84-1 succeeded.
What was both odd and interesting was what happened during a crash.
With 5.10.28-1 I got this:
debian@debian-bullseye:~$ ./bug900821
sha256sum should be:
20492a4d0d84f8beb1767f6616229f85d44c2827b64bdbfb260ee12fa1109e0e
.
Message from syslogd@debian-bullseye at Nov 19 18:43:22 ...
kernel:[ 40.266711] usercopy: Kernel memory exposure attempt detected from
SLUB object 'vm_area_struct' (offset 0, size 117)!
That killed my SSH session. I don't know if it was the case each time, but
at least twice I was able to directly log in to the VM ... and I was able
to secure `dmesg` which shows the kernel crash :-)
I have attached both that dmesg output as the Konsole output from my
BSP session wrt this bug.
I don't know if it's useful to do a (lengthy!) git-bisect session as I'm quite
sure the issue is fixed.
I've updated the metadata, but I haven't closed it (yet?).
Cheers,
Diederik[0.00] Linux version 5.10.0-9-amd64 (debian-ker...@lists.debian.org)
(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian)
2.35.2) #1 SMP Debian 5.10.70-1 (2021-09-30)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-amd64
root=UUID=a7893f33-27c0-4b56-8d49-b0e98db7f84a ro quiet
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[0.00] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
[0.00] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960
bytes, using 'compacted' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000f-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x3ffdbfff] usable
[0.00] BIOS-e820: [mem 0x3ffdc000-0x3fff] reserved
[0.00] BIOS-e820: [mem 0xb000-0xbfff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xfeffc000-0xfeff] reserved
[0.00] BIOS-e820: [mem 0xfffc-0x] reserved
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.8 present.
[0.00] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
1.16.0-debian-1.16.0-4 04/01/2014
[0.00] Hypervisor detected: KVM
[0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00
[0.00] kvm-clock: cpu 0, msr 2c4b3001, primary cpu clock
[0.00] kvm-clock: using sched offset of 1463003892121 cycles
[
Processed: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)
Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was didi.deb...@cknow.org). > usertag 900821 + bsp-2022-11-nl-tilburg There were no usertags set. Usertags are now: bsp-2022-11-nl-tilburg. > found 900821 5.10.70-1 Bug #900821 [src:linux] apache reads wrong data over cifs filesystems served by samba Marked as found in versions linux/5.10.70-1. > fixed 900821 5.10.84-1 Bug #900821 [src:linux] apache reads wrong data over cifs filesystems served by samba Marked as fixed in versions linux/5.10.84-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 900821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024267: marked as done (krb5: CVE-2022-42898: integer overflows in PAC parsing)
Your message dated Sat, 19 Nov 2022 19:47:26 + with message-id and subject line Bug#1024267: fixed in krb5 1.18.3-6+deb11u3 has caused the Debian Bug report #1024267, regarding krb5: CVE-2022-42898: integer overflows in PAC parsing 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.) -- 1024267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: krb5 Version: 1.20-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1.18.3-6+deb11u2 Control: found -1 1.18.3-6 Control: found -1 1.8+dfsg-1 Hi, The following vulnerability was published for krb5. CVE-2022-42898[0]: | integer overflows in PAC parsing 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-42898 https://www.cve.org/CVERecord?id=CVE-2022-42898 [1] https://github.com/krb5/krb5/commit/b99de751dd35360c0fccac74a40f4a60dbf1ceea Regards, Salvatore --- End Message --- --- Begin Message --- Source: krb5 Source-Version: 1.18.3-6+deb11u3 Done: Sam Hartman We believe that the bug you reported is fixed in the latest version of krb5, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sam Hartman (supplier of updated krb5 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, 17 Nov 2022 12:41:46 -0700 Source: krb5 Architecture: source Version: 1.18.3-6+deb11u3 Distribution: bullseye-security Urgency: high Maintainer: Sam Hartman Changed-By: Sam Hartman Closes: 1024267 Changes: krb5 (1.18.3-6+deb11u3) bullseye-security; urgency=high . * Integer overflows in PAC parsing; potentially critical for 32-bit KDCs or when cross-realm acts maliciously; DOS in other conditions; CVE-2022-42898, Closes: #1024267 Checksums-Sha1: 4563ee77b2b1f9f687870218a3f120185f87d521 3209 krb5_1.18.3-6+deb11u3.dsc fdbb31fab5bdea24fc464d09bdbc245740648f1a 8715312 krb5_1.18.3.orig.tar.gz 909b9c68601cf999cd2697c83a0f56efd0faba6d 833 krb5_1.18.3.orig.tar.gz.asc 3fb20afe28c1028005895e089327aa9b42d8572a 108804 krb5_1.18.3-6+deb11u3.debian.tar.xz 765dda2737715a73f4257f36aa23709d6dbfea6b 5299 krb5_1.18.3-6+deb11u3_source.buildinfo Checksums-Sha256: 539d8a8df5c181b5c16cab487fef4d192f934a170dcfe507e76020132fdb5399 3209 krb5_1.18.3-6+deb11u3.dsc e61783c292b5efd9afb45c555a80dd267ac67eebabca42185362bee6c4fbd719 8715312 krb5_1.18.3.orig.tar.gz ded19808ba7320ad0bb3ddfb5202845b2ff36a50613af7832f78dd3cb4437419 833 krb5_1.18.3.orig.tar.gz.asc 5efc82324430be1c2e12a6f0b40dd27b149f5f77cfe10a9ed0b8567a07f08981 108804 krb5_1.18.3-6+deb11u3.debian.tar.xz 010da2ea85740fd7c3aa006e18737aac611036e763369cea85bd0e2655d6204a 5299 krb5_1.18.3-6+deb11u3_source.buildinfo Files: bf71dfd670a582099641ffe284d25c3c 3209 net optional krb5_1.18.3-6+deb11u3.dsc a64e8018a7572e0b4bd477c745129ffc 8715312 net optional krb5_1.18.3.orig.tar.gz bca804e12e8dc2de6930e916cd7a2ce3 833 net optional krb5_1.18.3.orig.tar.gz.asc 2f8366885ca14a369e53dfa6290d70a5 108804 net optional krb5_1.18.3-6+deb11u3.debian.tar.xz 85ac8d7fcd056cc14c9fdeaf27049b10 5299 net optional krb5_1.18.3-6+deb11u3_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSj2jRwbAdKzGY/4uAsbEw8qDeGdAUCY3edjAAKCRAsbEw8qDeG dMeHAPwMg8/Dx2M51bFuxWo2fE/1mokrUxL7e0oJgdxNICXJwwEA2yTWOhMdTupp U/WQkuML2jqLSLDIek4IjsAEo0N0OgQ= =cMjT -END PGP SIGNATURE End Message ---
Bug#1024249: marked as done (wordpress: update to 5.7.8+dfsg1-0+deb11u1 have missing dependencies in bullseye-security)
Your message dated Sat, 19 Nov 2022 19:49:18 + with message-id and subject line Bug#1024249: fixed in wordpress 5.7.8+dfsg1-0+deb11u2 has caused the Debian Bug report #1024249, regarding wordpress: update to 5.7.8+dfsg1-0+deb11u1 have missing dependencies in bullseye-security 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.) -- 1024249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wordpress Version: 5.7.8+dfsg1-0+deb11u1 Severity: normal X-Debbugs-Cc: opensou...@wbk-it.de Dear Maintainer, * What led up to the situation? Just a simple 'apt upgrade'. The security package seems to be 2 missing dependencies for the stable(-security) dist. * What exactly did you do (or not do) that was effective (or ineffective)? Adding stable-security to apt repo. * What was the outcome of this action? Upgrade is not installed, so the bullseye installation is untouched but the theme is updated. * What outcome did you expect instead? Upgrade the package. The following packages have unmet dependencies: wordpress : Depends: libjs-underscore (>= 1.13.4~dfsg+~1.11.4) but 1.9.1~dfsg-3 is to be installed Depends: php-getid3 (>= 1.9.22+dfsg) but 1.9.20+dfsg-1 is to be installed E: Unable to correct problems, you have held broken packages. libjs-underscore: Installed: 1.9.1~dfsg-3 Candidate: 1.9.1~dfsg-3 Version table: *** 1.9.1~dfsg-3 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 100 /var/lib/dpkg/status -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.53-1-pve (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wordpress depends on: ii apache2 [httpd] 2.4.54-1~deb11u1 ii ca-certificates 20210119 ii default-mysql-client1.0.7 ii libapache2-mod-php 2:7.4+76 ii libapache2-mod-php7.4 [libapache2-mod-php] 7.4.33-1+deb11u1 ii libjs-cropper 1.2.2-1.1 ii libjs-underscore1.9.1~dfsg-3 ii mariadb-client-10.5 [virtual-mysql-client] 1:10.5.15-0+deb11u1 ii php-gd 2:7.4+76 ii php-getid3 1.9.20+dfsg-1 ii php-mysql 2:7.4+76 ii php7.4-gd [php-gd] 7.4.33-1+deb11u1 ii php7.4-mysql [php-mysqlnd] 7.4.33-1+deb11u1 Versions of packages wordpress recommends: ii wordpress-l10n 5.7.5+dfsg1-0+deb11u1 ii wordpress-theme-twentytwentyone 5.7.8+dfsg1-0+deb11u1 Versions of packages wordpress suggests: pn default-mysql-server | virtual-mysql-server pn php-ssh2 -- Configuration Files: /etc/wordpress/htaccess changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: wordpress Source-Version: 5.7.8+dfsg1-0+deb11u2 Done: Craig Small We believe that the bug you reported is fixed in the latest version of wordpress, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Craig Small (supplier of updated wordpress 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, 17 Nov 2022 08:11:54 +1100 Source: wordpress Binary: wordpress wordpress-l10n wordpress-theme-twentynineteen wordpress-theme-twentytwenty wordpress-theme-twentytwentyone Architecture: source all Version: 5.7.8+dfsg1-0+deb11u2 Distribution: bullseye-security Urgency: high Maintainer: Craig Small Changed-By: Craig Small Description: wordpress - weblog manager
Bug#997145: autoconf2.69: diff for NMU version 2.69-3.1
Control: tags 997145 + pending Dear maintainer, I've prepared an NMU for autoconf2.69 (versioned as 2.69-3.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru autoconf2.69-2.69/debian/changelog autoconf2.69-2.69/debian/changelog --- autoconf2.69-2.69/debian/changelog 2021-09-17 18:52:26.0 +0300 +++ autoconf2.69-2.69/debian/changelog 2022-11-19 21:40:11.0 +0200 @@ -1,3 +1,11 @@ +autoconf2.69 (2.69-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Backport upstream fix for FTBFS with recent texinfo. +(Closes: #997145) + + -- Adrian Bunk Sat, 19 Nov 2022 21:40:11 +0200 + autoconf2.69 (2.69-3) unstable; urgency=medium * Don't apply the add-runstatedir backport, not needed in the context diff -Nru autoconf2.69-2.69/debian/patches/0001-doc-port-to-Texinfo-6.3.patch autoconf2.69-2.69/debian/patches/0001-doc-port-to-Texinfo-6.3.patch --- autoconf2.69-2.69/debian/patches/0001-doc-port-to-Texinfo-6.3.patch 1970-01-01 02:00:00.0 +0200 +++ autoconf2.69-2.69/debian/patches/0001-doc-port-to-Texinfo-6.3.patch 2022-11-19 21:40:11.0 +0200 @@ -0,0 +1,28 @@ +From d7e0164f857408dbce186d97dc6ff67b5a276d89 Mon Sep 17 00:00:00 2001 +From: Paul Eggert +Date: Tue, 13 Sep 2016 17:51:18 -0700 +Subject: doc: port to Texinfo 6.3 + +* doc/autoconf.texi: Remove obsolete @setcontentsaftertitlepage +that provokes a warning from Texinfo 6.3. +--- + doc/autoconf.texi | 3 --- + 1 file changed, 3 deletions(-) + +diff --git a/doc/autoconf.texi b/doc/autoconf.texi +index 34ca2137..79f65412 100644 +--- a/doc/autoconf.texi b/doc/autoconf.texi +@@ -5,9 +5,6 @@ + @include version.texi + @settitle Autoconf + @setchapternewpage odd +-@ifnothtml +-@setcontentsaftertitlepage +-@end ifnothtml + @finalout + + @c @ovar(ARG) +-- +2.30.2 + diff -Nru autoconf2.69-2.69/debian/patches/series autoconf2.69-2.69/debian/patches/series --- autoconf2.69-2.69/debian/patches/series 2021-09-17 18:52:26.0 +0300 +++ autoconf2.69-2.69/debian/patches/series 2022-11-19 21:40:09.0 +0200 @@ -6,4 +6,4 @@ #add-runstatedir.patch unescaped-left-brace-warning-fix.patch mmap-leak-fix.patch - +0001-doc-port-to-Texinfo-6.3.patch
Processed: autoconf2.69: diff for NMU version 2.69-3.1
Processing control commands: > tags 997145 + pending Bug #997145 [src:autoconf2.69] autoconf2.69: FTBFS: autoconf.texi:9: unknown command `setcontentsaftertitlepage' Added tag(s) pending. -- 997145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: raqm: diff for NMU version 0.7.0-4.1
Processing control commands: > tags 1022404 + patch Bug #1022404 [src:raqm] raqm: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Added tag(s) patch. > tags 1022404 + pending Bug #1022404 [src:raqm] raqm: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 1022404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022404: raqm: diff for NMU version 0.7.0-4.1
Control: tags 1022404 + patch Control: tags 1022404 + pending Dear maintainer, I've prepared an NMU for raqm (versioned as 0.7.0-4.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru raqm-0.7.0/debian/changelog raqm-0.7.0/debian/changelog --- raqm-0.7.0/debian/changelog 2019-12-17 11:08:26.0 +0200 +++ raqm-0.7.0/debian/changelog 2022-11-19 21:15:45.0 +0200 @@ -1,3 +1,10 @@ +raqm (0.7.0-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add upstream fix for FTBFS with recent HarfBuzz. (Closes: #1022404) + + -- Adrian Bunk Sat, 19 Nov 2022 21:15:45 +0200 + raqm (0.7.0-4) unstable; urgency=medium * debian/tests/libssh-server: Use the correct compiler for proposed diff -Nru raqm-0.7.0/debian/patches/0001-Update-text-expectation.patch raqm-0.7.0/debian/patches/0001-Update-text-expectation.patch --- raqm-0.7.0/debian/patches/0001-Update-text-expectation.patch 1970-01-01 02:00:00.0 +0200 +++ raqm-0.7.0/debian/patches/0001-Update-text-expectation.patch 2022-11-19 19:32:08.0 +0200 @@ -0,0 +1,29 @@ +From 17170a1eeb63807b4035427f3ca2b3e475c8f42b Mon Sep 17 00:00:00 2001 +From: Khaled Hosny +Date: Wed, 25 Aug 2021 16:58:25 +0200 +Subject: Update text expectation + +--- + tests/cursor_position_GB8a.test | 6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/tests/cursor_position_GB8a.test b/tests/cursor_position_GB8a.test +index bef963e..d161691 100644 +--- a/tests/cursor_position_GB8a.test b/tests/cursor_position_GB8a.test +@@ -32,9 +32,9 @@ glyph [0] x_offset: 0 y_offset: 0 x_advance: 748 font: Amiri + glyph [0] x_offset: 0 y_offset: 0 x_advance: 748 font: Amiri + glyph [0] x_offset: 0 y_offset: 0 x_advance: 748 font: Amiri + +-UTF-32 clusters: 00 01 02 03 +-UTF-8 clusters: 00 04 08 12 ++UTF-32 clusters: 00 00 02 02 ++UTF-8 clusters: 00 00 08 08 + +-The position is 2992 at index 12 ++The position is 2244 at index 8 + + The start-index is 4 at position 1000 +-- +2.30.2 + diff -Nru raqm-0.7.0/debian/patches/series raqm-0.7.0/debian/patches/series --- raqm-0.7.0/debian/patches/series 2019-12-17 11:08:26.0 +0200 +++ raqm-0.7.0/debian/patches/series 2022-11-19 21:15:36.0 +0200 @@ -1 +1,2 @@ use_py3.diff +0001-Update-text-expectation.patch
Processed: Downgrading to severity important
Processing commands for cont...@bugs.debian.org: > severity 1024314 important Bug #1024314 [src:python-msgpack] python-msgpack: b-d on python3-all-dev, but not built for all supported Python3 Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1024314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1024453: mediathek: fails to start with openjdk 17
Processing control commands: > reassign -1 java-wrappers 0.3 Bug #1024453 [mediathekview] mediathek: fails to start with openjdk 17 Bug reassigned from package 'mediathekview' to 'java-wrappers'. No longer marked as found in versions mediathekview/13.2.1+ds-1. Ignoring request to alter fixed versions of bug #1024453 to the same values previously set Bug #1024453 [java-wrappers] mediathek: fails to start with openjdk 17 Marked as found in versions java-wrappers/0.3. > affects -1 mediathekview Bug #1024453 [java-wrappers] mediathek: fails to start with openjdk 17 Added indication that 1024453 affects mediathekview -- 1024453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024453: mediathek: fails to start with openjdk 17
Control: reassign -1 java-wrappers 0.3 Control: affects -1 mediathekview On 2022-11-19 19:18:14 +0100, Sebastian Ramacher wrote: > Package: mediathekview > Version: 13.2.1+ds-1 > Severity: grave > X-Debbugs-Cc: sramac...@debian.org > > Since the switch to openjre-17 as default, mediathekview nolonger > starts: > > $ mediathekview > [warning] /usr/bin/mediathekview: No java runtime was found This is an issue in java-wrappers. It does not know about version 17. Cheers > > > Cheers > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable-debug > APT policy: (650, 'unstable-debug'), (650, 'unstable'), (601, 'testing'), > (600, 'experimental-debug'), (600, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > 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) > > Versions of packages mediathekview depends on: > ii default-jre [java9-runtime] 2:1.17-73 > ii java-wrappers 0.3 > ii libcommons-compress-java1.21-1 > ii libcommons-configuration2-java 2.8.0-1 > ii libcommons-dbcp2-java 2.9.0-1 > ii libcommons-lang3-java 3.12.0-2 > ii libcommons-pool2-java 2.11.1-1 > ii libcontrolsfx-java 11.0.0-1 > ii libguava-java 29.0-6 > ii libjackson2-core-java 2.14.0-2 > ii libjchart2d-java3.2.2+dfsg2-3 > ii libjiconfont-font-awesome-java 4.7.0.1-1 > ii libjiconfont-java 1.0.0-2 > ii libjiconfont-swing-java 1.0.1-2 > ii libjide-oss-java3.7.6+dfsg-2 > ii liblog4j2-java 2.17.2-1 > ii libmbassador-java 1.3.1-2 > ii libmiglayout-java 5.1-3 > ii libokhttp-java 3.13.1-3 > ii libopenjfx-java 11.0.11+1-1.1 > ii libslf4j-java 1.7.32-1 > ii libswingx-java 1:1.6.2-4 > ii libxz-java 1.9-1 > ii openjdk-17-jre [java9-runtime] 17.0.5+8-2 > > Versions of packages mediathekview recommends: > pn flvstreamer > ii mpv 0.35.0-2 > ii vlc 3.0.18~rc2-1+b1 > > Versions of packages mediathekview suggests: > ii ffmpeg 7:5.1.2-1 > > -- no debconf information > > -- > Sebastian Ramacher -- Sebastian Ramacher
Processed: Re: Bug#1024391: gtk4: FTBFS on big-endian: some dependency made border-image-excess-size reftest regress
Processing control commands: > severity -1 normal Bug #1024392 [src:gtk+3.0] gtk+3.0: FTBFS on big-endian: some dependency made border-image-excess-size reftest regress Severity set to 'normal' from 'serious' > tags -1 - ftbfs Bug #1024392 [src:gtk+3.0] gtk+3.0: FTBFS on big-endian: some dependency made border-image-excess-size reftest regress Removed tag(s) ftbfs. -- 1024392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1024391: gtk4: FTBFS on big-endian: some dependency made border-image-excess-size reftest regress
Processing control commands: > severity -1 normal Bug #1024391 [src:gtk4] gtk4: FTBFS on big-endian: some dependency made border-image-excess-size reftest regress Severity set to 'normal' from 'serious' > tags -1 - ftbfs Bug #1024391 [src:gtk4] gtk4: FTBFS on big-endian: some dependency made border-image-excess-size reftest regress Removed tag(s) ftbfs. -- 1024391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024391: gtk4: FTBFS on big-endian: some dependency made border-image-excess-size reftest regress
Control: severity -1 normal Control: tags -1 - ftbfs On Fri, 18 Nov 2022 at 18:08:29 +, Simon McVittie wrote: > I'll ignore this test failure for now and downgrade these bugs to non-RC. gtk+3.0_3.24.34-5 and gtk4_4.8.2+ds-3 ignore this test failure on big-endian, and were built successfully on all release architectures. smcv
Bug#1022365: reproduction
This seems to be the source of the problem: pdsh@ip-10-84-234-180: module path "/<>/src/modules/.libs" insecure. pdsh@ip-10-84-234-180: "/build": Owner not root, current uid, or pdsh executable owner pdsh@ip-10-84-234-180: Couldn't load any pdsh modules Indeed, I can reproduce by building in a directory that has an ancestor directory owned by a user that is neither root, nor myself. I've not been clever enough to workaround this. Two options would be to (1) disable the failing tests or (2) avoid the failures by linking the plugins statically. Neither seems ideal.
Bug#1023427: marked as done (pixman: CVE-2022-44638)
Your message dated Sat, 19 Nov 2022 18:17:08 + with message-id and subject line Bug#1023427: fixed in pixman 0.40.0-1.1~deb11u1 has caused the Debian Bug report #1023427, regarding pixman: CVE-2022-44638 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.) -- 1023427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pixman Version: 0.40.0-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://gitlab.freedesktop.org/pixman/pixman/-/issues/63 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for pixman. CVE-2022-44638[0]: | In libpixman in Pixman before 0.42.2, there is an out-of-bounds write | (aka heap-based buffer overflow) in rasterize_edges_8 due to an | integer overflow in pixman_sample_floor_y. 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-44638 https://www.cve.org/CVERecord?id=CVE-2022-44638 [1] https://gitlab.freedesktop.org/pixman/pixman/-/issues/63 [2] https://gitlab.freedesktop.org/pixman/pixman/-/commit/a1f88e842e0216a5b4df1ab023caebe33c101395 Regards, Salvatore --- End Message --- --- Begin Message --- Source: pixman Source-Version: 0.40.0-1.1~deb11u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of pixman, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated pixman package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 08 Nov 2022 23:11:38 +0100 Source: pixman Architecture: source Version: 0.40.0-1.1~deb11u1 Distribution: bullseye-security Urgency: high Maintainer: Debian X Strike Force Changed-By: Salvatore Bonaccorso Closes: 1023427 Changes: pixman (0.40.0-1.1~deb11u1) bullseye-security; urgency=high . * Non-maintainer upload by the Security Team. * Rebuild for bullseye-security. . pixman (0.40.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Avoid integer overflow leading to out-of-bounds write (CVE-2022-44638) (Closes: #1023427) Checksums-Sha1: 572749f56d7840232818b8a0e1b7048620f86047 2216 pixman_0.40.0-1.1~deb11u1.dsc d7baa6377b6f48e29db011c669788bb1268d08ad 913976 pixman_0.40.0.orig.tar.gz 7d56f75acf14486cbf351e8b4c08333ce8baf38c 320106 pixman_0.40.0-1.1~deb11u1.diff.gz ac8916b66df58f30bb654044c7d36eb6c7b7f83d 7263 pixman_0.40.0-1.1~deb11u1_amd64.buildinfo Checksums-Sha256: f7a628fbfcb5dae5178daab6e0225be55dbf6ffd8efa60429d1d3dd59584d334 2216 pixman_0.40.0-1.1~deb11u1.dsc 6d200dec3740d9ec4ec8d1180e25779c00bc749f94278c8b9021f5534db223fc 913976 pixman_0.40.0.orig.tar.gz 11dad4be11db34aab221a324b78a5f7a88ac96596f5ac39d4fe3b634325b00b7 320106 pixman_0.40.0-1.1~deb11u1.diff.gz 928f99e55e77417431d734a12deb33f669868ff2bd3c5d29b1d06f394a4b325f 7263 pixman_0.40.0-1.1~deb11u1_amd64.buildinfo Files: 662ec6cf34d02e5db10546d4e01683a1 2216 devel optional pixman_0.40.0-1.1~deb11u1.dsc 73858c0862dd9896fb5f62ae267084a4 913976 devel optional pixman_0.40.0.orig.tar.gz 0428ae45a422f0a6f13195f8d95bf886 320106 devel optional pixman_0.40.0-1.1~deb11u1.diff.gz 182ba22c63418db3c4b3ea818e30d603 7263 devel optional pixman_0.40.0-1.1~deb11u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmNq11tfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EVEcQAJBvDL6tey54L6/KdbNgeshqQiwfm76z crfF99wxWcL13Qx3WbstblhC8TTb+0FIh/vuwOwgLAXYOpWMWrWpPv2bDFiFfcd2 hlpFG9Moz0ZgexRZHny6LgWfzjxKiKr3hQCWmVu36Ub3CTVH2RgzqfYt6oYVVdnu njf0yW4i4EeUzcZdUAImNhbtY2+ZHJYzIE6JSusIYav8BNV9kOVur6Y7HDhSd1J4 yaGmL/qZkGSf41N0LyKycQ5kVRLEyNvc1/VudHd4yW2HjKNcwPPJ1DE2Nsv774YK lb+ZDpAEkvw5B3TLU5KIY4csm0PdqUO31ig1Fc/NKAqqgJVmrRnhmvSSopTa9TsT
Bug#1024453: mediathek: fails to start with openjdk 17
Package: mediathekview Version: 13.2.1+ds-1 Severity: grave X-Debbugs-Cc: sramac...@debian.org Since the switch to openjre-17 as default, mediathekview nolonger starts: $ mediathekview [warning] /usr/bin/mediathekview: No java runtime was found Cheers -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (650, 'unstable-debug'), (650, 'unstable'), (601, 'testing'), (600, 'experimental-debug'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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) Versions of packages mediathekview depends on: ii default-jre [java9-runtime] 2:1.17-73 ii java-wrappers 0.3 ii libcommons-compress-java1.21-1 ii libcommons-configuration2-java 2.8.0-1 ii libcommons-dbcp2-java 2.9.0-1 ii libcommons-lang3-java 3.12.0-2 ii libcommons-pool2-java 2.11.1-1 ii libcontrolsfx-java 11.0.0-1 ii libguava-java 29.0-6 ii libjackson2-core-java 2.14.0-2 ii libjchart2d-java3.2.2+dfsg2-3 ii libjiconfont-font-awesome-java 4.7.0.1-1 ii libjiconfont-java 1.0.0-2 ii libjiconfont-swing-java 1.0.1-2 ii libjide-oss-java3.7.6+dfsg-2 ii liblog4j2-java 2.17.2-1 ii libmbassador-java 1.3.1-2 ii libmiglayout-java 5.1-3 ii libokhttp-java 3.13.1-3 ii libopenjfx-java 11.0.11+1-1.1 ii libslf4j-java 1.7.32-1 ii libswingx-java 1:1.6.2-4 ii libxz-java 1.9-1 ii openjdk-17-jre [java9-runtime] 17.0.5+8-2 Versions of packages mediathekview recommends: pn flvstreamer ii mpv 0.35.0-2 ii vlc 3.0.18~rc2-1+b1 Versions of packages mediathekview suggests: ii ffmpeg 7:5.1.2-1 -- no debconf information -- Sebastian Ramacher
Bug#1023576: Need to change the way raku-api is built (will breaks modules)
Hi Following bug #1023576 and [1], the dependency between raku modules and rakudo version needs to be tightened. Until now, every raku-module depends on raku-api- (currently is raku-api-2022-07). The idea is to lock the pre-compiled files contained in a raku-module package to a specific rakudo version. Turns out this is not enough. The pre-compiled files are specific to raku compiler id, which changes whenever nqp or rakudo sources are changed. This source change occurred only on nqp or rakudo upgrades, until I had to patch rakudo source code to fix a bug (#1019579). To fix this, I need to make sure that a module is dependent on a rakudo version with a matching compiler-id. I see no other solution than to change the way rakudo is built to include the compiler id in raku-api (well, only the first 8 chars, because compiler id is quite long). I.e. the next version of rakudo will have this in its control file: Provides: raku-api-2022.07+a6fe09f2 And dh-raku-build will be modified to inject this dependency in raku modules. E.g.: Depends: raku-api-2022.07+a6fe09f2 So, the plan is: - upload a new dh-raku (which will produce non installable raku module package until rakudo is updated) - upload a new version of rakudo in experimental - trigger a transition so that all raku modules are rebuilt with new rakudo and new dh-raku Until the transition is complete, raku in Debian/unstable will be a mess. If anyone has a better idea, I'm all ears ... Dod [1] https://github.com/rakudo/rakudo/issues/5099
Processed: Re: Bug#1024261: debhelper: dbgsym packages contain directory writable by build user
Processing commands for cont...@bugs.debian.org: > severity 1024261 serious Bug #1024261 [debhelper] debhelper: dbgsym packages contain directory writable by build user Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1024261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1022376 is forwarded to https://salsa.debian.org/gnome-team/glib-networking/-/merge_requests/2
Processing commands for cont...@bugs.debian.org: > forwarded 1022376 > https://salsa.debian.org/gnome-team/glib-networking/-/merge_requests/2 Bug #1022376 [src:glib-networking] glib-networking: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1 Set Bug forwarded-to-address to 'https://salsa.debian.org/gnome-team/glib-networking/-/merge_requests/2'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: pandoc: diff for NMU version 2.17.1.1-1.1
Processing control commands: > tags 1023149 + patch Bug #1023149 [src:pandoc] pandoc FTBFS on i386 Added tag(s) patch. > tags 1023149 + pending Bug #1023149 [src:pandoc] pandoc FTBFS on i386 Added tag(s) pending. -- 1023149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023149: pandoc: diff for NMU version 2.17.1.1-1.1
Control: tags 1023149 + patch Control: tags 1023149 + pending Dear maintainer, I've prepared an NMU for pandoc (versioned as 2.17.1.1-1.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru pandoc-2.17.1.1/debian/changelog pandoc-2.17.1.1/debian/changelog --- pandoc-2.17.1.1/debian/changelog 2022-08-13 17:45:31.0 +0300 +++ pandoc-2.17.1.1/debian/changelog 2022-11-19 15:13:51.0 +0200 @@ -1,3 +1,10 @@ +pandoc (2.17.1.1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Workaround i386 FTBFS with -O0. (Closes: #1023149) + + -- Adrian Bunk Sat, 19 Nov 2022 15:13:51 +0200 + pandoc (2.17.1.1-1) unstable; urgency=medium [ upstream ] diff -Nru pandoc-2.17.1.1/debian/rules pandoc-2.17.1.1/debian/rules --- pandoc-2.17.1.1/debian/rules 2022-08-13 17:27:42.0 +0300 +++ pandoc-2.17.1.1/debian/rules 2022-11-19 15:13:49.0 +0200 @@ -192,6 +192,10 @@ DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-optc--param -optcggc-min-expand=10 -O0" endif +ifneq (,$(filter $(DEB_HOST_ARCH_CPU), i386)) +DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-O0" +endif + DEB_SETUP_GHC_CONFIGURE_ARGS += $(if $(filter nocheck,$(DEB_BUILD_OPTIONS)),,-ftests) DEB_INSTALL_DOCS_ALL += README.md
Bug#997366: speedcrunch: FTBFS: TypeError: 'SpeedCrunchSessionLexer' object is not callable
On Sat, 29 Oct 2022 at 10:57, Felix Geyer wrote: > I've prepared a fix for building against Sphinx >= 4 and uploaded it to > DELAYED/5. > Please feel free to tell me if I should cancel it. The debdiff is attached. Nah, it's great, thanks for fixing this. I pushed the fix to the repo and upstream as well.
Bug#1024084: tar: missing licenses
user debian-rele...@lists.debian.org usertag 1024084 + bsp-2022-11-nl-tilburg thank you -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Processed: limit source to asterisk, tagging 1024443
Processing commands for cont...@bugs.debian.org: > limit source asterisk Limiting to bugs with field 'source' containing at least one of 'asterisk' Limit currently set to 'source':'asterisk' > tags 1024443 + pending Bug #1024443 [asterisk-modules] asterisk-modules no longer includes chan_sip which breaks existing configs Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024084: tar: missing licenses
user debian-rele...@lists.debian.org usertag 1024084 + bsp-2022-11-nl-tilburg thank you -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Bug#998977: marked as done (gkrellm-x86info: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Sat, 19 Nov 2022 15:44:54 + with message-id and subject line Bug#1024411: Removed package(s) from unstable has caused the Debian Bug report #998977, regarding gkrellm-x86info: missing required debian/rules targets build-arch and/or build-indep 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.) -- 998977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gkrellm-x86info Version: 0.0.2-9 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Version: 0.0.2-9+rm Dear submitter, as the package gkrellm-x86info 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/1024411 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#669731: marked as done ([PATCH] gkrellm-x86info: Helping to update to packaging format 3.0)
Your message dated Sat, 19 Nov 2022 15:44:54 +
with message-id
and subject line Bug#1024411: Removed package(s) from unstable
has caused the Debian Bug report #669731,
regarding [PATCH] gkrellm-x86info: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
669731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gkrellm-x86info
Severity: wishlist
Tags: patch
Hi,
The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:
http://wiki.debian.org/Projects/DebSrc3.0
I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.
Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.
Thanks,
Jari
>From 33abcf0947e013cc39b703f57d067fcc73ea653d Mon Sep 17 00:00:00 2001
From: Jari Aalto
Date: Sat, 21 Apr 2012 15:29:38 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Signed-off-by: Jari Aalto
---
debian/README.source |2 --
debian/changelog | 12
debian/compat |2 +-
debian/control |4 ++--
debian/copyright |4 +++-
debian/patches/00list |2 --
...{01_gcc-options.dpatch => 01-gcc-options.patch} |8 ++--
...gkrellm2-port.dpatch => 02-gkrellm2-port.patch} |8 ++--
.../{03_makefile.dpatch => 03-makefile.patch} |8 ++--
...h_x86info.dpatch => 04-sync-with-x86info.patch} |8 ++--
debian/patches/series |2 ++
debian/rules | 17 ++---
debian/source/format |2 +-
13 files changed, 35 insertions(+), 44 deletions(-)
delete mode 100644 debian/README.source
delete mode 100644 debian/patches/00list
rename debian/patches/{01_gcc-options.dpatch => 01-gcc-options.patch} (70%)
rename debian/patches/{02_gkrellm2-port.dpatch => 02-gkrellm2-port.patch} (88%)
rename debian/patches/{03_makefile.dpatch => 03-makefile.patch} (90%)
rename debian/patches/{04_sync_with_x86info.dpatch => 04-sync-with-x86info.patch} (91%)
create mode 100644 debian/patches/series
diff --git a/debian/README.source b/debian/README.source
deleted file mode 100644
index 5e94a7b..000
--- a/debian/README.source
+++ /dev/null
@@ -1,2 +0,0 @@
-This packages uses dpatch to manage differences between the upsteram and the
-Debian version.
diff --git a/debian/changelog b/debian/changelog
index 8dae469..4d8db2e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+gkrellm-x86info (0.0.2-9.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+ * Update to Standards-Version to 3.9.3 and debhelper to 9.
+ * Add build-arch and build-indep targets; use dh_prep in rules file.
+ * Add to copyright note about dead URL and successor of gkx86info.
+ * Fix copyright-refers-to-symlink-license (Lintian).
+ * Fix diff-contains-substvars (Lintian).
+
+ -- Jari Aalto Sat, 21 Apr 2012 15:29:24 +0300
+
gkrellm-x86info (0.0.2-9) unstable; urgency=low
* sync MHz.c with x86info 1.25
diff --git a/debian/compat b/debian/compat
index 7f8f011..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-7
+9
diff --git a/debian/control b/debian/control
index b9519b8..4b60a5c 100644
--- a/debian/control
+++ b/debian/control
@@ -1,9 +1,9 @@
Source: gkrellm-x86info
Section: x11
Priority: optional
-Build-Depends: debhelper (>= 7.0.50), gkrellm (>= 2.1.4), libgtk2.0-dev, dpatch
+Build-Depends: debhelper (>= 9), gkrellm (>= 2.1.4), libgtk2.0-dev
Maintainer: Martin Wuertele
-Standards-Version: 3.9.2
+Standards-Version: 3.9.3
Package: gkrellm-x86info
Architecture: i386 amd64
diff --git a/debian/copyright b/debian/copyright
index 48fe7b6..94fa17e 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,6 +1,8 @@
This package was debianized by Martin Wuertele m...@debian.org
Bug#1002714: marked as done (gkrellm-x86info: Obsoleted by gkrellm-cpufreq?)
Your message dated Sat, 19 Nov 2022 15:44:54 + with message-id and subject line Bug#1024411: Removed package(s) from unstable has caused the Debian Bug report #1002714, regarding gkrellm-x86info: Obsoleted by gkrellm-cpufreq? 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.) -- 1002714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gkrellm-x86info Version: 0.0.2-9 Severity: serious Tags: bookworm sid On my CPU gkrellm-x86info seems to show the nominal base speed of the CPU, while gkrellm-cpufreq shows per-cpu data and this data looks plausible. Is there any remaining usecase for gkrellm-x86info? --- End Message --- --- Begin Message --- Version: 0.0.2-9+rm Dear submitter, as the package gkrellm-x86info 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/1024411 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: Re: [Debian-med-packaging] Bug#1024425: python-pysam: FTBFS with Python 3.11 as a supported version
Processing control commands: > forwarded -1 https://github.com/pysam-developers/pysam/issues/1151 Bug #1024425 [src:python-pysam] python-pysam: FTBFS with Python 3.11 as a supported version Set Bug forwarded-to-address to 'https://github.com/pysam-developers/pysam/issues/1151'. -- 1024425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024425: [Debian-med-packaging] Bug#1024425: python-pysam: FTBFS with Python 3.11 as a supported version
Control: forwarded -1 https://github.com/pysam-developers/pysam/issues/1151 Hi Graham, Graham Inggs, on 2022-11-19: > python-pysam FTBFS during the recent rebuild adding Python 3.11 as a > supported version [1]. Thanks for the notice, I informed upstream as my own investigations did not allow me to tell whether this would come for the module itself, or from the interpreter (or from something else I might have missed). Will see how it goes; if nothing, it will still be possible to stick to python3.10 for Debian 12 I guess. Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/5, please excuse my verbosity. signature.asc Description: PGP signature
Bug#999301: marked as done (vsdump: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Sat, 19 Nov 2022 15:43:33 + with message-id and subject line Bug#1024409: Removed package(s) from unstable has caused the Debian Bug report #999301, regarding vsdump: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vsdump Version: 0.0.45-1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Version: 0.0.45-1+rm Dear submitter, as the package vsdump 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/1024409 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#999150: marked as done (cryptcat: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Sat, 19 Nov 2022 15:41:59 + with message-id and subject line Bug#1024406: Removed package(s) from unstable has caused the Debian Bug report #999150, regarding cryptcat: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cryptcat Version: 20031202-4 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Version: 20031202-4+rm Dear submitter, as the package cryptcat 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/1024406 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#998948: marked as done (ibam: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Sat, 19 Nov 2022 15:43:05 + with message-id and subject line Bug#1024408: Removed package(s) from unstable has caused the Debian Bug report #998948, regarding ibam: missing required debian/rules targets build-arch and/or build-indep 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.) -- 998948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ibam Version: 1:0.5.2-2.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Version: 1:0.5.2-2.1+rm Dear submitter, as the package ibam 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/1024408 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#998928: marked as done (scim-canna: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Sat, 19 Nov 2022 15:42:30 + with message-id and subject line Bug#1024407: Removed package(s) from unstable has caused the Debian Bug report #998928, regarding scim-canna: missing required debian/rules targets build-arch and/or build-indep 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.) -- 998928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scim-canna Version: 1.0.0-4.3 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Version: 1.0.0-4.3+rm Dear submitter, as the package scim-canna 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/1024407 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#965497: marked as done (dvbsnoop: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sat, 19 Nov 2022 15:44:02 + with message-id and subject line Bug#1024410: Removed package(s) from unstable has caused the Debian Bug report #965497, regarding dvbsnoop: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dvbsnoop Version: 1.4.50-5 Severity: normal Usertags: compat-5-6-removal Hi, The package dvbsnoop uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 1.4.50-5+rm Dear submitter, as the package dvbsnoop 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/1024410 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#965868: marked as done (vsdump: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sat, 19 Nov 2022 15:43:33 + with message-id and subject line Bug#1024409: Removed package(s) from unstable has caused the Debian Bug report #965868, regarding vsdump: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vsdump Version: 0.0.45-1 Severity: normal Usertags: compat-5-6-removal Hi, The package vsdump uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 0.0.45-1+rm Dear submitter, as the package vsdump 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/1024409 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#965470: marked as done (cryptcat: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sat, 19 Nov 2022 15:41:59 + with message-id and subject line Bug#1024406: Removed package(s) from unstable has caused the Debian Bug report #965470, regarding cryptcat: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cryptcat Version: 20031202-4 Severity: normal Usertags: compat-5-6-removal Hi, The package cryptcat uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 20031202-4+rm Dear submitter, as the package cryptcat 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/1024406 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#670935: marked as done ([PATCH] cryptcat: Helping to update to packaging format 3.0)
Your message dated Sat, 19 Nov 2022 15:41:59 +
with message-id
and subject line Bug#1024406: Removed package(s) from unstable
has caused the Debian Bug report #670928,
regarding [PATCH] cryptcat: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
670928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptcat
Severity: wishlist
Tags: patch
Hi,
The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:
http://wiki.debian.org/Projects/DebSrc3.0
I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.
Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.
Thanks,
Jari
>From d987e1519c3683ad6b0b1f0f62732b9a946a2c7b Mon Sep 17 00:00:00 2001
From: Jari Aalto
Date: Mon, 30 Apr 2012 17:20:52 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Signed-off-by: Jari Aalto
---
debian/changelog | 18 +---
debian/compat |2 +-
debian/control |9 +++---
debian/copyright | 10 +--
debian/patches/00list |2 --
debian/patches/{01_makefile => 01-makefile.patch} | 30
..._segfault => 02-fix-listen-mode-segfault.patch} |8 ++
debian/patches/series |2 ++
debian/rules | 11 ---
debian/source/format |1 +
10 files changed, 44 insertions(+), 49 deletions(-)
delete mode 100644 debian/patches/00list
rename debian/patches/{01_makefile => 01-makefile.patch} (62%)
rename debian/patches/{02_fix_listen_mode_segfault => 02-fix-listen-mode-segfault.patch} (65%)
create mode 100644 debian/patches/series
create mode 100644 debian/source/format
diff --git a/debian/changelog b/debian/changelog
index b045b64..727c8b4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+cryptcat (20031202-4.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+ * Update to Standards-Version to 3.9.3 and debhelper to 9.
+ * Add build-arch and build-indep targets; use dh_prep in rules file.
+ * Mark old upstream URL obsolete in copyright file.
+ * Fix copyright-without-copyright-notice (Lintian)
+ * Fix spelling-error-in-copyright (Lintian).
+ * Fix description-synopsis-starts-with-article (Lintian).
+ * Fix no-homepage-field (Lintian).
+
+ -- Jari Aalto Mon, 30 Apr 2012 17:15:07 +0300
+
cryptcat (20031202-4) unstable; urgency=low
* Removed "-s" in original Makefile to accomodate
@@ -91,7 +105,3 @@ cryptcat (0.0.950915-1) unstable; urgency=low
* Sent manpage upstream
-- Lars Bahner Wed, 11 Jul 2001 15:58:38 +0200
-
-Local variables:
-mode: debian-changelog
-End:
diff --git a/debian/compat b/debian/compat
index 7ed6ff8..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-5
+9
diff --git a/debian/control b/debian/control
index cc63036..25be9c3 100644
--- a/debian/control
+++ b/debian/control
@@ -2,13 +2,14 @@ Source: cryptcat
Section: net
Priority: optional
Maintainer: Lars Bahner
-Build-Depends: debhelper (>> 5.0.0), dpatch
-Standards-Version: 3.8.0
+Build-Depends: debhelper (>= 9)
+Standards-Version: 3.9.3
+Homepage: http://sourceforge.net/projects/cryptcat
Package: cryptcat
Architecture: any
-Depends: ${shlibs:Depends}
-Description: A lightweight version netcat extended with twofish encryption
+Depends: ${misc:Depends}, ${shlibs:Depends}
+Description: lightweight version netcat extended with twofish encryption
Cryptcat is a simple Unix utility which reads and writes data across
network connections, using TCP or UDP protocol while encrypting the
data being transmitted.
diff --git a/debian/copyright b/debian/copyright
index 9c116ed..575fb96 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -2,16 +2,20 @@ This package was debianized by Lars Bahner on
Bug#670928: marked as done ([PATCH] cryptcat: Helping to update to packaging format 3.0)
Your message dated Sat, 19 Nov 2022 15:41:59 +
with message-id
and subject line Bug#1024406: Removed package(s) from unstable
has caused the Debian Bug report #670928,
regarding [PATCH] cryptcat: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
670928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptcat
Severity: wishlist
Tags: patch
Hi,
The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:
http://wiki.debian.org/Projects/DebSrc3.0
I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.
Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.
Thanks,
Jari
>From d987e1519c3683ad6b0b1f0f62732b9a946a2c7b Mon Sep 17 00:00:00 2001
From: Jari Aalto
Date: Mon, 30 Apr 2012 17:20:52 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Signed-off-by: Jari Aalto
---
debian/changelog | 18 +---
debian/compat |2 +-
debian/control |9 +++---
debian/copyright | 10 +--
debian/patches/00list |2 --
debian/patches/{01_makefile => 01-makefile.patch} | 30
..._segfault => 02-fix-listen-mode-segfault.patch} |8 ++
debian/patches/series |2 ++
debian/rules | 11 ---
debian/source/format |1 +
10 files changed, 44 insertions(+), 49 deletions(-)
delete mode 100644 debian/patches/00list
rename debian/patches/{01_makefile => 01-makefile.patch} (62%)
rename debian/patches/{02_fix_listen_mode_segfault => 02-fix-listen-mode-segfault.patch} (65%)
create mode 100644 debian/patches/series
create mode 100644 debian/source/format
diff --git a/debian/changelog b/debian/changelog
index b045b64..727c8b4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+cryptcat (20031202-4.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+ * Update to Standards-Version to 3.9.3 and debhelper to 9.
+ * Add build-arch and build-indep targets; use dh_prep in rules file.
+ * Mark old upstream URL obsolete in copyright file.
+ * Fix copyright-without-copyright-notice (Lintian)
+ * Fix spelling-error-in-copyright (Lintian).
+ * Fix description-synopsis-starts-with-article (Lintian).
+ * Fix no-homepage-field (Lintian).
+
+ -- Jari Aalto Mon, 30 Apr 2012 17:15:07 +0300
+
cryptcat (20031202-4) unstable; urgency=low
* Removed "-s" in original Makefile to accomodate
@@ -91,7 +105,3 @@ cryptcat (0.0.950915-1) unstable; urgency=low
* Sent manpage upstream
-- Lars Bahner Wed, 11 Jul 2001 15:58:38 +0200
-
-Local variables:
-mode: debian-changelog
-End:
diff --git a/debian/compat b/debian/compat
index 7ed6ff8..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-5
+9
diff --git a/debian/control b/debian/control
index cc63036..25be9c3 100644
--- a/debian/control
+++ b/debian/control
@@ -2,13 +2,14 @@ Source: cryptcat
Section: net
Priority: optional
Maintainer: Lars Bahner
-Build-Depends: debhelper (>> 5.0.0), dpatch
-Standards-Version: 3.8.0
+Build-Depends: debhelper (>= 9)
+Standards-Version: 3.9.3
+Homepage: http://sourceforge.net/projects/cryptcat
Package: cryptcat
Architecture: any
-Depends: ${shlibs:Depends}
-Description: A lightweight version netcat extended with twofish encryption
+Depends: ${misc:Depends}, ${shlibs:Depends}
+Description: lightweight version netcat extended with twofish encryption
Cryptcat is a simple Unix utility which reads and writes data across
network connections, using TCP or UDP protocol while encrypting the
data being transmitted.
diff --git a/debian/copyright b/debian/copyright
index 9c116ed..575fb96 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -2,16 +2,20 @@ This package was debianized by Lars Bahner on
Bug#669862: marked as done ([PATCH] ibam: Helping to update to packaging format 3.0)
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #669862,
regarding [PATCH] ibam: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
669862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ibam
Severity: wishlist
Tags: patch
Hi,
The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:
http://wiki.debian.org/Projects/DebSrc3.0
I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.
Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.
Thanks,
Jari
>From 6fd5bfc551f989bc8817a2f06b3dcbb44cbd727d Mon Sep 17 00:00:00 2001
From: Jari Aalto
Date: Sat, 21 Apr 2012 16:30:06 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Signed-off-by: Jari Aalto
---
debian/README.source |2 --
debian/changelog | 15 +
debian/compat |2 +-
debian/control |5 ++---
debian/copyright |2 +-
debian/patches/00list |3 ---
.../{02deviation.dpatch => 02-deviation.patch} | 22 ++--
.../{03acpi-check.dpatch => 03-acpi-check.patch} |8 ++-
...5_sysfs_lenovo.dpatch => 05-sysfs-lenovo.patch} |8 ++-
debian/patches/10-makefile.patch | 18
debian/patches/series |4
.../{04sysfs.dpatch => unused/04-sysfs.patch} |8 ++-
debian/rules | 10 -
debian/source/format |1 +
debian/watch |3 +++
15 files changed, 66 insertions(+), 45 deletions(-)
delete mode 100644 debian/README.source
delete mode 100644 debian/patches/00list
rename debian/patches/{02deviation.dpatch => 02-deviation.patch} (70%)
rename debian/patches/{03acpi-check.dpatch => 03-acpi-check.patch} (73%)
rename debian/patches/{05_sysfs_lenovo.dpatch => 05-sysfs-lenovo.patch} (89%)
create mode 100644 debian/patches/10-makefile.patch
create mode 100644 debian/patches/series
rename debian/patches/{04sysfs.dpatch => unused/04-sysfs.patch} (89%)
create mode 100644 debian/source/format
create mode 100644 debian/watch
diff --git a/debian/README.source b/debian/README.source
deleted file mode 100644
index 5e94a7b..000
--- a/debian/README.source
+++ /dev/null
@@ -1,2 +0,0 @@
-This packages uses dpatch to manage differences between the upsteram and the
-Debian version.
diff --git a/debian/changelog b/debian/changelog
index 7b1e6b8..debf7be 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,18 @@
+ibam (1:0.5.2-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+ * Update to Standards-Version to 3.9.3 and debhelper to 9.
+ * Add build-arch and build-indep targets; use dh_prep in rules file.
+ * Patch 01: update with "quilt refresh" to make it apply cleanly.
+ * Patch 04: move to directory debian/patches/unused.
+ * Patch 10: new; fix makefile by removing unused linker flag.
+ * Fix debian-watch-file-is-missing (Lintian)
+ * Fix copyright-refers-to-symlink-license (Lintian).
+ * Fix binary-control-field-duplicates-source (Lintian).
+
+ -- Jari Aalto Sat, 21 Apr 2012 16:29:38 +0300
+
ibam (1:0.5.2-2) unstable; urgency=low
* added armhf to Architecture (closes: #604674)
diff --git a/debian/compat b/debian/compat
index 7f8f011..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-7
+9
diff --git a/debian/control b/debian/control
index 2567abf..99fff04 100644
--- a/debian/control
+++ b/debian/control
@@ -1,14 +1,13 @@
Source: ibam
Section: utils
Priority: optional
-Build-Depends: debhelper (>= 7.0.50), gkrellm (>= 2.1.4), libgtk2.0-dev, dpatch
Bug#664396: marked as done ([PATCH] vsdump: Helping to update to packaging format 3.0)
Your message dated Sat, 19 Nov 2022 15:43:33 +
with message-id
and subject line Bug#1024409: Removed package(s) from unstable
has caused the Debian Bug report #664396,
regarding [PATCH] vsdump: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
664396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vsdump
Severity: wishlist
Tags: patch
Hi,
The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:
http://wiki.debian.org/Projects/DebSrc3.0
I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.
Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.
Thanks,
Jari
>From b1cf85398925f4087ca5f728bb342018c656ec81 Mon Sep 17 00:00:00 2001
From: Jari Aalto
Date: Wed, 29 Feb 2012 04:39:24 -0500
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Signed-off-by: Jari Aalto
---
config.h |6 +++---
debian/changelog |8
debian/compat |2 +-
debian/control |4 ++--
debian/patches/00list |1 -
dpatch => 01_fix_path_chunks-parse-cmds.patch} |7 ++-
debian/patches/series |1 +
debian/rules | 13 ++---
8 files changed, 19 insertions(+), 23 deletions(-)
delete mode 100644 debian/patches/00list
rename debian/patches/{01_fix_path_chunks-parse-cmds.dpatch => 01_fix_path_chunks-parse-cmds.patch} (77%)
mode change 100755 => 100644
create mode 100644 debian/patches/series
diff --git a/config.h b/config.h
index 7bc2605..da85a8f 100644
--- a/config.h
+++ b/config.h
@@ -11,16 +11,16 @@
#define PACKAGE_NAME "vsdump"
/* Define to the full name and version of this package. */
-#define PACKAGE_STRING "vsdump 0.0.45"
+#define PACKAGE_STRING "vsdump 0.0.44"
/* Define to the one symbol short name of this package. */
#define PACKAGE_TARNAME "vsdump"
/* Define to the version of this package. */
-#define PACKAGE_VERSION "0.0.45"
+#define PACKAGE_VERSION "0.0.44"
/* Define to 1 if you have the ANSI C header files. */
#define STDC_HEADERS 1
/* Version number of package */
-#define VERSION "0.0.45"
+#define VERSION "0.0.44"
diff --git a/debian/changelog b/debian/changelog
index e37d6c3..5568e0f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+vsdump (0.0.45-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+ * Update to Standards-Version to 3.9.3 and debhelper to 9.
+
+ -- Jari Aalto Wed, 29 Feb 2012 04:37:20 -0500
+
vsdump (0.0.45-1) unstable; urgency=low
* New upstream release.
diff --git a/debian/compat b/debian/compat
index 1e8b314..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-6
+9
diff --git a/debian/control b/debian/control
index 1ad8aca..afdf3f1 100644
--- a/debian/control
+++ b/debian/control
@@ -2,8 +2,8 @@ Source: vsdump
Section: utils
Priority: extra
Maintainer: Juan Angulo Moreno
-Build-Depends: debhelper (>= 6), autotools-dev, pkg-config, libgsf-1-common, libglib2.0-0, libgsf-1-114, libgsf-1-dev, dpatch
-Standards-Version: 3.9.0
+Build-Depends: debhelper (>= 9), autotools-dev, pkg-config, libgsf-1-common, libglib2.0-0, libgsf-1-114, libgsf-1-dev
+Standards-Version: 3.9.3
Package: vsdump
Architecture: any
diff --git a/debian/patches/00list b/debian/patches/00list
deleted file mode 100644
index e5b0a84..000
--- a/debian/patches/00list
+++ /dev/null
@@ -1 +0,0 @@
-01_fix_path_chunks-parse-cmds.dpatch
diff --git a/debian/patches/01_fix_path_chunks-parse-cmds.dpatch b/debian/patches/01_fix_path_chunks-parse-cmds.patch
old mode 100755
new mode 100644
similarity index 77%
rename from debian/patches/01_fix_path_chunks-parse-cmds.dpatch
rename to debian/patches/01_fix_path_chunks-parse-cmds.patch
index 1ae0e59..2a2c733
---
Bug#1005986: marked as done (Please migrate away from dpatch)
Your message dated Sat, 19 Nov 2022 15:44:02 + with message-id and subject line Bug#1024410: Removed package(s) from unstable has caused the Debian Bug report #1005986, regarding Please migrate away from dpatch 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.) -- 1005986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dvbsnoop Version: 1.4.50-5 Severity: serious dpatch is deprecated and will be removed before the bookworm release. Please migrate to source format 3.0 (quilt) instead. --- End Message --- --- Begin Message --- Version: 1.4.50-5+rm Dear submitter, as the package dvbsnoop 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/1024410 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1005984: marked as done (Please migrate away from dpatch)
Your message dated Sat, 19 Nov 2022 15:42:30 + with message-id and subject line Bug#1024407: Removed package(s) from unstable has caused the Debian Bug report #1005984, regarding Please migrate away from dpatch 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.) -- 1005984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scim-canna Version: 1.0.0-4.3 Severity: serious dpatch is deprecated and will be removed before the bookworm release. Please migrate to source format 3.0 (quilt) instead. --- End Message --- --- Begin Message --- Version: 1.0.0-4.3+rm Dear submitter, as the package scim-canna 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/1024407 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1024443: asterisk-modules no longer includes chan_sip which breaks existing configs
Package: asterisk-modules Version: 1:20.0.0~dfsg+~cs6.12.40431414-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: james.bottom...@hansenpartnership.com The package asterisk-module no longer contains chan_sip.so which means that all existing SIP configuration with chan_sip stop functioning. I realise a migration to chan_pjsip is eventually required, but that requires at least notice of when chan_sip will be deprecated This actually seems to be a simple configuration error. chan_sip can be built by adding it to ADDONS_ENABLE in debian/rules -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages asterisk-modules depends on: ii libc-client2007e 8:2007f~dfsg-7+b2 ii libc6 2.36-5 ii libcodec2-1.0 1.0.5-1 ii libcurl4 7.86.0-1 ii libglib2.0-0 2.74.1-2 ii libgmime-3.0-03.2.13+dfsg-2 ii libgsm1 1.0.22-1 ii libical3 3.0.16-1+b1 ii libiksemel3 1.4-4 ii libjack0 [libjack-0.125] 1:0.126.0-1 ii libldap-2.5-0 2.5.13+dfsg-2+b1 ii liblua5.2-0 5.2.4-2 ii libneon27 0.32.4-1 ii libodbc2 2.3.11-2 ii libogg0 1.3.5-1 ii libopencore-amrnb00.1.6-1 ii libopencore-amrwb00.1.6-1 ii libopusfile0 0.12-2 ii libportaudio2 19.6.0-1.2 ii libpq515.1-1 ii libradcli41.2.11-1+b2 ii libresample1 0.1.3-5 ii libsnmp40 5.9.3+dfsg-1+b2 ii libspandsp2 0.0.6+dfsg-2 ii libspeex1 1.2.1-1 ii libspeexdsp1 1.2.1-1 ii libsqlite3-0 3.39.4-1 ii libsrtp2-12.4.2-3 ii libssl3 3.0.7-1 ii libsybdb5 1.3.6-1.1 ii libunbound8 1.17.0-1 ii libvo-amrwbenc0 0.1.3-2 ii libvorbis0a 1.3.7-1 ii libvorbisenc2 1.3.7-1 ii libvorbisfile31.3.7-1 ii libxml2 2.9.14+dfsg-1.1+b2 ii zlib1g1:1.2.11.dfsg-4.1 asterisk-modules recommends no packages. asterisk-modules suggests no packages. -- no debconf information
Bug#975931: marked as done (libllvm11: libgpuarray autopkgtest using pocl on armhf triggers segfault)
Your message dated Sat, 19 Nov 2022 15:36:25 + with message-id and subject line Bug#1000941: Removed package(s) from unstable has caused the Debian Bug report #975931, regarding libllvm11: libgpuarray autopkgtest using pocl on armhf triggers segfault 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.) -- 975931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pocl, libgpuarray Control: found -1 pocl/1.5-7 Control: found -1 libgpuarray/0.7.6-5 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of pocl the autopkgtest of libgpuarray fails in testing when that autopkgtest is run with the binary packages of pocl from unstable. It passes when run with only packages from testing. In tabular form: passfail pocl from testing1.5-7 libgpuarrayfrom testing0.7.6-5 all others from testingfrom testing I copied some of the output at the bottom of this report. There's not a hell of a lot to use for debugging. Currently this regression is blocking the migration of pocl to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=pocl https://ci.debian.net/data/autopkgtest/testing/amdhf/libg/libgpuarray/8423908/log.gz autopkgtest [20:16:04]: test command1: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; DEVICE=opencl0:0 $py -m nose -v pygpu.tests ; echo "Testing with $py-dbg:" ; DEVICE=opencl0:0 $py-dbg -m nose -v pygpu.tests ; done autopkgtest [20:16:04]: test command1: [--- Testing with python3.9: *** Testing for pthread-x-gene-1 mpi4py found: True runTest (pygpu.tests.test_basic.test_errors) ... ok pygpu.tests.test_basic.test_tril ... ok pygpu.tests.test_basic.test_triu ... ok pygpu.tests.test_blas.test_dot(1, 'float32', True, True, True, False) ... bash: line 1: 2439 Segmentation fault DEVICE=opencl0:0 $py -m nose -v pygpu.tests autopkgtest [20:16:16]: test command1: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 1:11.1.0-6+rm Dear submitter, as the package llvm-toolchain-11 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/1000941 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#853456: marked as done (ion: ftbfs with GCC-7)
Your message dated Sat, 19 Nov 2022 15:37:56 + with message-id and subject line Bug#1024339: Removed package(s) from unstable has caused the Debian Bug report #853456, regarding ion: ftbfs with GCC-7 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.) -- 853456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ion Version: 3.2.1+dfsg-1.1 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-7 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The severity of this report may be raised before the buster release. There is no need to fix this issue in time for the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc7-20170126/ion_3.2.1+dfsg-1.1_unstable_gcc7.log The last lines of the build log are at the end of this report. To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-7/porting_to.html [...] pod2man -s 3 -c "ICI library functions" ici/doc/pod3/sdrhash.pod ici/doc/sdrhash.3 pod2man -s 3 -c "ICI library functions" ici/doc/pod3/sdr.pod ici/doc/sdr.3 pod2man -s 1 -c "LTP executables" ltp/doc/pod1/ltpadmin.pod ltp/doc/ltpadmin.1 pod2man -s 1 -c "LTP executables" ltp/doc/pod1/ltpclock.pod ltp/doc/ltpclock.1 pod2man -s 1 -c "LTP executables" ltp/doc/pod1/ltpcounter.pod ltp/doc/ltpcounter.1 pod2man -s 1 -c "LTP executables" ltp/doc/pod1/ltpdriver.pod ltp/doc/ltpdriver.1 pod2man -s 1 -c "LTP executables" ltp/doc/pod1/ltpmeter.pod ltp/doc/ltpmeter.1 pod2man -s 1 -c "LTP executables" ltp/doc/pod1/udplsi.pod ltp/doc/udplsi.1 pod2man -s 1 -c "LTP executables" ltp/doc/pod1/udplso.pod ltp/doc/udplso.1 pod2man -s 1 -c "LTP executables" ltp/doc/pod1/dccplsi.pod ltp/doc/dccplsi.1 pod2man -s 1 -c "LTP executables" ltp/doc/pod1/dccplso.pod ltp/doc/dccplso.1 pod2man -s 5 -c "LTP configuration files" ltp/doc/pod5/ltprc.pod ltp/doc/ltprc.5 pod2man -s 3 -c "LTP library functions" ltp/doc/pod3/ltp.pod ltp/doc/ltp.3 pod2man -s 1 -c "DGR executables" dgr/doc/pod1/dgr2file.pod dgr/doc/dgr2file.1 pod2man -s 1 -c "DGR executables" dgr/doc/pod1/file2dgr.pod dgr/doc/file2dgr.1 pod2man -s 3 -c "DGR library functions" dgr/doc/pod3/dgr.pod dgr/doc/dgr.3 pod2man -s 1 -c "BP executables" bp/doc/pod1/bpadmin.pod bp/doc/bpadmin.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bpclock.pod bp/doc/bpclock.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bpcounter.pod bp/doc/bpcounter.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bpcancel.pod bp/doc/bpcancel.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bplist.pod bp/doc/bplist.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bpdriver.pod bp/doc/bpdriver.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bpecho.pod bp/doc/bpecho.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bpsendfile.pod bp/doc/bpsendfile.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bprecvfile.pod bp/doc/bprecvfile.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bpsink.pod bp/doc/bpsink.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bpsource.pod bp/doc/bpsource.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bpstats.pod bp/doc/bpstats.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/bptrace.pod bp/doc/bptrace.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/brsccla.pod bp/doc/brsccla.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/brsscla.pod bp/doc/brsscla.1 pod2man -s 1 -c "BP executables" bp/doc/pod1/dgrcla.pod bp/doc/dgrcla.1 cc1: all warnings being treated as errors Makefile:7655: recipe for target 'nm/shared/adm/nm_mgr-adm_bp.o' failed make[4]: *** [nm/shared/adm/nm_mgr-adm_bp.o] Error 1 make[4]: *** Waiting for unfinished jobs make[4]: Leaving directory '/<>/ion-3.2.1+dfsg' Makefile:8841: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/<>/ion-3.2.1+dfsg' Makefile:3246: recipe for target 'all' failed make[2]:
