Bug#1054937: marked as done (haskell-hakyll: FTBFS: unsatisfiable build-dependencies: libghc-fsnotify-dev (< 0.4), libghc-optparse-applicative-dev (< 0.17), libghc-pandoc-dev (>= 2.11), libghc-pandoc-
Your message dated Fri, 01 Dec 2023 07:19:01 + with message-id and subject line Bug#1054937: fixed in haskell-hakyll 4.16.2.0-2 has caused the Debian Bug report #1054937, regarding haskell-hakyll: FTBFS: unsatisfiable build-dependencies: libghc-fsnotify-dev (< 0.4), libghc-optparse-applicative-dev (< 0.17), libghc-pandoc-dev (>= 2.11), libghc-pandoc-dev (< 2.18), libghc-pandoc-prof, libghc-vector-dev (< 0.13), libghc-pandoc-doc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-hakyll Version: 4.15.1.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: haskell-devscripts (>= 0.13), cdbs, debhelper (>= 10), > ghc (>= 8.4.3), ghc-prof, libghc-aeson-dev, libghc-aeson-prof, > libghc-blaze-html-dev (>= 0.5), libghc-blaze-html-dev (<< 0.10), > libghc-blaze-html-prof, libghc-blaze-markup-dev (>= 0.5.1), > libghc-blaze-markup-dev (<< 0.9), libghc-blaze-markup-prof, > libghc-data-default-dev (>= 0.4), libghc-data-default-dev (<< 0.8), > libghc-data-default-prof, libghc-file-embed-dev (>= 0.0.10.1), > libghc-file-embed-dev (<< 0.0.16), libghc-file-embed-prof, > libghc-fsnotify-dev (>= 0.2), libghc-fsnotify-dev (<< 0.4), > libghc-fsnotify-prof, libghc-hashable-dev (>= 1.0), libghc-hashable-dev (<< > 2), libghc-hashable-prof, libghc-http-conduit-dev (>= 2.2), > libghc-http-conduit-dev (<< 2.4), libghc-http-conduit-prof, > libghc-http-types-dev (>= 0.9), libghc-http-types-dev (<< 0.13), > libghc-http-types-prof, libghc-lifted-async-dev (>= 0.10), > libghc-lifted-async-dev (<< 1), libghc-lifted-async-prof, libghc-lrucache-dev > (>= 1.1.1), libghc-lrucache-dev (<< 1.3), libghc-lrucache-prof, > libghc-network-uri-dev (>= 2.6), libghc-network-uri-dev (<< 2.7), > libghc-network-uri-prof, libghc-optparse-applicative-dev (>= 0.12), > libghc-optparse-applicative-dev (<< 0.17), libghc-optparse-applicative-prof, > libghc-pandoc-dev (>= 2.11), libghc-pandoc-dev (<< 2.18), libghc-pandoc-prof, > libghc-random-dev (>= 1.0), libghc-random-dev (<< 1.3), libghc-random-prof, > libghc-regex-tdfa-dev (>= 1.1), libghc-regex-tdfa-dev (<< 1.4), > libghc-regex-tdfa-prof, libghc-resourcet-dev (>= 1.1), libghc-resourcet-dev > (<< 1.3), libghc-resourcet-prof, libghc-scientific-dev (<< 0.4), > libghc-scientific-dev (>= 0.3.4), libghc-scientific-prof, libghc-tagsoup-dev > (>= 0.13.1), libghc-tagsoup-dev (<< 0.15), libghc-tagsoup-prof, > libghc-test-framework-dev (<< 0.9), libghc-test-framework-dev (>= 0.4), > libghc-test-framework-hunit-dev (<< 0.4), libghc-test-framework-hunit-dev (>= > 0.3), libghc-test-framework-quickcheck2-dev (<< 0.4), > libghc-test-framework-quickcheck2-dev (>= 0.3), libghc-time-locale-compat-dev > (<< 0.2), libghc-time-locale-compat-dev (>= 0.1), > libghc-time-locale-compat-prof, libghc-unordered-containers-dev (<< 0.3), > libghc-unordered-containers-dev (>= 0.2), libghc-unordered-containers-prof, > libghc-vector-dev (>= 0.11), libghc-vector-dev (<< 0.13), libghc-vector-prof, > libghc-wai-dev (>= 3.2), libghc-wai-dev (<< 3.3), libghc-wai-prof, > libghc-wai-app-static-dev (>= 3.1), libghc-wai-app-static-dev (<< 3.2), > libghc-wai-app-static-prof, libghc-warp-dev (>= 3.2), libghc-warp-dev (<< > 3.4), libghc-warp-prof, libghc-yaml-dev (>= 0.8.11), libghc-yaml-dev (<< > 0.12), libghc-yaml-prof, libghc-quickcheck2-dev (>= 2.8), > libghc-quickcheck2-dev (<< 2.15), libghc-quickcheck2-prof, libghc-tasty-dev > (>= 0.11), libghc-tasty-dev (<< 1.5), libghc-tasty-prof, > libghc-tasty-golden-dev (>= 2.3), libghc-tasty-golden-dev (<< 2.4), > libghc-tasty-golden-prof, libghc-tasty-hunit-dev (>= 0.9), > libghc-tasty-hunit-dev (<< 0.11), libghc-tasty-quickcheck-dev (>= 0.8), > libghc-tasty-quickcheck-dev (<< 0.11), build-essential, fakeroot, ghc-doc, > libghc-aeson-doc, libghc-blaze-html-doc, libghc-blaze-markup-doc, > libghc-data-default-doc, libghc-file-embed-doc, libghc-fsnotify-doc, > libghc-hashable-doc, libghc-http-conduit-doc,
Bug#1057148: marked as done (python-dbusmock/0.30.0-1 autopkg tests are failing)
Your message dated Fri, 01 Dec 2023 07:04:30 + with message-id and subject line Bug#1057148: fixed in python-dbusmock 0.30.0-2 has caused the Debian Bug report #1057148, regarding python-dbusmock/0.30.0-1 autopkg tests are failing 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.) -- 1057148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-dbusmock Version: 0.30.0-1 Severity: serious Tags: sid trixie python-dbusmock/0.30.0-1 autopkg tests are failing: [...] 1428s autopkgtest [12:44:58]: test upstream: [--- 1433s ...dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Activating service name='org.TestSession' requested by ':1.0' (uid=1000 pid=1717 comm="python3 test_api.py" label="unconfined") 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Successfully activated service 'org.TestSession' 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s ..dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s .dbus-daemon[1748]: [system] Reloaded configuration 1433s dbus-daemon[1748]: [system] Activating service name='org.TestSystem' requested by ':1.0' (uid=1000 pid=1717 comm="python3 test_api.py" label="unconfined") 1433s dbus-daemon[1748]: [system] Successfully activated service 'org.TestSystem' 1433s dbus-daemon[1748]: [system] Reloaded configuration 1433s dbus-daemon[1748]: [system] Reloaded configuration 1433s .dbus-daemon[1748]: [system] Reloaded configuration 1433s dbus-daemon[1748]: [system] Reloaded configuration 1433s dbus-daemon[1748]: [system] Reloaded configuration 1435s ... 1435s -- 1435s Ran 42 tests in 6.080s 1435s 1435s OK 1435s Traceback (most recent call last): 1435s File "/tmp/autopkgtest.gGVLMr/build.Dnb/src/tests/test_api_pytest.py", line 14, in 1435s import pytest 1435s ModuleNotFoundError: No module named 'pytest' 1435s autopkgtest [12:45:05]: test upstream: ---] --- End Message --- --- Begin Message --- Source: python-dbusmock Source-Version: 0.30.0-2 Done: Martin Pitt We believe that the bug you reported is fixed in the latest version of python-dbusmock, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated python-dbusmock package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Dec 2023 06:45:16 + Source: python-dbusmock Architecture: source Version: 0.30.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Martin Pitt Closes: 1057148 Changes: python-dbusmock (0.30.0-2) unstable; urgency=medium . * Add missing python3-pytest autopkgtest dependency (Closes: #1057148) Checksums-Sha1: bd620e49de3eea82d71f6bb6ae5513f9c8dab440 2316 python-dbusmock_0.30.0-2.dsc 3da05fc1c72d6aed66ef6e10622379e7a9bba3bf 7432 python-dbusmock_0.30.0-2.debian.tar.xz 7e931cdffb099bdcce95a2a4a4d56f60e4a8a664 6108 python-dbusmock_0.30.0-2_source.buildinfo Checksums-Sha256: aa8a3d7b4332faf0d5461f6dcb50561af4335c39e2b166c1ee581cf34ba22bbe 2316 python-dbusmock_0.30.0-2.dsc 919462c9303a8431c14b7c8b71a2452208913c5a5243050eb9d3a85e4d6aaac0 7432 python-dbusmock_0.30.0-2.debian.tar.xz 545da59248d8a87c3e231655e764b08e938b6c0642f8d2db438178f4e1ccd22b 6108 python-dbusmock_0.30.0-2_source.buildinfo Files: 37eb3f29fedd0215691d0ac556249901 2316 python optional python-dbusmock_0.30.0-2.dsc beda8dd0bef8b7afd322e5eed70dd5c1 7432 python optional python-dbusmock_0.30.0-2.debian.tar.xz 130134c8d6ca41551ac4ae078b8967cc 6108 python optional python-dbusmock_0.30.0-2_source.buildinfo -BEGIN PGP
Processed: Bug#1057148 marked as pending in python-dbusmock
Processing control commands: > tag -1 pending Bug #1057148 [src:python-dbusmock] python-dbusmock/0.30.0-1 autopkg tests are failing Added tag(s) pending. -- 1057148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057148: marked as pending in python-dbusmock
Control: tag -1 pending Hello, Bug #1057148 in python-dbusmock 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/python-dbusmock/-/commit/122e5ff6f4274db2d91fe315bb4a2bc78dcc5e69 Add missing python3-pytest autopkgtest dependency Closes: #1057148 (this message was generated automatically) -- Greetings https://bugs.debian.org/1057148
Bug#1057178: marked as done (FTBFS: unsatisfiable build-deps in testing on mdds and liborcus)
Your message dated Fri, 1 Dec 2023 06:51:17 +0100 with message-id and subject line has caused the Debian Bug report #1057178, regarding FTBFS: unsatisfiable build-deps in testing on mdds and liborcus 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.) -- 1057178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libreoffice Version: 4:7.5.9~rc1-1 Severity: serious Tags: wontfix trixie Hi, apparently mdds 2.1/liborcus 0.19 migrated to testing even though Build-Depends clearly say libmdds-dev (<< 2.1~), libmdds-dev (>= 2.0), and liborcus-dev (<< 0.18~), liborcus-dev (>= 0.17.2), and testings LO depending on liborcus-0.17.0. The latter is probably due to the smooth transitions, but the former now causes this to be unbuildable. Filing for documentation purposes. Obviously fixed in sid, thankfully 4:7.5.9~rc1-1 is the end of a branch. Regards, Rene --- End Message --- --- Begin Message --- Version: 4:7.6.0~beta1-1--- End Message ---
Bug#1057178: FTBFS: unsatisfiable build-deps in testing on mdds and liborcus
Source: libreoffice Version: 4:7.5.9~rc1-1 Severity: serious Tags: wontfix trixie Hi, apparently mdds 2.1/liborcus 0.19 migrated to testing even though Build-Depends clearly say libmdds-dev (<< 2.1~), libmdds-dev (>= 2.0), and liborcus-dev (<< 0.18~), liborcus-dev (>= 0.17.2), and testings LO depending on liborcus-0.17.0. The latter is probably due to the smooth transitions, but the former now causes this to be unbuildable. Filing for documentation purposes. Obviously fixed in sid, thankfully 4:7.5.9~rc1-1 is the end of a branch. Regards, Rene
Processed: user debian...@lists.debian.org, usertagging 1053331, affects 1053331
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 1053331 piuparts There were no usertags set. Usertags are now: piuparts. > affects 1053331 + bettercap-caplets Bug #1053331 [src:bettercap-caplets] bettercap-caplets: Unsatisfiable dependency on bettercap-ui Added indication that 1053331 affects bettercap-caplets > thanks Stopping processing here. Please contact me if you need assistance. -- 1053331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057174: python3-diagrams: depends on no longer available python3-typed-ast
Package: python3-diagrams Version: 0.23.4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: python3-diagrams : Depends: python3-typed-ast but it is not installable python3-typed-ast has recently disappeared from sid: https://bugs.debian.org/1051802 Cheers, Andreas
Bug#1056897: [3dprinter-general] Bug#1056897: FTBFS: Plater.cpp:5313: error: call of overloaded ‘load_files?=()=?UTF-8?Q?’ is ambiguous
On 11/30/23 16:34, Gregor Riepl wrote: Hi Aaron, Simon is uploading the new packaging to the DELAYED/1 queue. It should arrive in the archive on November 30. If you are a maintainer of slic3r-prusa, you can review the new packaging in the mean time and reject or fast-track it as you see fit. Thanks a lot for this! The NMU is building right now. Unfortunately, it looks like a new issue cropped up that curiously didn't happen to me during testing: [1] ./tests/arrange/test_arrange.cpp:935: FAILED: REQUIRE_THAT( score, WithinRel(0., EPSILON) ) with expansion: -0.0 and 0 are within 0.01% of each other Sounds like the EPSILON value is not appropriate for this test, or WithinRel has problems with negative zero (or near-zero). Gah, looks like some arch-dependent glitch. Which explains why it didn't happen to either of us (we probably both used amd64 machines, I definitely did) and then the failure did happen upon publishing. Thanks for your help, I'll try to help get the next fix in once it's ready. I'll investigate this issue as soon as I can. Regards, Gregor [1] https://buildd.debian.org/status/fetch.php?pkg=slic3r-prusa=arm64=2.6.1%2Bdfsg-4.1=1701382946=0 -- Aaron Rainbolt Lubuntu Developer Matrix: @arraybolt3:matrix.org IRC: arraybolt3 on irc.libera.chat GitHub: https://github.com/ArrayBolt3
Bug#1056897: [3dprinter-general] Bug#1056897: FTBFS: Plater.cpp:5313: error: call of overloaded ‘load_files?=()=?UTF-8?Q?’ is ambiguous
Hi Aaron, Simon is uploading the new packaging to the DELAYED/1 queue. It should arrive in the archive on November 30. If you are a maintainer of slic3r-prusa, you can review the new packaging in the mean time and reject or fast-track it as you see fit. Thanks a lot for this! The NMU is building right now. Unfortunately, it looks like a new issue cropped up that curiously didn't happen to me during testing: [1] ./tests/arrange/test_arrange.cpp:935: FAILED: REQUIRE_THAT( score, WithinRel(0., EPSILON) ) with expansion: -0.0 and 0 are within 0.01% of each other Sounds like the EPSILON value is not appropriate for this test, or WithinRel has problems with negative zero (or near-zero). I'll investigate this issue as soon as I can. Regards, Gregor [1] https://buildd.debian.org/status/fetch.php?pkg=slic3r-prusa=arm64=2.6.1%2Bdfsg-4.1=1701382946=0
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052309 [src:lirc] lirc FTBFS when systemd.pc changes systemdsystemunitdir Severity set to 'serious' from 'important' -- 1052309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052984 [src:deviceinfo] deviceinfo FTBFS when systemd.pc changes systemdsystemunitdir Severity set to 'serious' from 'important' -- 1052984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1053111 [src:e2fsprogs] e2fsprogs FTBFS when systemd.pc changes systemdsystemunitdir Severity set to 'serious' from 'important' -- 1053111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052983 [src:bluez] bluez FTBFS when systemd.pc changes systemdsystemunitdir Severity set to 'serious' from 'important' -- 1052983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052644 [src:kmscon] kmscon FTBFS when systemd.pc changes systemdsystemunitdir Severity set to 'serious' from 'important' -- 1052644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052666 [src:lvm2] lvm2 FTBFS when systemd.pc changes systemdsystemunitdir Severity set to 'serious' from 'important' -- 1052666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052664 [src:ntpsec] ntpsec FTBFS when systemd.pc changes systemdsystemunitdir Severity set to 'serious' from 'important' -- 1052664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052639 [src:hfd-service] hfd-service FTBFS when systemd.pc changes systemdsystemunitdir Severity set to 'serious' from 'important' -- 1052639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052632 [src:clevis] clevis FTBFS when systemd.pc changes systemdsystemunitdir Severity set to 'serious' from 'important' -- 1052632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052643 [src:intel-hdcp] intel-hdcp FTBFS when systemd.pc changes systemdsystemunitdir Severity set to 'serious' from 'important' -- 1052643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052380 [src:opensm] opensm FTBFS when systemdsystemunitdir changes in systemd.pc Severity set to 'serious' from 'important' -- 1052380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052310 [src:plymouth] plymouth FTBFS when systemdsystemunitdir changes in systemd.pc Severity set to 'serious' from 'important' -- 1052310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bumping severity to serious
Processing control commands: > severity -1 serious Bug #1052277 [src:heartbeat] heartbeat FTBFS when systemd_system_unit_dir changes Severity set to 'serious' from 'important' -- 1052277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057171: libitext5-java: FTBFS with bouncycastle 1.77
Source: libitext5-java Version: 5.5.13.3-2 Severity: serious Tags: ftbfs sid User: a...@debian.org Usertags: bouncycastle-1.77 X-Debbugs-Cc: a...@debian.org Dear maintainer, libitext5-java fails to build from source with bouncycastle 1.77. The reason is the removal of long deprecated methods. The (hopefully) relevant error message from the build log. BUILD FAILURE [INFO] [INFO] Total time: 12.832 s [INFO] Finished at: 2023-11-30T13:27:49+01:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler- plugin:3.10.1:compile (default-compile) on project itextpdf: Compilation failure: Compilation failure: [ERROR] /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja va:[223,95] cannot find symbol [ERROR] symbol: method getObject() [ERROR] location: class org.bouncycastle.asn1.ASN1TaggedObject [ERROR] /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja va:[246,109] cannot find symbol [ERROR] symbol: method getObject() [ERROR] location: class org.bouncycastle.asn1.ASN1TaggedObject [ERROR] /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja va:[346,70] cannot find symbol [ERROR] symbol: method getObject() [ERROR] location: variable tg of type org.bouncycastle.asn1.ASN1TaggedObject [ERROR] /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja va:[350,70] cannot find symbol [ERROR] symbol: method getObject() [ERROR] location: variable tg of type org.bouncycastle.asn1.ASN1TaggedObject [ERROR] /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja va:[1286,28] cannot find symbol [ERROR] symbol: method getObject() [ERROR] location: variable tag of type org.bouncycastle.asn1.ASN1TaggedObject [ERROR] /<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.ja va:[1287,48] cannot find symbol [ERROR] symbol: method getObject() [ERROR] location: variable tag of type org.bouncycastle.asn1.ASN1TaggedObject [ERROR] /<>/itext/src/main/java/com/itextpdf/text/pdf/security/Certificate Util.java:[123,67] incompatible types: org.bouncycastle.asn1.ASN1IA5String cannot be converted to org.bouncycastle.asn1.DERIA5String [ERROR] -> [Help 1] [ERROR] signature.asc Description: This is a digitally signed message part
Bug#1057170: ssl-utils-clojure: FTBFS with bouncycastle 1.77
Source: ssl-utils-clojure Version: 3.5.0-2 Severity: serious Tags: ftbfs sid User: a...@debian.org Usertags: bouncycastle-1.77 X-Debbugs-Cc: a...@debian.org Dear maintainer, ssl-utils-clojure fails to build from source with bouncycastle 1.77. The reason is the removal of long deprecated methods. The (hopefully) relevant error message from the build log. lein jar Compiling 2 source files to /<>/target/classes /<>/src/java/com/puppetlabs/ssl_utils/ExtensionsUtils.java:632: error: cannot find symbol return asn1ObjToObj(taggedObj.getObject()); ^ symbol: method getObject() location: variable taggedObj of type ASN1TaggedObject 1 error Compilation of Java sources(lein javac) failed. make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:11: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --- - signature.asc Description: This is a digitally signed message part
Processed: comskip: diff for NMU version 0.82.009+git20230112.d0cc422+ds.1-2.1
Processing control commands: > tags 1041376 + patch Bug #1041376 [src:comskip] comskip: FTBFS with ffmpeg 6.0 Added tag(s) patch. > tags 1041376 + pending Bug #1041376 [src:comskip] comskip: FTBFS with ffmpeg 6.0 Added tag(s) pending. -- 1041376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057169: pdftk-java: FTBFS with bouncycastle 1.77
Source: pdftk-java Version: 3.3.3-1 Severity: serious Tags: ftbfs sid User: a...@debian.org Usertags: bouncycastle-1.77 X-Debbugs-Cc: a...@debian.org Dear maintainer, pdftk-java fails to build from source with bouncycastle 1.77. The reason is the removal of long deprecated methods. The (hopefully) relevant error message from the build log. [javac] /<>/java/com/gitlab/pdftk_java/com/lowagie/text/pdf/PdfPKCS7.java: 228: error: cannot find symbol [javac] ASN1Sequence content = (ASN1Sequence)((DERTaggedObject)signedData.getObjectAt(1)).getObject(); [javac] ^ [javac] symbol: method getObject() [javac] location: class DERTaggedObject [javac] /<>/java/com/gitlab/pdftk_java/com/lowagie/text/pdf/PdfPKCS7.java: 261: error: cannot find symbol [javac] DEROctetString rsaDataContent = (DEROctetString)((DERTaggedObject)rsaData.getObjectAt(1)).getObject(); [javac] ^ [javac] symbol: method getObject() [javac] location: class DERTaggedObject [javac] /<>/java/com/gitlab/pdftk_java/com/lowagie/text/pdf/PdfPKCS7.java: 297: error: cannot find symbol [javac] ASN1Sequence sseq = (ASN1Sequence)tagsig.getObject(); [javac] ^ [javac] symbol: method getObject() [javac] location: variable tagsig of type ASN1TaggedObject [javac] /<>/java/com/gitlab/pdftk_ signature.asc Description: This is a digitally signed message part
Bug#1041376: comskip: diff for NMU version 0.82.009+git20230112.d0cc422+ds.1-2.1
Control: tags 1041376 + patch Control: tags 1041376 + pending Dear maintainer, I've prepared an NMU for comskip (versioned as 0.82.009+git20230112.d0cc422+ds.1-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru comskip-0.82.009+git20230112.d0cc422+ds.1/debian/changelog comskip-0.82.009+git20230112.d0cc422+ds.1/debian/changelog --- comskip-0.82.009+git20230112.d0cc422+ds.1/debian/changelog 2023-01-13 11:35:18.0 +0100 +++ comskip-0.82.009+git20230112.d0cc422+ds.1/debian/changelog 2023-11-30 22:56:06.0 +0100 @@ -1,3 +1,10 @@ +comskip (0.82.009+git20230112.d0cc422+ds.1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches: Fix build with ffmpeg 6 (Closes: #1041376) + + -- Sebastian Ramacher Thu, 30 Nov 2023 22:56:06 +0100 + comskip (0.82.009+git20230112.d0cc422+ds.1-2) unstable; urgency=medium [ Debian Janitor ] diff -Nru comskip-0.82.009+git20230112.d0cc422+ds.1/debian/patches/ffmpeg-6.patch comskip-0.82.009+git20230112.d0cc422+ds.1/debian/patches/ffmpeg-6.patch --- comskip-0.82.009+git20230112.d0cc422+ds.1/debian/patches/ffmpeg-6.patch 1970-01-01 01:00:00.0 +0100 +++ comskip-0.82.009+git20230112.d0cc422+ds.1/debian/patches/ffmpeg-6.patch 2023-11-30 22:54:14.0 +0100 @@ -0,0 +1,18 @@ +--- a/comskip.h b/comskip.h +@@ -8,3 +8,15 @@ + + #define MAXWIDTH 8000 + #define MAXHEIGHT 4800 ++ ++#if defined(__INTEL_COMPILER) && __INTEL_COMPILER < 1110 || defined(__SUNPRO_C) ++#define DECLARE_ALIGNED(n,t,v) t __attribute__ ((aligned (n))) v ++#elif defined(__DJGPP__) ++#define DECLARE_ALIGNED(n,t,v) t __attribute__ ((aligned (FFMIN(n, 16 v ++#elif defined(__GNUC__) || defined(__clang__) ++#define DECLARE_ALIGNED(n,t,v) t __attribute__ ((aligned (n))) v ++#elif defined(_MSC_VER) ++#define DECLARE_ALIGNED(n,t,v) __declspec(align(n)) t v ++#else ++#define DECLARE_ALIGNED(n,t,v) t v ++#endif diff -Nru comskip-0.82.009+git20230112.d0cc422+ds.1/debian/patches/series comskip-0.82.009+git20230112.d0cc422+ds.1/debian/patches/series --- comskip-0.82.009+git20230112.d0cc422+ds.1/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ comskip-0.82.009+git20230112.d0cc422+ds.1/debian/patches/series 2023-11-30 22:52:13.0 +0100 @@ -0,0 +1 @@ +ffmpeg-6.patch
Bug#1056059: marked as done (dracut: systemd 255: dracut fails to boot due to lack of systemd-executor)
Your message dated Thu, 30 Nov 2023 21:57:52 + with message-id and subject line Bug#1056059: fixed in dracut 059+212-1 has caused the Debian Bug report #1056059, regarding dracut: systemd 255: dracut fails to boot due to lack of systemd-executor 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.) -- 1056059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dracut Version: 059-4 Severity: important Dear Maintainer, dracut will fail to produce a booting initrd since systemd 255 in Debian trixie. The reason is that /usr/lib/systemd/systemd-executor is missing from the initrd image. The corresponding patch is: https://github.com/dracutdevs/dracut/pull/2535/files This can also be worked around by creating /etc/dracut.conf.d/99-systemd-dracut-bug.conf: install_items+=" /usr/lib/systemd/systemd-executor " ... and then running dpkg-reconfigure dracut again. $ apt show systemd Package: systemd Version: 255~rc2-1 Thanks! Matteo Settenvini -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-4-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dracut depends on: ii dracut-core 059-4 dracut recommends no packages. Versions of packages dracut suggests: pn dracut-network -- no debconf information --- End Message --- --- Begin Message --- Source: dracut Source-Version: 059+212-1 Done: Thomas Lange We believe that the bug you reported is fixed in the latest version of dracut, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Lange (supplier of updated dracut 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, 30 Nov 2023 22:10:02 +0100 Source: dracut Architecture: source Version: 059+212-1 Distribution: unstable Urgency: low Maintainer: Thomas Lange Changed-By: Thomas Lange Closes: 1016052 1041562 1054400 1056059 Changes: dracut (059+212-1) unstable; urgency=low . * merge upstream changes, Closes: #1056059, #1041562, #1054400, #1016052 Checksums-Sha1: 7fa50548bcee3290cfa4a232664bd6119b826020 2318 dracut_059+212-1.dsc c730124772b6d781c47566953d9d4d721992e65e 379172 dracut_059+212.orig.tar.xz 9c0970657f220c34fb96dd82f1881986d4d3cb29 15704 dracut_059+212-1.debian.tar.xz 07dfeedcd1441ee6086c891bcf083597c730cd55 9245 dracut_059+212-1_amd64.buildinfo Checksums-Sha256: d8ecd9ff2d4b5a0954fe867cb09a8a2a5be936a30865e7667562735febe61151 2318 dracut_059+212-1.dsc 74ebb69e0bdbd9d960f9909b446a26d02eb584c623d748fa5a22fd6c5b2be183 379172 dracut_059+212.orig.tar.xz 7e644439db104e1a6bb3432acf6d2f6f73cfbc627f800db5897d9c40ab4f2649 15704 dracut_059+212-1.debian.tar.xz 79cf8a788771cc38fb6da0e8fee67230c01a3e67bd2845340bd97b332ab639f7 9245 dracut_059+212-1_amd64.buildinfo Files: 7e7f6eb3527a378bb6be8a5261bdc9f3 2318 utils optional dracut_059+212-1.dsc 8061d5a3b712693c912a4e6614986b7d 379172 utils optional dracut_059+212.orig.tar.xz 0d60f52a398ad4367a22c38f8dbacc0a 15704 utils optional dracut_059+212-1.debian.tar.xz 1b6c94a0747fe9f5e668123dd2334b1e 9245 utils optional dracut_059+212-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEsR7jJz9rLetSjJPaK/jZ/gdLzeQFAmVo+r8RHGxhbmdlQGRl Ymlhbi5vcmcACgkQK/jZ/gdLzeSTnw/+LcH1Y6IQs1peK1v+seO+4XBuBf8JePWH uHpDqcZwiQx2K4nwQX7+bjubpNf2mjL/B/uuNPEtyu6L/PlKsagZXVJVCs+aUXV+ J2aDCeRp71R34JqiemmVQsn1jQwcsq7QdEee4eGNcpYwHbkIOQAyJrOGpj+/dmQo UDIB7zjbgDAAyEXQoK6LJiOiWl5I/Kx9Eim546SMVFRN+kTNbAIyRW5MnXlaXgXj 1xM/O4q6OlBrGiUIvf5vsM0N1xwiAvFW7mebxox47tECqdgVZ6QnDcREqn6/DsPS 7wVnKfDl1j9pJlwKGJYH71vdBLDdkaHrTJYIYfsZeYR+FRm7LV8UFZqrNzSh/cEB 0ZgY5adtj9zoiEgNCWTcPRAPG2lB2u1gxNeYRNQ4xXyisAVZ9HXz8Zb57r5aGY8E
Bug#1057168: jdeb: FTBFS with bouncycastle 1.77
Source: jdeb Version: 1.9-1 Severity: serious Tags: ftbfs sid User: a...@debian.org Usertags: bouncycastle-1.77 X-Debbugs-Cc: a...@debian.org Dear maintainer, jdeb fails to build from source with bouncycastle 1.77. The reason is the removal of long deprecated methods. The (hopefully) relevant error message from the build log. ERROR] Failures: [ERROR] PGPSignerTestCase.testClearSign:79->Assert.assertEquals:146- >Assert.assertEquals:117 expected:<...[] -END PGP SIGNAT...> but was:<...[Sek] -END PGP SIGNAT...> [INFO] [ERROR] Tests run: 90, Failures: 1, Errors: 0, Skipped: 0 [INFO] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 14.039 s [INFO] Finished at: 2023-11-30T13:32:26+01:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire- plugin:2.22.3:test (default-test) on project jdeb: There are test failures. [ERROR] [ERROR] Please refer to /<>/target/surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date].dump, [date]- jvmRun[N].dump and [date].dumpstream. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [0m[0mdh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> - Dclassworlds.conf=/etc/maven/m2-debian.conf - Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings- debian.xml -Ddebian.dir=/<>/debian - Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test returned exit code 1 make: *** [debian/rules:6: build] Error 25 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 signature.asc Description: This is a digitally signed message part
Bug#1057167: libapache-poi-java: FTBFS with bouncycastle 1.77
Source: libapache-poi-java Version: 4.0.1-4 Severity: serious Tags: ftbfs sid User: a...@debian.org Usertags: bouncycastle-1.77 X-Debbugs-Cc: a...@debian.org Dear maintainer, libapache-poi-java fails to build from source with bouncycastle 1.77. The reason is the removal of long deprecated methods. The (hopefully) relevant error message from the build log. ompile-ooxml: [javac] Compiling 589 source files to /<>/build/ooxml-classes [javac] Ignoring source, target and bootclasspath as release has been set [javac] /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/facets/XAdESXLS ignatureFacet.java:235: error: cannot find symbol [javac] ASN1OctetString keyHashOctetString = (ASN1OctetString)derTaggedObject.getObject(); [javac] ^ [javac] symbol: method getObject() [javac] location: variable derTaggedObject of type DERTaggedObject [javac] /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/facets/XAdESXLS ignatureFacet.java:239: error: cannot find symbol [javac] X500Name name = X500Name.getInstance(derTaggedObject.getObject()); [javac] ^ [javac] symbol: method getObject() [javac] location: variable derTaggedObject of type DERTaggedObject [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/SignaturePart.j ava uses unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 2 errors BUILD FAILED /<>/build.xml:1133: Compile failed; see the compiler error output for details. signature.asc Description: This is a digitally signed message part
Bug#1057166: pgpainless: FTBFS with bouncycastle 1.77
Source: pgpainless Version: 1.3.16-2 Severity: serious Tags: ftbfs sid User: a...@debian.org Usertags: bouncycastle-1.77 X-Debbugs-Cc: a...@debian.org Dear maintainer, pgpainless fails to build from source with bouncycastle 1.77. The reason is the removal of long deprecated methods. The (hopefully) relevant error message from the build log. It seems, in this case, just a test is failing now. Failures (1): JUnit Jupiter:CertifyCertificateTest:testKeyDelegation() MethodSource [className = 'org.pgpainless.key.certification.CertifyCertificateTest', methodName = 'testKeyDelegation', methodParameterTypes = ''] => org.pgpainless.exception.SignatureValidationException: Cannot verify direct-key signature correctness org.pgpainless.signature.consumer.SignatureValidator$17.verify(SignatureValidat or.java:547) org.pgpainless.signature.consumer.SignatureVerifier.verifyDirectKeySignature(Si gnatureVerifier.java:328) org.pgpainless.key.certification.CertifyCertificateTest.testKeyDelegation(Certi fyCertificateTest.java:98) java.base/java.lang.reflect.Method.invoke(Method.java:568) java.base/java.util.ArrayList.forEach(ArrayList.java:1511) [...] Caused by: org.bouncycastle.openpgp.PGPException: signature is not a key binding signature. org.bouncycastle.openpgp.PGPSignature.verifyCertification(Unknown Source) org.pgpainless.signature.consumer.SignatureValidator$17.verify(SignatureValidat or.java:539) [...] Test run finished after 44748 ms [ 240 containers found ] [ 0 containers skipped] [ 240 containers started] [ 0 containers aborted] [ 240 containers successful ] [ 0 containers failed ] [ 732 tests found ] [ 1 tests skipped ] [ 731 tests started ] [ 0 tests aborted ] [ 730 tests successful ] [ 1 tests failed ] signature.asc Description: This is a digitally signed message part
Bug#1057165: libitext-java: FTBFS with bouncycastle 1.77
Source: libitext-java
Version: 2.1.7-14
Severity: serious
Tags: ftbfs sid
User: a...@debian.org
Usertags: bouncycastle-1.77
X-Debbugs-Cc: a...@debian.org
Dear maintainer,
libitext-java fails to build from source with bouncycastle 1.77. The reason
is the removal of long deprecated methods. The (hopefully) relevant
error message from the build log.
compile:
[mkdir] Created dir: /<>/build/bin
[javac] /<>/ant/compile.xml:45: warning: 'includeantruntime'
was not set, defaulting to build.sysclasspath=last; set to false for repeatable
builds
[javac] Using javac -source 1.5 is no longer supported, switching to 7
[javac] Using javac -target 1.5 is no longer supported, switching to 7
[javac] Compiling 359 source files to /<>/build/bin
[javac] warning: [options] bootstrap class path not set in conjunction with
-source 7
[javac] warning: [options] source value 7 is obsolete and will be removed
in a future release
[javac] warning: [options] target value 7 is obsolete and will be removed
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use
-Xlint:-options.
[javac]
/<>/core/com/lowagie/text/pdf/MappedRandomAccessFile.java:58:
warning: [removal] AccessController in java.security has been deprecated and
marked for removal
[javac] import java.security.AccessController;
[javac] ^
[javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:356:
error: cannot find symbol
[javac] if (tag.getObject() instanceof ASN1Sequence) {
[javac]^
[javac] symbol: method getObject()
[javac] location: variable tag of type ASN1TaggedObject
[javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:357:
error: cannot find symbol
[javac] seq = (ASN1Sequence)tag.getObject();
[javac]^
[javac] symbol: method getObject()
[javac] location: variable tag of type ASN1TaggedObject
[javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:403:
error: cannot find symbol
[javac] ASN1Sequence content =
(ASN1Sequence)((DERTaggedObject)signedData.getObjectAt(1)).getObject();
[javac]
^
[javac] symbol: method getObject()
[javac] location: class DERTaggedObject
[javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:435:
error: cannot find symbol
[javac] DEROctetString rsaDataContent =
(DEROctetString)((DERTaggedObject)rsaData.getObjectAt(1)).getObject();
[javac]
^
[javac] symbol: method getObject()
[javac] location: class DERTaggedObject
[javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:488:
error: cannot find symbol
[javac] ASN1Sequence seqin =
(ASN1Sequence)tg.getObject();
[javac] ^
[javac] symbol: method getObject()
[javac] location: variable tg of type ASN1TaggedObject
[javac] /<>/core/com/lowagie/text/pdf/FontDetails.java:264:
warning: [removal] Integer(int) in Integer has been deprecated and marked for
removal
[javac] Integer codeKey = new Integer(code);
[javac] ^
[javac]
/<>/core/com/lowagie/text/pdf/TrueTypeFontUnicode.java:144:
warning: [removal] Integer(int) in Integer has been deprecated and marked for
removal
[javac] inverseCmap.put(new
Integer(metrics[0]), code);
[javac] ^
[javac]
/<>/core/com/lowagie/text/pdf/TrueTypeFontUnicode.java:150:
warning: [removal] Integer(int) in Integer has been deprecated and marked for
removal
[javac] return inverseCmap == null ? null : (Integer)
inverseCmap.get(new Integer(code));
[javac]
^
[javac]
/<>/core/com/lowagie/text/pdf/MappedRandomAccessFile.java:203:
warning: [removal] AccessController in java.security has been deprecated and
marked for removal
[javac] Boolean b = (Boolean) AccessController.doPrivileged(new
PrivilegedAction() {
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 5 errors
[javac] 9 warnings
signature.asc
Description: This is a digitally signed message part
Bug#1057162: jglobus: FTBFS with bouncycastle 1.77
Source: jglobus Version: 2.1.0-8.1 Severity: serious Tags: ftbfs sid User: a...@debian.org Usertags: bouncycastle-1.77 X-Debbugs-Cc: a...@debian.org Dear maintainer, jglobus fails to build from source with bouncycastle 1.77. The reason is the removal of long deprecated methods. The (hopefully) relevant error message from the build log. [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /<>/ssl-proxies/src/main/java/org/globus/gsi/proxy/ext/ProxyPolicy.java:[63,46] cannot find symbol symbol: method getObject() location: class org.bouncycastle.asn1.DERTaggedObject [INFO] 1 error
Bug#1053686: pandoc: cannot fulfill the build dependencies
On Sun, 26 Nov 2023, Scott Talbert wrote: On Sat, 25 Nov 2023, Jonas Smedegaard wrote: Quoting Scott Talbert (2023-11-25 19:09:39) On Thu, 23 Nov 2023, Jonas Smedegaard wrote: Quoting Ilias Tsitsimpis (2023-11-23 21:10:36) On Fri, Nov 17, 2023 at 09:28AM, Ilias Tsitsimpis wrote: On Thu, Nov 16, 2023 at 10:16PM, Jonas Smedegaard wrote: Quoting John MacFarlane (2023-11-16 19:25:17) Removing lua support would be most unfortunate! If you need help from upstream in getting things to work, let me know. I agree: Pandoc with its core scripting language disabled is a severely crippled Pandoc. Understood, but I am not really sure how to move forward, since Pandoc doesn't fully support the latest Stackage LTS. I can help with packaging/upgrade libraries if you can provide the right set of libraries we need. I uploaded the following packages: * haskell-hslua-cli_v1.3.0-1, * haskell-hslua-module-doclayout_v1.1.0-1 * haskell-hslua-module-zip_v1.1.0-1 I believe the next step is to update pandoc to 3.0.1, so we can then package pandoc-lua-engine, pandoc-server and eventually pandoc-cli. Jonas, how can I help move this forward? Pandoc is the last blocker to finish the Haskell transition. I think this will be the best way forward: Haskell team introduces new source package haskell-pandoc. When available, I can build package pandoc depending on it. I really don't like breaking upstream project pandoc into two Debian source packages like that, but I don't have the energy at the moment to try fix dh-haskell (which I suspect will be similar work as I am doing to dh-cargo currently). I'm working on this (packaging haskell-pandoc). And it's been uploaded, headed to NEW. Jonas, haskell-pandoc has been accepted into unstable, so I think you should be able to update src:pandoc to now build from the pandoc-cli hackage package. This brings up an interesting question, though. The pandoc-cli package versioning does not follow that of the pandoc package, so it's unclear how to best handle that with the existing numbering of src:pandoc and pandoc binary package. Regards, Scott
Bug#1056897: marked as done (FTBFS: Plater.cpp:5313: error: call of overloaded ‘load_files()’ is ambiguous)
Your message dated Thu, 30 Nov 2023 21:22:10 +
with message-id
and subject line Bug#1056897: fixed in slic3r-prusa 2.6.1+dfsg-4.1
has caused the Debian Bug report #1056897,
regarding FTBFS: Plater.cpp:5313: error: call of overloaded
‘load_files()’ is ambiguous
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.)
--
1056897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slic3r-prusa
Version: 2.6.1+dfsg-4
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: onit...@gmail.com
Hi,
During a recent upload, PrusaSlicer failed to build due to incompatible chanes
in wxWidgets 3.2.
These changes include support for initializer lists, which clashes with some
overloads in the
PrusaSlicer source code. The errors are as follows:
src/slic3r/GUI/Plater.cpp: In member function ‘void
Slic3r::GUI::Plater::load_project(const wxString&)’:
src/slic3r/GUI/Plater.cpp:5313:21: error: call of overloaded
‘load_files()’ is ambiguous
5313 | if (! load_files({ into_path(filename) }).empty()) {
| ~~^
In file included from src/slic3r/GUI/Plater.cpp:20:
src/slic3r/GUI/Plater.hpp:193:25: note: candidate: ‘std::vector Slic3r::GUI::Plater::load_files(const
std::vector&, bool, bool, bool)’
193 | std::vector load_files(const
std::vector& input_files, bool load_model = true, bool
load_config = true, bool imperial_units = false);
| ^~
src/slic3r/GUI/Plater.hpp:197:10: note: candidate: ‘bool
Slic3r::GUI::Plater::load_files(const wxArrayString&, bool)’
197 | bool load_files(const wxArrayString& filenames, bool
delete_after_load = false);
| ^~
and
src/slic3r/GUI/PhysicalPrinterDialog.cpp: In member function 'void
Slic3r::GUI::PhysicalPrinterDialog::build_printhost_settings(Slic3r::GUI::ConfigOptionsGroup*)':
src/slic3r/GUI/PhysicalPrinterDialog.cpp:465:27: error: call of overloaded
'set_values()' is ambiguous
465 | choice->set_values({ m_config->opt_string("printhost_port") });
| ~~^~~~
In file included from src/slic3r/GUI/ConfigManipulation.hpp:16,
from src/slic3r/GUI/Tab.hpp:50,
from src/slic3r/GUI/PhysicalPrinterDialog.cpp:28:
src/slic3r/GUI/Field.hpp:381:33: note: candidate: 'void
Slic3r::GUI::Choice::set_values(const
std::vector >&)'
381 | voidset_values(const
std::vector );
| ^~
src/slic3r/GUI/Field.hpp:382:33: note: candidate: 'void
Slic3r::GUI::Choice::set_values(const wxArrayString&)'
382 | voidset_values(const wxArrayString );
| ^~
These issues can be worked around with an explicit instantiation of the
std::vector.
A better solution would be a change to wxWidgets, by making the initializer
list constructor explicit.
A patch will follow shortly.
Regards,
Gregor
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (300,
'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-4-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: slic3r-prusa
Source-Version: 2.6.1+dfsg-4.1
Done: Aaron Rainbolt
We believe that the bug you reported is fixed in the latest version of
slic3r-prusa, 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 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aaron Rainbolt (supplier of updated slic3r-prusa
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
Processed: Re: clang-17: ClangTargets.cmake cannot find libclang-17.so.1
Processing control commands: > severity -1 serious Bug #1057151 [clang-17] clang-17: ClangTargets.cmake cannot find libclang-17.so.1 Severity set to 'serious' from 'normal' -- 1057151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057122: initscripts has an undeclared file conflict on /usr/lib/udev/hwclock-set
Helmut,
Thanks for this
On Tue, Nov 28, 2023 at 10:27:41AM +0100, Helmut Grohne wrote:
> Package: initscripts
> Version: 3.08-3~bpo12+1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fileconflict
> Control: affects -1 + util-linux
> Tags: bookworm
>
> initscripts has an undeclared file conflict. This may result in an
> unpack error from dpkg.
>
> The file /usr/lib/udev/hwclock-set is contained in the packages
> * initscripts/3.08-3~bpo12+1 as present in bookworm-backports
> * util-linux/2.36.1-8+deb11u1 as present in bullseye|bullseye-security
Are the suites and versions reported here really the problematic ones?
I agree there is a conflict, but I think it is between
initscripts/3.08-3~bpo12+1 in bookworm-backports and util-linux-extra/2.38.1-5
in bookworm.
My proposed fix is attached. It reverts the transition of the hwclock machinery
to initscripts, since this is still present in bookworm src:util-linux.
Or, have I misunderstood?
Best wishes,
Mark
diff --git a/debian/control b/debian/control
index 551b7abc..02bfe1b5 100644
--- a/debian/control
+++ b/debian/control
@@ -99,15 +99,12 @@ Multi-Arch: foreign
Depends:
sysvinit-utils (>= 3.05-1),
sysv-rc | file-rc | openrc,
- util-linux-extra,
${misc:Depends},
Recommends:
e2fsprogs,
psmisc,
Breaks: udev (<< 254.3-1),
- util-linux-extra (<< 2.39.2-2.1~)
Replaces: udev (<< 254.3-1),
- util-linux-extra (<< 2.39.2-2.1~)
Description: scripts for initializing and shutting down the system
The scripts in this package initialize a standard Debian
system at boot time and shut it down at halt or reboot time.
diff --git a/debian/initscripts.postinst b/debian/initscripts.postinst
index 0074f2a3..eb126710 100755
--- a/debian/initscripts.postinst
+++ b/debian/initscripts.postinst
@@ -42,7 +42,7 @@ INITSCRIPTS="mountkernfs.sh mount-configfs brightness
hostname.sh mountdevsubfs.
checkroot-bootclean.sh checkfs.sh mountall.sh mountall-bootclean.sh \
mountnfs.sh mountnfs-bootclean.sh bootmisc.sh urandom halt reboot \
udev umountroot umountfs umountnfs.sh sendsigs killprocs single motd \
- bootlogs rc.local rmnologin hwclock.sh"
+ bootlogs rc.local rmnologin"
for F in $INITSCRIPTS; do
if [ -x /etc/init.d/$F ]; then
diff --git a/debian/initscripts.postrm b/debian/initscripts.postrm
index 25bbb932..e53672dc 100755
--- a/debian/initscripts.postrm
+++ b/debian/initscripts.postrm
@@ -9,7 +9,7 @@ INITSCRIPTS="mountkernfs.sh mount-configfs brightness
hostname.sh mountdevsubfs.
checkroot-bootclean.sh checkfs.sh mountall.sh mountall-bootclean.sh \
mountnfs.sh mountnfs-bootclean.sh bootmisc.sh urandom halt reboot \
udev umountroot umountfs umountnfs.sh sendsigs killprocs single motd \
- bootlogs rc.local rmnologin hwclock.sh"
+ bootlogs rc.local rmnologin"
case "$1" in
purge)
diff --git a/debian/src/initscripts/Makefile b/debian/src/initscripts/Makefile
index 5da80089..b13eafa3 100644
--- a/debian/src/initscripts/Makefile
+++ b/debian/src/initscripts/Makefile
@@ -34,9 +34,6 @@ install:
$(INSTALL) -d $(DESTDIR)$(sbindir)/.
$(INSTALL) sbin/fsck.nfs $(DESTDIR)$(sbindir)/fsck.nfs
- $(INSTALL_DATA) -Dt $(DESTDIR)/usr/lib/udev/rules.d
usr/lib/udev/rules.d/hwclock.rules
- $(INSTALL) usr/lib/udev/hwclock-set $(DESTDIR)/usr/lib/udev/hwclock-set
-
$(INSTALL) -d $(DESTDIR)/usr/share/man/man8
$(INSTALL_DATA) man/fsck.nfs.8 \
$(DESTDIR)/usr/share/man/man8/fsck.nfs.8
diff --git a/debian/src/initscripts/etc/default/hwclock
b/debian/src/initscripts/etc/default/hwclock
deleted file mode 100644
index 44b04312..
--- a/debian/src/initscripts/etc/default/hwclock
+++ /dev/null
@@ -1,2 +0,0 @@
-# Settings for the hwclock init script.
-# See hwclock(5) for supported settings.
diff --git a/debian/src/initscripts/etc/init.d/hwclock.sh
b/debian/src/initscripts/etc/init.d/hwclock.sh
deleted file mode 100644
index a9872b64..
--- a/debian/src/initscripts/etc/init.d/hwclock.sh
+++ /dev/null
@@ -1,57 +0,0 @@
-#!/bin/sh
-
-### BEGIN INIT INFO
-# Provides: hwclock
-# Required-Start:
-# Required-Stop: mountdevsubfs
-# Should-Stop: umountfs
-# Default-Start: S
-# Default-Stop: 0 6
-# Short-Description: Save system clock to hardware on shutdown.
-### END INIT INFO
-
-# Note: this init script and related code is only useful if you
-# run a sysvinit system, without NTP synchronization.
-
-if [ -e /run/systemd/system ] ; then
-exit 0
-fi
-
-unset TZ
-
-hwclocksh()
-{
-HCTOSYS_DEVICE=rtc0
-[ ! -x /sbin/hwclock ] && return 0
-[ ! -r /etc/default/rcS ] || . /etc/default/rcS
-[ ! -r /etc/default/hwclock ] || . /etc/default/hwclock
-
-. /lib/lsb/init-functions
-verbose_log_action_msg() { [ "$VERBOSE" = no ] || log_action_msg "$@"; }
-
-case "$1" in
-start)
-# start is handled by /usr/lib/udev/rules.d/85-hwclock.rules.
-
Bug#1057155: vonsh REJECT on amd64
Source: vonsh Version: 1.0-0.1 Severity: serious X-Debbugs-Cc: b...@debian.org Reason: Version check failed: Your upload included the binary package vonsh, version 1.0-0.1, for amd64, however testing already has version 1.0+b1. Uploads to unstable must have a higher version than present in testing. REJECT
Processed: severity of 1038076 is serious
Processing commands for cont...@bugs.debian.org: > severity 1038076 serious Bug #1038076 [src:ocamlsdl] ocamlsdl: Is a language binding for an obsolete version of SDL Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1038076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to sysvinit, tagging 1057122
Processing commands for cont...@bugs.debian.org: > limit source sysvinit Limiting to bugs with field 'source' containing at least one of 'sysvinit' Limit currently set to 'source':'sysvinit' > tags 1057122 + pending Bug #1057122 [initscripts] initscripts has an undeclared file conflict on /usr/lib/udev/hwclock-set Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1057122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1054932
Processing commands for cont...@bugs.debian.org: > close 1054932 Bug #1054932 [src:haskell-swish] haskell-swish: FTBFS: unsatisfiable build-dependencies: libghc-array-dev-0.5.4.0-0b6fa, libghc-base-dev-4.15.1.0-6a406, libghc-bytestring-dev-0.10.12.1-ced9a, libghc-hashable-dev-1.3.5.0-3fad8, libghc-text-dev-1.2.5.0-8553e, libghc-unordered-containers-dev-0.2.17.0-1d16d, haddock-interface-38, libghc-array-prof-0.5.4.0-0b6fa, libghc-base-prof-4.15.1.0-6a406, libghc-bytestring-prof-0.10.12.1-ced9a, libghc-hashable-prof-1.3.5.0-3fad8, libghc-text-prof-1.2.5.0-8553e, libghc-unordered-containers-prof-0.2.17.0-1d16d Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1054932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054284: marked as done (xscorch: Segmentation fault)
Your message dated Thu, 30 Nov 2023 18:58:44 + with message-id and subject line Bug#1054288: Removed package(s) from unstable has caused the Debian Bug report #1054284, regarding xscorch: Segmentation fault 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.) -- 1054284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xscorch Severity: grave Version: 0.2.1-1+nmu6 Running xscorch on sid/i386 gives the following segfault, preventing the program from starting: #0 0x00441792 in shashlist_insert_by_int (list=0x4c84c0, data=0x4cf950, class=2, key=1) at shashlist.c:202 #1 0x00411fec in sc_registry_add_by_int (registry=0x4c84b0, data=0x4cf950, class=2, key=1) at sregistry.c:101 #2 0x0041797b in _sc_accessory_read_item (ac=0x4cdd90, reader=0x4cdd10, item=0x4ccca0) at saddconf.c:137 #3 0x004182fe in sc_addconf_append_file (type=SC_ADDCONF_ACCESSORIES, filename=0x449ec0 "/usr/share/games/xscorch//accessories.def", container=0x4cdd90) at saddconf.c:458 #4 0x004174e0 in sc_accessory_config_create (c=0x4be840) at saccessory.c:366 #5 0x00406502 in sc_config_new (argc=0xb120, argv=0xb124) at sconfig.c:186 #6 0x00406048 in main (argc=, argv=) at xscorch.c:86 --- End Message --- --- Begin Message --- Version: 0.2.1-1+nmu6+rm Dear submitter, as the package xscorch 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/1054288 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1054840: marked as done (haskell-random-source: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25)
Your message dated Thu, 30 Nov 2023 18:56:44 +
with message-id
and subject line Bug#1054496: Removed package(s) from unstable
has caused the Debian Bug report #1054840,
regarding haskell-random-source: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
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.)
--
1054840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-random-source
Version: 0.3.0.11-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-random-source-doc.substvars
> dh_installdirs -plibghc-random-source-doc \
>
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'make_setup_recipe'
> Running ghc --make Setup.lhs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.lhs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'configure_recipe'
> Running find . ! -newer /tmp/VqnBFXN1pm -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-random-source-dev
> libghc-random-source-prof
> libghc-random-source-doc
> Running dh_listpackages
> libghc-random-source-dev
> libghc-random-source-prof
> libghc-random-source-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
> --haddockdir=/usr/lib/ghc-doc/haddock/random-source-0.3.0.11/
> --datasubdir=random-source
> --htmldir=/usr/share/doc/libghc-random-source-doc/html/
> --enable-library-profiling
> Using Parsec parser
> Configuring random-source-0.3.0.11...
> Flags chosen: base4=True, mtl2=True
> Dependency base >=4 && <5: using base-4.17.2.0
> Dependency flexible-defaults >=0.0.0.2: using flexible-defaults-0.0.3
> Dependency mersenne-random-pure64: using mersenne-random-pure64-0.2.2.0
> Dependency mtl >=2 && <3: using mtl-2.2.2
> Dependency mwc-random: using mwc-random-0.15.0.2
> Dependency primitive: using primitive-0.8.0.0
> Dependency random >=1.2.0 && <1.3: using random-1.2.1.1
> Dependency stateref >=0.3 && <0.4: using stateref-0.3
> Dependency syb: using syb-0.7.2.4
> Dependency template-haskell: using template-haskell-2.19.0.0
> Dependency th-extras: using th-extras-0.0.0.6
> Source component graph: component lib
> Configured component graph:
> component random-source-0.3.0.11-CPnrTi8UKmI2LUX1LaGb3J
> include base-4.17.2.0
> include flexible-defaults-0.0.3-KFvhARZBLCOBba1iTrgx1d
> include mersenne-random-pure64-0.2.2.0-3bJvbdZXsQkBjIh9GURJ3k
> include mtl-2.2.2
> include mwc-random-0.15.0.2-5v49xpOEU6WFI3BQ1ublFP
> include primitive-0.8.0.0-LlEyZnmQ2mlGS0nNflVSqQ
> include random-1.2.1.1-Aatha6E6c0aE6gEWaLlLCn
> include stateref-0.3-21fwDCeEkQ5IAXqad2E21C
> include syb-0.7.2.4-URkW17Cd7D7rpu7G0BDIE
> include template-haskell-2.19.0.0
> include th-extras-0.0.0.6-9JCEX3123VjFpaB83xMotc
> Linked component graph:
> unit random-source-0.3.0.11-CPnrTi8UKmI2LUX1LaGb3J
> include base-4.17.2.0
> include flexible-defaults-0.0.3-KFvhARZBLCOBba1iTrgx1d
> include mersenne-random-pure64-0.2.2.0-3bJvbdZXsQkBjIh9GURJ3k
> include mtl-2.2.2
> include mwc-random-0.15.0.2-5v49xpOEU6WFI3BQ1ublFP
> include primitive-0.8.0.0-LlEyZnmQ2mlGS0nNflVSqQ
> include random-1.2.1.1-Aatha6E6c0aE6gEWaLlLCn
> include stateref-0.3-21fwDCeEkQ5IAXqad2E21C
> include syb-0.7.2.4-URkW17Cd7D7rpu7G0BDIE
> include template-haskell-2.19.0.0
> include th-extras-0.0.0.6-9JCEX3123VjFpaB83xMotc
>
>
Bug#1054836: marked as done (haskell-cipher-des: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25)
Your message dated Thu, 30 Nov 2023 18:55:55 +
with message-id
and subject line Bug#1054499: Removed package(s) from unstable
has caused the Debian Bug report #1054836,
regarding haskell-cipher-des: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
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.)
--
1054836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-cipher-des
Version: 0.0.6-11
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-cipher-des-doc.substvars
> dh_installdirs -plibghc-cipher-des-doc \
>
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'configure_recipe'
> Running find . ! -newer /tmp/bFTy0iCrr_ -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-cipher-des-dev
> libghc-cipher-des-prof
> libghc-cipher-des-doc
> Running dh_listpackages
> libghc-cipher-des-dev
> libghc-cipher-des-prof
> libghc-cipher-des-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
> --haddockdir=/usr/lib/ghc-doc/haddock/cipher-des-0.0.6/
> --datasubdir=cipher-des --htmldir=/usr/share/doc/libghc-cipher-des-doc/html/
> --enable-library-profiling --enable-tests
> Using Parsec parser
> Configuring cipher-des-0.0.6...
> Dependency base >=4 && <5: using base-4.17.2.0
> Dependency byteable: using byteable-0.1.1
> Dependency bytestring: using bytestring-0.11.5.2
> Dependency crypto-cipher-types >=0.0.3 && <0.1: using
> crypto-cipher-types-0.0.9
> Dependency securemem >=0.1.2: using securemem-0.1.10
> Dependency QuickCheck >=2: using QuickCheck-2.14.3
> Dependency base >=4 && <5: using base-4.17.2.0
> Dependency byteable: using byteable-0.1.1
> Dependency bytestring: using bytestring-0.11.5.2
> Dependency cipher-des: using cipher-des-0.0.6
> Dependency crypto-cipher-tests: using crypto-cipher-tests-0.0.11
> Dependency crypto-cipher-types: using crypto-cipher-types-0.0.9
> Dependency test-framework >=0.3.3: using test-framework-0.8.2.0
> Dependency test-framework-quickcheck2 >=0.2.9: using
> test-framework-quickcheck2-0.3.0.5
> Source component graph:
> component lib
> component test:test-cipher-des dependency lib
> Configured component graph:
> component cipher-des-0.0.6-J4iJofhZDV4El4dC7oG1HH
> include base-4.17.2.0
> include byteable-0.1.1-IqNqKPqTApI9aYZC1xb5GB
> include bytestring-0.11.5.2
> include crypto-cipher-types-0.0.9-7QznYxW7ATC1a01iQPlbfE
> include securemem-0.1.10-5ic4bqTTxHpA1HhPdeWrry
> component cipher-des-0.0.6-LRlg3iCQt0pAHr1Tw5qsmu-test-cipher-des
> include QuickCheck-2.14.3-BmeqZc5o1KN1SLTJnQ4VO3
> include base-4.17.2.0
> include byteable-0.1.1-IqNqKPqTApI9aYZC1xb5GB
> include bytestring-0.11.5.2
> include cipher-des-0.0.6-J4iJofhZDV4El4dC7oG1HH
> include crypto-cipher-tests-0.0.11-ysUaALYTD36Xq3Jys2hGc
> include crypto-cipher-types-0.0.9-7QznYxW7ATC1a01iQPlbfE
> include test-framework-0.8.2.0-3iFahy3v2iClaMAyMHfWA
> include test-framework-quickcheck2-0.3.0.5-4BHchnnNAoZ8GoDQFSXhMG
> Linked component graph:
> unit cipher-des-0.0.6-J4iJofhZDV4El4dC7oG1HH
> include base-4.17.2.0
> include byteable-0.1.1-IqNqKPqTApI9aYZC1xb5GB
> include bytestring-0.11.5.2
> include crypto-cipher-types-0.0.9-7QznYxW7ATC1a01iQPlbfE
> include securemem-0.1.10-5ic4bqTTxHpA1HhPdeWrry
>
>
Bug#1054444: marked as done (golang-github-facebook-ent: include non free font Calibre)
Your message dated Thu, 30 Nov 2023 18:51:28 + with message-id and subject line Bug#1054504: Removed package(s) from unstable has caused the Debian Bug report #105, regarding golang-github-facebook-ent: include non free font Calibre 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.) -- 105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-facebook-ent Version: 0.5.4-3 Severity: serious Tags: ftbfs Justification: FTBFS Control: block -1 by 1054426 Dear Maintainer, The documentation is build with docusaurus. See website directory https://sources.debian.org/src/golang-github-facebook-ent/0.5.4-3/doc/website/ You should repack or package docusaurus and rebuild Bastien signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Version: 0.5.4-3+rm Dear submitter, as the package golang-github-facebook-ent 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/1054504 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1057149: marked as done (gimp: Please add Conflicts+Replaces: gimp-dds)
Your message dated Thu, 30 Nov 2023 18:50:58 + with message-id and subject line Bug#1057149: fixed in gimp 2.10.36-2 has caused the Debian Bug report #1057149, regarding gimp: Please add Conflicts+Replaces: gimp-dds 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.) -- 1057149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gimp Version: 2.10.12-1 Severity: serious gimp-dds was included in 2.10.10, and the old version of the plugin in gimp-dds is also vulnerable to CVE-2023-1. Please add[1] Conflicts: gimp-dds Replaces: gimp-dds to get rid of the stale version of this plugin. A fast upload would be appreciated so that I can also submit this change for the next bookworm (and bullseye) point releases. Thanks in advance [1] https://lists.debian.org/deity/2023/11/msg00037.html --- End Message --- --- Begin Message --- Source: gimp Source-Version: 2.10.36-2 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of gimp, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated gimp 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, 30 Nov 2023 13:21:31 -0500 Source: gimp Built-For-Profiles: noudeb Architecture: source Version: 2.10.36-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1057149 Changes: gimp (2.10.36-2) unstable; urgency=medium . [ Jarred Wilson ] * Add upstream metadata . [ Jeremy Bícha ] * Add Conflicts/Replaces: gimp-dds. Thanks to Adrian Bunk (Closes: #1057149) * Stop using debian/control.in and dh-sequence-gnome * Remove an obsolete maintscript entry * Bump Standards-Version to 4.6.2 Checksums-Sha1: 30377657429355c02103a3ba24101d0a79871e42 3454 gimp_2.10.36-2.dsc e7666e8daae5e92103522cd03f60cf2b196a07d2 58068 gimp_2.10.36-2.debian.tar.xz 2720fb9589990e5cfbca33c4279a56d782dbace2 15369 gimp_2.10.36-2_source.buildinfo Checksums-Sha256: 53e588d30a197f3f0ebfdeb0384d711274c002d966ead07f8f474ebb12514b38 3454 gimp_2.10.36-2.dsc 7cad7d9134ffca90f0c0178e21398b3eace71d4b52c2337983acaa485233963c 58068 gimp_2.10.36-2.debian.tar.xz 9d2f11af09207b7e1a2e4e2158868acb2dad120b6a368ff6bd71db896aed267a 15369 gimp_2.10.36-2_source.buildinfo Files: 455e109c8251a92e612121690df78f83 3454 graphics optional gimp_2.10.36-2.dsc 2d67f76ea2ff34735123cb1adf11e0b0 58068 graphics optional gimp_2.10.36-2.debian.tar.xz 466ac3cb1c14d4b367281eece473045e 15369 graphics optional gimp_2.10.36-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmVo0zYACgkQ5mx3Wuv+ bH1rWw//WRTMId4KAHDfOCW99/ULeCjoOfUT6b9zXe7FqYV5tULsVdycHV0tecgc azrSDdZr/hbxpF5ivhqSKq7L06Bxtu86dEZc2/XhJJJPbP5Cw6BxPxPuoFOc4Dfa POMrXWvkd9quHwPQ3K5v2nzP4HIZInkoaungj+0DWPafGa0fohztXp4jNW8iDgmV SzEURrI6m1XaIob4MbiQbSgEy6V6T570lBG7g1BiRj/MjZXZb9h6sULWDv2NPCGR EmIl7hGMdjxv8nUAqjWHKkgJSi0cReGdkLlwujFWhxv795X5aRuu/2Inkc693P6U m53Ohr7811qIQU0aTqVnDO9BqbG4jCVw9d+FUMdFBs7n9AA5pocpBhnXHhx3p21U lwnB1+I9aT+SUcuF5MoDfgnCQH7WLGP9Poi5BX/28i4VgNprNJWpvhaBDr/evHHc fK6ua04pw9xm482ePjVugOIDbag9/P4yRoiIaaf/ROx7SOhdi4zElVIJuf8JE4D7 JWmaxzEdSD3RoqXjsIC2xeXvH8nQ9zQwVPaAVn8/h2KnLDzXP4yCWOaDQ5Pck7xS ymBcaWmSlWJF009BJi3WqdE69rqE+Bs8tMUGLgVnTz72MaTBhnmfsNHWuxy+aYpm jYaz7BzDILd2iKsRhg7iU7hT539EWJEPS0dwpiGjKI1DOtFxZZs= =R7E1 -END PGP SIGNATURE End Message ---
Bug#1054303: marked as done (RM: gscanbus -- RoQA; orphaned; dead upstream; depends on gtk2)
Your message dated Thu, 30 Nov 2023 18:48:34 + with message-id and subject line Bug#1056370: Removed package(s) from unstable has caused the Debian Bug report #1054303, regarding RM: gscanbus -- RoQA; orphaned; dead upstream; depends on gtk2 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.) -- 1054303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gscanbus Severity: serious gscanbus is orphaned for 7 years and dead upstream. It also depends on the obsolete GTK 2. I am going to file a RM bug when this is autoremoved from testing and nobody objects. --- End Message --- --- Begin Message --- Version: 0.8-3+rm Dear submitter, as the package gscanbus 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/1056370 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1054301: marked as done (RM: glfer -- RoQA; orphaned; dead upstream; depends on gtk2)
Your message dated Thu, 30 Nov 2023 18:50:24 + with message-id and subject line Bug#1056369: Removed package(s) from unstable has caused the Debian Bug report #1054301, regarding RM: glfer -- RoQA; orphaned; dead upstream; depends on gtk2 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.) -- 1054301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glfer Severity: serious glfer is orphaned for 14 years and dead upstream. It also depends on the obsolete GTK 2. I am going to file a RM bug when this is autoremoved from testing and nobody objects. --- End Message --- --- Begin Message --- Version: 0.4.2-4+rm Dear submitter, as the package glfer 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/1056369 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Processed: Bug#1057149 marked as pending in gimp
Processing control commands: > tag -1 pending Bug #1057149 [gimp] gimp: Please add Conflicts+Replaces: gimp-dds Added tag(s) pending. -- 1057149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057149: marked as pending in gimp
Control: tag -1 pending Hello, Bug #1057149 in gimp 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/gnome-team/gimp/-/commit/5dd24337dd4ba1682c1d9ef5a69eab12c16a9d6a Add Conflicts/Replaces: gimp-dds Closes: #1057149 Thanks: Adrian Bunk (this message was generated automatically) -- Greetings https://bugs.debian.org/1057149
Bug#1057149: gimp: Please add Conflicts+Replaces: gimp-dds
Package: gimp Version: 2.10.12-1 Severity: serious gimp-dds was included in 2.10.10, and the old version of the plugin in gimp-dds is also vulnerable to CVE-2023-1. Please add[1] Conflicts: gimp-dds Replaces: gimp-dds to get rid of the stale version of this plugin. A fast upload would be appreciated so that I can also submit this change for the next bookworm (and bullseye) point releases. Thanks in advance [1] https://lists.debian.org/deity/2023/11/msg00037.html
Bug#1051256: marked as done (milkytracker crashes with signal 6 (double free detected in tcache 2))
Your message dated Thu, 30 Nov 2023 17:36:28 + with message-id and subject line Bug#1051256: fixed in milkytracker 1.04.00.20230830+dfsg-1 has caused the Debian Bug report #1051256, regarding milkytracker crashes with signal 6 (double free detected in tcache 2) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1051256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: milkytracker Version: 1.04.00+dfsg-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, * What led up to the situation? spawning milkytracker. * What exactly did you do (or not do) that was effective (or ineffective)? Entered the command : milkytracker * What was the outcome of this action? Output of the command : Available Renderers: opengl opengles2 software Vendor : NVIDIA Corporation Renderer : NVIDIA GeForce GTX 1660/PCIe/SSE2 Version : OpenGL ES 3.2 NVIDIA 525.125.06 SDL: Minimum window size set to 1440x940. SDL: Using accelerated renderer. SDL: Renderer supports rendering to texture. 0 0 SDL: Using audio driver: pulseaudio SDL: Buffer size = 2048 samples (requested 2048) MIDI: scanning input ports: MIDI: 0. Midi Through:Midi Through Port-0 14:0 free(): double free detected in tcache 2 Crashed with signal 6 Please submit a bug report stating exactly what you were doing at the time of the crash, as well as the above signal number. Also note if it is possible to reproduce this crash. A backup has been saved to /home/ylb/BACKUP00.XM Abandon * What outcome did you expect instead? milkytracker main window Crash is reproductible. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages milkytracker depends on: ii libasound2 1.2.9-2 ii libc6 2.37-7 ii libgcc-s1 13.2.0-3 ii liblhasa0 0.4.0-1 ii librtmidi6 5.0.0-3 ii libsdl2-2.0-0 2.28.3+dfsg-1 ii libstdc++6 13.2.0-3 ii libzzip-0-13 0.13.72+dfsg.1-1.1 ii zlib1g 1:1.2.13.dfsg-3 milkytracker recommends no packages. Versions of packages milkytracker suggests: pn bambootracker pn cheesecutter pn freepats pn goattracker pn hivelytracker pn modplug-tools pn opencubicplayer pn protracker pn schism -- no debconf information --- End Message --- --- Begin Message --- Source: milkytracker Source-Version: 1.04.00.20230830+dfsg-1 Done: James Cowgill We believe that the bug you reported is fixed in the latest version of milkytracker, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James Cowgill (supplier of updated milkytracker 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, 30 Nov 2023 17:24:39 + Source: milkytracker Architecture: source Version: 1.04.00.20230830+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: James Cowgill Closes: 1051256 Changes: milkytracker (1.04.00.20230830+dfsg-1) unstable; urgency=medium . * New upstream version of 1.04.00. - Upstream moved the existing 1.04.00 tag to another commit around the end of August. - Fixes crash on startup. (Closes: #1051256, LP: #2040293) . * d/copyright: Update date. * d/patches: - Drop patches applied upstream. - Refresh 01_remove-resources-music.patch. * d/source/lintian-overrides: Override source-is-missing. Checksums-Sha1: 1bb7e5244ce5a4421371639d747265f637c86f57 2403 milkytracker_1.04.00.20230830+dfsg-1.dsc ea54dcbcf3918cda66401155944a2455ed5a4602 2968728 milkytracker_1.04.00.20230830+dfsg.orig.tar.xz ceab7fec24612ff67467a0fcb8d49535b14cccb4 8512 milkytracker_1.04.00.20230830+dfsg-1.debian.tar.xz
Bug#1057148: python-dbusmock/0.30.0-1 autopkg tests are failing
Package: src:python-dbusmock Version: 0.30.0-1 Severity: serious Tags: sid trixie python-dbusmock/0.30.0-1 autopkg tests are failing: [...] 1428s autopkgtest [12:44:58]: test upstream: [--- 1433s ...dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Activating service name='org.TestSession' requested by ':1.0' (uid=1000 pid=1717 comm="python3 test_api.py" label="unconfined") 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Successfully activated service 'org.TestSession' 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s ..dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s dbus-daemon[1749]: [session uid=1000 pid=1749] Reloaded configuration 1433s .dbus-daemon[1748]: [system] Reloaded configuration 1433s dbus-daemon[1748]: [system] Activating service name='org.TestSystem' requested by ':1.0' (uid=1000 pid=1717 comm="python3 test_api.py" label="unconfined") 1433s dbus-daemon[1748]: [system] Successfully activated service 'org.TestSystem' 1433s dbus-daemon[1748]: [system] Reloaded configuration 1433s dbus-daemon[1748]: [system] Reloaded configuration 1433s .dbus-daemon[1748]: [system] Reloaded configuration 1433s dbus-daemon[1748]: [system] Reloaded configuration 1433s dbus-daemon[1748]: [system] Reloaded configuration 1435s ... 1435s -- 1435s Ran 42 tests in 6.080s 1435s 1435s OK 1435s Traceback (most recent call last): 1435s File "/tmp/autopkgtest.gGVLMr/build.Dnb/src/tests/test_api_pytest.py", line 14, in 1435s import pytest 1435s ModuleNotFoundError: No module named 'pytest' 1435s autopkgtest [12:45:05]: test upstream: ---]
Processed: closing 1054982
Processing commands for cont...@bugs.debian.org: > close 1054982 0.9.5-1 Bug #1054982 [src:haskell-intern] haskell-intern: FTBFS: unsatisfiable build-dependency: libghc-hashable-dev (< 1.4) but 1.4.3.0-1+b1 is to be installed The source 'haskell-intern' and version '0.9.5-1' do not appear to match any binary packages Marked as fixed in versions haskell-intern/0.9.5-1. Bug #1054982 [src:haskell-intern] haskell-intern: FTBFS: unsatisfiable build-dependency: libghc-hashable-dev (< 1.4) but 1.4.3.0-1+b1 is to be installed Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1054982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block bug
Processing commands for cont...@bugs.debian.org: > block 1042746 by 1050086 Bug #1042746 [src:rust-hashbrown] rust-hashbrown: Please upgrade to v0.13 1042746 was not blocked by any bugs. 1042746 was not blocking any bugs. Added blocking bug(s) of 1042746: 1050086 > thanks Stopping processing here. Please contact me if you need assistance. -- 1042746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
Hi Graham On 30 November 2023 at 07:54, Graham Inggs wrote: | Hi Dirk | | On Thu, 30 Nov 2023 at 00:51, Dirk Eddelbuettel wrote: | > Ping squared. | > | > If I don't hear from you I may just close this. I believe this (non-, to me) | > issue has been taken care of. If you think I am wrong please let me know. | | I closed it on 2023-11-24 [1]. Where do you see it still open? My bad: I don't. I just didn't see an explicit ack. (General bts acks are filtered away by procmail to a different folder). So my bad and sorry for wasting your time. I see you track it at Ubuntu too so all good. r2u, which dominates of course all r-(cran,bioc)-* packages for use on jammy had it long covered. Cheers, Dirk | | [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055922#118 -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Processed (with 1 error): fix meta info
Processing commands for cont...@bugs.debian.org: > severity 1042978 normal Bug #1042978 [release.debian.org] Tests invalid package upgrades Severity set to 'normal' from 'serious' > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was elb...@debian.org). > usertag 1042978 britney There were no usertags set. Usertags are now: britney. > title 1042978 britney: sometimes triggers wrong tests for linux Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019488: bouncycastle: incomplete information in the manifest files
This problem still exists in 1.77 (to be released soon). That sounds like a bnd problem. I can find a reference to a bnd.sh script but it is not included in the source distribution. There is also a add_module.sh script. If we can't find a way to automate this build step, we could use jh_manifest which I would prefer over the patch. signature.asc Description: This is a digitally signed message part
Bug#1051294: marked as done (fwupd: FTBFS: Run-time dependency xmlb found: NO (tried pkgconfig and cmake))
Your message dated Thu, 30 Nov 2023 12:18:47 + with message-id <108f92b9576797d05ff1954213b3583b2758beec.ca...@dalerichards.net> and subject line RE: fwupd: FTBFS: Run-time dependency xmlb found: NO (tried pkgconfig and cmake) has caused the Debian Bug report #1051294, regarding fwupd: FTBFS: Run-time dependency xmlb found: NO (tried pkgconfig and cmake) 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.) -- 1051294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fwupd Version: 1.9.4-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=fwupd=armel=1.9.4-2%2Bb1=1693947882=0 --- env[PKG_CONFIG_PATH]: --- Called: `/usr/bin/pkg-config --cflags xmlb` -> 1 stderr: Package libzstd was not found in the pkg-config search path. Perhaps you should add the directory containing `libzstd.pc' to the PKG_CONFIG_PATH environment variable Package 'libzstd', required by 'xmlb', not found --- pkg-config error with 'xmlb': Could not generate cargs for xmlb: Package libzstd was not found in the pkg-config search path. Perhaps you should add the directory containing `libzstd.pc' to the PKG_CONFIG_PATH environment variable Package 'libzstd', required by 'xmlb', not found CMake binary for 1 is not cached CMake binary missing from cross or native file, or env var undefined. Trying a default CMake fallback at cmake Did not find CMake 'cmake' Found CMake: NO CMake binary for machine 1 not found. Giving up. Run-time dependency xmlb found: NO (tried pkgconfig and cmake) Looking for a fallback subproject for the dependency xmlb ../meson.build:216:10: ERROR: Automatic wrap-based subproject downloading is disabled dh_auto_configure: error: cd obj-arm-linux-gnueabi && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/arm-linux-gnueabi -Dpython.bytecompile=-1 -Dplugin_flashrom=enabled -Dplugin_dell=disabled -Dplugin_msr=disabled -Dplugin_dummy=true -Dplugin_powerd=disabled -Dsupported_build=enabled -Dplugin_modem_manager=enabled -Dsystemd_unit_user=fwupd-refresh -Defi_binary=false returned exit code 1 make[1]: *** [debian/rules:55: override_dh_auto_configure] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:48: binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Build finished at 2023-09-05T21:04:31Z Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 0.3.13-1 The missing libzstd-dev dependency was added in libxmlb/0.3.13-1, and fwupd is now building as expected. Closing this bug. Best regards, Dale Richards--- End Message ---
Processed: Fixed upstream
Processing control commands: > tag -1 patch fixed-upstream Bug #1042652 [src:pyfuse3] pyfuse3: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' Added tag(s) fixed-upstream and patch. -- 1042652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042652: Fixed upstream
Control: tag -1 patch fixed-upstream If the package is updated to version 3.3 plus a 'backport' of upstream commit df95c4ee7bf489448a02c1f5053a24c628d637d9, then this bug should be fixed. signature.asc Description: This is a digitally signed message part.
Processed: severity of 1042970 is minor
Processing commands for cont...@bugs.debian.org: > severity 1042970 minor Bug #1042970 [src:zoneminder] zoneminder: Embded cakephp Severity set to 'minor' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1042970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
Hi Dirk On Thu, 30 Nov 2023 at 00:51, Dirk Eddelbuettel wrote: > Ping squared. > > If I don't hear from you I may just close this. I believe this (non-, to me) > issue has been taken care of. If you think I am wrong please let me know. I closed it on 2023-11-24 [1]. Where do you see it still open? Regards Graham [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055922#118
Bug#1055484: marked as done (libpam-elogind-compat has ineffective replaces for libpam-systemd due to /usr-merge)
Your message dated Thu, 30 Nov 2023 09:48:24 +0100 with message-id and subject line libpam-elogind-compat has been removed from experimental has caused the Debian Bug report #1055484, regarding libpam-elogind-compat has ineffective replaces for libpam-systemd due to /usr-merge 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.) -- 1055484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-elogind-compat Version: 1.3 Severity: serious Justification: silent file overwrite in upgrade situation User: helm...@debian.org Usertags: dep17p1 Control: clone -1 -2 Control: affects -1 + libpam-systemd Control: retitle -2 libpam-systemd needs a versioned conflict for libpam-elogind-compat Control: reassign -2 libpam-systemd Control: found -2 255~rc1-2 Control: affects -2 + libpam-elogind-compat Control: block -2 by -1 libpam-elogind-compat declares "Replaces: libpam-systemd", because they both install e.g. /lib/x86_64-linux-gnu/security/pam_systemd.so on amd64. Since libpam-systemd/255~rc1-2 in experimental, this file is located in the corresponding location below /usr. Therefore the Replaces declaration is not matched by dpkg and becomes ineffective. The resulting behaviour is as if there was no replaces. This is problem class is described in more detail in DEP17[1] P1. The simplest mitigation for this kind of problem is preventing concurrent unpack by upgrading Replaces to Conflicts (and thus dropping the now implied Breaks). This mitigation is described in more detail in DEP17[1] M7. Do you know why Breaks+Replaces has been chosen here? Do you see any issues with upgrading to Conflicts? A timely solution is appreciated, because libpam-systemd will need a versioned Conflicts on unfixed versions of libpam-elogind-compat to avoid breaking upgrades. Helmut [1] https://subdivi.de/~helmut/dep17.html --- End Message --- --- Begin Message --- Version: 1.3+rm libpam-elogind-compat has been removed from Debian, see https://bugs.debian.org/1055562 for details on the removal. Andreas--- End Message ---
Bug#913800: marked as done (libpam-elogind-compat will always be RC-buggy)
Your message dated Thu, 30 Nov 2023 09:48:24 +0100 with message-id and subject line libpam-elogind-compat has been removed from experimental has caused the Debian Bug report #913800, regarding libpam-elogind-compat will always be RC-buggy 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.) -- 913800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-elogind-compat Version: 1.0 Severity: serious This package exists in Debian to facilitate testing within Debian, but it grossly interferes with the arrangements of other nonconsenting packages (notably, systemd packages in Debian). It must therefore not form part of any Debian release. We do not intend to upload libpam-elogind-compat to sid, so it ought not to propagate to testing. But I am filing this bug in case it is uploaded to sid accidentally, and to help document the situation. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter. --- End Message --- --- Begin Message --- Version: 1.3+rm libpam-elogind-compat has been removed from Debian, see https://bugs.debian.org/1055562 for details on the removal. Andreas--- End Message ---
