Bug#1031074: quickjs: QuickJS and security maintenance

[Sebastian Humenda]

Package: quickjs
Version: 2021.03.27-1
Severity: critical
X-Debbugs-Cc: secur...@debian.org


Hi

I have packaged QuickJS, an embeddable JavaScript engine. It is a direct
dependency for Edbrowse, a command-line browser, often used by blind users.
This currently blocks the update to the latest Edbrowse version.

QuickJS is on the same "security-sensitive" level as Duktape, i.e. it is a
JavaScript engine that, if exposed to untrusted sources, might have
vulnerabilities. Duktape is already in Debian, so I would argue that we could
also support QuickJS, hence seeking your feedback.

Upstream of *Edbrowse* said:

>> seems that QuickJS is not the most actively maintained project.
>
>Well, much more than duktape, which we used before. We had to drop duktape
>because it doesn't even support the es6 features of js, and emails to their
>maintainers went unanswered for months. In other words, duktape can't parse
>most of the js out there at this time.

I haven't talked to QuicJS upstream yet, mostly because I would need your
feedback and understand concerns, if any.

Thanks!
Sebastian

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

Kernel: Linux 6.1.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1030948: marked as done (rust-test-dir: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Sat, 11 Feb 2023 07:36:08 +
with message-id 
and subject line Bug#1030948: fixed in rust-test-dir 0.2.0-3
has caused the Debian Bug report #1030948,
regarding rust-test-dir: autopkgtest failure
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.)


-- 
1030948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-test-dir
Version: 0.2.0-2
Severity: serious

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

...
running 6 tests
test tests::test_testdir_temp_dir ... ok
test tests::test_testdir_remove ... ok
test tests::test_testdir_path ... ok
test tests::test_testdir_create ... ok
test tests::test_testdir_current_dir ... FAILED
test tests::test_testdir_current_rnd_dir ... FAILED

failures:

 tests::test_testdir_current_dir stdout 
thread 'tests::test_testdir_current_dir' panicked at 'Cannot create dir in 
current directory', src/lib.rs:155:13
stack backtrace:
   0: std::panicking::begin_panic
 at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:616:12
   1: test_dir::TestDir::current
 at /usr/share/cargo/registry/test-dir-0.2.0/src/lib.rs:155:13
   2: test_dir::tests::test_testdir_current_dir
 at /usr/share/cargo/registry/test-dir-0.2.0/src/lib.rs:335:23
   3: test_dir::tests::test_testdir_current_dir::{{closure}}
 at /usr/share/cargo/registry/test-dir-0.2.0/src/lib.rs:332:5
   4: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
   5: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.

 tests::test_testdir_current_rnd_dir stdout 
thread 'tests::test_testdir_current_rnd_dir' panicked at 'Cannot create temp 
dir in current directory', src/lib.rs:145:13
stack backtrace:
   0: std::panicking::begin_panic
 at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:616:12
   1: test_dir::TestDir::current_rnd
 at /usr/share/cargo/registry/test-dir-0.2.0/src/lib.rs:145:13
   2: test_dir::tests::test_testdir_current_rnd_dir
 at /usr/share/cargo/registry/test-dir-0.2.0/src/lib.rs:316:23
   3: test_dir::tests::test_testdir_current_rnd_dir::{{closure}}
 at /usr/share/cargo/registry/test-dir-0.2.0/src/lib.rs:313:5
   4: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
   5: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
tests::test_testdir_current_dir
tests::test_testdir_current_rnd_dir

test result: FAILED. 4 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.01s

error: test failed, to rerun pass `--lib`
autopkgtest [20:24:51]: test librust-test-dir-dev:: ---]
autopkgtest [20:24:51]: test librust-test-dir-dev::  - - - - - - - - - - 
results - - - - - - - - - -
librust-test-dir-dev: FAIL non-zero exit status 101
--- End Message ---
--- Begin Message ---
Source: rust-test-dir
Source-Version: 0.2.0-3
Done: Blair Noctis 

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

Debian distribution maintenance software
pp.
Blair Noctis  (supplier of updated rust-test-dir package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 11 Feb 2023 07:03:14 +
Source: rust-test-dir
Architecture: source
Version: 0.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Blair Noctis 
Closes: 1030948
Changes:
 rust-test-dir (0.2.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Patch to create test dirs in /tmp to avoid permission error
 (Closes: #1030948)
Checksums-Sha1:
 

Bug#1031073: librust-lewton+async-ogg-dev is not installable

[Adrian Bunk]

Package: librust-lewton+async-ogg-dev
Version: 0.9.4-3
Severity: serious

The following packages have unmet dependencies:
 librust-lewton+async-ogg-dev : Depends: librust-futures-0.1+default-dev
Depends: librust-ogg-0.7+async-dev
Depends: librust-ogg-0.7+default-dev
Depends: librust-tokio-io-0.1+default-dev

Bug#1031072: librust-rspotify-dev is not installable

[Adrian Bunk]

Package: librust-rspotify-dev
Version: 0.7.0-3
Severity: serious

The following packages have unmet dependencies:
 librust-rspotify-dev : Depends: librust-base64-0.12+default-dev
Depends: librust-itertools-0.9+default-dev
Depends: librust-rand-0.7+default-dev
Depends: librust-reqwest-0.9+default-dev but it is not 
installable

Bug#1031038: marked as done (rust-libsodium-sys: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Sat, 11 Feb 2023 07:22:49 +
with message-id 
and subject line Bug#1031038: fixed in rust-libsodium-sys 0.2.7-1
has caused the Debian Bug report #1031038,
regarding rust-libsodium-sys: autopkgtest failure
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.)


-- 
1031038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-libsodium-sys
Version: 0.2.5-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-libsodium-sys/31212775/log.gz

...
  process didn't exit successfully: 
`/tmp/tmp.Oamh8HTRc5/target/debug/build/libsodium-sys-17f33e83e141b528/build-script-build`
 (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=SODIUM_LIB_DIR
  cargo:rerun-if-env-changed=SODIUM_SHARED
  cargo:rerun-if-env-changed=SODIUM_USE_PKG_CONFIG
  cargo:rerun-if-env-changed=SODIUM_DISABLE_PIE

  --- stderr
  thread 'main' panicked at 'Failed to open libsodium-1.0.18.tar.gz: Os { code: 
2, kind: NotFound, message: "No such file or directory" }', build.rs:370:34
  stack backtrace:
 0: rust_begin_unwind
   at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
 1: core::panicking::panic_fmt
   at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
 2: core::result::unwrap_failed
   at /usr/src/rustc-1.63.0/library/core/src/result.rs:1805:5
 3: core::result::Result::expect
   at /usr/src/rustc-1.63.0/library/core/src/result.rs:1055:23
 4: build_script_build::get_archive
   at ./build.rs:370:13
 5: build_script_build::build_libsodium
   at ./build.rs:419:27
 6: build_script_build::main
   at ./build.rs:64:9
 7: core::ops::function::FnOnce::call_once
   at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
  note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.
autopkgtest [16:42:22]: test librust-libsodium-sys-dev: ---]
autopkgtest [16:42:22]: test librust-libsodium-sys-dev:  - - - - - - - - - - 
results - - - - - - - - - -
librust-libsodium-sys-dev FAIL non-zero exit status 101
autopkgtest [16:42:22]:  summary
@PASS
librust-libsodium-sys-dev FAIL non-zero exit status 101
--- End Message ---
--- Begin Message ---
Source: rust-libsodium-sys
Source-Version: 0.2.7-1
Done: Blair Noctis 

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

Debian distribution maintenance software
pp.
Blair Noctis  (supplier of updated rust-libsodium-sys package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 11 Feb 2023 06:56:36 +
Source: rust-libsodium-sys
Architecture: source
Version: 0.2.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Blair Noctis 
Closes: 1031038
Changes:
 rust-libsodium-sys (0.2.7-1) unstable; urgency=medium
 .
   * Team upload.
   * Package libsodium-sys 0.2.7 from crates.io using debcargo 2.6.0
   * Patch to always use Debian packaged libsodium (Closes: #1031038)
   * Add exclusion for `libsodium/`
Checksums-Sha1:
 02c1a54241b81d2cefd41eb4a204f39836b2e427 2368 rust-libsodium-sys_0.2.7-1.dsc
 3768b9874c6196f3ca711e301ef0b8f947a875b4 21293 
rust-libsodium-sys_0.2.7.orig.tar.gz
 33c0862bd2d5489c2bc4e4a0592b853106331da1 3708 
rust-libsodium-sys_0.2.7-1.debian.tar.xz
 5cca26a73f77bd9bd034cc7ed7e085765f29c13f 7732 
rust-libsodium-sys_0.2.7-1_source.buildinfo
Checksums-Sha256:
 be69dca828e88a672cf3fffe892a9172a025f3523d651e233f504d86749b42d2 2368 
rust-libsodium-sys_0.2.7-1.dsc
 0db93514976e08318808a4a24a1c564f18b882321fb360b67428cce60f46acd2 21293 
rust-libsodium-sys_0.2.7.orig.tar.gz
 2bbaf221b9da598fb1c05009debec5211fd3acd507697f2025d05486c70837ff 3708 
rust-libsodium-sys_0.2.7-1.debian.tar.xz
 93648e97ac6f10a6385dfd9840cb94cecafd8abbe55b66ed133191532a67944f 7732 
rust-libsodium-sys_0.2.7-1_source.buildinfo
Files:
 21dd11edcd657

Bug#1030915: marked as done (rust-sequoia-keyring-linter: FTBFS with new rust-rpassword.)

[Debian Bug Tracking System]

Your message dated Sat, 11 Feb 2023 07:05:25 +
with message-id 
and subject line Bug#1030915: fixed in rust-sequoia-keyring-linter 1.0.0-2
has caused the Debian Bug report #1030915,
regarding rust-sequoia-keyring-linter: FTBFS with new rust-rpassword.
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.)


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

Package: rust-sequoia-keyring-linter
Version: 1.0.0-1
Severity: serious

rust-rpassword was recently updated to version 6.x, but sequoia-keyring-linter
still depends on version 5.x. I have checked crates.io and upstream git, and
there does not appear to be an upstream patch available.

on bumping the dependency it fails to build with.


error[E0425]: cannot find function `read_password_from_tty` in crate `rpassword`
   --> src/keyring-linter.rs:57:38
|
57  | match rpassword::read_password_from_tty(
|  ^^ help: a 
function with a similar name exists: `read_password_from_bufread`


sequoia-sq fixed a similar issue by replacing read_password_from_tty
with prompt_password, as can be seen at
https://gitlab.com/sequoia-pgp/sequoia/-/commit/7936e3513ee339650a7ac2eff11edd2fac3f037d
but I am not in a position to determine if this is also appropriate
for sequoia-keyring-linter.
--- End Message ---
--- Begin Message ---
Source: rust-sequoia-keyring-linter
Source-Version: 1.0.0-2
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated 
rust-sequoia-keyring-linter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 11 Feb 2023 06:43:16 +
Source: rust-sequoia-keyring-linter
Architecture: source
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1030915
Changes:
 rust-sequoia-keyring-linter (1.0.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Package sequoia-keyring-linter 1.0.0 from crates.io using debcargo 2.6.0
   * Apply upstream patch for rpassword 6.0 (Closes: #1030915).
Checksums-Sha1:
 ad272971ef190acaad014244caf066aa16c851f1 2499 
rust-sequoia-keyring-linter_1.0.0-2.dsc
 a655b80b5cba84e0b66bc67297637745ff6eb1af 2772 
rust-sequoia-keyring-linter_1.0.0-2.debian.tar.xz
 a33a51e774c2e99951bc216ce76d083559561a34 15673 
rust-sequoia-keyring-linter_1.0.0-2_source.buildinfo
Checksums-Sha256:
 5963f134cba9357b5463b586ed7b32ad879d31690a1ae6f309c454644ff7ac47 2499 
rust-sequoia-keyring-linter_1.0.0-2.dsc
 29c256f42599071bcea9209fd6425fc0734a537b02a3a9c1f14b26a970a649a2 2772 
rust-sequoia-keyring-linter_1.0.0-2.debian.tar.xz
 671d3073d2971a53e9f0c34f2392d9908fb13b80fd813ad9c1d608c690e7ff01 15673 
rust-sequoia-keyring-linter_1.0.0-2_source.buildinfo
Files:
 347e65e26d7213d90ce3f3a851b55174 2499 utils optional 
rust-sequoia-keyring-linter_1.0.0-2.dsc
 9e0be37453072ca110c7ba0b7d216a53 2772 utils optional 
rust-sequoia-keyring-linter_1.0.0-2.debian.tar.xz
 e0440873dd8e8f1fa7f1267d93eaa7b1 15673 utils optional 
rust-sequoia-keyring-linter_1.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmPnObAUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xtpeg/9EDabueGBUvMyYz1gW6hNdE2ay0UQ
fMIlMQqBFT6FJbQrtX+TEB610SfG+roVhfB+c+EfY67H0E80kSKeict07PBicRt9
LzxJ5e7Lido8OHEDUpoazvnXfPg5SIAk5IuFg1hFnFFUzousSANVmf27s84ritld
v4XDCj9GR2EZdms+tyC+uhPwMW7AF9oTcxV9kxSiKZS9q51RitCa9dUXd51eg/yK
urOstltqhl374mehXqe4E7Y5xrafAKEJwLna4RzVf1IIOEYODcvlXB00ectOBFJ9
K8ilPwlE6VNaEfotb5Bsqg4rVmMlOOtAAA/kcTXfPZyzXlAXTw14oGgaMuFrhoWF
7rfwJVZUB+murI3pJ6wluLmHkRJsGBlrwIk6utjl+jX+BMrJGem2Qo69rTsCSIqn
+uq0w64AduyO1ex2Ez//Jc779mIK3nv8XDws3SzyutTlKCk3EUuAViCs/tI3OOv0
Euxu8bofGHuSYCPWcjtDUmbXSDcMz2SVzXBDhfPBM36QKwl76OkEhy+ms8dq17E9
G86MzgaNok26hkRyza33P/43nlVVdGKRCH0yK0ywVOGDSW4mr+QSuMG3SyMGQjSD
KUcsKhK27zOYOT0

Bug#1028375: Accepted xz-utils 5.4.1-0.1 (source) into unstable

[Helge Kreutzmann]

Hello Sebastian,
On Fri, Feb 10, 2023 at 09:25:08PM +, Thorsten Glaser wrote:
> Sebastian Andrzej Siewior dixit:
> 
> >How is this getting to work without manpages-fr contributing to it?
> 
> By adding a conflict (can’t remember if it has to be Conflicts or Breaks
> will also work) plus Replaces on manpages-fr (<< 4.17.0-2~bpo11+1) on
> xz-utils in bookworm. (And the others similarily.)

And please remember to make the same for manpages-de (sorry, if that
was obvious).

Thanks!

Greetings

Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1031017: marked as done (rust-webbrowser: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Sat, 11 Feb 2023 06:04:54 +
with message-id 
and subject line Bug#1031017: fixed in rust-webbrowser 0.8.7-1
has caused the Debian Bug report #1031017,
regarding rust-webbrowser: autopkgtest failure
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.)


-- 
1031017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-webbrowser
Version: 0.5.2-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-webbrowser/31209809/log.gz

...
unning 4 tests
test test_open_chrome ... ignored
test test_open_firefox ... ignored
test test_open_safari ... ignored
test test_open_default ... FAILED

failures:

 test_open_default stdout 
thread 'test_open_default' panicked at 'assertion failed: 
open(\"http://github.com\";).is_ok()', src/lib.rs:331:5
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
   2: core::panicking::panic
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:48:5
   3: webbrowser::test_open_default
 at ./src/lib.rs:331:5
   4: webbrowser::test_open_default::{{closure}}
 at ./src/lib.rs:330:1
   5: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
   6: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
test_open_default

test result: FAILED. 0 passed; 1 failed; 3 ignored; 0 measured; 0 filtered out; 
finished in 0.01s

error: test failed, to rerun pass `--lib`
autopkgtest [14:00:43]: test command2: ---]
autopkgtest [14:00:43]: test command2:  - - - - - - - - - - results - - - - - - 
- - - -
command2 FAIL non-zero exit status 101
autopkgtest [14:00:43]:  summary
command1 FAIL non-zero exit status 101
command2 FAIL non-zero exit status 101
--- End Message ---
--- Begin Message ---
Source: rust-webbrowser
Source-Version: 0.8.7-1
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-webbrowser 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 11 Feb 2023 05:34:11 +
Source: rust-webbrowser
Architecture: source
Version: 0.8.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1031017
Changes:
 rust-webbrowser (0.8.7-1) unstable; urgency=medium
 .
   * Package webbrowser 0.8.7 from crates.io using debcargo 2.6.0
   * Disable tests that depend on actix-web and actix-files
   * Add test_depends on firefox-esr
 .
   [ Blair Noctis ]
   * Package webbrowser 0.8.7 from crates.io using debcargo 2.6.0
 (Closes: #1031017)
   * Patch to remove dep on actix-web, actix-files, not yet in Debian
   * Patch to remove deps for other platforms
   * Remove d/rules and dep on xdg-util, problem addressed upstream
 .
   [ Nick Black ]
   * Team upload.
   * package.lib -> packages.lib
   * Package webbrowser 0.5.5 from crates.io using debcargo 2.4.2
Checksums-Sha1:
 1194c921fe0af86ff1c5c695ec5250da5e103ffe 2578 rust-webbrowser_0.8.7-1.dsc
 d96a709c7c04b5f118b60e1dda6bb5b2f523a0bb 37862 
rust-webbrowser_0.8.7.orig.tar.gz
 e548536d1c763428508df5019df9cce11598ad01 4916 
rust-webbrowser_0.8.7-1.debian.tar.xz
 453bb24ce0667f1e0d3f5d2d3be974386a461d65 8486 
rust-webbrowser_0.8.7-1_source.buildinfo
Checksums-Sha256:
 1f28180823725653d91d8bcc969f4765a489ea571a8869257e0a078942b176b4 2578 
rust-webbrowser_0.8.7-1.dsc
 97d1fa1e5c829b2bf9eb1e28fb950248b797cd6a04866fbdfa8bc31e5eef4c78 37862 
rust-webbrowser_0.8.7.orig.tar

Bug#1009261: Evolution bwrap problem - may fail to print or hang in startup

[Diane Trout]

On Sun, 01 May 2022 14:41:26 +0200 Domenico Cufalo 
wrote:
> Dear developers,
> 
> I have the same issue in my machine (Debian Bullseye Stable with
Gnome 
> 3.38): Evolution doesn't start at all.
> 

I also had this problem, but it went away on systems running testing or
bookworm.

Bug#1029814: ixp4xx-microcode: no longer useful, ixp4xx support dropped in 2014

[Hector Oron]

Hello,

  This firmware was used by slugs or NSLU-2,
  https://www.cyrius.com/debian/nslu2/install/

  Those devices were great to bootstrap and play with armel port.

  Due to low ram and flash it is no longer capable to run Debian. Therefore
I agree this package can be marked for removal.

  Userland package was removed time ago:
  https://tracker.debian.org/pkg/nslu2-utils

Regards

Bug#1030635: marked as done (rust-isahc: autopkgtest failure on s390x)

[Debian Bug Tracking System]

Your message dated Sat, 11 Feb 2023 00:34:54 +
with message-id 
and subject line Bug#1030635: fixed in rust-isahc 1.7.2+ds-20
has caused the Debian Bug report #1030635,
regarding rust-isahc: autopkgtest failure on s390x
to be marked as done.

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

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


-- 
1030635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-isahc
Version: 1.7.2+ds-18
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/s390x/r/rust-isahc/31083641/log.gz

...
running 2 tests
test request_errors_if_read_timeout_is_reached ... FAILED
test timeout_during_response_body_produces_error ... FAILED

failures:

 request_errors_if_read_timeout_is_reached stdout 
thread 'request_errors_if_read_timeout_is_reached' panicked at 'assertion 
failed: `result` matches `Err(e) if e == isahc :: error :: ErrorKind :: Timeout`
  value: `Ok(Response { status: 200, version: HTTP/1.1, headers: {}, body: 
Body(?) })`', tests/timeouts.rs:28:5
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
   2: timeouts::request_errors_if_read_timeout_is_reached
 at ./tests/timeouts.rs:28:5
   3: timeouts::request_errors_if_read_timeout_is_reached::{{closure}}
 at ./tests/timeouts.rs:14:1
   4: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
   5: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.

 timeout_during_response_body_produces_error stdout 
thread 'timeout_during_response_body_produces_error' panicked at 'called 
`Result::unwrap_err()` on an `Ok` value: 98304', tests/timeouts.rs:61:43
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
   2: core::result::unwrap_failed
 at /usr/src/rustc-1.63.0/library/core/src/result.rs:1805:5
   3: core::result::Result::unwrap_err
 at /usr/src/rustc-1.63.0/library/core/src/result.rs:1194:22
   4: timeouts::timeout_during_response_body_produces_error
 at ./tests/timeouts.rs:61:9
   5: timeouts::timeout_during_response_body_produces_error::{{closure}}
 at ./tests/timeouts.rs:35:1
   6: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
   7: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
request_errors_if_read_timeout_is_reached
timeout_during_response_body_produces_error

test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.54s

error: test failed, to rerun pass `--test timeouts`
 Running 
`/tmp/tmp.6iU3rvj85w/target/s390x-unknown-linux-gnu/debug/deps/unix-457994c20ca0a0bc
 --skip accept_headers_populated_by_default --skip 
header_can_be_inserted_in_httpclient_builder --skip 
headers_in_request_builder_must_override_headers_in_httpclient_builder --skip 
headers_in_request_builder_must_override_multiple_headers_in_httpclient_builder 
--skip multiple_headers_with_same_key_can_be_inserted_in_httpclient_builder 
--skip deflate_encoded_response_is_decoded_automatically --skip 
gzip_encoded_response_is_decoded_automatically`

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.00s

error: 3 targets failed:
`--test encoding`
`--test net`
`--test timeouts`
autopkgtest [12:03:05]: test rust-isahc-1:text-decoding: 
---]
autopkgtest [12:03:06]: test rust-isahc-1:text-decoding:  - - - - - - - - - - 
results - - - - - - - - - -
rust-isahc-1:text-decoding FAIL non-zero exit status 101
autopkgtest [12:03:06]:  summary
rust-isahc:@ FAIL non-zero exit status 101
rust-isahc-1:unstable-interceptors FAIL non-zero exit status 101
rust-isahc-1:FAIL non-zero exit status 101
rust-isahc-1:default FAIL non-zero exit status 101
rust-isahc-1:cookies FAIL non-zero exit status 101
rust-isahc-1:http2

Bug#1029326: marked as done (intel-mkl: autopkgtest regression in testing)

[Debian Bug Tracking System]

Your message dated Sat, 11 Feb 2023 00:34:37 +
with message-id 
and subject line Bug#1029326: fixed in intel-mkl 2020.4.304-4
has caused the Debian Bug report #1029326,
regarding intel-mkl: autopkgtest regression in testing
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.)


-- 
1029326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: intel-mkl
Version: 2020.4.304-3
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Sometime in February 2021, intel-mkl's autopkgtests regressed in
testing [1].  I've copied what I hope are relevant parts of the log
below.

Regards
Graham


[1] https://ci.debian.net/packages/i/intel-mkl/testing/amd64/


autopkgtest [21:17:41]: test command4: g++ debian/tests/test-gemm.cc
-I/usr/include/mkl -Wl,--no-as-needed -lmkl_rt -lpthread -lm -ldl -o
tester; MKL_THREADING_LAYER=tbb MKL_INTERFACE_LAYER=lp64 ./tester
autopkgtest [21:17:41]: test command4: [---
INTEL MKL ERROR: /lib/x86_64-linux-gnu/libmkl_tbb_thread.so: undefined
symbol: _ZN3tbb4task13note_affinityEt.
Intel MKL FATAL ERROR: Cannot load libmkl_tbb_thread.so.
autopkgtest [21:17:41]: test command4: ---]
autopkgtest [21:17:42]: test command4:  - - - - - - - - - - results -
- - - - - - - - -
command4 FAIL non-zero exit status 2


autopkgtest [21:22:33]: test command12: [---
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::task_group_context::cancel_group_execution()'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::interface5::internal::task_base::destroy(tbb::task&)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to `tbb::task::note_affinity(unsigned short)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::internal::allocate_via_handler_v3(unsigned long)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::interface7::internal::task_arena_base::internal_current_slot()'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::internal::concurrent_queue_base_v3::internal_push(void const*)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to `tbb::internal::NFS_Allocate(unsigned long,
unsigned long, void*)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to `tbb::internal::NFS_Free(void*)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::task_group_context::is_group_execution_cancelled() const'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::internal::allocate_root_proxy::allocate(unsigned long)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::internal::allocate_continuation_proxy::allocate(unsigned long)
const'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::internal::throw_exception_v4(tbb::internal::exception_id)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to `tbb::task_scheduler_init::terminate()'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::internal::concurrent_queue_base_v3::internal_pop_if_present(void*)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::internal::concurrent_queue_base_v3::concurrent_queue_base_v3(unsigned
long)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::internal::concurrent_queue_base_v3::internal_empty() const'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_thread.so:
undefined reference to
`tbb::task::spawn_and_wait_for_all(tbb::task_list&)'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmkl_tbb_th

Bug#1031015: marked as done (librust-ogg+async-dev is not installable)

[Debian Bug Tracking System]

Your message dated Sat, 11 Feb 2023 00:19:27 +
with message-id 
and subject line Bug#1031015: fixed in rust-ogg 0.9.0-1
has caused the Debian Bug report #1031015,
regarding librust-ogg+async-dev is not installable
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.)


-- 
1031015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-ogg+async-dev
Version: 0.7.0-1
Severity: serious
Tags: bookworm sid

The following packages have unmet dependencies:
 librust-ogg+async-dev : Depends: librust-bytes-0.4+default-dev
 Depends: librust-futures-0.1+default-dev
 Depends: librust-tokio-io-0.1+default-dev
--- End Message ---
--- Begin Message ---
Source: rust-ogg
Source-Version: 0.9.0-1
Done: Blair Noctis 

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

Debian distribution maintenance software
pp.
Blair Noctis  (supplier of updated rust-ogg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Feb 2023 23:46:12 +
Source: rust-ogg
Architecture: source
Version: 0.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Blair Noctis 
Closes: 1031015
Changes:
 rust-ogg (0.9.0-1) unstable; urgency=medium
 .
   * Team upload.
   * Package ogg 0.9.0 from crates.io using debcargo 2.6.0 (Closes: #1031015)
   * Relax dep on tokio-util to packaged higher 0.7
   * Collapse features
Checksums-Sha1:
 cbdb055f034911170c76ec2c65ecc969d127b851 2253 rust-ogg_0.9.0-1.dsc
 96000a5a1f3f8c276e7f8d72ebb7abaf6cf8b5d5 28444 rust-ogg_0.9.0.orig.tar.gz
 5367ef2beb6db3fe1ce7c6337516759a117ef794 3696 rust-ogg_0.9.0-1.debian.tar.xz
 14e3884b2e5a4133836984c52254a8dac8c5131c 7239 rust-ogg_0.9.0-1_source.buildinfo
Checksums-Sha256:
 fc7e92e555b0401cbc877df281b8b4d09cc7f1c67e151996c2a82eaa435ff833 2253 
rust-ogg_0.9.0-1.dsc
 960d0efc0531a452c442c777288f704b300a5f743c04a14eba71f9aabc4897ac 28444 
rust-ogg_0.9.0.orig.tar.gz
 612c9014374b917f67fb1fc720bdc91af15c3db1ad4af24140f008e12ce0bd7f 3696 
rust-ogg_0.9.0-1.debian.tar.xz
 d0f4a29d4ac4d5d040148f58150785150acef7c85853d501d58612a6bc5d64ea 7239 
rust-ogg_0.9.0-1_source.buildinfo
Files:
 fc48a09fbfe208a3c2cf40c1ee81c281 2253 rust optional rust-ogg_0.9.0-1.dsc
 3311d8c6247a4a049811020aef7003e7 28444 rust optional rust-ogg_0.9.0.orig.tar.gz
 6775f2c7ebe0e024f47e134815fedc8b 3696 rust optional 
rust-ogg_0.9.0-1.debian.tar.xz
 5ae4951a9f7a8f39cbf7eb44d6ca7f65 7239 rust optional 
rust-ogg_0.9.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmPm2wkUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsiUg//XlniKkPckPlQBNZWisNsPdy8sXxn
dmN8Lx+I8z5lvFkDNFVWTI6OADY/iu9aD8QB8I2iOi+cCpA4KrJUcs9sMIsqkKN/
4wuSIwchy8x86Z/2y8xrF2cdnR6MdKr4FfrEsR5i/GwZwRtBBGg6MzeFHPGUnEPL
rMqiWSaQPdWtLrd599YQnQUUcZOgbvHV49uv0ekY89cN6TcZ5o1wwVTUm5lAGFrL
ED8EzLYNk/3amHPgatbUKloiAD2T4mm2WeTBvAgpRUMEd4Mfa5oon512YoDtjHw2
C4HBxqid5VrPUOqze0h9Q+0cvO9CkY6k8191cHU1XKH1crv9vwPB96rLdWWelqgt
wwTtKvifBB/1R7Xd8RfNRHkmI+/KJELoJcS7j+ljdrtfoa1UKNYVaPwYQ5cZUnc1
5BJ+8aXQWhHV2XS6KAkgvvve48wZb1yr47Lo/xcvHdijF84emvvtKpqwSV/tmjXD
GrocFPo4fAWRH4Y+OqUB2yDoQvENPrR1rFluN4D97giBDl9Mve7AYLDaFGaVeZK2
JF9deACyrRPaJyrNKAy2qaZ6Ri3O/8kCsbNKhim2PTpJjfhTojXkC8AWrnVLIrfA
genBXR5Kub/0/EKJOhONemUCDR8hciH0gbIbZlQ5dseFfxOzmxEkoYJ7yawbnh/s
4KsgOk3aODaFRd8=
=J2z9
-END PGP SIGNATURE End Message ---

Bug#1031039: rust-aes-ctr build depends on librust-aes-soft-0.3+default-dev but it is not installable

[Blair Noctis]

On Fri, 10 Feb 2023 19:04:20 +0200 Adrian Bunk  wrote:
> Source: rust-aes-ctr
> Version: 0.3.0-2
> Severity: serious
> Tags: ftbfs
> 
> The following packages have unmet dependencies:
>  builddeps:rust-aes-ctr : Depends: librust-aes-soft-0.3+default-dev but it is 
> not installable
> 
> 

[aes-ctr] and aes-soft are both deprecated upstream, we are [planning] to update
to aes then RM them.

[aes-ctr]: https://crates.io/crates/aes-ctr
[aes-soft]: https://crates.io/crates/aes-soft
[planning]: https://lists.debian.org/debian-rust/2022/11/msg2.html

-- 
Sdrager,
Blair Noctis


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1031051: librust-rustls-dev depends on librust-ring-dev which is missing on mips, ppc*, s390x, riscv, sparc64, c32

[Jonas Smedegaard]

Quoting Blair Noctis (2023-02-10 22:55:44)
> Package: librust-rustls-dev
> Version: 0.20.8-4
> Severity: serious
> X-Debbugs-Cc: n...@sail.ng
> 
> Dear maintainer,
> 
> Your package librust-rustls-dev depends on librust-ring-dev that fails to 
> build
> on mips, ppc, s390x, riscv, sparc64, c32. That renders librust-tokio-utils-dev
> FTBFS on said archs, in turn librust-reqwest-0.11+rustls-tls-dev, in turn 
> tealdeer.

This sounds like a duplicate of bug#1030957.

Please clarify if you consider is independent, or if same issue then close it.

Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1031013: librust-rust-code-analysis-dev is not installable

[Peter Green]

The following packages have unmet dependencies:
 librust-rust-code-analysis-dev : Depends: librust-petgraph-0.5+default-dev
  Depends: librust-phf-0.8+default-dev
  Depends: librust-phf-0.8+macros-dev
  Depends: librust-phf-codegen-0.8+default-dev
  Depends: librust-tree-sitter-0.17+default-dev


There is a new upstream release that fixes these issues, but it also intoduces
new dependencies that are not in debian.

Bug#1030855: marked as done (ring_20230206.0~ds1-2_amd64-buildd.changes REJECTED)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 22:59:04 +
with message-id 
and subject line Bug#1030855: fixed in ring 20230206.0~ds1-3
has caused the Debian Bug report #1030855,
regarding ring_20230206.0~ds1-2_amd64-buildd.changes REJECTED
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.)


-- 
1030855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ring
Version: 20230206.0~ds1-2
Severity: serious

On 2023-02-08 08:40, Debian FTP Masters wrote:
> jami_20230206.0~ds1-2_amd64.deb: has 5 file(s) with a timestamp too far in th=
> e past:
>   usr/share/applications/jami.desktop (Thu Jan  1 00:00:01 1970)  usr/share/i=
> cons/hicolor/scalable/apps/jami.svg (Thu Jan  1 00:00:01 1970)  usr/share/jam=
> i/jami.desktop (Thu Jan  1 00:00:01 1970)  usr/share/metainfo/jami.appdata.xm=
> l (Thu Jan  1 00:00:01 1970)  usr/share/pixmaps/jami.xpm (Thu Jan  1 00:00:01=
>  1970)
> 
> 
> 
> =3D=3D=3D
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 
--- End Message ---
--- Begin Message ---
Source: ring
Source-Version: 20230206.0~ds1-3
Done: Amin Bandali 

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

Debian distribution maintenance software
pp.
Amin Bandali  (supplier of updated ring package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Feb 2023 16:52:37 -0500
Source: ring
Architecture: source
Version: 20230206.0~ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Amin Bandali 
Closes: 1030855
Changes:
 ring (20230206.0~ds1-3) unstable; urgency=medium
 .
   * debian/control: Add missing dependency on qt6-positioning-dev.
   * debian/rules: Add stopgap workaround to disable building with the
 Qt WebEngine on architectures it's missing from.  Also add a
 potential workaround for this dak error for the uploads:
 jami_20230206.0~ds1-2_amd64.deb: has 5 file(s) with a timestamp
 too far in the past: ... (Closes: #1030855)
 .
   * Upload sponsored by Petter Reinholdtsen.
Checksums-Sha1:
 1d795713569e6b9b88bbdb2acb26032c2bae68d5 3729 ring_20230206.0~ds1-3.dsc
 3e1dc8fcad0d4a3c11fe4f8d9cb767869b792fbf 21372 
ring_20230206.0~ds1-3.debian.tar.xz
 578392b1a71c987ba7baaa009370d804860e27d9 23062 
ring_20230206.0~ds1-3_source.buildinfo
Checksums-Sha256:
 c5bb3c64a24aed89b6f6e9bccf223702f075ec2bdf9f5ca402b3749033f0a7c7 3729 
ring_20230206.0~ds1-3.dsc
 b6bac85d56704f5538abfa2252b71dec2ef423e58a8e8f6e86dfadaa0c50160b 21372 
ring_20230206.0~ds1-3.debian.tar.xz
 2825d78ffa3e578f4f23679a976e374d8e973bc6130525e4a2112e175df1ecc7 23062 
ring_20230206.0~ds1-3_source.buildinfo
Files:
 2673f30ec4db940bd741b70ab22b2146 3729 comm optional ring_20230206.0~ds1-3.dsc
 1c1a7d0ac2ed8842e2e36d5728fd4514 21372 comm optional 
ring_20230206.0~ds1-3.debian.tar.xz
 30b551057f43e741a3260d8f1943a4d8 23062 comm optional 
ring_20230206.0~ds1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmPmwJ4ACgkQgSgKoIe6
+w6stA/9HB2FAJxX+488BkrvYbxs55QSYKESnxN9siPg3sxXR1flSqj1dFwaefiv
35OCIbqlIKb3AbRYtgICsPT/AtKyZZ7lDtymMOql0FXm9B8I3wb2xEHNwY85SWBM
U0WZPMGY+KF4BPe9vFq9QVFhCDIagvwYWtp8EZ60MudIUu1EIHOsw+Qbmk2eI6SK
AbZVuvBmh8FwS+rEAza7zxRj9ywb/5xuQTZwQi9WHuLBOugcjo4I/mfjTI0X60Kb
Ljgmz9W8lPLQMV7aKdR99Al9iDr1cIBkqwyL8QM7W9BTL6KBsvb0l/pTY9SZGF+b
j5C2DrJegyG1wRk+C8Agk+2ZYXV4yRck+6gHYAChk16pga4uIHrO9ejIx8AL/Mm3
JgCKUOCMCDeTwZtr2cdUATgKfd0kVYBhe/HB7meApNNMybxtEN7DPvrKwlwyoAid
B2qVHeHanc9feVUxOl9Z2Scef1Sr4IDPvCIRxslam6uvIG249vdslb/+XF9y/Q2/
32fnBT0TLTIQb/LdcZrD/REeVcG5PDpWFqvNPBb7UQ6gczWwERXq2OlSgcbiF541
rdA25L8EVoRXzsM8+f6BDX4JnEdoAecXKcmiP7Ir1smF5QjPJnCeYpPasrjHJTNB
3ob0NQhkndceoUm2NvSHNYJpkPenJiy/NXUz/uaXbFAH082bqV8=
=vMZQ
-END PGP SIGNATURE End Message ---

Bug#1030096: dask.distributed intermittent autopkgtest fail

[Diane Trout]

> 
> That presumably means 5 days, which we don't have, i.e. *don't*
> unless 
> release team tell you otherwise.


For what it's worth this is our answer from #debian-release

elbrus
detrout: I'll handle dask.distributed

detrout
elbrus, Thank you. sorry about needing to ask for an exception

elbrus
ack, thanks for working on the package; it wasn't pretty that we had to
remove it for the python3.11 transition

Bug#1031051: librust-rustls-dev depends on librust-ring-dev which is missing on mips, ppc*, s390x, riscv, sparc64, c32

[Blair Noctis]

Package: librust-rustls-dev
Version: 0.20.8-4
Severity: serious
X-Debbugs-Cc: n...@sail.ng

Dear maintainer,

Your package librust-rustls-dev depends on librust-ring-dev that fails to build
on mips, ppc, s390x, riscv, sparc64, c32. That renders librust-tokio-utils-dev
FTBFS on said archs, in turn librust-reqwest-0.11+rustls-tls-dev, in turn 
tealdeer.

-- 
Sdrager,
Blair Noctis


OpenPGP_signature
Description: OpenPGP digital signature

Processed: severity of 1022728 is important

[Debian Bug Tracking System]

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

> severity 1022728 important
Bug #1022728 [src:gnome-subtitles] src:gnome-subtitles: fails to migrate to 
testing for too long: FTBFS on 32 bit archs
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: severity of 1004103 is important

[Debian Bug Tracking System]

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

> severity 1004103 important
Bug #1004103 [src:calcurse] calcurse FTBFS on big endian
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1030602: marked as done (scapy: autopkgtest regression on 32 bit architectures and s390x)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 21:28:25 +
with message-id 
and subject line Bug#1030602: fixed in scapy 2.5.0+dfsg-2
has caused the Debian Bug report #1030602,
regarding scapy: autopkgtest regression on 32 bit architectures and s390x
to be marked as done.

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

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


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

Source: scapy
Version: 2.5.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of scapy the autopkgtest of scapy fails in testing 
when that autopkgtest is run with the binary packages of scapy from 
unstable. It passes when run with only packages from testing. In tabular 
form:


   passfail
scapy  from testing2.5.0+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=scapy

https://ci.debian.net/data/autopkgtest/testing/armel/s/scapy/31071000/log.gz

###(046)=[failed] Fragment exception

>>> ex = False
>>> try:
... fragments = ISOTP(b"a" * (1 << 32)).fragment()
... except Scapy_Exception:
... ex = True
... Traceback (most recent call last):
  File "", line 3, in 
OverflowError: cannot fit 'int' into an index-sized integer


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: scapy
Source-Version: 2.5.0+dfsg-2
Done: Carlos Henrique Lima Melara 

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

Debian distribution maintenance software
pp.
Carlos Henrique Lima Melara  (supplier of updated 
scapy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 09 Feb 2023 19:34:45 -0300
Source: scapy
Architecture: source
Version: 2.5.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Carlos Henrique Lima Melara 
Closes: 1030602
Changes:
 scapy (2.5.0+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Upload to unstable.
   * debian/patches/fix-endianness-in-utf-16-encoding.patch: remove patch.
   * debian/tests/control: disable tests in 32 bits and big endian archs
 (closes: #1030602).
Checksums-Sha1:
 a0e6e52ec1278e9519bbd05cf3ccd310179af570 2130 scapy_2.5.0+dfsg-2.dsc
 0342f764c87951e81651d3a2f49a344b82a5de69 12008 scapy_2.5.0+dfsg-2.debian.tar.xz
 cfd0461966e13c8aa97fbda137d150e865ecad79 7043 
scapy_2.5.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 52d560cbe928168e95a2955cb19f94645d7e2b2431a6c5232c67dc04094229ca 2130 
scapy_2.5.0+dfsg-2.dsc
 f00732eb0e8e190f9f31262dda547db5104905aec808dfbfdafd02b46a1e325a 12008 
scapy_2.5.0+dfsg-2.debian.tar.xz
 5edaf3853f1b259eff07ac0737461da9a50fbe90a3b438c36363bf97e8616bc2 7043 
scapy_2.5.0+dfsg-2_amd64.buildinfo
Files:
 f1831b6152bd40680b056c500ea1a0d4 2130 python optional scapy_2.5.0+dfsg-2.dsc
 201474cb212c6b58f995c76564b6f6a8 12008 python optional 
scapy_2.5.0+dfsg-2.debian.tar.xz
 5dd6c13223022cd9adafaf5309117388 7043 python optional 
scapy_2.5.0+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAmPmr78ACgkQu6n6rcz7
RwdApA//RFEJl6OVfBbyz0kAPbZbmyNUO/YNOQxNDt09NBqWP1YJaxdN7BpTcchT
FquxDlwqY7Pp0KId7Tpo2bOupuk3vrvVR0Sn2DBcN6X5W+3HEawAPAzLPrPUAph8
Q71zgJWpLpBbOXE/28tp3PcMHwWaxEq/y9/wsVfS5AKuld+sME7AgGQbkzwzKFNU
623oqxnEBplD+DBr7IVUJ73Ew2s0dtNFw2dUYh2rfJOn58YxkJVSqf6ggLFKF1Ys
vOJRNN04qwSeDoKVqLd0pTjXuvL+wc+XPSkGjzhO9fjPYXAyLNNoG/Q6/DTEMRBo
JLk7toSSIMpZ/Imvkeohl3/JA2XiNduISM0Of3BLzk37V1Ee2wUsZx8CFjKo7rv4
GJ7yN0z4dEcDS+fsfqbQzhjETRx8XRET/uYfT+uUTPfNB7WZC1aXIglsnJ5rxwm1
Lt/70i+mXWgjjmT7VetA3Uc95PkiWNyU6i203Je

Bug#1028375: Accepted xz-utils 5.4.1-0.1 (source) into unstable

[Thorsten Glaser]

Sebastian Andrzej Siewior dixit:

>How is this getting to work without manpages-fr contributing to it?

By adding a conflict (can’t remember if it has to be Conflicts or Breaks
will also work) plus Replaces on manpages-fr (<< 4.17.0-2~bpo11+1) on
xz-utils in bookworm. (And the others similarily.)

Which is, kinda, what I wrote before.

And no, you cannot rely on people upgrading within bpo first,
especially as bpo repository signatures expire YEARS before
the lifetime of the base release.

bye,
//mirabilos
-- 
 you introduced a merge commit│ % g rebase -i HEAD^^
 sorry, no idea and rebasing just fscked │ Segmentation
 should have cloned into a clean repo  │  fault (core dumped)
 if I rebase that now, it's really ugh │ wuahh

Bug#1030921: marked as done (satpy/spyder-kernels: unsatisfied build dependency in testing: python3-distributed)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 22:23:56 +0100
with message-id 
and subject line Re: satpy/spyder-kernels: unsatisfied build dependency in 
testing: python3-distributed
has caused the Debian Bug report #1030921,
regarding satpy/spyder-kernels: unsatisfied build dependency in testing: 
python3-distributed
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.)


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

Source: satpy
Version: 0.39.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Control: clone -1 -2
Control: reassign -2 src:spyder-kernels 2.4.2-1

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way. dask.distributed was removed from testing because of
bug 1030096.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---

Hi,

On 10-02-2023 08:58, Sebastiaan Couwenberg wrote:
With the soft freeze in two days it will likely need help from the 
release managers to migrate.


If no other issues pop up, it will migrate to testing before the freeze. 
I added a age hint.


Paul


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Bug#1030922: marked as done (satpy/spyder-kernels: unsatisfied build dependency in testing: python3-distributed)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 22:23:56 +0100
with message-id 
and subject line Re: satpy/spyder-kernels: unsatisfied build dependency in 
testing: python3-distributed
has caused the Debian Bug report #1030922,
regarding satpy/spyder-kernels: unsatisfied build dependency in testing: 
python3-distributed
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.)


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

Source: satpy
Version: 0.39.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Control: clone -1 -2
Control: reassign -2 src:spyder-kernels 2.4.2-1

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way. dask.distributed was removed from testing because of
bug 1030096.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---

Hi,

On 10-02-2023 08:58, Sebastiaan Couwenberg wrote:
With the soft freeze in two days it will likely need help from the 
release managers to migrate.


If no other issues pop up, it will migrate to testing before the freeze. 
I added a age hint.


Paul


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Bug#1030431: marked as done (sphinxcontrib-autoprogram: FTBFS: AttributeError: 'NoneType' object has no attribute 'reporter')

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 21:05:21 +
with message-id 
and subject line Bug#1030431: fixed in sphinxcontrib-autoprogram 0.1.7-4
has caused the Debian Bug report #1030431,
regarding sphinxcontrib-autoprogram: FTBFS: AttributeError: 'NoneType' object 
has no attribute 'reporter'
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.)


-- 
1030431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxcontrib-autoprogram
Version: 0.1.7-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with=python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:285: 
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated, 
> consider using implicit namespaces instead (PEP 420).
>   warnings.warn(msg, SetuptoolsDeprecationWarning)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:285: 
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated, 
> consider using implicit namespaces instead (PEP 420).
>   warnings.warn(msg, SetuptoolsDeprecationWarning)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/sphinxcontrib
> copying sphinxcontrib/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/sphinxcontrib
> copying sphinxcontrib/autoprogram.py -> 
> /<>/.pybuild/cpython3_3.11/build/sphinxcontrib
> running egg_info
> creating sphinxcontrib_autoprogram.egg-info
> writing sphinxcontrib_autoprogram.egg-info/PKG-INFO
> writing dependency_links to 
> sphinxcontrib_autoprogram.egg-info/dependency_links.txt
> writing namespace_packages to 
> sphinxcontrib_autoprogram.egg-info/namespace_packages.txt
> writing requirements to sphinxcontrib_autoprogram.egg-info/requires.txt
> writing top-level names to sphinxcontrib_autoprogram.egg-info/top_level.txt
> writing manifest file 'sphinxcontrib_autoprogram.egg-info/SOURCES.txt'
> reading manifest file 'sphinxcontrib_autoprogram.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'README'
> warning: no files found matching 'CHANGES.*'
> warning: manifest_maker: MANIFEST.in, line 4: unknown action 'tox.ini'
> 
> adding license file 'LICENSE'
> writing manifest file 'sphinxcontrib_autoprogram.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py test 
> /usr/lib/python3/dist-packages/setuptools/dist.py:285: 
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated, 
> consider using implicit namespaces instead (PEP 420).
>   warnings.warn(msg, SetuptoolsDeprecationWarning)
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> writing sphinxcontrib_autoprogram.egg-info/PKG-INFO
> writing dependency_links to 
> sphinxcontrib_autoprogram.egg-info/dependency_links.txt
> writing namespace_packages to 
> sphinxcontrib_autoprogram.egg-info/namespace_packages.txt
> writing requirements to sphinxcontrib_autoprogram.egg-info/requires.txt
> writing top-level names to sphinxcontrib_autoprogram.egg-info/top_level.txt
> reading manifest file 'sphinxcontrib_autoprogram.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'README'
> warning: no files found matching 'CHANGES.*'
> warning: manifest_maker: MANIFEST.in, line 4: unknown action 'tox.ini'
> 
> adding license file 'LICENSE'
> writing manifest file 'sphinxcontrib_autoprogram.egg-info/SOURCES.txt'
> running build_ext
> test_argument_groups 
> (sphinxcontrib.autoprogram.ScannerTestCase.test_argument_groups) ... ok
> test_choices (sphinxcontrib.autoprogram.ScannerTestCase.test_choices) ... ok
> test_parse_epilog 
> (sphinxcontrib.autoprogram.ScannerTestCase.test_parse_epilog) ... ok
> test_simple_parser 
> (sphinxcontrib.autoprogram.ScannerTestCase.test_simple_parser) ... ok
> test_subcommands (sphinxco

Bug#981903: marked as done (puppetdb: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 15:45:11 -0500
with message-id <6fa957ad-aa0b-f215-5fb7-1995b2aa8...@riseup.net>
and subject line Re: puppetdb: autopkgtest failure
has caused the Debian Bug report #981903,
regarding puppetdb: autopkgtest failure
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.)


-- 
981903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: puppetdb
Version: 6.2.0-5
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/puppetdb/10223214/log.gz

...
autopkgtest [03:52:37]: test puppet: [---
Adding user `puppetdb' to group `puppet' ...
Adding user puppetdb to group puppet
Done.
Waiting for PuppetDB to start
Timed out
cp: cannot stat '/var/log/puppetdb/puppetdb.log': No such file or directory
autopkgtest [03:54:46]: test puppet: ---]
autopkgtest [03:54:46]: test puppet:  - - - - - - - - - - results - - - - - - - 
- - -
puppet   FAIL non-zero exit status 1
autopkgtest [03:54:47]: test puppet:  - - - - - - - - - - stderr - - - - - - - 
- - -
cp: cannot stat '/var/log/puppetdb/puppetdb.log': No such file or directory
autopkgtest [03:54:47]:  summary
standalone   FAIL non-zero exit status 1
puppet   FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---

Version: 7.12.1-3

With the recent updates in this package, including improved 
autopkgtests, I believe this bug can be closed, as debci is now green.


Thanks,

-- Jérôme--- End Message ---

Bug#1028375: Accepted xz-utils 5.4.1-0.1 (source) into unstable

[Sebastian Andrzej Siewior]

On 2023-02-10 20:22:54 [+], Thorsten Glaser wrote:
> Sebastian Andrzej Siewior dixit:
> 
> >Good. So unless Thorsten disagrees this is done ;)
> 
> Please also test the upgrade with 4.16.0-1~bpo11+1 installed
> on bullseye instead of 4.17.0-2~bpo11+1 (since that is a valid
> upgrade path), without going via 4.17.0-2~bpo11+1.

I would expect that people upgrade to 4.17.0-2~bpo11+1 before going to
the next stable. This whole procedure follows then case #9 from
https://wiki.debian.org/PackageTransition

where manpages-fr is A and xz-utils is B.
How is this getting to work without manpages-fr contributing to it?

> bye,
> //mirabilos

Sebastian

Bug#1028375: Accepted xz-utils 5.4.1-0.1 (source) into unstable

[Thorsten Glaser]

Sebastian Andrzej Siewior dixit:

>Good. So unless Thorsten disagrees this is done ;)

Please also test the upgrade with 4.16.0-1~bpo11+1 installed
on bullseye instead of 4.17.0-2~bpo11+1 (since that is a valid
upgrade path), without going via 4.17.0-2~bpo11+1.

bye,
//mirabilos
-- 
15:41⎜ Somebody write a testsuite for helloworld :-)

Bug#997217: emms: FTBFS: ld: cannot find -lz

[Adrian Bunk]

Control: reassign -1 libtag1-dev 1.13-1
Control: retitle -1 libtag1-dev: Missing dependency on zlib1g-dev
Control: affects -1 src:emms

On Sat, Oct 23, 2021 at 09:11:37PM +0200, Lucas Nussbaum wrote:
>...
> > g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> > -Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o 
> > src/emms-print-metadata src/emms-print-metadata.cpp `taglib-config --cflags 
> > --libs`
> > /usr/bin/ld: cannot find -lz
> > collect2: error: ld returned 1 exit status
>...

This is a missing dependency in libtag1-dev:

$ taglib-config --cflags --libs
-I/usr/include -I/usr/include/taglib -L/usr/lib/x86_64-linux-gnu -ltag -lz
$ pkg-config --cflags --libs taglib
-I/usr/include/taglib -ltag -lz 
$ 

cu
Adrian

Processed: Re: Bug#997217: emms: FTBFS: ld: cannot find -lz

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libtag1-dev 1.13-1
Bug #997217 [src:emms] emms: FTBFS: ld: cannot find -lz
Bug reassigned from package 'src:emms' to 'libtag1-dev'.
No longer marked as found in versions emms/5.1-1.
Ignoring request to alter fixed versions of bug #997217 to the same values 
previously set
Bug #997217 [libtag1-dev] emms: FTBFS: ld: cannot find -lz
Marked as found in versions taglib/1.13-1.
> retitle -1 libtag1-dev: Missing dependency on zlib1g-dev
Bug #997217 [libtag1-dev] emms: FTBFS: ld: cannot find -lz
Changed Bug title to 'libtag1-dev: Missing dependency on zlib1g-dev' from 
'emms: FTBFS: ld: cannot find -lz'.
> affects -1 src:emms
Bug #997217 [libtag1-dev] libtag1-dev: Missing dependency on zlib1g-dev
Added indication that 997217 affects src:emms

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

Bug#1028375: Accepted xz-utils 5.4.1-0.1 (source) into unstable

[Sebastian Andrzej Siewior]

On 2023-02-10 20:43:01 [+0100], Helge Kreutzmann wrote:
> Hello Sebastian,
Hi Helge,

> From the manpages-l10n side everything is in place, I would then also
> properly close #1028233. (Uploads to bpo do not manipulate the BTS).

Good. So unless Thorsten disagrees this is done ;)

