Bug#1056031: rust-rstest-test: autopkgtest failure

[Adrian Bunk]

Source: rust-rstest-test
Version: 0.11.0-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rstest-test/39198638/log.gz

...
84s  more_tests::case_2_contains stdout 
 84s Stderr: debian cargo wrapper: options, profiles, parallel: ['parallel=64'] 
[] ['-j64']
 84s debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
 84s debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '+stable', '-Zavoid-dev-deps', 'test', '--verbose', 
'--verbose', '-j64', '--target', 'x86_64-unknown-linux-gnu'],) {}
 84s error: no such subcommand: `+stable`
 84s 
 84sCargo does not handle `+toolchain` directives.
 84sDid you mean to invoke `cargo` through `rustup` instead?
 84s 
 84s thread 'more_tests::case_2_contains' panicked at 'Empty stdout!', 
/usr/share/cargo/registry/rstest-test-0.11.0/src/utils.rs:308:13
 84s stack backtrace:
 84s0: std::panicking::begin_panic
 84s  at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:610:12
 84s1: rstest_test::utils::TestResults::assert
 84s  at 
/usr/share/cargo/registry/rstest-test-0.11.0/src/utils.rs:308:13
 84s2: framework::more_tests
 84s  at 
/usr/share/cargo/registry/rstest-test-0.11.0/tests/framework.rs:87:5
 84s3: framework::more_tests::case_2_contains
 84s  at 
/usr/share/cargo/registry/rstest-test-0.11.0/tests/framework.rs:58:1
 84s4: framework::more_tests::case_2_contains::{{closure}}
 84s  at 
/usr/share/cargo/registry/rstest-test-0.11.0/tests/framework.rs:58:1
 84s5: core::ops::function::FnOnce::call_once
 84s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
 84s6: core::ops::function::FnOnce::call_once
 84s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
 84s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.
 84s 
 84s 
 84s failures:
 84s add_local_dependency
 84s more_tests::case_1_default_conf
 84s more_tests::case_2_contains
 84s nocapture_in_tests
 84s one_fail::case_1_default_conf
 84s one_fail::case_2_contains
 84s one_success::case_1_default_conf
 84s one_success::case_2_contains
 84s should_check_just_contains_conf
 84s should_check_just_contains_on_some_test
 84s should_check_some_tests_as_contains
 84s should_detect_wrong_contains
 84s tests_with_should_panic::case_1_default_conf
 84s tests_with_should_panic::case_2_contains
 84s 
 84s test result: FAILED. 1 passed; 14 failed; 0 ignored; 0 measured; 0 
filtered out; finished in 0.79s
 84s 
 84s error: test failed, to rerun pass `--test framework`
 85s autopkgtest [21:27:08]: test librust-rstest-test-dev:: 
---]
 85s autopkgtest [21:27:08]: test librust-rstest-test-dev::  - - - - - - - - - 
- results - - - - - - - - - -
 85s librust-rstest-test-dev: FAIL non-zero exit status 101
 85s autopkgtest [21:27:08]:  summary
 85s rust-rstest-test:@   FAIL non-zero exit status 101
 85s librust-rstest-test-dev:default FAIL non-zero exit status 101
 85s librust-rstest-test-dev: FAIL non-zero exit status 101

Bug#1056030: rust-color-thief: autopkgtest failure on !x86

[Adrian Bunk]

Source: rust-color-thief
Version: 0.2.2-1
Severity: serious

https://tracker.debian.org/pkg/rust-color-thief

Issues preventing migration:
∙ ∙ autopkgtest for rust-color-thief/0.2.2-1: amd64: Pass, arm64: Regression ♻ 
, armel: Regression ♻ , armhf: Regression ♻ , i386: Pass, ppc64el: Regression ♻ 
, s390x: Regression ♻


...
109s running 1 test
109s test image1 ... FAILED
109s 
109s failures:
109s 
109s  image1 stdout 
109s thread 'image1' panicked at 'assertion failed: `(left == right)`
109s   left: `RGB { r: 43, g: 125, b: 149 }`,
109s  right: `RGB { r: 42, g: 125, b: 149 }`', tests/test.rs:26:5
109s stack backtrace:
109s0: rust_begin_unwind
109s  at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
109s1: core::panicking::panic_fmt
109s  at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
109s2: core::panicking::assert_failed_inner
109s3: core::panicking::assert_failed
109s  at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:228:5
109s4: test::image1
109s  at ./tests/test.rs:26:5
109s5: test::image1::{{closure}}
109s  at ./tests/test.rs:17:13
109s6: core::ops::function::FnOnce::call_once
109s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
109s7: core::ops::function::FnOnce::call_once
109s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
109s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.
109s 
109s 
109s failures:
109s image1
109s 
109s test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered 
out; finished in 0.27s
109s 
109s error: test failed, to rerun pass `--test test`
109s autopkgtest [03:27:39]: test librust-color-thief-dev:: 
---]
110s librust-color-thief-dev: FAIL non-zero exit status 101
110s autopkgtest [03:27:40]: test librust-color-thief-dev::  - - - - - - - - - 
- results - - - - - - - - - -
110s autopkgtest [03:27:40]:  summary
110s rust-color-thief:@   FAIL non-zero exit status 101
110s librust-color-thief-dev:default FAIL non-zero exit status 101
110s librust-color-thief-dev: FAIL non-zero exit status 101

Bug#1056029: rust-hafas-rs: autopkgtest failure

[Adrian Bunk]

Source: rust-hafas-rs
Version: 0.1.0-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-hafas-rs/39490355/log.gz

...
143s error[E0432]: unresolved import `crate::requester::hyper`
143s--> src/profile/mod.rs:460:20
143s |
143s 460 | requester::hyper::HyperRustlsRequester,
143s |^ could not find `hyper` in `requester`
143s 
...
1412s autopkgtest [23:42:46]:  summary
1412s rust-hafas-rs:@  FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:all-profiles FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:anyhow FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:avv-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:bart-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:bls-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:cfl-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:cmta-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:dart-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:db-busradar-nrw-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:db-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:default PASS
1412s librust-hafas-rs-dev:env_logger FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:geojson FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:hyper FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:hyper-requester PASS
1412s librust-hafas-rs-dev:hyper-rustls FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:insa-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:irish-rail-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:mobil-nrw-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:mobiliteit-lu-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:nahsh-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:nvv-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:oebb-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:ooevv-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:polyline FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:polylines FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:rejseplanen-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:rest-server PASS
1412s librust-hafas-rs-dev:rmv-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:rsag-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:rt-multi-thread FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:saarvv-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:salzburg-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:sbahn-muenchen-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:serde_urlencoded FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:svv-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:tokio FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:vbb-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:vbn-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:verbundlinie-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:vgi-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:vkg-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:vmt-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:vor-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:vos-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:vrn-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:vsn-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:vvt-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:vvv-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev:zvv-profile FAIL non-zero exit status 101
1412s librust-hafas-rs-dev: FAIL non-zero exit status 101

Bug#1056028: rust-ntp-udp: autopkgtest failure

[Adrian Bunk]

Source: rust-ntp-udp
Version: 1.0.0-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-ntp-udp/38887148/log.gz

...
 75s error[E0433]: failed to resolve: could not find `test` in `tokio`
 75s--> src/socket.rs:394:14
 75s |
 75s 394 | #[tokio::test]
 75s |   could not find `test` in `tokio`
 75s 
 75s error[E0433]: failed to resolve: could not find `test` in `tokio`
 75s--> src/socket.rs:423:14
 75s |
 75s 423 | #[tokio::test]
 75s |   could not find `test` in `tokio`
 75s 
 75s error[E0433]: failed to resolve: could not find `test` in `tokio`
 75s--> src/socket.rs:452:14
 75s |
 75s 452 | #[tokio::test]
 75s |   could not find `test` in `tokio`
 75s 
 75s error[E0433]: failed to resolve: could not find `test` in `tokio`
 75s--> src/socket.rs:478:14
 75s |
 75s 478 | #[tokio::test]
 75s |   could not find `test` in `tokio`
 75s 
 75s error[E0433]: failed to resolve: could not find `test` in `tokio`
 75s--> src/socket.rs:550:14
 75s |
 75s 550 | #[tokio::test]
 75s |   could not find `test` in `tokio`
 75s 
 75s error[E0433]: failed to resolve: could not find `test` in `tokio`
 75s--> src/socket.rs:556:14
 75s |
 75s 556 | #[tokio::test]
 75s |   could not find `test` in `tokio`
 75s 
 75s error[E0433]: failed to resolve: could not find `test` in `tokio`
 75s--> src/socket.rs:562:14
 75s |
 75s 562 | #[tokio::test]
 75s |   could not find `test` in `tokio`
 75s 
 75s error[E0433]: failed to resolve: could not find `test` in `tokio`
 75s--> src/socket.rs:568:14
 75s |
 75s 568 | #[tokio::test]
 75s |   could not find `test` in `tokio`
 75s 
 76s For more information about this error, try `rustc --explain E0433`.
 76s error: could not compile `ntp-udp` due to 8 previous errors
...
 96s autopkgtest [03:27:44]:  summary
 96s rust-ntp-udp:@   FAIL non-zero exit status 101
 96s librust-ntp-udp-dev:default FAIL non-zero exit status 101
 96s librust-ntp-udp-dev: FAIL non-zero exit status 101

Bug#1056027: rsass: autopkgtest regression

[Adrian Bunk]

Source: rsass
Version: 0.28.2+20231021-3
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rsass/39898469/log.gz

...
 54s autopkgtest [11:12:12]: test rust-rsass:@:  
/usr/share/cargo/bin/cargo-auto-test rsass --all-targets --all-features 
--no-fail-fast -- --skip core_functions::math::log::base::one_fuzzy --skip 
values::calculation::calc::constant::e::equals_max_precision --skip 
values::calculation::calc::constant::pi::equals_max_precision
 54s autopkgtest [11:12:12]: test rust-rsass:@: [---
 54s crate directory not found: /usr/share/cargo/registry/rsass---all-targets
 54s autopkgtest [11:12:12]: test rust-rsass:@: ---]
 54s autopkgtest [11:12:12]: test rust-rsass:@:  - - - - - - - - - - results - 
- - - - - - - - -
 54s rust-rsass:@ FAIL non-zero exit status 1
...
132s autopkgtest [11:13:30]:  summary
132s rust-rsass:@ FAIL non-zero exit status 1
132s librust-rsass-dev:default FAIL non-zero exit status 1
132s librust-rsass-dev:   FAIL non-zero exit status 1

Bug#1056026: librust-eza-dev is not installable

[Adrian Bunk]

Package: librust-eza-dev
Version: 0.15.0-1
Severity: serious

The following packages have unmet dependencies:
 librust-eza-dev : Depends: librust-git2-0.16+vendored-libgit2-dev but it is 
not installable or
librust-git2-0.15+vendored-libgit2-dev but it is 
not installable or
librust-git2-0.14+vendored-libgit2-dev but it is 
not installable or
librust-git2-0.13+vendored-libgit2-dev but it is 
not installable

Bug#1055525: cryptojs: CVE-2023-46233

[Yadd]

Hi,

