Bug#1034939: marked as done (librust-block-buffer-0.9-dev: missing Breaks+Replaces for librust-block-buffer-dev when upgrading from bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 02 May 2023 05:48:48 +
with message-id 
and subject line Bug#1034939: fixed in rust-block-buffer-0.9 0.9.0-2
has caused the Debian Bug report #1034939,
regarding librust-block-buffer-0.9-dev: missing Breaks+Replaces for 
librust-block-buffer-dev when upgrading from bullseye
to be marked as done.

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

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


-- 
1034939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-block-buffer-0.9-dev
Version: 0.9.0-1+b1
Severity: serious
Justification: dpkg unpack error

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

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


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

Helmut
--- End Message ---
--- Begin Message ---
Source: rust-block-buffer-0.9
Source-Version: 0.9.0-2
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-block-buffer-0.9, which is due to be installed in the Debian FTP archive.

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 May 2023 05:28:11 +
Source: rust-block-buffer-0.9
Architecture: source
Version: 0.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1034939
Changes:
 rust-block-buffer-0.9 (0.9.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Declare breaks+replaces on physical package instead of virtual one
 (Closes: #1034939)
Checksums-Sha1:
 4eeac0a79a4591a71fb05cdd9653b7e2d6076dd8 2400 rust-block-buffer-0.9_0.9.0-2.dsc
 db2a98660590af2dfd1bbb21c547986891e616d6 3016 
rust-block-buffer-0.9_0.9.0-2.debian.tar.xz
 4c635c80a8393046f769ac0c9c6f335fdcba41c8 7390 
rust-block-buffer-0.9_0.9.0-2_source.buildinfo
Checksums-Sha256:
 eac7b327d2bad02e5ce6f69ef14b9da856a1c1ca5dcc156a6583d4e08e7a40eb 2400 
rust-block-buffer-0.9_0.9.0-2.dsc
 941fd165e23a37fdd51369306084bb1a5fab6f5d78f4622bfbb6a464d2746a6c 3016 
rust-block-buffer-0.9_0.9.0-2.debian.tar.xz
 4f3fdca0579e6696d415057a48e2f7fde7935e22759a1f15949df195933b9ae5 7390 
rust-block-buffer-0.9_0.9.0-2_source.buildinfo
Files:
 f4d255fc8d330363c3d1071ae67fcbb2 2400 rust optional 
rust-block-buffer-0.9_0.9.0-2.dsc
 892258ee03c843739c6951722a7751db 3016 rust optional 
rust-block-buffer-0.9_0.9.0-2.debian.tar.xz
 c6af62545c9700ef43a8c5b68863799e 7390 rust optional 
rust-block-buffer-0.9_0.9.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmRQoW8UHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XuRxhAAnSf2NbgR/yUdy0NdaFvLEtznvMIU
LAfPu3h6AWKx83JPTyURQGjwobXg6cIMquPX/sPlgGzcoXD4bk+HGRgM+hoedtJb
Fkrrivto7uda/9jlrFQ2G2QHEKZMGsMWE6ZD8QUyYUtTZZc3aD271mXvZWpQm1Tg

Bug#1034969: Fwd: Bug#1034969: terser: missing Breaks+Replaces for uglifyjs.terser when upgrading from bullseye

[Jonas Smedegaard]

Quoting Yadd (2023-05-02 04:58:47)
> a previous "unblock" was missing here: unstable version is 5.16.5-1 
> while testing version is 5.16.4-1. What do you want to do, fix only this 
> bug with a 5.16.5-really-5.16.4-1 or a full update ?

It is a bugfix release, and as such I would consider it relevant for
stable, but I get exhausted just thinking about the need for "defending"
changes against the release team: If you do it, you can desice if you
want to try get all of it in or only a (arguably too) minimal patch.

Thanks!

 - Jonas

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

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

signature.asc
Description: signature

Bug#1034969: Fwd: Bug#1034969: terser: missing Breaks+Replaces for uglifyjs.terser when upgrading from bullseye

[Yadd]

Hi,

a previous "unblock" was missing here: unstable version is 5.16.5-1 
while testing version is 5.16.4-1. What do you want to do, fix only this 
bug with a 5.16.5-really-5.16.4-1 or a full update ?


On 5/1/23 08:37, Jonas Smedegaard wrote:

Thanks for the patch, Yadd - and for the bugreport, Helmut.

I am quite busy elsewhere currently - if you have the time then I would
appreciate if you would handle this issue.

Otherwise I'll try make time for it the upcoming weekend.

  - Jonas

Quoting Yadd (2023-04-28 05:38:56)

Hi Jonas,

it seems that "Breaks" fields needs to be duplicated in "Replaces":

diff --git a/debian/control b/debian/control
index 6772ac76..3d8f1174 100644
--- a/debian/control
+++ b/debian/control
@@ -34,6 +34,9 @@ Depends:
   Breaks:
uglifyjs.terser (<< 4.8.0-1~),
node-rollup-plugin-terser (<< 7.0.2+~5.0.1-3~)
+Replaces:
+ uglifyjs.terser (<< 4.8.0-1~),
+ node-rollup-plugin-terser (<< 7.0.2+~5.0.1-3~)
   Suggests:
terser,
   Multi-Arch: foreign
@@ -87,6 +90,8 @@ Recommends:
node-source-map-support,
   Breaks:
uglifyjs.terser (<< 4.8.0-1~),
+Replaces:
+ uglifyjs.terser (<< 4.8.0-1~),
   Suggests:
node-acorn,
   Multi-Arch: foreign

Cheers,
Yadd

 Forwarded Message 
Subject: [Pkg-javascript-devel] Bug#1034969: terser: missing
Breaks+Replaces for uglifyjs.terser when upgrading from bullseye
Resent-Date: Thu, 27 Apr 2023 13:11:12 +
Resent-From: Helmut Grohne 
Resent-To: debian-bugs-d...@lists.debian.org
Resent-CC: Debian Javascript Maintainers

Date: Thu, 27 Apr 2023 14:59:55 +0200
From: Helmut Grohne 
Reply-To: Helmut Grohne , 1034...@bugs.debian.org
To: sub...@bugs.debian.org

Package: terser
Version: 5.16.4-1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack terser/5.16.4-1 from Debian bookworm
on a minimal Debian bullseye with uglifyjs.terser/4.1.2-8
installed, causes an unpack error from dpkg due to
/usr/share/nodejs/terser/bin/uglifyjs being contained in both packages.

| Selecting previously unselected package terser.
| dpkg: considering deconfiguration of uglifyjs.terser, which would be
broken by installation of terser ...
| dpkg: yes, will deconfigure uglifyjs.terser (broken by terser)
| (Reading database ... 4922 files and directories currently installed.)
| Preparing to unpack ./terser_5.16.4-1_all.deb ...
| De-configuring uglifyjs.terser (4.1.2-8) ...
| Unpacking terser (5.16.4-1) ...
| dpkg: error processing archive ./terser_5.16.4-1_all.deb (--unpack):
|  trying to overwrite '/usr/share/nodejs/terser/bin/uglifyjs', which is
also in package uglifyjs.terser 4.1.2-8
| Errors were encountered while processing:
|  ./terser_5.16.4-1_all.deb


Please ensure that terser has sufficient Breaks and Replaces declarations.

Helmut

--
Pkg-javascript-devel mailing list
pkg-javascript-de...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Processed: user debian...@lists.debian.org, usertagging 1024661, usertagging 996227, found 981878 in 1.3.1-2 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 1024661 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 996227 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 981878 1.3.1-2
Bug #981878 [src:ruby-gitlab-pg-query] ruby-gitlab-pg-query downloads from the 
internet during the build
Marked as found in versions ruby-gitlab-pg-query/1.3.1-2.
> usertags 981878 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 1027350 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 1027339 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 1004719 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 997288 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 1029199 piuparts
There were no usertags set.
Usertags are now: piuparts.
> severity 1029199 serious
Bug #1029199 [taskell] taskell: Depends: libffi7 (>= 3.3~20180313) but it is 
not installable
Severity set to 'serious' from 'important'
> usertags 1014623 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 947586 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 941453 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 941453 + libvibe-utils0
Bug #941453 [src:vibe.d] vibe.d: FTBFS with libphobos2-ldc-shared86
Added indication that 941453 affects libvibe-utils0
> usertags 1008979 piuparts
Usertags were: edos-uninstallable.
Usertags are now: edos-uninstallable piuparts.
> affects 1008979 + libasis2019.1
Bug #1008979 [src:asis] asis: depends on gnat-util, almost orphaned upstream
Added indication that 1008979 affects libasis2019.1
> usertags 993701 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 993701 + srslte-core
Bug #993701 [src:srslte] srslte: FTBFS with libsoapysdr 0.8
Added indication that 993701 affects srslte-core
> usertags 1013153 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1013153 + libcamitk5
Bug #1013153 [camitk] camitk: vtk[6,7] removal
Added indication that 1013153 affects libcamitk5
> usertags 1012464 piuparts
Usertags were: edos-uninstallable.
Usertags are now: edos-uninstallable piuparts.
> usertags 1031476 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 1024790 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1024790 + libortools8
Bug #1024790 [src:ortools] ortools: FTBFS everywhere
Added indication that 1024790 affects libortools8
> usertags 1012893 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1012893 + libanfo0
Bug #1012893 [src:anfo] anfo: ftbfs with GCC-12
Added indication that 1012893 affects libanfo0
> usertags 1008981 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1008981 + libaws6
Bug #1008981 [src:libaws] libaws: depends on unavailable asis
Added indication that 1008981 affects libaws6
> usertags 1031346 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1031346 + libgnuradio-dab3.8.0
Bug #1031346 [gr-dab] gr-dab not installable due to dependency on outdated 
gnuradio 3.8 (current is 3.10)
Added indication that 1031346 affects libgnuradio-dab3.8.0
> usertags 984187 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 984187 + libneo4j-client11
Bug #984187 [src:libneo4j-client] libneo4j-client: ftbfs with GCC-11
Added indication that 984187 affects libneo4j-client11
> usertags 1019172 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1019172 + libngram2
Bug #1019172 [src:opengrm-ngram] opengrm-ngram FTBFS against libfst 1.7.9
Added indication that 1019172 affects libngram2
> usertags 1001528 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1001528 + libpurify2.0
Bug #1001528 [src:purify] FTBFS with eigen3/3.4.0
Added indication that 1001528 affects libpurify2.0
> usertags 1022008 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1022008 + librm0
Bug #1022008 [src:librm] librm: transition to gssdp/gupnp 1.6
Added indication that 1022008 affects librm0
> usertags 1006506 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1006506 + libzorpll-7.0-4
Bug #1006506 [src:libzorpll] libzorpll: FTBFS with OpenSSL 3.0
Added indication that 1006506 affects libzorpll-7.0-4
> usertags 1002760 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 966726 piuparts
Usertags were: edos-uninstallable.
Usertags are now: edos-uninstallable piuparts.
> usertags 1028527 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1028527 + i2masschroq-tools
Bug #1028527 [src:i2masschroq] i2masschroq: FTBFS in local pbuilder
Added indication that 1028527 affects 

Processed: not fixed in experimental

[Debian Bug Tracking System]

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

> unarchive 983303
Bug #983303 {Done: Paul Gevers } [src:imagemagick] 
imagemagick: reproducible builds: Embeds different paths on usrmerge system
Unarchived Bug 983303
> found 983303 8:6.9.12.20+dfsg1-1.2
Bug #983303 {Done: Paul Gevers } [src:imagemagick] 
imagemagick: reproducible builds: Embeds different paths on usrmerge system
Marked as found in versions imagemagick/8:6.9.12.20+dfsg1-1.2 and reopened.
> thanks
Stopping processing here.

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

Processed: pytorch-ignite: FTBFS: py3versions: empty set of versions

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + python3-torch-ignite
Bug #1035366 [src:pytorch-ignite] pytorch-ignite: FTBFS: py3versions: empty set 
of versions
Added indication that 1035366 affects python3-torch-ignite

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

Bug#1035366: pytorch-ignite: FTBFS: py3versions: empty set of versions

[Andreas Beckmann]

Source: pytorch-ignite
Version: 0.4.3-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python3-torch-ignite


pytorch-ignite FTBFS in sid (it builds fine in bullseye):

 fakeroot debian/rules clean
dh clean -Spybuild --with python3
   dh_auto_clean -O-Spybuild
py3versions: empty set of versions
E: py3versions failed at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/pybuild.pm line 53.
make: *** [debian/rules:5: clean] Error 1


Andreas

Processed: user debian...@lists.debian.org, found 1034758 in 4.1.0.3-5, affects 1034758, usertagging 1024499 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> found 1034758 4.1.0.3-5
Bug #1034758 [x2goserver-common] x2goserver-common: fails to purge - command 
(deluser|delgroup) in postrm not found
Marked as found in versions x2goserver/4.1.0.3-5.
> affects 1034758 + x2goserver-desktopsharing x2goserver-extensions 
> x2goserver-fmbindings x2goserver-printing x2goserver-xsession
Bug #1034758 [x2goserver-common] x2goserver-common: fails to purge - command 
(deluser|delgroup) in postrm not found
Added indication that 1034758 affects x2goserver-desktopsharing, 
x2goserver-extensions, x2goserver-fmbindings, x2goserver-printing, and 
x2goserver-xsession
> usertags 1024499 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1024499 + python3-bdsf
Bug #1024499 [src:pybdsf] pybdsf: FTBFS with Python 3.11 as a supported version
Added indication that 1024499 affects python3-bdsf
> usertags 1028633 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1028633 + python3-mlpack
Bug #1028633 [src:mlpack] mlpack: FTBFS: mkdir: cannot create directory 
‘/usr/lib/python3.11/site-packages/’: Permission denied
Added indication that 1028633 affects python3-mlpack
> usertags 1009424 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1009424 + python3-mpltoolkits.basemap
Bug #1009424 [src:basemap] basemap: FTBFS: dh_install: error: missing files, 
aborting
Added indication that 1009424 affects python3-mpltoolkits.basemap
> usertags 1028896 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1028896 + python3-qiskit-aer
Bug #1028896 [src:qiskit-aer] qiskit-aer: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.10 3.11" returned exit code 13
Added indication that 1028896 affects python3-qiskit-aer
> usertags 1012074 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1012074 + python3-rocksdb
Bug #1012074 [src:python-rocksdb] python-rocksdb: FTBFS with rocksdb 7.2+
Added indication that 1012074 affects python3-rocksdb
> usertags 982647 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 982647 + python3-spyder-reports
Bug #982647 [src:spyder-reports] spyder-reports: incompatible with spyder 4.2.1+
Added indication that 982647 affects python3-spyder-reports
> usertags 1009423 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1009423 + python3-subvertpy
Bug #1009423 [src:subvertpy] subvertpy: FTBFS: pydoctor: error: Error parsing 
config: "Couldn't parse TOML file: Found invalid character in key name: ':'. 
Try quoting the key name. (line 1 column 9 char 8)", "Couldn't parse INI file: 
File contains no section headers.\nfile: '', line: 1\n'packages: 
subvertpy\\n'"
Added indication that 1009423 affects python3-subvertpy
> usertags 1004805 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1004805 + python3-xmmsclient
Bug #1004805 [src:xmms2] xmms2: FTBFS with ffmpeg 5.0
Added indication that 1004805 affects python3-xmmsclient
> usertags 1022504 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1022504 + python3-xrstools
Bug #1022504 [src:xrstools] xrstools: FTBFS: 
distutils.errors.DistutilsClassError: command class  must subclass Command
Added indication that 1022504 affects python3-xrstools
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1004805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004805
1009423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009423
1009424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009424
1012074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012074
1022504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022504
1024499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024499
1028633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028633
1028896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028896
1034758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034758
982647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1035364: lttng-modules-dkms: fails to build module on bullseye for Linux 5.10.0-22-amd64

[Andreas Beckmann]

Package: lttng-modules-dkms
Version: 2.12.5-1
Severity: serious
Tags: bullseye
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up lttng-modules-dkms (2.12.5-1) ...
  Loading new lttng-modules-2.12.5 DKMS files...
  It is likely that 6.1.20 belongs to a chroot's host
  Building for 5.10.0-22-amd64
  Building initial module for 5.10.0-22-amd64
  Error! Bad return status for module build on kernel: 5.10.0-22-amd64 (x86_64)
  Consult /var/lib/dkms/lttng-modules/2.12.5/build/make.log for more 
information.
  dpkg: error processing package lttng-modules-dkms (--configure):
   installed lttng-modules-dkms package post-installation script subprocess 
returned error exit status 10
  Processing triggers for libc-bin (2.31-13+deb11u6) ...
  Errors were encountered while processing:
   lttng-modules-dkms


DKMS make.log for lttng-modules-2.12.5 for kernel 5.10.0-22-amd64 (x86_64)
Mon May  1 23:45:42 UTC 2023
make: Entering directory '/usr/src/linux-headers-5.10.0-22-amd64'
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lttng-ring-buffer-client-discard.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lttng-ring-buffer-client-overwrite.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lttng-ring-buffer-metadata-client.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lttng-ring-buffer-client-mmap-discard.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lttng-ring-buffer-client-mmap-overwrite.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lttng-ring-buffer-metadata-mmap-client.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-clock.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-events.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-abi.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-string-utils.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-probes.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context-pid.o
/var/lib/dkms/lttng-modules/2.12.5/build/probes/Kbuild:62: File 
/usr/src/linux-headers-5.10.0-22-common/arch/x86/kvm/lapic.h not found. Probe 
"kvm" x86-specific is disabled. Use full kernel source tree to enable it.
/var/lib/dkms/lttng-modules/2.12.5/build/probes/Kbuild:166: Files 
/usr/src/linux-headers-5.10.0-22-common/fs/btrfs/*.h not found. Probe "btrfs" 
is disabled. Use full kernel source tree to enable it.
/var/lib/dkms/lttng-modules/2.12.5/build/probes/Kbuild:177: Files 
/usr/src/linux-headers-5.10.0-22-common/fs/ext4/*.h not found. Probe "ext4" is 
disabled. Use full kernel source tree to enable it.
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context-procname.o
/var/lib/dkms/lttng-modules/2.12.5/build/probes/Kbuild:208: File 
/usr/src/linux-headers-5.10.0-22-common/drivers/base/regmap/trace.h not found. 
Probe "regmap" is disabled. Need Linux 4.1+ kernel source tree to enable it.
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lib/ringbuffer/ring_buffer_backend.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-sched.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/tests/probes/lttng-test.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context-prio.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context-nice.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context-vpid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-irq.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-timer.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/tests/clock-plugin/lttng-clock-plugin-test.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context-tid.o
  LD [M]  /var/lib/dkms/lttng-modules/2.12.5/build/tests/lttng-test.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context-vtid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context-ppid.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lib/ringbuffer/ring_buffer_frontend.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lib/ringbuffer/ring_buffer_iterator.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lib/ringbuffer/ring_buffer_vfs.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lib/ringbuffer/ring_buffer_splice.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context-vppid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-kmem.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context-cpu-id.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/lib/ringbuffer/ring_buffer_mmap.o
  LD [M]  
/var/lib/dkms/lttng-modules/2.12.5/build/tests/lttng-clock-plugin-test.o
  CC [M]  /var/lib/dkms/lttng-modules/2.12.5/build/lttng-context-uid.o
  CC [M]  

Bug#1035363: torrus-common: fails to install: addgroup with two arguments is an unspecified operation.

[Andreas Beckmann]

Package: torrus-common
Version: 3.00-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up torrus-common (3.00-1.1) ...
  dpkg: error processing package torrus-common (--configure):
   installed torrus-common package post-installation script subprocess returned 
error exit status 1
  Processing triggers for libc-bin (2.36-9) ...
  Errors were encountered while processing:
   torrus-common

Re-running the postinst script with set -x:

Setting up torrus-common (3.00-1.1) ...
+ set -e
+ dpkg-maintscript-helper rm_conffile /etc/logrotate.d/torrus-common 2.01-3 -- 
configure
+ test -L /etc/apache2/conf.d/torrus-apache2.conf
+ configure_user_group
+ adduser --quiet --system --no-create-home --home /nonexistent --force-badname 
--group Debian-torrus
+ fix_owner_perm
+ chown Debian-torrus:Debian-torrus /var/lib/torrus /var/log/torrus
+ chmod g+w /var/log/torrus
+ chmod g+w /var/lib/torrus/session_data/lock /var/lib/torrus/session_data/store
+ [ -d /var/cache/torrus ]
+ rm -rf /var/lib/torrus/db
+ addgroup www-data Debian-torrus

Re-running the last command manually in the chroot without output
redirection:

# addgroup www-data Debian-torrus
addgroup: addgroup with two arguments is an unspecified operation.


cheers,

Andreas


torrus-common_3.00-1.1.log.gz
Description: application/gzip

Bug#1035361: sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755

[Andreas Beckmann]

Package: sauce
Version: 0.9.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package's logrotate
configuration causes logrotate to exit with an error after the package
has been removed (*) or when logrote is run but no logfile exists.

Usually the solution is to specify 'missingok' in the logrotate
configuration.

*) logrotate configuration files remain installed and executed after a
package has been removed, they only get removed when the package is
purged.

>From the attached log (scroll to the bottom...):

0m17.0s DEBUG: Starting command: ['chroot', 
'/srv/piuparts.debian.org/tmp/tmp6h9n6ntx', '/usr/sbin/logrotate', 
'/etc/logrotate.d/sauce']
0m17.0s DUMP: 
  warning: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755
0m17.0s DEBUG: Command ok: ['chroot', 
'/srv/piuparts.debian.org/tmp/tmp6h9n6ntx', '/usr/sbin/logrotate', 
'/etc/logrotate.d/sauce']
0m17.0s ERROR: FAIL: Logrotate file /etc/logrotate.d/sauce exits with error or 
has output with package removed


Setting severity to serious since this does not seem limited to being
emitted after package removal but always. The current logrotate version
in sid seems to be more strict.


cheers,

Andreas


sauce_0.9.1.log.gz
Description: application/gzip

Bug#1035360: bookworm RC2 installation leaves luks encrypted system in unbootable state

[Cyril Brulebois]

[ Reordering slightly ]

Cyril Brulebois  (2023-05-02):
> Paul Seelig  (2023-05-02):
> > Attached installation logs should be sufficiently verbose about what
> > actually happened underneath.
> 
> Either it was forgotten or dropped by the BTS; please use reply-all,
> and attach it compressed (to avoid hitting size limits on either the
> BTS side or on the debian-boot ML side).

For reference:
 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035360#10
 - 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=1035360;filename=installer-logs.tar.xz;msg=10

> > Apparently, the required cryptsetup-initramfs packages were removed
> > from the system during the last instalation stages, rendering the
> > resulting system unbootable.

That's not quite what happened. Instead, the cryptsetup-initramfs wasn't
available to start with:

Apr 30 16:11:44 in-target: Package cryptsetup-initramfs is not available, 
but is referred to by another package.
Apr 30 16:11:44 in-target: E: Package 'cryptsetup-initramfs' has no 
installation candidate

Later on, cryptsetup got removed along with a bunch of live packages.

Presumably, if cryptsetup-initramfs had been successfully installed, it
would have kept cryptsetup around.

Again, I'm not familiar with the live environment, it'd be great if some
with some knowledge about the way it operates and/or the way it's built
could comment on this.

Adding debian-live@ for now, but might be debian-cd@ territory…

Very wild guess: Could cryptsetup-initramfs be missing from live-setup?
  https://salsa.debian.org/images-team/live-setup.git


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


signature.asc
Description: PGP signature

Processed: found 1035350 in 3.1.4-7

[Debian Bug Tracking System]

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

> found 1035350 3.1.4-7
Bug #1035350 [postfix] postfix: postinst script modifies configuration files 
despite local changes
Marked as found in versions postfix/3.1.4-7.
> thanks
Stopping processing here.

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

Bug#1035350: postfix: postinst script modifies configuration files despite local changes

[Scott Kitterman]

On Monday, May 1, 2023 3:20:19 PM EDT Einhard Leichtfuß wrote:
> On 01/05/2023 19:47, Scott Kitterman wrote:
> > On Monday, May 1, 2023 1:01:17 PM EDT Einhard Leichtfuß wrote:
> >> On 01/05/2023 18:14, Scott Kitterman wrote:
> >>> On Monday, May 1, 2023 11:06:07 AM EDT Einhard Leichtfuß wrote:
>  Package: postfix
> > 
> > ...
> > 
>  In `main.cf`, the following lines were appended:
> > readme_directory = /usr/share/doc/postfix
> > html_directory = /usr/share/doc/postfix/html
>  
>  If I understand the postinst script correctly, this modification of
>  `main.cf` should only have happened upon first installation, which this
>  was not.  I was unable to reproduce this.  So maybe this modification
>  was indeed done earlier.
>  
>  However, even upon initial installation (with pre-existing
>  configuration), this should, in my opinion, not happen.
> > 
> > ...
> > 
> >>> Also, note that the message about is about main.cf not being modified.
> >>> These changes are in master.cf, so I don't understand the concern with
> >>> the message?
> >> 
> >> The second modification (readme_directory, html_directory) was to
> >> `main.cf`.  While this modification should only happen for initial
> >> installations (with pre-existing configuration), the message is
> >> displayed even then.
> >> 
> >> Steps to reproduce (assuming postfix is not installed):
> >> 
> >> $ apt install postfix-doc
> >> $ echo > /etc/postfix/main.cf
> >> $ apt install postfix
> > 
> > To focus in on the main.cf part of this, I believe that's per policy.
> > 
> > First, it's a change made by postfix-doc, not postifx, so the postfix
> > package statement that main.cf was not modified by it is correct and
> > unrelated to the main.cf change.
> 
> Ah, I did not check the postfix-doc postinst script.  It seems that both
> postfix-doc's and postfix's postinst scripts conditionally run
> 
>   postconf -e readme_directory=/usr/share/doc/postfix
> html_directory=/usr/share/doc/postfix/html
> 
> However, postfix's postinst script only does so in the arguably rare
> case that postfix-doc was installed first.  So one might argue that this
> is still an action performed for postfix-doc falling under Policy 10.7.4.
> 
> > For the postfix-doc change to main.cf, Policy 10.7.4 is the relevant
> > portion. Postfix-doc uses the provided interface (postfconf), when
> > available.
> It is not clear to me that Policy 10.7.4 overrides Policy 10.7.3 w.r.t.
> the requirement not to override local changes.  While this may very well
> not be the intention behind these policies, I'd understand them as such
> that the related package (postfix-doc) must only [be able to] modify the
> configuration file if it does not contain local changes.
> 
> I.e., either the provided program (currently postconf) should refuse to
> modify a locally modified configuration file, or the related package
> (postfix-doc) should check for local changes itself.
> 
> I am generally unsure, however, how detection of local modification is
> supposed to work in practice without using conffiles.  I suppose a
> second configuration file copy that is modified by postinst scripts, but
> not the local administrator, should work.

Preserve local modifications means don't undo specific changes made by the 
local 
administrator.  It does not mean make no changes to a file that an 
administrator has made changes to.  The use of postconf specifically enables 
changing the values relevant to postfix-doc without disturbing anything else in 
the file.  I think this is fine.

Scott K


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

Bug#1035360: bookworm RC2 installation leaves luks encrypted system in unbootable state

[Cyril Brulebois]

Hi Paul,

and thanks for the report.

Paul Seelig  (2023-05-02):
> using the xfce4 based RC2 live ISO image[1], on a Thinkpad T480 (16GB
> RAM/256GB NVME/INTEL GRAPHICS ONLY) installation of Debian in an luks
> encrypted LVM was performed.
> 
> Apparently, the required cryptsetup-initramfs packages were removed
> from the system during the last instalation stages, rendering the
> resulting system unbootable.

Oh wow, that looks bad. Unfortunately I'm mostly familiar with the
regular d-i installer, not so much with the live counterpart.

> Manual intervention was required to fix the issue from a live rescue
> system, something a novice user will never be able to accomplish.

Can't agree with you more. (Even with a developer hat, the first time
one gets confronted with a LUKS system that cannot be unlocked leaves
traces… Still remembering that initramfs bug I encountered around 2010,
as if it were yesterday…)

FWIW: While I'm not sure about live images (and I won't check right
now), regular d-i offers a rescue mode which automates the painful
detecting and unlocking steps when it comes to LUKS stuff, so you don't
have to know about cryptsetup luksOpen and friends to get a shell into
the installed system.

> The same issue was already note with the prior RC1 variant of this
> bookworm live ISO. It can be reliably reproduced. 

Helpful data point, thanks.

> Attached installation logs should be sufficiently verbose about what
> actually happened underneath.

Either it was forgotten or dropped by the BTS; please use reply-all,
and attach it compressed (to avoid hitting size limits on either the BTS
side or on the debian-boot ML side).


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


signature.asc
Description: PGP signature

Bug#1035360: bookworm RC2 installation leaves luks encrypted system in unbootable state

[Paul Seelig]

Package: debian-installer
Severity: grave
X-Debbugs-Cc: think...@rumbero.org

Hi all,

using the xfce4 based RC2 live ISO image[1], on a Thinkpad T480 (16GB RAM/256GB 
NVME/INTEL GRAPHICS ONLY) installation of Debian in an luks encrypted LVM was 
performed.

Apparently, the required cryptsetup-initramfs packages were removed from the 
system during the last instalation stages, rendering the resulting system 
unbootable. 
Manual intervention was required to fix the issue from a live rescue system, 
something a novice user will never be able to accomplish.

The same issue was already note with the prior RC1 variant of this bookworm 
live ISO. It can be reliably reproduced. 
Attached installation logs should be sufficiently verbose about what actually 
happened underneath.

[1] 
https://cdimage.debian.org/cdimage/bookworm_di_rc2-live/amd64/iso-hybrid/debian-live-bkworm-DI-rc2-amd64-xfce.iso

Regards,
P.Seelig

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-security'), (500, 
'oldstable-proposed-updates'), (500, 'unstable'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-8-amd64 (SMP w/8 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

Bug#1034310: Another issue which is not fixed in 7.x.x

[Rainer Dorsch]

Comment 35 in upstream bugreport:

https://bugs.kde.org/show_bug.cgi?id=466170#c35

Thanks for the backtrace, the problem in slotEmptyMessageTimer() is known and 
was fixed about 5 months ago. We seem to have forgotten the backport to 
digiKam-7.x.x when I look at the history. Only with digiKam-8.0.0 will the 
problem no longer occur.


-- 
Rainer Dorsch
http://bokomoko.de/

Bug#1035282: marked as done (firmware-brcm80211: broken symlinks: /lib/firmware/brcm/brcmfmac4356-sdio.*,*.txt -> brcmfmac4356-sdio.AP6356S.txt)

[Debian Bug Tracking System]

Your message dated Mon, 01 May 2023 19:49:53 +
with message-id 
and subject line Bug#1035282: fixed in firmware-nonfree 20230210-5
has caused the Debian Bug report #1035282,
regarding firmware-brcm80211: broken symlinks: 
/lib/firmware/brcm/brcmfmac4356-sdio.*,*.txt -> brcmfmac4356-sdio.AP6356S.txt
to be marked as done.

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

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


-- 
1035282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-brcm80211
Version: 20230210-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m14.9s ERROR: WARN: Broken symlinks:
  /lib/firmware/brcm/brcmfmac4356-sdio.khadas,vim2.txt -> 
brcmfmac4356-sdio.AP6356S.txt (firmware-brcm80211)
  /lib/firmware/brcm/brcmfmac4356-sdio.vamrs,rock960.txt -> 
brcmfmac4356-sdio.AP6356S.txt (firmware-brcm80211)

Severity serious, since this likely means that the kernel cannot find
the firmware at the expected location.


cheers,

Andreas


firmware-brcm80211_20230210-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: firmware-nonfree
Source-Version: 20230210-5
Done: Salvatore Bonaccorso 

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

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated firmware-nonfree 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 May 2023 21:30:16 +0200
Source: firmware-nonfree
Architecture: source
Version: 20230210-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1035282
Changes:
 firmware-nonfree (20230210-5) unstable; urgency=medium
 .
   * brcm80211: brcm: rename Rock960 NVRAM to AP6356S and link devices to it
 (Closes: #1035282)
   * Update to linux-support 6.1.0-8
Checksums-Sha1:
 69c17b044126806cb09de93999c8fed8a898f794 4276 firmware-nonfree_20230210-5.dsc
 5fd690bc99be5dc165d88c8aff9df73da2bc5455 827972 
firmware-nonfree_20230210-5.debian.tar.xz
 98d4e36884115ebe5e95753ae9fc589e5d9387bb 6029 
firmware-nonfree_20230210-5_source.buildinfo
Checksums-Sha256:
 dc91a89403ca8a40cfb3745cad2099815cf75ba5a5da17caf022ea5b9a2fe8bf 4276 
firmware-nonfree_20230210-5.dsc
 64f5cd779ca920afcafabca224f7c27e0be8b6e40698e2d38860bc25f1612998 827972 
firmware-nonfree_20230210-5.debian.tar.xz
 a641340fc6452c132ee6585d54451e4321152028540fee61545c464c40da2e26 6029 
firmware-nonfree_20230210-5_source.buildinfo
Files:
 fceecc387756d8fd8610b9a5bec08fac 4276 non-free-firmware/kernel optional 
firmware-nonfree_20230210-5.dsc
 1741a3c09fa4d8cc85c8250cb0d5969d 827972 non-free-firmware/kernel optional 
firmware-nonfree_20230210-5.debian.tar.xz
 0301249dd29389417cb6fcc76d81dd80 6029 non-free-firmware/kernel optional 
firmware-nonfree_20230210-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmRQE/hfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89ESSkP/Awa2c6QlBFal1XUoG5kqwkotXUj51KM
OhEU+sgsDFBskqPLk+BEfkg6cQ+YL+Rk+DRXWlc3npe1iUroe/r+TsQm+kV0Pxid
Qxna1msA6fieZle1enihbz6s6vcfT+2FlQRQqHL0u2Dpq/5R/yilbrwKPErz3dLI
vtGdMgrRatvbroNr1Ew3Tevq8qpJdcjDK62AhBxLq8bqoQS3qlaWtsoBiaMCXJze
9I4c3VR0QPEfHj5C242arVwzwjXX2gI45QTiEtz3eHnZ+g3k71Qk2Q9vkjmVtnSR
/UDbAW369BEclM9v2cGWwCH05arYrLu9M8sCWIb3VTjb69KpCxp6ZCJKJQW+y6lG
PY812ahC7TEUNFpkshQe4feqrTQpuMvPdg5TaMujgttbQ2NH81H5mdqn+nqfrebP
2Ir2M3hd88gwhMIL8T5Caxbxmn0iO9UqkuUHDRAbt86GIAxUNYgOiqVFZIh5V8Fa
hzliZkhObhTCU0BN8F7al5C0hjRAtubLFS05mFjhGIaVD3hZLMxbVzfSP9fmhXxU
4IRGIrI2A3YSG52k33xOYuLSdpH6AXM6VJ//Dejr0G6uA3vNhqG7vzUl7Alet9cH
leb3o7xopxaOVefnt1B1tMU+ka0hmZkxTzS5hK9QM6LEZbD9NHD6p1hXCEJhymSF
pPho8vxIsNre
=rJVj
-END PGP SIGNATURE End Message ---

Bug#1035350: postfix: postinst script modifies configuration files despite local changes

[Einhard Leichtfuß]

On 01/05/2023 19:47, Scott Kitterman wrote:
> On Monday, May 1, 2023 1:01:17 PM EDT Einhard Leichtfuß wrote:
>> On 01/05/2023 18:14, Scott Kitterman wrote:
>>> On Monday, May 1, 2023 11:06:07 AM EDT Einhard Leichtfuß wrote:
 Package: postfix
> ...
 In `main.cf`, the following lines were appended:
> readme_directory = /usr/share/doc/postfix
> html_directory = /usr/share/doc/postfix/html

 If I understand the postinst script correctly, this modification of
 `main.cf` should only have happened upon first installation, which this
 was not.  I was unable to reproduce this.  So maybe this modification
 was indeed done earlier.

 However, even upon initial installation (with pre-existing
 configuration), this should, in my opinion, not happen.
> ...
>>> Also, note that the message about is about main.cf not being modified. 
>>> These changes are in master.cf, so I don't understand the concern with
>>> the message?
>> The second modification (readme_directory, html_directory) was to
>> `main.cf`.  While this modification should only happen for initial
>> installations (with pre-existing configuration), the message is
>> displayed even then.
>>
>> Steps to reproduce (assuming postfix is not installed):
>>
>> $ apt install postfix-doc
>> $ echo > /etc/postfix/main.cf
>> $ apt install postfix
> 
> To focus in on the main.cf part of this, I believe that's per policy.
> 
> First, it's a change made by postfix-doc, not postifx, so the postfix package 
> statement that main.cf was not modified by it is correct and unrelated to the 
> main.cf change.

Ah, I did not check the postfix-doc postinst script.  It seems that both
postfix-doc's and postfix's postinst scripts conditionally run

  postconf -e readme_directory=/usr/share/doc/postfix
html_directory=/usr/share/doc/postfix/html

However, postfix's postinst script only does so in the arguably rare
case that postfix-doc was installed first.  So one might argue that this
is still an action performed for postfix-doc falling under Policy 10.7.4.

> For the postfix-doc change to main.cf, Policy 10.7.4 is the relevant portion. 
>  
> Postfix-doc uses the provided interface (postfconf), when available.

It is not clear to me that Policy 10.7.4 overrides Policy 10.7.3 w.r.t.
the requirement not to override local changes.  While this may very well
not be the intention behind these policies, I'd understand them as such
that the related package (postfix-doc) must only [be able to] modify the
configuration file if it does not contain local changes.

I.e., either the provided program (currently postconf) should refuse to
modify a locally modified configuration file, or the related package
(postfix-doc) should check for local changes itself.

I am generally unsure, however, how detection of local modification is
supposed to work in practice without using conffiles.  I suppose a
second configuration file copy that is modified by postinst scripts, but
not the local administrator, should work.

> I checked and this goes back at least to when the postfix packaging was first 
> kept in git in 2007.  I think this part is not a bug.  Please let me know if 
> I'm misunderstanding the issue.
> 
> I suspect the master.cf fix_master can be removed entirely, but I'm not 100% 
> certain yet.


Best regards,
Einhard Leichtfuß

Bug#1035350: postfix: postinst script modifies configuration files despite local changes

[Scott Kitterman]

On Monday, May 1, 2023 1:01:17 PM EDT Einhard Leichtfuß wrote:
> On 01/05/2023 18:14, Scott Kitterman wrote:
> > On Monday, May 1, 2023 11:06:07 AM EDT Einhard Leichtfuß wrote:
> >> Package: postfix
...
> >> In `main.cf`, the following lines were appended:
> >>> readme_directory = /usr/share/doc/postfix
> >>> html_directory = /usr/share/doc/postfix/html
> >> 
> >> If I understand the postinst script correctly, this modification of
> >> `main.cf` should only have happened upon first installation, which this
> >> was not.  I was unable to reproduce this.  So maybe this modification
> >> was indeed done earlier.
> >> 
> >> However, even upon initial installation (with pre-existing
> >> configuration), this should, in my opinion, not happen.
...
> > Also, note that the message about is about main.cf not being modified. 
> > These changes are in master.cf, so I don't understand the concern with
> > the message?
> The second modification (readme_directory, html_directory) was to
> `main.cf`.  While this modification should only happen for initial
> installations (with pre-existing configuration), the message is
> displayed even then.
> 
> Steps to reproduce (assuming postfix is not installed):
> 
> $ apt install postfix-doc
> $ echo > /etc/postfix/main.cf
> $ apt install postfix

To focus in on the main.cf part of this, I believe that's per policy.

First, it's a change made by postfix-doc, not postifx, so the postfix package 
statement that main.cf was not modified by it is correct and unrelated to the 
main.cf change.

For the postfix-doc change to main.cf, Policy 10.7.4 is the relevant portion.  
Postfix-doc uses the provided interface (postfconf), when available.

I checked and this goes back at least to when the postfix packaging was first 
kept in git in 2007.  I think this part is not a bug.  Please let me know if 
I'm misunderstanding the issue.

I suspect the master.cf fix_master can be removed entirely, but I'm not 100% 
certain yet.

Scott K

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

Bug#1035098: marked as done (file transfer to manpages without proper relationship)

[Debian Bug Tracking System]

Your message dated Mon, 01 May 2023 17:48:53 +
with message-id 
and subject line Bug#1035098: fixed in inn2 2.7.1-1
has caused the Debian Bug report #1035098,
regarding file transfer to manpages without proper relationship
to be marked as done.

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

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


-- 
1035098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: manpages-dev
Version: 6.03-1
Severity: serious
Justification: dpkg unpack error

Attempting to unpack manpages-dev/6.03-1 from Debian bookworm
on a minimal Debian bullseye with inn2-dev/2.6.4-2
installed, causes an unpack error from dpkg due to
/usr/share/man/man3/list.3.gz being contained in both packages.

| Selecting previously unselected package manpages-dev.
| (Reading database ... 4741 files and directories currently installed.)
| Preparing to unpack ./manpages-dev_6.03-1_all.deb ...
| Unpacking manpages-dev (6.03-1) ...
| dpkg: error processing archive ./manpages-dev_6.03-1_all.deb (--unpack):
|  trying to overwrite '/usr/share/man/man3/list.3.gz', which is also in 
package inn2-dev 2.6.4-2
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Errors were encountered while processing:
|  ./manpages-dev_6.03-1_all.deb


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

Helmut
--- End Message ---
--- Begin Message ---
Source: inn2
Source-Version: 2.7.1-1
Done: Marco d'Itri 

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

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

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

Debian distribution maintenance software
pp.
Marco d'Itri  (supplier of updated inn2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 May 2023 19:25:42 +0200
Source: inn2
Architecture: source
Version: 2.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Marco d'Itri 
Changed-By: Marco d'Itri 
Closes: 1035098
Changes:
 inn2 (2.7.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Breaks manpages-dev << 6.03-2 to make upgrades smoother, because of
 file(3) and list(3) removed from inn2-dev 2.6.5-1. (Closes: #1035098)
Checksums-Sha1:
 107a2bca75627f76171df07ae109b5212bcda374 1567 inn2_2.7.1-1.dsc
 c23b58bcff9db3f92e91002f10502b16302ab16e 1543116 inn2_2.7.1.orig.tar.xz
 b04f8c6268aa208bac802112e635f04a6820276e 36396 inn2_2.7.1-1.debian.tar.xz
 f9e568b40934014f0ec150de211f5fc1245a5aec 7766 inn2_2.7.1-1_amd64.buildinfo
Checksums-Sha256:
 186ad19d928864f4ad52458f62ceaa28fa15a81bb22d071569bef25c13724956 1567 
inn2_2.7.1-1.dsc
 d6e8d9db5d2bce9054b9f959beaee8af33eb6b1e8583999491c17ee392de33af 1543116 
inn2_2.7.1.orig.tar.xz
 ca7c8d65f8c2e8e64359b0c3a9774afb9e077cc2bd47c5f6f6322abe6a63afd8 36396 
inn2_2.7.1-1.debian.tar.xz
 792585cf2ff0a4b22c1a1f17e21f5585ffef5f98849d74ba77909d6db6a5a76a 7766 
inn2_2.7.1-1_amd64.buildinfo
Files:
 bf6f8807d4a067adcc97761bb4c5c052 1567 news optional inn2_2.7.1-1.dsc
 a7577b9dd97d2c20f8c0644e1e6095f0 1543116 news optional inn2_2.7.1.orig.tar.xz
 7c041e6db629e67077c3abb929a81aea 36396 news optional inn2_2.7.1-1.debian.tar.xz
 523dc60189a048ab4719317e2bb02dfa 7766 news optional 
inn2_2.7.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCZE/3HAAKCRDLPsM64d7X
gWyGAP9qIsyhfaEdtrVO8g6MA8lq23NGn6+qRuACPkGcXDvrtwD/cgBTiwGz2Yp9
KYi3fAxW7xEc5DkJCeJ/NzJWVB3Kpwc=
=OkAp
-END PGP SIGNATURE End Message ---

Bug#1035350: postfix: postinst script modifies configuration files despite local changes

[Einhard Leichtfuß]

On 01/05/2023 18:14, Scott Kitterman wrote:
> On Monday, May 1, 2023 11:06:07 AM EDT Einhard Leichtfuß wrote:
>> Package: postfix
>> Version: 3.5.18-0+deb11u1
>> Severity: serious
>>
>> Upon upgrade of postfix (due to `apt dist-upgrade`), the `master.cf`
>> [and `main.cf`] configuration files were modified by the postinst
>> script, despite existing local changes.
>>
>> If I understand correctly, this violates Debian Policy 10.7.3 [0]:
>> "local changes must be preserved during a package upgrade".  This is why
>> I chose Severity "serious".
>>
>> I would instead expect a handling similar to that of changed conffiles
>> (i.e., one is given an option to or is suggested to apply certain
>> modifications).
>>
>> In `master.cf`, the following lines were appended:
>>> proxymap  unix  -   -   n   -   -   proxymap
>>> verifyunix  -   -   y   -   1   verify
>>> relay unix  -   -   n   -   -   smtp -o
>>> smtp_fallback_relay= #   -o smtp_helo_timeout=5 -o
>>> smtp_connect_timeout=5
>>
>> See the `fix_master()` function in the postinst script.
>>
>> (sidenote: The first two entries are the same as in
>> `/usr/share/postfix/master.cf.dist`, the last one is different.)
>>
>> In `main.cf`, the following lines were appended:
>>> readme_directory = /usr/share/doc/postfix
>>> html_directory = /usr/share/doc/postfix/html
>>
>> If I understand the postinst script correctly, this modification of
>> `main.cf` should only have happened upon first installation, which this
>> was not.  I was unable to reproduce this.  So maybe this modification
>> was indeed done earlier.
>>
>> However, even upon initial installation (with pre-existing
>> configuration), this should, in my opinion, not happen.
>>
>> The changes were accompanied by the following message:
>>> Setting up postfix (3.5.18-0+deb11u1) ...
>>>
>>> In master.cf:
>>>   adding missing entry for proxymap service
>>>   adding missing entry for verify service
>>>   adding missing entry for relay service
>>>
>>> Postfix (main.cf) configuration was untouched.  If you need to make
>>> changes, edit /etc/postfix/main.cf (and others) as needed.  To view
>>> Postfix configuration values, see postconf(1).
>>>
>>> After modifying main.cf, be sure to run 'systemctl reload postfix'.
>>
>> The message that `main.cf` was untouched is displayed regardless of
>> whether the above noted modifications of `main.cf` are made.
>>
>>
>> I noticed that many actions in the postinst script are only run if
>> `[ "$mailer" != "No configuration" ]`.  I am unsure whether this case
>> would warrant the above mentioned modifications.  If so, maybe this
>> condition should be added to these modifications.
>>
>>
>> [0] https://www.debian.org/doc/debian-policy/ch-files.html#behavior
> 
> fix_master() was added in 2017 to upgrade pre-postfix 3.0 master.cf files to 
> support postfix 3.0 and hasn't been touched since then.
> 
> What version of Debian were you upgrading from?

That should be the previous minor version of Debian 11 (i.e., 11.6).
postfix was upgraded from version 3.5.17-0+deb11u1.

I did not notice this with earlier versions because this is the first
upgrade of postfix on this installation (it is quite new).

> Also, note that the message about is about main.cf not being modified.  These 
> changes are in master.cf, so I don't understand the concern with the message?

The second modification (readme_directory, html_directory) was to
`main.cf`.  While this modification should only happen for initial
installations (with pre-existing configuration), the message is
displayed even then.

Steps to reproduce (assuming postfix is not installed):

$ apt install postfix-doc
$ echo > /etc/postfix/main.cf
$ apt install postfix


Einhard Leichtfuß

Bug#1035350: postfix: postinst script modifies configuration files despite local changes

[Scott Kitterman]

On Monday, May 1, 2023 11:06:07 AM EDT Einhard Leichtfuß wrote:
> Package: postfix
> Version: 3.5.18-0+deb11u1
> Severity: serious
> 
> Upon upgrade of postfix (due to `apt dist-upgrade`), the `master.cf`
> [and `main.cf`] configuration files were modified by the postinst
> script, despite existing local changes.
> 
> If I understand correctly, this violates Debian Policy 10.7.3 [0]:
> "local changes must be preserved during a package upgrade".  This is why
> I chose Severity "serious".
> 
> I would instead expect a handling similar to that of changed conffiles
> (i.e., one is given an option to or is suggested to apply certain
> modifications).
> 
> In `master.cf`, the following lines were appended:
> > proxymap  unix  -   -   n   -   -   proxymap
> > verifyunix  -   -   y   -   1   verify
> > relay unix  -   -   n   -   -   smtp -o
> > smtp_fallback_relay= #   -o smtp_helo_timeout=5 -o
> > smtp_connect_timeout=5
> 
> See the `fix_master()` function in the postinst script.
> 
> (sidenote: The first two entries are the same as in
> `/usr/share/postfix/master.cf.dist`, the last one is different.)
> 
> In `main.cf`, the following lines were appended:
> > readme_directory = /usr/share/doc/postfix
> > html_directory = /usr/share/doc/postfix/html
> 
> If I understand the postinst script correctly, this modification of
> `main.cf` should only have happened upon first installation, which this
> was not.  I was unable to reproduce this.  So maybe this modification
> was indeed done earlier.
> 
> However, even upon initial installation (with pre-existing
> configuration), this should, in my opinion, not happen.
> 
> The changes were accompanied by the following message:
> > Setting up postfix (3.5.18-0+deb11u1) ...
> > 
> > In master.cf:
> >   adding missing entry for proxymap service
> >   adding missing entry for verify service
> >   adding missing entry for relay service
> > 
> > Postfix (main.cf) configuration was untouched.  If you need to make
> > changes, edit /etc/postfix/main.cf (and others) as needed.  To view
> > Postfix configuration values, see postconf(1).
> > 
> > After modifying main.cf, be sure to run 'systemctl reload postfix'.
> 
> The message that `main.cf` was untouched is displayed regardless of
> whether the above noted modifications of `main.cf` are made.
> 
> 
> I noticed that many actions in the postinst script are only run if
> `[ "$mailer" != "No configuration" ]`.  I am unsure whether this case
> would warrant the above mentioned modifications.  If so, maybe this
> condition should be added to these modifications.
> 
> 
> [0] https://www.debian.org/doc/debian-policy/ch-files.html#behavior

fix_master() was added in 2017 to upgrade pre-postfix 3.0 master.cf files to 
support postfix 3.0 and hasn't been touched since then.

What version of Debian were you upgrading from?

Also, note that the message about is about main.cf not being modified.  These 
changes are in master.cf, so I don't understand the concern with the message?

Scott K

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

Bug#1035350: postfix: postinst script modifies configuration files despite local changes

[Einhard Leichtfuß]

Package: postfix
Version: 3.5.18-0+deb11u1
Severity: serious

Upon upgrade of postfix (due to `apt dist-upgrade`), the `master.cf`
[and `main.cf`] configuration files were modified by the postinst
script, despite existing local changes.

If I understand correctly, this violates Debian Policy 10.7.3 [0]:
"local changes must be preserved during a package upgrade".  This is why
I chose Severity "serious".

I would instead expect a handling similar to that of changed conffiles
(i.e., one is given an option to or is suggested to apply certain
modifications).


In `master.cf`, the following lines were appended:
> proxymap  unix  -   -   n   -   -   proxymap
> verifyunix  -   -   y   -   1   verify
> relay unix  -   -   n   -   -   smtp -o 
> smtp_fallback_relay=
> #   -o smtp_helo_timeout=5 -o smtp_connect_timeout=5

See the `fix_master()` function in the postinst script.

(sidenote: The first two entries are the same as in
`/usr/share/postfix/master.cf.dist`, the last one is different.)


In `main.cf`, the following lines were appended:
> readme_directory = /usr/share/doc/postfix
> html_directory = /usr/share/doc/postfix/html

If I understand the postinst script correctly, this modification of
`main.cf` should only have happened upon first installation, which this
was not.  I was unable to reproduce this.  So maybe this modification
was indeed done earlier.

However, even upon initial installation (with pre-existing
configuration), this should, in my opinion, not happen.


The changes were accompanied by the following message:
> Setting up postfix (3.5.18-0+deb11u1) ...
> In master.cf:
>   adding missing entry for proxymap service
>   adding missing entry for verify service
>   adding missing entry for relay service
> 
> Postfix (main.cf) configuration was untouched.  If you need to make changes,
> edit /etc/postfix/main.cf (and others) as needed.  To view Postfix
> configuration values, see postconf(1).
> 
> After modifying main.cf, be sure to run 'systemctl reload postfix'.
The message that `main.cf` was untouched is displayed regardless of
whether the above noted modifications of `main.cf` are made.


I noticed that many actions in the postinst script are only run if
`[ "$mailer" != "No configuration" ]`.  I am unsure whether this case
would warrant the above mentioned modifications.  If so, maybe this
condition should be added to these modifications.


[0] https://www.debian.org/doc/debian-policy/ch-files.html#behavior



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

Kernel: Linux 5.10.0-22-cloud-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 postfix depends on:
ii  adduser3.118
ii  cpio   2.13+dfsg-4
ii  debconf [debconf-2.0]  1.5.77
ii  dpkg   1.20.12
ii  e2fsprogs  1.46.2-2
ii  libc6  2.31-13+deb11u6
ii  libdb5.3   5.3.28+dfsg1-0.8
ii  libicu67   67.1-7
ii  libnsl21.3.0-2
ii  libsasl2-2 2.1.27+dfsg-2.1+deb11u1
ii  libssl1.1  1.1.1n-0+deb11u4
ii  lsb-base   11.1.0
ii  netbase6.3
ii  ssl-cert   1.1.0+nmu1

Versions of packages postfix recommends:
ii  ca-certificates  20210119
ii  python3  3.9.2-3

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]8.1.2-0.20180807cvs-2
ii  dovecot-core [dovecot-common]  1:2.3.13+dfsg1-2+deb11u1
pn  postfix-cdb
ii  postfix-doc3.5.18-0+deb11u1
pn  postfix-ldap   
pn  postfix-lmdb   
pn  postfix-mysql  
pn  postfix-pcre   
ii  postfix-pgsql  3.5.18-0+deb11u1
pn  postfix-sqlite 
pn  procmail   
pn  resolvconf 
pn  ufw

-- debconf information:
  postfix/relay_restrictions_warning:
  postfix/bad_recipient_delimiter:
  postfix/destinations: $myhostname, myfancyhostname,
localhost.localdomain, , localhost
  postfix/newaliases: false
  postfix/not_configured:
  postfix/main_cf_conversion_warning: true
  postfix/procmail: false
  postfix/mailname: myfancyhostname
  postfix/sqlite_warning:
  postfix/mailbox_limit: 0
  postfix/protocols: all
  postfix/dynamicmaps_conversion_warning:
  postfix/tlsmgr_upgrade_warning:
  postfix/kernel_version_warning:
  postfix/root_address:
  postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
  postfix/lmtp_retired_warning: true
  postfix/retry_upgrade_warning:
  postfix/recipient_delim: +
  postfix/chattr: false
* postfix/main_mailer_type: No 

Bug#1033231: fixed in postgrey 1.37-2

[Tim Boneko]

Hello!
After a little testing i can confirm that postgrey is installed fine:
The user is created with uid=119 and gid=130, /etc/postgrey contains
the files whitelist_clients and whitelist_recipients and the daemon
seems to be running fine.
Thanks a lot!
Cheers,

tim

Tested version: 1.37-2 from unstable
Platform: amd64
Debian version: 12/testing
Recommended packages from testing



On Sun, 30 Apr 2023 23:18:59 + Debian FTP Masters
 wrote:
> Source: postgrey
> Source-Version: 1.37-2
> Done: Jordi Mallach 
> 
> We believe that the bug you reported is fixed in the latest version
of
> postgrey, which is due to be installed in the Debian FTP archive.
> 
> A summary of the changes between this version and the previous one
is
> attached.
> 
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to
1033...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Jordi Mallach  (supplier of updated postgrey
package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Mon, 01 May 2023 00:57:30 +0200
> Source: postgrey
> Architecture: source
> Version: 1.37-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Jordi Mallach 
> Changed-By: Jordi Mallach 
> Closes: 1031401 1033231
> Changes:
>  postgrey (1.37-2) unstable; urgency=medium
>  .
>    * Use %H in the service file to set the hostname in the rejection
message
>  (closes: #1031401).
>    * Add missing ucf machinery so the default config file and
whitelists get
>  installed correctly (closes: #1033231).
>    * Reinstate creation of postgrey user.
>    * Ensure /var/lib/postgrey exists and is owned by postgrey.
> Checksums-Sha1:
>  55f468de0bc7b115b24b782df971dc1d315977a0 1888 postgrey_1.37-2.dsc
>  5d48d6399d98c4ff93a5298c4129a61607332284 18584 postgrey_1.37-
2.debian.tar.xz
>  f4ee4febb21d2bc5c5a256c3232ba10a64096289 6169 postgrey_1.37-
2_amd64.buildinfo
> Checksums-Sha256:
>  87c3ac7f80fab0a0bf2710ec1f4bd21614ff508d68a8c5c0a61191bce19c1455
1888 postgrey_1.37-2.dsc
>  7920f5299346b1d29b20fb18779350264fa0de7275f18a3b9e6a956e0a8b1f6e
18584 postgrey_1.37-2.debian.tar.xz
>  0c91dc74591a19387c8e82276a8d3bf1f224caac87c8d6e07830cf551a3e75da
6169 postgrey_1.37-2_amd64.buildinfo
> Files:
>  d27b863757d844ed32d511bc7d5dc441 1888 mail optional postgrey_1.37-
2.dsc
>  b1d772f1519986eead7640c64a89bef0 18584 mail optional postgrey_1.37-
2.debian.tar.xz
>  5e72d9727b2d0a152ff8a905803e6b44 6169 mail optional postgrey_1.37-
2_amd64.buildinfo
> 
> -BEGIN PGP SIGNATURE-
> 

Bug#1035347: boxer-data: generates dependencies on no longer installable lightning

[Andreas Beckmann]

Followup-For: Bug #1035347
Control: notfixed -1 10.9.4
Control: fixed -1 10.9.6
Control: block 1000872 with -1

The thunderbird-l10n-si change from 10.9.6 needs to be backported to
bullseye as well.


Andreas

Processed: Re: boxer-data: generates dependencies on no longer installable lightning

[Debian Bug Tracking System]

Processing control commands:

> notfixed -1 10.9.4
Bug #1035347 [boxer-data] boxer-data: generates dependencies on no longer 
installable lightning
No longer marked as fixed in versions boxer-data/10.9.4.
> fixed -1 10.9.6
Bug #1035347 [boxer-data] boxer-data: generates dependencies on no longer 
installable lightning
Marked as fixed in versions boxer-data/10.9.6.
> block 1000872 with -1
Bug #1000872 {Done: Jonas Smedegaard } [parl-desktop-world] 
parl-desktop-world: depends on removed package thunderbird-l10n-si
1000872 was not blocked by any bugs.
1000872 was not blocking any bugs.
Added blocking bug(s) of 1000872: 1035347

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

Processed: user debian...@lists.debian.org, unarchiving 1000872, found 1000872 in 1.9.27, usertagging 1000872 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> unarchive 1000872
Bug #1000872 {Done: Jonas Smedegaard } [parl-desktop-world] 
parl-desktop-world depends on removed package.
Unarchived Bug 1000872
> found 1000872 1.9.27
Bug #1000872 {Done: Jonas Smedegaard } [parl-desktop-world] 
parl-desktop-world depends on removed package.
Marked as found in versions debian-parl/1.9.27.
> usertags 1000872 piuparts
There were no usertags set.
Usertags are now: piuparts.
> retitle 1000872 parl-desktop-world: depends on removed package 
> thunderbird-l10n-si
Bug #1000872 {Done: Jonas Smedegaard } [parl-desktop-world] 
parl-desktop-world depends on removed package.
Changed Bug title to 'parl-desktop-world: depends on removed package 
thunderbird-l10n-si' from 'parl-desktop-world depends on removed package.'.
> thanks
Stopping processing here.

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

Processed: boxer-data: generates dependencies on no longer installable lightning

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 10.9.4
Bug #1035347 [boxer-data] boxer-data: generates dependencies on no longer 
installable lightning
Marked as fixed in versions boxer-data/10.9.4.
> block 1000737 with -1
Bug #1000737 {Done: Jonas Smedegaard } [design-desktop] 
debian-design: Depends: lightning but it is not installable
1000737 was not blocked by any bugs.
1000737 was not blocking any bugs.
Added blocking bug(s) of 1000737: 1035347
> block 1035344 with -1
Bug #1035344 [parl-desktop] parl-desktop: depends on no longer installable 
lightning
1035344 was not blocked by any bugs.
1035344 was not blocking any bugs.
Added blocking bug(s) of 1035344: 1035347

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

Bug#1035347: boxer-data: generates dependencies on no longer installable lightning

[Andreas Beckmann]

Package: boxer-data
Version: 10.8.28
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 10.9.4
Control: block 1000737 with -1
Control: block 1035344 with -1

src:thunderbird has stopped building the lightning package as part of a
stable update, rendering parl-desktop and design-desktop uninstallable
in stable. In order to rebuild them with changed dependencies,
boxer-data needs to be updated in bullseye first.


Andreas

Bug#1035344: parl-desktop: depends on no longer installable lightning

[Andreas Beckmann]

Package: parl-desktop
Version: 1.9.27
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 1.9.29

parl-desktop/bullseye is no longer installable since thunderbird stopped
building the transitional lightning package in stable, too. (There is
only an uninstallable cruft lightning version left in bullseye-security.)

Please make parl-desktop installable in stable again by updating
boxer-data in stable and rebuilding src:debian-parl against that.


Andreas

Processed: parl-desktop: depends on no longer installable lightning

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.9.29
Bug #1035344 [parl-desktop] parl-desktop: depends on no longer installable 
lightning
Marked as fixed in versions debian-parl/1.9.29.

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

Processed: user debian...@lists.debian.org, unarchiving 1000737, found 1000737 in 3.0.22, usertagging 1000737

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> unarchive 1000737
Bug #1000737 {Done: Jonas Smedegaard } [design-desktop] 
debian-design: Depends: lightning but it is not installable
Unarchived Bug 1000737
> found 1000737 3.0.22
Bug #1000737 {Done: Jonas Smedegaard } [design-desktop] 
debian-design: Depends: lightning but it is not installable
Marked as found in versions debian-design/3.0.22.
> usertags 1000737 piuparts
There were no usertags set.
Usertags are now: piuparts.
> thanks
Stopping processing here.

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

Bug#1034310: [digikam] [Bug 466170] Digikam 7.9.0 (and 7.8.0) crashes on startup

[Rainer Dorsch]

Hi Steve,

many thanks for applying the patch. I reenabled the splash screen in digikamrc 
and it seems to crash at the same location again:

rd@h370:~$ apt-cache policy digikam
digikam:
  Installed: 4:7.9.0-2
  Candidate: 4:7.9.0-2
  Version table:
 *** 4:7.9.0-2 100
100 http://deb.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status
 4:7.9.0-1+b2 500
500 http://ftp-stud.hs-esslingen.de/debian bookworm/main amd64 
Packages
rd@h370:~$ digikam 
digikam.facedb: Cannot found faces engine model "shapepredictor.dat"
digikam.facedb: Faces recognition feature cannot be used!
digikam.facedb: Cannot found faces engine DNN model 
"openface_nn4.small2.v1.t7"
digikam.facedb: Faces recognition feature cannot be used!
kf.xmlgui: Unhandled container to remove :  Digikam::DigikamApp
ASSERT: "!isEmpty()" in file /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h, 
line 363
21 -- exe=/usr/bin/digikam
13 -- platform=xcb
11 -- display=:0
16 -- appname=digikam
17 -- apppath=/usr/bin
9 -- signal=6
12 -- pid=1073797
17 -- appversion=7.9.0
20 -- programname=digiKam
31 -- bugaddress=sub...@bugs.kde.org
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = digikam path = /usr/bin pid = 1073797
KCrash: Arguments: /usr/bin/digikam 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi

[2]+  Stopped digikam
rd@h370:~$

I will create a trace and append it to the upstream bugreport:

https://bugs.kde.org/show_bug.cgi?id=466170

Thanks again
Rainer

Am Montag, 1. Mai 2023, 08:21:12 CEST schrieb Steve Robbins:
> I’ve just uploaded new version with upstream patch for the splash screen. 
> Would love to know I how it works on your system.
> 
> Sent from my iPhone
> 
> > On Apr 26, 2023, at 8:24 AM, Steve Robbins  wrote:
> > 
> > I understood that upstream fixed a splash screen bug from your traces.  I
> > do plan to look into applying that patch.
> > 
> > But I thought that even after disabling the splash screen you were seeing
> > a second crash?  That is what I’m trying to figure out.
> > 
> > Sent from my iPhone
> > 
> >>> On Apr 26, 2023, at 1:24 AM, Rainer Dorsch  wrote:
> >> 
> >> Hi Steve,
> >> 
> >> Am Mittwoch, 26. April 2023, 05:49:03 CEST schrieben Sie:
> >> > On Tuesday, April 25, 2023 12:50:39 P.M. CDT Rainer Dorsch wrote:
> >> > > Am Dienstag, 25. April 2023, 03:51:44 CEST schrieben Sie:
> >> > > > I'd be interested to know if the issue persists on your system
> >> > > > after
> >> > > > upgrading.
> >> > > 
> >> > > Yes, it repros always.
> >> > 
> >> > OK.
> >> > 
> >> > > -- System Information:
> >> > > Debian Release: 12.0
> >> > > 
> >> > >   APT prefers testing-security
> >> > >   APT policy: (500, 'testing-security'), (500, 'testing-debug'),
> >> > >   (105,
> >> > > 
> >> > > 'testing')
> >> > > Architecture: amd64 (x86_64)
> >> > > Foreign Architectures: i386
> >> > > 
> >> > > Kernel: Linux 6.1.0-7-amd64 (SMP w/6 CPU threads; PREEMPT)
> >> > > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
> >> > > LANGUAGE=de:en_US
> >> > 
> >> > I'm still not able to reproduce the issue.  Today I was trying with the
> >> > same locale as you (de_DE.UTF-8).   I have seen issues in the past
> >> > with certain locales -- typically in software that isn't careful
> >> > enough and gets into trouble when a locale switches the period and
> >> > comma in number formats.>> 
> >> Be aware that upstream also was unable to repro the issue and finally
> >> they managed to understand and fix the problem by the traces I was able
> >> to generated.>> 
> >> > Even though I wasn't able to reproduce the problem here, it would be
> >> 
> >> > interesting if you can try with locale set to en_US for example:
> >> There is no change if I unset LANG:
> >> 
> >> rd@h370:~/tmp.nobackup$ unset LANG
> >> rd@h370:~/tmp.nobackup$ digikam
> >> digikam.facedb: Cannot found faces engine model "shapepredictor.dat"
> >> digikam.facedb: Faces recognition feature cannot be used!
> >> digikam.facedb: Cannot found faces engine DNN model
> >> "openface_nn4.small2.v1.t7" digikam.facedb: Faces recognition feature
> >> cannot be used!
> >> kf.xmlgui: Unhandled container to remove :  Digikam::DigikamApp
> >> ASSERT: "!isEmpty()" in file
> >> /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h, line 363 21 --
> >> exe=/usr/bin/digikam
> >> 13 -- platform=xcb
> >> 11 -- display=:0
> >> 16 -- appname=digikam
> >> 17 -- apppath=/usr/bin
> >> 9 -- signal=6
> >> 11 -- pid=459194
> >> 17 -- appversion=7.9.0
> >> 20 -- programname=digiKam
> >> 31 -- bugaddress=sub...@bugs.kde.org
> >> KCrash: crashing... crashRecursionCounter = 2
> >> KCrash: Application Name = digikam path = /usr/bin pid = 459194
> >> KCrash: Arguments: /usr/bin/digikam
> >> KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
> >> 
> >> [1]+  Stopped digikam
> >> rd@h370:~/tmp.nobackup$
> >> 
> >> > I have no idea where else to look.  Given that no-one else has reported
> 

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

[Tobias Frost]

Control: tags -1 unreproducible
Control: severity -1 important

Hi Helmut, 

On Thu, 27 Apr 2023 14:58:58 +0200 Helmut Grohne  wrote:
> 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
 
I cannot reproduce this.  liboce-foundation-dev liboce-modeling-dev is 
deinstalled here when
trying to installing libocct-data-exchange-dev. 
libocct-data-exchange-dev depends on libocct-foundation-dev, which conflicts 
liboce-foundation-dev.
liboce-modeling-dev is depending on liboce-foundation-dev, so the conflict is 
inherited.

Any hints what I am missing?


This is what I have done:
On a bullseye pbuilder chroot:

1) Installing liboce-modeling-dev

# apt install liboce-modeling-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  liboce-foundation-dev liboce-foundation11 liboce-modeling11
The following NEW packages will be installed:
  liboce-foundation-dev liboce-foundation11 liboce-modeling-dev 
liboce-modeling11
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.6 MB of archives.
After this operation, 77.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] 

(...)

2) changing to source.list to bookworm

3) apt update

4) # apt install libocct-data-exchange-dev

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  liboce-foundation11 liboce-modeling11
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  binutils binutils-common binutils-x86-64-linux-gnu fontconfig-config 
fonts-dejavu-core gcc-12-base libbinutils libbrotli-dev libbrotli1
  libbsd0 libc-bin libc-dev-bin libc6 libc6-dev libctf-nobfd0 libctf0 
libdeflate0 libdrm-amdgpu1 libdrm-common libdrm-intel1
  libdrm-nouveau2 libdrm-radeon1 libdrm2 libedit2 libegl-dev libegl-mesa0 
libegl1 libelf1 libffi8 libfontconfig1 libfreeimage-dev
  libfreeimage3 libfreetype-dev libfreetype6 libfreetype6-dev libgbm1 libgl-dev 
libgl1 libgl1-mesa-dev libgl1-mesa-dri libglapi-mesa
  libgles-dev libgles1 libgles2 libglu1-mesa libglu1-mesa-dev libglvnd-core-dev 
libglvnd-dev libglvnd0 libglx-dev libglx-mesa0 libglx0
  libgprofng0 libhwloc15 libice-dev libice6 libimath-3-1-29 libjansson4 
libjbig0 libjpeg62-turbo libjxr0 liblcms2-2 liblerc4 libllvm15
  libmd0 libocct-data-exchange-7.6 libocct-draw-7.6 libocct-foundation-7.6 
libocct-foundation-dev libocct-modeling-algorithms-7.6
  libocct-modeling-algorithms-dev libocct-modeling-data-7.6 
libocct-modeling-data-dev libocct-ocaf-7.6 libocct-ocaf-dev
  libocct-visualization-7.6 libocct-visualization-dev libopenexr-3-1-30 
libopengl-dev libopengl0 libopenjp2-7 libpciaccess0 libpng-dev
  libpng16-16 libpthread-stubs0-dev libraw20 libsensors-config libsensors5 
libsm-dev libsm6 libstdc++6 libtbb12 libtbbbind-2-5
  libtbbmalloc2 libtcl8.6 libtiff6 libtk8.6 libwayland-client0 
libwayland-server0 libwebp7 libwebpmux3 libx11-6 libx11-data libx11-dev
  libx11-xcb1 libxau-dev libxau6 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 
libxcb-present0 libxcb-randr0 libxcb-shm0 libxcb-sync1
  libxcb-xfixes0 libxcb1 libxcb1-dev libxdmcp-dev libxdmcp6 libxext-dev 
libxext6 libxfixes3 libxft2 libxmu-dev libxmu-headers libxmu6
  libxrender1 libxshmfence1 libxss1 libxt-dev libxt6 libxxf86vm1 libz3-4 
libzstd1 occt-misc rpcsvc-proto x11-common x11proto-dev
  xorg-sgml-doctools xtrans-dev zlib1g zlib1g-dev
Suggested packages:
  binutils-doc glibc-doc libc-l10n locales libnss-nis libnss-nisplus 
manpages-dev freetype2-doc libhwloc-contrib-plugins libice-doc
  liblcms2-utils pciutils lm-sensors libsm-doc tcl8.6 tk8.6 libx11-doc 
libxcb-doc libxext-doc libxt-doc
Recommended packages:
  manpages manpages-dev libc-devtools libhwloc-plugins libpng-tools
The 

Processed: Re: libocct-data-exchange-dev: missing Breaks+Replaces for liboce-modeling-dev when upgrading from bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible
Bug #1035009 [libocct-data-exchange-dev] libocct-data-exchange-dev: missing 
Breaks+Replaces for liboce-modeling-dev when upgrading from bullseye
Added tag(s) unreproducible.
> severity -1 important
Bug #1035009 [libocct-data-exchange-dev] libocct-data-exchange-dev: missing 
Breaks+Replaces for liboce-modeling-dev when upgrading from bullseye
Severity set to 'important' from 'serious'

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 1016903 patch
Bug #1016903 [g++-12] tree-vectorize: Wrong code at O2 level 
(-fno-tree-vectorize is working)
Added tag(s) patch.
>
End of message, stopping processing here.

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

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

[Tobias Frost]

On Thu, 27 Apr 2023 14:58:58 +0200 Helmut Grohne  wrote:
> 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
> 
> 

src:oce is a different edition of src:opencascade, so I guess this needs to be 
a Conflicts:

-- 
tobi

Bug#1034310: [digikam] [Bug 466170] Digikam 7.9.0 (and 7.8.0) crashes on startup

[Steve Robbins]

I’ve just uploaded new version with upstream patch for the splash screen.  
Would love to know I how it works on your system. 

Sent from my iPhone

> On Apr 26, 2023, at 8:24 AM, Steve Robbins  wrote:
> 
> I understood that upstream fixed a splash screen bug from your traces.  I do 
> plan to look into applying that patch.  
> 
> But I thought that even after disabling the splash screen you were seeing a 
> second crash?  That is what I’m trying to figure out. 
> 
> Sent from my iPhone
> 
>>> On Apr 26, 2023, at 1:24 AM, Rainer Dorsch  wrote:
>>> 
>> 
>> Hi Steve,
>> 
>> Am Mittwoch, 26. April 2023, 05:49:03 CEST schrieben Sie:
>> > On Tuesday, April 25, 2023 12:50:39 P.M. CDT Rainer Dorsch wrote:
>> > > Am Dienstag, 25. April 2023, 03:51:44 CEST schrieben Sie:
>> > > > I'd be interested to know if the issue persists on your system after
>> > > > upgrading.
>> > >
>> > > Yes, it repros always.
>> >
>> > OK.
>> >
>> > > -- System Information:
>> > > Debian Release: 12.0
>> > >
>> > >   APT prefers testing-security
>> > >   APT policy: (500, 'testing-security'), (500, 'testing-debug'), (105,
>> > >
>> > > 'testing')
>> > > Architecture: amd64 (x86_64)
>> > > Foreign Architectures: i386
>> > >
>> > > Kernel: Linux 6.1.0-7-amd64 (SMP w/6 CPU threads; PREEMPT)
>> > > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
>> > > LANGUAGE=de:en_US
>> >
>> > I'm still not able to reproduce the issue.  Today I was trying with the 
>> > same
>> > locale as you (de_DE.UTF-8).   I have seen issues in the past with certain
>> > locales -- typically in software that isn't careful enough and gets into
>> > trouble when a locale switches the period and comma in number formats.
>> 
>> Be aware that upstream also was unable to repro the issue and finally they 
>> managed to understand and fix the problem by the traces I was able to 
>> generated.
>> 
>> > Even though I wasn't able to reproduce the problem here, it would be
>> > interesting if you can try with locale set to en_US for example:
>> 
>> There is no change if I unset LANG:
>> 
>> rd@h370:~/tmp.nobackup$ unset LANG
>> rd@h370:~/tmp.nobackup$ digikam
>> digikam.facedb: Cannot found faces engine model "shapepredictor.dat"
>> digikam.facedb: Faces recognition feature cannot be used!
>> digikam.facedb: Cannot found faces engine DNN model 
>> "openface_nn4.small2.v1.t7"
>> digikam.facedb: Faces recognition feature cannot be used!
>> kf.xmlgui: Unhandled container to remove :  Digikam::DigikamApp
>> ASSERT: "!isEmpty()" in file 
>> /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h, line 363
>> 21 -- exe=/usr/bin/digikam
>> 13 -- platform=xcb
>> 11 -- display=:0
>> 16 -- appname=digikam
>> 17 -- apppath=/usr/bin
>> 9 -- signal=6
>> 11 -- pid=459194
>> 17 -- appversion=7.9.0
>> 20 -- programname=digiKam
>> 31 -- bugaddress=sub...@bugs.kde.org
>> KCrash: crashing... crashRecursionCounter = 2
>> KCrash: Application Name = digikam path = /usr/bin pid = 459194
>> KCrash: Arguments: /usr/bin/digikam
>> KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
>> 
>> [1]+  Stopped digikam
>> rd@h370:~/tmp.nobackup$
>> 
>> > I have no idea where else to look.  Given that no-one else has reported
>> > this, I'm leaning towards downgrading the severity to keep digikam in the
>> > upcoming release.
>> 
>> That is certainly and option. For me as a user it would be helpful if you 
>> would highlight in the changelog that I get during the upgrade the 
>> information to disable the splash screen if they run into this issue.
>> 
>> Alternatively you could apply the bugfix
>> 
>> https://invent.kde.org/graphics/digikam/-/commit/28977ed2aac8a3575b979725e3141dd94b104833
>> 
>> to the Debian package. I can test if it fixes the problem for me.
>> 
>> Thanks
>> Rainer
>> 
>> --
>> Rainer Dorsch
>> http://bokomoko.de/