Bug#1032328: ITP: python-ctranslate2 -- Optimized inference engine for OpenNMT-py and OpenNMT-tf models

[Petter Reinholdtsen]

[Kartik Mistry 2023-03-04]
> CTranslate2 is an optimized inference engine for OpenNMT-py and OpenNMT-tf
> models supporting both CPU and GPU execution. It also aims to be a place for
> experimentation around model compression and inference acceleration.

Hi, what is the state of your effort to get CTranslate2 into Debian?

Is this something for the Debian Deep Learning team?

I am looking at https://github.com/guillaumekln/faster-whisper/ >,
which need CTranslate2, and thus am curious how far away from Debian
packages you are.
-- 
Happy hacking
Petter Reinholdtsen

Bug#1034971: lxd-client: missing Breaks+Replaces for lxc when upgrading from bullseye

[Helmut Grohne]

Hi Mathias,

On Fri, Apr 28, 2023 at 02:32:10AM +, Mathias Gibbens wrote:
>   It looks like you're trying to install the version of lxd from
> testing on a bullseye system? Mixing packages from different releases
> isn't supported [1]. Furthermore, there hasn't yet been a stable

In fact this is supported as a partial upgrade. The situation of mixing
packages from stable and testing is very common and happens during and
dist-upgrade.

> release of Debian that shipped lxd, so there's no way lxd-client might
> be upgraded before lxc when upgrading from bullseye to bookworm. As
> such, I don't know if it's really worthwhile to try to address this
> situation that would only occur when the end-user has already broken
> key assumptions about how their system is configured.

That's indeed a better argument. It is non-trivial to rule out the
scenario in bookworm Depends or Recommends lxd and thus pulls lxd into
the upgrade scenario.

>   The packaging of lxc was updated during the bookworm development
> cycle to properly name its bash completion file and de-conflict with
> lxd packaging [2]. Upgrading lxc packages from bullseye -> bookworm
> should work smoothly; after the upgrade is complete users will then
> also be able to `apt install lxd` if they so wish, and they won't
> encounter the packaging conflict.

This is a good reason for why the effects should be minor. It still is
not clear whether something in the upgrade would be able to pull lxd and
thus trigger the situation. In any case, the reasoning seems sufficient
to me to downgrade the severity to important. After bookworm is
released, the bug can be closed in any case as we don't support skip
upgrades.

>   Does that address your concern?

Partially.

Helmut

Bug#1034939: librust---dev: missing Breaks+Replaces for librust-mio-dev when upgrading from bullseye

[Helmut Grohne]

Hi Peter,

On Fri, Apr 28, 2023 at 01:24:16AM +0100, Peter Green wrote:
> Summarising a number of bug reports by Helmut Ghrone:
> 
> > Please ensure that librust---dev has sufficient Breaks and 
> > Replaces declarations.
> 
> The issue specifically appears to be that the breaks+replaces are declared
> against a virtual package, it seems dpkg is honoring the breaks against the
> virtual package but not the replaces. So it correctly marks the package from
> stable as broken, but fails to actually unpack the package from testing.

Thanks for looking into this so quickly. I concur: The Breaks are ok,
but the Replaces are not. Debian policy section 7.6.1 explicitly says
that Replaces don't work on virtual packages.

> Declaring against the physical package is also problematic becase Debian 
> package
> relationships don't support version ranges. What this would likely mean in
> practice is it would be possible to co-install the "current" semver alongside
> one previous semver, but it would not be possible to co-install two different
> previous semvers.

Can you go into more detail as to what you mean with "don't support
version ranges"? In principle, you could declare the Replacs to be
slightly broader than necessary (i.e. instead of declaring against the
specific range, you can replace all old packages). Do you agree that
this is feasible?

> Another option may be to use "Conflicts" instead of "Breaks". This should 
> force
> the old package to be upgraded or removed before the semver-specific package
> can be unpacked.

It's a big hammer. It'll work. It's a hammer we're looking into as part
of the DEP 17 thread on debian-de...@lists.debian.org currently, but I
recommend avoiding it if possible. Possible it seems in this case.

> I feel the timing of these bugs is very unfortunate. I don't object to
> people running QA checks, but it's generally easier to deal with bugs if
> they are reported earlier in the freeze process. The timing of these bugs
> leaves little time for discussion if we are to get the fixes in before the
> full freeze.

I am sorry about that. This is a side-effect of earlier discussions
having stalled and only recently been picked up. However, these tests
should likely be running more continuously.

> As I see it we have a few options to deal with this for bookworm.
> 
> 1. Make debcargo Use Conflicts instead of Breaks.
> 2. Make debcargo declare Breaks/Replaces against the physical package
>version using a << dependency. This will allow the non-semver suffixed
>package to be installed alongside one semver-suffixed package, but with
>our current virtual packages scheme would not allow two semver-suffixed
>packages of the same crate to be coinstalled.
> 3. Add manual breaks/replaces for the versions in bullseye, this will
>paper over the issue for bullseye-bookworm upgrades, but is not a long
>term fix.

 4. Continue to use Breaks the way they are. Declare Replaces against
the physical package using a << relation. This would not allow the
semver-suffixed package to be installed alongside, but Breaks and
Replaces would no longer match up and that could make lintian
unhappy.

 5. In a different bug, Samuel Thibault observed that the target package
was not part of bullseye. As such, an upgrade scenario involving it
was unlikely. All of the 6 affected librus-*-dev packages are not
part of bullseye. We could argue that the risk of these effects
showing up in practice is not big enough to warrant an invasive fix.
Rather, we'd downgrade them to important (and upgrade to serious
when we see them in the wild) and close them after bookworm (since
we don't support skip upgrades).

> Do any other members of the rust team have an opinion on this? I'm
> personally inclined towards option 1 and intend to implement it if
> noone objects in the next couple of days.

Let me know if you see 4 as a viable option.

> Do the release team have an opinion on this? It looks like only one of
> the packages involved (rust-env-logger-0.7) is a key package.

I filed these as serious, because these are policy violations with a
trivial fix. You made it quite clear that the premise of the fix being
trivial is false here. If the cure is worse than the symptoms, maybe we
should consider not applying the cure and select option 5.

Helmut

Bug#1035041: unblock: rust-h2/0.3.13-2

[plugwash]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package rust-h2

The new version fixes CVE-2023-26964/RUSTSEC-2023-0034 it consists of two
commits backported from upstream, one for the CVE fix itself and one to fix
a regression caused by the CVE fix. The fix has been uploaded to unstable
and autopkgtests passed on all architectures where britney runs them.

Please also schedule binnmus for rust-sequoia-sq, rust-tealdeer and sccache so
that they pick up the fix. I have done local rebuild tests on these packages
and they all built sucessfully.

unblock rust-h2/0.3.13-2

-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 4.19.0-18-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru rust-h2-0.3.13/debian/changelog rust-h2-0.3.13/debian/changelog
--- rust-h2-0.3.13/debian/changelog 2022-06-21 15:47:48.0 +
+++ rust-h2-0.3.13/debian/changelog 2023-04-23 09:50:43.0 +
@@ -1,3 +1,15 @@
+rust-h2 (0.3.13-2) unstable; urgency=medium
+
+  * Team upload.
+  * Package h2 0.3.13 from crates.io using debcargo 2.5.0
+  * Add patch limit-pending-accept-reset-streams.patch cherry picked from
+upstream to fix denial of service vulnerability. CVE-2023-26964
+RUSTSEC-2023-0034 (Closes: #1034723)
+  * Add patch fix-regression.patch chrerry picked from upstream to fix a
+regression introduced by the above patch.
+
+ -- Peter Michael Green   Sun, 23 Apr 2023 09:50:43 +
+
 rust-h2 (0.3.13-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru rust-h2-0.3.13/debian/copyright rust-h2-0.3.13/debian/copyright
--- rust-h2-0.3.13/debian/copyright 2022-06-21 15:47:48.0 +
+++ rust-h2-0.3.13/debian/copyright 2023-04-23 09:50:43.0 +
@@ -7,12 +7,12 @@
 Files: *
 Copyright:
  2017-2019 Carl Lerche 
- 2017-2022 Sean McArthur 
+ 2017-2023 Sean McArthur 
 License: MIT
 
 Files: debian/*
 Copyright:
- 2018-2022 Debian Rust Maintainers 

+ 2018-2023 Debian Rust Maintainers 

  2018-2019 Wolfgang Silbermayr 
 License: MIT
 
diff -Nru rust-h2-0.3.13/debian/copyright.debcargo.hint 
rust-h2-0.3.13/debian/copyright.debcargo.hint
--- rust-h2-0.3.13/debian/copyright.debcargo.hint   2022-06-21 
15:47:48.0 +
+++ rust-h2-0.3.13/debian/copyright.debcargo.hint   2023-04-23 
09:50:43.0 +
@@ -25,8 +25,8 @@
 
 Files: debian/*
 Copyright:
- 2018-2022 Debian Rust Maintainers 

- 2018-2022 Wolfgang Silbermayr 
+ 2018-2023 Debian Rust Maintainers 

+ 2018-2023 Wolfgang Silbermayr 
 License: MIT
 
 License: MIT
diff -Nru rust-h2-0.3.13/debian/patches/fix-regression.patch 
rust-h2-0.3.13/debian/patches/fix-regression.patch
--- rust-h2-0.3.13/debian/patches/fix-regression.patch  1970-01-01 
00:00:00.0 +
+++ rust-h2-0.3.13/debian/patches/fix-regression.patch  2023-04-23 
09:50:43.0 +
@@ -0,0 +1,19 @@
+commit 1c6fa285afe436ca2a1f8abd38a6389353f360b6
+Author: Sean McArthur 
+Date:   Mon Apr 17 14:08:02 2023 -0400
+
+fix: pending-accept remotely-reset streams pattern was checking is_local
+
+diff --git a/src/proto/streams/state.rs b/src/proto/streams/state.rs
+index b9612addc..76638fc87 100644
+--- a/src/proto/streams/state.rs
 b/src/proto/streams/state.rs
+@@ -362,7 +362,7 @@ impl State {
+ 
+ pub fn is_remote_reset() -> bool {
+ match self.inner {
+-Closed(Cause::Error(ref e)) => e.is_local(),
++Closed(Cause::Error(ref e)) => !e.is_local(),
+ _ => false,
+ }
+ }
diff -Nru 
rust-h2-0.3.13/debian/patches/limit-pending-accept-reset-streams.patch 
rust-h2-0.3.13/debian/patches/limit-pending-accept-reset-streams.patch
--- rust-h2-0.3.13/debian/patches/limit-pending-accept-reset-streams.patch  
1970-01-01 00:00:00.0 +
+++ rust-h2-0.3.13/debian/patches/limit-pending-accept-reset-streams.patch  
2023-04-23 09:50:43.0 +
@@ -0,0 +1,288 @@
+commit 5bc8e72e5fcbd8ae2d3d9bc78a1c0ef0040bcc39
+Author: Sean McArthur 
+Date:   Wed Apr 12 12:23:56 2023 -0400
+
+fix: limit the amount of pending-accept reset streams
+
+Streams that have been received by the peer, but not accepted by the
+user, can also receive a RST_STREAM. This is a legitimate pattern: one
+could send a request and then shortly after, realize it is not needed,
+sending a CANCEL.
+
+However, since those streams are now "closed", they don't count towards
+the max concurrent streams. So, they will sit in the accept queue, using
+memory.
+
+In most cases, the user is calling 

Bug#1034865: [Pkg-rust-maintainers] Bug#1034865: compilation error on riscv64

[Peter Green]

reassign 1034865 rust-virtiofsd
thanks

On 28/04/2023 05:23, Michael Tokarev wrote:

I'm sorry about this.. - I planned but forgot to include the link,
here it is:

https://buildd.debian.org/status/fetch.php?pkg=rust-virtiofsd=riscv64=1.5.1-2=1682451850=0



The real error seems to be.


error[E0425]: cannot find value `SYS_renameat` in crate `libc`
--> src/seccomp.rs:156:31
 |
156 | allow_syscall!(ctx, libc::SYS_renameat);
 |    help: a constant with a 
similar name exists: `SYS_renameat2`

  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=virtiofsd CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='The Virtiofs Project Developers' CARGO_PKG_DESCRIPTION='A virtio-fs vhost-user device daemon' CARGO_PKG_HOMEPAGE='https://virtio-fs.gitlab.io/' CARGO_PKG_LICENSE='Apache-2.0 AND BSD-3-Clause' CARGO_PKG_LICENSE_FILE='' 
CARGO_PKG_NAME=virtiofsd CARGO_PKG_REPOSITORY='https://gitlab.com/virtio-fs/virtiofsd' CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=1.5.1 CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_MINOR=5 CARGO_PKG_VERSION_PATCH=1 CARGO_PKG_VERSION_PRE='' CARGO_PRIMARY_PACKAGE=1 LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
--crate-name virtiofsd --edition=2018 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 -C metadata=6f7229c0f333c6ab -C extra-filename=-6f7229c0f333c6ab --out-dir /<>/target/riscv64gc-unknown-linux-gnu/debug/deps --target 
riscv64gc-unknown-linux-gnu -C incremental=/<>/target/riscv64gc-unknown-linux-gnu/debug/incremental -L dependency=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps -L dependency=/<>/target/debug/deps --extern 
bitflags=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libbitflags-020e1d6f4909c410.rlib --extern capng=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libcapng-bdfdf42ef80240ab.rlib --extern 
env_logger=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libenv_logger-d43f373285c87e7e.rlib --extern futures=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libfutures-b3bc500ee27aba0a.rlib --extern 
libc=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/liblibc-8a51d731e0dcd23a.rlib --extern libseccomp_sys=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/liblibseccomp_sys-0ab028f4698ed367.rlib --extern 
log=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/liblog-cc8c7fcd95f45900.rlib --extern structopt=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libstructopt-841cdf971c364072.rlib --extern 
syslog=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libsyslog-65f8c45d0eba9692.rlib --extern vhost=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libvhost-085bcc60ec15e5ad.rlib --extern 
vhost_user_backend=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libvhost_user_backend-6a6bde03ae798550.rlib --extern virtio_bindings=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libvirtio_bindings-cd7994908f89c7ca.rlib --extern 
virtio_queue=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libvirtio_queue-347a8b571369835e.rlib --extern vm_memory=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libvm_memory-5fe874c960e9ebd0.rlib --extern 
vmm_sys_util=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps/libvmm_sys_util-7b1ce134cf22cc99.rlib -C debuginfo=2 --cap-lints warn -C linker=riscv64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix /<>=/usr/share/cargo/registry/virtiofsd-1.5.1 --remap-path-prefix 
/<>/debian/cargo_registry=/usr/share/cargo/registry`
For more information about this error, try `rustc --explain E0425`.
error: could not compile `virtiofsd` due to previous error

It looks like this is fixed in version 1.6.0

https://gitlab.com/virtio-fs/virtiofsd/-/commit/4c792d7d4d0dc1ade166ebcf839ef6e2f62681c7

Bug#892377: RFP: company-irony -- C, C++ and Objective-C completion tooltips for emacs.

[Nicholas D Steeves]

# resending because the BTS bounced this email due to then-archived
# state of this bug.  It won't bounce now, because it's been unarchived.
unarchive 892377
reopen 892377
retitle 892377 RFP: company-irony -- C, C++ and Objective-C completion tooltips 
for emacs.
submitter 892377 !
thanks

Dear Alberto and anyone else reading this,

It appears that Bart's stale-bot closed this bug, which is a shame
because this package makes our Emacs and irony-mode packages more
useful.  Since the last update to this bug I've been granted DD
privileges, so, Alberto, I'd like to sponsor your work now that I'm able
to.  TODO notes from my last review are at
https://bugs.debian.org/890878, but I haven't verified if they're still
current.

The only reason that I've set myself as submitter is to make it easier
to remain appraised of this bug's status.  Alberto, please set yourself
as owner and retitle if you'd like to resume the work.

Current state of the progress on this RFP (from when it was an ITP) can
be found here:
https://salsa.debian.org/aluaces-guest/company-irony
and I've created a backup copy in my personal namespace here:
https://salsa.debian.org/sten/company-irony

If Alberto or someone else doesn't want to carry the baton for this RFP
then I ought to be able to eventually get around to it.

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1026078: bullseye-pu: package ceph/14.2.21-1 CVE-2022-3650

[Salvatore Bonaccorso]

Thomas,

On Fri, Mar 17, 2023 at 05:37:54PM +, Jonathan Wiltshire wrote:
> Control: tag -1 moreinfo
> 
> On Wed, Dec 14, 2022 at 11:52:16AM +0100, Thomas Goirand wrote:
> > I have prepared an update for Ceph in Bullseye to address
> > CVE-2022-3650 (ie: ceph to root privilege escalation).
> > The security team already told me that there will be no DSA.
> 
> Your upload doesn't match the debdiff on this bug (see
> https://release.debian.org/proposed-updates/bullseye_diffs/ceph_14.2.21-1+deb11u1.debdiff).
> Is that intentional or did something go wrong?

Have you seen the question from Jonathan?

Right now it was not accepted, respectively hold back, see
https://release.debian.org/proposed-updates/stable.html and thus will
miss the next point release.

Regards,
Salvatore

Bug#1034865: compilation error on riscv64

[Michael Tokarev]

I forgot to give reference to the actual issue. Here it is:

https://buildd.debian.org/status/fetch.php?pkg=rust-virtiofsd=riscv64=1.5.1-2=1682451850=0
https://buildd.debian.org/status/package.php?p=rust-virtiofsd

I don't know rust so maybe the bug is mis-filed..

Thanks,

/mjt

Bug#1035040: unblock: node-jest/29.3.1~ds1+~cs70.48.25-2

[Yadd]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: node-j...@packages.debian.org
Control: affects -1 + src:node-jest

Please unblock package node-jest

[ Reason ]
"Breaks" field isn't enough for apt, it needs a "Replaces" to manage 
file conflicts. This update just adds this.

[ Risks ]
No risk here

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

Cheers,
Yadd

unblock node-jest/29.3.1~ds1+~cs70.48.25-2
diff --git a/debian/changelog b/debian/changelog
index 920d0a8..e577799 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+node-jest (29.3.1~ds1+~cs70.48.25-2) unstable; urgency=medium
+
+  * Duplicate Breaks field with Replaces (Closes: #1035008)
+
+ -- Yadd   Fri, 28 Apr 2023 06:42:41 +0400
+
 node-jest (29.3.1~ds1+~cs70.48.25-1) unstable; urgency=medium
 
   * New upstream version 29.3.1~ds1+~cs70.48.25 (updates @types/jest)
diff --git a/debian/control b/debian/control
index 90aeb56..cd2f3cb 100644
--- a/debian/control
+++ b/debian/control
@@ -203,6 +203,7 @@ Depends: ${misc:Depends}
  , node-types-node
 Breaks: node-rollup-plugin-terser (<< 7.0.2-6~)
  , jest (<< 29.1.2~ds1+~cs70.47.21-1~)
+Replaces: jest (<< 29.1.2~ds1+~cs70.47.21-1~)
 Provides: ${nodeJestWorker:Provides}
 Multi-Arch: foreign
 Description: Nodejs module for executing heavy tasks under forked processes in 
parallel

Bug#1035039: unblock: node-core-js/3.26.1-2

[Yadd]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: node-core...@packages.debian.org
Control: affects -1 + src:node-core-js

Please unblock package node-core-js

[ Reason ]
"Breaks" field isn't enough for apt, it needs a "Replaces" to manage 
file conflicts. This update just adds this.

[ Risks ]
No risk here

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

Cheers,
Yadd

unblock node-core-js/3.26.1-2
diff --git a/debian/changelog b/debian/changelog
index f85b17e..0c46ebf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+node-core-js (3.26.1-2) unstable; urgency=medium
+
+  * Team upload
+  * Duplicate Breaks fields with Replaces
+(Closes: #1034980, #1034989, 1035000, #1034947)
+
+ -- Yadd   Fri, 28 Apr 2023 06:52:43 +0400
+
 node-core-js (3.26.1-1) unstable; urgency=medium
 
   * Team upload
diff --git a/debian/control b/debian/control
index cce0fb8..955a902 100644
--- a/debian/control
+++ b/debian/control
@@ -41,6 +41,7 @@ Depends: ${misc:Depends}
  , node-semver
  , webpack
 Breaks: node-core-js (<< 3.21.1~)
+Replaces: node-core-js (<< 3.21.1~)
 Description: Node.js module to build a custom core-js
  For some cases could be useful to exclude some `core-js` features or
  generate a polyfill for target engines. This API helps conditionally include
@@ -52,6 +53,7 @@ Architecture: all
 Depends: ${misc:Depends}
 Multi-Arch: foreign
 Breaks: node-core-js (<< 3.21.1~)
+Replaces: node-core-js (<< 3.21.1~)
 Description: Modular version of core-js to load only required features
  core-js is a modular standard library for JavaScript. Includes polyfills for
  ECMAScript up to 2021: promises, symbols, collections, iterators, typed
@@ -65,6 +67,7 @@ Depends: ${misc:Depends}
  , node-semver
 Multi-Arch: foreign
 Breaks: node-core-js (<< 3.21.1~)
+Replaces: node-core-js (<< 3.21.1~)
 Description: data about the necessity of core-js
  core-js-compat contains data about the necessity of core-js modules and API
  for getting a list of required core-js modules by browserslist query.
@@ -74,6 +77,7 @@ Architecture: all
 Depends: ${misc:Depends}
 Multi-Arch: foreign
 Breaks: node-core-js (<< 3.21.1~)
+Replaces: node-core-js (<< 3.21.1~)
 Description: Modular standard library for JavaScript without global namespace 
pollution
  Includes polyfills for ECMAScript up to 2021: promises, symbols,
  collections, iterators, typed arrays, ECMAScript 7+ proposals, setImmediate,

Bug#1035038: unblock: node-strip-eof/3.0.0-5

[Yadd]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: node-strip-...@packages.debian.org
Control: affects -1 + src:node-strip-eof

Please unblock package node-strip-eof

[ Reason ]
"Breaks" field isn't enough for apt, it needs a "Replaces" to manage 
file conflicts. This update just adds this.

[ Risks ]
No risk here

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

Cheers,
Yadd

unblock node-strip-eof/3.0.0-5
diff --git a/debian/changelog b/debian/changelog
index 0f08d46..fbe8ec8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+node-strip-eof (3.0.0-5) unstable; urgency=medium
+
+  * Team upload
+  * Duplicate Breaks field with Replaces (Closes: #1034924)
+
+ -- Yadd   Fri, 28 Apr 2023 06:54:14 +0400
+
 node-strip-eof (3.0.0-4) unstable; urgency=medium
 
   * Team upload
diff --git a/debian/control b/debian/control
index 9b911b4..45de062 100644
--- a/debian/control
+++ b/debian/control
@@ -19,6 +19,7 @@ Architecture: all
 Depends: ${misc:Depends}
 Provides: ${nodejs:Provides}
 Breaks: node-execa (<< 5.1.1+dfsg+~cs19.3.6~)
+Replaces: node-execa (<< 5.1.1+dfsg+~cs19.3.6~)
 Multi-Arch: foreign
 Description: strip CR and LF characters from a string/buffer
  Strips CR and LF characters (i.e., it strips them away, if the string ends

Bug#1035037: unblock: node-parse5/7.1.2+dfsg-2

[Yadd]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: node-par...@packages.debian.org
Control: affects -1 + src:node-parse5

Please unblock package node-parse5

[ Reason ]
Missing Breaks+Replaces agaist node-cheerio (#1034984)

[ Risks ]
No risk

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

Cheers,
Yadd

unblock node-parse5/7.1.2+dfsg-2
diff --git a/debian/changelog b/debian/changelog
index 94e7e84..3719f73 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+node-parse5 (7.1.2+dfsg-2) unstable; urgency=medium
+
+  * Team upload
+  * Add missing Breaks+Replaces against node-cheerio (Closes: #1034984)
+
+ -- Yadd   Fri, 28 Apr 2023 06:58:41 +0400
+
 node-parse5 (7.1.2+dfsg-1) unstable; urgency=medium
 
   * Apply multi-arch hints (foreign)
diff --git a/debian/control b/debian/control
index 85e9fc2..c821db8 100644
--- a/debian/control
+++ b/debian/control
@@ -40,7 +40,9 @@ Depends: ${misc:Depends}
  , node-domhandler
  , node-parse5
 Breaks: node-jsdom (<< 20.0.0+repack1~)
+ , node-cheerio (<< 1.0.0~rc~10+repack-1~)
 Replaces: node-jsdom (<< 20.0.0+repack1~)
+ , node-cheerio (<< 1.0.0~rc~10+repack-1~)
 Description: node-htmlparser2 tree adapter
  Parse5 provides nearly everything needed when dealing with HTML. It's the
  fastest spec-compliant HTML parser for Node.js to date. It parses HTML the

Bug#1035036: unblock: node-npm-run-path/5.1.0+~4.0.0-8

[Yadd]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: node-npm-run-p...@packages.debian.org
Control: affects -1 + src:node-npm-run-path

[ Reason ]
"Breaks" field isn't enough for apt, it needs a "Replaces" to manage 
file conflicts. This update just adds this.

[ Risks ]
No risk here

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

Cheers,
Yadd

unblock node-npm-run-path/5.1.0+~4.0.0-8
diff --git a/debian/changelog b/debian/changelog
index 2c842dd..e2ff48a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+node-npm-run-path (5.1.0+~4.0.0-8) unstable; urgency=medium
+
+  * Team upload
+  * Duplicate Breaks field with Replaces (Closes: #1034945)
+
+ -- Yadd   Fri, 28 Apr 2023 07:08:33 +0400
+
 node-npm-run-path (5.1.0+~4.0.0-7) unstable; urgency=medium
 
   * Team upload
diff --git a/debian/control b/debian/control
index 56b3abf..dcd115f 100644
--- a/debian/control
+++ b/debian/control
@@ -20,5 +20,6 @@ Architecture: all
 Depends: ${misc:Depends}
 Provides: ${nodejs:Provides}
 Breaks: node-execa (<< 6.1.0+dfsg1~)
+Replaces: node-execa (<< 6.1.0+dfsg1~)
 Description: Get your PATH prepended with locally installed binaries
  Node.js is an event-based server-side JavaScript engine.

Bug#1035035: unblock: node-whatwg-fetch/3.6.2-7

[Yadd]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: node-whatwg-fe...@packages.debian.org
Control: affects -1 + src:node-whatwg-fetch

[ Reason ]
"Breaks" field isn't enough for apt, it needs a "Replaces" to manage
file conflicts. This update just adds this.

[ Risks ]
No risk here

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

Cheers,
Yadd

unblock node-whatwg-fetch/3.6.2-7
diff --git a/debian/changelog b/debian/changelog
index 125ed5c..6838dbe 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+node-whatwg-fetch (3.6.2-7) unstable; urgency=medium
+
+  * Team upload
+  * Duplicate Breaks field with Replaces (Closes: #1034933)
+
+ -- Yadd   Fri, 28 Apr 2023 07:13:09 +0400
+
 node-whatwg-fetch (3.6.2-6) unstable; urgency=medium
 
   * Add fix for rollup 3 (Closes: #1022653)
diff --git a/debian/control b/debian/control
index a61d511..371adc4 100644
--- a/debian/control
+++ b/debian/control
@@ -18,6 +18,7 @@ Architecture: all
 Depends: ${misc:Depends}
 Provides: libjs-whatwg-fetch (= ${binary:Version})
 Breaks: libjs-fetch (<< 3.5.0-2~)
+Replaces: libjs-fetch (<< 3.5.0-2~)
 Multi-Arch: foreign
 Description: window.fetch JavaScript polyfill
  The fetch() function is a Promise-based mechanism for programmatically making

Bug#1034971: lxd-client: missing Breaks+Replaces for lxc when upgrading from bullseye

[Mathias Gibbens]

Hi Helmut,

On Thu, 27 Apr 2023 15:00:05 +0200 Helmut Grohne  wrote:
> Attempting to unpack lxd-client/5.0.2-3+b2 from Debian bookworm
> on a minimal Debian bullseye with lxc/1:4.0.6-2+deb11u1
> installed, causes an unpack error from dpkg due to
> /usr/share/bash-completion/completions/lxc being contained in both packages.

  It looks like you're trying to install the version of lxd from
testing on a bullseye system? Mixing packages from different releases
isn't supported [1]. Furthermore, there hasn't yet been a stable
release of Debian that shipped lxd, so there's no way lxd-client might
be upgraded before lxc when upgrading from bullseye to bookworm. As
such, I don't know if it's really worthwhile to try to address this
situation that would only occur when the end-user has already broken
key assumptions about how their system is configured.

  The packaging of lxc was updated during the bookworm development
cycle to properly name its bash completion file and de-conflict with
lxd packaging [2]. Upgrading lxc packages from bullseye -> bookworm
should work smoothly; after the upgrade is complete users will then
also be able to `apt install lxd` if they so wish, and they won't
encounter the packaging conflict.

> Please ensure that lxd-client has sufficient Breaks and Replaces declarations.

  Does that address your concern?

Mathias

[1] -- https://wiki.debian.org/DontBreakDebian
[2] -- https://bugs.debian.org/1010843


signature.asc
Description: This is a digitally signed message part

Bug#1035034: unblock: libmodulemd/2.14.0-3

[Peter Pentchev]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: libmodul...@packages.debian.org, team+pkg-...@tracker.debian.org, 
r...@debian.org
Control: affects -1 + src:libmodulemd

Please unblock package libmodulemd; this is a pre-approval request
before I upload version 2.14.0-3 to unstable.

In version 2.13.0-1, I moved a file from the libmodulemd-dev package to
the gir1.2-modulemd-2.0 one, and I forgot to add the appropriate
Breaks+Replaces relationship. Helmut Grohne kindly reminded me in
the severity: serious bug #1034935 (thanks!).

[ Reason ]
Declare the Breaks+Replaces relationship so that dpkg will not fail to
unpack the new version of the gir-* package over the old version of
the -dev one.

[ Impact ]
An upgrade from bullseye to bookworm will break, see #1034935.

[ Tests ]
piuparts, I guess... no idea why I did not notice that :(

[ Risks ]
IMHO, no risk at all.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock libmodulemd/2.14.0-3
diff -Nru libmodulemd-2.14.0/debian/changelog 
libmodulemd-2.14.0/debian/changelog
--- libmodulemd-2.14.0/debian/changelog 2022-12-26 13:38:43.0 +0200
+++ libmodulemd-2.14.0/debian/changelog 2023-04-28 04:48:28.0 +0300
@@ -1,3 +1,10 @@
+libmodulemd (2.14.0-3) unstable; urgency=medium
+
+  * Declare that the gir-* package Breaks+Replaces older versions of
+the -dev one. Closes: #1034935
+
+ -- Peter Pentchev   Fri, 28 Apr 2023 04:48:28 +0300
+
 libmodulemd (2.14.0-2) unstable; urgency=medium
 
   * Use the GitHub API in the watch file.
diff -Nru libmodulemd-2.14.0/debian/control libmodulemd-2.14.0/debian/control
--- libmodulemd-2.14.0/debian/control   2022-12-26 13:38:30.0 +0200
+++ libmodulemd-2.14.0/debian/control   2023-04-28 04:45:57.0 +0300
@@ -70,6 +70,8 @@
 Section: introspection
 Architecture: any
 Multi-Arch: same
+Breaks: libmodulemd-dev (<< 2.13.0-1~)
+Replaces: libmodulemd-dev (<< 2.13.0-1~)
 Depends:
  ${gir:Depends},
  ${misc:Depends},


signature.asc
Description: PGP signature

Bug#1034939: librust---dev: missing Breaks+Replaces for librust-mio-dev when upgrading from bullseye

[Peter Green]

Summarising a number of bug reports by Helmut Ghrone:


Please ensure that librust---dev has sufficient Breaks and 
Replaces declarations.


The issue specifically appears to be that the breaks+replaces are declared
against a virtual package, it seems dpkg is honoring the breaks against the
virtual package but not the replaces. So it correctly marks the package from
stable as broken, but fails to actually unpack the package from testing.

Declaring against the physical package is also problematic becase Debian package
relationships don't support version ranges. What this would likely mean in
practice is it would be possible to co-install the "current" semver alongside
one previous semver, but it would not be possible to co-install two different
previous semvers.

Another option may be to use "Conflicts" instead of "Breaks". This should force
the old package to be upgraded or removed before the semver-specific package
can be unpacked.

I feel the timing of these bugs is very unfortunate. I don't object to
people running QA checks, but it's generally easier to deal with bugs if
they are reported earlier in the freeze process. The timing of these bugs
leaves little time for discussion if we are to get the fixes in before the
full freeze.

As I see it we have a few options to deal with this for bookworm.

1. Make debcargo Use Conflicts instead of Breaks.
2. Make debcargo declare Breaks/Replaces against the physical package
   version using a << dependency. This will allow the non-semver suffixed
   package to be installed alongside one semver-suffixed package, but with
   our current virtual packages scheme would not allow two semver-suffixed
   packages of the same crate to be coinstalled.
3. Add manual breaks/replaces for the versions in bullseye, this will
   paper over the issue for bullseye-bookworm upgrades, but is not a long
   term fix.

Do any other members of the rust team have an opinion on this? I'm
personally inclined towards option 1 and intend to implement it if
noone objects in the next couple of days.

Do the release team have an opinion on this? It looks like only one of
the packages involved (rust-env-logger-0.7) is a key package.

Bug#1035031: gnome-software: Manually checking for updates immediately finishes and does nothing

[asciiwolf]

Package: gnome-software
Version: 43.4-1

Clean Debian testing (amd64) system installed in a vm using latest iso. When 
opening GNOME Software, switching to the "Updates" tab and clicking the spinner 
button in header to check for new updates, the check immediately finishes 
(after a second or two) and does not seem to actually fetch any new update 
info. I am including a verbose gnome-software log from after clicking the 
button.

This part of the log may be related:
app invalid as no summary system/package/*/debian.www.debian-12/*

P.S. I have noticed the cdrom error in the log, however it looks like that 
disabling the cdrom source in /etc/apt/sources.list did not help.

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-software depends on:
ii  appstream0.16.1-1
ii  apt-config-icons 0.16.1-1
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gnome-software-common43.4-1
ii  gsettings-desktop-schemas43.0-1
ii  libadwaita-1-0   1.2.2-1
ii  libappstream40.16.1-1
ii  libc62.36-9
ii  libcairo21.16.0-7
ii  libfwupd21.8.12-2
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-4-1   4.8.3+ds-2
ii  libgtk3-perl 0.038-3
ii  libgudev-1.0-0   237-2
ii  libjson-glib-1.0-0   1.6.6-1
ii  libmalcontent-0-00.11.0-4
ii  libpackagekit-glib2-18   1.2.6-3
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpolkit-gobject-1-0122-3
ii  libsoup-3.0-03.2.2-2
ii  libxmlb2 0.3.10-2
ii  packagekit   1.2.6-3
ii  software-properties-gtk  0.99.30-4

Versions of packages gnome-software recommends:
ii  fwupd  1.8.12-2

Versions of packages gnome-software suggests:
pn  apt-config-icons-hidpi 
pn  gnome-software-plugin-flatpak  
pn  gnome-software-plugin-snap 

-- no debconf information

gs.log
Description: Binary data

Bug#1034412: release-notes: Information about manpages-l10n for bookworm release notes

[McIntyre, Vincent (S, Marsfield)]

On Thu, Apr 27, 2023 at 10:07:29PM +0200, Holger Wansing wrote:
>Control: tags -1 + patch
>
>I would like to propose the attached patch for this report (mostly grabbed
>from Helge's text).
>
>-- 
>Holger Wansing 
>PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

>diff --git a/en/whats-new.dbk b/en/whats-new.dbk
>index bf290b89..91a878c4 100644
>--- a/en/whats-new.dbk
>+++ b/en/whats-new.dbk
>@@ -414,6 +414,18 @@ Some descriptions of the ports: 
>https://www.debian.org/ports/
>   
> 
> 
>+
>+  
>+  Greatly expanded translations of man pages
>+  
>+Thank to many efforts of our translators, the translation of many

'Thanks' here

>+manpages has been greatly expanded (e.g. we have complete translation
>+of systemd user pages into German now) and various new languages have
>+been added (Czech, Danish, Greek, Finnish, Indonesian, Macedonian,
>+Norwegian, Russian, Serbian, Swedish, Ukranian and Vietnamesian).

I think 'Vietnamese' is correct here.

Kind regards
Vince

Bug#1034205: wayout: does not do anything

[Antoine Beaupré]

On 2023-04-22 20:09:57, Anjandev Momi wrote:
> Hi Antoine!
>
>> I can't figure out how to use this program.
>>
>> The upstream README (which is actually not shipped with the Debian
>> package) has a few examples:
>> So, how does one use this?
>
> You can find a better example of wayout usage here:
>
> https://git.sr.ht/~mil/sxmo-utils/tree/f630b2bbdb712f0a3bb66778efcdf196d1d093e4/item/configs/default_hooks/sxmo_hook_desktop_widget.sh
>
> I always modify the above script because the script works out of the box on
> every device I've tried Sxmo on.
>
> I agree the wayout *man page* should include a better example of how to
> make wayout work. If you find the time, please do some trial and error
> and send us a patch with your improved wayout man page here:
>
> https://sxmo.org/contribute
>
> Alternatively, conky got wayland support recently and Sxmo 1.14.1 supports
> conky. I like wayout cause old habits die hard.

Right. :) So my use case is I want to create a pop-up in a status bar
that doesn't quite support this. Having to run a process in the
background for this is not exactly the best scenario, as I'd need to
implement process management in the thing, which is a little sub par (as
opposed to just forking a process and let it kill itself based on user
interaction).

So I guess it's more something I should check with the status bar...

a.
-- 
The lazy man does not stand in the way of progress. When he sees
progress roaring down upon him he steps nimbly out of the way
 - Christopher Morley, "On Laziness"

Bug#1035030: nfs-utils: nfsconvert.py is missing support for the syslog option

[Mark Grimes]

Source: nfs-utils
Version: 1:2.6.2-4
Severity: normal
X-Debbugs-Cc: mark.gri...@ixsystems.com

Dear Maintainer,

While testing upgrades I found the nfsconvert.py script would fail when
the '-s' or '--syslog' option was included with RPCNFSDOPTS.

Here is the patch file with what I believe are the necessary changes:

--- nfsconvert.py   2023-04-27 15:46:24.628347999 -0700
+++ /usr/share/nfs-common/nfsconvert.py 2023-01-11 12:41:40.0 -0800
@@ -15,7 +15,7 @@
 # options for nfsd found in RPCNFSDOPTS
 OPTS_NFSD = 'dH:p:rR:N:V:stTuUG:L:'
 LONG_NFSD = ['debug', 'host=', 'port=', 'rdma=', 'nfs-version=', 
'no-nfs-version=',
- 'syslog', 'tcp', 'no-tcp', 'udp', 'no-udp', 'grace-time=', 
'lease-time=']
+ 'tcp', 'no-tcp', 'udp', 'no-udp', 'grace-time=', 'lease-time=']
 CONV_NFSD = {'-d': (CONF_NFS, 'nfsd', 'debug', 'all'),
  '-H': (CONF_NFS, 'nfsd', 'host', ','),
  '-p': (CONF_NFS, 'nfsd', 'port', '$1'),
@@ -23,7 +23,6 @@
  '-R': (CONF_NFS, 'nfsd', 'rdma', '$1'),
  '-N': (CONF_NFS, 'nfsd', 'vers$1', 'n'),
  '-V': (CONF_NFS, 'nfsd', 'vers$1', 'y'),
- '-s': (CONF_NFS, 'nfsd', 'syslog', '1'),
  '-t': (CONF_NFS, 'nfsd', 'tcp', '1'),
  '-T': (CONF_NFS, 'nfsd', 'tcp', '0'),
  '-u': (CONF_NFS, 'nfsd', 'udp', '1'),
@@ -37,7 +36,6 @@
  '--rdma': (CONF_NFS, 'nfsd', 'rdma', '$1'),
  '--no-nfs-version': (CONF_NFS, 'nfsd', 'vers$1', 'n'),
  '--nfs-version': (CONF_NFS, 'nfsd', 'vers$1', 'y'),
- '--syslog': (CONF_NFS, 'nfsd', 'syslog', '1'),
  '--tcp': (CONF_NFS, 'nfsd', 'tcp', '1'),
  '--no-tcp': (CONF_NFS, 'nfsd', 'tcp', '0'),
  '--udp': (CONF_NFS, 'nfsd', 'udp', '1'),

I have not done any additional testing.


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages nfs-common depends on:
ii  adduser3.132
ii  init-system-helpers1.65.2
ii  keyutils   1.6.3-2
ii  libc6  2.36-9
ii  libcap21:2.66-3
ii  libcom-err21.47.0-2
ii  libdevmapper1.02.1 2:1.02.185-2
ii  libevent-core-2.1-72.1.12-stable-8
ii  libgssapi-krb5-2   1.20.1-1+b1
ii  libkeyutils1   1.6.3-2
ii  libkrb5-3  1.20.1-1+b1
ii  libmount1  2.38.1-5+b1
ii  libnfsidmap1   1:2.6.2-4
ii  libtirpc3  1.3.3+ds-1
ii  libwrap0   7.6.q-32
ii  python33.11.2-1+b1
ii  rpcbind1.2.6-6+b1
ii  sysvinit-utils [lsb-base]  3.06-4
ii  ucf3.0043+nmu1

Versions of packages nfs-common suggests:
pn  open-iscsi  
pn  watchdog

Versions of packages nfs-kernel-server depends on:
ii  keyutils   1.6.3-2
ii  libblkid1  2.38.1-5+b1
ii  libc6  2.36-9
ii  libcap21:2.66-3
ii  libevent-core-2.1-72.1.12-stable-8
ii  libsqlite3-0   3.40.1-2
ii  libtirpc3  1.3.3+ds-1
ii  libuuid1   2.38.1-5+b1
ii  libwrap0   7.6.q-32
ii  netbase6.4
ii  nfs-common 1:2.6.2-4
ii  sysvinit-utils [lsb-base]  3.06-4
ii  ucf3.0043+nmu1

Versions of packages nfs-kernel-server recommends:
ii  python3   3.11.2-1+b1
ii  python3-yaml  6.0-3+b2

Versions of packages nfs-kernel-server suggests:
ii  procps  2:4.0.2-3

Bug#1032899: unblock: rocm-hipamd/5.2.3-6

[Christian Kastner]

Control: tags -1 - moreinfo

Hi Paul,

sorry this took a while.

On 2023-04-22 13:34, Paul Gevers wrote:
> On 21-04-2023 23:43, Christian Kastner wrote:
>> The only way to do that with llvm-toolchain-15 from testing is by
>> changing the dependency libclang-rt-15-dev back to
>> libclang-common-15-dev (the pre-split version).
> 
> Hmm, so this complicates things. Can you do this change in unstable, or
> would it be broken in unstable?

Luckily, the newer llvm-toolchain-15 is only needed for building tests.
These aren't run (cannot be run) by buildds, so by dropping them for
now, we can drop the problematic build dependency.

And for bin:hipcc, the only binary package affected, I believe the
dependency on libclang-rt-15-dev was wrong anyway, there's a broken
upgrade path for the files that moved in the dependency. The correct
specification  should be:

libclang-common-15-dev (<< 1:15.0.6-5~exp1) | libclang-rt-15-dev (>=
1:15:0.6-5~exp1)

>> If that is an option, I could prepare an upload, and also reduce out
>> whatever other changes you don't feel comfortable with in the larger
>> diff.
> 
> That would be good. Can you also share the minimal delta with the
> current version in unstable? I'll check if that's acceptable.

I've attached the new diff as 01 (FULL) but its d/changelog is noisy,
reflecting the ongoing development process we had in this younger library.

So I split that diff into 02 (patches) and 03 (NOT-patches), also attached.

02_rocm-hipamd-patches.diff
There were 5 patches added (Jan:4 Feb:1), and these represent fixes that
really must be in the package, but were held up by our dependency. One
patch was dropped. Many others just got DEP3 headers.

03_rocm-NOT-hipamd-patches.diff
The diff is not as large as d/changelog suggests. I've summarized all
the changes below, with (*) marking changes that really should get into
testing, and (+) marking changes that aren't strictly needed.

  * Build Depends added: llvm-15, file
  * (RC #1032677) Depends fixed: bin:libamdhip64-5, bin:libamdhip64-dev
  * Depends fixed: bin:hipcc (as described above)
  * *.install files fixed (+ one d/rules change), not-installed added
  * Build flags fixed in d/rules
  * Another RPATH removed
  * Updates to d/copyright

  + Build Depends added: rocminfo (just for tests)
  + Reduce architectures to amd64, arm64, ppc64el (the only platforms
with the necessary drivers)
  + Update Standards-Version from 4.6.1 to 4.6.2
  + autopkgtest added

Would a package with just the patches and the (*) changes be acceptable?

Best,
Christiandiff -Nru rocm-hipamd-5.2.3/debian/changelog rocm-hipamd-5.2.3/debian/changelog
--- rocm-hipamd-5.2.3/debian/changelog  2022-10-20 21:20:33.0 +0200
+++ rocm-hipamd-5.2.3/debian/changelog  2023-04-25 19:50:14.0 +0200
@@ -1,3 +1,85 @@
+rocm-hipamd (5.2.3-7) UNRELEASED; urgency=medium
+
+  * hipcc: Fix Depends to enable transition from split clang package
+  * Drop building of tests, and libclang-rt-15-dev dependency
+
+ -- Christian Kastner   Tue, 25 Apr 2023 19:50:14 +0200
+
+rocm-hipamd (5.2.3-6) unstable; urgency=medium
+
+  * Reduce arch to amd64, arm64, ppc64el
+  * libamdhip64-5: Add dependency on libamd-comgr2 (Closes: #1032677)
+  * Add myself to Uploaders
+  * Fix Maintainer (same list, different name)
+
+ -- Christian Kastner   Fri, 10 Mar 2023 23:38:51 +0100
+
+rocm-hipamd (5.2.3-5) unstable; urgency=medium
+
+  * d/{libamdhip64-dev,rules}: fix version file
+Closes: #1031264
+  * add d/p/0020-replace-x86_64-with-variables.patch
+to fix build on aarch64
+  * d/control: add file to hipcc dependencies
+  * d/control: add dependencies for find_package(hip)
+Closes: #1031538
+  * add d/p/0021-fix-default-cmake-build-on-unsupported-gpus.patch
+to enable gpu arch autodetection with find_package(hip)
+  * d/not-installed: ignore doxygen docs
+  * d/p/000{4,8,9}*.patch: change hip-lang cmake files,
+to partially fix #1031540
+  * d/copyright: update copyright date
+  * d/control: add self to uploaders
+  * cleanup patch metadata
+
+ -- Cordell Bloor   Sun, 19 Feb 2023 03:51:26 -0700
+
+rocm-hipamd (5.2.3-4) unstable; urgency=medium
+
+  * d/t/hipcc: also skip when no kfd driver is loaded.
+
+ -- Étienne Mollier   Sat, 21 Jan 2023 12:54:49 +0100
+
+rocm-hipamd (5.2.3-3) unstable; urgency=medium
+
+  * d/control: build depends on libclang-rt-15-dev.
+  * d/control: hipcc depends on libclang-rt-15-dev.
+  * d/t/hipcc: add; basic script testing hipcc.
+  * d/t/hipconfig: add; script skipping hipconfig if no amdgpu is available.
+  * d/t/control: add hipcc to superficial autopkgtests.
+  * d/t/control: run the d/t/hipconfig test script instead of the command;
+this allows us to trigger conditions for when hardware is not available
+and the script has to be skipped.
+
+ -- Étienne Mollier   Wed, 18 Jan 2023 20:35:17 +0100
+
+rocm-hipamd (5.2.3-2) unstable; urgency=medium
+
+  [ Cordell Bloor ]
+  * d/patches: add 0020-hipcc-remove-rpath-flags.patch
+

Bug#1035029: l10n broken

[gitne]

Package: binutils-aarch64-linux-gnu
Version: 2.35.2-2

No binutil tool makes use of `LC_MESSAGES` (.mo) files, although they
have been correctly installed (via binutils-common) and all required
glibc locales have been generated and environment variables set. For
example,

$ LANG=fr.UTF-8 gettext ld 'out of memory'
plus de mémoire

$ LANG=de.UTF-8 gettext ld 'out of memory'
Zu wenig Speicher

works as expected. This leads to the conclusion that something went
wrong during the build. Did you configure `HAVE_LC_MESSAGES`?
Interestingly enough, the same behavior can be observed with Flathub’s
latest binutils 2.38 builds. Hence, this may also be an upstream issue.

Actually, all binutils-*-linux-gnu since version 2.35.2 may be affected.

Bug#1035028: unblock: iso-codes/4.15.0-1

[Dr. Tobias Quathamer]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: affects -1 + src:iso-codes

Please unblock package iso-codes.

The package provides translations for country and language names, used 
by e. g. the Debian installer.


Apart from the minimal needed changes to configure.ac (version number) 
and the changelog, the new upstream version consists only of translation 
updates and fixes, only touching .po files.


However, the debdiff is huge, so I'm waiting for your approval before 
uploading to unstable.


Regards,
Tobias


unblock iso-codes/4.15.0-1


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034566: unblock: isc-dhcp/4.4.3-P1-1.1

[Santiago R.R.]

El 27/04/23 a las 07:36, Paul Gevers escribió:
> Control: tags -1 confirmed moreinfo
> Control: retitle -1 unblock: isc-dhcp/4.4.3-P1-2
> 
> On 18-04-2023 14:11, Santiago R.R. wrote:
> > 2. This is the autopkgtest included in this request applied to the
> > current version in testing:
> 
> Minor question: I *think* you are configuring the test to use the internet
> (nameserver 8.8.8.8). If that's true, please add the `needs-internet`
> restriction. (Or maybe it doesn't need to be configured like that.

Not really. The test just tests if the namespace's resolv.conf is
finally (over)written with the nameserver provided by the dhcp server.
No DNS queries are done during the test, even less querying any resolver
on internet.
I don't see the need to add the `needs-internet` restriction, but please
let me know if you think otherwise.

> 
> > unblock isc-dhcp/4.4.3-P1-1.1
> 
> That version is already in testing. I have fixed the title too (which, for
> next time, could have done with the word `pre-approval` or similar).

Thanks. I just let reportbug fill that version. And I always forgot the
unblock semantics.

> 
> Anyways, please go ahead.
> 

Thank you. I'll just wait your opinion about the above mentioned
restriction.

> Paul

Cheers,

 -- S

Bug#1034740: boost1.74: reproducible builds: build date and time embedded in .html documentation

[Vagrant Cascadian]

Control: clone 1034740 -1
Control: reassign -1 boost1.81
Control: retitle -1 boost1.81: reproducible builds: build date and time 
embedded in .html documentation
Control: tags -1 patch

Issue and patch is also valid for boost1.81!

On 2023-04-22, Vagrant Cascadian wrote:
> From 7c9c189ea32470cd683939c11fabf78f0b2f3f17 Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian 
> Date: Sat, 22 Apr 2023 19:53:22 -0700
> Subject: [PATCH] Remove timestamps and dates from documentation.
>
> https://reproducible-builds.org/docs/timestamps/
> ---
>  libs/circular_buffer/doc/circular_buffer.qbk |  2 --
>  libs/units/doc/units.qbk |  1 -
>  tools/boostbook/xsl/html-base.xsl| 22 
>  tools/quickbook/doc/block.qbk|  4 ++--
>  4 files changed, 2 insertions(+), 27 deletions(-)
>
> diff --git a/libs/circular_buffer/doc/circular_buffer.qbk 
> b/libs/circular_buffer/doc/circular_buffer.qbk
> index a7177e4c..217c42b6 100644
> --- a/libs/circular_buffer/doc/circular_buffer.qbk
> +++ b/libs/circular_buffer/doc/circular_buffer.qbk
> @@ -596,8 +596,6 @@ Paul A. Bristow refactored the documentation in 2013 to 
> use the full power of Qu
>  
>  [section:version_id Documentation Version Info]
>  
> -Last edit to Quickbook file __FILENAME__ was at __TIME__ on __DATE__.
> -
>  [tip This should appear on the pdf version
>  (but may be redundant on a html version where the last edit date is on the 
> first (home) page).]
>  
> diff --git a/libs/units/doc/units.qbk b/libs/units/doc/units.qbk
> index 0c7345fc..b160ef21 100644
> --- a/libs/units/doc/units.qbk
> +++ b/libs/units/doc/units.qbk
> @@ -1309,7 +1309,6 @@ the design and implementation of this library.
>  
>  __boostroot
>  
> -Last edit to Quickbook file __FILENAME__ was at __TIME__ on __DATE__.
>  
>  [tip This should appear on the pdf version (but may be redundant on html).]
>  [/ Useful on pdf version. See also Last revised timestamp on first page of 
> html version.]
> diff --git a/tools/boostbook/xsl/html-base.xsl 
> b/tools/boostbook/xsl/html-base.xsl
> index a1031710..cfba8727 100644
> --- a/tools/boostbook/xsl/html-base.xsl
> +++ b/tools/boostbook/xsl/html-base.xsl
> @@ -234,28 +234,6 @@ set   toc,title
>  
> select="normalize-space($revision-node/attribute::rev:last-revision)"/>
>  
> -
> -  
> -
> -  Last revised: 
> -  
> -
> -  
> -
> -
> -  
> -
> -  
> -
> -
> -  
> -
> -  
> -
> -  
> -
> -  
> -
>
>  
>  
> diff --git a/tools/quickbook/doc/block.qbk b/tools/quickbook/doc/block.qbk
> index dbfdb8d2..bcf3f406 100644
> --- a/tools/quickbook/doc/block.qbk
> +++ b/tools/quickbook/doc/block.qbk
> @@ -601,8 +601,8 @@ Quickbook has some predefined macros that you can already 
> use.
>  
>  [table Predefined Macros
>  [[Macro]   [Meaning]   [Example]]
> -[[[^\__DATE__]][Today's date]  [__DATE__]]
> -[[[^\__TIME__]][The current time]  [__TIME__]]
> +[[[^\__DATE__]][Today's date]  [2022-04-20]]
> +[[[^\__TIME__]][The current time]  [01:42:48 PM]]
>  [[[^\__FILENAME__]][Quickbook source filename] [__FILENAME__]]
>  ]
>  
> -- 
> 2.39.2


signature.asc
Description: PGP signature

Bug#1033730: [release-notes] adduser changes in bookworm

[Holger Wansing]

I think, we don't want to have all of the text from the bugreport in the
release-notes, it's much to specific stuff for the majority of people IMO.

Maybe we just want some more generic text like:



Extensive changes in adduser for bookworm

There have been several changings in adduser during the development cycle of
bookworm. Users might be affected by this, and also developers of other 
packages, if they use adduser in their maintainer scripts.

Remember to check /usr/share/doc/adduser/NEWS.Debian
and /usr/shade/doc/adduser/README.Debian as well as the manual pages that come
with the package for detailed information.

Developers also can find out there, which changes are planned for Debian's next
release after bookworm (trixie), enabling them to do necessary changes to their
packages and code during the bookworm cycle to get ready for trixie.


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1034412: release-notes: Information about manpages-l10n for bookworm release notes

[Holger Wansing]

Hi,

Paul Gevers  wrote (Thu, 27 Apr 2023 22:17:40 +0200):
> Hi,
> 
> On 27-04-2023 22:07, Holger Wansing wrote:
> > Control: tags -1 + patch
> > 
> > I would like to propose the attached patch for this report (mostly grabbed
> > from Helge's text).
> 
> +  Greatly expanded translations of man pages
> +  
> +Thank to many efforts of our translators, the translation of many
> 
> That feels like one many too many for one sentence.
> 
> +manpages has been greatly expanded (e.g. we have complete 
> translation
> +of systemd user pages into German now) and various new 
> languages have
> +been added (Czech, Danish, Greek, Finnish, Indonesian, Macedonian,
> +Norwegian, Russian, Serbian, Swedish, Ukranian and Vietnamesian).
> 
> I happen to know that "Norwegian" is ambiguous? There's Bokmål and 
> Nynorsk. I assume the former is meant, maybe "Norwegian (Bokmål)"?

Looking at the repo
https://salsa.debian.orgNorwegian 
(Bokmål/manpages-l10n-team/manpages-l10n/-/tree/master/po
there is a folder for Norwegian Bokmål (nb), but none for Norwegian Nynorsk 
(nn),
so it looks you are right.

> 
> My spelling checker also suggests Ukrainian and Vietnamese.

Good catch. Correct.

> Paul


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1034412: release-notes: Information about manpages-l10n for bookworm release notes

[Paul Gevers]

Hi,

On 27-04-2023 22:07, Holger Wansing wrote:

Control: tags -1 + patch

I would like to propose the attached patch for this report (mostly grabbed
from Helge's text).


+  Greatly expanded translations of man pages
+  
+Thank to many efforts of our translators, the translation of many

That feels like one many too many for one sentence.

+manpages has been greatly expanded (e.g. we have complete 
translation
+of systemd user pages into German now) and various new 
languages have

+been added (Czech, Danish, Greek, Finnish, Indonesian, Macedonian,
+Norwegian, Russian, Serbian, Swedish, Ukranian and Vietnamesian).

I happen to know that "Norwegian" is ambiguous? There's Bokmål and 
Nynorsk. I assume the former is meant, maybe "Norwegian (Bokmål)"?


My spelling checker also suggests Ukrainian and Vietnamese.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034248: release-notes: Document that GTK4 apps are not accessible with screen reader

[Holger Wansing]

Hi Paul,

Paul Gevers  wrote (Thu, 27 Apr 2023 22:10:16 +0200):
> 
> + If you depend on a screen reader and want to upgrade to , 
> we suggest
> + that you install a desktop like MATE instead of GNOME.
> 
> I guess our recommendation also holds for new installs. So maybe leave 
> out the "and want to upgrade to bookworm" part?

That part was not existing in the original report, but added by me :-)
so - yes, I guess your argument counts.


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1034248: release-notes: Document that GTK4 apps are not accessible with screen reader

[Paul Gevers]

Hi Holger,

Thanks for doing the leg work.

On 27-04-2023 21:50, Holger Wansing wrote:
+  Accessibility: GNOME GTK4 apps with reduced screen reader 
support

+  
+   Many GNOME apps have switched from GTK3 to GTK4. Sadly, GTK4 is much
+   less accessible with the Orca screen reader compared to GTK3.
+  

(Tiny nitpick, we normally put those ^ one two lines.)

+	If you depend on a screen reader and want to upgrade to , 
we suggest

+   that you install a desktop like MATE instead of GNOME.

I guess our recommendation also holds for new installs. So maybe leave 
out the "and want to upgrade to bookworm" part?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034412: release-notes: Information about manpages-l10n for bookworm release notes

[Holger Wansing]

Control: tags -1 + patch

I would like to propose the attached patch for this report (mostly grabbed
from Helge's text).


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
diff --git a/en/whats-new.dbk b/en/whats-new.dbk
index bf290b89..91a878c4 100644
--- a/en/whats-new.dbk
+++ b/en/whats-new.dbk
@@ -414,6 +414,18 @@ Some descriptions of the ports: https://www.debian.org/ports/
   
 
 
+
+  
+  Greatly expanded translations of man pages
+  
+Thank to many efforts of our translators, the translation of many
+manpages has been greatly expanded (e.g. we have complete translation
+of systemd user pages into German now) and various new languages have
+been added (Czech, Danish, Greek, Finnish, Indonesian, Macedonian, 
+Norwegian, Russian, Serbian, Swedish, Ukranian and Vietnamesian).
+  
+
+
 
   Something
   

Bug#1035026: singularity-container: CVE-2023-30549

[Salvatore Bonaccorso]

Source: singularity-container
Version: 3.11.0+ds1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for singularity-container.
The issue originally reference for apptainer is affecting in same way
singularity.

CVE-2023-30549[0]:
| Apptainer is an open source container platform for Linux. There is an
| ext4 use-after-free flaw that is exploitable through versions of
| Apptainer  1.1.0, installations that include apptainer-suid 
| 1.1.8, and all versions of Singularity in their default configurations
| on older operating systems where that CVE has not been patched. That
| includes Red Hat Enterprise Linux 7, Debian 10 buster (unless the
| linux-5.10 package is installed), Ubuntu 18.04 bionic and Ubuntu 20.04
| focal. Use-after-free flaws in the kernel can be used to attack the
| kernel for denial of service and potentially for privilege escalation.
| Apptainer 1.1.8 includes a patch that by default disables mounting of
| extfs filesystem types in setuid-root mode, while continuing to allow
| mounting of extfs filesystems in non-setuid "rootless" mode using
| fuse2fs. Some workarounds are possible. Either do not install
| apptainer-suid (for versions 1.1.0 through 1.1.7) or set `allow setuid
| = no` in apptainer.conf (or singularity.conf for singularity
| versions). This requires having unprivileged user namespaces enabled
| and except for apptainer 1.1.x versions will disallow mounting of sif
| files, extfs files, and squashfs files in addition to other, less
| significant impacts. (Encrypted sif files are also not supported
| unprivileged in apptainer 1.1.x.). Alternatively, use the `limit
| containers` options in apptainer.conf/singularity.conf to limit sif
| files to trusted users, groups, and/or paths, and set `allow container
| extfs = no` to disallow mounting of extfs overlay files. The latter
| option by itself does not disallow mounting of extfs overlay
| partitions inside SIF files, so that's why the former options are also
| needed.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-30549
https://www.cve.org/CVERecord?id=CVE-2023-30549
[1] 
https://github.com/apptainer/apptainer/security/advisories/GHSA-j4rf-7357-f4cg

Regards,
Salvatore

Bug#1035025: chkrootkit.service does not run every day if system gets suspended

[richardn]

Package: chkrootkit
Version: 0.57-2+b1
Severity: normal
X-Debbugs-Cc: richard...@gmail.com


/lib/systemd/system/chkrootkit.timer contains -

# then run every day
OnUnitActiveSec=24h

This is a monotonic timer. According to systemd.timer manpage -

These are monotonic timers, independent of wall-clock time and
timezones. If the computer is temporarily suspended, the monotonic
clock generally pauses, too.

On my system, which is usually suspended overnight, the chkrootkit.service has 
not run since last upgrading over 2 days ago.

~$ date
Thu 27 Apr 14:40:00 CEST 2023
~$ systemctl status chkrootkit.timer | more
● chkrootkit.timer - chkrootkit daily timer
 Loaded: loaded (/lib/systemd/system/chkrootkit.timer; enabled; preset: enab
led)
 Active: active (waiting) since Tue 2023-04-25 05:51:39 CEST; 2 days ago
  Until: Tue 2023-04-25 05:51:39 CEST; 2 days ago
Trigger: Fri 2023-04-28 06:04:11 CEST; 15h left
   Triggers: ● chkrootkit.service
   Docs: man:chkrootkit(8)
~$
~$ #suspended for about one hour
~$
~$ date
Thu 27 Apr 17:46:01 CEST 2023
~$ systemctl status chkrootkit.timer | more
● chkrootkit.timer - chkrootkit daily timer
 Loaded: loaded (/lib/systemd/system/chkrootkit.timer; enabled; preset: enab
led)
 Active: active (waiting) since Tue 2023-04-25 05:51:39 CEST; 2 days ago
  Until: Tue 2023-04-25 05:51:39 CEST; 2 days ago
Trigger: Fri 2023-04-28 07:37:58 CEST; 13h left
   Triggers: ● chkrootkit.service
   Docs: man:chkrootkit(8)

The trigger is further in the future. I guess the timer will expire eventually, 
but to preserve the old crontab behaviour and run every day, perhaps a realtime 
(i.e. wallclock) timer should be used e.g

OnCalendar=daily


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages chkrootkit depends on:
ii  libc6  2.36-9

Versions of packages chkrootkit recommends:
ii  anacron2.3-36
ii  binutils   2.40-2
ii  exim4-daemon-light [mail-transport-agent]  4.96-14
ii  iproute2   6.1.0-2
ii  mailutils [mailx]  1:3.15-4
ii  net-tools  2.10-0.1
ii  procps 2:4.0.2-3
ii  systemd-sysv   252.6-1

chkrootkit suggests no packages.

-- no debconf information

Bug#1034248: release-notes: Document that GTK4 apps are not accessible with screen reader

[Holger Wansing]

Control: tags -1 + patch

I think, the text proposed in this report is almost fit for publication.
So I have prepared a patch based on that.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
diff --git a/en/issues.dbk b/en/issues.dbk
index 1de96461..dd96f5cc 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -293,6 +293,17 @@
   
 
 
+
+  Accessibility: GNOME GTK4 apps with reduced screen reader support
+  
+	Many GNOME apps have switched from GTK3 to GTK4. Sadly, GTK4 is much
+	less accessible with the Orca screen reader compared to GTK3.
+  
+	If you depend on a screen reader and want to upgrade to , we suggest
+	that you install a desktop like MATE instead of GNOME.
+  
+
+
 
   Things to do post upgrade before rebooting
   

Bug#1035024: unblock: nvidia-cudnn/8.7.0.84~cuda11.8+1 (pre-approval)

[M. Zhou]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: nvidia-cu...@packages.debian.org
Control: affects -1 + src:nvidia-cudnn

Please unblock package nvidia-cudnn. Not yet uploaded to unstable,
just asking for a pre-approval.

[ Reason ]

Our current package version in testing is 8.5.0.96~cuda11.7,
but the nvidia-cuda-toolkit version in testing is 11.8.89~11.8.0-2.
So there is a little minor version mismatch in the cuda version
(one 11.7, and the other 11.8).

This package is a downloader script that downloads the Nvidia
binary blob releases of the cuDNN library, and installs the library
to the system directories for building reverse dependencies.

So, generally updating the package is simply to update the binary
tarball URL in the script, along with the exact version number,
which is very trivial.

But unfortunately, during the cuda11.7 to cuda11.8 update,
I also introduced many changes to the package to the maintainer
scripts to let the package correctly support the pytorch-cuda build.
I'm the upstream of this package, and this looks like a low risk
update to me. But I'm not sure how the release team will think.
So asking for uploading permission in advance.

[ Impact ]
(What is the impact for the user if the unblock isn't granted?)

Nearly no impact. This package is new and does not exist
in the previous stable releases. To the best of my knowledge,
there is only one tentative reverse dependency pytorch-cuda,
which is not present in testing.

[ Tests ]
(What automated or manual tests cover the affected code?)

The updated package is now able to correctly support the
build of pytorch-cuda. I tested the built package with both
Nvidia MX250 (laptop) and RTX 2060 (laptop) GPUs. It works
correctly.

[ Risks ]

There is a small risk. The additional code is very simple.
It does not have reverse dependency in testing. There
is no alternative to this package. I'm the upstream author
of the script, and I can provide stable updates on my own
even if something goes wrong.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
(Anything else the release team should know.)

The debdiff contains necessary changes to make the package
correctly support the pytorch-cuda build (with sbuild).

Specifically:

1. A fake library is compiled (from a nearly empty C file cudnn-fake.c)
   with the soname of the library to be downloaded. This seems to be
   the only way to make apt/dpkg believe that the libcudnn.so.* is
   really provided by this binary package.
   This solves the libcudnn_* cannot be found in any system package
   error from dh_shlibdeps.

2. Added curl as an alternative binary blob downloader.

3. Updated the postinst and prerm script for handling installed files.
In the current testing version, when we want to remove this package,
we use some manually written glob patterns to remove the downloaded
cudnn library. This implementation is not very safe when the user manually
install another instance of cudnn to the system. The glob pattern will also
include them to make them removed during postrm.

In the proposed version (see debdiff), I record a list of files that are 
installed
from the tarball to the system. And the postrm process will use the exact
recorded installation paths for removal. I think this is a safer 
implementation
than removal by glob pattern match.

4. debconf template default choice is changed to "I Agree".
This package is in non-free section. Only by setting the debconf default 
choice
to "I Agree", can we correctly build pytorch-cuda in sbuild without the 
cuDNN
libraries not downloaded but the bin:nvidia-cudnn package installed.

5. More code comments (maintainence notes) in the script, and the upgraded
binary blob URL.

unblock nvidia-cudnn/8.7.0.84~cuda11.8+1
Thank you for using reportbug

diff -Nru nvidia-cudnn-8.5.0.96~cuda11.7/cudnn-fake.c nvidia-cudnn-8.7.0.84~cuda11.8/cudnn-fake.c
--- nvidia-cudnn-8.5.0.96~cuda11.7/cudnn-fake.c	1969-12-31 19:00:00.0 -0500
+++ nvidia-cudnn-8.7.0.84~cuda11.8/cudnn-fake.c	2023-03-21 18:49:17.0 -0400
@@ -0,0 +1,8 @@
+/* This is a fake library. We want dpkg-shlibdeps to believe that the
+ * shared object libcudnn.so.8 is provided in this package.
+ */
+int
+__cudnn_fake_library__()
+{
+return 0;
+}
diff -Nru nvidia-cudnn-8.5.0.96~cuda11.7/debian/changelog nvidia-cudnn-8.7.0.84~cuda11.8/debian/changelog
--- nvidia-cudnn-8.5.0.96~cuda11.7/debian/changelog	2023-02-17 23:24:39.0 -0500
+++ nvidia-cudnn-8.7.0.84~cuda11.8/debian/changelog	2023-03-21 18:49:17.0 -0400
@@ -1,3 +1,33 @@
+nvidia-cudnn (8.7.0.84~cuda11.8) experimental; urgency=medium
+
+  * Upgrade to cuDNN v8.7.0.84
+  * Set the debconf template default choice to "I Agree".
+Only in this way can we use the binary 

Bug#1035023: cloud-init: CVE-2023-1786

[Salvatore Bonaccorso]

Source: cloud-init
Version: 22.4.2-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for cloud-init.

CVE-2023-1786[0]:
| Sensitive data could be exposed in logs of cloud-init before version
| 23.1.2. An attacker could use this information to find hashed
| passwords and possibly escalate their privilege.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-1786
https://www.cve.org/CVERecord?id=CVE-2023-1786
[1] https://bugs.launchpad.net/cloud-init/+bug/2013967
[2] 
https://github.com/canonical/cloud-init/commit/a378b7e4f47375458651c0972e7cd813f6fe0a6b

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#741537: pssh: IPv6 host address processing broken

[Preuße]

Control: tags -1 + pending

On 27.04.2023 19:23, Ivan Vilata i Balaguer wrote:

Preuße, Hilmar (2023-03-23 23:01:22 +0100) wrote:

On 13.03.2014 16:37, Ivan Vilata i Balaguer wrote:


Hi,


The handling of IPv6 addresses is broken since the ``parse_host_entry()``
function in ``psshutil.py`` thinks the colons in it are an indication for a
port and the last component is taken apart.  Enclosing the address in brackets
doesn't work either because the host name resolution includes the brackets
around the IP address.


Upstream released version 2.3.5, which says "Fix IPv6 address as host".
I've put new packages on [1]. Could you check if they solve the issue?

[1] https://freeshell.de/~hille42/pssh/


2. A bracketed IPv6 works just fine.


Yes, this is expected.


3. A bracketed IPv6 plus `:PORT_NUMBER` raises `TypeError` in
psshlib/task.py:40 as it tries to join the host string to the integer port.

So I'd say that the original issue is fixed as per point 2, but using an
alternative port will fail as per point 3 (though that wasn't part of the
issue).


I tag that bug as pending, but I won't push the new version to bookworm.
Sorry!

Hilmar

Bug#1035008: [Pkg-javascript-devel] Bug#1035008: node-jest-worker: missing Breaks+Replaces for jest when upgrading from bullseye

[Helmut Grohne]

On Thu, Apr 27, 2023 at 10:03:00PM +0400, Yadd wrote:
> node-jest-worker has already
> 
>   Breaks: jest (<< 29.1.2~ds1+~cs70.47.21-1~)
> 
> how it is possible to have this issue ?

Breaks prevents both packages from being configured concurrently, so
installing node-jest-worker will cause jest to be deconfigured (and
later removed). However the packages can still be unpacked concurrently.
To avoid concurrent unpacks, one can use Conflicts instead of Breaks,
but this makes upgrades more difficult for apt. Instead, you should add
Replaces: jest (<< ...) to tell apt that during such a concurrent
unpack, node-jest-worker is allowed to "steal" files from jest. This is
detailed in policy section 7.6. Hope it helps.

Helmut

Bug#1034634: unblock: freetype/2.12.1+dfsg-5

[Cyril Brulebois]

Paul Gevers  (2023-04-27):
> This is currently udeb blocked, so I now realize I should have pinged
> you.

No worries, the udeb block is here so that we don't have to worry. :)

> I approved this from our side, can you confirm that after RC2 it's OK
> for d-i too?

It looks fine to me, it can get into testing once the udeb block is
lifted.


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


signature.asc
Description: PGP signature

Bug#1035008: [Pkg-javascript-devel] Bug#1035008: node-jest-worker: missing Breaks+Replaces for jest when upgrading from bullseye

[Yadd]

On 4/27/23 16:59, Helmut Grohne wrote:

Package: node-jest-worker
Version: 29.3.1~ds1+~cs70.48.25-1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack node-jest-worker/29.3.1~ds1+~cs70.48.25-1 from Debian 
bookworm
on a minimal Debian bullseye with jest/26.6.3+repack+~cs64.44.39-3
installed, causes an unpack error from dpkg due to
/usr/share/nodejs/@jest/types/build/Circus.d.ts being contained in both 
packages.

| dpkg: considering deconfiguration of jest, which would be broken by 
installation of node-jest-worker ...
| dpkg: yes, will deconfigure jest (broken by node-jest-worker)
| (Reading database ... 21294 files and directories currently installed.)
| Preparing to unpack .../node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb ...
| De-configuring jest (26.6.3+repack+~cs64.44.39-3) ...
| Unpacking node-jest-worker (29.3.1~ds1+~cs70.48.25-1) over 
(26.6.3+repack+~cs64.44.39-3) ...
| dpkg: error processing archive 
./node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb (--unpack):
|  trying to overwrite '/usr/share/nodejs/@jest/types/build/Circus.d.ts', which 
is also in package jest 26.6.3+repack+~cs64.44.39-3
| Errors were encountered while processing:
|  ./node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb


Please ensure that node-jest-worker has sufficient Breaks and Replaces 
declarations.

Helmut


Hi,

node-jest-worker has already

  Breaks: jest (<< 29.1.2~ds1+~cs70.47.21-1~)

how it is possible to have this issue ?

Bug#1034634: unblock: freetype/2.12.1+dfsg-5

[Paul Gevers]

Control: tags -1 d-i

Hi kibi,

On 20-04-2023 13:47, Hugh McMaster wrote:

[ Reason ]
An integer overflow vulnerability was discovered in FreeType (specifically, the
tt_hvadvance_adjust() function). This is CVE-2023-2004.

[ Impact ]
FreeType 2 can crash when getting TrueType font metrics due to the overflow.

[ Tests ]
Chromium's OSS-Fuzz project regularly fuzzes the FreeType source. After the
upstream fix was applied, the vulnerability was fixed.

[ Risks ]
The patch is non-invasive and very small.



unblock freetype/2.12.1+dfsg-5


This is currently udeb blocked, so I now realize I should have pinged 
you. I approved this from our side, can you confirm that after RC2 it's 
OK for d-i too?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#741537: pssh: IPv6 host address processing broken

[Ivan Vilata i Balaguer]

Preuße, Hilmar (2023-03-23 23:01:22 +0100) wrote:

> On 13.03.2014 16:37, Ivan Vilata i Balaguer wrote:
> 
> > The handling of IPv6 addresses is broken since the ``parse_host_entry()``
> > function in ``psshutil.py`` thinks the colons in it are an indication for a
> > port and the last component is taken apart.  Enclosing the address in 
> > brackets
> > doesn't work either because the host name resolution includes the brackets
> > around the IP address.
> > 
> Upstream released version 2.3.5, which says "Fix IPv6 address as host".
> I've put new packages on [1]. Could you check if they solve the issue?
> 
> [1] https://freeshell.de/~hille42/pssh/

Thanks Hilmar, I tested the packages and:

1. A raw IPv6 address raises `ValueError` as it tries to parse the part after
   the 1st colon as a port.

2. A bracketed IPv6 works just fine.

3. A bracketed IPv6 plus `:PORT_NUMBER` raises `TypeError` in
   psshlib/task.py:40 as it tries to join the host string to the integer port.

So I'd say that the original issue is fixed as per point 2, but using an
alternative port will fail as per point 3 (though that wasn't part of the
issue).

Thanks you very much!

-- 
Ivan Vilata i Balaguer -- https://elvil.net/

Bug#1035022: unpaper: undefined symbol: vaSyncBuffer

[Jean-Marc Spaggiari]

Package: unpaper
Version: 7.0.0-0.1
Severity: important

Dear Maintainer,

   * What led up to the situation?

Launching the application from command line gives an error. Unable to start
it.

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

Simply entered "unpaper" in the command line.

   * What was the outcome of this action?

The following error message:
unpaper: symbol lookup error: /lib/x86_64-linux-gnu/libavcodec.so.59:
undefined symbol: vaSyncBuffer

   * What outcome did you expect instead?

Anything but what I got. As an example, the version being printed in the
output.


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (100,
'bookworm-fasttrack'), (100, 'bookworm-backports-staging')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages unpaper depends on:
ii  libavcodec59   10:5.1.3-dmo3
ii  libavformat59  10:5.1.3-dmo3
ii  libavutil5710:5.1.3-dmo3
ii  libc6  2.36-9

unpaper recommends no packages.

unpaper suggests no packages.

-- no debconf information

Bug#1034785: unblock: gummi/0.8.3-1

[Martin Dosch]

Control: tags - moreinfo

Hi Paul,

On 27.04.2023 10:58, Paul Gevers wrote:

Your debdiff was so big that the mail didn't even reach the list.

60 files changed, 7341 insertions(+), 6240 deletions(-)


As you can see in a diff from 0.8.1 to 0.8.3 [1] also generated UI files 
and translations changed which makes the debdiff between both packages 
huge. I created a diff for the upstream changes in the src folder 
between 0.8.1 and 0.8.3 which should be less bloated and attach it to 
this email.


Best regards,
Martin

[1] 
https://github.com/alexandervdm/gummi/compare/0.8.1...0.8.3#files_bucket
diff --git a/Makefile b/Makefile
index 8e8911b..930b1ed 100644
--- a/Makefile
+++ b/Makefile
@@ -7,7 +7,7 @@ TARGET=gummi
 OBJS = main.o gui/gui-main.o gui/gui-prefs.o gui/gui-menu.o gui/gui-search.o 
gui/gui-import.o gui/gui-preview.o gui/gui-tabmanager.o gui/gui-project.o 
gui/gui-snippets.o gui/gui-infoscreen.o compile/texlive.o compile/rubber.o 
compile/latexmk.o motion.o external.o latex.o editor.o utils.o configfile.o 
iofunctions.o environment.o project.o importer.o tabmanager.o template.o 
biblio.o snippets.o signals.o
 
 
-CFLAGS=-g -Wall  -DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED 
-DGSEAL_ENABLE -export-dynamic -I. `pkg-config --cflags --libs gtk+-3.0 
gthread-2.0 gtksourceview-3.0 cairo poppler-glib gtkspell3-3.0 synctex zlib` 
-lm -DUSE_SYNCTEX1 -DGUMMI_LOCALES="\"/usr/share/locale\"" 
-DGUMMI_DATA="\"$$PWD/../data\"" -DGUMMI_LIBS="\"$$PWD/../lib\""
+CFLAGS=-g -Wall -Wno-deprecated-declarations -DGDK_DISABLE_DEPRECATED 
-DGTK_DISABLE_DEPRECATED -DGSEAL_ENABLE -export-dynamic -I. `pkg-config 
--cflags --libs gtk+-3.0 gthread-2.0 gtksourceview-3.0 cairo poppler-glib 
gtkspell3-3.0 synctex zlib` -lm -DUSE_SYNCTEX2 
-DGUMMI_LOCALES="\"/usr/share/locale\"" -DGUMMI_DATA="\"$$PWD/../data\"" 
-DGUMMI_LIBS="\"$$PWD/../lib\""
 
 gummi: $(OBJS)
$(CC) -o $(TARGET) $(OBJS) $(CFLAGS)
diff --git a/configfile.c b/configfile.c
index fefda66..a6a338f 100644
--- a/configfile.c
+++ b/configfile.c
@@ -49,9 +49,11 @@ const gchar default_config[] =
 "mainwindow_max = false\n"
 "toolbar = true\n"
 "statusbar = true\n"
+"rightpane = true\n"
 "snippets = true\n"
 "[Editor]\n"
-"font = Monospace 14\n"
+"font_str = Monospace 14\n"
+"font_css = * { font-family: Monospace; font-size: 14px; }\n"
 "line_numbers = true\n"
 "highlighting = true\n"
 "textwrapping = true\n"
diff --git a/constants.h b/constants.h
index 030..439c0fa 100644
--- a/constants.h
+++ b/constants.h
@@ -35,7 +35,7 @@
 // Gummi defs:
 #define C_PACKAGE "gummi"
 #define C_PACKAGE_NAME "Gummi"
-#define C_PACKAGE_VERSION "0.8.1"
+#define C_PACKAGE_VERSION "0.8.3"
 #define C_PACKAGE_COMMENTS "Simple LaTeX Editor for GTK+"
 #define C_PACKAGE_COPYRIGHT "Copyright \xc2\xa9 2009\n\n"\
 "Alexander van der Meij\n"\
@@ -94,7 +94,7 @@
 "Arabic: Hamad Mohammad\n" \
 "Brazilian-Portugese: Fernando Cruz, Alexandre Guimarães\n" \
 "Catalan: Marc Vinyals\n" \
-"Chinese (Simplified): Mathlab pass\n" \
+"Chinese (Simplified): Mathlab pass, yjwork-cn\n" \
 "Chinese (Traditional): Wei-Ning Huang\n" \
 "Czech: Přemysl Janouch\n" \
 "Danish: Jack Olsen\n" \
@@ -103,6 +103,7 @@
 "German: Thomas Niederprüm\n" \
 "Greek: Dimitris Leventeas\n" \
 "Hungarian: Balázs Meskó\n" \
+"Interlingue: OIS\n" \
 "Italian: Salvatore Vassallo\n" \
 "Polish: Hubert Kowalski\n" \
 "Portugese: Alexandre Guimarães\n" \
diff --git a/editor.c b/editor.c
index 5c91857..b97292b 100644
--- a/editor.c
+++ b/editor.c
@@ -190,7 +190,7 @@ void editor_fileinfo_update (GuEditor* ec, const gchar* 
filename) {
 
 // directory should exist, but if not create ~/.cache/gummi:
 if (!g_file_test (C_TMPDIR, G_FILE_TEST_IS_DIR)) {
-slog (L_WARNING, ".cache directory does not exist, creating..\n");
+slog (L_WARNING, "gummi cache directory does not exist, 
creating..\n");
 g_mkdir_with_parents (C_TMPDIR, DIR_PERMS);
 }
 
@@ -313,7 +313,7 @@ void editor_sourceview_config (GuEditor* ec) {
 const gchar* style_scheme = config_get_string ("Editor", "style_scheme");
 editor_set_style_scheme_by_id (ec, style_scheme);
 
-editor_set_font (ec, config_get_string ("Editor", "font"));
+editor_set_font (ec, config_get_string ("Editor", "font_css"));
 
 gtk_source_view_set_show_line_numbers (
 GTK_SOURCE_VIEW (ec->view),
@@ -724,15 +724,8 @@ void editor_redo_change (GuEditor* ec) {
 }
 }
 
-void editor_set_font (GuEditor* ec, const gchar* font) {
-// surely there has to be a better solution to transform
-// a string like 'Monospace 12' into css syntax right..?
-gchar** font_elems = g_strsplit (font, " ", BUFSIZ);
-gchar* style = g_strdup_printf ("* { font: %spx '%s'; }",
-font_elems[1], font_elems[0]);
-
-gtk_css_provider_load_from_data (ec->css, style, -1, NULL);
-g_free (style);
+void editor_set_font (GuEditor* ec, const gchar* font_css) {
+ 

Bug#1012838: Bug closed?

[Markus Steinko]

Dear maintainer,

I guess this bug is fixed with the latest upgrade?!

Best regards,

Bug#1034302: fixed in passwordsafe 1.16.0+dfsg-3

[Bill Blough]

It looks like there might have been another issue with the package (test
issues on i386).

I'm uploading another version today to fix that, so it will reset the 20
day timer, but it should migrate without issue after that unless there's
another problem.

Bug#1033900: pre-approval: dkms/3.0.10-10

[Andreas Beckmann]

Control: reopen -1
Control: retitle -1 pre-approval: dkms/3.0.11-2

On 20/04/2023 22.07, Paul Gevers wrote:

On 03-04-2023 19:19, Andreas Beckmann wrote:

I'd like to ask for pre-approval for adding a new binary package to
bookworm: dkms-test-dkms.


At this stage of the freeze I don't think what's currently in 
experimental on its own is worth having in bookworm. So unless something 
else appears that warrants an unblock, let's not do this. If something 
else appears soon worth an unblock, you can include this in your request.


I've just uploaded a new upstream release 3.0.11-1 with some additional
bugfixes to experimental. Most patches are now applied upstream.

The attached diff is between the versions in testing and experimental,
both trees with patches applied (and the patches itself excluded).
(as a normal debdiff with removal of the patches that are now included
in the upstream release would result in a large unhelpful noisy diff)

Most of the remaining changes are in the test infrastructure (these
I had previously excluded while cherry-picking bugfixes).

 .github/workflows/tests.yml   |   40
 Makefile  |4
 README.md |   21
 debian/changelog  |   23
 debian/control|   11
 debian/dkms-test-dkms.dkms|1
 debian/dkms-test-dkms.install |1
 debian/patches/series |   13
 debian/rules  |3
 debian/tests/control  |   50
 dkms.8.in |  138 +-
 dkms.in   |  240 ++--
 dkms_autoinstaller|2
 dkms_find-provides|2
 dkms_framework.conf   |2
 lsb_release   |6
 run_test.sh   |  801 +++---
 test/dkms_build_exclusive_dependencies_test-1.0/Makefile  |3
 test/dkms_build_exclusive_dependencies_test-1.0/dkms.conf |6
 test/dkms_build_exclusive_test-1.0/Makefile   |3
 test/dkms_build_exclusive_test-1.0/dkms.conf  |5
 test/dkms_conf_test_defaulted_BUILT_MODULE_NAME/dkms.conf |3
 test/dkms_conf_test_invalid/dkms.conf |6
 test/dkms_conf_test_zero_modules/dkms.conf|3
 test/dkms_dependencies_test-1.0/Makefile  |4
 test/dkms_dependencies_test-1.0/dkms.conf |1
 test/dkms_emptyver_test/dkms.conf |5
 test/dkms_failing_test-1.0/Makefile   |4
 test/dkms_failing_test-1.0/dkms.conf  |1
 test/dkms_nover_test/dkms.conf|5
 test/dkms_nover_update_test/1.0/Makefile  |7
 test/dkms_nover_update_test/1.0/dkms.conf |   12
 test/dkms_nover_update_test/1.0/dkms_nover_update_test.c  |   20
 test/dkms_nover_update_test/2.0/Makefile  |7
 test/dkms_nover_update_test/2.0/dkms.conf |   12
 test/dkms_nover_update_test/2.0/dkms_nover_update_test.c  |   20
 test/dkms_nover_update_test/3.0/Makefile  |7
 test/dkms_nover_update_test/3.0/dkms.conf |   12
 test/dkms_nover_update_test/3.0/dkms_nover_update_test.c  |   20
 test/dkms_test-1.0/dkms.conf  |5
 40 files changed, 1160 insertions(+), 369 deletions(-)


Andreas

dkms-3.0.11.diff.xz
Description: application/xz

Bug#1034908: Update libabsl-dev to new upstream version/snapshot for protobuf

[Pirate Praveen]

Control: tags -1 patch

On Thu, 27 Apr 2023 21:41:43 +0530 Pirate Praveen 
 wrote:

> After adding and adapting the patch from upstream,

attaching the patch if anyone wants to try

From 807763a7f57dcf0ba4af7c3b218013e8f525e811 Mon Sep 17 00:00:00 2001
From: Derek Mauro 
Date: Thu, 2 Mar 2023 17:32:02 -0800
Subject: [PATCH] CMake: Install TESTONLY libraries and their dependencies when
 they are built

https://github.com/abseil/abseil-cpp/issues/1407

PiperOrigin-RevId: 513684529
Change-Id: Ie0a164eea32becfef8f8e4a112aee158fd93dd7e
---
 CMake/AbseilHelpers.cmake | 92 +++
 1 file changed, 44 insertions(+), 48 deletions(-)

--- a/CMake/AbseilHelpers.cmake
+++ b/CMake/AbseilHelpers.cmake
@@ -153,52 +153,55 @@
 
   # Generate a pkg-config file for every library:
   if(ABSL_ENABLE_INSTALL)
-if(NOT ABSL_CC_LIB_TESTONLY)
-  if(absl_VERSION)
-set(PC_VERSION "${absl_VERSION}")
-  else()
-set(PC_VERSION "head")
-  endif()
-  if(NOT _build_type STREQUAL "dll")
-set(LNK_LIB "${LNK_LIB} -labsl_${_NAME}")
-  endif()
-  foreach(dep ${ABSL_CC_LIB_DEPS})
-if(${dep} MATCHES "^absl::(.*)")
-  # for DLL builds many libs are not created, but add
-  # the pkgconfigs nevertheless, pointing to the dll.
-  if(_build_type STREQUAL "dll")
-# hide this MATCHES in an if-clause so it doesn't overwrite
-# the CMAKE_MATCH_1 from (${dep} MATCHES "^absl::(.*)")
-if(NOT PC_DEPS MATCHES "abseil_dll")
-  # Join deps with commas.
-  if(PC_DEPS)
-set(PC_DEPS "${PC_DEPS},")
-  endif()
-  # don't duplicate dll-dep if it exists already
-  set(PC_DEPS "${PC_DEPS} abseil_dll = ${PC_VERSION}")
-  set(LNK_LIB "${LNK_LIB} -labseil_dll")
-endif()
-  else()
+if(absl_VERSION)
+  set(PC_VERSION "${absl_VERSION}")
+else()
+  set(PC_VERSION "head")
+endif()
+if(NOT _build_type STREQUAL "dll")
+  set(LNK_LIB "${LNK_LIB} -labsl_${_NAME}")
+endif()
+foreach(dep ${ABSL_CC_LIB_DEPS})
+  if(${dep} MATCHES "^absl::(.*)")
+# for DLL builds many libs are not created, but add
+# the pkgconfigs nevertheless, pointing to the dll.
+if(_build_type STREQUAL "dll")
+  # hide this MATCHES in an if-clause so it doesn't overwrite
+  # the CMAKE_MATCH_1 from (${dep} MATCHES "^absl::(.*)")
+  if(NOT PC_DEPS MATCHES "abseil_dll")
 # Join deps with commas.
 if(PC_DEPS)
   set(PC_DEPS "${PC_DEPS},")
 endif()
-set(PC_DEPS "${PC_DEPS} absl_${CMAKE_MATCH_1} = ${PC_VERSION}")
+# don't duplicate dll-dep if it exists already
+set(PC_DEPS "${PC_DEPS} abseil_dll = ${PC_VERSION}")
+set(LNK_LIB "${LNK_LIB} -labseil_dll")
   endif()
-endif()
-  endforeach()
-  foreach(cflag ${ABSL_CC_LIB_COPTS})
-if(${cflag} MATCHES "^(-Wno|/wd)")
-  # These flags are needed to suppress warnings that might fire in our headers.
-  set(PC_CFLAGS "${PC_CFLAGS} ${cflag}")
-elseif(${cflag} MATCHES "^(-W|/w[1234eo])")
-  # Don't impose our warnings on others.
 else()
   set(PC_CFLAGS "${PC_CFLAGS} ${cflag}")
+  # Join deps with commas.
+  if(PC_DEPS)
+set(PC_DEPS "${PC_DEPS},")
+  endif()
+  set(PC_DEPS "${PC_DEPS} absl_${CMAKE_MATCH_1} = ${PC_VERSION}")
 endif()
-  endforeach()
-  string(REPLACE ";" " " PC_LINKOPTS "${ABSL_CC_LIB_LINKOPTS}")
-  FILE(GENERATE OUTPUT "${CMAKE_BINARY_DIR}/lib/pkgconfig/absl_${_NAME}.pc" CONTENT "\
+  endif()
+endforeach()
+foreach(cflag ${ABSL_CC_LIB_COPTS})
+  if(${cflag} MATCHES "^(-Wno|/wd)")
+# These flags are needed to suppress warnings that might fire in our headers.
+set(PC_CFLAGS "${PC_CFLAGS} ${cflag}")
+  elseif(${cflag} MATCHES "^(-W|/w[1234eo])")
+# Don't impose our warnings on others.
+  elseif(${cflag} MATCHES "^-m")
+# Don't impose CPU instruction requirements on others, as
+# the code performs feature detection on runtime.
+  else()
+set(PC_CFLAGS "${PC_CFLAGS} ${cflag}")
+  endif()
+endforeach()
+string(REPLACE ";" " " PC_LINKOPTS "${ABSL_CC_LIB_LINKOPTS}")
+FILE(GENERATE OUTPUT "${CMAKE_BINARY_DIR}/lib/pkgconfig/absl_${_NAME}.pc" CONTENT "\
 prefix=${CMAKE_INSTALL_PREFIX}\n\
 exec_prefix=\${prefix}\n\
 libdir=${CMAKE_INSTALL_FULL_LIBDIR}\n\
@@ -211,9 +214,8 @@
 Requires:${PC_DEPS}\n\
 Libs: -L\${libdir} ${PC_LINKOPTS} $<$>:${LNK_LIB}>\n\
 Cflags: -I\${includedir}${PC_CFLAGS}\n")
-  INSTALL(FILES "${CMAKE_BINARY_DIR}/lib/pkgconfig/absl_${_NAME}.pc"
-  DESTINATION "${CMAKE_INSTALL_LIBDIR}/pkgconfig")
-endif()
+INSTALL(FILES 

Bug#1034138: Backport message retraction support from upstream master

[Pirate Praveen]

Control: retitle -1 Update ejabberd to 23.04

On Mon, 10 Apr 2023 17:08:15 +0530 Pirate Praveen 
 wrote:

>
>
> On Mon, Apr 10 2023 at 04:50:05 PM +05:30:00 +05:30:00, Pirate 
Praveen

>  wrote:
> > I guess
> > 
https://salsa.debian.org/praveen/ejabberd/-/blob/master/debian/patches/src.includes.patch

> > will need to be updated, but I'm not familiar with erlang to figure
> > this out myself. Any help is welcome.
>
> Figured out this, I need to update erlang-p1-xmpp as well. After
> updating erlang-p1-xmpp, I could build ejabberd as well.

Support for message retractions is part of 23.04 release, so uploading 
a new version to experimental would be nice. Until freeze is lifted, 
this could be shipped via fasttrack.debian.net as well[1].


[1] https://salsa.debian.org/fasttrack-team/support/-/issues/49

Bug#1035020: Info received (Bug#1035020: Acknowledgement (okular scans my homefolder without any need))

[Georg Gast]

Found out that these file paths are stored in
~/.config/okularrc

Bug#1034908: Update libabsl-dev to new upstream version/snapshot for protobuf

[Pirate Praveen]

On Thu, 27 Apr 2023 20:14:46 +0530 Pirate Praveen 
 wrote:

> Looks like this is a bug in abseil itself
> https://github.com/abseil/abseil-cpp/issues/1407

After adding and adapting the patch from upstream, the build fails with 
below error. I can't find libgtest.so in any package.


apt-file list libgtest-dev gives
libgtest-dev: /usr/lib/x86_64-linux-gnu/libgtest.a

so we should either ship .so in libgtest-dev or adapt abseil to link 
against libgtest.a


dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_per_thread_sem_test_common.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_spinlock_test_common.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgmock.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_scoped_mock_log.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_scoped_mock_log.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_exception_safety_testing.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_log_internal_test_matchers.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_log_internal_test_helpers.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')

dpkg-shlibdeps: error: cannot continue due to the errors listed above
Note: libraries are not searched in other binary packages that do not 
have any shlibs or symbols file.

Bug#1035020: Acknowledgement (okular scans my homefolder without any need)

[Georg Gast]

I found out that these documents are stored in recentdocuments:/ url
in dolphin. I disabled the "Zuletzt geöffnete Dokumente" (last opened
files) in the settings but it still tries to open these files. I also
disabled in the plasma search category "Zuletzt geöffnete Dokumente"
but no change.

Bug#1019364: gnome-software: Unable to install XXX as not supported

[asciiwolf]

I am experiencing this issue on latest Debian testing using gnome-software 
43.4-1. However, in my case the packages actually seem to get installed despite 
this message. Also, it does not seem to happen every time, I am not sure, but 
it looks like it happens only when there are additional dependencies installed, 
not just one (main) package.

Sadly, there does not seem to be anything useful/related in the system journal 
or other logs, however this bug is easy to reproduce when installing using the 
latest Debian testing amd64 iso (from 2023-04-24 07:10), updating the system 
after the installation, running Software and installing "VLC" for the first 
time.

Daniel

Bug#1035021: keepass2: Keepass2 window elements is out of screen

[Serge]

Package: keepass2
Version: 2.47+dfsg-2
Severity: important

Dear Maintainer,



   just install, start and trying to add database.
Window about master password is big and bottom of window with buttons is out of 
screen.
Compaq CQ57, screen resolution is 1366x768.


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

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

Versions of packages keepass2 depends on:
ii  libgcrypt20  1.10.1-3
ii  libmono-corlib4.5-cil6.8.0.105+dfsg-3.3
ii  libmono-system-drawing4.0-cil6.8.0.105+dfsg-3.3
ii  libmono-system-security4.0-cil   6.8.0.105+dfsg-3.3
ii  libmono-system-windows-forms4.0-cil  6.8.0.105+dfsg-3.3
ii  libmono-system-xml4.0-cil6.8.0.105+dfsg-3.3
ii  libmono-system4.0-cil6.8.0.105+dfsg-3.3
ii  libx11-6 2:1.8.4-2
ii  mono-runtime 6.8.0.105+dfsg-3.3

Versions of packages keepass2 recommends:
ii  xsel  1.2.0+git9bfc13d.20180109-3

Versions of packages keepass2 suggests:
pn  keepass2-doc  
pn  mono-dmcs 
pn  xdotool   

-- no debconf information

Bug#1035018: btrfs-progs: /sbin/fsck.btrfs missing from udeb

[Adam Borowski]

On Thu, Apr 27, 2023 at 04:58:46PM +0200, Emanuele Rocca wrote:
> 
> the btrfs-progs udeb currently includes only /bin/btrfs and /bin/mkfs.btrfs.
> 
> Please add /sbin/fsck.btrfs as well so that it can be included in the 
> initramfs
> generated by the debian installer. Patch attached.

That file is a no-op script that's there just to placate mount mechanisms
which blindly run fsck on startup.  Unlike ext4 which still supports
ext2 filesystems that risk damage, possibly widespread and/or hidden,
in the case of an unsafe shutdown, modern filesystems (btrfs, xfs, jfs, …)
no longer require that.

If the kernel is unable to recover on its own, the cause must have been a
hardware or software problem which can't happen during normal operation,
and data loss of some kind is likely -- thus there's nothing that's prudent
to try to fix _automatically_.

Ie, /sbin/fsck.btrfs serves no purpose that'd be useful in an udeb.

Before I close this report, may I ask if you have a purpose for this
stub?  You probably wanted a full-blown recovery tool, but I may be
getting you wrong.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ ʀᴜꜱꜱɪᴀɴᴇꜱ ᴇᴜɴᴛ ᴅᴏᴍᴜꜱ
⢿⡄⠘⠷⠚⠋⠀
⠈⠳⣄

Bug#830857: [Pkg-libvirt-maintainers] Bug#830857: libvirt-daemon: CPU feature cmt not found

[Emanuele Rocca]

Hi,

On Tue, Jul 12, 2016 at 08:22:31PM +0200, Ansgar Hegerfeld wrote:
> Okay, thanks. I opened a bugreport upstream:
> https://bugzilla.redhat.com/show_bug.cgi?id=1355857

The upstream bug was fixed a long time ago. Is the issue still reproducible in
Debian, or can this bug be closed?

Thanks,
  ema

Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

[kt programs]

On Thu Apr 27, 2023 at 10:39 PM +08, Cyril Brulebois wrote:
> Control: tag -1 patch
>
> Hi Keith and X team,
>
> and thanks for your report.
>
> Keith Toh  (2023-04-27):
> > Image version: 
> > http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
> >  (2023-04-24 23:09)
>
> For the avoidance of doubt: same story with amd64.
>
> > Machine: UTM QEMU VM
> > 
> > When booting the installer in Graphical install mode, Xorg repeatedly
> > errors saying "no screens found". Based on the Xorg log, it is failing
> > to load the modesetting driver, as the file
> > /usr/lib/xorg/modules/drivers/modesetting_drv.so appears to have been
> > dropped from xerver-xorg-core-udeb between bullseye and bookworm.
> > 
> > >From kibi on #debian-boot (https://paste.debian.net/1278647/):
> > xserver-xorg-core-udeb_1.20.11-1+deb11u3_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.11-1+deb11u4_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.11-1+deb11u5_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.11-1+deb11u6_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.13-1_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.13-2_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.13-3_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.14-1_amd64.udeb YES
> > xserver-xorg-core-udeb_21.1.1-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.1-2_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.3-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.3-2+b1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.3-2_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.4-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.4-2_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.4-3_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.5-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.6-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.7-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.7-2_amd64.udeb NO
>
> Tracked down to 9c81b8f5b5 upstream:
>   https://cgit.freedesktop.org/xorg/xserver/commit/?id=9c81b8f5b5
>
> Flipping the switch and wrapping it up in a netboot mini.iso
> debian-installer build led to a successful test (with amd64) by Keith.
> We'll try and confirm the same happens with arm64.

Can confirm that an arm64 mini.iso with the same fixes works.

> If you're happy with that approach, feel free to reassign to the udeb,
> and check the udeb-modesetting branch in xorg-server:
>   
> https://salsa.debian.org/xorg-team/xserver/xorg-server/-/commits/udeb-modesetting
>
> I don't have access to VirtualBox right now, but we've had reports of
> failures there as well, maybe that's the same kind of things.
>
>
> Cheers,
> -- 
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant

Bug#1035019: Sync translations from Ubuntu

[asciiwolf]

Package: software-properties-gtk
Version: 0.99.30-4

The "Software & Updates" GTK application has most of its strings untranslated 
in Debian in our (Czech) language although it is fully translated in Ubuntu.[1] 
When looking at the bug tracker, it looks like that many other language 
translations have the same problem.

When looking at the software-properties po files[2] at Debian Salsa GitLab, it 
looks like that they were never updated, only the pot template was.

I am not sure how translations of this component are handled in Debian, but 
please consider syncing them from Ubuntu.

Thanks!

[1] 
https://translations.launchpad.net/ubuntu/lunar/+source/software-properties/+pots/software-properties
[2] 
https://salsa.debian.org/pkgutopia-team/software-properties/-/tree/debian/master/po

Bug#1035018: btrfs-progs: /sbin/fsck.btrfs missing from udeb

[Emanuele Rocca]

Package: btrfs-progs
Version: 6.2-1
X-Debbugs-CC: debian-b...@lists.debian.org
Tags: patch

Hi,

the btrfs-progs udeb currently includes only /bin/btrfs and /bin/mkfs.btrfs.

Please add /sbin/fsck.btrfs as well so that it can be included in the initramfs
generated by the debian installer. Patch attached.

Thanks!
  ema
diff -Nru btrfs-progs-6.2/debian/btrfs-progs-udeb.install btrfs-progs-6.2/debian/btrfs-progs-udeb.install
--- btrfs-progs-6.2/debian/btrfs-progs-udeb.install	2023-03-01 00:16:51.0 +0100
+++ btrfs-progs-6.2/debian/btrfs-progs-udeb.install	2023-04-27 16:43:48.0 +0200
@@ -1,2 +1,3 @@
 btrfs		/bin
 mkfs.btrfs	/bin
+fsck.btrfs /sbin

Bug#1035017: unblock: pdl/1:2.081-2

[Bas Couwenberg]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: p...@packages.debian.org
Control: affects -1 + src:pdl

Please unblock package pdl

[ Reason ]
It fixed the upgrade failure from bullseye reported in #1034942.

[ Impact ]
Upgrade from bullseye to bookworm fails.

[ Tests ]
autopkgtest, Salsa CI, and upstream test suite.

I've manually verified the fix for #1034942 by upgrading a bullseye chroot to 
bookworm using the fixed pdl from my local repo.

[ Risks ]
Low, the other changes that were pending in git since 1:2.081-1 don't risk 
breakage.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
The package has been uploaded to unstable.

unblock pdl/1:2.081-2
diff -Nru pdl-2.081/debian/changelog pdl-2.081/debian/changelog
--- pdl-2.081/debian/changelog  2022-10-27 18:57:46.0 +0200
+++ pdl-2.081/debian/changelog  2023-04-27 15:54:44.0 +0200
@@ -1,3 +1,22 @@
+pdl (1:2.081-2) unstable; urgency=medium
+
+  * Team upload.
+
+  [ Bas Couwenberg ]
+  * Add Rules-Requires-Root to control file.
+  * Add a debhelper sequence to run dh_pdl.
+  * Bump Standards-Version to 4.6.2, no changes.
+  * Add Breaks/Replaces on libpdl-stats-perl to fix upgrade.
+(closes: #1034942)
+
+  [ Debian Janitor ]
+  * Update lintian override info to new format:
++ debian/source/lintian-overrides: line 2
++ debian/pdl.lintian-overrides: line 6, 10, 22, 28
+  * Use secure URI in Homepage field.
+
+ -- Bas Couwenberg   Thu, 27 Apr 2023 15:54:44 +0200
+
 pdl (1:2.081-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru pdl-2.081/debian/control pdl-2.081/debian/control
--- pdl-2.081/debian/control2022-07-04 19:03:29.0 +0200
+++ pdl-2.081/debian/control2023-04-27 15:53:33.0 +0200
@@ -37,10 +37,11 @@
proj-bin,
sharutils,
x11proto-core-dev
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/pdl
 Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/pdl.git
-Homepage: http://pdl.perl.org/
+Homepage: https://pdl.perl.org/
+Rules-Requires-Root: binary-targets
 
 Package: pdl
 Architecture: any
@@ -66,9 +67,12 @@
   libpgplot-perl,
   netpbm | imagemagick,
   proj-bin
+Breaks: libpdl-stats-perl (<< 0.77)
 Conflicts: r-pdl
-Provides: ${pdlapi:Provides}
-Replaces: r-pdl
+Provides: dh-sequence-pdl,
+  ${pdlapi:Provides}
+Replaces: libpdl-stats-perl (<< 0.77),
+  r-pdl
 Description: perl data language: Perl extensions for numerics
  PDL gives standard perl the ability to COMPACTLY
  store and SPEEDILY manipulate the large N-dimensional data arrays
diff -Nru pdl-2.081/debian/Debian/Debhelper/Sequence/pdl.pm 
pdl-2.081/debian/Debian/Debhelper/Sequence/pdl.pm
--- pdl-2.081/debian/Debian/Debhelper/Sequence/pdl.pm   1970-01-01 
01:00:00.0 +0100
+++ pdl-2.081/debian/Debian/Debhelper/Sequence/pdl.pm   2023-04-27 
15:41:56.0 +0200
@@ -0,0 +1,15 @@
+# pdl.pm - debhelper addon for running dh_pdl
+#
+# Copyright 2022, Bas Couwenberg 
+#
+# This program is free software, you can redistribute it and/or modify it
+# under the same terms as Perl itself.
+
+use strict;
+use warnings;
+
+use Debian::Debhelper::Dh_Lib;
+
+insert_after("dh_perl", "dh_pdl");
+
+1;
diff -Nru pdl-2.081/debian/pdl.install pdl-2.081/debian/pdl.install
--- pdl-2.081/debian/pdl.install2022-03-16 18:50:30.0 +0100
+++ pdl-2.081/debian/pdl.install2023-04-27 15:41:56.0 +0200
@@ -1,3 +1,4 @@
 Doc/scantree.pl  usr/lib/x86_64-linux-gnu/perl5/5.22/PDL/Doc/
 Doc/mkhtmldoc.pl usr/lib/x86_64-linux-gnu/perl5/5.22/PDL/Doc/
 debian/dh_pdlusr/bin
+debian/Debianusr/share/perl5
diff -Nru pdl-2.081/debian/pdl.install.in pdl-2.081/debian/pdl.install.in
--- pdl-2.081/debian/pdl.install.in 2022-03-16 18:50:30.0 +0100
+++ pdl-2.081/debian/pdl.install.in 2023-04-27 15:41:56.0 +0200
@@ -1,3 +1,4 @@
 Doc/scantree.pl  @vendorarch@/PDL/Doc/
 Doc/mkhtmldoc.pl @vendorarch@/PDL/Doc/
 debian/dh_pdlusr/bin
+debian/Debianusr/share/perl5
diff -Nru pdl-2.081/debian/pdl.lintian-overrides 
pdl-2.081/debian/pdl.lintian-overrides
--- pdl-2.081/debian/pdl.lintian-overrides  2022-10-26 18:32:22.0 
+0200
+++ pdl-2.081/debian/pdl.lintian-overrides  2023-04-27 15:41:56.0 
+0200
@@ -3,11 +3,11 @@
 doc-base-file-references-missing-file /var/lib/pdl/html/*.html *
 
 # these two images need to be in usr/lib
-image-file-in-usr-lib */PDL/Transform/Cartography/earth_*.jpg*
+image-file-in-usr-lib [*/PDL/Transform/Cartography/earth_*.jpg*]
 
 # Build uses -D_FORTIFY_SOURCE=2, but hardening-check reports:
 #  Fortify Source functions: no, only unprotected functions found!
-hardening-no-fortify-functions *

Bug#1033571: unblock: keyman/16.0.139-4

[Eberhard Beilharz]

-set -e
+# Don't call `set -e`. Even if some commands should fail, it's still
+# worth running the rest of the commands.

Can you elaborate?


After the installation of ibus-keyman the ibus daemon needs to be 
restarted which is what the `postinst` script tries to do. It restarts 
or stops ibus-daemon, then checks if ibus-daemon is running - if not it 
will start it. If any of these steps fail we still want to successfully 
finish the installation. Since then ibus is not running the user will 
not be able to see any installed Keyman keyboards and will have to 
logout or reboot which will start ibus.


If we return with a non-exit code from the postinst script instead the 
installation of ibus-keyman aborts. The user can then try to install 
again which might lead into the same error, leaving him with an 
uninstallable ibus-keyman where the only thing that failed was the 
failure to (re-)start ibus.


Since all of postinst deals with ibus-daemon which is not part of the 
ibus-keyman package it seems to me that ignoring failures would be 
acceptable. This means the admin (who in most cases will be an ordinary 
user) won't be aware of problems with the postinst script, but he might 
notice ibus-daemon not running. Ignoring these postinst errors makes it 
harder for the developer to notice and fix errors in the postinst 
script, but IMO gives a better experience for the ordinary user.



Did I miss something but is the *only* change upstream the addition echo?
That might well be the only change. New upstream versions get released 
simultaneously with the same version on all platforms, so it can happen 
that there is a new version without any changes on a platform. IMO this 
still has value since it simplifies dealing with help requests (the 
latest version of the binary is the latest version in the source code).


Doesn't feel very appropriate at this stage... 
That's your call. I still would like to see this version be available in 
Bookworm, but if you decide that's not an appropriate change I can live 
with that.


Thanks,
    Eberhard




OpenPGP_0xE9140597606020D3.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034908: Update libabsl-dev to new upstream version/snapshot for newer protobuf

[Pirate Praveen]

On Thu, 27 Apr 2023 19:16:36 +0530 Pirate Praveen 
 wrote:

> though now the error changed to,
> CMake Error at cmake/tests.cmake:97 (target_link_libraries):
>   Target "tests" links to:
>
> absl::scoped_mock_log
>
>   but the target was not found. Possible reasons include:
>
> * There is a typo in the target name.
> * A find_package call is missing for an IMPORTED target.
> * An ALIAS target is missing.
>
> Call Stack (most recent call first):
>   CMakeLists.txt:401 (include)

Looks like this is a bug in abseil itself
https://github.com/abseil/abseil-cpp/issues/1407

Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

[Cyril Brulebois]

Control: tag -1 patch

Hi Keith and X team,

and thanks for your report.

Keith Toh  (2023-04-27):
> Image version: 
> http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
>  (2023-04-24 23:09)

For the avoidance of doubt: same story with amd64.

> Machine: UTM QEMU VM
> 
> When booting the installer in Graphical install mode, Xorg repeatedly
> errors saying "no screens found". Based on the Xorg log, it is failing
> to load the modesetting driver, as the file
> /usr/lib/xorg/modules/drivers/modesetting_drv.so appears to have been
> dropped from xerver-xorg-core-udeb between bullseye and bookworm.
> 
> >From kibi on #debian-boot (https://paste.debian.net/1278647/):
> xserver-xorg-core-udeb_1.20.11-1+deb11u3_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.11-1+deb11u4_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.11-1+deb11u5_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.11-1+deb11u6_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.13-1_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.13-2_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.13-3_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.14-1_amd64.udeb YES
> xserver-xorg-core-udeb_21.1.1-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.1-2_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.3-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.3-2+b1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.3-2_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.4-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.4-2_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.4-3_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.5-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.6-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.7-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.7-2_amd64.udeb NO

Tracked down to 9c81b8f5b5 upstream:
  https://cgit.freedesktop.org/xorg/xserver/commit/?id=9c81b8f5b5

Flipping the switch and wrapping it up in a netboot mini.iso
debian-installer build led to a successful test (with amd64) by Keith.
We'll try and confirm the same happens with arm64.

If you're happy with that approach, feel free to reassign to the udeb,
and check the udeb-modesetting branch in xorg-server:
  
https://salsa.debian.org/xorg-team/xserver/xorg-server/-/commits/udeb-modesetting

I don't have access to VirtualBox right now, but we've had reports of
failures there as well, maybe that's the same kind of things.


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


signature.asc
Description: PGP signature

Bug#1035016: unblock: eztrace/2.0+repack-12

[Samuel Thibault]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: eztr...@packages.debian.org
Control: affects -1 + src:eztrace

Hello,

I have uploaded eztrace_2.0+repack-12 to unstable, for
inclusion in bookworm.

[ Reason ]
As detailed in Bug#1034956, there is a missing breaks+replace between
the libeztrace0 package and the libeztrace-dev package.
What happened is that usr/lib/*/libeztrace-*.so (plugins) were
moved from the latter to the former in version 2.0-1, but adding
breaks replaces was missed.

[ Impact ]
The impact happens if libeztrace0 gets upgraded before libeztrace-dev:

| (Reading database ... 5608 files and directories currently installed.)
| Preparing to unpack .../libeztrace0_2.0+repack-11_amd64.deb ...
| Unpacking libeztrace0:amd64 (2.0+repack-11) over (1.1-10-2) ...
| dpkg: error processing archive ./libeztrace0_2.0+repack-11_amd64.deb 
(--unpack):
|  trying to overwrite '/usr/lib/x86_64-linux-gnu/libeztrace-memory.so', which 
is also in package libeztrace-dev:amd64 1.1-10-2
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

It usually doesn't happen in practice because since libeztrace-dev
depends on the same version of libeztrace0, apt would upgrade the latter
before the former.

[ Tests ]
This was tested by hand by installing libeztrace0 on a bullseye system
with --auto-deconfigure and with libeztrace-dev installed.

[ Risks ]
The code is very trivial.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

Thanks!

unblock eztrace/2.0+repack-12
diff -Nru eztrace-2.0+repack/debian/changelog 
eztrace-2.0+repack/debian/changelog
--- eztrace-2.0+repack/debian/changelog 2022-12-20 16:17:31.0 +0100
+++ eztrace-2.0+repack/debian/changelog 2023-04-27 16:07:04.0 +0200
@@ -1,3 +1,11 @@
+eztrace (2.0+repack-12) unstable; urgency=medium
+
+  * control: Add missing breaks+replaces between libeztrace0 and
+libeztrace-dev, missed when moving /usr/lib/*/*.so from the latter to the
+former (Closes: Bug#1034956)
+
+ -- Samuel Thibault   Thu, 27 Apr 2023 16:07:04 +0200
+
 eztrace (2.0+repack-11) unstable; urgency=medium
 
   * control: Always depend on otf2, eztrace now always requires it actually.
diff -Nru eztrace-2.0+repack/debian/control eztrace-2.0+repack/debian/control
--- eztrace-2.0+repack/debian/control   2022-12-20 16:17:31.0 +0100
+++ eztrace-2.0+repack/debian/control   2023-04-27 16:06:20.0 +0200
@@ -53,6 +53,8 @@
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}
+Breaks: libeztrace-dev (<< 2.0-1)
+Replaces: libeztrace-dev (<< 2.0-1)
 Pre-Depends: ${misc:Pre-Depends}
 Description: Automatic execution trace generation for HPC - runtime libraries
  EZTrace is a tool that aims at generating automatically execution traces

Bug#1034668: Please update to new upstream release 3.22.3 in experimental

[Pirate Praveen]

With a newer libabsl-dev from 
https://people.debian.org/~praveen/new/pool/main/a/abseil/, the error 
changed to


CMake Error at cmake/tests.cmake:97 (target_link_libraries):
Target "tests" links to:

  absl::scoped_mock_log

but the target was not found. Possible reasons include:

  * There is a typo in the target name.
  * A find_package call is missing for an IMPORTED target.
  * An ALIAS target is missing.

Call Stack (most recent call first):
CMakeLists.txt:401 (include)

Bug#1035015: Mail list requests failing with Recipient address rejected

[Andre AE]

Package: lists.debian.org
Severity: normal

I tried to subscribe to user mail lists, and got:

--

Sorry, we were unable to deliver your message to the following address.

:

550: 5.1.1 : Recipient address 
rejected: User unknown in virtual alias table

--

Sorry, we were unable to deliver your message to the following address.

:

550: 5.1.1 : Recipient 
address rejected: User unknown in virtual alias table

Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

[Keith Toh]

Package: installation-reports
Severity: important

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
 (2023-04-24 23:09)

Machine: UTM QEMU VM


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[ ]
Configure network:  [ ]
Detect media:   [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

When booting the installer in Graphical install mode, Xorg repeatedly
errors saying "no screens found". Based on the Xorg log, it is failing
to load the modesetting driver, as the file
/usr/lib/xorg/modules/drivers/modesetting_drv.so appears to have been
dropped from xerver-xorg-core-udeb between bullseye and bookworm.

>From kibi on #debian-boot (https://paste.debian.net/1278647/):
xserver-xorg-core-udeb_1.20.11-1+deb11u3_amd64.udeb YES
xserver-xorg-core-udeb_1.20.11-1+deb11u4_amd64.udeb YES
xserver-xorg-core-udeb_1.20.11-1+deb11u5_amd64.udeb YES
xserver-xorg-core-udeb_1.20.11-1+deb11u6_amd64.udeb YES
xserver-xorg-core-udeb_1.20.13-1_amd64.udeb YES
xserver-xorg-core-udeb_1.20.13-2_amd64.udeb YES
xserver-xorg-core-udeb_1.20.13-3_amd64.udeb YES
xserver-xorg-core-udeb_1.20.14-1_amd64.udeb YES
xserver-xorg-core-udeb_21.1.1-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.1-2_amd64.udeb NO
xserver-xorg-core-udeb_21.1.3-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.3-2+b1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.3-2_amd64.udeb NO
xserver-xorg-core-udeb_21.1.4-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.4-2_amd64.udeb NO
xserver-xorg-core-udeb_21.1.4-3_amd64.udeb NO
xserver-xorg-core-udeb_21.1.5-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.6-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.7-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.7-2_amd64.udeb NO


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230423-02:07:34"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 6.1.0-7-arm64 #1 SMP Debian 6.1.20-2 (2023-04-08) 
aarch64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Red Hat, Inc. QEMU PCIe Host bridge 
[1b36:0008]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:1100]
lspci -knn: 00:01.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network 
device [1af4:1000]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0001]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:02.0 Display controller [0380]: Red Hat, Inc. Virtio GPU 
[1af4:1050] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:1100]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller 
[8086:2668] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: 00:04.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 
Host Controller [1033:0194] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:05.0 USB controller [0c03]: Red Hat, Inc. QEMU XHCI Host 
Controller [1b36:000d] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:1100]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:06.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio block 
device [1af4:1001]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0002]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:07.0 Communication controller [0780]: Red Hat, Inc. Virtio 
console [1af4:1003]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0003]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:08.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG 
[1af4:1005]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0004]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
usb-list: 
usb-list: Bus 01 Device 01: xHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 6.1.0-7-arm64 xhci-hcd
usb-list:Interface 00: Class 09(hub  ) 

Bug#1010478: Probably related to mutter 2570 suspend resume monitor readiness

[Ryan]

This is probably related to this issue / fix that has just been made 
against gnome 44:


https://gitlab.gnome.org/GNOME/mutter/-/issues/2570

https://gitlab.gnome.org/salmanmlk/mutter/-/commit/f39416f45e5f8c46755abb24684a1aeea1b708df

Since bookworm will release with gnome 43 and this is only fixed in 
gnome 44, perhaps there might be a backport patch of this important fix 
against 43?


At work this bug makes wayland unuseable if multiple times per day the 
segfault essentially logs me out with the loss of all work whenever it 
hits powersave mode.


Thank you for the hard maintenance work you do!

Bug#1034942: pdl: missing Breaks+Replaces for libpdl-stats-perl when upgrading from bullseye

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 4/27/23 14:58, Helmut Grohne wrote:

Attempting to unpack pdl/1:2.081-1+b1 from Debian bookworm
on a minimal Debian bullseye with libpdl-stats-perl/0.76-1
installed, causes an unpack error from dpkg due to
/usr/share/man/man3/PDL::GSL::CDF.3pm.gz being contained in both packages.


libpdl-stats-perl (0.82-3) in bookworm no longer includes the 
PDL::GSL::CDF files, but that can only be installed after the pdl 
(1:2.081-1).


The CDF files are no longer included since libpdl-stats-perl (0.77-1~exp1).

The issue is fixed in git and a new upload to unstable will follow shortly.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1034420: grub-efi-amd64: Package update fails with error: installation script subprocess returned error exit status 128

[Steve McIntyre]

On Sat, Apr 22, 2023 at 11:05:14AM +, Andrea Palazzi wrote:
>>>Errors were encountered while processing:
>>> grub-efi-amd64
>>> grub-efi
>>>E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>>There's not a lot to see here so far. What happens if you run:
>>
>> "sudo grub-install -v"
>>
>> by hand please?
>
>Hi,
>
>not sure if it's relevant or not, but I'm running on a ZFS boot and root
>filesystem.

Ok, thanks for the extra info.

>Regarding the grub-install command, you can find attached the full output of
>LC_ALL=C grub-install -v .

Thanks. That's not showing anything unexpected, which surprises me.

Could you please edit /var/lib/dpkg/info/grub-efi-amd64.postinst and
add a line near the top saying

set -x

and then run

# script -c "dpkg --configure --pending" dpkg.log

please? That should capture whatever is failing in dpkg.log, I hope

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
We don't need no education.
We don't need no thought control.

Bug#1034908: Update libabsl-dev to new upstream version/snapshot for newer protobuf

[Pirate Praveen]

Control: forwarded
-1 https://salsa.debian.org/debian/abseil/-/merge_requests/1


On Thu, 27 Apr 2023 16:55:49 +0530 Pirate Praveen 
 wrote:

> Package: libabsl-dev
> Version: 20220623.1-1
> Severity: wishlist
> Control: block 1034668 by -1
> Control: affects -1 protobuf
>
> Please update libabsl-dev so that we can build protobuf 3.22.3 in
> experimental.
>
> CMake Error at cmake/libprotobuf-lite.cmake:26 
(target_link_libraries):

>   Target "libprotobuf-lite" links to:
>
> absl::absl_check
>
>   but the target was not found. Possible reasons include:
>
> * There is a typo in the target name.
> * A find_package call is missing for an IMPORTED target.
> * An ALIAS target is missing.
>
> Call Stack (most recent call first):
>   CMakeLists.txt:354 (include)
>
> If you want to reprpoduce this, a wip version is available at
> https://people.debian.org/~praveen/new/pool/main/p/protobuf/

I have created a merge request with the new upstream version
https://salsa.debian.org/debian/abseil/-/merge_requests/1

though now the error changed to,
CMake Error at cmake/tests.cmake:97 (target_link_libraries):
 Target "tests" links to:

   absl::scoped_mock_log

 but the target was not found. Possible reasons include:

   * There is a typo in the target name.
   * A find_package call is missing for an IMPORTED target.
   * An ALIAS target is missing.

Call Stack (most recent call first):
 CMakeLists.txt:401 (include)

Bug#1034757: unblock (pre-approval): scilab/6.1.1+dfsg2-5 libjogl2-java/2.3.2+dfsg-10 gluegen2/2.3.2-9

[Pierre Gruet]

Control: tags -1 - moreinfo

Hi Paul,

Le 27/04/2023 à 11:38, Paul Gevers a écrit :

Control: tags -1 moreinfo

Hi Pierre,

On Sun, 23 Apr 2023 17:27:30 +0200 Pierre Gruet  wrote:
This unblock would lead to new upstream versions (with some packaging 
work more
complex than just refreshing patches) of gluegen2 and libjogl2 shipped 
into
Bookworm, which I trust to be OK as they have only one rdep, king, 
which works

well with them.


Are targeted fixes an option? We're well past new upstreams being 
acceptable [1] unless they are targeted fixes themselves.


Thanks for looking at my proposal. I understand well this is not 
feasible as is. Indeed the fixes I proposed are quite important as they 
require a new upstream version of 2 packages. Also, working around RC 
bug #1034752 in src:gluegen2 requires quite a lot of Debian-specific 
changes.


So I now propose to do something simpler, in order to have Scilab be 
able to start and work plainly except for plotting (which was also the 
case in Bullseye anyway), fixing RC bug #1033496.


In order to get a pre-approval, I only did the change locally (source 
debdiff attached), will upload to unstable if granted.


Below is my proposal:

[ Reason ]

Currently, the key package scilab/6.1.1+dfsg2-5 in sid/testing does not 
start since we have openjdk-17 as default Java machine, see grave bug 
#1033496: it is unusable right now.


[ Impact ]

If the unblock is not granted, scilab will remain unusable in Bookworm.
If it is granted, then it will be working except for plotting.

[ Tests ]

I changed one line in the source, built it in a clean chroot, installed 
in on my machine running Bookworm and could use all of Scilab features 
(plotting aside).


[ Risks ]

No risk, as we would not change the biinaries but only the shell wrapper 
that invokes them with the correct environment variables.


[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes (did them myself) and I approve them
  [X] attach debdiffs of the locally built package against the package
  in testing



Paul
PS: your message didn't reach our list, which is a bad sign about the 
size of the changes.



That's right...!

Best,

--
Pierre
diff -Nru scilab-6.1.1+dfsg2/debian/changelog scilab-6.1.1+dfsg2/debian/changelog
--- scilab-6.1.1+dfsg2/debian/changelog	2023-03-11 16:23:07.0 +0100
+++ scilab-6.1.1+dfsg2/debian/changelog	2023-04-27 12:37:49.0 +0200
@@ -1,3 +1,11 @@
+scilab (6.1.1+dfsg2-6) UNRELEASED; urgency=medium
+
+  * Team upload
+  * Adding another --add-opens clause to the scilab invocation to avoid the
+Exception at GUI start (Closes: #1033496)
+
+ -- Pierre Gruet   Thu, 27 Apr 2023 12:37:49 +0200
+
 scilab (6.1.1+dfsg2-5) unstable; urgency=medium
 
   * Team upload
diff -Nru scilab-6.1.1+dfsg2/debian/patches/populating_java_options_by_default.patch scilab-6.1.1+dfsg2/debian/patches/populating_java_options_by_default.patch
--- scilab-6.1.1+dfsg2/debian/patches/populating_java_options_by_default.patch	2023-03-11 14:13:54.0 +0100
+++ scilab-6.1.1+dfsg2/debian/patches/populating_java_options_by_default.patch	2023-04-27 12:36:03.0 +0200
@@ -14,7 +14,7 @@
 +# We initialize _JAVA_OPTIONS so that the right paths are looked into and we
 +# add the needed --add-opens to work with OpenJDK 17.
 +if ! echo "${_JAVA_OPTIONS}" | grep -q "java\.library\.path" ; then
-+_JAVA_OPTIONS="${_JAVA_OPTIONS} -Djava.library.path=/usr/lib/jni:/usr/lib/scilab --add-opens=java.desktop/sun.awt.X11=ALL-UNNAMED --add-opens=java.desktop/sun.java2d.opengl=ALL-UNNAMED"
++_JAVA_OPTIONS="${_JAVA_OPTIONS} -Djava.library.path=/usr/lib/jni:/usr/lib/scilab --add-opens=java.desktop/sun.awt.X11=ALL-UNNAMED --add-opens=java.desktop/sun.java2d.opengl=ALL-UNNAMED --add-opens=java.desktop/javax.swing.plaf.basic=ALL-UNNAMED"
 +fi
 +
  if test ! -z "$SCIVERBOSE"; then


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1035013: libanet7-dev: missing Breaks+Replaces for libanet5-dev when upgrading from bullseye

[Helmut Grohne]

Package: libanet7-dev
Version: 0.4.3-2
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libanet7-dev/0.4.3-2 from Debian bookworm
on a minimal Debian bullseye with libanet5-dev/0.4.2-4
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/ada/adalib/anet/anet-arp.ali being contained in both 
packages.

| Selecting previously unselected package libanet7-dev.
| (Reading database ... 9228 files and directories currently installed.)
| Preparing to unpack .../libanet7-dev_0.4.3-2_amd64.deb ...
| Unpacking libanet7-dev (0.4.3-2) ...
| dpkg: error processing archive ./libanet7-dev_0.4.3-2_amd64.deb (--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/ada/adalib/anet/anet-arp.ali', which is also in 
package libanet5-dev 0.4.2-4
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Errors were encountered while processing:
|  ./libanet7-dev_0.4.3-2_amd64.deb


Please ensure that libanet7-dev has sufficient Breaks and Replaces declarations.

Helmut

Bug#1035011: libahven11-dev: missing Breaks+Replaces for libahven9-dev when upgrading from bullseye

[Helmut Grohne]

Package: libahven11-dev
Version: 2.8-6
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libahven11-dev/2.8-6 from Debian bookworm
on a minimal Debian bullseye with libahven9-dev/2.8-1
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/ada/adalib/ahven/ahven-astrings.ali being contained 
in both packages.

| Selecting previously unselected package libahven11-dev.
| (Reading database ... 9179 files and directories currently installed.)
| Preparing to unpack .../libahven11-dev_2.8-6_amd64.deb ...
| Unpacking libahven11-dev (2.8-6) ...
| dpkg: error processing archive ./libahven11-dev_2.8-6_amd64.deb (--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/ada/adalib/ahven/ahven-astrings.ali', which is also 
in package libahven9-dev 2.8-1
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Errors were encountered while processing:
|  ./libahven11-dev_2.8-6_amd64.deb


Please ensure that libahven11-dev has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1035012: libzmat-dev: missing Breaks+Replaces for libzmat1-dev when upgrading from bullseye

[Helmut Grohne]

Package: libzmat-dev
Version: 0.9.8+ds-7
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libzmat-dev/0.9.8+ds-7 from Debian bookworm
on a minimal Debian bullseye with libzmat1-dev/0.9.8+ds-3
installed, causes an unpack error from dpkg due to
/usr/include/zmatlib.f90 being contained in both packages.

| Selecting previously unselected package libzmat-dev:amd64.
| (Reading database ... 4701 files and directories currently installed.)
| Preparing to unpack .../libzmat-dev_0.9.8+ds-7_amd64.deb ...
| Unpacking libzmat-dev:amd64 (0.9.8+ds-7) ...
| dpkg: error processing archive ./libzmat-dev_0.9.8+ds-7_amd64.deb (--unpack):
|  trying to overwrite '/usr/include/zmatlib.f90', which is also in package 
libzmat1-dev:amd64 0.9.8+ds-3
| Errors were encountered while processing:
|  ./libzmat-dev_0.9.8+ds-7_amd64.deb


Please ensure that libzmat-dev has sufficient Breaks and Replaces declarations.

Helmut

Bug#1035009: libocct-data-exchange-dev: missing Breaks+Replaces for liboce-modeling-dev when upgrading from bullseye

[Helmut Grohne]

Package: libocct-data-exchange-dev
Version: 7.6.3+dfsg1-5
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libocct-data-exchange-dev/7.6.3+dfsg1-5 from Debian 
bookworm
on a minimal Debian bullseye with liboce-modeling-dev/0.18.3-1
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/libTKIGES.so being contained in both packages.

| Selecting previously unselected package libocct-data-exchange-dev:amd64.
| (Reading database ... 17251 files and directories currently installed.)
| Preparing to unpack .../libocct-data-exchange-dev_7.6.3+dfsg1-5_amd64.deb ...
| Unpacking libocct-data-exchange-dev:amd64 (7.6.3+dfsg1-5) ...
| dpkg: error processing archive 
./libocct-data-exchange-dev_7.6.3+dfsg1-5_amd64.deb (--unpack):
|  trying to overwrite '/usr/lib/x86_64-linux-gnu/libTKIGES.so', which is also 
in package liboce-modeling-dev:amd64 0.18.3-1
| Errors were encountered while processing:
|  ./libocct-data-exchange-dev_7.6.3+dfsg1-5_amd64.deb


Please ensure that libocct-data-exchange-dev has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1035010: libgnatcoll-postgres3-dev: missing Breaks+Replaces for libgnatcoll-postgres1-dev when upgrading from bullseye

[Helmut Grohne]

Package: libgnatcoll-postgres3-dev
Version: 23.0.0-3
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libgnatcoll-postgres3-dev/23.0.0-3 from Debian bookworm
on a minimal Debian bullseye with libgnatcoll-postgres1-dev/21.0.0-6
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_postgres/gnatcoll-sql-postgres.ali
 being contained in both packages.

| Selecting previously unselected package libgnatcoll-postgres3-dev.
| (Reading database ... 10135 files and directories currently installed.)
| Preparing to unpack .../libgnatcoll-postgres3-dev_23.0.0-3_amd64.deb ...
| Unpacking libgnatcoll-postgres3-dev (23.0.0-3) ...
| dpkg: error processing archive ./libgnatcoll-postgres3-dev_23.0.0-3_amd64.deb 
(--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_postgres/gnatcoll-sql-postgres.ali',
 which is also in package libgnatcoll-postgres1-dev 21.0.0-6
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Errors were encountered while processing:
|  ./libgnatcoll-postgres3-dev_23.0.0-3_amd64.deb


Please ensure that libgnatcoll-postgres3-dev has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1035008: node-jest-worker: missing Breaks+Replaces for jest when upgrading from bullseye

[Helmut Grohne]

Package: node-jest-worker
Version: 29.3.1~ds1+~cs70.48.25-1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack node-jest-worker/29.3.1~ds1+~cs70.48.25-1 from Debian 
bookworm
on a minimal Debian bullseye with jest/26.6.3+repack+~cs64.44.39-3
installed, causes an unpack error from dpkg due to
/usr/share/nodejs/@jest/types/build/Circus.d.ts being contained in both 
packages.

| dpkg: considering deconfiguration of jest, which would be broken by 
installation of node-jest-worker ...
| dpkg: yes, will deconfigure jest (broken by node-jest-worker)
| (Reading database ... 21294 files and directories currently installed.)
| Preparing to unpack .../node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb ...
| De-configuring jest (26.6.3+repack+~cs64.44.39-3) ...
| Unpacking node-jest-worker (29.3.1~ds1+~cs70.48.25-1) over 
(26.6.3+repack+~cs64.44.39-3) ...
| dpkg: error processing archive 
./node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb (--unpack):
|  trying to overwrite '/usr/share/nodejs/@jest/types/build/Circus.d.ts', which 
is also in package jest 26.6.3+repack+~cs64.44.39-3
| Errors were encountered while processing:
|  ./node-jest-worker_29.3.1~ds1+~cs70.48.25-1_all.deb


Please ensure that node-jest-worker has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1035007: davmail-server: missing Breaks+Replaces for davmail when upgrading from bullseye

[Helmut Grohne]

Package: davmail-server
Version: 6.0.1.3390-6
Severity: serious
Justification: dpkg unpack error

Attempting to unpack davmail-server/6.0.1.3390-6 from Debian bookworm
on a minimal Debian bullseye with davmail/5.5.1.3299-5
installed, causes an unpack error from dpkg due to
/etc/davmail/davmail.properties being contained in both packages.

| Selecting previously unselected package davmail-server.
| dpkg: considering deconfiguration of davmail, which would be broken by 
installation of davmail-server ...
| dpkg: yes, will deconfigure davmail (broken by davmail-server)
| (Reading database ... 6734 files and directories currently installed.)
| Preparing to unpack .../davmail-server_6.0.1.3390-6_all.deb ...
| De-configuring davmail (5.5.1.3299-5) ...
| Unpacking davmail-server (6.0.1.3390-6) ...
| dpkg: error processing archive ./davmail-server_6.0.1.3390-6_all.deb 
(--unpack):
|  trying to overwrite '/etc/davmail/davmail.properties', which is also in 
package davmail 5.5.1.3299-5
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| invoke-rc.d: could not determine current runlevel
| invoke-rc.d: policy-rc.d denied execution of restart.
| Errors were encountered while processing:
|  ./davmail-server_6.0.1.3390-6_all.deb


Please ensure that davmail-server has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1035006: libflorist2022-dev: missing Breaks+Replaces for libflorist2020-dev when upgrading from bullseye

[Helmut Grohne]

Package: libflorist2022-dev
Version: 2022.0.1~20220616-2
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libflorist2022-dev/2022.0.1~20220616-2 from Debian bookworm
on a minimal Debian bullseye with libflorist2020-dev/2017-9
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/ada/adalib/florist/ada_streams.ali being contained in 
both packages.

| Selecting previously unselected package libflorist2022-dev.
| (Reading database ... 9336 files and directories currently installed.)
| Preparing to unpack .../libflorist2022-dev_2022.0.1~20220616-2_amd64.deb ...
| Unpacking libflorist2022-dev (2022.0.1~20220616-2) ...
| dpkg: error processing archive 
./libflorist2022-dev_2022.0.1~20220616-2_amd64.deb (--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/ada/adalib/florist/ada_streams.ali', which is also 
in package libflorist2020-dev 2017-9
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Errors were encountered while processing:
|  ./libflorist2022-dev_2022.0.1~20220616-2_amd64.deb


Please ensure that libflorist2022-dev has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1035005: uwsgi-plugin-jvm-openjdk-17: missing Breaks+Replaces for uwsgi-plugin-jvm-openjdk-11 when upgrading from bullseye

[Helmut Grohne]

Package: uwsgi-plugin-jvm-openjdk-17
Version: 2.0.21-5
Severity: serious
Justification: dpkg unpack error

Attempting to unpack uwsgi-plugin-jvm-openjdk-17/2.0.21-5 from Debian bookworm
on a minimal Debian bullseye with uwsgi-plugin-jvm-openjdk-11/2.0.19.1-7.1
installed, causes an unpack error from dpkg due to
/usr/share/java/uwsgi.jar being contained in both packages.

| Selecting previously unselected package uwsgi-plugin-jvm-openjdk-17.
| (Reading database ... 6132 files and directories currently installed.)
| Preparing to unpack .../uwsgi-plugin-jvm-openjdk-17_2.0.21-5_amd64.deb ...
| Unpacking uwsgi-plugin-jvm-openjdk-17 (2.0.21-5) ...
| dpkg: error processing archive 
./uwsgi-plugin-jvm-openjdk-17_2.0.21-5_amd64.deb (--unpack):
|  trying to overwrite '/usr/share/java/uwsgi.jar', which is also in package 
uwsgi-plugin-jvm-openjdk-11 2.0.19.1-7.1
| Errors were encountered while processing:
|  ./uwsgi-plugin-jvm-openjdk-17_2.0.21-5_amd64.deb


Please ensure that uwsgi-plugin-jvm-openjdk-17 has sufficient Breaks and 
Replaces declarations.

Helmut

Bug#1035003: python3-meep-openmpi: missing Breaks+Replaces in multiple situations when upgrading from bullseye

[Helmut Grohne]

Package: python3-meep-openmpi
Version: 1.25.0-1+b1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack python3-meep-openmpi/1.25.0-1+b1 from Debian bookworm
on a minimal Debian bullseye with python3-meep-mpi-default/1.17.1-2
installed, causes an unpack error from dpkg due to
/usr/lib/python3/dist-packages/meep/__init__.py being contained in both 
packages.

| Selecting previously unselected package python3-meep-openmpi.
| (Reading database ... 9458 files and directories currently installed.)
| Preparing to unpack .../python3-meep-openmpi_1.25.0-1+b1_amd64.deb ...
| Unpacking python3-meep-openmpi (1.25.0-1+b1) ...
| dpkg: error processing archive ./python3-meep-openmpi_1.25.0-1+b1_amd64.deb 
(--unpack):
|  trying to overwrite '/usr/lib/python3/dist-packages/meep/__init__.py', which 
is also in package python3-meep-mpi-default 1.17.1-2
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Processing triggers for libc-bin (2.31-13+deb11u5) ...
| Errors were encountered while processing:
|  ./python3-meep-openmpi_1.25.0-1+b1_amd64.deb

Attempting to unpack python3-meep-openmpi/1.25.0-1+b1 from Debian bookworm
on a minimal Debian bullseye with python3-meep/1.17.1-1
installed, causes an unpack error from dpkg due to
/usr/lib/python3/dist-packages/meep/__init__.py being contained in both 
packages.

| Selecting previously unselected package python3-meep-openmpi.
| (Reading database ... 8718 files and directories currently installed.)
| Preparing to unpack .../python3-meep-openmpi_1.25.0-1+b1_amd64.deb ...
| Unpacking python3-meep-openmpi (1.25.0-1+b1) ...
| dpkg: error processing archive ./python3-meep-openmpi_1.25.0-1+b1_amd64.deb 
(--unpack):
|  trying to overwrite '/usr/lib/python3/dist-packages/meep/__init__.py', which 
is also in package python3-meep 1.17.1-1
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Processing triggers for libc-bin (2.31-13+deb11u5) ...
| Errors were encountered while processing:
|  ./python3-meep-openmpi_1.25.0-1+b1_amd64.deb


Please ensure that python3-meep-openmpi has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1035004: libalog8-dev: missing Breaks+Replaces for libalog6-dev when upgrading from bullseye

[Helmut Grohne]

Package: libalog8-dev
Version: 0.6.2-2
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libalog8-dev/0.6.2-2 from Debian bookworm
on a minimal Debian bullseye with libalog6-dev/0.6.1-4
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/ada/adalib/alog/alog-active_logger.ali being 
contained in both packages.

| Selecting previously unselected package libalog8-dev.
| (Reading database ... 9183 files and directories currently installed.)
| Preparing to unpack .../libalog8-dev_0.6.2-2_amd64.deb ...
| Unpacking libalog8-dev (0.6.2-2) ...
| dpkg: error processing archive ./libalog8-dev_0.6.2-2_amd64.deb (--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/ada/adalib/alog/alog-active_logger.ali', which is 
also in package libalog6-dev 0.6.1-4
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Errors were encountered while processing:
|  ./libalog8-dev_0.6.2-2_amd64.deb


Please ensure that libalog8-dev has sufficient Breaks and Replaces declarations.

Helmut

Bug#1035002: libgnatcoll-readline21-dev: missing Breaks+Replaces for libgnatcoll-readline19-dev when upgrading from bullseye

[Helmut Grohne]

Package: libgnatcoll-readline21-dev
Version: 23.0.0-5
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libgnatcoll-readline21-dev/23.0.0-5 from Debian bookworm
on a minimal Debian bullseye with libgnatcoll-readline19-dev/21.0.0-4
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_readline/gnatcoll-readline.ali 
being contained in both packages.

| Selecting previously unselected package libgnatcoll-readline21-dev.
| (Reading database ... 10158 files and directories currently installed.)
| Preparing to unpack .../libgnatcoll-readline21-dev_23.0.0-5_amd64.deb ...
| Unpacking libgnatcoll-readline21-dev (23.0.0-5) ...
| dpkg: error processing archive 
./libgnatcoll-readline21-dev_23.0.0-5_amd64.deb (--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_readline/gnatcoll-readline.ali', 
which is also in package libgnatcoll-readline19-dev 21.0.0-4
| Errors were encountered while processing:
|  ./libgnatcoll-readline21-dev_23.0.0-5_amd64.deb


Please ensure that libgnatcoll-readline21-dev has sufficient Breaks and 
Replaces declarations.

Helmut

Bug#1035001: wbar: missing Breaks+Replaces for wbar-config when upgrading from bullseye

[Helmut Grohne]

Package: wbar
Version: 2.3.4-12
Severity: serious
Justification: dpkg unpack error

Attempting to unpack wbar/2.3.4-12 from Debian bookworm
on a minimal Debian bullseye with wbar-config/2.3.4-10
installed, causes an unpack error from dpkg due to
/usr/share/wbar/glade/wbar.glade being contained in both packages.

| (Reading database ... 12816 files and directories currently installed.)
| Preparing to unpack ./wbar_2.3.4-12_amd64.deb ...
| Unpacking wbar (2.3.4-12) over (2.3.4-10) ...
| dpkg: error processing archive ./wbar_2.3.4-12_amd64.deb (--unpack):
|  trying to overwrite '/usr/share/wbar/glade/wbar.glade', which is also in 
package wbar-config 2.3.4-10
| Processing triggers for hicolor-icon-theme (0.17-2) ...
| Errors were encountered while processing:
|  ./wbar_2.3.4-12_amd64.deb


Please ensure that wbar has sufficient Breaks and Replaces declarations.

Helmut

Bug#1035000: node-core-js-pure: missing Breaks+Replaces for node-core-js when upgrading from bullseye

[Helmut Grohne]

Package: node-core-js-pure
Version: 3.26.1-1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack node-core-js-pure/3.26.1-1 from Debian bookworm
on a minimal Debian bullseye with node-core-js/3.8.2-2
installed, causes an unpack error from dpkg due to
/usr/share/nodejs/core-js-pure/configurator.js being contained in both packages.

| Selecting previously unselected package node-core-js-pure.
| dpkg: considering deconfiguration of node-core-js, which would be broken by 
installation of node-core-js-pure ...
| dpkg: yes, will deconfigure node-core-js (broken by node-core-js-pure)
| (Reading database ... 7666 files and directories currently installed.)
| Preparing to unpack .../node-core-js-pure_3.26.1-1_all.deb ...
| De-configuring node-core-js (3.8.2-2) ...
| Unpacking node-core-js-pure (3.26.1-1) ...
| dpkg: error processing archive ./node-core-js-pure_3.26.1-1_all.deb 
(--unpack):
|  trying to overwrite '/usr/share/nodejs/core-js-pure/configurator.js', which 
is also in package node-core-js 3.8.2-2
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Errors were encountered while processing:
|  ./node-core-js-pure_3.26.1-1_all.deb


Please ensure that node-core-js-pure has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1034999: librust-sha3-0.9-dev: missing Breaks+Replaces for librust-sha3-dev when upgrading from bullseye

[Helmut Grohne]

Package: librust-sha3-0.9-dev
Version: 0.9.1-1+b1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack librust-sha3-0.9-dev/0.9.1-1+b1 from Debian bookworm
on a minimal Debian bullseye with librust-sha3-dev/0.9.1-1
installed, causes an unpack error from dpkg due to
/usr/share/cargo/registry/sha3-0.9.1/.cargo-checksum.json being contained in 
both packages.

| Selecting previously unselected package librust-sha3-0.9-dev:amd64.
| dpkg: considering deconfiguration of librust-sha3-dev:amd64, which would be 
broken by installation of librust-sha3-0.9-dev:amd64 ...
| dpkg: yes, will deconfigure librust-sha3-dev:amd64 (broken by 
librust-sha3-0.9-dev:amd64)
| (Reading database ... 4873 files and directories currently installed.)
| Preparing to unpack .../librust-sha3-0.9-dev_0.9.1-1+b1_amd64.deb ...
| De-configuring librust-sha3-dev:amd64 (0.9.1-1) ...
| Unpacking librust-sha3-0.9-dev:amd64 (0.9.1-1+b1) ...
| dpkg: error processing archive ./librust-sha3-0.9-dev_0.9.1-1+b1_amd64.deb 
(--unpack):
|  trying to overwrite 
'/usr/share/cargo/registry/sha3-0.9.1/.cargo-checksum.json', which is also in 
package librust-sha3-dev:amd64 0.9.1-1
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Errors were encountered while processing:
|  ./librust-sha3-0.9-dev_0.9.1-1+b1_amd64.deb


Please ensure that librust-sha3-0.9-dev has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1034998: pcp-export-pcp2elasticsearch: missing Breaks+Replaces for pcp when upgrading from bullseye

[Helmut Grohne]

Package: pcp-export-pcp2elasticsearch
Version: 6.0.3-1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack pcp-export-pcp2elasticsearch/6.0.3-1 from Debian bookworm
on a minimal Debian bullseye with pcp/5.2.6-1
installed, causes an unpack error from dpkg due to
/usr/bin/pcp2elasticsearch being contained in both packages.

| Selecting previously unselected package pcp-export-pcp2elasticsearch.
| dpkg: considering deconfiguration of pcp, which would be broken by 
installation of pcp-export-pcp2elasticsearch ...
| dpkg: yes, will deconfigure pcp (broken by pcp-export-pcp2elasticsearch)
| (Reading database ... 10064 files and directories currently installed.)
| Preparing to unpack .../pcp-export-pcp2elasticsearch_6.0.3-1_amd64.deb ...
| De-configuring pcp (5.2.6-1) ...
| invoke-rc.d: could not determine current runlevel
| invoke-rc.d: policy-rc.d denied execution of stop.
| invoke-rc.d: could not determine current runlevel
| invoke-rc.d: policy-rc.d denied execution of stop.
| invoke-rc.d: could not determine current runlevel
| invoke-rc.d: policy-rc.d denied execution of stop.
| invoke-rc.d: could not determine current runlevel
| invoke-rc.d: policy-rc.d denied execution of stop.
| Unpacking pcp-export-pcp2elasticsearch (6.0.3-1) ...
| dpkg: error processing archive 
./pcp-export-pcp2elasticsearch_6.0.3-1_amd64.deb (--unpack):
|  trying to overwrite '/usr/bin/pcp2elasticsearch', which is also in package 
pcp 5.2.6-1
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| invoke-rc.d: could not determine current runlevel
| invoke-rc.d: policy-rc.d denied execution of start.
| invoke-rc.d: could not determine current runlevel
| invoke-rc.d: policy-rc.d denied execution of start.
| Errors were encountered while processing:
|  ./pcp-export-pcp2elasticsearch_6.0.3-1_amd64.deb


Please ensure that pcp-export-pcp2elasticsearch has sufficient Breaks and 
Replaces declarations.

Helmut

Bug#1034997: libdtkcommon: missing Breaks+Replaces for libdtkcore5 when upgrading from bullseye

[Helmut Grohne]

Package: libdtkcommon
Version: 5.5.23-1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libdtkcommon/5.5.23-1 from Debian bookworm
on a minimal Debian bullseye with libdtkcore5/5.2.2.5-3
installed, causes an unpack error from dpkg due to
/usr/share/glib-2.0/schemas/com.deepin.dtk.gschema.xml being contained in both 
packages.

| Selecting previously unselected package libdtkcommon.
| dpkg: considering deconfiguration of libdtkcore5:amd64, which would be broken 
by installation of libdtkcommon ...
| dpkg: yes, will deconfigure libdtkcore5:amd64 (broken by libdtkcommon)
| (Reading database ... 5903 files and directories currently installed.)
| Preparing to unpack .../libdtkcommon_5.5.23-1_amd64.deb ...
| De-configuring libdtkcore5:amd64 (5.2.2.5-3) ...
| Unpacking libdtkcommon (5.5.23-1) ...
| dpkg: error processing archive ./libdtkcommon_5.5.23-1_amd64.deb (--unpack):
|  trying to overwrite 
'/usr/share/glib-2.0/schemas/com.deepin.dtk.gschema.xml', which is also in 
package libdtkcore5:amd64 5.2.2.5-3
| Processing triggers for libc-bin (2.31-13+deb11u5) ...
| Processing triggers for libglib2.0-0:amd64 (2.66.8-1) ...
| Errors were encountered while processing:
|  ./libdtkcommon_5.5.23-1_amd64.deb


Please ensure that libdtkcommon has sufficient Breaks and Replaces declarations.

Helmut

Bug#1034996: libomemo0: missing Breaks+Replaces for libomemo-dev when upgrading from bullseye

[Helmut Grohne]

Package: libomemo0
Version: 0.8.1-1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libomemo0/0.8.1-1 from Debian bookworm
on a minimal Debian bullseye with libomemo-dev/0.7.0-1
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/libomemo.so being contained in both packages.

| (Reading database ... 12426 files and directories currently installed.)
| Preparing to unpack ./libomemo0_0.8.1-1_amd64.deb ...
| Unpacking libomemo0:amd64 (0.8.1-1) over (0.7.0-1) ...
| dpkg: error processing archive ./libomemo0_0.8.1-1_amd64.deb (--unpack):
|  trying to overwrite '/usr/lib/x86_64-linux-gnu/libomemo.so', which is also 
in package libomemo-dev:amd64 0.7.0-1
| Processing triggers for libc-bin (2.31-13+deb11u5) ...
| Errors were encountered while processing:
|  ./libomemo0_0.8.1-1_amd64.deb


Please ensure that libomemo0 has sufficient Breaks and Replaces declarations.

Helmut

Bug#1034995: python-is-python3: missing Breaks+Replaces for python-dev-is-python2 when upgrading from bullseye

[Helmut Grohne]

Package: python-is-python3
Version: 3.11.1-3
Severity: serious
Justification: dpkg unpack error

Attempting to unpack python-is-python3/3.11.1-3 from Debian bookworm
on a minimal Debian bullseye with python-dev-is-python2/2.7.18-9
installed, causes an unpack error from dpkg due to
/usr/bin/pydoc being contained in both packages.

| Selecting previously unselected package python-is-python3.
| dpkg: considering deconfiguration of python-is-python2, which would be broken 
by installation of python-is-python3 ...
| dpkg: yes, will deconfigure python-is-python2 (broken by python-is-python3)
| (Reading database ... 9300 files and directories currently installed.)
| Preparing to unpack .../python-is-python3_3.11.1-3_all.deb ...
| De-configuring python-is-python2 (2.7.18-9) ...
| Unpacking python-is-python3 (3.11.1-3) ...
| dpkg: error processing archive ./python-is-python3_3.11.1-3_all.deb 
(--unpack):
|  trying to overwrite '/usr/bin/pydoc', which is also in package 
python-dev-is-python2 2.7.18-9
| Errors were encountered while processing:
|  ./python-is-python3_3.11.1-3_all.deb


Please ensure that python-is-python3 has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1034994: librust-semver-0.9-dev: missing Breaks+Replaces for librust-semver-dev when upgrading from bullseye

[Helmut Grohne]

Package: librust-semver-0.9-dev
Version: 0.9.0-3+b1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack librust-semver-0.9-dev/0.9.0-3+b1 from Debian bookworm
on a minimal Debian bullseye with librust-semver-dev/0.9.0-1+b1
installed, causes an unpack error from dpkg due to
/usr/share/cargo/registry/semver-0.9.0/.cargo-checksum.json being contained in 
both packages.

| Selecting previously unselected package librust-semver-0.9-dev:amd64.
| dpkg: considering deconfiguration of librust-semver-dev:amd64, which would be 
broken by installation of librust-semver-0.9-dev:amd64 ...
| dpkg: yes, will deconfigure librust-semver-dev:amd64 (broken by 
librust-semver-0.9-dev:amd64)
| (Reading database ... 4714 files and directories currently installed.)
| Preparing to unpack .../librust-semver-0.9-dev_0.9.0-3+b1_amd64.deb ...
| De-configuring librust-semver-dev:amd64 (0.9.0-1+b1) ...
| Unpacking librust-semver-0.9-dev:amd64 (0.9.0-3+b1) ...
| dpkg: error processing archive ./librust-semver-0.9-dev_0.9.0-3+b1_amd64.deb 
(--unpack):
|  trying to overwrite 
'/usr/share/cargo/registry/semver-0.9.0/.cargo-checksum.json', which is also in 
package librust-semver-dev:amd64 0.9.0-1+b1
| Errors were encountered while processing:
|  ./librust-semver-0.9-dev_0.9.0-3+b1_amd64.deb


Please ensure that librust-semver-0.9-dev has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1034993: software-properties-qt: missing Breaks+Replaces for software-properties-kde when upgrading from bullseye

[Helmut Grohne]

Package: software-properties-qt
Version: 0.99.30-4
Severity: serious
Justification: dpkg unpack error

Attempting to unpack software-properties-qt/0.99.30-4 from Debian bookworm
on a minimal Debian bullseye with software-properties-kde/0.96.20.2-2.1
installed, causes an unpack error from dpkg due to
/usr/share/software-properties/designer/dialog_add.ui being contained in both 
packages.

| Selecting previously unselected package software-properties-qt.
| (Reading database ... 11560 files and directories currently installed.)
| Preparing to unpack .../software-properties-qt_0.99.30-4_all.deb ...
| Unpacking software-properties-qt (0.99.30-4) ...
| dpkg: error processing archive ./software-properties-qt_0.99.30-4_all.deb 
(--unpack):
|  trying to overwrite '/usr/share/software-properties/designer/dialog_add.ui', 
which is also in package software-properties-kde 0.96.20.2-2.1
| Errors were encountered while processing:
|  ./software-properties-qt_0.99.30-4_all.deb


Please ensure that software-properties-qt has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1034992: slurm-wlm-rrd-plugin: missing Breaks+Replaces for slurm-wlm-basic-plugins when upgrading from bullseye

[Helmut Grohne]

Package: slurm-wlm-rrd-plugin
Version: 22.05.8-3
Severity: serious
Justification: dpkg unpack error

Attempting to unpack slurm-wlm-rrd-plugin/22.05.8-3 from Debian bookworm
on a minimal Debian bullseye with 
slurm-wlm-basic-plugins/20.11.7+really20.11.4-2+deb11u1
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/slurm-wlm/ext_sensors_rrd.so being contained in both 
packages.

| Selecting previously unselected package slurm-wlm-rrd-plugin.
| (Reading database ... 5770 files and directories currently installed.)
| Preparing to unpack .../slurm-wlm-rrd-plugin_22.05.8-3_amd64.deb ...
| Unpacking slurm-wlm-rrd-plugin (22.05.8-3) ...
| dpkg: error processing archive ./slurm-wlm-rrd-plugin_22.05.8-3_amd64.deb 
(--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/slurm-wlm/ext_sensors_rrd.so', which is also in 
package slurm-wlm-basic-plugins 20.11.7+really20.11.4-2+deb11u1
| Errors were encountered while processing:
|  ./slurm-wlm-rrd-plugin_22.05.8-3_amd64.deb


Please ensure that slurm-wlm-rrd-plugin has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1034990: [INTL:be] updated Belarusian translation

[Viktar Siarheichyk]

Package: grub-installer
Version: 1.190

be.po
Description: application/po

Severity: wishlist
Tags: patch l10n
Please find attached the updated Belarusian translation.

Bug#1034991: libgnatcoll-omp3-dev: missing Breaks+Replaces for libgnatcoll-omp1-dev when upgrading from bullseye

[Helmut Grohne]

Package: libgnatcoll-omp3-dev
Version: 23.0.0-5
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libgnatcoll-omp3-dev/23.0.0-5 from Debian bookworm
on a minimal Debian bullseye with libgnatcoll-omp1-dev/21.0.0-4
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_omp/a-cvgpso.ali being contained 
in both packages.

| Selecting previously unselected package libgnatcoll-omp3-dev.
| (Reading database ... 10018 files and directories currently installed.)
| Preparing to unpack .../libgnatcoll-omp3-dev_23.0.0-5_amd64.deb ...
| Unpacking libgnatcoll-omp3-dev (23.0.0-5) ...
| dpkg: error processing archive ./libgnatcoll-omp3-dev_23.0.0-5_amd64.deb 
(--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll_omp/a-cvgpso.ali', which is also 
in package libgnatcoll-omp1-dev 21.0.0-4
| Errors were encountered while processing:
|  ./libgnatcoll-omp3-dev_23.0.0-5_amd64.deb


Please ensure that libgnatcoll-omp3-dev has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1034989: node-core-js-bundle: missing Breaks+Replaces for node-core-js when upgrading from bullseye

[Helmut Grohne]

Package: node-core-js-bundle
Version: 3.26.1-1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack node-core-js-bundle/3.26.1-1 from Debian bookworm
on a minimal Debian bullseye with node-core-js/3.8.2-2
installed, causes an unpack error from dpkg due to
/usr/share/nodejs/core-js-bundle/package.json being contained in both packages.

| Selecting previously unselected package node-core-js-bundle.
| dpkg: considering deconfiguration of node-core-js, which would be broken by 
installation of node-core-js-bundle ...
| dpkg: yes, will deconfigure node-core-js (broken by node-core-js-bundle)
| (Reading database ... 7666 files and directories currently installed.)
| Preparing to unpack .../node-core-js-bundle_3.26.1-1_all.deb ...
| De-configuring node-core-js (3.8.2-2) ...
| Unpacking node-core-js-bundle (3.26.1-1) ...
| dpkg: error processing archive ./node-core-js-bundle_3.26.1-1_all.deb 
(--unpack):
|  trying to overwrite '/usr/share/nodejs/core-js-bundle/package.json', which 
is also in package node-core-js 3.8.2-2
| Errors were encountered while processing:
|  ./node-core-js-bundle_3.26.1-1_all.deb


Please ensure that node-core-js-bundle has sufficient Breaks and Replaces 
declarations.

Helmut

Bug#1034988: python3-meep: missing Breaks+Replaces in multiple situations when upgrading from bullseye

[Helmut Grohne]

Package: python3-meep
Version: 1.25.0-1+b1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack python3-meep/1.25.0-1+b1 from Debian bookworm
on a minimal Debian bullseye with python3-meep-mpi-default/1.17.1-2
installed, causes an unpack error from dpkg due to
/usr/lib/python3/dist-packages/meep/__init__.py being contained in both 
packages.

| Selecting previously unselected package python3-meep.
| (Reading database ... 9458 files and directories currently installed.)
| Preparing to unpack .../python3-meep_1.25.0-1+b1_amd64.deb ...
| Unpacking python3-meep (1.25.0-1+b1) ...
| dpkg: error processing archive ./python3-meep_1.25.0-1+b1_amd64.deb 
(--unpack):
|  trying to overwrite '/usr/lib/python3/dist-packages/meep/__init__.py', which 
is also in package python3-meep-mpi-default 1.17.1-2
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Processing triggers for libc-bin (2.31-13+deb11u5) ...
| Errors were encountered while processing:
|  ./python3-meep_1.25.0-1+b1_amd64.deb

Attempting to unpack python3-meep/1.25.0-1+b1 from Debian bookworm
on a minimal Debian bullseye with python3-meep-openmpi/1.17.1-2
installed, causes an unpack error from dpkg due to
/usr/lib/python3/dist-packages/meep/__init__.py being contained in both 
packages.

| Selecting previously unselected package python3-meep.
| (Reading database ... 9458 files and directories currently installed.)
| Preparing to unpack .../python3-meep_1.25.0-1+b1_amd64.deb ...
| Unpacking python3-meep (1.25.0-1+b1) ...
| dpkg: error processing archive ./python3-meep_1.25.0-1+b1_amd64.deb 
(--unpack):
|  trying to overwrite '/usr/lib/python3/dist-packages/meep/__init__.py', which 
is also in package python3-meep-openmpi 1.17.1-2
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Processing triggers for libc-bin (2.31-13+deb11u5) ...
| Errors were encountered while processing:
|  ./python3-meep_1.25.0-1+b1_amd64.deb


Please ensure that python3-meep has sufficient Breaks and Replaces declarations.

Helmut

Bug#1034987: slurm-wlm-elasticsearch-plugin: missing Breaks+Replaces for slurm-wlm-basic-plugins when upgrading from bullseye

[Helmut Grohne]

Package: slurm-wlm-elasticsearch-plugin
Version: 22.05.8-3
Severity: serious
Justification: dpkg unpack error

Attempting to unpack slurm-wlm-elasticsearch-plugin/22.05.8-3 from Debian 
bookworm
on a minimal Debian bullseye with 
slurm-wlm-basic-plugins/20.11.7+really20.11.4-2+deb11u1
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/slurm-wlm/jobcomp_elasticsearch.so being contained in 
both packages.

| Selecting previously unselected package slurm-wlm-elasticsearch-plugin.
| (Reading database ... 5770 files and directories currently installed.)
| Preparing to unpack .../slurm-wlm-elasticsearch-plugin_22.05.8-3_amd64.deb ...
| Unpacking slurm-wlm-elasticsearch-plugin (22.05.8-3) ...
| dpkg: error processing archive 
./slurm-wlm-elasticsearch-plugin_22.05.8-3_amd64.deb (--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/slurm-wlm/jobcomp_elasticsearch.so', which is also 
in package slurm-wlm-basic-plugins 20.11.7+really20.11.4-2+deb11u1
| Errors were encountered while processing:
|  ./slurm-wlm-elasticsearch-plugin_22.05.8-3_amd64.deb


Please ensure that slurm-wlm-elasticsearch-plugin has sufficient Breaks and 
Replaces declarations.

Helmut