> Greetings
> 
>  Helge

Sebastian

Processed: forcibly merging 1012277 1013609

[Debian Bug Tracking System]

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

> forcemerge 1012277 1013609
Bug #1012277 [src:hipspy] hipspy fails with astropy 5.1
Bug #1013609 [src:hipspy] hipspy: FTBFS: E   ModuleNotFoundError: No module 
named 'astropy.tests.plugins'
Added tag(s) upstream.
Merged 1012277 1013609
> thanks
Stopping processing here.

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

Processed: Re: Bug#1030827: FTBFS on armhf

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1030827 [src:pspp] FTBFS on armhf
Severity set to 'serious' from 'important'

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

Processed: Bug#1030431 marked as pending in sphinxcontrib-autoprogram

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1030431 [src:sphinxcontrib-autoprogram] sphinxcontrib-autoprogram: FTBFS: 
AttributeError: 'NoneType' object has no attribute 'reporter'
Added tag(s) pending.

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

Bug#1030431: marked as pending in sphinxcontrib-autoprogram

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

Bug #1030431 in sphinxcontrib-autoprogram reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/sphinxcontrib-autoprogram/-/commit/43dc5ca4cacd9508220f320cdbf1f3aa06004f61


Mock state_machine in AutoprogramDirectiveTestCase

Closes: #1030431


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030431

Bug#1031046: Only include in Bookworm with commitment to stable updates

[Moritz Muehlenhoff]

Source: asterisk
Version: 1:20.1.0~dfsg+~cs6.12.40431414-1
Severity: serious

Asterisk should only be included in Bookworm with a reliable commitment
by the maintainers to backport/test security fixes across the typical
three year life cycle (two years of stable-security and one year of
oldstable-security). (There have been 37 CVEs in 2021/2022)

Cheers,
Moritz

Bug#1030635: closed by Debian FTP Masters (reply to Jonas Smedegaard ) (Bug#1030635: fixed in rust-isahc 1.7.2+ds-19)

[Adrian Bunk]

Control: reopen -1

On Wed, Feb 08, 2023 at 06:21:03PM +, Debian Bug Tracking System wrote:
>...
>  rust-isahc (1.7.2+ds-19) unstable; urgency=medium
>...
>* add patch 2005 to skip failing tests on s390x;
>...

Unfortunately this didn't fix the autopkgtest:

https://ci.debian.net/data/autopkgtest/testing/s390x/r/rust-isahc/31177323/log.gz

...
autopkgtest [12:46:36]:  summary
rust-isahc:@ FAIL non-zero exit status 101
rust-isahc-1:unstable-interceptors FAIL non-zero exit status 101
rust-isahc-1:FAIL non-zero exit status 101
rust-isahc-1:default FAIL non-zero exit status 101
rust-isahc-1:cookies FAIL non-zero exit status 101
rust-isahc-1:http2   FAIL non-zero exit status 101
rust-isahc-1:jsonFAIL non-zero exit status 101
rust-isahc-1:psl FAIL non-zero exit status 101
rust-isahc-1:spnego  FAIL non-zero exit status 101
rust-isahc-1:static-curl FAIL non-zero exit status 101
rust-isahc-1:static-ssl FAIL non-zero exit status 101
rust-isahc-1:text-decoding FAIL non-zero exit status 101


cu
Adrian

Processed: Re: Bug#1030635 closed by Debian FTP Masters (reply to Jonas Smedegaard ) (Bug#1030635: fixed in rust-isahc 1.7.2+ds-19)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1030635 {Done: Jonas Smedegaard } [src:rust-isahc] 
rust-isahc: autopkgtest failure on s390x
'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 rust-isahc/1.7.2+ds-19.

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

Bug#1028375: Accepted xz-utils 5.4.1-0.1 (source) into unstable

[Helge Kreutzmann]

Hello Sebastian,
On Fri, Feb 10, 2023 at 08:06:38PM +0100, Sebastian Andrzej Siewior wrote:
> On 2023-02-01 17:59:57 [+], Thorsten Glaser wrote:
> > > xz-utils (5.4.1-0.1) unstable; urgency=medium
> > > .
> > >   * Non-maintainer upload.
> > >   * Update pt_BR translations.
> > >   * Add lintian overrides and an override for blhc.
> > 
> > This is missing the updated Breaks+Replaces for manpages-l10n though.
> 
> That is correct, I wanted to wait until the bpo packages gets accepted
> as discussed with Helge.
> Now with the bpo package accepted I did a test from bullseye -> sid and
> from the log:
> 
> | $ grep -E 'manpages-fr|xz-utils' screenlog.0
> | dpkg -l manpages-fr xz-utils
> | ii  manpages-fr4.17.0-2~bpo11+1  all  French man pages
> | ii  xz-utils   5.2.5-2.1~deb11u1 amd64XZ-format compression 
> utilities
> |   logrotate logsave lsb-base lsb-release lsof mailcap man-db manpages 
> manpages-fr manpages-fr-dev mawk media-types mount nano ncurses-base 
> ncurses-bin ncurses-term netbase
> |   util-linux-locales vim-common vim-tiny wamerican wget whiptail xauth 
> xdg-user-dirs xkb-data xxd xz-utils zlib1g
> | Get:277 http://httpredir.debian.org/debian sid/main amd64 manpages-fr all 
> 4.17.0-2 [1,926 kB]
> | Get:278 http://httpredir.debian.org/debian sid/main amd64 xz-utils amd64 
> 5.4.1-0.1 [468 kB]
> | Get:279 http://httpredir.debian.org/debian sid/main amd64 manpages-fr-dev 
> all 4.17.0-2 [2,489 kB]
> | dpkg: considering removing manpages-fr in favour of xz-utils ...
> | dpkg: yes, will remove manpages-fr in favour of xz-utils
> | Preparing to unpack .../066-xz-utils_5.4.1-0.1_amd64.deb ...
> | Unpacking xz-utils (5.4.1-0.1) over (5.2.5-2.1~deb11u1) ...
> | Removing manpages-fr (4.17.0-2~bpo11+1), to allow configuration of xz-utils 
> (5.4.1-0.1) ...
> | Selecting previously unselected package manpages-fr.
> | Preparing to unpack .../067-manpages-fr_4.17.0-2_all.deb ...
> | Unpacking manpages-fr (4.17.0-2) ...
> | Preparing to unpack .../068-manpages-fr-dev_4.17.0-2_all.deb ...
> | Unpacking manpages-fr-dev (4.17.0-2) over (4.17.0-2~bpo11+1) ...
> | Setting up manpages-fr-dev (4.17.0-2) ...
> | Setting up xz-utils (5.4.1-0.1) ...
> | Setting up manpages-fr (4.17.0-2) ...
> 
> So it works as intended. Therefore I would close this bug report.
> Any disagreement?

From the manpages-l10n side everything is in place, I would then also
properly close #1028233. (Uploads to bpo do not manipulate the BTS).

Greetings

 Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1028375: Accepted xz-utils 5.4.1-0.1 (source) into unstable

[Sebastian Andrzej Siewior]

On 2023-02-01 17:59:57 [+], Thorsten Glaser wrote:
> > xz-utils (5.4.1-0.1) unstable; urgency=medium
> > .
> >   * Non-maintainer upload.
> >   * Update pt_BR translations.
> >   * Add lintian overrides and an override for blhc.
> 
> This is missing the updated Breaks+Replaces for manpages-l10n though.

That is correct, I wanted to wait until the bpo packages gets accepted
as discussed with Helge.
Now with the bpo package accepted I did a test from bullseye -> sid and
from the log:

| $ grep -E 'manpages-fr|xz-utils' screenlog.0
| dpkg -l manpages-fr xz-utils
| ii  manpages-fr4.17.0-2~bpo11+1  all  French man pages
| ii  xz-utils   5.2.5-2.1~deb11u1 amd64XZ-format compression 
utilities
|   logrotate logsave lsb-base lsb-release lsof mailcap man-db manpages 
manpages-fr manpages-fr-dev mawk media-types mount nano ncurses-base 
ncurses-bin ncurses-term netbase
|   util-linux-locales vim-common vim-tiny wamerican wget whiptail xauth 
xdg-user-dirs xkb-data xxd xz-utils zlib1g
| Get:277 http://httpredir.debian.org/debian sid/main amd64 manpages-fr all 
4.17.0-2 [1,926 kB]
| Get:278 http://httpredir.debian.org/debian sid/main amd64 xz-utils amd64 
5.4.1-0.1 [468 kB]
| Get:279 http://httpredir.debian.org/debian sid/main amd64 manpages-fr-dev all 
4.17.0-2 [2,489 kB]
| dpkg: considering removing manpages-fr in favour of xz-utils ...
| dpkg: yes, will remove manpages-fr in favour of xz-utils
| Preparing to unpack .../066-xz-utils_5.4.1-0.1_amd64.deb ...
| Unpacking xz-utils (5.4.1-0.1) over (5.2.5-2.1~deb11u1) ...
| Removing manpages-fr (4.17.0-2~bpo11+1), to allow configuration of xz-utils 
(5.4.1-0.1) ...
| Selecting previously unselected package manpages-fr.
| Preparing to unpack .../067-manpages-fr_4.17.0-2_all.deb ...
| Unpacking manpages-fr (4.17.0-2) ...
| Preparing to unpack .../068-manpages-fr-dev_4.17.0-2_all.deb ...
| Unpacking manpages-fr-dev (4.17.0-2) over (4.17.0-2~bpo11+1) ...
| Setting up manpages-fr-dev (4.17.0-2) ...
| Setting up xz-utils (5.4.1-0.1) ...
| Setting up manpages-fr (4.17.0-2) ...

So it works as intended. Therefore I would close this bug report.
Any disagreement?

> bye,
> //mirabilos

Sebastian

Processed: Let libapache2-mod-jk migrate to testing

[Debian Bug Tracking System]

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

> severity 1016131 important
Bug #1016131 [libapache2-mod-jk] libapache2-mod-jk: Apache does not start after 
upgrade (JkWorkersFile only allowed once)
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Processed: ghdl: diff for NMU version 2.0.0+dfsg-6.1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1010539 [src:ghdl] ghdl: FTBFS on armhf
Severity set to 'important' from 'serious'

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

Bug#1010539: ghdl: diff for NMU version 2.0.0+dfsg-6.1

[Adrian Bunk]

Control: severity -1 important

Dear maintainer,

I've uploaded an NMU for ghdl (versioned as 2.0.0+dfsg-6.1).
The diff is attached to this message.

cu
Adrian
diff -Nru ghdl-2.0.0+dfsg/debian/changelog ghdl-2.0.0+dfsg/debian/changelog
--- ghdl-2.0.0+dfsg/debian/changelog	2023-01-20 04:29:12.0 +0200
+++ ghdl-2.0.0+dfsg/debian/changelog	2023-02-10 18:49:58.0 +0200
@@ -1,3 +1,11 @@
+ghdl (2.0.0+dfsg-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Adjust the autopkgtest for the ghwdump move.
+  * Drop the gcc backend on armhf for now. (see #1010539)  
+
+ -- Adrian Bunk   Fri, 10 Feb 2023 18:49:58 +0200
+
 ghdl (2.0.0+dfsg-6) unstable; urgency=medium
 
   * Upload to unstable
diff -Nru ghdl-2.0.0+dfsg/debian/control ghdl-2.0.0+dfsg/debian/control
--- ghdl-2.0.0+dfsg/debian/control	2023-01-11 03:56:31.0 +0200
+++ ghdl-2.0.0+dfsg/debian/control	2023-02-10 18:49:58.0 +0200
@@ -26,7 +26,7 @@
 Architecture: any
 Depends: ghdl-common (= ${binary:Version}),
  ghdl-mcode [any-i386 any-amd64] 
- | ghdl-gcc 
+ | ghdl-gcc [!armhf] 
  | ghdl-llvm ,
  ${misc:Depends}
 Suggests: gtkwave
@@ -79,7 +79,7 @@
  This package contains the compiler with the mcode backend.
 
 Package: ghdl-gcc
-Architecture: any
+Architecture: alpha amd64 arc arm64 armel hppa hurd-i386 i386 ia64 kfreebsd-i386 kfreebsd-amd64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32
 Build-Profiles: 
 Built-Using: ${Built-Using-GCC}
 Depends: ghdl-common (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
diff -Nru ghdl-2.0.0+dfsg/debian/rules ghdl-2.0.0+dfsg/debian/rules
--- ghdl-2.0.0+dfsg/debian/rules	2023-01-20 04:10:35.0 +0200
+++ ghdl-2.0.0+dfsg/debian/rules	2023-02-10 18:49:58.0 +0200
@@ -38,6 +38,11 @@
 BACKENDS := $(filter-out mcode,$(BACKENDS))
 endif
 
+# https://bugs.debian.org/1010539 
+ifneq ($(filter armhf,$(DEB_HOST_ARCH)),)
+BACKENDS := $(filter-out gcc,$(BACKENDS))
+endif
+
 BUILDDIR := $(CURDIR)/builddir
 TESTRUNDIR := $(CURDIR)/testrundir
 STAMPSDIR := $(BUILDDIR)/stamps
diff -Nru ghdl-2.0.0+dfsg/debian/tests/control ghdl-2.0.0+dfsg/debian/tests/control
--- ghdl-2.0.0+dfsg/debian/tests/control	2023-01-04 02:36:14.0 +0200
+++ ghdl-2.0.0+dfsg/debian/tests/control	2023-02-10 18:49:58.0 +0200
@@ -1,11 +1,11 @@
 Test-Command: debian/tests/ghdl-tests autopkgtest gcc
-Depends: ghdl-gcc
+Depends: ghdl-gcc, ghdl-tools
 Restrictions: skip-not-installable
 
 Test-Command: debian/tests/ghdl-tests autopkgtest llvm
-Depends: ghdl-llvm
+Depends: ghdl-llvm, ghdl-tools
 Restrictions: skip-not-installable
 
 Test-Command: debian/tests/ghdl-tests autopkgtest mcode
-Depends: ghdl-mcode, gcc, libc6-dev
+Depends: ghdl-mcode, gcc, libc6-dev, ghdl-tools
 Restrictions: skip-not-installable
diff -Nru ghdl-2.0.0+dfsg/debian/tests/ghdl-tests ghdl-2.0.0+dfsg/debian/tests/ghdl-tests
--- ghdl-2.0.0+dfsg/debian/tests/ghdl-tests	2023-01-10 05:26:00.0 +0200
+++ ghdl-2.0.0+dfsg/debian/tests/ghdl-tests	2023-02-10 18:49:58.0 +0200
@@ -22,19 +22,9 @@
 	RUNDIR=testrundir/$BACKEND
 	mkdir -p "$RUNDIR"
 	GHDL="$PWD/$RUNDIR/usr/bin/ghdl-$BACKEND"
-	GHWDUMP=
 elif [ "$1" = autopkgtest ]; then
 	RUNDIR="$AUTOPKGTEST_TMP"
 	GHDL=/usr/bin/ghdl-$BACKEND
-
-	# Check for temporary location of up to date ghwdump for autopkgtests
-	# where it can be found until /usr/bin/ghwdump can be replaced in
-	# coordination with the gtkwave package
-	if [ -x /usr/lib/ghdl/ghwdump ]; then
-		GHWDUMP=/usr/lib/ghdl/ghwdump
-	else
-		GHWDUMP=
-	fi
 else
 	echo >&2 "Invalid test environment specification"
 	exit 1
@@ -52,5 +42,5 @@
 mkdir -p "$RUNDIR/src"
 cp -r src/grt "$RUNDIR/src"
 
-export GHDL GHWDUMP
+export GHDL
 (cd "$RUNDIR/testsuite"; ./testsuite.sh $TESTS -- --keep-going)

Processed: severity of 1018724 is important

[Debian Bug Tracking System]

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

> severity 1018724 important
Bug #1018724 [src:rust-jemalloc-sys] rust-jemalloc-sys FTBFS on riscv64(gc)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1030096: dask.distributed intermittent autopkgtest fail

[Diane Trout]

> 
> That might be true on amd64, but I don't think it's true of
> arm*/s390x: 
> the tests that are failing there do *not* appear to be isinstalled
> tests.
> 
> I suspect the tests wouldn't have worked on those architectures in 
> 2022.02 either, and we didn't notice because the previously mentioned
> bug was causing the autopkgtest to not actually run the tests. 
> (dask.distributed is arch:all, so it's only built once, presumably on
> amd64.)

Ok yes there could also be issues with their serialization code on
unusual architectures.

>  > When under less time pressure I think a good plan might be two
> split
>  > the tests internally marked as isinstalled or flaky into a
> separate
>  > autopkgtest run that's marked flaky and let the CI gate on the
> more
>  > reliable tests.
> 
> As stated above, that's probably the wrong split for this.

It might not be enough to solve all dask.distributed's test problems,
(as you point out for the other architectures) but it does seem like
their test suites include both unit tests that don't depend on the host
networking, and integration tests that are strongly impacted by the
configuration of test runner.

And there might be value in separating the unit & integration test
types?

Bug#1031039: rust-aes-ctr build depends on librust-aes-soft-0.3+default-dev but it is not installable

[Adrian Bunk]

Source: rust-aes-ctr
Version: 0.3.0-2
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:rust-aes-ctr : Depends: librust-aes-soft-0.3+default-dev but it is 
not installable

Bug#1031038: rust-libsodium-sys: autopkgtest failure

[Adrian Bunk]

Source: rust-libsodium-sys
Version: 0.2.5-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-libsodium-sys/31212775/log.gz

...
  process didn't exit successfully: 
`/tmp/tmp.Oamh8HTRc5/target/debug/build/libsodium-sys-17f33e83e141b528/build-script-build`
 (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=SODIUM_LIB_DIR
  cargo:rerun-if-env-changed=SODIUM_SHARED
  cargo:rerun-if-env-changed=SODIUM_USE_PKG_CONFIG
  cargo:rerun-if-env-changed=SODIUM_DISABLE_PIE

  --- stderr
  thread 'main' panicked at 'Failed to open libsodium-1.0.18.tar.gz: Os { code: 
2, kind: NotFound, message: "No such file or directory" }', build.rs:370:34
  stack backtrace:
 0: rust_begin_unwind
   at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
 1: core::panicking::panic_fmt
   at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
 2: core::result::unwrap_failed
   at /usr/src/rustc-1.63.0/library/core/src/result.rs:1805:5
 3: core::result::Result::expect
   at /usr/src/rustc-1.63.0/library/core/src/result.rs:1055:23
 4: build_script_build::get_archive
   at ./build.rs:370:13
 5: build_script_build::build_libsodium
   at ./build.rs:419:27
 6: build_script_build::main
   at ./build.rs:64:9
 7: core::ops::function::FnOnce::call_once
   at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
  note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.
autopkgtest [16:42:22]: test librust-libsodium-sys-dev: ---]
autopkgtest [16:42:22]: test librust-libsodium-sys-dev:  - - - - - - - - - - 
results - - - - - - - - - -
librust-libsodium-sys-dev FAIL non-zero exit status 101
autopkgtest [16:42:22]:  summary
@PASS
librust-libsodium-sys-dev FAIL non-zero exit status 101

Bug#1030442: marked as done (ruby-rack: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError: invalid domain: ".test.com")

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 17:00:27 +
with message-id 
and subject line Bug#1030442: fixed in ruby-rack 2.2.4-3
has caused the Debian Bug report #1030442,
regarding ruby-rack: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError: 
invalid domain: ".test.com"
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.)


-- 
1030442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack
Version: 2.2.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> ArgumentError: invalid domain: ".test.com"
> /usr/lib/ruby/3.1.0/cgi/cookie.rb:128:in `domain='
> /usr/lib/ruby/3.1.0/cgi/cookie.rb:95:in `initialize'
> /<>/lib/rack/mock.rb:239:in `new'
> /<>/lib/rack/mock.rb:239:in `block in 
> parse_cookies_from_header'
> /<>/lib/rack/mock.rb:236:in `each'
> /<>/lib/rack/mock.rb:236:in `parse_cookies_from_header'
> /<>/lib/rack/mock.rb:187:in `initialize'
> /<>/lib/rack/mock.rb:85:in `new'
> /<>/lib/rack/mock.rb:85:in `request'
> /<>/lib/rack/mock.rb:57:in `get'
> /<>/test/spec_mock.rb:365:in `block (2 levels) in  (required)>'
> 
> 1152 runs, 3990 assertions, 0 failures, 27 errors, 3 skips
> 
> You have skipped tests. Run with --verbose for details.
> rake aborted!
> Command failed with status (1): [ruby -I"lib:test" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "test/spec_auth_basic.rb" "test/spec_auth_digest.rb" 
> "test/spec_body_proxy.rb" "test/spec_builder.rb" "test/spec_cascade.rb" 
> "test/spec_chunked.rb" "test/spec_common_logger.rb" 
> "test/spec_conditional_get.rb" "test/spec_config.rb" 
> "test/spec_content_length.rb" "test/spec_content_type.rb" 
> "test/spec_deflater.rb" "test/spec_directory.rb" "test/spec_etag.rb" 
> "test/spec_events.rb" "test/spec_files.rb" "test/spec_handler.rb" 
> "test/spec_head.rb" "test/spec_lint.rb" "test/spec_lobster.rb" 
> "test/spec_lock.rb" "test/spec_logger.rb" "test/spec_media_type.rb" 
> "test/spec_method_override.rb" "test/spec_mime.rb" "test/spec_mock.rb" 
> "test/spec_multipart.rb" "test/spec_null_logger.rb" "test/spec_recursive.rb" 
> "test/spec_request.rb" "test/spec_response.rb" 
> "test/spec_rewindable_input.rb" "test/spec_runtime.rb" 
> "test/spec_sendfile.rb" "test/spec_server.rb" 
> "test/spec_session_abstract_id.rb" "test/spec_session_abstract_persisted.rb" 
> "test/spec_session_abstract_persisted_secure_secure_session_hash.rb" 
> "test/spec_session_abstract_session_hash.rb" "test/spec_session_cookie.rb" 
> "test/spec_session_pool.rb" "test/spec_show_exceptions.rb" 
> "test/spec_show_status.rb" "test/spec_static.rb" 
> "test/spec_tempfile_reaper.rb" "test/spec_thin.rb" "test/spec_urlmap.rb" 
> "test/spec_utils.rb" "test/spec_version.rb" "test/spec_webrick.rb" 
> "test/gemloader.rb" ]
> 
> Tasks: TOP => default => test
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
http://qa-logs.debian.net/2023/02/03/ruby-rack_2.2.4-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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: ruby-rack
Source-Version: 2.2.4-3
Done: Sruthi Chandran 

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

Debian distribution 

Bug#1029832: marked as done (ruby-rack: CVE-2022-44570 CVE-2022-44571 CVE-2022-44572)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 17:00:27 +
with message-id 
and subject line Bug#1029832: fixed in ruby-rack 2.2.4-3
has caused the Debian Bug report #1029832,
regarding ruby-rack: CVE-2022-44570 CVE-2022-44571 CVE-2022-44572
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.)


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

Hi,

The following vulnerabilities were published for ruby-rack.

CVE-2022-44570[0]:
| rack: Fix ReDoS in Rack::Utils.get_byte_ranges

CVE-2022-44571[1]:
| rack: Fix ReDoS vulnerability in multipart parser

CVE-2022-44572[2]:
| rack: Forbid control characters in attributes

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-44570
https://www.cve.org/CVERecord?id=CVE-2022-44570
[1] https://security-tracker.debian.org/tracker/CVE-2022-44571
https://www.cve.org/CVERecord?id=CVE-2022-44571
[2] https://security-tracker.debian.org/tracker/CVE-2022-44572
https://www.cve.org/CVERecord?id=CVE-2022-44572

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ruby-rack
Source-Version: 2.2.4-3
Done: Sruthi Chandran 

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

Debian distribution maintenance software
pp.
Sruthi Chandran  (supplier of updated ruby-rack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 09 Feb 2023 11:47:17 +0100
Source: ruby-rack
Architecture: source
Version: 2.2.4-3
Distribution: unstable
Urgency: high
Maintainer: Debian Ruby Team 

Changed-By: Sruthi Chandran 
Closes: 1029832 1030442
Changes:
 ruby-rack (2.2.4-3) unstable; urgency=high
 .
   * Team upload
   * Fix test failures (Closes:  #1030442)
   * Fix CVE-2022-44570 CVE-2022-44571 CVE-2022-44572 (Closes:  #1029832)
   * Add Breaks for ruby-sinatra
Checksums-Sha1:
 3eca0143cdc2a7927a1bbffbc4732f230d4bdab3 2165 ruby-rack_2.2.4-3.dsc
 3e11458f9841eb86ed9ff62264804290c00dce41 10484 ruby-rack_2.2.4-3.debian.tar.xz
 cffc772f0b91805f3006c8068a23bf959ee15559 9194 ruby-rack_2.2.4-3_amd64.buildinfo
Checksums-Sha256:
 82715d0642a28aac99f9b351b1e048ad879c954835b42dde88760dae052532b2 2165 
ruby-rack_2.2.4-3.dsc
 66ad16c0cd91e2317cce6a53944970544d7a2b47b0f159da7026c3782a551702 10484 
ruby-rack_2.2.4-3.debian.tar.xz
 680c842c82c4f8a13a84981a7bfffaea4b78c91f8078c60947f2e642ce8aaf43 9194 
ruby-rack_2.2.4-3_amd64.buildinfo
Files:
 a24601c50bd142ac78a66d3c2da4f8b1 2165 ruby optional ruby-rack_2.2.4-3.dsc
 68e9e4fbe6d7f450dde64bf281a8bf9a 10484 ruby optional 
ruby-rack_2.2.4-3.debian.tar.xz
 185aad555768e8f9aeb9e818aa728623 9194 ruby optional 
ruby-rack_2.2.4-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEEcd3Fxr6GmkZB13n+x+ob4VdN7V0FAmPmbJkACgkQx+ob4VdN
7V2J3gwAgfy72J26Eq5Esd93ikxX6SzeEwjvDQpT1CdycLYcQhW+EFHT6GA/Q6xp
TasN7sUQC4ho3IMq218bPunSXaVRU2gCQ/Pb7bqziS1NuRi9YwVnBcPg25sHD6+9
+XYOYebsH6FENlYpgWLiijqYL9Ysxrq9dZ9XA2xMUYwlYXTeRj1HRE+deZo3vu7I
3j3Ar/g9Xz0qe0r6fERdxA8sEemoQ9yWhV243AZL3i/JMBxZJER/BQLS8Wj79pES
9hpW4RmYF6uXjq+Y+V1D03+Y1Dwpyw33V8k0Ihq7YjxwY3JiU4CPodEmI5Ix0loY
9Kw6odqiaUJsT2sbvvMvgCeSb6tVZmnduUX85KUF707LwuaLNTdQ4GAKYAd+FfRl
bxKEFWKFiOp+Y1TKsHaPaqkzDM2qTeWKDUNUi6S0usJxkGkqPCPiz9LoBRDP5zqc
prk8HPywUajr3bGuzsRk51MvwGyKHDvWfWTSOtOEWJN/MxqLefn/rxvr8Y7BPeZ4
GlgfX+pK
=5OHE
-END PGP SIGNATURE End Message ---

Bug#980575: marked as done (kworkflow: autopkgtest needs update for new version of git)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 16:55:56 +
with message-id 
and subject line Bug#980575: fixed in kworkflow 20191112-1.2
has caused the Debian Bug report #980575,
regarding kworkflow: autopkgtest needs update for new version of git
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.)


-- 
980575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kworkflow
Version: 20191112-1.1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, g...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git

Dear maintainer(s),

With a recent upload of git the autopkgtest of kworkflow fails in
testing when that autopkgtest is run with the binary packages of git
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
gitfrom testing1:2.30.0-1
kworkflow  from testing20191112-1.1
all others from testingfrom testing

I copied some of the output at the bottom of this report. git is
printing a warning to stderr, and your autopkgtest fails on that (you
can ignore it with the allow-stderr, you can of course prevent the output).

Currently this regression is blocking the migration of git to testing
[1]. Of course, git shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in git was
intended and your package needs to update to the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from git should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
git/1:2.30.0-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=git

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kworkflow/9861987/log.gz

OK
=
Total: 12 test file(s)
Test file(s) SUCCEEDED
test_codestyle
test_maintainers
test_explore
hint: Using 'master' as the name for the initial branch. This default
branch name
hint: is subject to change. To configure the initial branch name to use
in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch 
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this
command:
hint:
hint:   git branch -m 
Initialized empty Git repository in
/tmp/autopkgtest-lxc.e4dt0kgy/downtmp/autopkgtest_tmp/.git/

Ran 3 tests.

OK
autopkgtest [14:14:07]: test kw-basic-test: ---]
autopkgtest [14:14:07]: test kw-basic-test:  - - - - - - - - - - results
- - - - - - - - - -
kw-basic-testFAIL stderr: hint: Using 'master' as the name for
the initial branch. This default branch name
autopkgtest [14:14:08]: test kw-basic-test:  - - - - - - - - - - stderr
- - - - - - - - - -
hint: Using 'master' as the name for the initial branch. This default
branch name
hint: is subject to change. To configure the initial branch name to use
in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch 
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this
command:
hint:
hint:   git branch -m 
autopkgtest [14:14:08]:  summary
kw-basic-testFAIL stderr: hint: Using 'master' as the name for
the initial branch. This default branch name



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: kworkflow
Source-Version: 20191112-1.2
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
kworkflow, which is due to be installed in the Debian FTP archive.

A summary of the changes be

Processed: tagging 1016131

[Debian Bug Tracking System]

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

> tags 1016131 + bullseye
Bug #1016131 [libapache2-mod-jk] libapache2-mod-jk: Apache does not start after 
upgrade (JkWorkersFile only allowed once)
Added tag(s) bullseye.
> thanks
Stopping processing here.

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

Bug#980575: kworkflow: diff for NMU version 20191112-1.2

[Adrian Bunk]

Control: tags 980575 + patch

Dear maintainer,

I've uploaded an NMU for kworkflow (versioned as 20191112-1.2).
The diff is attached to this message.

cu
Adrian
diff -Nru kworkflow-20191112/debian/changelog kworkflow-20191112/debian/changelog
--- kworkflow-20191112/debian/changelog	2020-05-30 09:37:01.0 +0300
+++ kworkflow-20191112/debian/changelog	2023-02-10 18:30:18.0 +0200
@@ -1,3 +1,11 @@
+kworkflow (20191112-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply autopkgtest fix for newer git from Steve Langasek.
+(Closes: #980575)
+
+ -- Adrian Bunk   Fri, 10 Feb 2023 18:30:18 +0200
+
 kworkflow (20191112-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru kworkflow-20191112/debian/tests/kw-basic-test kworkflow-20191112/debian/tests/kw-basic-test
--- kworkflow-20191112/debian/tests/kw-basic-test	2019-12-12 19:19:30.0 +0200
+++ kworkflow-20191112/debian/tests/kw-basic-test	2023-02-10 18:30:13.0 +0200
@@ -25,6 +25,7 @@
 
 git config --global user.email "deb...@debian.com"
 git config --global user.name "Debian SO"
+git config --global init.defaultBranch master
 
 ./run_tests.sh
 

Processed: kworkflow: diff for NMU version 20191112-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 980575 + patch
Bug #980575 [src:kworkflow] kworkflow: autopkgtest needs update for new version 
of git
Added tag(s) patch.

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

Bug#1030559: marked as done (speechpy-fast: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 15:23:26 +
with message-id 
and subject line Bug#1030559: fixed in speechpy-fast 2.4-2
has caused the Debian Bug report #1030559,
regarding speechpy-fast: autopkgtest failure
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.)


-- 
1030559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: speechpy-fast
Version: 2.4-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/s/speechpy-fast/31022842/log.gz

...
autopkgtest [03:53:37]: test autodep8-python3: set -e ; for py in $(py3versions 
-r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c 
"import speechpy_fast; print(speechpy_fast)" ; done
autopkgtest [03:53:37]: test autodep8-python3: [---
Testing with python3.11:
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'speechpy_fast'
autopkgtest [03:53:37]: test autodep8-python3: ---]
autopkgtest [03:53:37]: test autodep8-python3:  - - - - - - - - - - results - - 
- - - - - - - -
autodep8-python3 FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: speechpy-fast
Source-Version: 2.4-2
Done: Scarlett Moore 

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

Debian distribution maintenance software
pp.
Scarlett Moore  (supplier of updated speechpy-fast package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Feb 2023 07:54:46 -0700
Source: speechpy-fast
Architecture: source
Version: 2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Scarlett Moore 
Changed-By: Scarlett Moore 
Closes: 1030559
Changes:
 speechpy-fast (2.4-2) unstable; urgency=medium
 .
   * Remove Testsuite from control as there are no tests.
(Closes: 1030559)
Checksums-Sha1:
 4a5f9dac82be77df552a9fc6b4b94acc32afaffb 1950 speechpy-fast_2.4-2.dsc
 87d7f25ca6156c5f3f58965fe1ac451120b7f3be 8848 speechpy-fast_2.4.orig.tar.xz
 c682de8c13eb348ad8c235b5e5201f1867ba 2220 speechpy-fast_2.4-2.debian.tar.xz
 ccf80661429362a6eaa343459130bf11573e6110 7493 
speechpy-fast_2.4-2_amd64.buildinfo
Checksums-Sha256:
 df0c7f02ef31fb661504ea1742881db8ae63cc6b7a4e7d9de377e4738897e7a7 1950 
speechpy-fast_2.4-2.dsc
 3fbd409b7147ff205888a9a558ba9f93b1167eb1a42deadd51bb1511ce5481e4 8848 
speechpy-fast_2.4.orig.tar.xz
 56728af93afb8dc1ad5560f62c8f05a44c7c376f6028adb75272d8b497b80f7f 2220 
speechpy-fast_2.4-2.debian.tar.xz
 33bec0b6b462b987c1c4820147f27207b81a7d0b266173be381601e55815deb1 7493 
speechpy-fast_2.4-2_amd64.buildinfo
Files:
 52c3fe030709fcdfe180b880c610b6a8 1950 python optional speechpy-fast_2.4-2.dsc
 d52498365865afda065752d44f895e02 8848 python optional 
speechpy-fast_2.4.orig.tar.xz
 0691222fe316b8338c40a7e325353675 2220 python optional 
speechpy-fast_2.4-2.debian.tar.xz
 8acaa6534259baf3a1314d662fa59256 7493 python optional 
speechpy-fast_2.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEfDWSDxziiZ6OqarQLnwDZ7m/oIkFAmPmXG4THHNnbW9vcmVA
ZGViaWFuLm9yZwAKCRAufANnub+giVa4D/0YEzTT/5kBya02Ow+XTgGpE5iUL3Mv
kU732DPJY1sz8gIEfSbZzgSe1HKJp/YfeiJ0WBCpoXjqcEfkNhrBIBQ6beq/MI/J
vJ8jU4xZ7zuz/Wppvx4Pu+ze+WB0eQ6ijSGpMWEx8DjEWPwQM9JJVIKyi5MgzgkW
mQVJ+pdx/a2BC7Le6DK38WXFWnJhBqVlX7oka0kzF/Ocs9c2DCqeniueUEN79S78
rKZmsVJfqmG3Tpy16vqRgQTd2hA9MHiibZQEAUxTB3Q8nloswAFNOxZRo0ObIeWG
voRfaJUzuklG5AfR7Pk4r2ysgmuCDj1cuSXWWWXxcCZ4xxiNpj+efvAjbYNP0unM
gLjJGhSPCZtUdYnmHXW+EiFvbKrsuUNrK63/8u5h0Tm/0mkmY+udBkYICET9R0/n
Q+geqAaaI5+ZvhUCB5dF4FsWJ0V1lEx9O8YC22EP5NkyBC1T3ebJa4w8CD5HIyVZ
S/uOEY6okz95l4zkFYP5/7WgI5cmu39fQEf0XLaCQB1i+zEnHsxmMetO1vQAGHxC
PX88pn9KrYLVA/67aekb5ETWWEFl/IP0QKwwRH047fWZq+wjCA41oaVroFrAhqvM
pxcS7ds/RuHPdt/scApaSh8p+zH1GVxLLDZmxaJ661QFpVXiECWcz6RoWll1SF5R
gALVFqmDXiCDjQ==
=T3zr
-END PGP SIGNATURE End Message ---

Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Cyril Brulebois]

Theodore Ts'o  (2023-02-10):
> But that problem has already been solved by cloning the bug back to
> e2fpsrogs (#1030939) which will prevent e2fsprogs from transitioning
> to testing, no?  So what's the problem.

I never said there was a problem with the current state of things
(indeed, that's one of the two soltions I described as being equally
fine with me).

Instead, I've explained why your suggested “solution” wouldn't help,
with some context since you seemed unconvinced by previous answers from
others.


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


signature.asc
Description: PGP signature

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1012232 autoconf
Bug #1012232 [src:freespace2] freespace2: FTBFS: ./configure: line 17040: 
syntax error near unexpected token `ax_cxx_compile_cxx11_required=falsednl'
Bug reassigned from package 'src:freespace2' to 'autoconf'.
No longer marked as found in versions freespace2/3.7.4+repack-1.1.
Ignoring request to alter fixed versions of bug #1012232 to the same values 
previously set
> forcemerge 1016728 1012232
Bug #1016728 {Done: Matthias Klose } [autoconf] autoconf: 
_AC_PROG_CXX_STDCXX_EDITION_TRY test is broken due to typo
Bug #1012232 [autoconf] freespace2: FTBFS: ./configure: line 17040: syntax 
error near unexpected token `ax_cxx_compile_cxx11_required=falsednl'
Severity set to 'important' from 'serious'
Marked Bug as done
Marked as fixed in versions autoconf/2.71-3.
Marked as found in versions autoconf/2.71-2.
Added tag(s) fixed-upstream and patch.
Bug #1016728 {Done: Matthias Klose } [autoconf] autoconf: 
_AC_PROG_CXX_STDCXX_EDITION_TRY test is broken due to typo
Added tag(s) sid, bookworm, and ftbfs.
Merged 1012232 1016728
> affects 1016728 src:freespace2
Bug #1016728 {Done: Matthias Klose } [autoconf] autoconf: 
_AC_PROG_CXX_STDCXX_EDITION_TRY test is broken due to typo
Bug #1012232 {Done: Matthias Klose } [autoconf] freespace2: 
FTBFS: ./configure: line 17040: syntax error near unexpected token 
`ax_cxx_compile_cxx11_required=falsednl'
Added indication that 1016728 affects src:freespace2
Added indication that 1012232 affects src:freespace2
> thanks
Stopping processing here.

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

Bug#1030982: gscan2pdf: Segmentation fault

[Janusz S . Bień]

On Fri, Feb 10 2023 at 12:54 GMT, Jeff wrote:
> In the log you provide, you seem to have a successful scan. Is the
> problem therefore only the warning message?

It's binary: either it works or not, depending on the choice of the device.

>
> If the other device does not work, please provide a log file created
> when scanning with the other device.

It was attached to my previous mail.


On Fri, Feb 10 2023 at 12:33 +01, Janusz S. Bień wrote:

[...]

> The failure log is missing the line which appeared on the terminal:
>
> Not a JPEG file: starts with 0x00 0x00


Regards - Janusz

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Theodore Ts'o]

On Fri, Feb 10, 2023 at 08:31:04AM +0100, Cyril Brulebois wrote:
> > Holding back file system development because grub2 uptsream is super
> > slow doesn't seem like a reasonable way forward, so I really don't
> > want to set this precedent.
> 
> The Bookworm freeze has started, we need to be able to install stuff, so
> we need a solution for the grub2/e2fsprogs situation *now*.
> 
> I really don't care about “setting a precedent”.

But that problem has already been solved by cloning the bug back to
e2fpsrogs (#1030939) which will prevent e2fsprogs from transitioning
to testing, no?  So what's the problem.

The fact that grub2 upstream is super-slow in doing releases is
already a pain in *ass that has caused much pain over the years.
Adding a conflict just adds more pain, without adding any additional
benefit.  So what's the point?

 - Ted

Bug#1031017: rust-webbrowser: autopkgtest failure

[Adrian Bunk]

Source: rust-webbrowser
Version: 0.5.2-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-webbrowser/31209809/log.gz

...
unning 4 tests
test test_open_chrome ... ignored
test test_open_firefox ... ignored
test test_open_safari ... ignored
test test_open_default ... FAILED

failures:

 test_open_default stdout 
thread 'test_open_default' panicked at 'assertion failed: 
open(\"http://github.com\";).is_ok()', src/lib.rs:331:5
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
   2: core::panicking::panic
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:48:5
   3: webbrowser::test_open_default
 at ./src/lib.rs:331:5
   4: webbrowser::test_open_default::{{closure}}
 at ./src/lib.rs:330:1
   5: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
   6: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
test_open_default

test result: FAILED. 0 passed; 1 failed; 3 ignored; 0 measured; 0 filtered out; 
finished in 0.01s

error: test failed, to rerun pass `--lib`
autopkgtest [14:00:43]: test command2: ---]
autopkgtest [14:00:43]: test command2:  - - - - - - - - - - results - - - - - - 
- - - -
command2 FAIL non-zero exit status 101
autopkgtest [14:00:43]:  summary
command1 FAIL non-zero exit status 101
command2 FAIL non-zero exit status 101

Bug#1013153: camitk: vtk[6,7] removal

[Andreas Tille]

Hi Emmanuel,

Am Wed, Feb 01, 2023 at 04:21:35PM +0100 schrieb Andreas Tille:
> I've checked insice my build-chroot
> 
>   # grep -c 'error while loading' 
> /build/camitk-5.0.2/camitk-build/Testing/Temporary/LastTest.log   
>   
>   505
> 
> so yes, its always the same error for all bugs like for example
> ... 
> Thanks.  I keep Pierre in CC who frequently found a solution for Java
> issues.

I admit I lost a bit track on camitk but I'm afraid its to late now to
let it migrate to testing.  Please also note that I will be not able to
work on this package for the next 10 days since I do not have access to
any proper machine. 

Kind regards
Andreas.

-- 
http://fam-tille.de

Bug#1031015: librust-ogg+async-dev is not installable

[Adrian Bunk]

Package: librust-ogg+async-dev
Version: 0.7.0-1
Severity: serious
Tags: bookworm sid

The following packages have unmet dependencies:
 librust-ogg+async-dev : Depends: librust-bytes-0.4+default-dev
 Depends: librust-futures-0.1+default-dev
 Depends: librust-tokio-io-0.1+default-dev

Bug#1031014: rust-r2d2: autopkgtest regression on ppc64el

[Adrian Bunk]

Source: rust-r2d2
Version: 0.8.10-3
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/ppc64el/r/rust-r2d2/31176721/log.gz

...
test test::test_idle_timeout ... FAILED
test test::test_max_lifetime ... ok

failures:

 test::test_idle_timeout stdout 
thread 'test::test_idle_timeout' panicked at 'assertion failed: `(left == 
right)`
  left: `4`,
 right: `2`', src/test.rs:392:5
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:181:5
   4: r2d2::test::test_idle_timeout
 at ./src/test.rs:392:5
   5: r2d2::test::test_idle_timeout::{{closure}}
 at ./src/test.rs:350:1
   6: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
   7: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
test::test_idle_timeout

test result: FAILED. 17 passed; 1 failed; 0 ignored; 0 measured; 0 filtered 
out; finished in 9.13s

error: test failed, to rerun pass `--lib`
autopkgtest [00:20:10]: test librust-r2d2-dev:default: ---]
librust-r2d2-dev:default FAIL non-zero exit status 101
...
autopkgtest [00:20:43]:  summary
rust-r2d2:@  PASS
librust-r2d2-dev:default FAIL non-zero exit status 101
librust-r2d2-dev:PASS


This might be related to

rust-r2d2 (0.8.10-3) unstable; urgency=medium
...
  * Dropped fix-test.diff; skipped idle_timeout on arm(el,hf), i386 and
ppc64el

 -- Matthias Geiger   Fri, 10 Feb 2023 
10:12:58 +0100

Bug#1031013: librust-rust-code-analysis-dev is not installable

[Adrian Bunk]

Package: librust-rust-code-analysis-dev
Version: 0.0.18-2
Severity: serious

The following packages have unmet dependencies:
 librust-rust-code-analysis-dev : Depends: librust-petgraph-0.5+default-dev
  Depends: librust-phf-0.8+default-dev
  Depends: librust-phf-0.8+macros-dev
  Depends: librust-phf-codegen-0.8+default-dev
  Depends: librust-tree-sitter-0.17+default-dev

Processed: severity of 1030227 is important

[Debian Bug Tracking System]

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

> severity 1030227 important
Bug #1030227 [rtpengine] rtpengine: please use dkms packaging helpers
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1031011: pgagroal: autopkgtest failure on s390x

[Adrian Bunk]

Source: pgagroal
Version: 1.5.0-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/s390x/p/pgagroal/31207516/log.gz

...
autopkgtest [04:12:21]: test connect: [---
+ trap bailout EXIT
+ service postgresql stop
+ test -d /run/systemd/system
+ systemctl start pgagroal.socket
+ pg_virtualenv -oport=5432
Creating new PostgreSQL cluster 15/regress ...
+ PW=agroalpass
+ su -c '( echo agroalpass; echo agroalpass ) | createuser --pwprompt 
agroaltestuser' postgres
Enter password for new role: 
Enter it again: 
+ PGPASSWORD=agroalpass
+ psql -h /run/postgresql -p 2345 -U agroaltestuser -c 'select 6*7' postgres
+ grep 42
autopkgtest [06:59:01]: ERROR: timed out on command "su -s /bin/bash root -c 
set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true;  . 
~/.profile >/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.17zbkv9d/downtmp/build.rre/src"; mkdir -p -m 
1777 -- "/tmp/autopkgtest-lxc.17zbkv9d/downtmp/connect-artifacts"; export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.17zbkv9d/downtmp/connect-artifacts";
 export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.17zbkv9d/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.17zbkv9d/downtmp/autopkgtest_tmp"; export 
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=10; unset LANGUAGE LC_CTYPE 
LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME 
LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;cd 
"$buildtree"; export AUTOPKGTEST_NORMAL_USER=debci; export 
ADT_NORMAL_USER=debci; chmod +x 
/tmp/autopkgtest-lxc.17zbkv9d/downtmp/build.rre/src/debian/tests/connect; exec 
/tmp/autopkgtest-lxc.17zbkv9d/downtmp/wrapper.sh 
--script-pid-file=/tmp/autopkgtest_script_pid 
--stderr=/tmp/autopkgtest-lxc.17zbkv9d/downtmp/connect-stderr 
--stdout=/tmp/autopkgtest-lxc.17zbkv9d/downtmp/connect-stdout -- 
/tmp/autopkgtest-lxc.17zbkv9d/downtmp/build.rre/src/debian/tests/connect ;" 
(kind: test)
autopkgtest [06:59:01]: test connect: ---]
autopkgtest [06:59:01]: test connect:  - - - - - - - - - - results - - - - - - 
- - - -
connect  FAIL timed out

Bug#965794: python-ooolib: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Santiago Vila]

Note: The absolute minimum change to fix the FTBFS problem is to raise
debian/compat from 5 to 7.

However, it is possible to raise it from 5 to 11 without changing anything else,
and the package is still functionally equivalent.

When using compat 12 there are things in debian/rules that would have to be
changed as well, those can be fixed after the release of bookworm.

I attach the proposed diff (for this bug) and also the output from
diffoscope when applying such change, where it can be seen that the
generated package is still "equivalent" and none of the changes is really
significant.

Thanks.--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-5
+11
--- old/python3-ooolib_0.0.22-5_all.deb
+++ python3-ooolib_0.0.22-5_all.deb
├── file list
│ @@ -1,3 +1,3 @@
│  -rw-r--r--   0004 2019-09-15 19:10:44.00 
debian-binary
│ --rw-r--r--   000 1452 2019-09-15 19:10:44.00 
control.tar.xz
│ --rw-r--r--   00020212 2019-09-15 19:10:44.00 
data.tar.xz
│ +-rw-r--r--   000 1428 2019-09-15 19:10:44.00 
control.tar.xz
│ +-rw-r--r--   00019864 2019-09-15 19:10:44.00 
data.tar.xz
├── control.tar.xz
│ ├── control.tar
│ │ ├── file list
│ │ │ @@ -1,5 +1,5 @@
│ │ │  drwxr-xr-x   0 root (0) root (0)0 2019-09-15 
19:10:44.00 ./
│ │ │  -rw-r--r--   0 root (0) root (0)  490 2019-09-15 
19:10:44.00 ./control
│ │ │  -rw-r--r--   0 root (0) root (0) 1651 2019-09-15 
19:10:44.00 ./md5sums
│ │ │ --rwxr-xr-x   0 root (0) root (0)  253 2019-09-15 
19:10:44.00 ./postinst
│ │ │ --rwxr-xr-x   0 root (0) root (0)  402 2019-09-15 
19:10:44.00 ./prerm
│ │ │ +-rwxr-xr-x   0 root (0) root (0)  263 2019-09-15 
19:10:44.00 ./postinst
│ │ │ +-rwxr-xr-x   0 root (0) root (0)  376 2019-09-15 
19:10:44.00 ./prerm
│ │ ├── ./md5sums
│ │ │ ├── ./md5sums
│ │ │ │┄ Files differ
│ │ ├── ./postinst
│ │ │ @@ -1,12 +1,12 @@
│ │ │  #!/bin/sh
│ │ │  set -e
│ │ │  
│ │ │  # Automatically added by dh_python3
│ │ │ -if which py3compile >/dev/null 2>&1; then
│ │ │ +if command -v py3compile >/dev/null 2>&1; then
│ │ │   py3compile -p python3-ooolib 
│ │ │  fi
│ │ │ -if which pypy3compile >/dev/null 2>&1; then
│ │ │ +if command -v pypy3compile >/dev/null 2>&1; then
│ │ │   pypy3compile -p python3-ooolib  || true
│ │ │  fi
│ │ │  
│ │ │  # End automatically added section
│ │ ├── ./prerm
│ │ │ @@ -1,12 +1,12 @@
│ │ │  #!/bin/sh
│ │ │  set -e
│ │ │  
│ │ │  # Automatically added by dh_python3
│ │ │ -if which py3clean >/dev/null 2>&1; then
│ │ │ +if command -v py3clean >/dev/null 2>&1; then
│ │ │   py3clean -p python3-ooolib 
│ │ │  else
│ │ │ - dpkg -L python3-ooolib | perl -ne 's,/([^/]*)\.py$,/__pycache__/\1.*, 
or next; unlink $_ or die $! foreach glob($_)'
│ │ │ + dpkg -L python3-ooolib | sed -En -e '/^(.*)\/(.+)\.py$/s,,rm 
"\1/__pycache__/\2".*,e'
│ │ │   find /usr/lib/python3/dist-packages/ -type d -name __pycache__ -empty 
-print0 | xargs --null --no-run-if-empty rmdir
│ │ │  fi
│ │ │  
│ │ │  # End automatically added section
├── data.tar.xz
│ ├── data.tar
│ │ ├── file list
│ │ │ @@ -10,15 +10,15 @@
│ │ │  -rw-r--r--   0 root (0) root (0) 8222 2018-01-08 
09:48:31.00 ./usr/lib/python3/dist-packages/ooolib/tests/test_calc_cell.py
│ │ │  -rw-r--r--   0 root (0) root (0)  234 2018-01-08 
09:48:31.00 ./usr/lib/python3/dist-packages/ooolib/tests/utils.py
│ │ │  -rw-r--r--   0 root (0) root (0)  289 2019-09-15 
19:10:44.00 ./usr/lib/python3/dist-packages/ooolib_python-0.0.21.egg-info
│ │ │  drwxr-xr-x   0 root (0) root (0)0 2019-09-15 
19:10:44.00 ./usr/share/
│ │ │  drwxr-xr-x   0 root (0) root (0)0 2019-09-15 
19:10:44.00 ./usr/share/doc/
│ │ │  drwxr-xr-x   0 root (0) root (0)0 2019-09-15 
19:10:44.00 ./usr/share/doc/python3-ooolib/
│ │ │  -rw-r--r--   0 root (0) root (0) 1341 2018-01-08 
09:48:31.00 ./usr/share/doc/python3-ooolib/README
│ │ │ --rw-r--r--   0 root (0) root (0)  870 2019-09-15 
19:10:44.00 ./usr/share/doc/python3-ooolib/changelog.Debian.gz
│ │ │ +-rw-r--r--   0 root (0) root (0)  531 2019-09-15 
19:10:44.00 ./usr/share/doc/python3-ooolib/changelog.Debian.gz
│ │ │  -rw-r--r--   0 root (0) root (0) 1418 2018-01-08 
09:48:31.00 ./usr/share/doc/python3-ooolib/changelog.gz
│ │ │  -rw-r--r--   0 root (0) root (0)  600 2019-09-15 
19:10:44.00 ./usr/share/doc/python3-ooolib/copyright
│ │ │  drwxr-xr-x   0 root (0) root (0)0 2019-09-15 
19:10:44.00 ./usr/share/doc/python3-ooolib/examples/
│ │ │  -rw-r--r--   0 root (0) root (0)  491 2018-01-08 
09:4

Bug#1030982: gscan2pdf: Segmentation fault

[Jeff]

In the log you provide, you seem to have a successful scan. Is the 
problem therefore only the warning message?


If the other device does not work, please provide a log file created 
when scanning with the other device.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1029578: New security

[William Desportes]

using git bisect and icmake unit tests I found out that 
https://github.com/kward/shunit2/commit/f08632b331612f554e97c598508e4aac3dfa39a2#diff-a453761d888ea6645a651da189e89605523e4eab9500ee9e5988e55bca4f437bR892-R896
 is the first bad commit. 
it's a new security that was added, so the affected packages must adapt. 

ref: https://github.com/kward/shunit2/issues/84

now shunit2 does not like that any command exits -gt 0 in a test.

so the fix is:
- assertTrue commandExits1
+ assertTrue "$(commandExit1; echo $?)"

Bug#998970: marked as done (setcd: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 11:35:07 +
with message-id 
and subject line Bug#998970: fixed in setcd 1.5-6.1
has caused the Debian Bug report #998970,
regarding setcd: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


-- 
998970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: setcd
Version: 1.5-6
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: setcd
Source-Version: 1.5-6.1
Done: Stephen Kitt 

We believe that the bug you reported is fixed in the latest version of
setcd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 998...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated setcd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 09 Feb 2023 13:52:45 +0100
Source: setcd
Architecture: source
Version: 1.5-6.1
Distribution: unstable
Urgency: medium
Maintainer: LENART Janos 
Changed-By: Stephen Kitt 
Closes: 902574 965821 998970
Changes:
 setcd (1.5-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch to debhelper compatibility level 13 with short dh rules,
 enabling all hardening options. Closes: #965821, #998970.
   * Explicitly mark the package as using format “1.0”.
   * Pass dpkg-specified compiler settings to the build. Closes: #902574.
   * Set “Rules-Requires-Root: no”.
   * Clean up whitespace in debian/changelog.
Checksums-Sha1:
 2162b10fe1571fa938e735c5501e1a97c0b4dfd3 1601 setcd_1.5-6.1.dsc
 aabb0904d7ddd02c133fe953a43403e57d1f8a8e 5488 setcd_1.5-6.1.diff.gz
 7c4ad30644e34151d3b9fe52deddd96fd49d3938 6434 setcd_1.5-6.1_source.buildinfo
Checksums-Sha256:
 670ca5bdaae0396f5c4ed7021fb691f85056fd581ae9fba32e2eb191d62b7a8f 1601 
setcd_1.5-6.1.dsc
 67857817d7e6aa0002dd130e4699005aa67842d0a11f190bcd988b61ac27fa45 5488 
setcd_1.5-6.1.diff.gz
 3ae91a2e2f8037b9396d7c7e4a9c7821305ddb3a0028ac5d5a735a09e42cd2b0 6434 
setcd_1.5-6.1_source.buildinfo
Files:
 a62a9f1f6f20af8b4ac5e268d45939bd 1601 utils optional setcd_1.5-6.1.dsc
 e2bbb004e30e6e7a07f964daac6cb695 5488 utils optional setcd_1.5-6.1.diff.gz
 76bf2540638bfb24d8017ff7e25498f6 6434 utils optional 
setcd_1.5-6.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmPk7LcACgkQgNMC9Yht
g5wjFw//W84T1tga74cm06XcX1zdQTtC2rS8QBo9iqYZQ7L6UHwEdEIxV3WIFbgE
Xh7sCeMcfzrL212CgYvjhDcAZ0qD5rPLjoRuYvO9LnOnP26vixgiSE/jF41by6Dx
p9jErKcJypJJwjyKTin2jlK+dUWt2ytcipPN8pAPt9qf1iLikrE0AbU0zlZl5Ea1
er4pFOmfHYlqKyXLd/1NxzAaDywkHrPhZNspDF5uqpx7hjbPIzRGmNT3acMxwzDd
K8HK+zEl9P9S7HlxEcGQ6t75uz9XS59IpLLGWRitUcJ+FoR1yqIE/jaH55V5XV6S
USDobzHfhoHcL2sokth/A5pdtBo8FHcZ0qhs/IExZGItI3TGFyET5aVx7gh3vgUm
8ssrYz+AmJ7Kxh/tRuwbmqE1X7gZt2aikZH2IiW8629m3Tkj+TG9EIIyPVY6SUDo
0RwSAwAf7JeNiPoMuw8uMfv/4fEK49eWM0DMsKtart7A82bi/hfL1ARBFscyJiR6
qaMJu+Yh3ZzHzk4yT8vXlJXn008dy2vjADjcXZT/knAAxrl0LAShYI9uwfc+8e1y
cywU0y7cnxM+6JcD1N4boLbinQluSj6Tje5+xFPIeX7gGWuirfUu+0D/E7F9QH41
3F+cY/Sew7/pjl7a178pszNVRtw75SQAAwD5XuuiIJ9zEDlOsMk=
=2XsK
-END PGP SIGNATURE End Message ---

Bug#985262: marked as done (librust-migrations-internals+barrel-dev: depends on unavailabe librust-barrel+default-dev)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 11:34:52 +
with message-id 
and subject line Bug#985262: fixed in rust-migrations-internals 2.0.0-1
has caused the Debian Bug report #985262,
regarding librust-migrations-internals+barrel-dev: depends on unavailabe 
librust-barrel+default-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.)


-- 
985262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-migrations-internals+barrel-dev
Version: 1.4.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in sid:

  The following packages have unmet dependencies:
   librust-migrations-internals+barrel-dev : Depends: 
librust-barrel+default-dev (< 0.2.1-~~)
 Depends: 
librust-barrel+diesel-filled-dev (< 0.2.1-~~) but it is not installable


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: rust-migrations-internals
Source-Version: 2.0.0-1
Done: Matthias Geiger 

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

Debian distribution maintenance software
pp.
Matthias Geiger  (supplier of updated 
rust-migrations-internals package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Feb 2023 12:08:25 +0100
Source: rust-migrations-internals
Architecture: source
Version: 2.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Matthias Geiger 
Closes: 985262
Changes:
 rust-migrations-internals (2.0.0-1) unstable; urgency=medium
 .
   * Package migrations_internals 2.0.0 from crates.io using debcargo 2.6.0 
(Closes: #985262)
   * Added myself to Uploaders
   * Updated copyright
Checksums-Sha1:
 c874057dba69336d58e713e3659b1640232f6626 2427 
rust-migrations-internals_2.0.0-1.dsc
 35d4a6f05fc5fdf96eecfdc00714cee2d1eeeabf 6094 
rust-migrations-internals_2.0.0.orig.tar.gz
 774bf33d92db0350446cd06027e8b4e23ae77aad 2764 
rust-migrations-internals_2.0.0-1.debian.tar.xz
 ae2960dccdd561f9ba9d980fd07742fa8f4073c8 9056 
rust-migrations-internals_2.0.0-1_source.buildinfo
Checksums-Sha256:
 9136d219b1de35d84719d1f3d34f9218246d8fcbb2e2ff892cfd9d8060869313 2427 
rust-migrations-internals_2.0.0-1.dsc
 c493c09323068c01e54c685f7da41a9ccf9219735c3766fbfd6099806ea08fbc 6094 
rust-migrations-internals_2.0.0.orig.tar.gz
 7d7c011725355369e10428293d9161ca270266a28bb19b469218fec38b4bc4a2 2764 
rust-migrations-internals_2.0.0-1.debian.tar.xz
 a43f3755e43c8ce0cd5ef03656ce95278fa915fedb7aecc4c1ba77dda76a74d7 9056 
rust-migrations-internals_2.0.0-1_source.buildinfo
Files:
 dda529a1801f8b0303f95b25b66101c4 2427 rust optional 
rust-migrations-internals_2.0.0-1.dsc
 66a324e5415beedf4b9d18cf1710db53 6094 rust optional 
rust-migrations-internals_2.0.0.orig.tar.gz
 4e0ebfda1b9017e3c569ead4eabaec27 2764 rust optional 
rust-migrations-internals_2.0.0-1.debian.tar.xz
 27cae9e13a5d07516492426fa9ef395e 9056 rust optional 
rust-migrations-internals_2.0.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAmPmJaoACgkQ1QhaB1D9
t6OewxAAncUMTADBUsThERGHFuOq2TP2Os0bGM+6+iykJw7oa6T8mo760R6DaDiq
YATIsCh2Z2LhK0rXDkEyq8/ji/LSTcs/Nlt5zp3g2N6Crw8FVZrtHM5tUJ21O/xW
BWZZkYZK87a+qSUVpYDMmE7QUH8yQpSeM/8KeqUguAUV0bml2SSesgOIrm48yk+y
Xu+xYvxCSF3ilqdJ1A2ZegAhCyaoHFrYguChW6p8kfvPJW2jGVYPGnww3cSjksbM
PU1I+hwJJrX1J72wAe7GIqkwr39H7JDL9DWKlJYEDjE0qkq8d50RHcD9mHaLi/PZ
nlxboxqbQZI90qgRYCuw9HVc2B05Er1QXaOiSDr0JGQliRgu4AFr5W0O2dbcc77H
3gLatbfjSOdiPmUQqcextOqFSOtn74Ckl0sAEtJJTcLMBHj93Sq/cUWwZ2bCiskx
1HY2wfSSyJK/oEr3gGNGLu7nK8AdjvIwUp5ra5O5naqeg2GIKd4FlO3UXaC37e1w
WG5b4gr8yruwPDvK2xN0PJhZgYQdTopeonWPX9skqRPYwy30XF3ef38Zf81rMnN0
JpscfZexWLYCwxTQWzwYZuDsCxqAcDG0mZKIyPnF9yheSSGwlkpk5p6IjjtaP0HJ
YeqmNPoWCty6zGdVtIr2IyTBHg4hO25r7zuP/nEV7o7OHyicfgw=
=Z7sF
-END PGP SIGNATURE End Message ---

Bug#965821: marked as done (setcd: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 11:35:07 +
with message-id 
and subject line Bug#965821: fixed in setcd 1.5-6.1
has caused the Debian Bug report #965821,
regarding setcd: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


-- 
965821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: setcd
Version: 1.5-6
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package setcd uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: setcd
Source-Version: 1.5-6.1
Done: Stephen Kitt 

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated setcd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 09 Feb 2023 13:52:45 +0100
Source: setcd
Architecture: source
Version: 1.5-6.1
Distribution: unstable
Urgency: medium
Maintainer: LENART Janos 
Changed-By: Stephen Kitt 
Closes: 902574 965821 998970
Changes:
 setcd (1.5-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch to debhelper compatibility level 13 with short dh rules,
 enabling all hardening options. Closes: #965821, #998970.
   * Explicitly mark the package as using format “1.0”.
   * Pass dpkg-specified compiler settings to the build. Closes: #902574.
   * Set “Rules-Requires-Root: no”.
   * Clean up whitespace in debian/changelog.
Checksums-Sha1:
 2162b10fe1571fa938e735c5501e1a97c0b4dfd3 1601 setcd_1.5-6.1.dsc
 aabb0904d7ddd02c133fe953a43403e57d1f8a8e 5488 setcd_1.5-6.1.diff.gz
 7c4ad30644e34151d3b9fe52deddd96fd49d3938 6434 setcd_1.5-6.1_source.buildinfo
Checksums-Sha256:
 670ca5bdaae0396f5c4ed7021fb691f85056fd581ae9fba32e2eb191d62b7a8f 1601 
setcd_1.5-6.1.dsc
 67857817d7e6aa0002dd130e4699005aa67842d0a11f190bcd988b61ac27fa45 5488 
setcd_1.5-6.1.diff.gz
 3ae91a2e2f8037b9396d7c7e4a9c7821305ddb3a0028ac5d5a735a09e42cd2b0 6434 
setcd_1.5-6.1_source.buildinfo
Files:
 a62a9f1f6f20af8b4ac5e268d45939bd 1601 utils optional setcd_1.5-6.1.dsc
 e2bbb004e30e6e7a07f964daac6cb695 5488 utils optional setcd_1.5-6.1.diff.gz
 76bf2540638bfb24d8017ff7e25498f6 6434 utils optional 
setcd_1.5-6.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmPk7LcACgkQgNMC9Yht
g5wjFw//W84T1tga74cm06XcX1zdQTtC2rS8QBo9iqYZQ7L6UHwEdEIxV3WIFbgE
Xh7sCeMcfzrL212CgYvjhDcAZ0qD5rPLjoRuYvO9LnOnP26vixgiSE/jF41by6Dx
p9jErKcJypJJwjyKTin2jlK+dUWt2ytcipPN8pAPt9qf1iLikrE0AbU0zlZl5Ea1
er4pFOmfHYlqKyXLd/1NxzAaDywkHrPhZNspDF5uqpx7hjbPIzRGmNT3acMxwzDd
K8HK+zEl9P9S7HlxEcGQ6t75uz9XS59IpLLGWRitUcJ+FoR1yqIE/jaH55V5XV6S
USDobzHfhoHcL2sokth/A5pdtBo8FHcZ0qhs/IExZGItI3TGFyET5aVx7gh3vgUm
8ssrYz+AmJ7Kxh/tRuwbmqE1X7gZt2aikZH2IiW8629m3Tkj+TG9EIIyPVY6SUDo
0RwSAwAf7JeNiPoMuw8uMfv/4fEK49eWM0DMsKtart7A82bi/hfL1ARBFscyJiR6
qaMJu+Yh3ZzHzk4yT8vXlJXn008dy2vjADjcXZT/knAAxrl0LAShYI9uwfc+8e1y
cywU0y7cnxM+6JcD1N4boLbinQluSj6Tje5+xFPIeX7gGWuirfUu

Bug#987275: marked as done (CVE-2021-28305)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 11:23:52 +
with message-id 
and subject line Bug#987275: fixed in rust-diesel 2.0.3-1
has caused the Debian Bug report #987275,
regarding CVE-2021-28305
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.)


-- 
987275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-diesel
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

This was assigned CVE-2021-28305:
https://rustsec.org/advisories/RUSTSEC-2021-0037.html

Cheers,
Moritz  
--- End Message ---
--- Begin Message ---
Source: rust-diesel
Source-Version: 2.0.3-1
Done: Matthias Geiger 

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

Debian distribution maintenance software
pp.
Matthias Geiger  (supplier of updated 
rust-diesel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Feb 2023 12:05:35 +0100
Source: rust-diesel
Architecture: source
Version: 2.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Matthias Geiger 
Closes: 984866 987275
Changes:
 rust-diesel (2.0.3-1) unstable; urgency=medium
 .
   [ Matthias Geiger ]
   * Package diesel 2.0.3 from crates.io using debcargo 2.6.0
   * Collapsed features in debcargo.toml
   * Patched dependencies in Cargo.toml (Closes: #984866, #987275)
   * Added myself to uploaders
   * Updated copyright
   * Added dotenv patch
   * Marked autopkgtest as broken in debcargo.toml
 .
   [ Emanuele Rocca ]
   * Add noop autopkgtest marked as "superficial" to avoid pointless churn on
 CI
Checksums-Sha1:
 ceffdf745e56f050b7aed292e96c9753c1836767 2300 rust-diesel_2.0.3-1.dsc
 b9522daf8a43829297e516986a9535fd2c8eae49 314327 rust-diesel_2.0.3.orig.tar.gz
 64cbd4168ef3cd779ecaff707af0186557c1340f 6252 rust-diesel_2.0.3-1.debian.tar.xz
 6d65985b0ddc200f4e5a1348575958fb7c071a22 8687 
rust-diesel_2.0.3-1_source.buildinfo
Checksums-Sha256:
 7418fc66ccb543b660d49f29b37f6c627d7f35db5cb724e87605f93da372 2300 
rust-diesel_2.0.3-1.dsc
 4391a22b19c916e50bec4d6140f29bdda3e3bb187223fe6e3ea0b6e4d1021c04 314327 
rust-diesel_2.0.3.orig.tar.gz
 51e52a8ee4ee7af652cb977e267b8b1b8cca56dcd29ffdcf120c839311591d6b 6252 
rust-diesel_2.0.3-1.debian.tar.xz
 d57ed6cb96d2b1443eb744f00349aa67647431451422bb359135284fc4938258 8687 
rust-diesel_2.0.3-1_source.buildinfo
Files:
 2fbc03db2a8b8a25b009df799690264e 2300 rust optional rust-diesel_2.0.3-1.dsc
 a6458921e3b216b819bda983046c4d40 314327 rust optional 
rust-diesel_2.0.3.orig.tar.gz
 7ae959a9bcc49bb706962cc9c24d364f 6252 rust optional 
rust-diesel_2.0.3-1.debian.tar.xz
 dd749ffe341b30195b977ea82768 8687 rust optional 
rust-diesel_2.0.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAmPmJQEACgkQ1QhaB1D9
t6PIuw//RZHA+orFW1DFE1VPYCCHz+okoaNqfhwcghtjC9H+E9nxK5hNsWRwyjuO
E1M3QCeeRY57nhZqxHNkzouPuAu3gnqjaFc4ruCbGtKMq/+kkUXbmp3Z474ko9p+
tgaK6QlWJFcWYlgBqtP3cNDeW20Q35SoMl4SVEVHkeShoM7YdOlSTTPxDn5HUksR
27h4sxv/sQEDVyif91KnPOInvX0DKOLabXZo8V/GzTa2QVxVdt0ZYQ3Pe6JVTMb8
WGfi+4xjyKFDdc4HrenQyxfXevXx4ti/ljajOvZINLnxmS+Xibx1flNOfHOSL+nt
WQFo11dTPqfWn/bqo6jKyuy2zY4zrWNhzEuQBzmZ0IjkhQqeR3H6VvF7PjeT1sNa
nnz0ms/BcNL1vlLC1uWDAAVji9b5QaVpk2O/ucz09JOcO3EOpnDiM0UNlQdWHYyb
UVOTzr7u4AZgjVsdj0BuwBcDLZRxYf0vqOwG4lexqDkO1WrGo6yAJX/Cin52PBEg
H/VoAexrL5Otgl+7V1Lu72XC0effmhLd+nSSDOrDH1KKjl7ed+puExetqYE95hHt
6MH/yXqy7N+JVxbd+k9lVp+4ltTm/8vkoKrwSYvkplXmtxLpmKZVEcsxgI2JSAd2
VvNm+PqMjjAFiuBTaY17vTcdz5PogQUAMJIGtH6Ngd73vtRUK6w=
=k5XS
-END PGP SIGNATURE End Message ---

Bug#984866: marked as done (rust-diesel: depends on multiple unavailable packages)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 11:23:52 +
with message-id 
and subject line Bug#984866: fixed in rust-diesel 2.0.3-1
has caused the Debian Bug report #984866,
regarding rust-diesel: depends on multiple unavailable packages
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.)


-- 
984866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-diesel
Version: 1.4.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + librust-diesel+extras-dev librust-diesel+ipnetwork-dev 
librust-diesel+quickcheck-dev librust-diesel+r2d2-dev librust-diesel+uuid-dev

Hi,

the binary packages built from src:rust-diesel depend on several no
longer available packages, e.g.

The following packages have unmet dependencies:
 librust-diesel+extras-dev : Depends: librust-diesel+network-address-dev (= 
1.4.4-2) but it is not going to be installed
 Depends: librust-r2d2-0.8+default-dev but it is 
not installable
 Depends: librust-uuid-0.6+default-dev but it is 
not installable or
  librust-uuid-0.5+default-dev but it is 
not installable or
  librust-uuid-0.4+default-dev but it is 
not installable or
  librust-uuid-0.3+default-dev but it is 
not installable or
  librust-uuid-0.2+default-dev but it is 
not installable
 Depends: librust-uuid-0.6+use-std-dev but it is 
not installable or
  librust-uuid-0.5+use-std-dev but it is 
not installable or
  librust-uuid-0.4+use-std-dev but it is 
not installable or
  librust-uuid-0.3+use-std-dev but it is 
not installable or
  librust-uuid-0.2+use-std-dev but it is 
not installable


Andreas
--- End Message ---
--- Begin Message ---
Source: rust-diesel
Source-Version: 2.0.3-1
Done: Matthias Geiger 

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

Debian distribution maintenance software
pp.
Matthias Geiger  (supplier of updated 
rust-diesel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Feb 2023 12:05:35 +0100
Source: rust-diesel
Architecture: source
Version: 2.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Matthias Geiger 
Closes: 984866 987275
Changes:
 rust-diesel (2.0.3-1) unstable; urgency=medium
 .
   [ Matthias Geiger ]
   * Package diesel 2.0.3 from crates.io using debcargo 2.6.0
   * Collapsed features in debcargo.toml
   * Patched dependencies in Cargo.toml (Closes: #984866, #987275)
   * Added myself to uploaders
   * Updated copyright
   * Added dotenv patch
   * Marked autopkgtest as broken in debcargo.toml
 .
   [ Emanuele Rocca ]
   * Add noop autopkgtest marked as "superficial" to avoid pointless churn on
 CI
Checksums-Sha1:
 ceffdf745e56f050b7aed292e96c9753c1836767 2300 rust-diesel_2.0.3-1.dsc
 b9522daf8a43829297e516986a9535fd2c8eae49 314327 rust-diesel_2.0.3.orig.tar.gz
 64cbd4168ef3cd779ecaff707af0186557c1340f 6252 rust-diesel_2.0.3-1.debian.tar.xz
 6d65985b0ddc200f4e5a1348575958fb7c071a22 8687 
rust-diesel_2.0.3-1_source.buildinfo
Checksums-Sha256:
 7418fc66ccb543b660d49f29b37f6c627d7f35db5cb724e87605f93da372 2300 
rust-diesel_2.0.3-1.dsc
 4391a22b19c916e50bec4d6140f29bdda3e3bb187223fe6e3ea0b6e4d1021c04 314327 
rust-diesel_2.0.3.orig.tar.gz
 51e52a8ee4ee7af652cb977e267b8b1b8cca56dcd29ffdcf120c839311591d6b 6252 
rust-diesel_2.0.3-1.debian.tar.xz
 d57ed6cb96d2b1443eb744f00349aa67647431451422bb359135284fc4938258 8687 
rust-diesel_2.0.3-1_source.buildinfo
Files:
 2fbc03db2a8b8a25b009df799690264e 2300 rust optional rust-diesel_2.0.3-1.dsc
 a6458921e3b216b819bda983046c4d40 314327 rust optional 
rust-diesel_2.0.3.orig.tar.gz
 7ae959a9bcc49bb706962cc

Bug#1011656: marked as done (flexbar ftbfs: cannot find tbb header)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 11:05:01 +
with message-id 
and subject line Bug#1011656: fixed in flexbar 1:3.5.0-5
has caused the Debian Bug report #1011656,
regarding flexbar ftbfs: cannot find tbb header
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.)


-- 
1011656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flexbar
Version: 1:3.5.0-4
Severity: important

tbb -> onetbb transition breaks this package.
--- End Message ---
--- Begin Message ---
Source: flexbar
Source-Version: 1:3.5.0-5
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated flexbar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Feb 2023 11:37:36 +0100
Source: flexbar
Architecture: source
Version: 1:3.5.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1008220 1011656
Changes:
 flexbar (1:3.5.0-5) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Set upstream metadata fields: Archive.
   * Port to onetbb (thanks to Liam Keegan - see
  https://github.com/seqan/flexbar/pull/41/)
 Closes: #1008220, #1011656
   * Fix watch file
 .
   [ Étienne Mollier ]
   * onetbb.patch: port Paired* classes.
 .
   [ Andreas Tille ]
   * Standards-Version: 4.6.2 (routine-update)
Checksums-Sha1:
 a311f9f153c203285844bdc938c6947db7e48902 2041 flexbar_3.5.0-5.dsc
 045efb9ac3a789f7903dd592234959f5c8865508 11436 flexbar_3.5.0-5.debian.tar.xz
 f2811b38b68d53488e0eac14c9a1b32d4ed6768a 7230 flexbar_3.5.0-5_amd64.buildinfo
Checksums-Sha256:
 0293c3297a5774aea6fd28d67dd63f06f32fe72c6139bc31a00e0314500ef736 2041 
flexbar_3.5.0-5.dsc
 b718a9bf496bfead917292eee67d085beb2864b750374794f34ff28bcb6e9795 11436 
flexbar_3.5.0-5.debian.tar.xz
 2dab36d734a1784ea8346dcf1b98809197cd94c8bc43316cb6cc172deec1 7230 
flexbar_3.5.0-5_amd64.buildinfo
Files:
 51f5ac6d6a17cd8880a108d379110ed4 2041 science optional flexbar_3.5.0-5.dsc
 e818565eaed0b2c567aeb296816f803c 11436 science optional 
flexbar_3.5.0-5.debian.tar.xz
 59266ab0121b123c33a8b6e63665cdf2 7230 science optional 
flexbar_3.5.0-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPmH8QRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGk/w/9H5jKSz0LrCgTh7p5Md0bQovncajQuixw
z2SGGufeQPZspTjOfFuEy+5ZCjcGPBXAED3iU+f0qe/yTArH2LPZH5blqwXWqVnf
uIpQPleAe9Uacxa8d2Ybp22XuprsWZx/TWPP2uWMaAIhNrwZb1Po7DlXJ9vmJH82
B8RWEpZ47zaZsuogf97vUORggsuTn0tJobSnlhDwJB4+kcxfKDdCgUHOTIGDo9Pt
Osb7JZ2J4lercTmJcnH1CA+/FzUtkLKr78AGfQYS+R8A7HLbtDe7R6rFFOrYCMsC
v+9VuPNJiYiGRZAh2JRS013GoyHUWZF8feCP53cJTjEF9HfCv6mYR5BEKpf9nlcY
62B9bOMknhCzQ5gTNSM3m3EF3K0i9jZ4BHFMWl7DhX3758SRiCNFqcD++fLnx2U8
YCQ8uNcWsulUTwqo7LZgMb41tGmRVWTVBZU7cDBGUlKSopk+XJepX2M+Z2zb8L+R
NYGyCRT7xyAIQ6TMmKH9Myl8NLITF1g+e9MwWNjuMcw1MqvIBBmHtSxSOg8ck0Yo
BcujVLP4kZXdFczmr6dbltYd0F7+HPh6faaPUe4Fm8l3Ro3xy+8NAO5S0+sKyJOO
Ajsck997sDSFZXpXp43d9ISfiVAOt9HfN3+pRngxAKVo8NE91WBaHNutS97x21DP
Wmb1aJ1VYyk=
=9803
-END PGP SIGNATURE End Message ---

Bug#1012127: marked as done (flexbar: FTBFS with onetbb/2021.5.0-8 in experimental)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 11:05:01 +
with message-id 
and subject line Bug#1008220: fixed in flexbar 1:3.5.0-5
has caused the Debian Bug report #1008220,
regarding flexbar: FTBFS with onetbb/2021.5.0-8 in experimental
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.)


-- 
1008220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flexbar
Version: 1:3.5.0-4
Severity: normal
Tags: ftbfs

Hello,

tbb/onetbb transition (#1007222) is currently in the planning. During
test rebuild of libtbb-dev reverse dependencies with onetbb/2021.5.0-8
in experimental, current source failed to build with the following:

[ 50%] Building CXX object src/CMakeFiles/flexbar.dir/Flexbar.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++
-DSEQAN_HAS_BZIP2=1 -DSEQAN_HAS_ZLIB=1 -I/<>/include -g -O2
-ffile-prefix-ma
p=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -MD
-MT src/CMakeFiles/flexb
ar.dir/Flexbar.cpp.o -MF CMakeFiles/flexbar.dir/Flexbar.cpp.o.d -o
CMakeFiles/flexbar.dir/Flexbar.cpp.o -c /<>/src/Flexbar.cpp
In file included from /<>/src/Flexbar.cpp:24:
/<>/src/Flexbar.h:15:10: fatal error: tbb/pipeline.h: No
such file or directory
   15 | #include 
  |  ^~~~
compilation terminated.

Andrius
--- End Message ---
--- Begin Message ---
Source: flexbar
Source-Version: 1:3.5.0-5
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated flexbar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Feb 2023 11:37:36 +0100
Source: flexbar
Architecture: source
Version: 1:3.5.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1008220 1011656
Changes:
 flexbar (1:3.5.0-5) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Set upstream metadata fields: Archive.
   * Port to onetbb (thanks to Liam Keegan - see
  https://github.com/seqan/flexbar/pull/41/)
 Closes: #1008220, #1011656
   * Fix watch file
 .
   [ Étienne Mollier ]
   * onetbb.patch: port Paired* classes.
 .
   [ Andreas Tille ]
   * Standards-Version: 4.6.2 (routine-update)
Checksums-Sha1:
 a311f9f153c203285844bdc938c6947db7e48902 2041 flexbar_3.5.0-5.dsc
 045efb9ac3a789f7903dd592234959f5c8865508 11436 flexbar_3.5.0-5.debian.tar.xz
 f2811b38b68d53488e0eac14c9a1b32d4ed6768a 7230 flexbar_3.5.0-5_amd64.buildinfo
Checksums-Sha256:
 0293c3297a5774aea6fd28d67dd63f06f32fe72c6139bc31a00e0314500ef736 2041 
flexbar_3.5.0-5.dsc
 b718a9bf496bfead917292eee67d085beb2864b750374794f34ff28bcb6e9795 11436 
flexbar_3.5.0-5.debian.tar.xz
 2dab36d734a1784ea8346dcf1b98809197cd94c8bc43316cb6cc172deec1 7230 
flexbar_3.5.0-5_amd64.buildinfo
Files:
 51f5ac6d6a17cd8880a108d379110ed4 2041 science optional flexbar_3.5.0-5.dsc
 e818565eaed0b2c567aeb296816f803c 11436 science optional 
flexbar_3.5.0-5.debian.tar.xz
 59266ab0121b123c33a8b6e63665cdf2 7230 science optional 
flexbar_3.5.0-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPmH8QRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGk/w/9H5jKSz0LrCgTh7p5Md0bQovncajQuixw
z2SGGufeQPZspTjOfFuEy+5ZCjcGPBXAED3iU+f0qe/yTArH2LPZH5blqwXWqVnf
uIpQPleAe9Uacxa8d2Ybp22XuprsWZx/TWPP2uWMaAIhNrwZb1Po7DlXJ9vmJH82
B8RWEpZ47zaZsuogf97vUORggsuTn0tJobSnlhDwJB4+kcxfKDdCgUHOTIGDo9Pt
Osb7JZ2J4lercTmJcnH1CA+/FzUtkLKr78AGfQYS+R8A7HLbtDe7R6rFFOrYCMsC
v+9VuPNJiYiGRZAh2JRS013GoyHUWZF8feCP53cJTjEF9HfCv6mYR5BEKpf9nlcY
62B9bOMknhCzQ5gTNSM3m3EF3K0i9jZ4BHFMWl7DhX3758SRiCNFqcD++fLnx2U8
YCQ8uNcWsulUTwqo7LZgMb41tGmRVWTVBZU7cDBGUlKSopk+XJepX2M+Z2zb8L+R
NYGyCRT7xyAIQ6TMmKH9Myl8NLITF1g+e9MwWNjuMcw1MqvIBBmHtSxSOg8ck0Yo
BcujVLP4kZXdFczmr6dbltYd0F7+HPh6faaPUe4Fm8l3Ro3xy+8NAO5S0+sKyJOO
Ajsck997sDSFZXpXp43d9ISfiVAOt9HfN3+pRngxAKVo8NE91WBaHNutS97x21DP
Wmb1aJ1VYyk=
=9803
-END PGP SIGNATURE End Message ---

Bug#1008220: marked as done (flexbar 3.5.0-4 FTBFS against libtbb-dev 2021.5.0-7)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 11:05:01 +
with message-id 
and subject line Bug#1008220: fixed in flexbar 1:3.5.0-5
has caused the Debian Bug report #1008220,
regarding flexbar 3.5.0-4 FTBFS against libtbb-dev 2021.5.0-7
to be marked as done.

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

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


-- 
1008220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flexbar
Version: 3.5.0-4
Severity: important

Dear maintainer,

There is a major API change from tbb to onetbb, please refer
https://oneapi-src.github.io/oneTBB/main/tbb_userguide/Migration_Guide.html
for more details.

make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 50%] Building CXX object src/CMakeFiles/flexbar.dir/Flexbar.cpp.o 
   
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DSEQAN_HAS_BZIP2=1 -DSEQAN_HAS_ZLIB=1 -
I/<>/include -g -O2 -ffile-pre
fix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -
std=c++14 -MD -MT src/CMak
eFiles/flexbar.dir/Flexbar.cpp.o -MF CMakeFiles/flexbar.dir/Flexbar.cpp.o.d -o 
CMakeFiles/flexbar.dir/Flexbar.cpp.o -c
/<>/src/Flex
bar.cpp 
   
In file included from /<>/src/Flexbar.cpp:24:
/<>/src/Flexbar.h:15:10: fatal error: tbb/pipeline.h: No such file 
or directory
   15 | #include 
  |  ^~~~   
compilation terminated. 
make[3]: *** [src/CMakeFiles/flexbar.dir/build.make:79: 
src/CMakeFiles/flexbar.dir/Flexbar.cpp.o] Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'  
 
--- End Message ---
--- Begin Message ---
Source: flexbar
Source-Version: 1:3.5.0-5
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated flexbar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Feb 2023 11:37:36 +0100
Source: flexbar
Architecture: source
Version: 1:3.5.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1008220 1011656
Changes:
 flexbar (1:3.5.0-5) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Set upstream metadata fields: Archive.
   * Port to onetbb (thanks to Liam Keegan - see
  https://github.com/seqan/flexbar/pull/41/)
 Closes: #1008220, #1011656
   * Fix watch file
 .
   [ Étienne Mollier ]
   * onetbb.patch: port Paired* classes.
 .
   [ Andreas Tille ]
   * Standards-Version: 4.6.2 (routine-update)
Checksums-Sha1:
 a311f9f153c203285844bdc938c6947db7e48902 2041 flexbar_3.5.0-5.dsc
 045efb9ac3a789f7903dd592234959f5c8865508 11436 flexbar_3.5.0-5.debian.tar.xz
 f2811b38b68d53488e0eac14c9a1b32d4ed6768a 7230 flexbar_3.5.0-5_amd64.buildinfo
Checksums-Sha256:
 0293c3297a5774aea6fd28d67dd63f06f32fe72c6139bc31a00e0314500ef736 2041 
flexbar_3.5.0-5.dsc
 b718a9bf496bfead917292eee67d085beb2864b750374794f34ff28bcb6e9795 11436 
flexbar_3.5.0-5.debian.tar.xz
 2dab36d734a1784ea8346dcf1b98809197cd94c8bc43316cb6cc172deec1 7230 
flexbar_3.5.0-5_amd64.buildinfo
Files:
 51f5ac6d6a17cd8880a108d379110ed4 2041 science optional flexbar_3.5.0-5.dsc
 e818565eaed0b2c567aeb296816f803c 11436 science optional 
flexbar_3.5.0-5.debian.tar.xz
 59266ab0121b123c33a8b6e63665cdf2 7230 science optional 
flexbar_3.5.0-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPmH8QRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGk/w/9H5jKSz0LrCgTh7p5Md0bQovncajQuixw
z2SGGufeQPZspTjOfFuEy+5ZCjcGPBXAED3iU+f0qe/yTArH2LPZH5blqwXWqVnf
uIpQPleAe9Uacxa8d2Ybp22XuprsWZx/TWPP2uWMaAIhNrwZb1Po7DlXJ9vmJH82
B8RWEpZ47zaZsuogf97vUORggsuTn0tJobSnlhDwJB4+kcxfKDdCgUHOTIGDo9Pt
Osb7JZ2J4lercTmJcnH1CA+/FzUtkLKr78AGfQYS+R8A7HLbtDe7R6rFFOrYCMsC
v+9VuPNJiYiGRZAh2JRS013GoyHUWZF8feCP53cJTjEF9HfCv6mYR5BEKpf9nlcY
62B9bOMknhCzQ5gTNSM3m3EF3K0i9jZ4BHFMWl

Bug#1007000: marked as done (thin FTBFS on IPV6-only buildds)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 11:05:36 +
with message-id 
and subject line Bug#1007000: fixed in thin 1.8.1-2
has caused the Debian Bug report #1007000,
regarding thin FTBFS on IPV6-only buildds
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=thin&arch=amd64&ver=1.8.0-1%2Bb2&stamp=1646907946&raw=0

...
Thin::Server robustness
#>/spec/spec_helper.rb:191 run> 
terminated with exception (report_on_exception is true):
/usr/lib/ruby/vendor_ruby/eventmachine.rb:532:in `start_tcp_server': no 
acceptor (port is in use or requires root privileges) (RuntimeError)
from /usr/lib/ruby/vendor_ruby/eventmachine.rb:532:in `start_server'
from /<>/lib/thin/backends/tcp_server.rb:16:in `connect'
from /<>/lib/thin/backends/base.rb:65:in `block in start'
from /usr/lib/ruby/vendor_ruby/eventmachine.rb:196:in `run_machine'
from /usr/lib/ruby/vendor_ruby/eventmachine.rb:196:in `run'
from /<>/lib/thin/backends/base.rb:75:in `start'
from /<>/lib/thin/server.rb:162:in `start'
from /<>/spec/spec_helper.rb:191:in `block in start_server'
E: Build killed with signal TERM after 150 minutes of inactivity
--- End Message ---
--- Begin Message ---
Source: thin
Source-Version: 1.8.1-2
Done: Lucas Kanashiro 

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

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated thin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Feb 2023 07:27:48 -0300
Source: thin
Architecture: source
Version: 1.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Lucas Kanashiro 
Closes: 1007000
Changes:
 thin (1.8.1-2) unstable; urgency=medium
 .
   * Team upload.
   * d/ruby-tests.rake: fix how IPv6 only builders are identified
 (Closes: #1007000).
Checksums-Sha1:
 ad4d148a24a4c200cc3a6284e790a15ca34d7f20 2087 thin_1.8.1-2.dsc
 5726fd52d933ac9b2c9cadee5845e19945220623 8792 thin_1.8.1-2.debian.tar.xz
Checksums-Sha256:
 f686f42d18f20ac650721b914dcd219473ad2b3c66ce5ad67ac4dc0c7bf48201 2087 
thin_1.8.1-2.dsc
 8575ef0859d65f638f7415a1dcc0e792bcf6876b1542b9d1ddc872f862ab2b57 8792 
thin_1.8.1-2.debian.tar.xz
Files:
 1ccf260694825721cc277d2e410d036b 2087 ruby optional thin_1.8.1-2.dsc
 78daffd93bcd85a1d902d6e72fe95cc6 8792 ruby optional thin_1.8.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAmPmH1kVHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8Vf4P/1KWp6n1NeWgmZsHrjU/MycTSAfR
4OVnUL6TZOLiZn0AhA4lDgy9sSBwF0yKEXBqZSkGRGL/guz9xUUwYN6+XvHQKY8w
HBF0m5u4lcQqWF1VAzAZwDvqpcDpXphAxvfLHBsh1MnXwf0mHJo7jSNa8/pmYRsB
P9ghEFn7BOr7F76osRWF+UQl3PLVZkDg3K1HWObINWNZb4UW8p2ZIULPrnX4zgyo
BWuNLMaBNMloPDOgA7p+QNfSX4DVXBNFMFAC88TBAvLcKwjqkK2ysMKVhXikP4Al
UbS/ggv2mrJxUf6+8IYdWHj3i08YYNBZrT1si4SPwrlFYiA6uV7m4UANRXGI7xdE
6Spf+j+RaeNSfOvWfRnqxw4sYtuFadekBhToKjLLhmqdIosFfuxq+50U+K5Hn2Aq
JQSKnZX7Ihl5HO/hd5PeBI/2Fr4t8uPqkS4XshMEedU/IqOLUuVGeXIO86oP0S0w
k2mci1c+ctcz3X0BngjVorV0B+3OvO/QJUCieK0yUq5m8lpLQ2jlRvu1QucI3ij2
ZRrMEDeLLTwPgSLuGcefjuv1YXsNDmideFXknb3pPB68wds9oE7jNa5KUwuZMVeq
ihPOLnHYRrR7mJ5Rlp16vXNO3xOIr2cCpPzTmkY2UgNvx126eKxhWaSTEsjVYqft
n+6MUb2wpOjOfpCH
=IA6x
-END PGP SIGNATURE End Message ---

Bug#1030982: gscan2pdf: Segmentation fault

[Jeff]

There's no segfault there.

Please start gscan2pdf from the command line with the --log=log
option, if necessary, hit OK to select the crashed session, reproduce 
the problem (i.e. the segfaul), quit, and post the log file, which

gscan2pdf may have compressed with xz.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012890: android-platform-frameworks-base: ftbfs with GCC-12

[Jochen Sprickerhof]

* Roger Shimizu  [2023-02-09 13:42]:

Please try the version in experimental.
and also refer the version info of this ticket:

Found in versions android-platform-frameworks-base/1:10.0.0+r36-5,
android-platform-frameworks-base/13~beta3-1~exp1
Fixed in version android-platform-frameworks-base/1:10.0.0+r36-6


Oups, sorry. The attached patch against android-platform-tools fixes the 
issue for me.


Cheers Jochen
From: Jochen Sprickerhof 
Date: Fri, 10 Feb 2023 11:46:23 +0100
Subject: Implement const_iterator::operator--

Needed for
android-platform-frameworks-base/libs/androidfw/LoadedArsc.cpp
when compiling against libstdc++.
---
 .../incremental_delivery/incfs/util/include/util/map_ptr.h   | 12 
 1 file changed, 12 insertions(+)

diff --git a/system/incremental_delivery/incfs/util/include/util/map_ptr.h b/system/incremental_delivery/incfs/util/include/util/map_ptr.h
index 304540f..836b320 100644
--- a/system/incremental_delivery/incfs/util/include/util/map_ptr.h
+++ b/system/incremental_delivery/incfs/util/include/util/map_ptr.h
@@ -180,6 +180,11 @@ public:
 return *this;
 }
 
+const const_iterator& operator--() {
+safe_ptr_--;
+return *this;
+}
+
 const_iterator& operator+=(int n) {
 safe_ptr_ = safe_ptr_ + n;
 return *this;
@@ -321,6 +326,13 @@ public:
 return temp;
 }
 
+template  = 0>
+const map_ptr& operator--() {
+LIBINCFS_MAP_PTR_DEBUG_CODE(verified_ = false);
+--ptr_;
+return *this;
+}
+
 template  = 0>
 map_ptr operator+(const S n) const {
 return map_ptr(map_, ptr_ + n, verified_block_);


signature.asc
Description: PGP signature

Processed: affects 1019927

[Debian Bug Tracking System]

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

> affects 1019927 + ruby-tilt nanoc ruby-jekyll-coffeescript ruby-js-routes 
> ruby-client-side-validations ruby-sprockets
Bug #1019927 [ruby-coffee-script] Remove ruby-coffee-script - deprecated 
upstream
Added indication that 1019927 affects ruby-tilt, nanoc, 
ruby-jekyll-coffeescript, ruby-js-routes, ruby-client-side-validations, and 
ruby-sprockets
> thanks
Stopping processing here.

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

Bug#1030884: Chain of Dependencies prevents closing RC bugs

[Andreas Tille]

Hi,

to fix

  #1030884 python-cogent: FTBFS (ImportError: cannot import name 'float' from 
'numpy')

and let it migrate to testing it needs to wait for

  #950598 python3-jupyter-sphinx: package relies on unavailable 
`ipywidgets.embed` module

which in turn needs

  #896460 Please package ipywidgets 7

which needs another not yet packaged precondition.

Since I do not think that #896460 will be closed any time soon the only
realistic solution to let python-cogent migrate will probably be to make
it independent from python3-jupyter-sphinx by skipping features in its
docs or simply do not generate the doc at all as long as its
precondition will not be in testing.

Do you think that's correct?

Kind regards
   Andreas.

-- 
http://fam-tille.de

Processed: notfound 1013526 in 0.12-1

[Debian Bug Tracking System]

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

> notfound 1013526 0.12-1
Bug #1013526 {Done: Adrian Bunk } 
[src:libtickit-widget-scrollbox-perl] libtickit-widget-scrollbox-perl: 
intermittent memory corruption in t/02input-key.t and t/03input-mouse.t
No longer marked as found in versions libtickit-widget-scrollbox-perl/0.12-1.
> thanks
Stopping processing here.

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

Processed: closing 1013526

[Debian Bug Tracking System]

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

> close 1013526 0.12-1
Bug #1013526 [src:libtickit-widget-scrollbox-perl] 
libtickit-widget-scrollbox-perl: intermittent memory corruption in 
t/02input-key.t and t/03input-mouse.t
Marked as fixed in versions libtickit-widget-scrollbox-perl/0.12-1.
Bug #1013526 [src:libtickit-widget-scrollbox-perl] 
libtickit-widget-scrollbox-perl: intermittent memory corruption in 
t/02input-key.t and t/03input-mouse.t
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1031001: rust-av1-grain: autopkgtest failure

[Adrian Bunk]

Source: rust-av1-grain
Version: 0.2.2-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-av1-grain/31208263/log.gz

...
error[E0433]: failed to resolve: use of undeclared crate or module `v_frame`
 --> src/util.rs:3:5
  |
3 | use v_frame::{
  | ^^^ use of undeclared crate or module `v_frame`

error[E0432]: unresolved import `v_frame`
  --> src/lib.rs:70:9
   |
70 | pub use v_frame;
   | ^^^ no external crate `v_frame`

warning: unused imports: `borrow::Cow`, `mem::size_of`
 --> src/util.rs:1:11
  |
1 | use std::{borrow::Cow, mem::size_of};
  |   ^^^  
  |
  = note: `#[warn(unused_imports)]` on by default

Some errors have detailed explanations: E0432, E0433.
For more information about an error, try `rustc --explain E0432`.
warning: `av1-grain` (lib test) generated 1 warning
error: could not compile `av1-grain` due to 2 previous errors; 1 warning emitted

Caused by:
  process didn't exit successfully: `CARGO=/usr/bin/cargo 
CARGO_CRATE_NAME=av1_grain 
CARGO_MANIFEST_DIR=/usr/share/cargo/registry/av1-grain-0.2.2 
CARGO_PKG_AUTHORS='' CARGO_PKG_DESCRIPTION='Helpers for generating and parsing 
AV1 film grain data' CARGO_PKG_HOMEPAGE='https://github.com/rust-av/av1-grain' 
CARGO_PKG_LICENSE=BSD-2-Clause CARGO_PKG_LICENSE_FILE='' 
CARGO_PKG_NAME=av1-grain 
CARGO_PKG_REPOSITORY='https://github.com/rust-av/av1-grain' 
CARGO_PKG_RUST_VERSION=1.59.0 CARGO_PKG_VERSION=0.2.2 CARGO_PKG_VERSION_MAJOR=0 
CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=2 CARGO_PKG_VERSION_PRE='' 
CARGO_PRIMARY_PACKAGE=1 
LD_LIBRARY_PATH='/tmp/tmp.I1hay3bCHX/target/debug/deps:/usr/lib' rustc 
--crate-name av1_grain --edition=2021 src/lib.rs --error-format=json 
--json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link 
-C embed-bitcode=no -C debuginfo=2 --test --cfg 'feature="create"' -C 
metadata=7fb829ca8e38f919 -C extra-filename=-7fb829ca8e38f919 --out-dir 
/tmp/tmp.I1hay3bCHX/target/x86_64-unknown-linux-gnu/debug/deps --target 
x86_64-unknown-linux-gnu -C 
incremental=/tmp/tmp.I1hay3bCHX/target/x86_64-unknown-linux-gnu/debug/incremental
 -L dependency=/tmp/tmp.I1hay3bCHX/target/x86_64-unknown-linux-gnu/debug/deps 
-L dependency=/tmp/tmp.I1hay3bCHX/target/debug/deps --extern 
anyhow=/tmp/tmp.I1hay3bCHX/target/x86_64-unknown-linux-gnu/debug/deps/libanyhow-dca53b228d794c68.rlib
 --extern 
arrayvec=/tmp/tmp.I1hay3bCHX/target/x86_64-unknown-linux-gnu/debug/deps/libarrayvec-9490589bc30e05be.rlib
 --extern 
log=/tmp/tmp.I1hay3bCHX/target/x86_64-unknown-linux-gnu/debug/deps/liblog-fe7d61fb0ecee855.rlib
 --extern 
quickcheck=/tmp/tmp.I1hay3bCHX/target/x86_64-unknown-linux-gnu/debug/deps/libquickcheck-2c1f5f0a8cf66006.rlib
 --extern 
quickcheck_macros=/tmp/tmp.I1hay3bCHX/target/debug/deps/libquickcheck_macros-1550f17b9249df2e.so
 -C debuginfo=2 --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C 
link-arg=-Wl,-z,relro --remap-path-prefix 
/usr/share/cargo/registry/av1-grain-0.2.2=/usr/share/cargo/registry/av1-grain-0.2.2
 --remap-path-prefix /tmp/tmp.I1hay3bCHX/registry=/usr/share/cargo/registry` 
(exit status: 1)
autopkgtest [09:39:31]: test librust-av1-grain-dev:create: 
---]
autopkgtest [09:39:31]: test librust-av1-grain-dev:create:  - - - - - - - - - - 
results - - - - - - - - - -
librust-av1-grain-dev:create FAIL non-zero exit status 101
...
autopkgtest [09:41:33]:  summary
rust-av1-grain:@ PASS
librust-av1-grain-dev:create FAIL non-zero exit status 101
librust-av1-grain-dev:default PASS
librust-av1-grain-dev:diff PASS
librust-av1-grain-dev:estimate PASS
librust-av1-grain-dev:itertools FAIL non-zero exit status 101
librust-av1-grain-dev:nom FAIL non-zero exit status 101
librust-av1-grain-dev:num-rational FAIL non-zero exit status 101
librust-av1-grain-dev:parse FAIL non-zero exit status 101
librust-av1-grain-dev:serde FAIL non-zero exit status 101
librust-av1-grain-dev:serialize FAIL non-zero exit status 101
librust-av1-grain-dev:unstable FAIL non-zero exit status 101
librust-av1-grain-dev:v_frame PASS
librust-av1-grain-dev: FAIL non-zero exit status 101

Bug#1030813: marked as done (mumble: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 09:50:01 +
with message-id 
and subject line Bug#1030813: fixed in mumble 1.3.4-4
has caused the Debian Bug report #1030813,
regarding mumble: autopkgtest regression
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.)


-- 
1030813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mumble
Version: 1.3.4-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mumble/31139421/log.gz

...
autopkgtest [09:23:28]: test command1: smoke
autopkgtest [09:23:28]: test command1: [---
bash: line 1: smoke: command not found
autopkgtest [09:23:29]: test command1: ---]
autopkgtest [09:23:29]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 127
--- End Message ---
--- Begin Message ---
Source: mumble
Source-Version: 1.3.4-4
Done: Christopher Knadle 

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

Debian distribution maintenance software
pp.
Christopher Knadle  (supplier of updated mumble 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Feb 2023 04:00:49 -0500
Source: mumble
Architecture: source
Version: 1.3.4-4
Distribution: unstable
Urgency: medium
Maintainer: Christopher Knadle 
Changed-By: Christopher Knadle 
Closes: 1030813
Changes:
 mumble (1.3.4-4) unstable; urgency=medium
 .
   * debian/copyright:
 - Remove line 88 duplicate globbing pattern 3rdparty/speex-src/*
   * debian/tests/control
 - Explicitly list mumble and mumble-server packages to help understanding
   * debian/tests/smoke
 - Disable execution of mumble binary due to Qt error of
   "could not find display" causing test to fail and package regression
   (Closes: #1030813)
Checksums-Sha1:
 1620061a2e2f887deafa6a0803837f702c00c8d9 2528 mumble_1.3.4-4.dsc
 5d981571cff562ea234bbd34b24d35b9e5fd47b3 8592741 mumble_1.3.4.orig.tar.gz
 8cc9919339bb706174b97f676c76d9e3b815d072 721 mumble_1.3.4.orig.tar.gz.asc
 27c6ada749dbda8f2d6d6298d8db8a0487cab044 42544 mumble_1.3.4-4.debian.tar.xz
 c0a861984eb45bc8b0aa2ea364cbeb51e85f8956 5730 mumble_1.3.4-4_source.buildinfo
Checksums-Sha256:
 1ef9be3e490045682a91f25815540e91287013f5d5bec8f5b29ec373ae55f167 2528 
mumble_1.3.4-4.dsc
 615f4ebfc3385d945163f369efd3e910c8b6d0f025797a7eed541515fccb6093 8592741 
mumble_1.3.4.orig.tar.gz
 effd462191f4be3ddff9c1235b8a3817a5ef15ae0a7518d6193ec8e146209b98 721 
mumble_1.3.4.orig.tar.gz.asc
 227ec95512214f903d94522000678d135e7500f1d75c0d46fb7610bc517226cf 42544 
mumble_1.3.4-4.debian.tar.xz
 8f458afd7759d402df6b3969babb4c63ac0dae6e95bd90c8b43d7756e6673663 5730 
mumble_1.3.4-4_source.buildinfo
Files:
 438079982cfa8f04c00e0d68263c0ad4 2528 sound optional mumble_1.3.4-4.dsc
 d41ece1a4cefadfc1d04a16863514f98 8592741 sound optional 
mumble_1.3.4.orig.tar.gz
 0e212c95f8b1c24d671908f39ab27265 721 sound optional 
mumble_1.3.4.orig.tar.gz.asc
 957819651771e7ec6b4b51bb3c789c13 42544 sound optional 
mumble_1.3.4-4.debian.tar.xz
 2c4ec760fba2de6f33a0326000294229 5730 sound optional 
mumble_1.3.4-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEe1KzyGmRW/4DhtV6ieLKD9m6RHAFAmPmDHoACgkQieLKD9m6
RHDSTw//bLdyFrDOoilLarE3EHkjbidEKTOddMv+1VTGbvVMMeU6XvaBQEiCWZS8
Qoix6OcRVfUl5a8WEnl+K5z4PNDx3/TGH7Gkk7HuhVT8VG5gM9HYdr5ImZ52X7yT
OMWkgZ5RsyzVexoO6IyiN3yP4zNx4UfmCs++9xdVYwdHoLECTF4jI25TxnaPoxk+
ZcIGx+o/2q82jB9Aca5sCf06lB3Z3JS9Xup3ogw9gBuiwr/BBhr16Vp+6DzUr29K
Em3N1RwYn8cISKLUi4PR706f+PFVAfhOw2F22hCBwrXMQnHpi063rQRLVLUOOxkE
WsKM3Uaxo2n7Xlkx27rEV1DKUQexlrZPzNCLQ4cwYxjn171YZzH97UiYg+UEBIw3
vj8M8b8nxl7xw8D/KS8oB2uKk62oZ0Vb2z1nxUcMv6IAehB/ZD1FXg30dSVcFWOg
1NKDiSuRCqNLknXkDQyfHHGNEXYXweSARCuJO1z95uOTCYxW0DPJTmkNFHObyOk9
xZn9L+qaGtJt4AwUbb8csX7GE5114DQXscaDgrPZ8wduS0vPfaTekxyQC73cM0oC
VIt3CDNOq55xBTrio6Tq9kqgZryb5XmDzM0nvSHn9hYpSalaNt9l5nYjyKCYwbBi
F7a6YHX7KmvljHQs6VWy8lUrqPgU+ks82bjBeWC/+wO95HwrdZA=
=TKUq
-END PGP SIGNATURE End Message ---

Bug#1030590: marked as done (debrelease: doesn't work (related to DEBRELEASE_DEBS_DIR))

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 09:49:32 +
with message-id 
and subject line Bug#1030590: fixed in devscripts 2.23.1
has caused the Debian Bug report #1030590,
regarding debrelease: doesn't work (related to DEBRELEASE_DEBS_DIR)
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.)


-- 
1030590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: devscripts
Version: 2.23.0
Severity: normal

Dear Maintainer,

Now debrelease return :

,
| $ debrelease 
| debrelease: config file specified DEBRELEASE_DEBS_DIR directory ".." does not 
exist!
`

I did a test with DEBRELEASE_DEBS_DIR=../ in ~/.devscripts but the
problem is the same.


Christian


-- Package-specific info:

--- /etc/devscripts.conf ---
DSCVERIFY_KEYRINGS="trustedkeys.gpg"

--- ~/.devscripts ---
DEBCLEAN_CLEANDEBS=yes
DEBSIGN_ALWAYS_RESIGN=yes
DEBSIGN_PROGRAM="gpg --homedir /home/marillat/.gnupg-dmo"
DEBUILD_DPKG_BUILDPACKAGE_OPTS="-j26"
DEBUILD_LINTIAN=yes
DEBUILD_LINTIAN_OPTS="--color always"
DEBUILD_PREPEND_PATH="/usr/lib/ccache"
GREP_EXCUSES_MAINTAINER=Marillat
DEBCHANGE_RELEASE_HEURISTIC=log
USCAN_SAFE=yes
USCAN_DOWNLOAD=no
DEVSCRIPTS_CHECK_DIRNAME_LEVEL=0
DEBDIFF_UNPACK_TARBALLS=no
DEBUILD_SET_ENVVAR_CCACHE_DIR=/home/marillat/.ccache

-- System Information:
Debian Release: bookworm/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.9-1-custom (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages devscripts depends on:
ii  dpkg-dev 1.21.19
ii  fakeroot 1.30.1-1.1
ii  file 1:5.44-3
ii  gnupg2.2.40-1
ii  gpgv 2.2.40-1
ii  libc62.36-8
ii  libdigest-md5-file-perl  0.08-1.1
ii  libfile-dirlist-perl 0.05-3
ii  libfile-homedir-perl 1.006-2
ii  libfile-touch-perl   0.12-2
ii  libfile-which-perl   1.27-2
ii  libipc-run-perl  20220807.0-1
ii  libmoo-perl  2.005005-1
ii  libswitch-perl   2.17-3
ii  libwww-perl  6.67-1
ii  patchutils   0.4.2-1
ii  perl 5.36.0-7
ii  python3  3.11.1-3
ii  sensible-utils   0.0.17+nmu1
ii  wdiff1.2.2-5

Versions of packages devscripts recommends:
ii  apt 2.5.5
ii  curl7.87.0-2
ii  dctrl-tools 2.24-3+b1
pn  debian-keyring  
ii  dupload 2.9.12
pn  equivs  
pn  libdistro-info-perl 
ii  libdpkg-perl1.21.19
ii  libencode-locale-perl   1.05-3
pn  libgit-wrapper-perl 
pn  libgitlab-api-v4-perl   
ii  liblist-compare-perl0.55-2
ii  liblwp-protocol-https-perl  6.10-1
pn  libsoap-lite-perl   
ii  libstring-shellquote-perl   1.04-3
ii  libtry-tiny-perl0.31-2
ii  liburi-perl 5.17-1
pn  licensecheck
ii  lintian 2.116.2
ii  man-db  2.11.2-1
ii  patch   2.7.6-7
pn  pristine-tar
ii  python3-apt 2.5.2+b1
ii  python3-debian  0.1.49
ii  python3-magic   2:0.4.26-3
ii  python3-requests2.28.1+dfsg-1
pn  python3-unidiff 
ii  python3-xdg 0.28-2
ii  strace  6.1-0.1
ii  unzip   6.0-27
ii  wget1.21.3-1+b2
ii  xz-utils5.4.1-0.1

Versions of packages devscripts suggests:
pn  adequate  
pn  at
pn  autopkgtest   
pn  bls-standalone
ii  build-essential   12.9
pn  check-all-the-things  
pn  cvs-buildpackage  
ii  debhelper 13.11.4
pn  diffoscope
pn  disorderfs
pn  dose-extra
pn  duck  
ii  elpa-devscripts   40.5
pn  faketime  
pn  gnuplot  

Bug#1030982: gscan2pdf: Segmentation fault

[Janusz S . Bień]

On Fri, Feb 10 2023 at  8:35 GMT, Jeff wrote:
> Please start gscan2pdf from the command line with the --log=log
> option, reproduce the problem, quit, and post the log file, which
> gscan2pdf may have compressed with xz.
>

Enclosed.

Regards- Janusz




log
Description: log

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#994619: marked as done (xpra: recommends gir1.2-appindicator3-0.1 which is no longer available)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 09:36:43 +
with message-id 
and subject line Bug#994619: fixed in xpra 3.1.3-0.1
has caused the Debian Bug report #994619,
regarding xpra: recommends gir1.2-appindicator3-0.1 which is no longer available
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.)


-- 
994619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xpra
Version: 3.0.13+dfsg1-1
Severity: normal

Dear Maintainer,

xpra recommends gir1.2-appindicator3-0.1 but the latter is no longer available.

Regards,

Stephen


-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), 
(100, 'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 
'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xpra depends on:
ii  adduser   3.118
ii  gir1.2-gtk-3.03.24.24-4
ii  init-system-helpers   1.60
ii  libavcodec58  7:4.3.2-0+deb11u2
ii  libavformat58 7:4.3.2-0+deb11u2
ii  libavutil56   7:4.3.2-0+deb11u2
ii  libc6 2.31-13
ii  libcairo2 1.16.0-5
ii  libglib2.0-0  2.66.8-1
ii  libgtk-3-03.24.24-4
ii  libpam0g  1.4.0-9
ii  libswscale5   7:4.3.2-0+deb11u2
ii  libsystemd0   247.3-6
ii  libturbojpeg0 1:2.0.6-4
ii  libvpx6   1.9.0-1
ii  libwebp6  0.6.1-2.1
ii  libx11-6  2:1.7.2-1
ii  libx264-160   2:0.160.3011+gitcde9a93-2.1
ii  libx265-192   3.4-2
ii  libxcomposite11:0.4.5-1
ii  libxdamage1   1:1.1.5-2
ii  libxext6  2:1.3.3-1.1
ii  libxfixes31:5.0.3-2
ii  libxi62:1.7.10-1
ii  libxkbfile1   1:1.1.0-1
ii  libxrandr22:1.5.1-1
ii  libxtst6  2:1.2.3-1
ii  python3   3.9.2-3
ii  python3-cairo 1.16.2-4+b2
ii  python3-gi3.38.0-2
ii  python3-rencode   1.0.6-1+b3
ii  x11-xserver-utils 7.7+8
ii  xserver-xorg-video-dummy  1:0.3.8-1+b1
ii  xvfb  2:1.20.11-1

Versions of packages xpra recommends:
pn  gir1.2-appindicator3-0.1  
ii  keyboard-configuration1.205
ii  openssh-client1:8.4p1-5
ii  python3-brotli1.0.9-2+b2
ii  python3-cpuinfo   5.0.0-2
ii  python3-dbus  1.2.16-5
ii  python3-dns   3.2.1-1
ii  python3-gssapi1.6.1-1+b3
ii  python3-kerberos  1.1.14-3.1+b3
ii  python3-lz4   3.1.3+dfsg-1
ii  python3-lzo   1.12-3+b4
ii  python3-numpy 1:1.19.5-1
ii  python3-opengl3.1.5+dfsg-1
ii  python3-paramiko  2.7.2-1
ii  python3-pil   8.1.2+dfsg-0.3
ii  python3-setproctitle  1.2.1-1+b1
ii  python3-uritools  3.0.0-2
ii  python3-xdg   0.27-2
ii  python3-zeroconf  0.26.1-1
ii  ssh-askpass   1:1.2.4.1-10+b1

Versions of packages xpra suggests:
ii  cups-client2.3.3op2-3+deb11u1
ii  cups-common2.3.3op2-3+deb11u1
ii  cups-filters   1.28.7-1
pn  cups-pdf   
ii  gstreamer1.0-plugins-bad   1.18.4-3
ii  gstreamer1.0-plugins-base  1.18.4-2
ii  gstreamer1.0-plugins-good  1.18.4-2
ii  gstreamer1.0-plugins-ugly  1.18.4-2
ii  openssh-server 1:8.4p1-5
ii  pulseaudio 14.2-2
ii  pulseaudio-utils   14.2-2
pn  python3-avahi  
ii  python3-cryptography   3.3.2-1
ii  python3-cups   2.0.1-4+b1
ii  python3-gst-1.01.18.3-1
ii  python3-netifaces  0.10.9-0.2+b3
pn  python3-opencv 
ii  python3-pyinotify  0.9.6-1.3
pn  python3-pyopencl   
pn  python3-uinput 
ii  python3-yaml   5.3.1-5
pn  v4l2loopback-dkms  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xpra
Source-Version: 3.1.3-0.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
xpra, which is due to be installed in the Debia

Bug#1004797: marked as done (xpra: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 09:36:43 +
with message-id 
and subject line Bug#1004797: fixed in xpra 3.1.3-0.1
has caused the Debian Bug report #1004797,
regarding xpra: FTBFS with ffmpeg 5.0
to be marked as done.

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

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


-- 
1004797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xpra
Version: 3.1-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

xpra FTBFS with ffmpeg 5.0 in experimental:

x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -Ixpra/codecs/dec_avcodec2 
-I/usr/include/x86_64-linux-gnu -I/usr/include/python3.10 -c 
xpra/codecs/dec_avcodec2/decoder.c -o 
build/temp.linux-x86_64-3.10/xpra/codecs/dec_avcodec2/decoder.o -Wall -Werror 
-Wno-error=strict-prototypes -Wno-error=deprecated-declarations -fPIC -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-error=attributes -Wno-error=deprecated-declarations
xpra/codecs/dec_avcodec2/decoder.c: In function 
‘__pyx_pf_4xpra_6codecs_12dec_avcodec2_7decoder_7Decoder_init_context’:
xpra/codecs/dec_avcodec2/decoder.c:5663:23: error: assignment discards ‘const’ 
qualifier from pointer target type [-Werror=discarded-qualifiers]
 5663 |   __pyx_v_self->codec = avcodec_find_decoder(__pyx_v_CodecID);
  |   ^
xpra/codecs/dec_avcodec2/decoder.c:5858:3: warning: ‘thread_safe_callbacks’ is 
deprecated [-Wdeprecated-declarations]
 5858 |   __pyx_v_self->codec_ctx->thread_safe_callbacks = 1;
  |   ^~~~
In file included from xpra/codecs/dec_avcodec2/decoder.c:675:
/usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:1479:9: note: declared here
 1479 | int thread_safe_callbacks;
  | ^
xpra/codecs/dec_avcodec2/decoder.c: In function 
‘__pyx_pf_4xpra_6codecs_12dec_avcodec2_7decoder_7Decoder_26decompress_image’:
xpra/codecs/dec_avcodec2/decoder.c:9318:9: warning: ‘av_init_packet’ is 
deprecated [-Wdeprecated-declarations]
 9318 | av_init_packet((&__pyx_v_avpkt));
  | ^~
In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
 from xpra/codecs/dec_avcodec2/decoder.c:675:
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
  506 | void av_init_packet(AVPacket *pkt);
  |  ^~
cc1: all warnings being treated as errors
error: command '/usr/lib/ccache/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:367: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.10 setup.py build --with-verbose --with-Xdummy 
--without-Xdummy_wrapper --with-html5 --without-minify --without-html5_gzip 

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xpra
Source-Version: 3.1.3-0.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated xpra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Feb 2023 01:03:10 +0200
Source: xpra
Architecture: source
Version: 3.1.3-0.1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Adrian Bunk 
Closes: 994619 1004797
Changes:
 xpra (3.1.3-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release.
 - Supports FFmpeg 5. (Closes: #1004797)
   * Removed the obsolete gir1.2-appindicator3-0.1 from Recommends.
 (Closes: #994619)
   * Apply change to fix dh_python3 invocation from Steve Langasek.
Checksums-Sha1:
 fa9ff86ee60a12b3eba049f890dbafd3c01ea484 2475 xpra_3.1.3-0.1.dsc
 a3ff6ccb0e344e12ef73ea7

Bug#1030997: rust-fxprof-processed-profile: autopkgtets failure

[Adrian Bunk]

Source: rust-fxprof-processed-profile
Version: 0.4.0-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-fxprof-processed-profile/31208244/log.gz

...
running 1 test
test test::it_works ... FAILED

failures:

 test::it_works stdout 
thread 'test::it_works' panicked at '

json atoms at path ".threads[0].stackTable.category[9]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[11]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[14]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[7]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[8]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[10]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[4]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[5]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[2]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[3]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[15]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[1]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[6]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[12]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[0]" are not equal:
lhs:
1
rhs:
0

json atoms at path ".threads[0].stackTable.category[13]" are not equal:
lhs:
1
rhs:
0

', src/lib.rs:1680:9
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
   2: fxprof_processed_profile::test::it_works
 at ./src/lib.rs:1680:9
   3: fxprof_processed_profile::test::it_works::{{closure}}
 at ./src/lib.rs:1467:5
   4: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
   5: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
test::it_works

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.01s

error: test failed, to rerun pass `--lib`
autopkgtest [09:33:52]: test rust-fxprof-processed-profile:@: 
---]
autopkgtest [09:33:52]: test rust-fxprof-processed-profile:@:  - - - - - - - - 
- - results - - - - - - - - - -
rust-fxprof-processed-profile:@ FAIL non-zero exit status 101
...
autopkgtest [09:34:25]:  summary
rust-fxprof-processed-profile:@ FAIL non-zero exit status 101
librust-fxprof-processed-profile-dev:default FAIL non-zero exit status 101
librust-fxprof-processed-profile-dev: FAIL non-zero exit status 101

Bug#1013526: libtickit-widget-scrollbox-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255

[Adrian Bunk]

Version: 0.12-1

On Sat, Jun 25, 2022 at 10:09:46AM +0300, Damyan Ivanov wrote:
>...
> I've filed a wishlist #1013740 for upgrading libtickit to 0.4.2a, 
> which would allow upgrading libtickit-perl to the latest upstream, 
> either of which may help.

I don't know where it was fixed, but 0.12-1 seems to build reliably:
https://tests.reproducible-builds.org/debian/history/libtickit-widget-scrollbox-perl.html

cu
Adrian

Bug#1030813: mumble: autopkgtest regression

[Adrian Bunk]

On Fri, Feb 10, 2023 at 09:25:00AM +, Chris Knadle wrote:
> The autopkgtest smoke test still fails when calling /usr/bin/mumble because
> of not being able to connect to a display.
>...

The usual solution for this is to use a virtual X environment with
  xvfb-run -a 

I haven't checked whether this works with mumble.

cu
Adrian

Bug#1030813: mumble: autopkgtest regression

[Chris Knadle]

The autopkgtest smoke test still fails when calling /usr/bin/mumble because of 
not being able to connect to a display. I'm uploading another package that 
avoids calling mumble in the smoke test but still calls /usr/sbin/murmurd which 
should still pass, so I'll be closing this bug with it.


[Feel free to re-open the bug if it returns.]

-
autopkgtest [03:17:07]: test smoke: [---
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it 
was found.
This application failed to start because no Qt platform plugin could be 
initialized. Reinstalling the application may fix this problem.


Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, 
vnc, xcb.


Aborted
autopkgtest [03:17:07]: test smoke: ---]
autopkgtest [03:17:07]: test smoke:  - - - - - - - - - - results - - - - - - - 
- - -
smokeFAIL non-zero exit status 1
-

--
Chris Knadle
chris.kna...@coredump.us

Bug#965644: marked as done (libibtk: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 09:19:42 +
with message-id 
and subject line Bug#965644: fixed in libibtk 0.0.14-12.2
has caused the Debian Bug report #965644,
regarding libibtk: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


-- 
965644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libibtk
Version: 0.0.14-12.1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package libibtk uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: libibtk
Source-Version: 0.0.14-12.2
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libibtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Feb 2023 01:30:33 +0200
Source: libibtk
Architecture: source
Version: 0.0.14-12.2
Distribution: unstable
Urgency: high
Maintainer: Christian Bayle 
Changed-By: Adrian Bunk 
Closes: 965644 999106
Changes:
 libibtk (0.0.14-12.2) unstable; urgency=high
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965644)
   * debian/rules: Add build-{arch,indep}. (Closes: #999106)
Checksums-Sha1:
 d7c18bfd1e9c257a99077af6d04ad403cf1c16b9 1753 libibtk_0.0.14-12.2.dsc
 c2238a403ea188a5a94b4fb898e6e76a9c94f5e6 366376 libibtk_0.0.14-12.2.diff.gz
Checksums-Sha256:
 59cb759160ed19adfcc31fefea0a599f989e11443e03a9243b31ba8e3b7378ab 1753 
libibtk_0.0.14-12.2.dsc
 03217f64ce547c8989792e81cee4a79b7b2f9cb9246ed9ba54a927a6c0778131 366376 
libibtk_0.0.14-12.2.diff.gz
Files:
 995da51927179800b2216c232c0ac37f 1753 libs optional libibtk_0.0.14-12.2.dsc
 d8f06ea887d30072ee6683b68f74307f 366376 libs optional 
libibtk_0.0.14-12.2.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmPlgw4ACgkQiNJCh6LY
mLFPtA/+I+QnR5k2YsMXgQWfQs7IqbGMNS2RJQE0I+afallX05SRIT4/Z7PADQit
Kzn4vMhnVMXvu5HZfdmArMm8XnMYArvp0/vdBsOp7JQW2CM+LVf51daLxLlvt7Sz
k/OAmNZ+sfB8B/+Kkgb5YCBU1kAsy6KDC2JSjlCmfscj3PZ5d0JzwUpeCQ6aF6hO
CcHbYfHO1w3UPXy2UA2fAXWwdXj3jq6u8LLgVxOENKvUcr67Vq3W6/va5gHL0X66
hGfj69NgjSoQAXjv08Ndcvzlq0D1fKH/mNAEq73HKak6V1ELrJQ6vWjj7v9Ov8AF
+RE2uOpZ6q0mtT/FiHCoSIvRF3ipcBbPkRzGWGHQd29ZTO53fxaMsOcUr8rtLZmS
RqIY44b/YEFDM4uR4uKfP89A9AizWUX6gww6LQI8J1EmuqR83HTmrUPJKrsqNyjt
yiU2atWMxrYOIb2zT+9NlPsOOdxJmFIQljUVKamMppo9E90pEyP8Nof75GgRKe7H
4DmowHWSqUxb9K/fsuhCghIn/HWGdNNNfy7uMuAsrXKgeRxHojU/HINcKoTRCYNx
Lz5sn44x3lJgrFBvcBuIT8JF/QhjF82kKTRcwcZrUAG0HWe1SIAxYS+V0YhAzgr6
GPLduE/JhvnnsYSVY/RnvC+Zu1DSQuDs92vs0qKUk0S/NiDhock=
=tEPq
-END PGP SIGNATURE End Message ---

Bug#999106: marked as done (libibtk: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 09:19:42 +
with message-id 
and subject line Bug#999106: fixed in libibtk 0.0.14-12.2
has caused the Debian Bug report #999106,
regarding libibtk: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


-- 
999106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libibtk
Version: 0.0.14-12.1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: libibtk
Source-Version: 0.0.14-12.2
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
libibtk, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libibtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Feb 2023 01:30:33 +0200
Source: libibtk
Architecture: source
Version: 0.0.14-12.2
Distribution: unstable
Urgency: high
Maintainer: Christian Bayle 
Changed-By: Adrian Bunk 
Closes: 965644 999106
Changes:
 libibtk (0.0.14-12.2) unstable; urgency=high
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965644)
   * debian/rules: Add build-{arch,indep}. (Closes: #999106)
Checksums-Sha1:
 d7c18bfd1e9c257a99077af6d04ad403cf1c16b9 1753 libibtk_0.0.14-12.2.dsc
 c2238a403ea188a5a94b4fb898e6e76a9c94f5e6 366376 libibtk_0.0.14-12.2.diff.gz
Checksums-Sha256:
 59cb759160ed19adfcc31fefea0a599f989e11443e03a9243b31ba8e3b7378ab 1753 
libibtk_0.0.14-12.2.dsc
 03217f64ce547c8989792e81cee4a79b7b2f9cb9246ed9ba54a927a6c0778131 366376 
libibtk_0.0.14-12.2.diff.gz
Files:
 995da51927179800b2216c232c0ac37f 1753 libs optional libibtk_0.0.14-12.2.dsc
 d8f06ea887d30072ee6683b68f74307f 366376 libs optional 
libibtk_0.0.14-12.2.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmPlgw4ACgkQiNJCh6LY
mLFPtA/+I+QnR5k2YsMXgQWfQs7IqbGMNS2RJQE0I+afallX05SRIT4/Z7PADQit
Kzn4vMhnVMXvu5HZfdmArMm8XnMYArvp0/vdBsOp7JQW2CM+LVf51daLxLlvt7Sz
k/OAmNZ+sfB8B/+Kkgb5YCBU1kAsy6KDC2JSjlCmfscj3PZ5d0JzwUpeCQ6aF6hO
CcHbYfHO1w3UPXy2UA2fAXWwdXj3jq6u8LLgVxOENKvUcr67Vq3W6/va5gHL0X66
hGfj69NgjSoQAXjv08Ndcvzlq0D1fKH/mNAEq73HKak6V1ELrJQ6vWjj7v9Ov8AF
+RE2uOpZ6q0mtT/FiHCoSIvRF3ipcBbPkRzGWGHQd29ZTO53fxaMsOcUr8rtLZmS
RqIY44b/YEFDM4uR4uKfP89A9AizWUX6gww6LQI8J1EmuqR83HTmrUPJKrsqNyjt
yiU2atWMxrYOIb2zT+9NlPsOOdxJmFIQljUVKamMppo9E90pEyP8Nof75GgRKe7H
4DmowHWSqUxb9K/fsuhCghIn/HWGdNNNfy7uMuAsrXKgeRxHojU/HINcKoTRCYNx
Lz5sn44x3lJgrFBvcBuIT8JF/QhjF82kKTRcwcZrUAG0HWe1SIAxYS+V0YhAzgr6
GPLduE/JhvnnsYSVY/RnvC+Zu1DSQuDs92vs0qKUk0S/NiDhock=
=tEPq
-END PGP SIGNATURE End Message ---

Bug#965786: marked as done (pppoeconf: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 09:19:54 +
with message-id 
and subject line Bug#965786: fixed in pppoeconf 1.21+nmu3
has caused the Debian Bug report #965786,
regarding pppoeconf: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


-- 
965786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pppoeconf
Version: 1.21
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package pppoeconf uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: pppoeconf
Source-Version: 1.21+nmu3
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated pppoeconf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Feb 2023 01:46:49 +0200
Source: pppoeconf
Architecture: source
Version: 1.21+nmu3
Distribution: unstable
Urgency: high
Maintainer: Gregory Colpart 
Changed-By: Adrian Bunk 
Closes: 965786
Changes:
 pppoeconf (1.21+nmu3) unstable; urgency=high
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965786)
Checksums-Sha1:
 d2e6a44f76a6ee0ea56d42da5fc511c3381e453c 1584 pppoeconf_1.21+nmu3.dsc
 361395a351ab13251d8e3c25052fb89ae1710ce2 52005 pppoeconf_1.21+nmu3.tar.gz
Checksums-Sha256:
 20c313e4bf9d9596aae39b56c5493eb3e4063c2ec3326be4a823437b2b19ff83 1584 
pppoeconf_1.21+nmu3.dsc
 420bff71b4f3c0aceead57c1e3b095afe9da9ed67b3dccd0c7b29d9b0ad88240 52005 
pppoeconf_1.21+nmu3.tar.gz
Files:
 5bae8493c626173c4e70abb353f0038e 1584 net optional pppoeconf_1.21+nmu3.dsc
 ef0b3cd137a142d7fb19f0015b12799f 52005 net optional pppoeconf_1.21+nmu3.tar.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmPlhjgACgkQiNJCh6LY
mLE41g/9H5Bjgotnqghl5nvPwPN1Lasj6pgJ89S6fp1TETM3PMffmY61uu2V3wf9
4PM68DUP6yrqD8I08ocFudjYVP+Qy/FJLQaCJzlH3nQwjDVb3vFReBPWxIeosv6u
4N16vlNV4gcnj1CmWN1sZW5U7+5RAvn17kKlHgBUvigkxKbvspT5a1HVaG4mN08C
RQYuHpj2ErFB9eO/lPJ0PU+cj8nLg/Yzwilyuwu3Dpg1ThWIvMSfXwdQw1RUbB5m
I2FE2ce1MgpTDmRIzx+UoSYbxCiVX2fNY00sVeQ8rNPfUBGIE9pB+63i1bv/UH7y
56Dw9+rnIaUWI0CaRJQWNDvkx9LAT7fSLfQEb4uNztxV2RRUeMv4IQ4wPlK3IYy7
P+2/c223Mv6T/4tEnzuKzxe9GBO9Z3mMZnTE1hJ+Ti4QobudNz5vZzUmQzssZZgq
1s1N7xxGxxnAsklhegxIG0tEj8sjSKeDgJfh/UYt6rNz5l4sp29jS1JUPyjNT9gE
wkfS/MbkszI9hMwtjnCnYYxeqCqHdcHJOTHTzDZUE/DvFiDSPR8T6muz1TAbSWzK
QaNUvzcByT7jtW3Y6C3SgH4KllEB1Ng4SQkICKqutVPhrweWMlR5LRtvcwZK5qpM
KyhqHkNwaEKLzqwBJH0L1b/MVbhxY2CiUjmIWpCaMHL/QIHW788=
=s4An
-END PGP SIGNATURE End Message ---

Bug#965534: marked as done (gatos: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2023 09:19:14 +
with message-id 
and subject line Bug#965534: fixed in gatos 0.0.5-19.2
has caused the Debian Bug report #965534,
regarding gatos: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


-- 
965534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gatos
Version: 0.0.5-19
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package gatos uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: gatos
Source-Version: 0.0.5-19.2
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gatos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Feb 2023 01:40:51 +0200
Source: gatos
Architecture: source
Version: 0.0.5-19.2
Distribution: unstable
Urgency: high
Maintainer: Christian Bayle 
Changed-By: Adrian Bunk 
Closes: 965534
Changes:
 gatos (0.0.5-19.2) unstable; urgency=high
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965534)
Checksums-Sha1:
 e9a8f91056cde77fbb6bc7b3f2d150b0a4b89295 1865 gatos_0.0.5-19.2.dsc
 12f527fd01bf09344360dbe6cd95c3d01f5b68f6 372372 gatos_0.0.5-19.2.diff.gz
Checksums-Sha256:
 0cc68303c14639961c82b734d4a4e3a69a58ffbdc1e1ae25264514f44c84f558 1865 
gatos_0.0.5-19.2.dsc
 94da9f330cf63c55b1bd45012fe4492b717c5662f3d31e92f30d0b4c94c77edf 372372 
gatos_0.0.5-19.2.diff.gz
Files:
 28234c03ecaf22d4c7b1ece9859c15c5 1865 misc extra gatos_0.0.5-19.2.dsc
 cffa745613e93c82af481a5e5223d3d9 372372 misc extra gatos_0.0.5-19.2.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmPlhYwACgkQiNJCh6LY
mLESlBAAu82gd170psDFgLPBRQdvTvtNWTE1HPfhtsWdLv1dQ716Jqs7FLDg2pPg
HR49OrgMpf7pmQv/zH589BFIVX5/I7/eNLDwX0jnUS+1y89cZsfwh+NyC8K7NZbn
v7GmW4sYJUlFEC1MGIn8C8svDVDRY4Via+WK4SdNiW8jc0ZRLnV9GkblopyYM1ZD
ouWsPIf95pGDSx08H1u9TGKNQvlLKV3dedNMQzqnX8FfkemEbK8yEXMqiHqpnB7x
GKXmT2TOEhP72+a8PDIN68TDhlNKrRedwnAISPcmrUthZbt+SiT+cdNDcSvXmRqR
yHu8bUKVv459WznUW5giuRk6mnzZ2tHLsfxluKhWfv9RoN8+7MnIM+1PUU9Kkdr8
gpFsaIXzSL9sAUXVzBntW9JcTmm3a/2GT8SvGkJncf8kx28mayJ6S2dc8hAC/F+P
ZJ/Pf5aQyKaPKzJsiVx1PjMD8cLnIjnuTBWctx/uSrJDwWsdxn3xCqDjT4ZyUDa2
yzPlXW3Fsv9XP+WBELcUfGuwXp116jX5614eT1jnTqEX79Lg6SopxO/oeDbTiaGp
V7gw4Gcx6grdzqk+jXEPotCsEnRfYmhnYMPzwsFoxAdd6Dk/aQTMDAoJ0mXdjzFn
NvKa68b4cw3Z5BnSFMkZKnlznNNwjzKDMw+HuCj6KyPaHbimTgw=
=Md3c
-END PGP SIGNATURE End Message ---

Bug#1030989: librust-cradle-dev is not installable

[Adrian Bunk]

Package: librust-cradle-dev
Version: 0.2.2-2
Severity: serious

The following packages have unmet dependencies:
 librust-cradle-dev : Depends: librust-gag-1+default-dev but it is not 
installable
  Depends: librust-nix-0.25+default-dev but it is not 
installable

Processed: severity of 965534 is serious

[Debian Bug Tracking System]

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

> severity 965534 serious
Bug #965534 [src:gatos] gatos: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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