this bug is still unfixed even if patch is trivial. Here is a template 
for an updatediff --git a/debian/changelog b/debian/changelog
index 558cbac..849d0f4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+cryptojs (3.1.2+dfsg-3+deb12u1) bookworm-security; urgency=medium
+
+  * Change default hash algorithm and iteration's for PBKDF2
+(Closes: #1055525)
+
+ -- Yadd   Thu, 16 Nov 2023 10:53:45 +0400
+
 cryptojs (3.1.2+dfsg-3) unstable; urgency=medium
 
   * Add upstream metadata.
diff --git a/debian/patches/CVE-2023-46233.patch 
b/debian/patches/CVE-2023-46233.patch
new file mode 100644
index 000..c321f49
--- /dev/null
+++ b/debian/patches/CVE-2023-46233.patch
@@ -0,0 +1,38 @@
+Description: Change default hash algorithm and iteration's for PBKDF2
+ to prevent weak security by using the default configuration
+Author: evanvosberg 
+Origin: upstream, https://github.com/brix/crypto-js/commit/421dd538
+Bug: https://github.com/brix/crypto-js/security/advisories/GHSA-xwcq-pm8m-c4vf
+Bug-Debian: https://bugs.debian.org/1055525
+Forwarded: not-needed
+Reviewed-By: Yadd 
+Last-Update: 2023-11-16
+
+--- a/components/pbkdf2.js
 b/components/pbkdf2.js
+@@ -11,7 +11,7 @@
+ var Base = C_lib.Base;
+ var WordArray = C_lib.WordArray;
+ var C_algo = C.algo;
+-var SHA1 = C_algo.SHA1;
++var SHA256 = C_algo.SHA256;
+ var HMAC = C_algo.HMAC;
+ 
+ /**
+@@ -22,13 +22,13 @@
+  * Configuration options.
+  *
+  * @property {number} keySize The key size in words to generate. 
Default: 4 (128 bits)
+- * @property {Hasher} hasher The hasher to use. Default: SHA1
++ * @property {Hasher} hasher The hasher to use. Default: SHA256
+  * @property {number} iterations The number of iterations to perform. 
Default: 1
+  */
+ cfg: Base.extend({
+ keySize: 128/32,
+-hasher: SHA1,
+-iterations: 1
++hasher: SHA256,
++iterations: 25
+ }),
+ 
+ /**
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..4fdeacb
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+CVE-2023-46233.patch

Bug#1054697: marked as done (slic3r-prusa: FTBFS: test_arrange.cpp:1:10: fatal error: catch2/catch.hpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 16 Nov 2023 06:49:47 +
with message-id 
and subject line Bug#1054697: fixed in slic3r-prusa 2.6.1+dfsg-4
has caused the Debian Bug report #1054697,
regarding slic3r-prusa: FTBFS: test_arrange.cpp:1:10: fatal error: 
catch2/catch.hpp: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1054697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slic3r-prusa
Version: 2.6.1+dfsg-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):
> cd /<>/obj-x86_64-linux-gnu/tests/libslic3r && /usr/bin/c++ 
> -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK 
> -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK 
> -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_LOCALE_DYN_LINK -DBOOST_LOG_DYN_LINK 
> -DBOOST_REGEX_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK 
> -DCATCH_CONFIG_FAST_COMPILE -DLIBNEST2D_GEOMETRIES_libslic3r 
> -DLIBNEST2D_OPTIMIZER_nlopt -DLIBNEST2D_STATIC -DLIBNEST2D_THREADING_tbb 
> -DOPENVDB_ABI_VERSION_NUMBER=10 -DOPENVDB_USE_DELAYED_LOADING -DSLIC3R_GUI 
> -DTBB_USE_CAPTURED_EXCEPTION=0 
> -DTEST_DATA_DIR="R\"(/<>/tests/data)\"" -DUNICODE -DUSE_TBB 
> -DWXINTL_NO_GETTEXT_MACRO -D_UNICODE -DwxNO_UNSAFE_WXSTRING_CONV 
> -DwxUSE_UNICODE -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/<>/src 
> -I/<>/obj-x86_64-linux-gnu/src/platform -I/<>/tests 
> -I/<>/obj-x86_64-linux-gnu/src/libslic3r 
> -I/<>/src/libnest2d/include -I/<>/src/miniz 
> -I/<>/src/glu-libtess/include -isystem /usr/include/eigen3 
> -isystem /<>/src/libigl -isystem /usr/include/Imath -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fext-numeric-literals -Wall -Wno-reorder -O3 
> -DNDEBUG -std=gnu++17 -fPIE -fsigned-char -Werror=return-type 
> -Wno-ignored-attributes -Wno-unknown-pragmas -MD -MT 
> tests/libslic3r/CMakeFiles/libslic3r_tests.dir/test_3mf.cpp.o -MF 
> CMakeFiles/libslic3r_tests.dir/test_3mf.cpp.o.d -o 
> CMakeFiles/libslic3r_tests.dir/test_3mf.cpp.o -c 
> /<>/tests/libslic3r/test_3mf.cpp
> /<>/tests/arrange/test_arrange.cpp:1:10: fatal error: 
> catch2/catch.hpp: No such file or directory
> 1 | #include 
>   |  ^~
> In file included from /<>/tests/libslic3r/libslic3r_tests.cpp:1:
> /<>/tests/catch_main.hpp:7:10: fatal error: catch2/catch.hpp: No 
> such file or directory
> 7 | #include 
>   |  ^~
> compilation terminated.
> compilation terminated.
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[3]: *** [tests/libslic3r/CMakeFiles/libslic3r_tests.dir/build.make:79: 
> tests/libslic3r/CMakeFiles/libslic3r_tests.dir/libslic3r_tests.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/slic3r-prusa_2.6.1+dfsg-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: slic3r-prusa
Source-Version: 2.6.1+dfsg-4
Done: Chow Loong Jin 

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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chow Loong Jin  (supplier of updated slic3r-prusa package)

(This message was generated automatically at their request; if you
believe that there is a 

Bug#1056018: partman-base: parted_devices hangs with process in D state during Debian installer Detect Disks step

[Cyril Brulebois]

Control: severity -1 important

Hi,

Olivier F. R. Dierick  (2023-11-16):
> Justification: breaks the whole system

Not being able to install doesn't “break the whole system”. This is a
showstopper in the installation process in your case indeed, but that's
not what this severity is for.

> Updating from Debian 8 to Debian 12 from an USB stick.

Maybe check the image was correctly written on your USB stick? A number
of weird issues like that one are linked to hardware faults or similar
issues.

>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> Ineffective: Tried disconnecting external disks & USB storage HUB, and
> switching SATA setting from AHCI to IDE in BIOS.
> Also tried expert mode & text mode.
> 
>* What was the outcome of this action?
> 
> Debian Installer is stuck on Detect Disks.
> Switching to a console and running ps shows that a parted_devices
> process is in D state.

Anything in dmesg or /var/log/syslog?

It might be interesting to see what happens with 12.0 images (in case
something interesting happened in the kernel, but such a hard failure
seems rather strange), and maybe try your luck with some Debian Live
image?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: Bug#1056018: partman-base: parted_devices hangs with process in D state during Debian installer Detect Disks step

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1056018 [src:partman-base] partman-base: parted_devices hangs with process 
in D state during Debian installer Detect Disks step
Severity set to 'important' from 'critical'

-- 
1056018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1054697: marked as pending in slic3r-prusa

[Loong Jin Chow]

Control: tag -1 pending

Hello,

Bug #1054697 in slic3r-prusa 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/3dprinting-team/slic3r-prusa/-/commit/9c874772a23e75b0a8b768a716e1faf544cc0daf


Update catch2 patch for v3 changes

Thanks: Gregor Riepl 
Closes: #1054697


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1054697

Processed: Bug#1054697 marked as pending in slic3r-prusa

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1054697 [src:slic3r-prusa] slic3r-prusa: FTBFS: test_arrange.cpp:1:10: 
fatal error: catch2/catch.hpp: No such file or directory
Added tag(s) pending.

-- 
1054697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1054693: marked as done (cli11: FTBFS: catch.hpp:9:10: fatal error: catch2/catch.hpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 16 Nov 2023 06:19:30 +
with message-id 
and subject line Bug#1054693: fixed in cli11 2.3.2+ds-1
has caused the Debian Bug report #1054693,
regarding cli11: FTBFS: catch.hpp:9:10: fatal error: catch2/catch.hpp: No such 
file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1054693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cli11
Version: 2.1.2+ds-1
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):
> cd /<>/obj-x86_64-linux-gnu/tests && /usr/bin/c++  
> -I/usr/include/catch2 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
> -std=c++11 -MD -MT tests/CMakeFiles/catch_main.dir/main.cpp.o -MF 
> CMakeFiles/catch_main.dir/main.cpp.o.d -o 
> CMakeFiles/catch_main.dir/main.cpp.o -c /<>/tests/main.cpp
> In file included from /<>/tests/main.cpp:8:
> /<>/tests/catch.hpp:9:10: fatal error: catch2/catch.hpp: No such 
> file or directory
> 9 | #include 
>   |  ^~
> compilation terminated.
> make[4]: *** [tests/CMakeFiles/catch_main.dir/build.make:79: 
> tests/CMakeFiles/catch_main.dir/main.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/cli11_2.1.2+ds-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: cli11
Source-Version: 2.3.2+ds-1
Done: Jose Luis Rivero 

We believe that the bug you reported is fixed in the latest version of
cli11, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated cli11 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 13 Nov 2023 17:07:51 +
Source: cli11
Architecture: source
Version: 2.3.2+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Jose Luis Rivero 
Changed-By: Jose Luis Rivero 
Closes: 1054693
Changes:
 cli11 (2.3.2+ds-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
   * Update standards version to 4.6.2, no changes needed.
 .
   [ Jose Luis Rivero ]
   * New upstream version 2.3.2+ds
   * Fix compilation with catch2 version 2.3.x
 (Closes: #1054693)
   * Remove custom configure step in d/rules
   * Disable OptionalTest
   * Update d/copyright
Checksums-Sha1:
 a6eefc7c827d928da3ce8cf7db1c72c133f68e71 1995 cli11_2.3.2+ds-1.dsc
 b73990079af914b584e713290b086ba8a626ad84 214856 cli11_2.3.2+ds.orig.tar.xz
 e329a1a7d6748ab4c2501865affc861b54794ac5 6208 cli11_2.3.2+ds-1.debian.tar.xz
 017b31231f74c58765b37e54fd8e585b2a23cd04 7758 cli11_2.3.2+ds-1_source.buildinfo
Checksums-Sha256:
 9b74824585976081fd88fbc495278e67505e391d78490af5d443f730346dd104 1995 
cli11_2.3.2+ds-1.dsc
 202efcac08a6a9f2327e6ad436e8f23bdd8a4e7334f551b99a08eff492ce3c49 214856 
cli11_2.3.2+ds.orig.tar.xz
 0d78a5b37fcf3edbe0031f336633c453aa5d62cbec08237d278e4ca4ef0ebbcc 6208 
cli11_2.3.2+ds-1.debian.tar.xz
 03c81747a5f67c41ff233e0afbdef98fe4cbba2d41e04175b5ff2897d919f258 7758 
cli11_2.3.2+ds-1_source.buildinfo
Files:
 

Bug#1056018: partman-base: parted_devices hangs with process in D state during Debian installer Detect Disks step

[Olivier F. R. Dierick]

Source: partman-base
Version: 226
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?

Updating from Debian 8 to Debian 12 from an USB stick.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Ineffective: Tried disconnecting external disks & USB storage HUB, and 
switching SATA setting from AHCI to IDE in BIOS.
Also tried expert mode & text mode.

   * What was the outcome of this action?

Debian Installer is stuck on Detect Disks.
Switching to a console and running ps shows that a parted_devices process is in 
D state.

   * What outcome did you expect instead?

parted_devices should only take a few seconds and Debian Installer should 
continue to the partionning step.

Note: I'm reporting from another computer.
System information from the old OS is irrelevant anyway as the computer is 
booted on the Debian 12 installer image when the problem occurs.

-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-12-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1056014: cryptojs: Library no more maintained, please keep out of next Debian stable

[Yadd]

Source: cryptojs
Severity: serious
Tags: security upstream
Justification: security
X-Debbugs-Cc: y...@debian.org, Debian Security Team 

Hi,

according to https://github.com/brix/crypto-js#readme it seems that
cryptojs is no more maintained. I just dropped the only one reverse
dependency so cryptojs can be safely removed from Debian.

Bug#1054508: Connman: breaks connections, uses 1 CPU core, and trashes disk space

[программист некто]

Hello. I will try to test it, but it may be difficult. Because, I got the issue 
with Wi-Fi that located in another city.
I never got this issue with home Wi-Fi.

> Hi,
> 
> Please could you test with connman 1.42-1 in sid
> and see if you still see the issue. Thanks.
> 
> Regards,
> Vignesh
> 

Bug#1055914: marked as done (cp2k: BD-Uninstallable on armel)

[Debian Bug Tracking System]

Your message dated Thu, 16 Nov 2023 07:32:14 +0200
with message-id 
and subject line Re: [Debichem-devel] Bug#1055914: cp2k: BD-Uninstallable on 
armel
has caused the Debian Bug report #1055914,
regarding cp2k: BD-Uninstallable on armel
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.)


-- 
1055914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cp2k
Version: 2023.2-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/package.php?p=cp2k

cp2k build-depends on missing:
- libdbcsr-dev:armel (>= 2.6.0)

libdbcsr-dev is a new build dependency, but it is not available on
armel.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---

On 2023-11-14 10:29, Sebastian Ramacher wrote:

cp2k build-depends on missing:
- libdbcsr-dev:armel (>= 2.6.0)

libdbcsr-dev is a new build dependency, but it is not available on
armel.


This issue is fixed by resolving #1055928 in dbcsr, allowing dbcsr to 
build on armel.


Andrius--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1032104 - patch
Bug #1032104 [src:linux] linux: ppc64el iouring corrupted read
Removed tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1032104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037478: ca-certificates-java: Loop in the execution of the trigger

[Cyril Brulebois]

Hi,

Matthias Klose  (2023-07-12):
> Version: 20230710
> 
> Fixed now.

Thanks for the bugfix.

This is a serious issue that still affects at least bookworm (I didn't
check bullseye): applying the update published as DSA-5548-1 makes dpkg
error out. Cc-ing the security team accordingly.


On a bookworm system (freshly deployed and without any weird things done
package-wise) that had openjdk-17-jre-headless installed, upgrading it
to the version that's available in bullseye-security triggered the dpkg
trigger loop. Thankfully that's easily recoverable (e.g. by running
`dpkg --configure -a`, even if there might be better ways to do so), but
that's still something I believe shouldn't be happening on stable
systems with just the matching stable-security suite enabled.

This issue is trivially reproducible there by switching back and forth
between bookworm's version and bookworm-security's. Setting some debug
level in dpkg, I'm getting the attached log for one of those runs.

apt-get install -o dpkg::options::=-D7 openjdk-17-jre-headless/bookworm
apt-get install -o dpkg::options::=-D7 
openjdk-17-jre-headless/bookworm-security

→ ca-certificates-java-full-debug.txt

At the time of writing, that means switching between 17.0.8+7-1~deb12u1
and 17.0.9+9-1~deb12u1.


Checking whether this was possibly a problem with that particular
system, I tried reproducing the issue with openjdk-17-jre-headless in
a bookworm chroot, but I wasn't successful. Installing openjdk-17-jre
makes it possible to reproduce the issue though.

Shell script to reproduce (adjust DST=/tmp/bookworm if needed):

→ repro-1037478.sh

I'm attaching the log for the failed upgrade, again with dpkg debug:

→ repro-1037478.log


I've verified in both cases (real baremetal system and repro chroot)
that installing ca-certificates-java 20230710 beforehand indeed makes
the problem disappear. Since this release is a fixup for the previous
release which was mainly aimed at fixing this particular issue, I
suppose it would make sense to investigate whether something like
20230710~deb12u1 would be appropriate for bookworm-proposed-updates?

(And maybe bullseye-proposed-updates, but again, I didn't check the
bullseye part.)

Thanks for considering.


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
root@baremetal:~# apt-get install -o dpkg::options::=-D7 
openjdk-17-jre-headless/bookworm-security
…
Selected version '17.0.9+9-1~deb12u1' for 'openjdk-17-jre-headless'
…
The following packages will be upgraded:
  openjdk-17-jre-headless
1 upgraded, 0 newly installed, 0 to remove and 284 not upgraded.
Need to get 0 B/43.7 MB of archives.
After this operation, 487 kB disk space will be freed.
(Reading database ... 30411 files and directories currently installed.)
Preparing to unpack .../openjdk-17-jre-headless_17.0.9+9-1~deb12u1_amd64.deb ...
D02: trigproc_activate_packageprocessing pkg=openjdk-17-jre-headless:amd64
D02: post_script_tasks - ensure_diversions
D02: post_script_tasks - trig_incorporate
Unpacking openjdk-17-jre-headless:amd64 (17.0.9+9-1~deb12u1) over 
(17.0.8+7-1~deb12u1) ...
D02: post_script_tasks - ensure_diversions
D02: post_script_tasks - trig_incorporate
D01: trigproc_run_deferred
Setting up openjdk-17-jre-headless:amd64 (17.0.9+9-1~deb12u1) ...
D02: trigproc_activate_packageprocessing pkg=openjdk-17-jre-headless:amd64
Installing new version of config file 
/etc/java-17-openjdk/security/public_suffix_list.dat ...
D02: post_postinst_tasks - trig_incorporate
D01: trigproc_run_deferred
D01: trigproc ca-certificates-java:all
D01: trigproc ca-certificates-java:all
D01: trigproc ca-certificates-java:all
D01: trigproc ca-certificates-java:all
D01: trigproc ca-certificates-java:all
D01: trigproc ca-certificates-java:all
D01: trigproc ca-certificates-java:all
D01: trigproc ca-certificates-java:all
D01: trigproc ca-certificates-java:all
D01: trigproc ca-certificates-java:all
D01: check_triggers_cycle pnow=ca-certificates-java:all
D02: check_triggers_cycle pnow=ca-certificates-java:all first
D01: trigproc ca-certificates-java:all
D01: check_triggers_cycle pnow=ca-certificates-java:all
D02: tortoise_in_hare pnow=ca-certificates-java 
tortoise=ca-certificates-java
D02: tortoise_in_hare pnow=ca-certificates-java 
tortoise=ca-certificates-java tortoisetrig=/usr/lib/jvm
D04: tortoise_in_hare pnow=ca-certificates-java 
tortoise=ca-certificates-java tortoisetrig=/usr/lib/jvm haretrig=/usr/lib/jvm
D02: tortoise_in_hare pnow=ca-certificates-java 
tortoise=ca-certificates-java tortoisetrig=update-ca-certificates-java
D04: tortoise_in_hare pnow=ca-certificates-java 
tortoise=ca-certificates-java tortoisetrig=update-ca-certificates-java 
haretrig=/usr/lib/jvm
D04: tortoise_in_hare pnow=ca-certificates-java 
tortoise=ca-certificates-java tortoisetrig=update-ca-certificates-java 

Processed: Unarchive #1037478

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 1037478
Bug #1037478 {Done: Matthias Klose } [ca-certificates-java] 
ca-certificates-java: Loop in the execution of the trigger
Unarchived Bug 1037478
> tag 1037478 + bookworm
Bug #1037478 {Done: Matthias Klose } [ca-certificates-java] 
ca-certificates-java: Loop in the execution of the trigger
Added tag(s) bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1037478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1054849: marked as done (haskell-clash-prelude: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 16 Nov 2023 03:07:54 +
with message-id 
and subject line Bug#1054849: fixed in haskell-clash-prelude 1.8.1-1
has caused the Debian Bug report #1054849,
regarding haskell-clash-prelude: 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.)


-- 
1054849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-clash-prelude
Version: 1.6.6-2
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):
>  fakeroot 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-clash-prelude-doc.substvars
> dh_installdirs -plibghc-clash-prelude-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make /usr/share/haskell-devscripts/Setup-Simple.hs -o 
> debian/hlibrary.setup -outputdir debian/tmp-setup-hs
> [1 of 2] Compiling Main ( 
> /usr/share/haskell-devscripts/Setup-Simple.hs, debian/tmp-setup-hs/Main.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe'
> Running find . ! -newer /tmp/_CaCH2Lto5 -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-clash-prelude-dev
> libghc-clash-prelude-prof
> libghc-clash-prelude-doc
> Running dh_listpackages
> libghc-clash-prelude-dev
> libghc-clash-prelude-prof
> libghc-clash-prelude-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/clash-prelude-1.6.6/ 
> --datasubdir=clash-prelude 
> --htmldir=/usr/share/doc/libghc-clash-prelude-doc/html/ 
> --enable-library-profiling --enable-tests
> Using Parsec parser
> Configuring clash-prelude-1.6.6...
> Flags chosen: benchmarks=True, doctests=False, large-tuples=False,
> multiple-hidden=False, strict-mapsignal=False, super-strict=False,
> unittests=True, workaround-ghc-mmap-crash=False
> Dependency QuickCheck >=2.7 && <2.15: using QuickCheck-2.14.3
> Dependency array >=0.5.1.0 && <0.6: using array-0.5.4.0
> Dependency arrows >=0.4 && <0.5: using arrows-0.4.4.2
> Dependency base >=4.11 && <5: using base-4.17.2.0
> Dependency binary >=0.8.5 && <0.11: using binary-0.8.9.1
> Dependency bytestring >=0.10.8 && <0.12: using bytestring-0.11.5.2
> Dependency constraints >=0.9 && <1.0: using constraints-0.13.4
> Dependency containers >=0.4.0 && <0.7: using containers-0.6.7
> Dependency data-binary-ieee754 >=0.4.4 && <0.6: using
> data-binary-ieee754-0.4.4
> Dependency data-default-class >=0.1.2 && <0.2: using
> data-default-class-0.1.2.0
> Dependency deepseq >=1.4.1.0 && <1.5: using deepseq-1.4.8.0
> Dependency extra >=1.6.17 && <1.8: using extra-1.7.14
> Dependency ghc-bignum >=1.0 && <1.4: using ghc-bignum-1.3
> Dependency ghc-prim >=0.5.1.0 && <0.10: using ghc-prim-0.9.1
> Dependency ghc-typelits-extra >=0.4 && <0.5: using ghc-typelits-extra-0.4.6
> Dependency ghc-typelits-knownnat >=0.7.2 && <0.8: using
> ghc-typelits-knownnat-0.7.9
> Dependency ghc-typelits-natnormalise >=0.7.2 && <0.8: using
> ghc-typelits-natnormalise-0.7.9
> Dependency half >=0.2.2.3 && <1.0: using half-0.3.1
> Dependency hashable >=1.2.1.0 && <1.5: using hashable-1.4.3.0
> Dependency interpolate >=0.2 && <0.3: using interpolate-0.2.1
> Dependency lens >=4.10 && <5.3: using lens-5.2.3
> Dependency recursion-schemes >=5.1 && <5.3: using recursion-schemes-5.2.2.4
> Dependency reflection >=2 && <2.2: using reflection-2.1.7
> Dependency singletons >=2.0 && <3.1: using singletons-3.0.2
> Dependency template-haskell >=2.12.0.0 && <2.20: using
> template-haskell-2.19.0.0
> Dependency text >=0.11.3.1 && <2.1: using text-2.0.2
> Dependency th-abstraction >=0.2.10 && <0.5.0: using th-abstraction-0.4.5.0
> Dependency th-lift >=0.7.0 && <0.9: using th-lift-0.8.4
> Dependency th-orphans >=0.13.1 && <1.0: using 

Bug#1055635: marked as done (haskell-copilot-c99 FTBFS on !amd64)

[Debian Bug Tracking System]

Your message dated Thu, 16 Nov 2023 03:08:01 +
with message-id 
and subject line Bug#1055635: fixed in haskell-copilot-c99 3.17-2
has caused the Debian Bug report #1055635,
regarding haskell-copilot-c99 FTBFS on !amd64
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.)


-- 
1055635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-copilot-c99
Version: 3.16.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=haskell-copilot-c99=3.16.1-1

...
Copilot.Compile.C99:
  Compile specification: [OK, passed 1 tests]
  Compile specification in custom dir: [OK, passed 1 tests]
  Run specification: [Failed]
*** Failed! Exception: 'callProcess: ./main (exit 1): failed' (after 1 test):
...
 Properties  Total  
 Passed  3   3  
 Failed  1   1  
 Total   4   4  
Test suite unit-tests: FAIL
Test suite logged to: dist-ghc/test/copilot-c99-3.16.1-unit-tests.log
0 of 1 test suites (0 of 1 test cases) passed.
...
--- End Message ---
--- Begin Message ---
Source: haskell-copilot-c99
Source-Version: 3.17-2
Done: Scott Talbert 

We believe that the bug you reported is fixed in the latest version of
haskell-copilot-c99, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Scott Talbert  (supplier of updated haskell-copilot-c99 
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: Wed, 15 Nov 2023 20:13:17 -0500
Source: haskell-copilot-c99
Architecture: source
Version: 3.17-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Scott Talbert 
Closes: 1055635
Changes:
 haskell-copilot-c99 (3.17-2) unstable; urgency=medium
 .
   * Fix FTBFS on !amd64 (Closes: #1055635)
Checksums-Sha1:
 0ae15cd79a0ab6e88a076866dedc85fbe5b0d474 3084 haskell-copilot-c99_3.17-2.dsc
 91c09d53fb06f75c9831c126352f2b8b0a879e7b 2804 
haskell-copilot-c99_3.17-2.debian.tar.xz
 3c74c5e25aeea4645eacf235e98be77bc883a66b 11218 
haskell-copilot-c99_3.17-2_amd64.buildinfo
Checksums-Sha256:
 7e41e40b7bcac58e5c5acd1514a585568c2a9cd1486ec2dbe8e6383dddbe8511 3084 
haskell-copilot-c99_3.17-2.dsc
 44fd83b4b26283234c35b06676926c5d4f4acb17452b8ceb25ac4d384a1d3dd1 2804 
haskell-copilot-c99_3.17-2.debian.tar.xz
 9956fc44dd50995f28fbfdd1aea5390cbb949043e99ca6e5624af9726bffbafd 11218 
haskell-copilot-c99_3.17-2_amd64.buildinfo
Files:
 26dbb3073c3b9dbad17f91c3f5206b97 3084 haskell optional 
haskell-copilot-c99_3.17-2.dsc
 635c3457077a4fc56e3eec85dda59fea 2804 haskell optional 
haskell-copilot-c99_3.17-2.debian.tar.xz
 66ce7ace2cb0777ecac6d14b7339fb45 11218 haskell optional 
haskell-copilot-c99_3.17-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmVVbhIPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iisbAQALSeL0Lvwn4qLX7Gxg0bFDVX1C49cNgKfLjf
EKwk7KgvWMt700iAjzpezJABjS9iNHDLRCx6ResLoFZHseF0/YlzECTH9SN2jlkX
RwM3nqjnAFGzy5HwW+o/8VP1InSBmrNxuUTGDvCdKpHm16o6pSwxkEUknyfwIqlN
N7//RFE7FDgpx4QY3xgU/xHRLTQreg1puXZ1/3q/ERxZfNxuspj6WjcHiN29UhC1
SxIXH0x5Ysbm3c73SsUflZgTlSx+XF44aM6X9uVA3fjuCjxGjvAJShRD6PaziZlb
0F0TyT1qFdkmft3+3rhtNDkXNg8P+kCtck0l0/mERbWCybUFmXyOEQ7AcdtRHD9V
OM1xfkOwHu9ngMij5edMStqFvc37Tvmns6tlXj6xOqlmIybcSGFLX765/LKmfic8
OOGt9Yf737aIGz3X1og3mUSPGyJ0iFOcer+SjKmdfDaGq/2+cQHUR/OJBEPPZHCI
9IdrWzXWvih8MG3VkdGvHDaKlMpEgut7EXMCwB2XlC0uDq9pIOozuIFFnsKKvKjP
d3Zy1Ymt+iCwE1qyeL60v4p7e9YqvMutSBGHf8p+awHPJ8snxltl+lWfvbJVLnHP
WKIuqRoLOOQH6nC58KuqJ7OaHeVPNlQSIlB8y3jKZwDLOB2KQRz80h55w5h1ku/r
yNCmtqRC
=eudK
-END PGP SIGNATURE End Message ---

Bug#1028165: marked as done (libfltk1.3-dev: Missing dependency on fluid?)

[Debian Bug Tracking System]

Your message dated Thu, 16 Nov 2023 03:07:42 +
with message-id 
and subject line Bug#1028165: fixed in fltk1.3 1.3.8-6
has caused the Debian Bug report #1028165,
regarding libfltk1.3-dev: Missing dependency on fluid?
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.)


-- 
1028165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfltk1.3-dev
Version: 1.3.8-5
Severity: serious
Tags: ftbfs
Control: affects -1 src:giada

https://buildd.debian.org/status/fetch.php?pkg=giada=amd64=0.22.0-1%2Bb1=1672996393=0

...
CMake Error at /usr/lib/fltk/FLTK-Targets.cmake:145 (message):
  The imported target "fluid" references the file

 "/usr/bin/fluid"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/fltk/FLTK-Targets.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/fltk/FLTKConfig.cmake:31 (include)
  CMakeLists.txt:330 (find_package)


-- Configuring incomplete, errors occurred!



This was likely broken by 1.3.8-5, the fix for #1017271 did
touch the cmake files:
https://tests.reproducible-builds.org/debian/history/giada.html
--- End Message ---
--- Begin Message ---
Source: fltk1.3
Source-Version: 1.3.8-6
Done: Aaron M. Ucko 

We believe that the bug you reported is fixed in the latest version of
fltk1.3, 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 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aaron M. Ucko  (supplier of updated fltk1.3 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: Wed, 15 Nov 2023 21:05:08 -0500
Source: fltk1.3
Architecture: source
Version: 1.3.8-6
Distribution: unstable
Urgency: medium
Maintainer: Aaron M. Ucko 
Changed-By: Aaron M. Ucko 
Closes: 1028165
Changes:
 fltk1.3 (1.3.8-6) unstable; urgency=medium
 .
   * debian/FLTK-Targets-none-tail.cmake: Properly honor FLTK_SKIP_FLUID
 when built with CMake 3.24+, which uses _cmake_import_check_targets
 rather than _IMPORT_CHECK_TARGETS.  (Closes: #1028165.)
   * Standards-Version: 4.6.2 (routine-update)
Checksums-Sha1:
 161265cacadd379f863ef8b46e54fa4bf8648b7d 2803 fltk1.3_1.3.8-6.dsc
 231a338b771a229f8fb3bd5d6dae59b9399dad60 50808 fltk1.3_1.3.8-6.debian.tar.xz
Checksums-Sha256:
 126fa7442d4420da3e40daa1f86253868a0e5341e851532d10fc53dca2ea93a1 2803 
fltk1.3_1.3.8-6.dsc
 ef4ed45bf31736c658b291b7b4480dd2243087e48e1173bf2d54e66726058e0e 50808 
fltk1.3_1.3.8-6.debian.tar.xz
Files:
 e88919e9de5bbb92969f4c16e58d8fdc 2803 libs optional fltk1.3_1.3.8-6.dsc
 b307f3dcf7d18dbd968a81a0ed762066 50808 libs optional 
fltk1.3_1.3.8-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfDq5z9IwvTDdAJxZHnCRsfFKZKIFAmVVeU0ACgkQHnCRsfFK
ZKK/UA//c2UvB70yDJFDiwdlqSqifqtTy6IxwUjdwehCssnvsYEczCmoXlB9+6j9
KrHU2+Jz7lY0ZNHSJjSCMPbWj7kxYmbDekVTpiNiVNy1n+JcAHPuaNpKkWxJTyMt
cj261U08AiSbc5+IfgQqyWJXJdlZNYof4qosXt/TVZyRtM7ujKhDsrqq7n2cakJ3
LOTJ7/XFTWr/gjCLU5u9xXcVvwuDmjIVNbyB0nop0T+2457reTx6lA0fZpEb3mNP
+FTfIPb8mpmi1lBN5oOWs0MetDrVVrHP7XOQJq8wAUNQoWoR0TH1j3qfLyfpcPaH
2yiQBUkMNzocsSIetOTID//irQ47YfvU0PJitTw8m2RmENICIyY320h4jt0/xx/c
FwkZ5SWIfJUFsHwv8TCrmU6gPaO5v/ltC7Boa6afvL72WK5WfH+c+KCUCDYBvwZk
0t/rdlJuQsIBriC6d3wTvvd42VkqZJn+qNEXkfPS3IdFpKSU0FOoKqUK8UZxj5gf
uxZkMzvdkG2Iysfo5XPRB68lco3TKFJcro9wrI2+G1ryqyhjgM07ndKfB2kdebFB
L8ybjuHV9bKSRylxtNto0wGdeRuUsDdROot+zyAaISsuxba7q1CopphjqqiGl/A7
/ASM9+qr3GGGUibSo9GnAcZnSYIdb8rpor06JJEyc8K38XK3ID8=
=CwNo
-END PGP SIGNATURE End Message ---

Processed: unarchiving 1028165, reassign 1028165 to libfltk1.3-dev

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 1028165
Bug #1028165 {Done: Michael Gilbert } [src:giada] 
libfltk1.3-dev: Missing dependency on fluid?
Unarchived Bug 1028165
> reassign 1028165 libfltk1.3-dev 1.3.8-5
Bug #1028165 {Done: Michael Gilbert } [src:giada] 
libfltk1.3-dev: Missing dependency on fluid?
Bug reassigned from package 'src:giada' to 'libfltk1.3-dev'.
No longer marked as found in versions giada/0.22.0-1.
No longer marked as fixed in versions giada/0.22.0-2.
Bug #1028165 {Done: Michael Gilbert } [libfltk1.3-dev] 
libfltk1.3-dev: Missing dependency on fluid?
Marked as found in versions fltk1.3/1.3.8-5.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1028165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055901: Acknowledgement (raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/)

[Fabrice Meyer]

I got this issue while upgrading from bullseye to bookworm

I opened this PR
https://salsa.debian.org/debian/raspi-firmware/-/merge_requests/33 on
salsa. It might do the job. I just tested the small if I added, I'd be
glad if someone is able to make test in condition of this.

Regards,

Fabrice

Processed: (No Subject)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1024079 + ipv6
Bug #1024079 [src:uvloop] uvloop FTBFS on IPV6-only buildds
Added tag(s) ipv6.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1024079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1024079: uvloop FTBFS on IPV6-only buildds

[Dale Richards]

On Monday, 13 November 2023 at 09:13, d...@dalerichards.net 
 wrote:

> The attached patch should make the test agnostic to IP version.

My apologies - in my haste to post I accidentally attached the wrong version of 
the patch, which does not actually work. Please disregard.

In further testing, I've also found that the "correct" version of the patch is 
also imperfect, so I'm working on a more complete patch that will allow uvloop 
to build on IPv6-only hosts. I'll post it as soon as it's ready.

Best regards,
Dale Richards

Bug#1055962: intel-microcode: CVE-2023-23583: INTEL-SA-00950

[Salvatore Bonaccorso]

Proposed changes to rebase to 20231114 in
https://salsa.debian.org/hmh/intel-microcode/-/merge_requests/10

Regards,
Salvatore

Processed: Re: Bug#1013285: needrestart: Failed to check for processor microcode upgrades.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #1013285 [needrestart] needrestart: Failed to check for processor microcode 
upgrades.
Bug #1032979 [needrestart] needrestart:  Failed to check for processor 
microcode upgrades.
Added tag(s) patch.
Added tag(s) patch.

-- 
1013285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013285
1032979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1013285: needrestart: Failed to check for processor microcode upgrades.

[Antoine Beaupré]

Control: tags -1 +patch

On 2023-11-15 14:54:26, Antoine Beaupré wrote:
> On 2022-06-20 13:54:38, Nick Lewycky wrote:
>> Package: needrestart
>> Version: 3.6-1
>> Severity: normal
>>
>> `sudo needrestart -w` always prints "Failed to check for processor
>> microcode upgrades." on my AMD Ryzen 9 3900X 12-Core Processor.
>
> [...]
>
> There's now a PR for this upstream:
>
> https://github.com/liske/needrestart/pull/285
>
> People suffering from this issue are encouraged to test this and report
> back upstream (or here, if you can't upstream).

I tested it and it doesn't work. It only *seemed* to work because the
author tested with -v, which *does* work around the issue.

I found the issue, and sent this PR upstream to fix it:

https://github.com/liske/needrestart/pull/288

Patch attached, people are again encouraged to test and report back.

I also attach upstream commit v3.6-9-ge85bfe3 which also seem necessary
to fix firmware checks on my end...

a.

-- 
Advertisers, not governments, are the primary censors of media content 
in the United States today.
- C. Edwin Baker
>From b073fb6d9969597173daa8c511a85bae9b03ed37 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= 
Date: Wed, 15 Nov 2023 15:20:37 -0500
Subject: [PATCH] fix AMD ucode checking in non-debug mode

It looks like the assignment when the ucode exist was not
done *unless* `debug` (`-v`) was set. Therefore, all AMD microcode
checks were returning UNKNOWN, including in Nagios checks, unless the
`-v` ("verbose", but actually `debug`) was passed.

Closes: #249
---
 perl/lib/NeedRestart/uCode/AMD.pm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/perl/lib/NeedRestart/uCode/AMD.pm b/perl/lib/NeedRestart/uCode/AMD.pm
index 638e68d..6daad8f 100644
--- a/perl/lib/NeedRestart/uCode/AMD.pm
+++ b/perl/lib/NeedRestart/uCode/AMD.pm
@@ -185,8 +185,8 @@ sub nr_ucode_check_real {
 if ( exists( $_ucodes->{cpuid}->{$cpuid} ) ) {
 my $prid = $_ucodes->{cpuid}->{$cpuid};
 if ( exists( $_ucodes->{prid}->{$prid} ) ) {
-$vars{AVAIL} = sprintf( "0x%08x", $_ucodes->{prid}->{$prid} ),
-		print STDERR "$LOGPREF #$info->{processor} found ucode $vars{AVAIL}\n" if ($debug);
+$vars{AVAIL} = sprintf( "0x%08x", $_ucodes->{prid}->{$prid} );
+print STDERR "$LOGPREF #$info->{processor} found ucode $vars{AVAIL}\n" if ($debug);
 	}
 }
 
-- 
2.39.2

>From e85bfe33b595b88cc8052a7815d13612ecc2a841 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Stefan=20B=C3=BChler?= 
Date: Sun, 28 May 2023 17:42:28 +0200
Subject: [PATCH] [uCode] fix uninitialized value in logging of processor index

This got broken in f8c2609f8d5a0e10bd988497b8ea9815a7bb2fa8.

Before that it would have effectively logged
`$processors{$pid}->{processor}`, but the `processor` entry
is also the key in `%processors`, i.e. equals `$pid`.
---
 perl/lib/NeedRestart/uCode.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/perl/lib/NeedRestart/uCode.pm b/perl/lib/NeedRestart/uCode.pm
index 6251339..db81375 100644
--- a/perl/lib/NeedRestart/uCode.pm
+++ b/perl/lib/NeedRestart/uCode.pm
@@ -148,7 +148,7 @@ sub nr_ucode_check {
 }
 $ui->progress_step;
 
-my $nstate = compare_ucode_versions( $debug, $processors{processor}, @nvars );
+my $nstate = compare_ucode_versions( $debug, $pid, @nvars );
 if ( $nstate > $state ) {
 ( $state, @vars ) = ( $nstate, @nvars );
 }
-- 
2.39.2

Bug#1013285: needrestart: Failed to check for processor microcode upgrades.

[Antoine Beaupré]

On 2022-06-20 13:54:38, Nick Lewycky wrote:
> Package: needrestart
> Version: 3.6-1
> Severity: normal
>
> `sudo needrestart -w` always prints "Failed to check for processor
> microcode upgrades." on my AMD Ryzen 9 3900X 12-Core Processor.

[...]

There's now a PR for this upstream:

https://github.com/liske/needrestart/pull/285

People suffering from this issue are encouraged to test this and report
back upstream (or here, if you can't upstream).

I've also bumped the severity of this bug. For us it leads to alert
fatigue and creates security and reliability issues.

a.
-- 
Je viens d'un pays où engagé veut dire que tu t'es trouvé une job.
- Patrice Desbiens

Processed: severity of 1013285 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1013285 grave
Bug #1013285 [needrestart] needrestart: Failed to check for processor microcode 
upgrades.
Bug #1032979 [needrestart] needrestart:  Failed to check for processor 
microcode upgrades.
Severity set to 'grave' from 'normal'
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013285
1032979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055485: marked as done (libpam-systemd needs a versioned conflict for libpam-elogind-compat)

[Debian Bug Tracking System]

Your message dated Wed, 15 Nov 2023 19:09:34 +
with message-id 
and subject line Bug#1055485: fixed in systemd 255~rc2-1
has caused the Debian Bug report #1055485,
regarding libpam-systemd needs a versioned conflict for libpam-elogind-compat
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.)


-- 
1055485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055485
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 ---
Source: systemd
Source-Version: 255~rc2-1
Done: Luca Boccassi 

We believe that the bug you reported is fixed in the latest version of
systemd, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated systemd 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: Wed, 15 Nov 2023 17:10:26 +
Source: systemd
Architecture: source
Version: 255~rc2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Luca Boccassi 
Closes: 1053301 1055485 1055863
Changes:
 systemd (255~rc2-1) unstable; urgency=medium
 .
   [ Matthias Geiger ]
   * Bump version number for udev.postinst and udev.maintscript
   * Fix udev.postinst to preserve the enablement of the init script. When
 transferring ownership of the udev init script to sysvinit, the
 service was disabled as it didn't check for enablement before calling
 update-rc.d. Thanks to Mark Hindley for the original fix. (Closes:
 #1053301)
 .
   [ Luca Boccassi ]
   * New upstream version 255~rc2
   * Drop fix-build-without-SBAT_DISTRO.patch, merged upstream
   * Refresh patches
   * Upload to unstable
 .
 systemd (255~rc1-4) experimental; urgency=medium
 .
   * Add version to Conflict with molly-guard
   * Move systemd-hwdb-update.service to udev package. Commit a12cf5d187cb
 in 249-1 removed systemd-hwdb-update.service from udev, and 254.4-1
 re-added it in systemd, so move it back to udev. (Closes: #1055863)
 .
 systemd (255~rc1-3) experimental; urgency=medium
 .
   * Do not ship repart.standalone and shutdown.standalone
   * /usr/lib/sysvinit/telinit was dropped long ago, use /usr/sbin/telinit
   * Add Suggests: libip4tc2 as it is now dlopen'ed
   * Drop rc/rcS masking, no longer necessary
   * Add Conflicts to avoid issues due to DEP17P3. libpam-elogind-compat,
 opensysusers, bfh-container, molly-guard, and progress-linux-container
 divert files from our packages, so DEP17P3 is triggered. Add
 unversioned conflicts until those diversions are updated according to
 DEP17M18, and then we can make the conflicts versioned. (Closes:
 

Bug#1055228: plplot: FTBFS on armhf (test segfault)

[Emanuele Rocca]

Hi!

On 2023-11-09 05:11, Rafael Laboissière wrote:
> The Fortran example x09f.f90, which is exercised during the building of
> plplot, now fails on armhf, due to the use of the compiler option
> -fstack-clash-protection.

The problem seems unrelated to stach-clash-protection I think, enabling
the feature on armhf just made it evident.

Building the program on a x86 system without -fstack-clash-protection
but with -fsanitize=address, it segfaults:

 /usr/bin/gfortran -g -O2 x09f.f90 -o x09f 
-I/usr/lib/x86_64-linux-gnu/fortran/modules/plplot -lplplotfortran 
-fsanitize=address
 ./x09f -dev ps -o /dev/null

 Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

The SIGSEGV happens in plplot_single::pltransformf2c, which is about
where the SIGBUS happens on armhf with stack-clash-protector enabled:

 Program received signal SIGSEGV, Segmentation fault.
 0x75a000a8 in ?? ()
 (gdb) bt
 #0  0x75a000a8 in ?? ()
 #1  0x77f05683 in plplot_single::pltransformf2c (x=x@entry=0, 
y=y@entry=1, tx=4.9406564584124654e-324, 
 ty=6.9533558054215925e-310, data=)
 at ./bindings/fortran/plplot_single.f90:114

Here's the SIGBUS on armhf with stack-clash-protection:

 Program received signal SIGBUS, Bus error.
 0x00400822 in x09f::mypltr (x=0, y=1, xt=0, yt=0) at x09f.f90:38
 38  xt = tr(1) * x + tr(2) * y + tr(3)
 (gdb) bt
 #0  0x00400822 in x09f::mypltr (x=0, y=1, xt=0, yt=0) at x09f.f90:38
 #1  0xf7f58a06 in plplot_single::pltransformf2c (x=, 
y=, tx=-9.8841854819221187e+269, 
 ty=-nan(0xe5db40001), data=) at 
./bindings/fortran/plplot_single.f90:114

Bug#1055990: marked as done (geany-plugins: FTBFS with build=all)

[Debian Bug Tracking System]

Your message dated Wed, 15 Nov 2023 16:21:45 +
with message-id 
and subject line Bug#1055990: fixed in geany-plugins 2.0-2.2
has caused the Debian Bug report #1055990,
regarding geany-plugins: FTBFS with build=all
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.)


-- 
1055990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: geany-plugins
Version: 2.0-2
Severity: serious

The packages fails to build from souce for build=all builds:
dh_installdocs
cd debian/geany-plugin-latex/usr/share/doc/geany-plugin-latex/ && \
ls -1 *.html |  
\
while read -r file; do  
\
iconv --from=iso-8859-1 --to=utf-8 "$file" |   \
sponge "$file";\
done
/bin/sh: 1: cd: can't cd to 
debian/geany-plugin-latex/usr/share/doc/geany-plugin-latex/
--- End Message ---
--- Begin Message ---
Source: geany-plugins
Source-Version: 2.0-2.2
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
geany-plugins, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated geany-plugins 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: Wed, 15 Nov 2023 16:10:58 +0100
Source: geany-plugins
Architecture: source
Version: 2.0-2.2
Distribution: unstable
Urgency: medium
Maintainer: Geany Packaging Team 
Changed-By: Bastian Germann 
Closes: 1055990
Changes:
 geany-plugins (2.0-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Enable building arch-all packages (Closes: #1055990)
Checksums-Sha1:
 3e8ac82b0452768051d5341afc609793936d5f1d 5805 geany-plugins_2.0-2.2.dsc
 ace0a4215d72c5a47796b363ec952df1e1b673a8 25416 
geany-plugins_2.0-2.2.debian.tar.xz
 16fea527ec36e4665b163a2ec94971e518de526d 20232 
geany-plugins_2.0-2.2_source.buildinfo
Checksums-Sha256:
 a52cbbf672eacf7b7b511993ecb11ffcaa884ef9014e3b1bce5ba34242c14cb2 5805 
geany-plugins_2.0-2.2.dsc
 87366e348939fb9ec7107d15292e023540079cece0621e390ae70cccdfc5dcd7 25416 
geany-plugins_2.0-2.2.debian.tar.xz
 6c111c7a5ea13c358b246f9a5d68c74425ee88aa03ff73b22897c7e4d461fec3 20232 
geany-plugins_2.0-2.2_source.buildinfo
Files:
 938e7be35cb4706e38bc33c5fb131215 5805 devel optional geany-plugins_2.0-2.2.dsc
 64d0f55f62f870541c6b12ef525a6226 25416 devel optional 
geany-plugins_2.0-2.2.debian.tar.xz
 9db728698bb7a9d87eba35a8e0916124 20232 devel optional 
geany-plugins_2.0-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmVU7ZUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFBbzC/9Y0386f1vsXBm2PbD9CHPbdlqG46byQI/A
b7G28q2fF2roO6YaMYQlpelmH4AnK+JRFGYP3zR/RMyWbaIKBDYcZqr4t7m5jIWf
nn3Bar9Ddm9sGL0Of8qFI49oY3/g4xnvjWDOt4bq3NvL1sQTc3qWts9Yy3Hj89AA
pX79nipDt2HLFDCxiCjb8y7rbpWjcXy3VQVWB4mJDbaNWdsjZzHm01d6yGaefqpR
LaXGGXLL5IjM+vMRYoROUR5dj8V4aB25VZ4JxFVdJAscQzvLZdjdMy8aNA7ZvU3P
Ut+gMvD7Jp8G1kvdIh3bLZMt8eOIWdhVMpAFUkqvN9BzdX5IyPD3JTV7JPqH8rBC
/WCsUbZ7SZqxCVtkOiUEK34Acc9XFa5Zpm7eZ5hCIuC64wOWy7MG0Y3r5RwZEL9K
PDkEMOD0+taavAIrwWq+Rxu9lZUKBVYyCFQI7r3sYK6+RPK+WvoN6bDCls+uuMJB
BBTN4vqYBqhvZrhpmxQ6JZQEqx3O+rA=
=esxf
-END PGP SIGNATURE End Message ---

Bug#1055901: [Pkg-raspi-maintainers] Bug#1055901: raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/

[Cyril Brulebois]

ilf  (2023-11-15):
> reopen 1055901
> found 1055901 1:1.20231024+ds-1+rpt2
> 
> This seems to hit everyone with a Rasperry Pi who upgraded
> Debian/Raspian from bullseye to bookworm.

If a Raspbian package doesn't work on Raspbian systems, is the Debian
bug tracking system really the best place?


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature

Bug#1055990: geany-plugins: FTBFS with build=all

[Bastian Germann]

Source: geany-plugins
Version: 2.0-2
Severity: serious

The packages fails to build from souce for build=all builds:
dh_installdocs
cd debian/geany-plugin-latex/usr/share/doc/geany-plugin-latex/ && \
ls -1 *.html |  
\
while read -r file; do  
\
iconv --from=iso-8859-1 --to=utf-8 "$file" |   \
sponge "$file";\
done
/bin/sh: 1: cd: can't cd to 
debian/geany-plugin-latex/usr/share/doc/geany-plugin-latex/

Bug#1055901: raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/

[ilf]

reopen 1055901
found 1055901 1:1.20231024+ds-1+rpt2

This seems to hit everyone with a Rasperry Pi who upgraded 
Debian/Raspian from bullseye to bookworm.


https://forums.raspberrypi.com/viewtopic.php?p=2157290 has a workaround:


1. Unmount the boot partition with `sudo umount /boot`
2. Create the new firmware directory: `sudo mkdir /boot/firmware`
3. Edit `/etc/fstab`, with `sudo nano /etc/fstab`, and replace `/boot` 
   to `/boot/firmware`; exit and save with `Ctrl+x` then Y then Enter.

4. Run `sudo systemctl daemon-reload`
5. Remount the boot partition again with `sudo mount -a`
6. Fix the installation, with `sudo apt-get dist-upgrade` and/or `sudo 
   apt-get -f install`.


Would be great if the package did that automatically.

Looks like someone might be working on this: 
https://github.com/MichaIng/DietPi/issues/6747


--
ilf

If you upload your address book to "the cloud", I don't want to be in it.

Bug#1055984: marked as done (gimp: CVE-2023-44441 CVE-2023-44442 CVE-2023-44443 CVE-2023-44444)

[Debian Bug Tracking System]

Your message dated Wed, 15 Nov 2023 14:35:34 +
with message-id 
and subject line Bug#1055984: fixed in gimp 2.10.36-1
has caused the Debian Bug report #1055984,
regarding gimp: CVE-2023-1 CVE-2023-2 CVE-2023-3 CVE-2023-4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1055984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gimp
Version: 2.10.34-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for gimp.

CVE-2023-1[0]:
| GIMP DDS File Parsing Heap-based Buffer Overflow Remote Code Execution
| Vulnerability


CVE-2023-2[1]:
| GIMP PSD File Parsing Heap-based Buffer Overflow Remote Code Execution
| Vulnerability


CVE-2023-3[2]:
| GIMP PSP File Parsing Integer Overflow Remote Code Execution
| Vulnerability


CVE-2023-4[3]:
| GIMP PSP File Parsing Off-By-One Remote Code Execution Vulnerability


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-1
https://www.cve.org/CVERecord?id=CVE-2023-1
[1] https://security-tracker.debian.org/tracker/CVE-2023-2
https://www.cve.org/CVERecord?id=CVE-2023-2
[2] https://security-tracker.debian.org/tracker/CVE-2023-3
https://www.cve.org/CVERecord?id=CVE-2023-3
[3] https://security-tracker.debian.org/tracker/CVE-2023-4
https://www.cve.org/CVERecord?id=CVE-2023-4

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gimp
Source-Version: 2.10.36-1
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 1055...@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: Wed, 15 Nov 2023 07:31:56 -0500
Source: gimp
Built-For-Profiles: noudeb
Architecture: source
Version: 2.10.36-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1055984
Changes:
 gimp (2.10.36-1) unstable; urgency=medium
 .
   * New upstream release
 - Fixed vulnerabilities (Closes: #1055984):
   + CVE-2023-1, ZDI-23-1592, ZDI-CAN-22093
   + CVE-2023-2, ZDI-23-1594, ZDI-CAN-22094
   + CVE-2023-3, ZDI-23-1593, ZDI-CAN-22096
   + CVE-2023-4, ZDI-23-1591, ZDI-CAN-22097
Checksums-Sha1:
 bad08d4e780f11f8df9c09a2f44ec4ec9a78eded 3502 gimp_2.10.36-1.dsc
 0311a880373ad36056d3a9220ebe201c5d9d4699 31532334 gimp_2.10.36.orig.tar.bz2
 adcb1f685f1dc3769def36e1392e83d84b88dd9c 58028 gimp_2.10.36-1.debian.tar.xz
 7ee8ac47303b2f80ed01eabbb627a24edbc68d31 15658 gimp_2.10.36-1_source.buildinfo
Checksums-Sha256:
 4b0b3ce7488b99ff2d893cda6c0cd8ac3ed271b8588f4ac5eec1d2a9120f0432 3502 
gimp_2.10.36-1.dsc
 3d3bc3c69a4bdb3aea9ba2d5385ed98ea03953f3857aafd1d6976011ed7cdbb2 31532334 
gimp_2.10.36.orig.tar.bz2
 aacb708ddfd0c9902bd2e41ed8fb359c7bb528fc1f39dd88b942cd688338c187 58028 
gimp_2.10.36-1.debian.tar.xz
 a8447d6ce545a62a2335a5a22548ddcb9de277317f3168f487a18c0c963f7c50 15658 
gimp_2.10.36-1_source.buildinfo
Files:
 0a986839f23a25b9d44669b264b3a860 3502 graphics optional gimp_2.10.36-1.dsc
 e44e1c91b09db8fcdc9ef5797ce11b77 31532334 graphics optional 
gimp_2.10.36.orig.tar.bz2
 0f629c2517ede154613d6135e541dc43 58028 graphics optional 
gimp_2.10.36-1.debian.tar.xz
 755eb3176ac9ed3e3e587462ec70a7f0 15658 graphics optional 
gimp_2.10.36-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmVU0gYACgkQ5mx3Wuv+
bH3HEQ/8DAU3rzxoGwF4PRfChTgxuHxDc0VpGRV38UmmtHcTWVKFjVp2U2h9qKgI
pW0umMa5xMh9tFfo1BRV5CsmeNkSh9ygwPVNAleQ36GNdBfwRL0Li3XWe0ZXu++r
5HQgUAv166e4HHGCtpsmTvdN4n5SJK/WDostwfwwHHB8RgHjJHfm2RRElTTdlerF

Processed: Re: Bug#1055981: wmforecast: Does not retrieve data; shows error

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libgweather4
Bug #1055981 [wmforecast] wmforecast: Does not retrieve data; shows error
Bug reassigned from package 'wmforecast' to 'libgweather4'.
No longer marked as found in versions wmforecast/1.9.0-1.
Ignoring request to alter fixed versions of bug #1055981 to the same values 
previously set

-- 
1055981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055981: wmforecast: Does not retrieve data; shows error

[Jeremy Sowden]

Control: reassign -1 libgweather4

On 2023-11-15, at 11:57:30 +0200, Yavor Doganov wrote:
> Package: wmforecast
> Version: 1.9.0-1
> Severity: grave
> X-Debbugs-Cc: Yavor Doganov 
> 
> Since some time (about 2 weeks, but I'm not entirely sure) wmforecast
> displays an image with a question mark along with the text "ERROR".  The
> following message(s) appear on the console:
> 
> $ LC_ALL=C wmforecast
> GWeather-Message: 11:51:41.964: Failed to get weather.gov point data: 
> [status: 404] Not Found
> GWeather-Message: 11:52:41.353: Failed to get weather.gov point data: 
> [status: 404] Not Found
> GWeather-Message: 11:53:41.349: Failed to get weather.gov point data: 
> [status: 404] Not Found
> 
> (process:179771): GWeather-WARNING **: 11:54:40.649: Failed to get METAR 
> data: HTTP/2 Error: NO_ERROR
> 
> My ~/GNUstep/Defaults/wmforecast:
> ,
> | {
> |   longitude = "27,91108";
> |   interval = 60;
> |   text = "#20b2aa";
> |   icondir = "/usr/share/wmforecast";
> |   units = c;
> |   background = "#00";
> |   latitude = "43,211375";
> | }
> `

This is not a bug in wmforecast per se.  It uses libgweather4 to
retrieve forecasts are retrieved by libgweather4 from weather.gov, and
it appears that 404's are being returned for some locations.

The example given in the API doc's at
https://www.weather.gov/documentation/services-web-api succeeds:

  GET /points/39.7456,-97.0892 HTTP/1.1
  Host: api.weather.gov
  Accept: application/geo+json
  User-Agent: (azazel.net, jer...@azazel.net)
  
  HTTP/1.1 200 OK
  Server: nginx/1.20.1
  Content-Type: application/geo+json
  Access-Control-Allow-Origin: *
  Access-Control-Expose-Headers: X-Correlation-Id, X-Request-Id, X-Server-Id
  X-Request-ID: 08058eeb-9934-448a-bb4d-da9735491564
  X-Correlation-ID: 9922208
  X-Server-ID: vm-bldr-nids-apiapp1.ncep.noaa.gov
  Cache-Control: public, max-age=85382, s-maxage=120
  Expires: Thu, 16 Nov 2023 12:41:45 GMT
  Date: Wed, 15 Nov 2023 12:58:43 GMT
  Content-Length: 3096
  Connection: keep-alive
  X-Edge-Request-ID: b07ff2
  Vary: Accept,Feature-Flags,Accept-Language
  Strict-Transport-Security: max-age=31536000 ; includeSubDomains ; preload
  
  {
  "@context": [
  "https://geojson.org/geojson-ld/geojson-context.jsonld;,
  ...
  
However, if I send your latitude and longitude, I get a 404:

  GET /points/43.2113,27.911 HTTP/1.1
  Host: api.weather.gov
  Accept: application/geo+json
  User-Agent: (azazel.net, jer...@azazel.net)
  
  HTTP/1.1 404 Not Found
  Server: nginx/1.20.1
  Content-Type: application/problem+json
  X-Request-ID: 2f158817-e80e-40b1-bcb0-1ef801e85f04
  X-Correlation-ID: 3db7f703
  X-Server-ID: vm-bldr-nids-apiapp12.ncep.noaa.gov
  Access-Control-Allow-Origin: *
  Access-Control-Expose-Headers: X-Correlation-Id, X-Request-Id, X-Server-Id
  Pragma: no-cache
  Content-Length: 304
  Cache-Control: private, must-revalidate, max-age=86353
  Expires: Thu, 16 Nov 2023 12:55:30 GMT
  Date: Wed, 15 Nov 2023 12:56:17 GMT
  Connection: keep-alive
  X-Edge-Request-ID: afdb0d
  Vary: Accept,Feature-Flags,Accept-Language
  Strict-Transport-Security: max-age=31536000 ; includeSubDomains ; preload
  
  {
  "correlationId": "3db7f703",
  "title": "Data Unavailable For Requested Point",
  "type": "https://api.weather.gov/problems/InvalidPoint;,
  "status": 404,
  "detail": "Unable to provide data for requested point 43.2113,27.911",
  "instance": "https://api.weather.gov/requests/3db7f703;
  }

I am going to reassign this bug to libgweather4.

J.


signature.asc
Description: PGP signature

Bug#1037373: marked as done (geany-plugins: build-depends on transitional package libgdk-pixbuf2.0-dev)

[Debian Bug Tracking System]

Your message dated Wed, 15 Nov 2023 14:09:39 +0100
with message-id <32646a32-8d0d-4e41-90b5-433a72519...@debian.org>
and subject line Re: geany-plugins: build-depends on transitional package 
libgdk-pixbuf2.0-dev
has caused the Debian Bug report #1037373,
regarding geany-plugins: build-depends on transitional package 
libgdk-pixbuf2.0-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geany-plugins
Version: 1.38+dfsg-2
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: split-gdk-pixbuf

This package Build-Depends on libgdk-pixbuf2.0-dev.

In Debian 11, libgdk-pixbuf2.0-dev was split into two packages:

- libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library

- libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained
  Xlib integration layer, gdk-pixbuf-xlib-2.0

If this package only requires functionality from gdk-pixbuf-2.0.pc
and , please update the build-dependency to
libgdk-pixbuf-2.0-dev.

If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and
 (unlikely), then you can also build-depend on
libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove
that requirement.

libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so
it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative
dependency, even for packages that are expected to be backported.

We should remove the libgdk-pixbuf2.0-dev transitional package during
the Debian 13 'trixie' cycle, so this bug is likely to become RC later.

Thanks,
smcv
--- End Message ---
--- Begin Message ---

Version: 2.0-1--- End Message ---

Processed: patch for bedtools FTBFS on i386 with "intersect" tool failure

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1055414 [src:bedtools] bedtools: FTBFS on i386: "intersect" tool failure
Added tag(s) patch.

-- 
1055414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055414: patch for bedtools FTBFS on i386 with "intersect" tool failure

[Étienne Mollier]

Control: tags -1 + patch

The below patch fixes the test failure.  There is a catch though
in that I think it introduces a baseline violation on i386, but
similar change was already needed in htslib to fix #942580.  I'm
not sure what to make of that for now.


--- a/debian/rules
+++ b/debian/rules
@@ -6,7 +6,7 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 include /usr/share/dpkg/default.mk
 ifneq (,$(filter $(DEB_HOST_ARCH),i386 kfreebsd-i386 hurd-i386))
-  export DEB_CXXFLAGS_MAINT_APPEND=-ffloat-store
+  export DEB_CXXFLAGS_MAINT_APPEND=-msse -mfpmath=sse
 endif
 
 %:

-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/5, please excuse my verbosity
   `-


signature.asc
Description: PGP signature

Bug#1055984: gimp: CVE-2023-44441 CVE-2023-44442 CVE-2023-44443 CVE-2023-44444

[Salvatore Bonaccorso]

Source: gimp
Version: 2.10.34-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for gimp.

CVE-2023-1[0]:
| GIMP DDS File Parsing Heap-based Buffer Overflow Remote Code Execution
| Vulnerability


CVE-2023-2[1]:
| GIMP PSD File Parsing Heap-based Buffer Overflow Remote Code Execution
| Vulnerability


CVE-2023-3[2]:
| GIMP PSP File Parsing Integer Overflow Remote Code Execution
| Vulnerability


CVE-2023-4[3]:
| GIMP PSP File Parsing Off-By-One Remote Code Execution Vulnerability


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-1
https://www.cve.org/CVERecord?id=CVE-2023-1
[1] https://security-tracker.debian.org/tracker/CVE-2023-2
https://www.cve.org/CVERecord?id=CVE-2023-2
[2] https://security-tracker.debian.org/tracker/CVE-2023-3
https://www.cve.org/CVERecord?id=CVE-2023-3
[3] https://security-tracker.debian.org/tracker/CVE-2023-4
https://www.cve.org/CVERecord?id=CVE-2023-4

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1037373: geany-plugins: NMU 1.38+dfsg-2.1

[Bastian Germann]

On Sun, 17 Sep 2023 22:26:25 +0200 Bastian Germann  wrote:

I am uploading a NMU to fix this. The debdiff is attached.

The NMU was ignored and a new revision uploaded without its changes.
Please consider applying the changes on top of your new version.

I have reopened #1041807 and #1037373.

Processed: bedtools: FTBFS on i386: "intersect" tool failure forwarded upstream

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1055414 https://github.com/arq5x/bedtools2/issues/1072
Bug #1055414 [src:bedtools] bedtools: FTBFS on i386: "intersect" tool failure
Set Bug forwarded-to-address to 
'https://github.com/arq5x/bedtools2/issues/1072'.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
1055414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055981: wmforecast: Does not retrieve data; shows error

[Yavor Doganov]

Package: wmforecast
Version: 1.9.0-1
Severity: grave
X-Debbugs-Cc: Yavor Doganov 

Since some time (about 2 weeks, but I'm not entirely sure) wmforecast
displays an image with a question mark along with the text "ERROR".  The
following message(s) appear on the console:

$ LC_ALL=C wmforecast
GWeather-Message: 11:51:41.964: Failed to get weather.gov point data: [status: 
404] Not Found
GWeather-Message: 11:52:41.353: Failed to get weather.gov point data: [status: 
404] Not Found
GWeather-Message: 11:53:41.349: Failed to get weather.gov point data: [status: 
404] Not Found

(process:179771): GWeather-WARNING **: 11:54:40.649: Failed to get METAR data: 
HTTP/2 Error: NO_ERROR

My ~/GNUstep/Defaults/wmforecast:
,
| {
|   longitude = "27,91108";
|   interval = 60;
|   text = "#20b2aa";
|   icondir = "/usr/share/wmforecast";
|   units = c;
|   background = "#00";
|   latitude = "43,211375";
| }
`

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 6.5.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.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 wmforecast depends on:
ii  ca-certificates  20230311
ii  libc62.37-12
ii  libgeoclue-2-0   2.7.1-1
ii  libglib2.0-0 2.78.1-4
ii  libgweather-4-0  4.4.0-1
ii  libwings30.96.0-2+b1
ii  libwraster6  0.96.0-2+b1
ii  libwutil50.96.0-2+b1
ii  libx11-6 2:1.8.7-1

wmforecast recommends no packages.

wmforecast suggests no packages.

-- no debconf information

Processed: pandoc-sidenote needs a source upload for ghc 9.4

[Debian Bug Tracking System]

Processing control commands:

> affects -1 libghc-pandoc-sidenote-doc
Bug #1055980 [src:pandoc-sidenote] pandoc-sidenote needs a source upload for 
ghc 9.4
Added indication that 1055980 affects libghc-pandoc-sidenote-doc

-- 
1055980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055980: pandoc-sidenote needs a source upload for ghc 9.4

[Adrian Bunk]

Source: pandoc-sidenote
Version: 0.22.1.0-2
Severity: serious
X-Debbugs-Cc: Jonas Smedegaard 
Control: affects -1 libghc-pandoc-sidenote-doc

The following packages have unmet dependencies:
 libghc-pandoc-sidenote-doc : Depends: haddock-interface-38

Processed: unarchive

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 1037373
Bug #1037373 {Done: Bastian Germann } [src:geany-plugins] 
geany-plugins: build-depends on transitional package libgdk-pixbuf2.0-dev
Unarchived Bug 1037373
> reopen 1037373
Bug #1037373 {Done: Bastian Germann } [src:geany-plugins] 
geany-plugins: build-depends on transitional package libgdk-pixbuf2.0-dev
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions geany-plugins/1.38+dfsg-2.1.
> unarchive 1041807
Bug #1041807 {Done: Bastian Germann } [src:geany-plugins] 
geany-plugins: build-depends on libwnck-dev, and indirectly on GTK 2
Unarchived Bug 1041807
> reopen 1041807
Bug #1041807 {Done: Bastian Germann } [src:geany-plugins] 
geany-plugins: build-depends on libwnck-dev, and indirectly on GTK 2
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions geany-plugins/1.38+dfsg-2.1.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1037373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037373
1041807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1054508: Connman: breaks connections, uses 1 CPU core, and trashes disk space

[Vignesh Raman]

Hi,

Please could you test with connman 1.42-1 in sid
and see if you still see the issue. Thanks.

Regards,
Vignesh

On 24/10/23 23:30, программист некто wrote:

Package: connman
Version: 1.41-3
Severity: critical

Hello. I encountered with a problem: Connman randomly is getting inadequate.

Symptoms (simultaneously):
1. All existing connections stop working, cannot establish new.
2. Connman uses 1 CPU core.
3. Creates temporary file /var/lib/connman/stats.<6 random characters>.tmp
4. Connman don't responding to CLI or GUI, and signal SIGTERM.

I have a guess, that bug occurs when Connman tries to reconnect to Wi-Fi 
network.

$ top
   PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
  3281 root  20   0   42988  32504  31352 R  99,3   0,9   2:38.19 connmand

   
Temporary files:

$ ls -l /var/lib/connman | grep "tmp"
-rw--- 1 root root 23592960 окт 22 10:38 stats.0W91C2.tmp
-rw--- 1 root root 21585920 окт 22 11:46 stats.25A7C2.tmp
-rw--- 1 root root 67358720 окт 22 10:35 stats.UD8ED2.tmp

Connman writes to a temporary file until free disk space is end.
If free space is end, then systemd kills Connman and restart it.
"stats.<>.tmp" contains 'header' and 'record', that infinity repeated.

'header' contains:
position 0x8-0xB for every file differs.
   16 B9 00 FA  14 00 00 00  94 85 41 01  FF FF FF FF
0010   FF FF FF FF  00 00 00 00  00 00 00 00  00 00 00 00
0020   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00
0030   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00
repeated 'record' contains:
0040   00 00 00 00  D4 5B 05 00  32 F4 35 63  00 00 00 00
0050   4B 30 25 00  3E DB 18 00  C9 A0 C0 6E  6B E0 59 31
0060   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00
0070   BE 0A 06 00  00 00 00 00  2C DB 27 00  FF 4E 1A 00
0080   35 70 EC 7C  CC 64 0E 32  00 00 00 00  00 00 00 00
0090   00 00 00 00  00 00 00 00  8A 5C 07 00  08 55 39 63

syslog (when bug occured and I try to stop Connman, MAC adress removed):
Oct 23 11:46:44 debian-gateway connman-vpnd[9104]: wlan0 {update} flags 36867 

Oct 23 11:46:44 debian-gateway connman-vpnd[9104]: wlan0 {newlink} index 3 
address #WLAN_MAC# mtu 1500
Oct 23 11:46:44 debian-gateway connman-vpnd[9104]: wlan0 {newlink} index 3 operstate 
2 
Oct 23 11:46:44 debian-gateway connmand[9092]: wlan0 {RX} 289974 packets 
415132327 bytes
Oct 23 11:46:44 debian-gateway connmand[9092]: wlan0 {TX} 139436 packets 
15087832 bytes
Oct 23 11:46:44 debian-gateway kernel: rtlwifi: AP off, try to reconnect now
Oct 23 11:46:44 debian-gateway kernel: wlan0: Connection to AP #AP_MAC# lost
Oct 23 11:46:44 debian-gateway wpa_supplicant[532]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=#AP_MAC# reason=4 locally_generated=1
Oct 23 11:46:44 debian-gateway wpa_supplicant[532]: BSSID #AP_MAC# ignore list 
count incremented to 2, ignoring for 10 seconds
Oct 23 11:46:44 debian-gateway wpa_supplicant[532]: wlan0: 
CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Oct 23 11:46:50 debian-gateway kernel: wlan0: authenticate with #AP_MAC#
Oct 23 11:46:50 debian-gateway kernel: wlan0: 80 MHz not supported, disabling 
VHT
Oct 23 11:46:50 debian-gateway wpa_supplicant[532]: wlan0: SME: Trying to 
authenticate with #AP_MAC# (SSID=#SSID_NAME# freq=2462 MHz)
Oct 23 11:46:50 debian-gateway kernel: wlan0: send auth to #AP_MAC# (try 1/3)
Oct 23 11:46:50 debian-gateway wpa_supplicant[532]: wlan0: Trying to associate 
with #AP_MAC# (SSID=#SSID_NAME# freq=2462 MHz)
Oct 23 11:46:50 debian-gateway kernel: wlan0: authenticated
Oct 23 11:46:50 debian-gateway kernel: wlan0: associate with #AP_MAC# (try 1/3)
Oct 23 11:46:50 debian-gateway kernel: wlan0: associate with #AP_MAC# (try 2/3)
Oct 23 11:46:50 debian-gateway connman-vpnd[9104]: wlan0 {update} flags 102403 

Oct 23 11:46:50 debian-gateway connman-vpnd[9104]: wlan0 {newlink} index 3 
address #WLAN_MAC# mtu 1500
Oct 23 11:46:50 debian-gateway connman-vpnd[9104]: wlan0 {newlink} index 3 operstate 
5 
Oct 23 11:46:50 debian-gateway kernel: wlan0: RX AssocResp from #AP_MAC# 
(capab=0x431 status=0 aid=48)
Oct 23 11:46:50 debian-gateway kernel: wlan0: associated
Oct 23 11:46:50 debian-gateway wpa_supplicant[532]: wlan0: Associated with 
#AP_MAC#
Oct 23 11:46:50 debian-gateway wpa_supplicant[532]: wlan0: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Oct 23 11:46:50 debian-gateway wpa_supplicant[532]: wlan0: WPA: Key negotiation 
completed with #AP_MAC# [PTK=CCMP GTK=CCMP]
Oct 23 11:46:50 debian-gateway wpa_supplicant[532]: wlan0: CTRL-EVENT-CONNECTED 
- Connection to #AP_MAC# completed [id=2 id_str=]
Oct 23 11:46:50 debian-gateway connman-vpnd[9104]: wlan0 {update} flags 102467 

Oct 23 11:46:50 debian-gateway connman-vpnd[9104]: wlan0 {newlink} index 3 
address #WLAN_MAC# mtu 1500
Oct 23 11:46:50 debian-gateway connman-vpnd[9104]: wlan0 {newlink} index 3 operstate 
6 
Oct 23 11:46:50 debian-gateway wpa_supplicant[532]: bgscan simple: Failed to 
enable signal strength monitoring
Oct 23 11:47:37 

Bug#1054186: marked as done (icingadb: installs icingadb.service twice once dh_installsystemd installs to /usr)

[Debian Bug Tracking System]

Your message dated Wed, 15 Nov 2023 09:19:28 +
with message-id 
and subject line Bug#1054186: fixed in icingadb 1.1.1-2
has caused the Debian Bug report #1054186,
regarding icingadb: installs icingadb.service twice once dh_installsystemd 
installs to /usr
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.)


-- 
1054186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icingadb
Version: 1.1.1-1
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to change dh_installsystemd such that it installs units below
/usr to finalize the /usr-merge transition via DEP17. When doing so,
icingadb.service is installed to both /usr/lib/systemd/system (via
dh_installsystemd) and /lib/systemd/system (via dh_install). Doing so is
a policy violation. I'm attaching a patch for your convenience. Once I
upload debhelper, this bug will become release-critical.

Helmut
diff -Nru icingadb-1.1.1/debian/changelog icingadb-1.1.1/debian/changelog
--- icingadb-1.1.1/debian/changelog 2023-08-09 15:11:20.0 +0200
+++ icingadb-1.1.1/debian/changelog 2023-10-18 21:04:27.0 +0200
@@ -1,3 +1,10 @@
+icingadb (1.1.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd unit only once. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 18 Oct 2023 21:04:27 +0200
+
 icingadb (1.1.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru icingadb-1.1.1/debian/install icingadb-1.1.1/debian/install
--- icingadb-1.1.1/debian/install   2022-11-09 16:07:33.0 +0100
+++ icingadb-1.1.1/debian/install   2023-10-18 21:04:25.0 +0200
@@ -1,4 +1,3 @@
 #!/usr/bin/dh-exec
 config.example.yml   => etc/icingadb/config.yml
-debian/icingadb.service lib/systemd/system
 schema  usr/share/icingadb
--- End Message ---
--- Begin Message ---
Source: icingadb
Source-Version: 1.1.1-2
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
icingadb, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated icingadb 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: Wed, 15 Nov 2023 09:53:35 +0100
Source: icingadb
Architecture: source
Version: 1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Bas Couwenberg 
Closes: 1054186
Changes:
 icingadb (1.1.1-2) unstable; urgency=medium
 .
   [ Bas Couwenberg ]
   * Use dh-sequence-golang.
   * Update lintian overrides.
 .
   [ Helmut Grohne ]
   * Install systemd unit only once.
 (closes: #1054186)
Checksums-Sha1:
 51bdfe3ba16f0da93bdecb2f50b00b81985247ec 2341 icingadb_1.1.1-2.dsc
 e141101cde5d2948552883701ecb114df63b2b50 12624 icingadb_1.1.1-2.debian.tar.xz
 2eebd848a57d61b40278b562c710fd95027bef3f 9083 icingadb_1.1.1-2_amd64.buildinfo
Checksums-Sha256:
 14c6dc41b7aadfbf9de7e6d85fbe9ff310534fc40cccb22404b42bd3d09ed255 2341 
icingadb_1.1.1-2.dsc
 7d0cf860012dc86c566d08edfcb11d81b08442fe0f67369a3b5e37e03cad0777 12624 
icingadb_1.1.1-2.debian.tar.xz
 fe5c95fdfe53b5012d6f8adefbefff755a996d2337cb24beb649780605ad82a0 9083 
icingadb_1.1.1-2_amd64.buildinfo
Files:
 e7f57479e4e960a3995de2b928109c99 2341 admin optional icingadb_1.1.1-2.dsc
 3ac0f9c9e90d996d4cab60c0081ed1c7 12624 admin optional 
icingadb_1.1.1-2.debian.tar.xz
 05e4cada3bfa51df6e2b05b5be02c0d2 9083 admin optional 
icingadb_1.1.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmVUiBQACgkQZ1DxCuiN
SvH5qhAAse/ab4cOkmI6K+Xd0bUVdKknnjtUA4UaN10gAhui64JOAIiqb93cuLnu
3++72cpnqxLImW6cYt1RvqzxFC14HKrE2PH/oFxFT58I6UxV0HtWVvhP6VtpUW6Z
9TxR0sWkkwgCU44mkmc7Lo+N9R+hjdyfYVAtNMKkJeukEMfmp4dyk4d6Nn0fCmih
IwEIR6/O4BIbtoDFPvVYbyJZkRClXmmQA5vdIKZm5Yxu7Y7dM1K2RfdXCZNA0M0Q
Tnn9QrgPPVWWrCh6LWg2dlNDu8b9uy5eJOHJxqvlfP0LuWGU0+Wv0qDqongrjcto
AbVaW9FP/W0imVhvF/zGpl5xebYL//Vr87WmAmF8JZ53ICI4tEl4n7gqIExoO1bv
diHgo+3f0a3uw/OrDVbNQSXo5CDAFh05EDVdwTUFThRDfJIWYoPRqOEzGRqOmfNz

Processed: tagging 1055799

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1055799 + pending
Bug #1055799 [src:minetest] minetest-server: installs minetest-server@.service 
twice once dh_installsystemd installs to /usr
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1055874: intel-graphics-compiler: FTBFS in bookworm: Assertion `SupportedIntrinsics.find(CPU) != SupportedI, ntrinsics.end() && "Unknown Platform"' failed.

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 intel-graphics-compiler: FTBFS in bookworm with 
> intel-vc-intrinsics-dev 0.11
Bug #1055874 {Done: Santiago Vila } 
[src:intel-graphics-compiler] intel-graphics-compiler: FTBFS in bookworm: 
Assertion `SupportedIntrinsics.find(CPU) != SupportedI,ntrinsics.end() && 
"Unknown Platform"' failed.
Changed Bug title to 'intel-graphics-compiler: FTBFS in bookworm with 
intel-vc-intrinsics-dev 0.11' from 'intel-graphics-compiler: FTBFS in bookworm: 
Assertion `SupportedIntrinsics.find(CPU) != SupportedI,ntrinsics.end() && 
"Unknown Platform"' failed.'.

-- 
1055874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055874: intel-graphics-compiler: FTBFS in bookworm: Assertion `SupportedIntrinsics.find(CPU) != SupportedI, ntrinsics.end() && "Unknown Platform"' failed.

[Andreas Beckmann]

Control: retitle -1 intel-graphics-compiler: FTBFS in bookworm with 
intel-vc-intrinsics-dev 0.11

On 13/11/2023 11.49, Santiago Vila wrote:

Package: src:intel-graphics-compiler
Version: 1.0.12504.6-1



During a rebuild of all packages in bookworm, this package failed to build
with the following error:


vcb: ./GenXIntrinsics/lib/GenXIntrinsics/GenXIntrinsics.cpp:476: bool 
llvm::GenXIntrinsic::isSupport
edPlatform(const std::string&, unsigned int): Assertion 
`SupportedIntrinsics.find(CPU) != SupportedI

ntrinsics.end() && "Unknown Platform"' failed.


Reproducible here, too.

Comparing the buildd logfile (2022-12-08) with mine yields a possible
culprit:

-Setting up intel-vc-intrinsics-dev:amd64 (0.8.1-1) ...
+Setting up intel-vc-intrinsics-dev:amd64 (0.11.0-1) ...

...

Verified that building in current bookworm with intel-vc-intrinsics-dev
downgraded to 0.8.1 works fine, while it FTBFS with 0.11.0
(there were no intel-vc-intrinsics uploads between these two versions)


Andreas

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1054187 [dicod] dico: installs systemd units twice once dh_installsystemd 
installs to /usr
Severity set to 'serious' from 'normal'

-- 
1054187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1054186 [src:icingadb] icingadb: installs icingadb.service twice once 
dh_installsystemd installs to /usr
Severity set to 'serious' from 'normal'

-- 
1054186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1055799 [src:minetest] minetest-server: installs minetest-server@.service 
twice once dh_installsystemd installs to /usr
Severity set to 'serious' from 'normal'

-- 
1055799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1054485 [src:postfix] postfix: installs a systemd unit twice when 
dh_installsystemd installs below /usr
Severity set to 'serious' from 'normal'

-- 
1054485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1054489 [src:tarantool] tarantool: installs a systemd unit twice when 
dh_systemd_enable installs to /usr
Severity set to 'serious' from 'normal'

-- 
1054489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1054486 [src:sogo] sogo: installs sogo.service twice once 
dh_installsystemd installs to /usr
Severity set to 'serious' from 'normal'

-- 
1054486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1054484 [varnish] varnish: installs varnish.service twice once 
dh_installsystemd installs to /usr
Severity set to 'serious' from 'normal'

-- 
1054484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1054480 [src:dogtag-pki] dogtag-pki: installs a systemd unit twice once 
dh_installsystemd installs to /usr
Severity set to 'serious' from 'normal'

-- 
1054480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1054190 [src:arpon] arpon: installs arpon@.service twice once 
dh_installsystemd installs to /usr
Severity set to 'serious' from 'normal'

-- 
1054190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1054193 [src:arpwatch] arpwatch: installs arpwatch@.service twice once 
dh_installsystemd installs to /usr
Severity set to 'serious' from 'normal'

-- 
1054193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1054477 [src:autorandr] autorandr: install autorandr.service twice once 
dh_installsystemd installs to /usr
Severity set to 'serious' from 'normal'

-- 
1054477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: debhelper 13.11.8 uploaded with changed systemd helpers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1054188 [src:debci] debci: installs systemd unit twice once 
dh_installsystemd installs to /usr
Severity set to 'serious' from 'normal'

-- 
1054188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems