Bug#1035654: non-essential adduser poses problems to purging packages

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Helmut Grohne (2023-05-07 13:52:50)
> 
> I contend that:
> 
>  1. This change is in unstable since 2022-10-31, i.e. more than half a
> year.
>  2. While having adduser drop from the essential+apt set is caused by
> apt dropping it, this was an implementation detail and any package
> using adduser without a dependency was (invisibly) buggy before.
> 
> So I don't quite buy the reasoning of "too late" or it being apt's
> fault.
> 
> On the flip side, I think it would technically have been the
> responsibility of the proponents of dropping adduser to do the testing.
> The proponents have been Josch and my self and we ultimately failed to do so.
> Thanks to Andreas for doing it for us.

this is true. I must admit that I haven't thought of maintainer scripts using
adduser during purge and failing because they expect adduser to always be
installed. Even though it is too late, I ran this script on all 11864 binary
packages in unstable amd64 that have either a postrm or prerm script:

#!/bin/sh
set -eu
ret=0
PKG_TO_TEST="$1" mmdebstrap --logfile="$1.log" --variant=essential \
--customize-hook='APT_CONFIG=$MMDEBSTRAP_APT_CONFIG apt-get 
-oDPkg::Chroot-Directory="$1" --yes install --no-install-recommends 
"$PKG_TO_TEST"' \
--customize-hook='APT_CONFIG=$MMDEBSTRAP_APT_CONFIG apt-get 
-oDPkg::Chroot-Directory="$1" --yes remove adduser' \
--customize-hook='printf "#!/bin/sh\nset -eu\necho \"I: 
adduser-dummy: attempting to run \$0\" >&2\nexit 1\n" > 
"$1/usr/sbin/adduser-dummy"' \
--customize-hook='chmod +x "$1/usr/sbin/adduser-dummy"' \
--customize-hook='ln -s adduser-dummy "$1/usr/sbin/adduser"' \
--customize-hook='ln -s adduser-dummy "$1/usr/sbin/deluser"' \
--customize-hook='ln -s adduser-dummy "$1/usr/sbin/addgroup"' \
--customize-hook='ln -s adduser-dummy "$1/usr/sbin/delgroup"' \
--customize-hook='APT_CONFIG=$MMDEBSTRAP_APT_CONFIG apt-get 
-oDPkg::Chroot-Directory="$1" --yes remove --purge "$PKG_TO_TEST"' \
unstable /dev/null http://127.0.0.1:3142/debian || ret=$?
if [ "$ret" -eq 0 ] && ! grep --silent "^I: adduser-dummy: attempting to 
run " "$1.log"; then
rm "$1.log"
fi

I did not limit the investigation to the packages with strings like deluser and
delgroup in their maintainer scripts to make sure to also catch packages that
indirectly call adduser tools through another script.

Out of the tested 11864 packages, 133 called adduser tools at one point or the
other but purging still succeeds (for example because of a || true). 210 of the
tested 11864 packages fail this script. Out of the 210 failures, 17 are
Essential:yes packages and thus failed. Out of the 193 remaining failures, 113
fail to install in the first place. Out of the 80 remaining failures, 32 fail
because they try calling adduser tools which are not installed and thus fail. I
skimmed through the 48 other purging failures and they seem to be nearly all
related to gtk and gsettings. Of the remaining 32 adduser related purging
problems, 18 packages check if deluser/delgroup exist before calling it and
then fail because I installed the dummy. The remaining 14 failures belong to
the following 9 source packages:

amavisd-new #1035841
debian-edu-fai  #1035292
desktop-autoloader  #1035291
kismet  #1035290
matrix-sydent   #1035844
tcpcryptd   #1035845
webdis  #1035435
x2gobroker  #1035847
x2gothinclient  #1034755

Out of these 9 remaining source packages, 5 had bugs already filed by Andreas
Beckmann. I filed bugs with patches for the remaining 4 packages and offered
to NMU if necessary.

> > With such a change I would have expected upgrade/piuparts tests from
> > bullseye to bookworm that tried to remove adduser a various stages and
> > check for the fallout. Given that Andreas is only doing them now, that's
> > too late for changes to the pseudo-essential set.

Given that only 9 source packages in unstable fail to purge because they expect
adduser to be present, I have another proposal. I think making adduser
Essential:yes (even if temporary) or making it a dependency of an Essential:yes
has the downside, that now package maintainers have official reason to rely on
its functionality and include that into their maintainer scripts. Finding these
new bugs becomes a bit more tricky because to test for this, an Essential:yes
package has to be removed. Same goes for making it pseudo-essential via apt
because removing adduser to test regressions would remove apt.

According to [popcon], adduser is installed on 100% of the systems providing
popcon data. This makes sense because probably near 100% of the systems
submitting popcon data either has apt installed (which used to pull in adduser)
or was installed via d-i (which pulls in adduser because it is
Priority:important).

I would thus argue that what we have to guard against 

Bug#1035847: x2gobroker-* packages fail to purge without adduser

[josch]

Package: x2gobroker
Version: 0.0.4.3-2.1
Severity: serious
User: jo...@debian.org
Usertags: adduserpurge
Control: tag -1 + patch
X-Debbugs-CC: jo...@debian.org

Hi,

the packages passwd and adduser are not part of the Essential:yes set.
According to policy §7.2 maintainer scripts cannot assume them being installed
when purging a package.  If one tries to remove this package without adduser
(which depends on passwd) installed, one gets:

--%<-
==> x2gobroker-agent.log <==
Purging configuration files for x2gobroker-agent (0.0.4.3-2.1) ...
/var/lib/dpkg/info/x2gobroker-agent.postrm: 35: deluser: not found
dpkg: error processing package x2gobroker-agent (--purge):
 installed x2gobroker-agent package post-removal script subprocess returned 
error exit status 127
Errors were encountered while processing:
 x2gobroker-agent
==> x2gobroker-authservice.log <==
Purging configuration files for x2gobroker-authservice (0.0.4.3-2.1) ...
/var/lib/dpkg/info/x2gobroker-authservice.postrm: 31: deluser: not found
dpkg: error processing package x2gobroker-authservice (--purge):
 installed x2gobroker-authservice package post-removal script subprocess 
returned error exit status 127
Errors were encountered while processing:
 x2gobroker-authservice
==> x2gobroker-daemon.log <==
Purging configuration files for x2gobroker-daemon (0.0.4.3-2.1) ...
/var/lib/dpkg/info/x2gobroker-daemon.postrm: 31: deluser: not found
dpkg: error processing package x2gobroker-daemon (--purge):
 installed x2gobroker-daemon package post-removal script subprocess returned 
error exit status 127
Errors were encountered while processing:
 x2gobroker-daemon
==> x2gobroker-loadchecker.log <==
Purging configuration files for x2gobroker-loadchecker (0.0.4.3-2.1) ...
/var/lib/dpkg/info/x2gobroker-loadchecker.postrm: 31: deluser: not found
dpkg: error processing package x2gobroker-loadchecker (--purge):
 installed x2gobroker-loadchecker package post-removal script subprocess 
returned error exit status 127
Errors were encountered while processing:
 x2gobroker-loadchecker
==> x2gobroker-ssh.log <==
Purging configuration files for x2gobroker-ssh (0.0.4.3-2.1) ...
/var/lib/dpkg/info/x2gobroker-ssh.postrm: 30: deluser: not found
dpkg: error processing package x2gobroker-ssh (--purge):
 installed x2gobroker-ssh package post-removal script subprocess returned error 
exit status 127
Errors were encountered while processing:
 x2gobroker-ssh
==> x2gobroker-wsgi.log <==
Purging configuration files for x2gobroker-wsgi (0.0.4.3-2.1) ...
/var/lib/dpkg/info/x2gobroker-wsgi.postrm: 47: deluser: not found
dpkg: error processing package x2gobroker-wsgi (--purge):
 installed x2gobroker-wsgi package post-removal script subprocess returned 
error exit status 127
Errors were encountered while processing:
 x2gobroker-wsgi
-->%-

There is ongoing discussion how to handle system users on package
removal, see https://bugs.debian.org/621833

For a discussion about use of adduser during purge, see #1035654.

To work around this problem, at least 125 source packages [codesearch] simply
ignore failures of calling the passwd or adduser tools during purge. The
following patch should fix this package by doing the same:

--%<-
diff -Nru x2gobroker-0.0.4.3/debian/x2gobroker-agent.postrm 
x2gobroker-0.0.4.3/debian/x2gobroker-agent.postrm
--- x2gobroker-0.0.4.3/debian/x2gobroker-agent.postrm   2019-03-31 
16:49:49.0 +0200
+++ x2gobroker-0.0.4.3/debian/x2gobroker-agent.postrm   2023-05-10 
08:01:29.0 +0200
@@ -32,9 +32,9 @@
 
if [ ! -d /usr/share/doc/x2gobroker-daemon ] && [ ! -d 
/usr/share/doc/x2gobroker-authservice ] && [ ! -d 
/usr/share/doc/x2gobroker-wsgi ] && [ ! -d 
/usr/share/doc/x2gobroker-loadchecker ]; then
# remove user/group x2gobroker from system (if not in 
use by x2gobroker-daemon, x2gobroker-authservice, x2gobroker-wsgi, 
x2gobroker-loadchecker)
-   getent passwd x2gobroker 1>/dev/null && deluser 
x2gobroker
-   getent group x2gobroker 1>/dev/null && delgroup 
x2gobroker
-   getent group x2gobroker 1>/dev/null && delgroup 
x2gobroker
+   getent passwd x2gobroker 1>/dev/null && deluser 
x2gobroker || true
+   getent group x2gobroker 1>/dev/null && delgroup 
x2gobroker || true
+   getent group x2gobroker 1>/dev/null && delgroup 
x2gobroker || true
rm -Rf /var/lib/x2gobroker
fi
 
@@ -52,4 +52,4 @@
 
 #DEBHELPER#
 
-exit 0
\ No newline at end of file
+exit 0
diff -Nru x2gobroker-0.0.4.3/debian/x2gobroker-authservice.postrm 
x2gobroker-0.0.4.3/debian/x2gobroker-authservice.postrm
--- x2gobroker-0.0.4.3/debian/x2gobroker-authservice.postrm 2019-03-31 
16:49:49

Processed: x2gobroker-* packages fail to purge without adduser

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #1035847 [x2gobroker] x2gobroker-* packages fail to purge without adduser
Added tag(s) patch.

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

Processed: tcpcryptd fails to purge without adduser

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #1035845 [tcpcryptd] tcpcryptd fails to purge without adduser
Added tag(s) patch.

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

Bug#1035845: tcpcryptd fails to purge without adduser

[josch]

Package: tcpcryptd
Version: 0.5-1+b3
Severity: serious
User: jo...@debian.org
Usertags: adduserpurge
Control: tag -1 + patch
X-Debbugs-CC: jo...@debian.org

Hi,

the packages passwd and adduser are not part of the Essential:yes set.
According to policy §7.2 maintainer scripts cannot assume them being installed
when purging a package.  If one tries to remove this package without adduser
(which depends on passwd) installed, one gets:

--%<-
Purging configuration files for tcpcryptd (0.5-1+b3) ...
/var/lib/dpkg/info/tcpcryptd.postrm: 9: deluser: not found
dpkg: error processing package tcpcryptd (--purge):
 installed tcpcryptd package post-removal script subprocess returned error exit 
status 127
Errors were encountered while processing:
 tcpcryptd
-->%-

There is ongoing discussion how to handle system users on package
removal, see https://bugs.debian.org/621833

For a discussion about use of adduser during purge, see #1035654.

To work around this problem, at least 125 source packages [codesearch] simply
ignore failures of calling the passwd or adduser tools during purge. The
following patch should fix this package by doing the same:

--%<-
diff -Nru tcpcrypt-0.5/debian/tcpcryptd.postrm 
tcpcrypt-0.5/debian/tcpcryptd.postrm
--- tcpcrypt-0.5/debian/tcpcryptd.postrm2016-04-01 23:45:55.0 
+0200
+++ tcpcrypt-0.5/debian/tcpcryptd.postrm2023-05-10 07:54:45.0 
+0200
@@ -6,7 +6,7 @@
 purge)
# add a debian-tcpcryptd user if one does not already exist
if getent passwd "$TCPCRYPT_USER" >/dev/null ; then
-deluser "$TCPCRYPT_USER"
+deluser "$TCPCRYPT_USER" || true
fi
 ;;
 esac
-->%-

If you prefer I can fix this via an NMU.

Thanks!

cheers, josch

[codesearch] 
https://codesearch.debian.net/search?q=del%28user%7Cgroup%29.*%5C%7C%5C%7C+true+path%3Adebian%2F.*%5C.%28pre%7Cpost%29rm%24&literal=0

Processed: matrix-sydent fails to purge without adduser

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #1035844 [matrix-sydent] matrix-sydent fails to purge without adduser
Added tag(s) patch.

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

Bug#1035844: matrix-sydent fails to purge without adduser

[josch]

Package: matrix-sydent
Version: 2.5.1-1.1
Severity: serious
User: jo...@debian.org
Usertags: adduserpurge
Control: tag -1 + patch

Hi,

the packages passwd and adduser are not part of the Essential:yes set.
According to policy §7.2 maintainer scripts cannot assume them being installed
when purging a package.  If one tries to remove this package without adduser
(which depends on passwd) installed, one gets:

--%<-
Purging configuration files for matrix-sydent (2.5.1-1.1) ...
/var/lib/dpkg/info/matrix-sydent.postrm: 28: deluser: not found
dpkg: error processing package matrix-sydent (--purge):
 installed matrix-sydent package post-removal script subprocess returned error 
exit status 127
Errors were encountered while processing:
 matrix-sydent
-->%-

There is ongoing discussion how to handle system users on package
removal, see https://bugs.debian.org/621833

For a discussion about use of adduser during purge, see #1035654.

To work around this problem, at least 125 source packages [codesearch] simply
ignore failures of calling the passwd or adduser tools during purge. The
following patch should fix this package by doing the same:

--%<-
diff -Nru matrix-sydent-2.5.1/debian/postrm matrix-sydent-2.5.1/debian/postrm
--- matrix-sydent-2.5.1/debian/postrm   2021-06-01 21:17:05.0 +0200
+++ matrix-sydent-2.5.1/debian/postrm   2023-05-10 07:46:13.0 +0200
@@ -25,7 +25,7 @@
dpkg-statoverride --force-all --quiet --remove "${DIR}"
done
 
-   getent passwd "${USER}" >/dev/null && deluser "${USER}"
+   getent passwd "${USER}" >/dev/null && deluser "${USER}" || true
 
rm -f /var/lib/${NAME}/*
if [ -d /var/lib/${NAME} ]; then
-->%-

If you prefer I can fix this via an NMU.

Thanks!

cheers, josch

[codesearch] 
https://codesearch.debian.net/search?q=del%28user%7Cgroup%29.*%5C%7C%5C%7C+true+path%3Adebian%2F.*%5C.%28pre%7Cpost%29rm%24&literal=0

Bug#1035839: marked as done (jed-common: Fails to upgrade: new jed-common package pre-installation script subprocess returned error exit status 1)

[Debian Bug Tracking System]

Your message dated Wed, 10 May 2023 05:03:48 +
with message-id 
and subject line Bug#1035839: fixed in jed 1:0.99.20~pre.178+dfsg-4
has caused the Debian Bug report #1035839,
regarding jed-common: Fails to upgrade:  new jed-common package 
pre-installation script subprocess returned error exit status 1
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.)


-- 
1035839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jed-common
Version: 1:0.99.20~pre.178+dfsg-3
Severity: serious

Hi,

I'm sorry to say, but it now fails elsewhere to upgrade from
1:0.99.20~pre.178+dfsg-1 to 1:0.99.20~pre.178+dfsg-3:

Preparing to unpack .../01-jed_1%3a0.99.20~pre.178+dfsg-3_amd64.deb ...
Unpacking jed (1:0.99.20~pre.178+dfsg-3) over (1:0.99.20~pre.178+dfsg-1) ...
Preparing to unpack .../02-jed-common_1%3a0.99.20~pre.178+dfsg-3_all.deb ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-UN0WZQ/02-jed-common_1%3a0.99.20~pre.178+dfsg-3_all.deb 
(--unpack):
 new jed-common package pre-installation script subprocess returned error exit 
status 1
[…]
Errors were encountered while processing:
 /tmp/apt-dpkg-install-UN0WZQ/02-jed-common_1%3a0.99.20~pre.178+dfsg-3_all.deb
[…]
dpkg: dependency problems prevent configuration of jed:
 jed depends on jed-common (= 1:0.99.20~pre.178+dfsg-3); however:
  Version of jed-common on system is 1:0.99.20~pre.178+dfsg-1.

dpkg: error processing package jed (--configure):
 dependency problems - leaving unconfigured

I think that cause is this line in combination with "set -e"

  test -d $txtdir && rm -rf $txtdir

If the directory does not exist, it returns false because the test
failed. And due to the (totally legit) "set -e" it aborts there with
exit code not equal zero.

You likely need to replace it with a full if clause:

  if [ -d $txtdir ] ; then rm -rf $txtdir ; fi

Such code will not have this side effect.

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'testing-security'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 
'experimental-debug'), (1, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages jed-common depends on:
pn  slsh  

jed-common recommends no packages.

Versions of packages jed-common suggests:
ii  emacs-gtk [info-browser]  1:28.2+1-14
ii  info [info-browser]   6.8-6+b1
iu  jed [info-browser]1:0.99.20~pre.178+dfsg-3
ii  konqueror [info-browser]  4:22.12.3-1
ii  pinfo [info-browser]  0.6.13-1.3

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/doc/jed-common/changelog.Debian.gz (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/abbrev.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/color.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/compile.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/dfa.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/edt.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/emacs.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/filelock.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/fold.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/hooks.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/ide-mode.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/jed_faq.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/linux-keys.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/menus.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/mouse.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/pc-keys.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/program.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/recentx.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/

Processed: tagging 1035841

[Debian Bug Tracking System]

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

> tags 1035841 + patch
Bug #1035841 [amavisd-new] amavisd-new fails to purge without adduser - 
userdel: not found
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1035841: amavisd-new fails to purge without adduser - userdel: not found

[josch]

Package: amavisd-new
Version: 1:2.13.0-2
Severity: serious
User: jo...@debian.org
Usertags: adduserpurge

Hi,

the packages passwd and adduser are not part of the Essential:yes set.
According to policy §7.2 maintainer scripts cannot assume them being installed
when purging a package.  If one tries to remove this package without adduser
(which depends on passwd) installed, one gets:

--%<-
Purging configuration files for amavisd-new (1:2.13.0-2) ...
/var/lib/dpkg/info/amavisd-new.postrm: 36: userdel: not found
dpkg: error processing package amavisd-new (--purge):
 installed amavisd-new package post-removal script subprocess returned error 
exit status 127
Errors were encountered while processing:
 amavisd-new
-->%-

There is ongoing discussion how to handle system users on package
removal, see https://bugs.debian.org/621833

For a discussion about use of adduser during purge, see #1035654.

To work around this problem, at least 125 source packages [codesearch] simply
ignore failures of calling the passwd or adduser tools during purge. The
following patch should fix this package by doing the same:

--%<-
diff -Nru amavisd-new-2.13.0/debian/amavisd-new.postrm 
amavisd-new-2.13.0/debian/amavisd-new.postrm
--- amavisd-new-2.13.0/debian/amavisd-new.postrm2023-02-23 
05:59:36.0 +0100
+++ amavisd-new-2.13.0/debian/amavisd-new.postrm2023-05-10 
06:33:15.0 +0200
@@ -33,7 +33,7 @@
dpkg-statoverride --remove $i || true
done
 
-userdel amavis
+userdel amavis || true
 
echo "Removing amavis files and directories..."
[ -d /var/lib/amavis ] && rm -fr /var/lib/amavis
-->%-

If you prefer I can fix this via an NMU.

Thanks!

cheers, josch

[codesearch] 
https://codesearch.debian.net/search?q=del%28user%7Cgroup%29.*%5C%7C%5C%7C+true+path%3Adebian%2F.*%5C.%28pre%7Cpost%29rm%24&literal=0

Bug#1035839: jed-common: Fails to upgrade: new jed-common package pre-installation script subprocess returned error exit status 1

[Axel Beckert]

Package: jed-common
Version: 1:0.99.20~pre.178+dfsg-3
Severity: serious

Hi,

I'm sorry to say, but it now fails elsewhere to upgrade from
1:0.99.20~pre.178+dfsg-1 to 1:0.99.20~pre.178+dfsg-3:

Preparing to unpack .../01-jed_1%3a0.99.20~pre.178+dfsg-3_amd64.deb ...
Unpacking jed (1:0.99.20~pre.178+dfsg-3) over (1:0.99.20~pre.178+dfsg-1) ...
Preparing to unpack .../02-jed-common_1%3a0.99.20~pre.178+dfsg-3_all.deb ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-UN0WZQ/02-jed-common_1%3a0.99.20~pre.178+dfsg-3_all.deb 
(--unpack):
 new jed-common package pre-installation script subprocess returned error exit 
status 1
[…]
Errors were encountered while processing:
 /tmp/apt-dpkg-install-UN0WZQ/02-jed-common_1%3a0.99.20~pre.178+dfsg-3_all.deb
[…]
dpkg: dependency problems prevent configuration of jed:
 jed depends on jed-common (= 1:0.99.20~pre.178+dfsg-3); however:
  Version of jed-common on system is 1:0.99.20~pre.178+dfsg-1.

dpkg: error processing package jed (--configure):
 dependency problems - leaving unconfigured

I think that cause is this line in combination with "set -e"

  test -d $txtdir && rm -rf $txtdir

If the directory does not exist, it returns false because the test
failed. And due to the (totally legit) "set -e" it aborts there with
exit code not equal zero.

You likely need to replace it with a full if clause:

  if [ -d $txtdir ] ; then rm -rf $txtdir ; fi

Such code will not have this side effect.

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'testing-security'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 
'experimental-debug'), (1, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages jed-common depends on:
pn  slsh  

jed-common recommends no packages.

Versions of packages jed-common suggests:
ii  emacs-gtk [info-browser]  1:28.2+1-14
ii  info [info-browser]   6.8-6+b1
iu  jed [info-browser]1:0.99.20~pre.178+dfsg-3
ii  konqueror [info-browser]  4:22.12.3-1
ii  pinfo [info-browser]  0.6.13-1.3

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/doc/jed-common/changelog.Debian.gz (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/abbrev.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/color.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/compile.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/dfa.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/edt.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/emacs.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/filelock.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/fold.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/hooks.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/ide-mode.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/jed_faq.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/linux-keys.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/menus.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/mouse.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/pc-keys.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/program.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/recentx.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/rgrep.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/rmail.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/script.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/sessions.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/syntax.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/undo.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/utf8.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/wjed.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/wordstar.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/xjed.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/xr

Bug#1018730: lvm2: Initramfs does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot failure

[Christoph Anton Mitterer]

Hey Guilhem.

> There might be a better way to detect an initramfs-tools environment

I once faced the same question when writing a (cryptsetup) keyscript,
i.e. how to definitely find out whether one's "within" the initramfs.


With crypsetup it may seem easy - check for e.g. /scripts/local-
top/cryptroot - but that, as well as similar files (like
/conf/initramfs.conf) may in principle also exist after the system has
booted.

The best I could find was checking whether / is of type rootfs:

Something like:

# `grep`’s `-q`-option is not used as it may cause an exit status of `0` even
# when an error occurred.
grep -E '^[^ ]+ [^ ]+ [^ ]+ [^ ]+ / [^ ]+ ([^ ]+ )*- rootfs [^ ]+ [^ ]+$' 
/proc/self/mountinfo >/dev/null 2>/dev/null;  [ "$?" -ne 1 ];



But checking as you do may in practise fully suffice.


Cheers,
Chris.

Bug#1035781: emacs-common: needs Breaks against incompatible elpa packages from bullseye

[Rob Browning]

Rob Browning  writes:

> Right, I'm actually working on a release for this.  I think I should be
> able to upload today or tomorrow, and not sure if we need to wait for
> preapproval aince we'd want this in any other future migrations from
> unstable to testing/bullseye.

Oh, and possibly cf. https://bugs.debian.org/1034941 

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#1035781: emacs-common: needs Breaks against incompatible elpa packages from bullseye

[Rob Browning]

Rob Browning  writes:

> Rob Browning  writes:
>
>> Right, I'm actually working on a release for this.  I think I should be
>> able to upload today or tomorrow, and not sure if we need to wait for
>> preapproval aince we'd want this in any other future migrations from
>> unstable to testing/bullseye.
>
> Oh, and possibly cf. https://bugs.debian.org/1034941 

To clarify, I was planning to try to fix that one, and would of course
like to make sure whatever the fix is, it covers the cases you've found
too.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#1035781: emacs-common: needs Breaks against incompatible elpa packages from bullseye

[Rob Browning]

Andreas Beckmann  writes:

> There are some elpa packages from bullseye that won't be in bookworm and
> that are incompatible with emacs 28, i.e. upgrading emacs will fail if
> these packages are still installed.
> Therefore emacs-common needs to add Breaks against them s.t. they get
> removed during the upgrade to bookworm.

Right, I'm actually working on a release for this.  I think I should be
able to upload today or tomorrow, and not sure if we need to wait for
preapproval aince we'd want this in any other future migrations from
unstable to testing/bullseye.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Processed: Re: Bug#1018730: lvm2: Initramfs does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot failure

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1018730 [lvm2] lvm2: Initramfs does not activate root LVs if VG is 
incomplete since 2.03.15 or 2.03.16, boot failure
Bug #1034836 [lvm2] initramfs-tools: After bullseye -> bookworm upgrade boot 
stuck in the initramfs shell
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> tag -1 + patch
Bug #1018730 [lvm2] lvm2: Initramfs does not activate root LVs if VG is 
incomplete since 2.03.15 or 2.03.16, boot failure
Bug #1034836 [lvm2] initramfs-tools: After bullseye -> bookworm upgrade boot 
stuck in the initramfs shell
Added tag(s) patch.
Added tag(s) patch.

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

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

[Debian Bug Tracking System]

Your message dated Wed, 10 May 2023 00:56:04 +
with message-id 
and subject line Bug#1034992: fixed in slurm-wlm 22.05.8-4
has caused the Debian Bug report #1034992,
regarding slurm-wlm-rrd-plugin: missing Breaks+Replaces for 
slurm-wlm-basic-plugins 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.)


-- 
1034992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: slurm-wlm
Source-Version: 22.05.8-4
Done: Gennaro Oliva 

We believe that the bug you reported is fixed in the latest version of
slurm-wlm, 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.
Gennaro Oliva  (supplier of updated slurm-wlm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 10 May 2023 00:14:41 +0200
Source: slurm-wlm
Architecture: source
Version: 22.05.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Gennaro Oliva 
Closes: 1034950 1034955 1034978 1034987 1034992 1035562
Changes:
 slurm-wlm (22.05.8-4) unstable; urgency=medium
 .
   * Fix Breaks/Replaces dependencies (Closes: #1034950,
 #1034955, #1034978, #1034987, #1034992)
   * Restore plugstack.conf (Closes: #1035562)
Checksums-Sha1:
 a979d9e22c448479740f3c53d0c00505465de7e0 5255 slurm-wlm_22.05.8-4.dsc
 0719f99008a22ee412b3729e1e9ae0440d841c07 9699785 slurm-wlm_22.05.8.orig.tar.gz
 4afeb795d8fd020849e36323d397b6cbd8dbae77 134304 
slurm-wlm_22.05.8-4.debian.tar.xz
 12b3918458b84f362f98475b03c823947531f4ac 31174 
slurm-wlm_22.05.8-4_amd64.buildinfo
Checksums-Sha256:
 6d9be20b00448ea9fe822e4546ce07fe5515f38059619d0d18f32852b9ca461c 5255 
slurm-wlm_22.05.8-4.dsc
 8c8f6a26a5d51e6c63773f2e02653eb724540ee8b360125c8d7732314ce737d6 9699785 
slurm-wlm_22.05.8.orig.tar.gz
 f24465e26cfe933d754fc8c732a9dddedcbe89d6d8e25b7479f48db96332b1e1 134304 
slurm-wlm_22.05.8-4.debian.tar.xz
 b1c3c2b2c7aa4490f9921c3d9259d3425aacd081a86623d626851147cd758deb 31174 
slurm-wlm_22.05.8-4_amd64.buildinfo
Files:
 d6abbd9000c954571e703ed9aedc93cb 5255 admin optional slurm-wlm_22.05.8-4.dsc
 f7c710747f8eac5fe1940d48ce9d2775 9699785 admin optional 
slurm-wlm_22.05.8.orig.tar.gz
 c0dfd51fad4ff5bf0424177f0d1f51b9 134304 admin optional 
slurm-wlm_22.05.8-4.debian.tar.xz
 332745fa4d517264f27872e935af5026 31174 admin optional 
slurm-wlm_22.05.8-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEE6zNF9WRBuLgad5h2ffpBrZYZhdcFAmRazj4XHG9saXZhLmdA
bmEuaWNhci5jbnIuaXQACgkQffpBrZYZhdfYhw//eUjy+AP/vrB3MbA0sVNsltw4
EtvpEkkOizsdwDXZP6oNfc8W1u/3IdlCMSer3IWbFpS2K0gNX+tVnt9obhhqDD8A
Pv1ptETwFh8t/XzceZWAjzmwySAIHgU2iLbz8SYusFoi051izDYNJvFwBCqaHhLM
I+Dx1VKTJKmnyd9j6k9zHTCZ8CBEx0kXJqT1MLcG/w9L+gNZuj1OSKrS6M5nrJFX
EBgK3T0CwoTV8yIobWEa7cPCja3EFOrIp1iI8lYM92r+C+Q+ndxECTTgZyunjj4j
4vjqID9DK6/JGeatfu988uurkiv+XGw2mH9Pg1cRpXEbuKBiK0kGjG1DFNVktx1u
JxUUYkYrges0KjWpuQMKZsLIQnsv84yhkTXUO5l6Y88ExrMADyKAtZiWwGxj

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

[Debian Bug Tracking System]

Your message dated Wed, 10 May 2023 00:56:04 +
with message-id 
and subject line Bug#1034987: fixed in slurm-wlm 22.05.8-4
has caused the Debian Bug report #1034987,
regarding slurm-wlm-elasticsearch-plugin: missing Breaks+Replaces for 
slurm-wlm-basic-plugins 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.)


-- 
1034987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: slurm-wlm
Source-Version: 22.05.8-4
Done: Gennaro Oliva 

We believe that the bug you reported is fixed in the latest version of
slurm-wlm, 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.
Gennaro Oliva  (supplier of updated slurm-wlm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 10 May 2023 00:14:41 +0200
Source: slurm-wlm
Architecture: source
Version: 22.05.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Gennaro Oliva 
Closes: 1034950 1034955 1034978 1034987 1034992 1035562
Changes:
 slurm-wlm (22.05.8-4) unstable; urgency=medium
 .
   * Fix Breaks/Replaces dependencies (Closes: #1034950,
 #1034955, #1034978, #1034987, #1034992)
   * Restore plugstack.conf (Closes: #1035562)
Checksums-Sha1:
 a979d9e22c448479740f3c53d0c00505465de7e0 5255 slurm-wlm_22.05.8-4.dsc
 0719f99008a22ee412b3729e1e9ae0440d841c07 9699785 slurm-wlm_22.05.8.orig.tar.gz
 4afeb795d8fd020849e36323d397b6cbd8dbae77 134304 
slurm-wlm_22.05.8-4.debian.tar.xz
 12b3918458b84f362f98475b03c823947531f4ac 31174 
slurm-wlm_22.05.8-4_amd64.buildinfo
Checksums-Sha256:
 6d9be20b00448ea9fe822e4546ce07fe5515f38059619d0d18f32852b9ca461c 5255 
slurm-wlm_22.05.8-4.dsc
 8c8f6a26a5d51e6c63773f2e02653eb724540ee8b360125c8d7732314ce737d6 9699785 
slurm-wlm_22.05.8.orig.tar.gz
 f24465e26cfe933d754fc8c732a9dddedcbe89d6d8e25b7479f48db96332b1e1 134304 
slurm-wlm_22.05.8-4.debian.tar.xz
 b1c3c2b2c7aa4490f9921c3d9259d3425aacd081a86623d626851147cd758deb 31174 
slurm-wlm_22.05.8-4_amd64.buildinfo
Files:
 d6abbd9000c954571e703ed9aedc93cb 5255 admin optional slurm-wlm_22.05.8-4.dsc
 f7c710747f8eac5fe1940d48ce9d2775 9699785 admin optional 
slurm-wlm_22.05.8.orig.tar.gz
 c0dfd51fad4ff5bf0424177f0d1f51b9 134304 admin optional 
slurm-wlm_22.05.8-4.debian.tar.xz
 332745fa4d517264f27872e935af5026 31174 admin optional 
slurm-wlm_22.05.8-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEE6zNF9WRBuLgad5h2ffpBrZYZhdcFAmRazj4XHG9saXZhLmdA
bmEuaWNhci5jbnIuaXQACgkQffpBrZYZhdfYhw//eUjy+AP/vrB3MbA0sVNsltw4
EtvpEkkOizsdwDXZP6oNfc8W1u/3IdlCMSer3IWbFpS2K0gNX+tVnt9obhhqDD8A
Pv1ptETwFh8t/XzceZWAjzmwySAIHgU2iLbz8SYusFoi051izDYNJvFwBCqaHhLM
I+Dx1VKTJKmnyd9j6k9zHTCZ8CBEx0kXJqT1MLcG/w9L+gNZuj1OSKrS6M5nrJFX
EBgK3T0CwoTV8yIobWEa7cPCja3EFOrIp1iI8lYM92r+C+Q+ndxECTTgZyunjj4j
4vjqID9DK6/JGeatfu988u

Bug#1034978: marked as done (slurm-wlm-jwt-plugin: missing Breaks+Replaces for slurm-wlm-basic-plugins when upgrading from bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 10 May 2023 00:56:04 +
with message-id 
and subject line Bug#1034978: fixed in slurm-wlm 22.05.8-4
has caused the Debian Bug report #1034978,
regarding slurm-wlm-jwt-plugin: missing Breaks+Replaces for 
slurm-wlm-basic-plugins 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.)


-- 
1034978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slurm-wlm-jwt-plugin
Version: 22.05.8-3
Severity: serious
Justification: dpkg unpack error

Attempting to unpack slurm-wlm-jwt-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/auth_jwt.so being contained in both 
packages.

| Selecting previously unselected package slurm-wlm-jwt-plugin.
| (Reading database ... 5770 files and directories currently installed.)
| Preparing to unpack .../slurm-wlm-jwt-plugin_22.05.8-3_amd64.deb ...
| Unpacking slurm-wlm-jwt-plugin (22.05.8-3) ...
| dpkg: error processing archive ./slurm-wlm-jwt-plugin_22.05.8-3_amd64.deb 
(--unpack):
|  trying to overwrite '/usr/lib/x86_64-linux-gnu/slurm-wlm/auth_jwt.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-jwt-plugin_22.05.8-3_amd64.deb


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

Helmut
--- End Message ---
--- Begin Message ---
Source: slurm-wlm
Source-Version: 22.05.8-4
Done: Gennaro Oliva 

We believe that the bug you reported is fixed in the latest version of
slurm-wlm, 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.
Gennaro Oliva  (supplier of updated slurm-wlm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 10 May 2023 00:14:41 +0200
Source: slurm-wlm
Architecture: source
Version: 22.05.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Gennaro Oliva 
Closes: 1034950 1034955 1034978 1034987 1034992 1035562
Changes:
 slurm-wlm (22.05.8-4) unstable; urgency=medium
 .
   * Fix Breaks/Replaces dependencies (Closes: #1034950,
 #1034955, #1034978, #1034987, #1034992)
   * Restore plugstack.conf (Closes: #1035562)
Checksums-Sha1:
 a979d9e22c448479740f3c53d0c00505465de7e0 5255 slurm-wlm_22.05.8-4.dsc
 0719f99008a22ee412b3729e1e9ae0440d841c07 9699785 slurm-wlm_22.05.8.orig.tar.gz
 4afeb795d8fd020849e36323d397b6cbd8dbae77 134304 
slurm-wlm_22.05.8-4.debian.tar.xz
 12b3918458b84f362f98475b03c823947531f4ac 31174 
slurm-wlm_22.05.8-4_amd64.buildinfo
Checksums-Sha256:
 6d9be20b00448ea9fe822e4546ce07fe5515f38059619d0d18f32852b9ca461c 5255 
slurm-wlm_22.05.8-4.dsc
 8c8f6a26a5d51e6c63773f2e02653eb724540ee8b360125c8d7732314ce737d6 9699785 
slurm-wlm_22.05.8.orig.tar.gz
 f24465e26cfe933d754fc8c732a9dddedcbe89d6d8e25b7479f48db96332b1e1 134304 
slurm-wlm_22.05.8-4.debian.tar.xz
 b1c3c2b2c7aa4490f9921c3d9259d3425aacd081a86623d626851147cd758deb 31174 
slurm-wlm_22.05.8-4_amd64.buildinfo
Files:
 d6abbd9000c954571e703ed9aedc93cb 5255 admin optional slurm-wlm_22.05.8-4.dsc
 f7c710747f8eac5fe1940d48ce9d2775 9699785 admin optional 
slurm-wlm_22.05.8.orig.tar.gz
 c0dfd51fad4ff5bf0424177f0d1f51b9 134304 admin optional 
slurm-wlm_22.05.8-4.debian.tar.xz
 332745fa4d517264f27872e935af5026 31174 admin optional 
slurm-wlm_22.05.8-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEE6zNF9WRBuLgad5h2ffpBrZYZhdcFAmRazj4XHG9saXZhLmdA
bmEuaWNhci5jbnIuaXQACgkQffpBrZYZhdfYhw//eUjy+AP/vrB3MbA0sVNsltw4
EtvpEkkOizsdwDXZP6oNfc8W1u/3IdlCMSer3IWbFpS2K0gNX+tVnt9obhhqDD8A
Pv1ptETwFh8t/XzceZWAjzmwySAIHgU2iLbz8SYusFoi051izDYNJvFwBCqaHhLM
I+Dx1VKTJKmnyd9j6k9zHTCZ8CBEx0kXJqT1MLcG/w9L+gNZuj1OSKrS6M5nrJFX
EBgK3T0CwoTV8yIobWEa7cPCja3EFOrIp1iI8lYM92r+C+Q+ndxECTTgZyunjj4j
4vjqID9DK6/JGeatfu988uurkiv+XGw2mH9Pg1cRpXEbuKBiK0kGjG1DFNVktx1u
JxUUYkYrges0KjWpuQMKZsLIQnsv84yhkTXUO5l6Y88ExrMADyKAtZiWwGxjEe78
eN8xXk0Nh4

Bug#1034950: marked as done (slurm-wlm-hdf5-plugin: missing Breaks+Replaces in multiple situations when upgrading from bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 10 May 2023 00:56:04 +
with message-id 
and subject line Bug#1034950: fixed in slurm-wlm 22.05.8-4
has caused the Debian Bug report #1034950,
regarding slurm-wlm-hdf5-plugin: missing Breaks+Replaces in multiple situations 
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.)


-- 
1034950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slurm-wlm-hdf5-plugin
Version: 22.05.8-3
Severity: serious
Justification: dpkg unpack error

Attempting to unpack slurm-wlm-hdf5-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/acct_gather_profile_hdf5.so being contained 
in both packages.

| Selecting previously unselected package slurm-wlm-hdf5-plugin.
| (Reading database ... 5770 files and directories currently installed.)
| Preparing to unpack .../slurm-wlm-hdf5-plugin_22.05.8-3_amd64.deb ...
| Unpacking slurm-wlm-hdf5-plugin (22.05.8-3) ...
| dpkg: error processing archive ./slurm-wlm-hdf5-plugin_22.05.8-3_amd64.deb 
(--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/slurm-wlm/acct_gather_profile_hdf5.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-hdf5-plugin_22.05.8-3_amd64.deb

Attempting to unpack slurm-wlm-hdf5-plugin/22.05.8-3 from Debian bookworm
on a minimal Debian bullseye with slurm-client/20.11.7+really20.11.4-2+deb11u1
installed, causes an unpack error from dpkg due to
/usr/bin/sh5util being contained in both packages.

| Selecting previously unselected package slurm-wlm-hdf5-plugin.
| (Reading database ... 5876 files and directories currently installed.)
| Preparing to unpack .../slurm-wlm-hdf5-plugin_22.05.8-3_amd64.deb ...
| Unpacking slurm-wlm-hdf5-plugin (22.05.8-3) ...
| dpkg: error processing archive ./slurm-wlm-hdf5-plugin_22.05.8-3_amd64.deb 
(--unpack):
|  trying to overwrite '/usr/bin/sh5util', which is also in package 
slurm-client 20.11.7+really20.11.4-2+deb11u1
| Errors were encountered while processing:
|  ./slurm-wlm-hdf5-plugin_22.05.8-3_amd64.deb


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

Helmut
--- End Message ---
--- Begin Message ---
Source: slurm-wlm
Source-Version: 22.05.8-4
Done: Gennaro Oliva 

We believe that the bug you reported is fixed in the latest version of
slurm-wlm, 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.
Gennaro Oliva  (supplier of updated slurm-wlm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 10 May 2023 00:14:41 +0200
Source: slurm-wlm
Architecture: source
Version: 22.05.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Gennaro Oliva 
Closes: 1034950 1034955 1034978 1034987 1034992 1035562
Changes:
 slurm-wlm (22.05.8-4) unstable; urgency=medium
 .
   * Fix Breaks/Replaces dependencies (Closes: #1034950,
 #1034955, #1034978, #1034987, #1034992)
   * Restore plugstack.conf (Closes: #1035562)
Checksums-Sha1:
 a979d9e22c448479740f3c53d0c00505465de7e0 5255 slurm-wlm_22.05.8-4.dsc
 0719f99008a22ee412b3729e1e9ae0440d841c07 9699785 slurm-wlm_22.05.8.orig.tar.gz
 4afeb795d8fd020849e36323d397b6cbd8dbae77 134304 
slurm-wlm_22.05.8-4.debian.tar.xz
 12b3918458b84f362f98475b03c823947531f4ac 31174 
slurm-wlm_22.05.8-4_amd64.buildinfo
Checksums-Sha256:
 6d9be20b00448ea9fe822e4546ce07fe5515f38059619d0d18f32852b9ca461c 5255 
slurm-wlm_22.05.8-4.dsc
 8c8f6a26a5d51e6c63773f2e02653eb724540ee8b360125c8d7732314ce737d6 9699785 
slurm-wlm_22.05.8.orig.tar.gz
 f24465e26cfe933d754fc8c732a9dddedcbe89d6d8e25b7479f48db96332b1e1 134304 
slurm-wlm_22.05.8-4.debian.tar.xz
 b1c3c2b2c7aa4490f9921c3d9259d3425aacd081a86623d626851147cd758deb 31174 
slurm-wlm_22.05.8-4_amd64.buildinfo
Files:
 d6abbd9000c954571e703ed9aedc93cb 5255 admin optional slurm-wl

Bug#1034955: marked as done (slurm-wlm-influxdb-plugin: missing Breaks+Replaces for slurm-wlm-basic-plugins when upgrading from bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 10 May 2023 00:56:04 +
with message-id 
and subject line Bug#1034955: fixed in slurm-wlm 22.05.8-4
has caused the Debian Bug report #1034955,
regarding slurm-wlm-influxdb-plugin: missing Breaks+Replaces for 
slurm-wlm-basic-plugins 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.)


-- 
1034955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slurm-wlm-influxdb-plugin
Version: 22.05.8-3
Severity: serious
Justification: dpkg unpack error

Attempting to unpack slurm-wlm-influxdb-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/acct_gather_profile_influxdb.so being 
contained in both packages.

| Selecting previously unselected package slurm-wlm-influxdb-plugin.
| (Reading database ... 5770 files and directories currently installed.)
| Preparing to unpack .../slurm-wlm-influxdb-plugin_22.05.8-3_amd64.deb ...
| Unpacking slurm-wlm-influxdb-plugin (22.05.8-3) ...
| dpkg: error processing archive 
./slurm-wlm-influxdb-plugin_22.05.8-3_amd64.deb (--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/slurm-wlm/acct_gather_profile_influxdb.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-influxdb-plugin_22.05.8-3_amd64.deb


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

Helmut
--- End Message ---
--- Begin Message ---
Source: slurm-wlm
Source-Version: 22.05.8-4
Done: Gennaro Oliva 

We believe that the bug you reported is fixed in the latest version of
slurm-wlm, 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.
Gennaro Oliva  (supplier of updated slurm-wlm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 10 May 2023 00:14:41 +0200
Source: slurm-wlm
Architecture: source
Version: 22.05.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Gennaro Oliva 
Closes: 1034950 1034955 1034978 1034987 1034992 1035562
Changes:
 slurm-wlm (22.05.8-4) unstable; urgency=medium
 .
   * Fix Breaks/Replaces dependencies (Closes: #1034950,
 #1034955, #1034978, #1034987, #1034992)
   * Restore plugstack.conf (Closes: #1035562)
Checksums-Sha1:
 a979d9e22c448479740f3c53d0c00505465de7e0 5255 slurm-wlm_22.05.8-4.dsc
 0719f99008a22ee412b3729e1e9ae0440d841c07 9699785 slurm-wlm_22.05.8.orig.tar.gz
 4afeb795d8fd020849e36323d397b6cbd8dbae77 134304 
slurm-wlm_22.05.8-4.debian.tar.xz
 12b3918458b84f362f98475b03c823947531f4ac 31174 
slurm-wlm_22.05.8-4_amd64.buildinfo
Checksums-Sha256:
 6d9be20b00448ea9fe822e4546ce07fe5515f38059619d0d18f32852b9ca461c 5255 
slurm-wlm_22.05.8-4.dsc
 8c8f6a26a5d51e6c63773f2e02653eb724540ee8b360125c8d7732314ce737d6 9699785 
slurm-wlm_22.05.8.orig.tar.gz
 f24465e26cfe933d754fc8c732a9dddedcbe89d6d8e25b7479f48db96332b1e1 134304 
slurm-wlm_22.05.8-4.debian.tar.xz
 b1c3c2b2c7aa4490f9921c3d9259d3425aacd081a86623d626851147cd758deb 31174 
slurm-wlm_22.05.8-4_amd64.buildinfo
Files:
 d6abbd9000c954571e703ed9aedc93cb 5255 admin optional slurm-wlm_22.05.8-4.dsc
 f7c710747f8eac5fe1940d48ce9d2775 9699785 admin optional 
slurm-wlm_22.05.8.orig.tar.gz
 c0dfd51fad4ff5bf0424177f0d1f51b9 134304 admin optional 
slurm-wlm_22.05.8-4.debian.tar.xz
 332745fa4d517264f27872e935af5026 31174 admin optional 
slurm-wlm_22.05.8-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEE6zNF9WRBuLgad5h2ffpBrZYZhdcFAmRazj4XHG9saXZhLmdA
bmEuaWNhci5jbnIuaXQACgkQffpBrZYZhdfYhw//eUjy+AP/vrB3MbA0sVNsltw4
EtvpEkkOizsdwDXZP6oNfc8W1u/3IdlCMSer3IWbFpS2K0gNX+tVnt9obhhqDD8A
Pv1ptETwFh8t/XzceZWAjzmwySAIHgU2iLbz8SYusFoi051izDYNJvFwBCqaHhLM
I+Dx1VKTJKmnyd9j6k9zHTCZ8CBEx0kXJqT1MLcG/w9L+gNZuj1OSKrS6M5nrJFX
EBgK3T0CwoTV8yIobWEa7cPCja3EFOrIp1iI8lYM92r+C+Q+ndxECTTgZyunjj4j
4vjqID9DK6/JGeatfu988uurkiv+XGw2mH9Pg1cRpXEbuKBiK0kGjG

Processed: Re: Bug#1034836: initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - unreproducible
Bug #1034836 [cryptsetup-initramfs] initramfs-tools: After bullseye -> bookworm 
upgrade boot stuck in the initramfs shell
Removed tag(s) unreproducible.
> reassign -1 lvm2 2.03.15-1
Bug #1034836 [cryptsetup-initramfs] initramfs-tools: After bullseye -> bookworm 
upgrade boot stuck in the initramfs shell
Bug reassigned from package 'cryptsetup-initramfs' to 'lvm2'.
No longer marked as found in versions 0.142.
Ignoring request to alter fixed versions of bug #1034836 to the same values 
previously set
Bug #1034836 [lvm2] initramfs-tools: After bullseye -> bookworm upgrade boot 
stuck in the initramfs shell
Marked as found in versions lvm2/2.03.15-1.
> forcemerge 1018730 -1
Bug #1018730 [lvm2] lvm2: Initramfs does not activate root LVs if VG is 
incomplete since 2.03.15 or 2.03.16, boot failure
Bug #1034836 [lvm2] initramfs-tools: After bullseye -> bookworm upgrade boot 
stuck in the initramfs shell
Severity set to 'important' from 'critical'
Marked as found in versions lvm2/2.03.16-1.
Bug #1018730 [lvm2] lvm2: Initramfs does not activate root LVs if VG is 
incomplete since 2.03.15 or 2.03.16, boot failure
Marked as found in versions lvm2/2.03.15-1.
Merged 1018730 1034836
> affects -1 cryptsetup-initramfs
Bug #1034836 [lvm2] initramfs-tools: After bullseye -> bookworm upgrade boot 
stuck in the initramfs shell
Bug #1018730 [lvm2] lvm2: Initramfs does not activate root LVs if VG is 
incomplete since 2.03.15 or 2.03.16, boot failure
Added indication that 1034836 affects cryptsetup-initramfs
Added indication that 1018730 affects cryptsetup-initramfs

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

Bug#1034836: initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell

[Guilhem Moulin]

Control: tag -1 - unreproducible
Control: reassign -1 lvm2 2.03.15-1
Control: forcemerge 1018730 -1
Control: affects -1 cryptsetup-initramfs

Thanks for the the reproducer!  Much appreciated.  So the problem is
that your VG spans over multiple PVs, but the LVs that are required at
early boot stage (the ones holding the root FS and the resume device)
reside only on the first PV so cryptsetup-initramfs rightfully never
tries to unlock the second one (which only holds /home hence is not
needed that early).

This used to work, but it looks like lvm2's udev rules never try to
activate complete LVs residing on incomplete VGs, hence the deadlock.
This mostly affects cryptsetup-initramfs and perhaps the issue could be
mitigated there, but this is an lvm2 regression and non-luks systems can
be affected too [0] so I'm reassign the bug accordingly.  (Turns out it
was already reported, hence also merging.)

A quick fix for your particular setup is to edit crypttab(5), add the
‘initramfs’ option for the ‘4Tsolid’, and rebuild the initramfs image.
That should force the device to be considered at initramfs stage.

-- 
Guilhem.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1337220#c10


signature.asc
Description: PGP signature

Bug#1035833: cpptraj: autopkgtest failure everywhere except on amd64

[Kiran S Kunjumon]

Source: cpptraj
Version:  5.1.0+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You package cpptraj has an autopkgtest, great.
However, it fails everywhere except on amd64. Can you please investigate the 
situation and fix it?

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

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


https://qa.debian.org/excuses.php?package=cpptraj

https://ci.debian.net/data/autopkgtest/unstable/arm64/c/cpptraj/33255796/log.gz

=== FAILURES
===
TEST: /tmp/autopkgtest-lxc.kz5vbtvg/downtmp/build.qgE/src/test/Test_SPAM

  CPPTRAJ: SPAM Test
../MasterTest.sh: line 495:  3218 Killed  $cpptraj_cmd >> 
$CPPTRAJ_OUTPUT
Error:  cpptraj exited with status 137

  CPPTRAJ: SPAM Pure Solvent Test

  1 out of 2 executions exited with an error.
  2 out of 5 comparisons failed.

--
TEST: /tmp/autopkgtest-lxc.kz5vbtvg/downtmp/build.qgE/src/test/Test_SetVelocity

  CPPTRAJ: Set Velocity test

  CPPTRAJ: Scale velocity test

  1 out of 3 comparisons failed.

= TEST SUMMARY ==
  850 out of 859 comparisons OK (3 failed, 0 warnings, 6 skipped).
  479 out of 480 program executions completed.
  168 out of 173 tests completed with no issues.
  2 tests skipped.
=
make: *** [Makefile:662: summary] Error 4
make: Leaving directory 
'/tmp/autopkgtest-lxc.kz5vbtvg/downtmp/build.qgE/src/test'
autopkgtest [15:20:47]: test command1: ---]
autopkgtest [15:20:47]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 2
autopkgtest [15:20:47]: test command1:  - - - - - - - - - - stderr - - - - - - 
- - - -
../MasterTest.sh: line 495:  3218 Killed  $cpptraj_cmd >> 
$CPPTRAJ_OUTPUT
Error:  cpptraj exited with status 137
make: *** [Makefile:662: summary] Error 4
autopkgtest [15:20:48]:  summary
command1 FAIL non-zero exit status 2



OpenPGP_0x0D598BD7BC822E10.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034982: android-libnativehelper: missing Breaks+Replaces for android-libnativehelper-dev when upgrading from bullseye

[Andreas Beckmann]

Followup-For: Bug #1034982
Control: found -1 29.0.6-27

Hi,

this bug was not fixed correctly, yet.

The .so link actually moved from android-libnativehelper-dev to
android-libnativehelper (that's the unusual direction, since usually the
.so belongs to the -dev package). (Commit 306d8baf that wanted to fix
this issue describes it the other way around.)

debdiff excepts:

$ debdiff android-libnativehelper_10.0.0+r36-2_amd64.deb 
android-libnativehelper_29.0.6-27_amd64.deb

Files in second .deb but not in first
-
-rw-r--r--  root/root   /usr/share/lintian/overrides/android-libnativehelper
lrwxrwxrwx  root/root   /usr/lib/x86_64-linux-gnu/android/libnativehelper.so -> 
libnativehelper.so.0

$ debdiff android-libnativehelper-dev_10.0.0+r36-2_amd64.deb 
android-libnativehelper-dev_29.0.6-27_amd64.deb

Files in second .deb but not in first
-
-rw-r--r--  root/root   /usr/include/android/nativehelper/libnativehelper_api.h
-rw-r--r--  root/root   /usr/share/doc/android-libnativehelper-dev/README

Files in first .deb but not in second
-
-rw-r--r--  root/root   /usr/include/android/nativehelper/module_api.h
-rw-r--r--  root/root   /usr/share/doc/android-libnativehelper/README
lrwxrwxrwx  root/root   /usr/lib/x86_64-linux-gnu/android/libnativehelper.so -> 
libnativehelper.so.0

So you actually need

Package: android-libnativehelper
Breaks: android-libnativehelper-dev (<< 29)
Replaces: android-libnativehelper-dev (<< 29)   <== this is currently missing

and in the -dev package you could revert to

Package: android-libnativehelper-dev
Breaks: android-libnativehelper (<< 10.0.0+r36-1~)
Replaces: android-libnativehelper (<< 10.0.0+r36-1~)

since no files were moved in the other direction.
(That would make apt's job a bit simpler.)


Andreas

Processed: Re: android-libnativehelper: missing Breaks+Replaces for android-libnativehelper-dev when upgrading from bullseye

[Debian Bug Tracking System]

Processing control commands:

> found -1 29.0.6-27
Bug #1034982 {Done: Roger Shimizu } [android-libnativehelper] 
android-libnativehelper: missing Breaks+Replaces for 
android-libnativehelper-dev when upgrading from bullseye
Marked as found in versions android-platform-tools/29.0.6-27; no longer marked 
as fixed in versions android-platform-tools/29.0.6-27 and reopened.

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

Bug#1034976: marked as pending in gensio

[Marc Haber]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/gensio/-/commit/a1d30959e71df17106fd6c55b1f8e714342d28ce


gensio-bin: add missing Breaks+Replaces for libgensio-dev

Thanks: Helmut Grohne
Closes: #1034976


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1034976

Processed: Bug#1034976 marked as pending in gensio

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1034976 [gensio-bin] gensio-bin: missing Breaks+Replaces for libgensio-dev 
when upgrading from bullseye
Ignoring request to alter tags of bug #1034976 to the same tags previously set

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

Bug#1035764: marked as done (libtsm-dev: copyright file missing after upgrade (policy 12.5))

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 19:48:49 +
with message-id 
and subject line Bug#1035764: fixed in libtsm 4.0.2-0.4
has caused the Debian Bug report #1035764,
regarding libtsm-dev: copyright file missing after upgrade (policy 12.5)
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.)


-- 
1035764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtsm-dev
Version: 4.0.2-0.3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  bullseye -> bookworm

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

  MISSING COPYRIGHT FILE: /usr/share/doc/libtsm-dev/copyright
  # ls -lad /usr/share/doc/libtsm-dev
  drwxr-xr-x 2 root root 40 May  3 14:43 /usr/share/doc/libtsm-dev
  # ls -la /usr/share/doc/libtsm-dev/
  total 0
  drwxr-xr-x   2 root root   40 May  3 14:43 .
  drwxr-xr-x 114 root root 2320 May  3 14:43 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libtsm-dev_4.0.2-0.3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libtsm
Source-Version: 4.0.2-0.4
Done: Victor Westerhuis 

We believe that the bug you reported is fixed in the latest version of
libtsm, 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.
Victor Westerhuis  (supplier of updated libtsm 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: Tue, 09 May 2023 17:47:55 +0200
Source: libtsm
Architecture: source
Version: 4.0.2-0.4
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Victor Westerhuis 
Closes: 1035764
Changes:
 libtsm (4.0.2-0.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Unbreak d/watch broken by Github changes.
   * Switch /usr/share/doc/libtsm-dev from dir to symlink on upgrade.
 Thanks to Andreas Beckmann for reporting this packaging error.
 (Closes: #1035764)
Checksums-Sha1:
 f3f800a25a0b3e0c282d114a4fb37d74df96bac3 1667 libtsm_4.0.2-0.4.dsc
 365cf1192d108bb607019cd9cfb0cace908c78e3 5320 libtsm_4.0.2-0.4.debian.tar.xz
 462043e1b4441ce3644f200f7c7462d63a005de2 6386 libtsm_4.0.2-0.4_source.buildinfo
Checksums-Sha256:
 0b9f14c7007b71e0d2fa6f5dc4683801070d15e9694438b98dcde08e4f00919f 1667 
libtsm_4.0.2-0.4.dsc
 5aaf148c4b58dd9daf86baa0ae1ec21560f6ce039b2f5779e85aa6e095823ba5 5320 
libtsm_4.0.2-0.4.debian.tar.xz
 e12dd1d916f4892b6cfa1c6d5a49bd54bd9db37f945b48a6d6deefca7c9fcb7f 6386 
libtsm_4.0.2-0.4_source.buildinfo
Files:
 5d7b67260bd048e12882cb22825fd0eb 1667 libs optional libtsm_4.0.2-0.4.dsc
 641114eec4c33225310afbd0e8f6fe04 5320 libs optional 
libtsm_4.0.2-0.4.debian.tar.xz
 2466da3250bcf3afb96b2e6365a42881 6386 libs optional 
libtsm_4.0.2-0.4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmRaoEoQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFMZdDACBqS5DWBENvxWU17/ofTEfb6SFq0a7fQXL
jYu+tPNALhPPEeT7qNntK13lkxk4lbn1I8weGKEBx+2+qJ8eiIgpfwzSOjKSy8aM
qj0c7b2l3FBM0tstX2hH2jQAOHW8Ha3Klznk5j9+DgDqgy1ekekoFEAHUjB9UR3C
zxMFIl4IUcUC0/tbbP8OAX24ONdD60+be2ak4LI3pJpMwmgwloHwzjel9AsnxEtd
550m0nrmFhio1fMxX4KWJWYjIo2ActLzvSzCZCKOLRkqodSHKZUKYcCwgj

Bug#1035764: libtsm-dev: copyright file missing after upgrade (policy 12.5)

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru libtsm-4.0.2/debian/changelog libtsm-4.0.2/debian/changelog
--- libtsm-4.0.2/debian/changelog   2022-04-29 21:18:06.0 +0200
+++ libtsm-4.0.2/debian/changelog   2023-05-09 17:47:55.0 +0200
@@ -1,3 +1,13 @@
+libtsm (4.0.2-0.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Unbreak d/watch broken by Github changes.
+  * Switch /usr/share/doc/libtsm-dev from dir to symlink on upgrade.
+Thanks to Andreas Beckmann for reporting this packaging error.
+(Closes: #1035764)
+
+ -- Victor Westerhuis   Tue, 09 May 2023 17:47:55 +0200
+
 libtsm (4.0.2-0.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libtsm-4.0.2/debian/libtsm-dev.maintscript 
libtsm-4.0.2/debian/libtsm-dev.maintscript
--- libtsm-4.0.2/debian/libtsm-dev.maintscript  1970-01-01 01:00:00.0 
+0100
+++ libtsm-4.0.2/debian/libtsm-dev.maintscript  2023-05-09 17:47:52.0 
+0200
@@ -0,0 +1 @@
+dir_to_symlink /usr/share/doc/libtsm-dev /usr/share/doc/libtsm4 4.0.2-0.4~
diff -Nru libtsm-4.0.2/debian/watch libtsm-4.0.2/debian/watch
--- libtsm-4.0.2/debian/watch   2022-04-27 12:06:51.0 +0200
+++ libtsm-4.0.2/debian/watch   2023-05-09 17:47:51.0 +0200
@@ -1,4 +1,4 @@
 version=4
 
-https://github.com/Aetf/libtsm/releases \
+https://github.com/Aetf/libtsm/tags \
 .*/v@ANY_VERSION@\.tar\.(?:gz|bz2|xz) debian

Bug#1034976: marked as pending in gensio

[Marc Haber]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/gensio/-/commit/60eb4ac67d69c0a04e6be724ca84e002c4877424


gensio-bin: missing Breaks+Replaces for libgensio-dev

Thanks: Helmut Grohne
Closes: #1034976


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1034976

Processed: Bug#1034976 marked as pending in gensio

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1034976 [gensio-bin] gensio-bin: missing Breaks+Replaces for libgensio-dev 
when upgrading from bullseye
Added tag(s) pending.

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

Bug#1035829: frr: CVE-2022-43681 CVE-2022-40318 CVE-2022-40302

[Moritz Mühlenhoff]

Source: frr
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for frr.

CVE-2022-43681[0]:
| An out-of-bounds read exists in the BGP daemon of FRRouting FRR
| through 8.4. When sending a malformed BGP OPEN message that ends with
| the option length octet (or the option length word, in case of an
| extended OPEN message), the FRR code reads of out of the bounds of the
| packet, throwing a SIGABRT signal and exiting. This results in a bgpd
| daemon restart, causing a Denial-of-Service condition.

CVE-2022-40318[1]:
| An issue was discovered in bgpd in FRRouting (FRR) through 8.4. By
| crafting a BGP OPEN message with an option of type 0xff (Extended
| Length from RFC 9072), attackers may cause a denial of service
| (assertion failure and daemon restart, or out-of-bounds read). This is
| possible because of inconsistent boundary checks that do not account
| for reading 3 bytes (instead of 2) in this 0xff case. NOTE: this
| behavior occurs in bgp_open_option_parse in the bgp_open.c file, a
| different location (with a different attack vector) relative to
| CVE-2022-40302.

CVE-2022-40302[2]:
| An issue was discovered in bgpd in FRRouting (FRR) through 8.4. By
| crafting a BGP OPEN message with an option of type 0xff (Extended
| Length from RFC 9072), attackers may cause a denial of service
| (assertion failure and daemon restart, or out-of-bounds read). This is
| possible because of inconsistent boundary checks that do not account
| for reading 3 bytes (instead of 2) in this 0xff case.

Upstream's reaction on requests for information on these issues is
far from optimal..

https://github.com/FRRouting/frr/issues/13427
https://github.com/FRRouting/frr/issues/13480

Cheers,
Moritz

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-43681
https://www.cve.org/CVERecord?id=CVE-2022-43681
[1] https://security-tracker.debian.org/tracker/CVE-2022-40318
https://www.cve.org/CVERecord?id=CVE-2022-40318
[2] https://security-tracker.debian.org/tracker/CVE-2022-40302
https://www.cve.org/CVERecord?id=CVE-2022-40302

Please adjust the affected versions in the BTS as needed.

Bug#1035445: marked as done (libopenvlbi-dev: missing Depends: libopenvlbi1 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 17:19:43 +
with message-id 
and subject line Bug#1035445: fixed in openvlbi 1.23.5-2
has caused the Debian Bug report #1035445,
regarding libopenvlbi-dev: missing Depends: libopenvlbi1 (= ${binary:Version})
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.)


-- 
1035445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenvlbi-dev
Version: 1.23.5-1
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.

0m13.8s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libopenvlbi.so -> libopenvlbi.so.1 
(libopenvlbi-dev:amd64)


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: openvlbi
Source-Version: 1.23.5-2
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
openvlbi, 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.
Thorsten Alteholz  (supplier of updated openvlbi 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: Tue, 09 May 2023 18:20:46 +0200
Source: openvlbi
Architecture: source
Version: 1.23.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Thorsten Alteholz 
Closes: 1035445
Changes:
 openvlbi (1.23.5-2) unstable; urgency=medium
 .
   * debian/control: add missing dependencies
 (Closes: #1035445)
Checksums-Sha1:
 5b72e3e17ab4e850687e6bbb3f2b403c036cbbfb 2650 openvlbi_1.23.5-2.dsc
 1c07290df27b17300aa0b74a4ab2c8cb429ab6bc 4040182 openvlbi_1.23.5.orig.tar.gz
 3eece282910ecf4b8abea4565681659a86d4074c 4804 openvlbi_1.23.5-2.debian.tar.xz
 823b83b764ab3a695624a978223f9ccf94310586 11353 
openvlbi_1.23.5-2_amd64.buildinfo
Checksums-Sha256:
 f6bc5f80cf7972112601c3bb5523431b3f816bb1b94cc220c248b4afbe461a40 2650 
openvlbi_1.23.5-2.dsc
 1482904e80c664e056d1521af7f19e82c24b5e8d18f9cfccf1e582aa347296ef 4040182 
openvlbi_1.23.5.orig.tar.gz
 0a49bce0cc65c47bd2c4156707aaddc316db9089096d96b9b3b82824567c266c 4804 
openvlbi_1.23.5-2.debian.tar.xz
 758d0d9420d43153c3894379fd6bdee78ac6f6e9e26564d1c2c5abed2943eec0 11353 
openvlbi_1.23.5-2_amd64.buildinfo
Files:
 f2c1e9dc084f50c6e8578dc1713a6fa0 2650 misc optional openvlbi_1.23.5-2.dsc
 d72e0f979cdf2a220904c31b31bff1d5 4040182 misc optional 
openvlbi_1.23.5.orig.tar.gz
 4f10209084595020dacb27b9e8d6cf16 4804 misc optional 
openvlbi_1.23.5-2.debian.tar.xz
 7360eac3e04f30cd7f0343d06d283f95 11353 misc optional 
openvlbi_1.23.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmRafhJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR8jNEAC6CWqaQTbUdPyfKP5JHsna/SQqWJv9
Z4xbExH+O49CSdUVu0KP+mWpOKzplLA2Z/Z9VyhAZ7v9ISjWgWiNbtIAjRqbndFg
/sPckIXom+x4S1SG6dSdDj32DJlOKn1i7qeGrpHu6OTT8TPuJDDvTnPpTk6KIMbd
Z2wCAf6+S0EPwXYP3rxTGuIQWxsKBXs7NAvPsy8Oq4xadjqk/LnzrDZhBjZ7+b0p
Cj9t1vFFTMiyDUn0ejtmFm9hK430trt98DNBQ6NgEX6KUHnv1iaKET2lU7vyntUU
twJdpOkEVfLhyWJlQE7M4QzIhvyEXGE54Bl2eV03KGhCoH9oJ8e3ViL3sNNM22UL
n+dedzfJyVTG4jMg0rBHOs8ELU93UpW75xAewYFivYawqJdULl4Pg6hfTNb0CbI+
pn2wyoKsSySm2hPhW1I43pr3O4G6QIKhW4PMLdxRQfFOE60hH1XspakRpCew8AN5
iEUT6GYfRHhglSKNxLPcxu4pHP6waOgjXJmq6PUB6h3gspSETBXP1HOX2BRu5snI
BHHK/OsTzcSenEFc0cZISVALKU6jnuDq4YFXPg9WQE0YPbTdciyx+PGSmcy3c3fW
RRTC8Z4dGpdZ8qVOlo3TZw43hXdlF3F0bhLqT4uUug+3GaGk5M7CS1C59AVLbJ9s
wYHrc7sENUMg7w==
=zdGS
-END PGP SIGNATURE End Message ---

Bug#1029559: marked as done (sc-im FTBFS: link error)

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 17:19:52 +
with message-id 
and subject line Bug#1029559: fixed in sc-im 0.8.3+ds-2
has caused the Debian Bug report #1029559,
regarding sc-im FTBFS: link error
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.)


-- 
1029559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sc-im
Version: 0.8.3+ds-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=sc-im&ver=0.8.3%2Bds-1

...
/usr/bin/ld: tui.o: warning: relocation against `COLORS' in read-only section 
`.text'
/usr/bin/ld: main.o: in function `sig_tstp':
./src/./src/main.c:633: undefined reference to `def_prog_mode'
/usr/bin/ld: ./src/./src/main.c:634: undefined reference to `endwin'
/usr/bin/ld: main.o: in function `sig_cont':
./src/./src/main.c:647: undefined reference to `reset_prog_mode'
/usr/bin/ld: ./src/./src/main.c:648: undefined reference to `stdscr'
/usr/bin/ld: ./src/./src/main.c:648: undefined reference to `wrefresh'
/usr/bin/ld: color.o: in function `redefine_color':
./src/./src/color.c:586: undefined reference to `has_colors'
/usr/bin/ld: ./src/./src/color.c:586: undefined reference to `can_change_color'
/usr/bin/ld: ./src/./src/color.c:594: undefined reference to 
`init_extended_color'
/usr/bin/ld: color.o: in function `define_color':
./src/./src/color.c:627: undefined reference to `has_colors'
/usr/bin/ld: ./src/./src/color.c:627: undefined reference to `can_change_color'
/usr/bin/ld: ./src/./src/color.c:627: undefined reference to `COLORS'
/usr/bin/ld: ./src/./src/color.c:661: undefined reference to 
`init_extended_color'
...
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:194: sc-im] Error 1
--- End Message ---
--- Begin Message ---
Source: sc-im
Source-Version: 0.8.3+ds-2
Done: Gürkan Myczko 

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

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

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated sc-im 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, 09 May 2023 19:02:12 +0200
Source: sc-im
Architecture: source
Version: 0.8.3+ds-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Gürkan Myczko 
Closes: 1023267 1029559 1029570
Changes:
 sc-im (0.8.3+ds-2) experimental; urgency=medium
 .
   * d/control:
 - add myself to Uploaders.
 - add pkgconf to Build-Depends. (Closes: #1029559)
 - add gvim, w3m, evince as reported by bug. (Closes: #1023267)
 - adjust virtaul package gnuplot.
 - update libtinfo-dev to libncurses-dev.
   * d/copyright: relicensed d/* to BSD-4-clause. (Closes: #1029570)
Checksums-Sha1:
 fe8439a0143abbf4382694163a003eff7321c220 2008 sc-im_0.8.3+ds-2.dsc
 603fe442366a50d5dd29e26401f58076522fd44e 3200 sc-im_0.8.3+ds-2.debian.tar.xz
 e8b16cb47666cf909f2f61a3907f93511a49e134 11079 
sc-im_0.8.3+ds-2_source.buildinfo
Checksums-Sha256:
 9fee8b59e4541c4d0d945d502b2b0e9f149e554b364670248d6df2941502811c 2008 
sc-im_0.8.3+ds-2.dsc
 4d04e3fb5c20c8cd393499f01c710e6691c22b6f4c86cd3d69525c889eb8fbdd 3200 
sc-im_0.8.3+ds-2.debian.tar.xz
 1d1019849a14d7456f22c4a83a8495c17001be8be0cd7b8f5f52a93afb059a4f 11079 
sc-im_0.8.3+ds-2_source.buildinfo
Files:
 54d98e437344ffe7de89b2233e157869 2008 math optional sc-im_0.8.3+ds-2.dsc
 0210beccacd1a5c56662edba43c459c8 3200 math optional 
sc-im_0.8.3+ds-2.debian.tar.xz
 ebb7cbb482932618ec4383d7c9d7c382 11079 math optional 
sc-im_0.8.3+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmRafRkACgkQEWhSvN91
FcDt6BAAlYOViXXPLiKxihWPdB2+d0D812sj3R2ZgTo62biWNM9svepm2/xuyiNH
zIWKRA2PNrv+665aRv6R68DrFmgS2oPnQiUmuQNB63ZJVe4308Ukvw3h3xEg3DCS
fvYklOMkGgcQ5VBoBeb0zYunoCACT2IXIMrGw8ES6kq8s1JoDKNeqRyJrcusYNYr
fiOb8to4/jbyqMGM+63n932CtU0wGtVPDN1nXasqUqmrkciyeJj5itqzUi6Z9tPc
2bciTUAPdXAgSxWDBbissWUgQ/ysZEEZurbbFp3zxHjLvi2i+/w8TL47q9snPuN2
1/7YBVPhUG+PWCJbFtORCz6iNp65dA89YLV72vGFi4YZlhofugMbQBWZN0Ku+8ql
JPeaOhd1aInCntWKMpnVMJdV1UPq+EhUoCAR5IxWJqQSriJ

Bug#1029570: marked as done (sc-im: debian/copyright file seems to be inaccurate)

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 17:19:52 +
with message-id 
and subject line Bug#1029570: fixed in sc-im 0.8.3+ds-2
has caused the Debian Bug report #1029570,
regarding sc-im: debian/copyright file seems to be inaccurate
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.)


-- 
1029570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sc-im
Version: 0.8.3+ds-1
Severity: serious
Justification: Policy 4.5

Hello!
Thanks for packaging this interesting program.

I noticed that the [debian/copyright] file seems to be inaccurate
with respect to the [upstream license].

The [debian/copyright] file states:

  [...]
  Files: *
  Copyright: 2013-2021, Andrés Martinelli 
  License: BSD-4-Clause
  [...]

which looks accurate, but then the documented license text
is not a verbatim copy of the [upstream license].

Most notably, clause 3 (out of 4) is missing.
Other minor differences are present.

Please fix the debian/copyright file by including the
correct verbatim copy of the upstream license text.

[debian/copyright]: 

[upstream license]: 


Please note that clause 3 is the infamous "obnoxious advertising
clause" [OAC], which, unfortunately, makes the 4-clause BSD license
GPL-incompatible.

[OAC]: 

As a consequence, I would also recommend to not license
debian/* files under GPL-2+, since having two incompatible
licenses in the same package is risky (it could lead to
a legally undistributable package, unless much care is
taken to never mix the two parts up...).
Maybe debian/* files could be relicensed under the terms
of some non-copyleft permissive license (such as
the Expat license or maybe the 3-clause BSD license...),
if the copyright holder (Joshua Peisach) agrees.


In the meanwhile, it would be really nice, if upstream could
be persuaded to drop the [OAC], thus relicensing the program
under the terms of the 3-clause BSD license.
Why? Because the 4-clause BSD license is a deprecated license,
which causes many GPL-compatibility troubles in the rare cases
where it is still used.
Since the upstream program copyright is currently held by one
sole person, it is still pretty easy to switch to a better
license: only one guy to be persuaded!   :-)

Please try and get in touch with upstream about this.

Thanks for your time and dedication!
Bye.
--- End Message ---
--- Begin Message ---
Source: sc-im
Source-Version: 0.8.3+ds-2
Done: Gürkan Myczko 

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

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

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated sc-im 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, 09 May 2023 19:02:12 +0200
Source: sc-im
Architecture: source
Version: 0.8.3+ds-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Gürkan Myczko 
Closes: 1023267 1029559 1029570
Changes:
 sc-im (0.8.3+ds-2) experimental; urgency=medium
 .
   * d/control:
 - add myself to Uploaders.
 - add pkgconf to Build-Depends. (Closes: #1029559)
 - add gvim, w3m, evince as reported by bug. (Closes: #1023267)
 - adjust virtaul package gnuplot.
 - update libtinfo-dev to libncurses-dev.
   * d/copyright: relicensed d/* to BSD-4-clause. (Closes: #1029570)
Checksums-Sha1:
 fe8439a0143abbf4382694163a003eff7321c220 2008 sc-im_0.8.3+ds-2.dsc
 603fe442366a50d5dd29e26401f58076522fd44e 3200 sc-im_0.8.3+ds-2.debian.tar.xz
 e8b16cb47666cf909f2f61a3907f93511a49e134 11079 
sc-im_0.8.3+ds-2_source.buildinfo
Checksums-Sha256:
 9fee8b59e4541c4d0d945d502b2b0e9f149e554b364670248d6df2941502811c 2008 
sc-im_0.8.3+ds-2.dsc
 4d04e3fb5c20c8cd393499f01c710e6691c22b6f4c86cd3d69525c889eb8fbdd 3200 
sc-im_0.8.3+ds-2.debian.tar.xz
 1d1019849a14d7456f22c4a83a8495c17001be8be0cd7b8f5f52a93afb059a4f 11079 
sc-im_0.8.3+ds

Bug#1023267: marked as done (sc-im: scopen fails with gvim not found (if it is not installed))

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 17:19:52 +
with message-id 
and subject line Bug#1023267: fixed in sc-im 0.8.3+ds-2
has caused the Debian Bug report #1023267,
regarding sc-im: scopen fails with gvim not found (if it is not installed)
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.)


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

Package: sc-im
Version: 0.8.2+ds-1
Severity: normal

Dear Maintainer,

sc-im ships a shell script called scopen, it looks like:
8<---snip
[[ $Ext == htm* ]] && exec w3m "$File"
[[ $Ext =~ (sc|tab|csv) ]] && exec sc-im "$File"
[[ $Ext == pdf ]] && exec_bg evince "$File"

exec_bg gvim "$File"
snap--->8

there's calls to w3m, evince and gvim, however the sc-im binary
does not depend on them.

One way to get this fixed is to not ship scopen, another to add the
packages as Depends in the binary package.

Thanks,
--- End Message ---
--- Begin Message ---
Source: sc-im
Source-Version: 0.8.3+ds-2
Done: Gürkan Myczko 

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated sc-im 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, 09 May 2023 19:02:12 +0200
Source: sc-im
Architecture: source
Version: 0.8.3+ds-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Gürkan Myczko 
Closes: 1023267 1029559 1029570
Changes:
 sc-im (0.8.3+ds-2) experimental; urgency=medium
 .
   * d/control:
 - add myself to Uploaders.
 - add pkgconf to Build-Depends. (Closes: #1029559)
 - add gvim, w3m, evince as reported by bug. (Closes: #1023267)
 - adjust virtaul package gnuplot.
 - update libtinfo-dev to libncurses-dev.
   * d/copyright: relicensed d/* to BSD-4-clause. (Closes: #1029570)
Checksums-Sha1:
 fe8439a0143abbf4382694163a003eff7321c220 2008 sc-im_0.8.3+ds-2.dsc
 603fe442366a50d5dd29e26401f58076522fd44e 3200 sc-im_0.8.3+ds-2.debian.tar.xz
 e8b16cb47666cf909f2f61a3907f93511a49e134 11079 
sc-im_0.8.3+ds-2_source.buildinfo
Checksums-Sha256:
 9fee8b59e4541c4d0d945d502b2b0e9f149e554b364670248d6df2941502811c 2008 
sc-im_0.8.3+ds-2.dsc
 4d04e3fb5c20c8cd393499f01c710e6691c22b6f4c86cd3d69525c889eb8fbdd 3200 
sc-im_0.8.3+ds-2.debian.tar.xz
 1d1019849a14d7456f22c4a83a8495c17001be8be0cd7b8f5f52a93afb059a4f 11079 
sc-im_0.8.3+ds-2_source.buildinfo
Files:
 54d98e437344ffe7de89b2233e157869 2008 math optional sc-im_0.8.3+ds-2.dsc
 0210beccacd1a5c56662edba43c459c8 3200 math optional 
sc-im_0.8.3+ds-2.debian.tar.xz
 ebb7cbb482932618ec4383d7c9d7c382 11079 math optional 
sc-im_0.8.3+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmRafRkACgkQEWhSvN91
FcDt6BAAlYOViXXPLiKxihWPdB2+d0D812sj3R2ZgTo62biWNM9svepm2/xuyiNH
zIWKRA2PNrv+665aRv6R68DrFmgS2oPnQiUmuQNB63ZJVe4308Ukvw3h3xEg3DCS
fvYklOMkGgcQ5VBoBeb0zYunoCACT2IXIMrGw8ES6kq8s1JoDKNeqRyJrcusYNYr
fiOb8to4/jbyqMGM+63n932CtU0wGtVPDN1nXasqUqmrkciyeJj5itqzUi6Z9tPc
2bciTUAPdXAgSxWDBbissWUgQ/ysZEEZurbbFp3zxHjLvi2i+/w8TL47q9snPuN2
1/7YBVPhUG+PWCJbFtORCz6iNp65dA89YLV72vGFi4YZlhofugMbQBWZN0Ku+8ql
JPeaOhd1aInCntWKMpnVMJdV1UPq+EhUoCAR5IxWJqQSriJMWK9ejEB+IzDyIK96
ny7Kpds7jrAEmw4Jg3u3oWS5RAU7Dh0XuvYH6UitIxRe0X+y5xYO2JKpoYUmng3B
x6by3oW4D6UQAg+pARlBDI0ACtJ0DQVBn38txJy0QmuiiyfbDoiQeViEC9dl8NXT
Tem19v1Inft6px72sLWroy2VAJWYTwKZZAR5CcTmnK27uNxuJNQCYB/xRwxZerxn
5lcRo0sE0CVUPLc8ITyRFykFJHIUBtd9sNaSVjn/T/jSneowDNM=
=ELTt
-END PGP SIGNATURE End Message ---

Bug#886052: ogmrip: GSettings migration happened upstream

[Bastian Germann]

On Sun, 11 Sep 2022 20:06:18 -0400 Jeremy Bicha  
wrote:

ogmrip is basically the last package keeping gconf in Debian. There
has been plenty of notice and ogmrip was already removed from Testing
months ago.


Unfortunately, alarm-clock-applet reentered Debian, which also depends on gconf.


In this case, there apparently was work years ago to port it to
gsettings. It only needs a maintainer to do the integration work to
get it into Debian.


In the mean time I disable the gtk (and gconf) support with a NMU (dediff 
attached).diff -Nru ogmrip-1.0.1/debian/changelog ogmrip-1.0.1/debian/changelog
--- ogmrip-1.0.1/debian/changelog   2021-06-15 17:53:43.0 +0200
+++ ogmrip-1.0.1/debian/changelog   2023-05-09 18:35:29.0 +0200
@@ -1,3 +1,10 @@
+ogmrip (1.0.1-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable GUI and dbus. (Closes: #886052, #955929, #967667, #967881)
+
+ -- Bastian Germann   Tue, 09 May 2023 18:35:29 +0200
+
 ogmrip (1.0.1-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ogmrip-1.0.1/debian/control ogmrip-1.0.1/debian/control
--- ogmrip-1.0.1/debian/control 2020-04-15 21:47:50.0 +0200
+++ ogmrip-1.0.1/debian/control 2023-05-09 18:35:29.0 +0200
@@ -9,12 +9,9 @@
  debhelper-compat (= 12),
  gtk-doc-tools,
  intltool,
- libdbus-glib-1-dev (>= 0.7.2),
  libdvdread-dev (>= 4.1.3-4),
  libenca-dev,
  libenchant-2-dev,
- libgconf2-dev,
- libglade2-dev,
  libnotify-dev (>= 0.7),
  libtheora-dev,
  libtiff-dev,
@@ -128,8 +125,6 @@
  intltool,
  libdvdread-dev,
  libenca-dev,
- libgconf2-dev,
- libglade2-dev,
  libogmrip1 (= ${binary:Version}),
  ${misc:Depends}
 Description: Application for ripping and encoding DVD - development files
diff -Nru ogmrip-1.0.1/debian/ogmrip.1 ogmrip-1.0.1/debian/ogmrip.1
--- ogmrip-1.0.1/debian/ogmrip.12020-04-15 21:46:32.0 +0200
+++ ogmrip-1.0.1/debian/ogmrip.11970-01-01 01:00:00.0 +0100
@@ -1,55 +0,0 @@
-.\"  Hey, EMACS: -*- nroff -*-
-.\" First parameter, NAME, should be all caps
-.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
-.\" other parameters are allowed: see man(7), man(1)
-.TH OGMRIP 1 "July 16, 2007"
-.\" Please adjust this date whenever revising the manpage.
-.\"
-.\" Some roff macros, for reference:
-.\" .nhdisable hyphenation
-.\" .hyenable hyphenation
-.\" .ad l  left justify
-.\" .ad b  justify to both left and right margins
-.\" .nfdisable filling
-.\" .fienable filling
-.\" .brinsert line break
-.\" .sp insert n+1 empty lines
-.\" for manpage-specific macros, see man(7)
-.SH NAME
-ogmrip \- An application to rip and encode DVD for GNOME
-.SH SYNOPSIS
-.B ogmrip
-OGMRip is an application and a set of libraries for ripping and encoding 
DVDinto AVI, OGM, MP4, or Matroska files  using a wide variety of codecs. It 
relies on mplayer, mencoder, ogmtools, mkvtoolnix, oggenc, lame, and faac to 
perform its tasks.
-.SH DESCRIPTION
-\fBogmrip\fP is an application and a set of libraries for ripping and encoding 
DVDinto AVI, OGM, MP4, or Matroska files  using a wide variety of codecs. It 
relies on mplayer, mencoder, ogmtools, mkvtoolnix, oggenc, lame, and faac to 
perform its tasks.
-Features :
-.TP
- transcodes from DVD or files
-.TP
- outputs OGM, AVI, MP4, or Matroska files
-.TP
- supports a lot of codecs (Vorbis, MP3, PCM, AC3, DTS, AAC, XviD, LAVC, X264, 
Theora)
-.TP
- calculates video bitrate for a given file size
-.TP
- autodetects cropping parameters and scaling factors
-.TP
- supports multiple audio and subtitles streams encoding
-.TP
- extracts subtitles in SRT or VobSub format
-.TP
- uses maximum quality codecs switches
-.TP
- rips contiguous chapters
-.TP
- supports external audio (PCM, MP3, AC3, DTS, AAC, Vorbis)
-.TP
- and subtitle (MicroDVD, SubRip, SRT, Sami, VPlayer, RT, SSA, PJS, MPSub, AQT, 
JacoSub, VobSub) files
-
-Complet user manuel available on the website of ogmrip : 
http://ogmrip.sourceforge.net/en/manual.html
-
-.SH AUTHOR
-ogmrip was written by Olivier Rolland 
-.PP
-This manual page was written by Julien Lavergne ,
-for the Debian project (but may be used by others).
diff -Nru ogmrip-1.0.1/debian/ogmrip.install ogmrip-1.0.1/debian/ogmrip.install
--- ogmrip-1.0.1/debian/ogmrip.install  2020-04-15 21:46:32.0 +0200
+++ ogmrip-1.0.1/debian/ogmrip.install  2023-05-09 18:35:29.0 +0200
@@ -1,7 +1,3 @@
-etc/gconf/schemas/ogmrip.schemas usr/share/gconf/schemas
 usr/bin
-usr/share/applications/ogmrip.desktop
 usr/share/locale
 usr/share/man/man1
-usr/share/ogmrip
-usr/share/pixmaps
diff -Nru 
ogmrip-1.0.1/debian/patches/prevent-failing-autoreconf-without-gconf.diff 
ogmrip-1.0.1/debian/patches/prevent-failing-autoreconf-without-gconf.diff
--- ogmrip-1.0.1/debian/patches/prevent-failing-autoreconf-without-gconf.diff   
1970-01-01 01:00:00.0 +0100
+++ ogmrip-1.0.1/debian/patches/prevent-failing-autoreconf

Processed: Re: Bug#1034836: initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - moreinfo
Bug #1034836 [cryptsetup-initramfs] initramfs-tools: After bullseye -> bookworm 
upgrade boot stuck in the initramfs shell
Removed tag(s) moreinfo.

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

Bug#1034836: initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell

[Guilhem Moulin]

Control: tag -1 - moreinfo

On Tue, 09 May 2023 at 18:39:33 +0200, Pásztor János wrote:
> I have attached the machine definition and already sent the vm images for
> you (via filesender.hu).

Many thanks!  Will have something to put teeth into once the images have
been downloaded :-)

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1034836: initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell

[Pásztor János]

Dear Guilhem,

On 2023-05-09 17:34, Guilhem Moulin wrote:

Control: tag -1 + unreproducible moreinfo

On Tue, 09 May 2023 at 17:10:03 +0200, Pásztor János wrote:

The machine and the disks are having two snapshots named 'good' and 'bad' so
it is easy to jump between the states.
I am willing to share with you the VM(disks + virsh dump) via a filesharing
service. Would you be interested in it?

Yes please; I still cannot reproduce the issue.



I have attached the machine definition and already sent the vm images 
for you (via filesender.hu).


You can restore the machine by following these steps:

- virsh define path/to/debian11.xml
- extract the contents of the repro.tar.gz file to '/var/lib/libvirt' 
(as root)

- systemctl restart libvirtd.service (so it re-reads the snapshot xmls)

After that you should be able to start the machine via virt-manager and 
see the snapshots as well. I have just tested this procedure on my machine.


The pw for luks and root are the same: 'titkos' (without the quotes)

Regards,
János Pásztor

p.s.: I think that if we solve this, then we solve also #1023716 For my 
eyes they look very similar...
  debian11
  3ed4a074-10f8-4272-9070-b7cf92707954
  
http://libosinfo.org/xmlns/libvirt/domain/1.0";>
  http://debian.org/debian/11"/>

  
  4192256
  4192256
  4
  
hvm

  
  



  
  
  



  
  destroy
  restart
  destroy
  


  
  
/usr/bin/qemu-system-x86_64

  
  
  
  


  
  
  
  


  
  
  
  


  



  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  


  


  


  
  
  
  


  

  


  


  
  


  
  


  




  
  


  



  
  


  


  


  


  /dev/urandom
  

  

Bug#1035713: marked as pending in google-android-installers

[bastif]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/google-android-tools-team/google-android-installers/-/commit/4b0e417e8e8692ec456ac950baad64e3fba30f71


Makefile: fix broken symbolic links (Closes: #1035713)

There are broken symbolic links in the ndk r23b package of Google.
This change will fix them. If there are still broken symbolic links, the user
is invited to send a bug report and the installation will stop.

During installation, when there are broken symbolic links, the installer will
output:

  Fixing broken symbolic links.
Replacing symbolic link: 
./toolchains/llvm/prebuilt/linux-x86_64/arm-linux-androideabi/bin/as
  Original target: 
/buildbot/src/android/ndk-release-r23/out/linux/android-ndk-r23b/toolchains/llvm/prebuilt/linux-x86_64/bin/arm-linux-androideabi-as
  New target: 
toolchains/llvm/prebuilt/linux-x86_64/bin/arm-linux-androideabi-as
Replacing symbolic link: 
./toolchains/llvm/prebuilt/linux-x86_64/x86_64-linux-android/bin/as
  Original target: 
/buildbot/src/android/ndk-release-r23/out/linux/android-ndk-r23b/toolchains/llvm/prebuilt/linux-x86_64/bin/x86_64-linux-android-as
  New target: 
toolchains/llvm/prebuilt/linux-x86_64/bin/x86_64-linux-android-as
Replacing symbolic link: 
./toolchains/llvm/prebuilt/linux-x86_64/aarch64-linux-android/bin/as
  Original target: 
/buildbot/src/android/ndk-release-r23/out/linux/android-ndk-r23b/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android-as
  New target: 
toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android-as
Replacing symbolic link: 
./toolchains/llvm/prebuilt/linux-x86_64/i686-linux-android/bin/as
  Original target: 
/buildbot/src/android/ndk-release-r23/out/linux/android-ndk-r23b/toolchains/llvm/prebuilt/linux-x86_64/bin/i686-linux-android-as
  New target: 
toolchains/llvm/prebuilt/linux-x86_64/bin/i686-linux-android-as


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1035713

Processed: Bug#1035713 marked as pending in google-android-installers

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1035713 [google-android-ndk-r23b-installer] 
google-android-ndk-r23b-installer: broken symlinks: 
/usr/lib/android-sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/linux-x86_64/*/bin/as
 -> /buildbot/src/android/...
Added tag(s) pending.

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

Bug#1035793: marked as done (retroarch-assets: missing Depends: fonts-droid-fallback)

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 16:03:31 +
with message-id 
and subject line Bug#1035793: fixed in retroarch-assets 1.7.6+git20221024+dfsg-3
has caused the Debian Bug report #1035793,
regarding retroarch-assets: missing Depends: fonts-droid-fallback
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.)


-- 
1035793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: retroarch-assets
Version: 1.7.6+git20221024+dfsg-2
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.

0m19.4s ERROR: FAIL: Broken symlinks:
  /usr/share/libretro/assets/pkg/chinese-font.ttf -> 
../../../fonts/truetype/droid/DroidSansFallbackFull.ttf (retroarch-assets)

Given that the package depends on various other fonts, this is very
likely a missing dependency.


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: retroarch-assets
Source-Version: 1.7.6+git20221024+dfsg-3
Done: Tobias Frost 

We believe that the bug you reported is fixed in the latest version of
retroarch-assets, 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.
Tobias Frost  (supplier of updated retroarch-assets 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, 09 May 2023 17:19:28 +0200
Source: retroarch-assets
Architecture: source
Version: 1.7.6+git20221024+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Tobias Frost 
Closes: 1035793
Changes:
 retroarch-assets (1.7.6+git20221024+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Add Depends: fonts-droid-fallback (Closes: #1035793)
Checksums-Sha1:
 a6895e875a955d478dd82d4cd52d899b7c0fcdff 2172 
retroarch-assets_1.7.6+git20221024+dfsg-3.dsc
 b3ab58ca2f3fd9aed416f1888be04ecef7fce534 18168 
retroarch-assets_1.7.6+git20221024+dfsg-3.debian.tar.xz
 da19023177b2c7df791246f78f588e7e02ffdbb2 11297 
retroarch-assets_1.7.6+git20221024+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 9e4b1b1fda5f07ab8a7b9f190429dc8d447118ab22611b00c9bac039161e3bf8 2172 
retroarch-assets_1.7.6+git20221024+dfsg-3.dsc
 3a1d6aa808e198e892bfa16ed3c5fa25f13531fbef4f7346ce32528941aa4279 18168 
retroarch-assets_1.7.6+git20221024+dfsg-3.debian.tar.xz
 3d3fc79380493635b1c3e0e886e99fdb781fde31834fc82f2038efa4a75b717c 11297 
retroarch-assets_1.7.6+git20221024+dfsg-3_amd64.buildinfo
Files:
 221df81823ac1bf16ce0f27f0663b58d 2172 otherosfs optional 
retroarch-assets_1.7.6+git20221024+dfsg-3.dsc
 a0ce1c3aa51086f2f69a8a86ad529223 18168 otherosfs optional 
retroarch-assets_1.7.6+git20221024+dfsg-3.debian.tar.xz
 6b1806cfc1d761c5dc5e8078e164a123 11297 otherosfs optional 
retroarch-assets_1.7.6+git20221024+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmRaZXcACgkQkWT6HRe9
XTZqPA//alRqL49bwF8Ns+vxMJPsampfXLrWuAYkafYoUssqkM35NEqGjjPTj2l6
BoQJbsxby4+1LJBfZMIjSlKnW9eXkBgldJSX7gJ7UVYuaBM2CzIf+Yg4Bq78GinN
CMZAyN7kkdg6YFNp8oD88mi1w/O5MKBHFvgBXP55Q8+sJAk1jLfHvxrYsFE2qXap
OA9i4UUEUgM6NHp94AviGFpdzg2muo7kOLTcKzE3SOqazORYkySqzniWvEMjYWB3
0bfpI3+mzKyafgmGYQ0/MKp05Feekh2X60vs33lE8ZPBicaaaT3wxRr5D0kkgFlg
uTYqwSSPcQEGGsNr+sJ4fT58tFCwDqS07QQOKMpukVfZma/TWU2hsuz3wTsfCwJM
8iVj6sCp+7hLGdCc0AuUiTzN6Hxpu3gbTRqafN/PIJWj3mNhinD+pEjxnbFa9rE5
bDgO0aOP/zAOYfliGBruw6eEh5JaQxIlY4x/dj5AjzO2qaLg5wpgI+IbP4Pgxk6I
uKw88se6TytscMNCebjP4qLiJTOrZc1+mN/PN0p0jp5gaRAndN/g2dl44nVIgeNn
qIXB7w77C4ulBRFy0p/Kiq6ItUxpG7npB7KIw3dT6bZir+9xNu4oh9EO7n12iqd8
0rP4I/MZ1ZT/aLlb7a5vRUA36CjUVPHHVQKVKckYvTlHsFPhfqU=
=NiBK
-END PGP SIGNATURE End Message ---

Bug#1035543: init-system-helpers: bla bla

[Michael Biebl]

On Fri, 5 May 2023 13:38:52 +0200 Michael Biebl  wrote:

Am 05.05.23 um 11:14 schrieb Luca Boccassi:
> On Fri, 05 May 2023 11:04:29 +0200 Andreas Beckmann 

>> This is a new systemd unit in package e2fsprogs.

It's not, both bullseye and bookworm ship this file in e2fsprogs. The 
difference is this


bullseye:
cat /lib/systemd/system/e2scrub_reap.service | tail -n 2
[Install]
WantedBy=default.target

bookworm
# cat /lib/systemd/system/e2scrub_reap.service | tail -n 2
[Install]
WantedBy=multi-user.target


I.e. it changed the target from default.target to multi-user.target.
i-s-h does not have support for removing obsolete enablement symlinks in 
such a case.




Andreas, you filed this with RC severity with the justification that 
systemd units are not enabled. I don't see that, so could you please 
clarify.


What I could find out so far is the change of WantedBy target not being 
properly cleaned up on upgrades, but that doesn't strike me as RC (and 
would need to be done in e2fsprogs)



Michael




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034836: initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell

[Guilhem Moulin]

Control: tag -1 + unreproducible moreinfo

On Tue, 09 May 2023 at 17:10:03 +0200, Pásztor János wrote:
> The machine and the disks are having two snapshots named 'good' and 'bad' so
> it is easy to jump between the states.
> I am willing to share with you the VM(disks + virsh dump) via a filesharing
> service. Would you be interested in it?

Yes please; I still cannot reproduce the issue.

-- 
Guilhem.


signature.asc
Description: PGP signature

Processed: Re: Bug#1034836: initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + unreproducible moreinfo
Bug #1034836 [cryptsetup-initramfs] initramfs-tools: After bullseye -> bookworm 
upgrade boot stuck in the initramfs shell
Added tag(s) moreinfo and unreproducible.

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

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

[Andreas Beckmann]

On 09/05/2023 16.55, Helmut Grohne wrote:

9base/bookworm no longer does, because it now uses dpkg-triggers to


Good to know that there is a better way nowadays ...


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

0m45.2s ERROR: FAIL: After purging files have been modified:
   /etc/shells   not owned


You should look closer:

0m45.2s DEBUG: Modified(user, group, mode, size, target): /etc/shells 
expected(root, root, - 100644, 128, None) != found(root, root, - 100644, 140, 
None)

It's a 12 byte difference. That's not 9base's entries. What you see here
is "/usr/bin/sh\n". So this is a /usr-merge bug. We already know it.
Thus force-merging.


Given that this seems to be the only package showing this behavior in my 
bullseye2bookworm tests so far, I didn' expect some "systematic" error 
outside of this package.



Andreas

Bug#1034836: {Spam?} Bug#1034836: {Spam?} Bug#1034836: initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell

[Pásztor János]

Control: tag -1 - unreproducible - moreinfo

Dear Dennis,

On 2023-05-05 18:10, Dennis Filder wrote:

X-Debbugs-CC: Pásztor János 

On Wed, May 03, 2023 at 11:20:07PM +0200, Pásztor János wrote:

I have checked #902943 and the fine print from
/usr/share/doc/cryptsetup-initramfs/README.initramfs.gz
Based on that I have made an attempt to replace the UUIDs with
`traditional` disk device paths.

[...]

However this fails spectacularly, as during the boot process the
ordering is not stable, sometimes it is sdb1 or sda1 instead of sdc1
:/

If your device order is not stable during boot you need to use
PARTUUID instead of UUID.  You might argue that you should be able to
use UUID because it worked before Bookworm if you overwrote the
crypttab.  However, it might be that your LUKS containers were created
with an old version of cryptsetup that did not wipe the start of the
partition properly.  libblkid has had "behavioural changes" in the
past under such circumstances wrt. to block device probing and making
decisions [1].  It might be that whatever component is used to create
/dev/disk/by-* symlinks in the initramfs has changed behaviour, too.
According to your initramfs.debug log it's systemd-udevd.

 + /scripts/init-top/udev
 Starting systemd-udevd version 252.6-1

You'd have to try to get access to its log output.

You should also take copies of the first 1 MiB of your partitions that
hold the LUKS containers so libblkid (or whatever the culprit) can be
debugged with before you overwrite anything.  You'll have to provide
copies of some sort if you want someone else to debug this for you --
no idea how to sanitize/dekey them.  "cryptsetup luksErase" might
render the LUKS header unrecognizable.  You'll have to try it out.

If you feel like it you can investigate further with:

   LIBBLKID_DEBUG=all blkid -p
   lsblk -o NAME,SIZE,TYPE,UUID,PARTUUID

The next-heavier cannons would be ltrace/strace and gdb.



I think that we can let that option(libblkid changes) go, as I have 
managed to reproduce this issue in a virtual machine, freshly installed 
from `firmware-11.7.0-amd64-netinst.iso`


With that we have get rid of:
- the possible fallout from the history of my old install
- the underlying hw dependencies

The big lesson what I have learned from it that you need to install and 
enable plymouth to have the magic password sharing between the LUKS 
devices. If you do not have that, then it will ask the pw twice (on 
bullseye) but besides that it boots properly


The machine and the disks are having two snapshots named 'good' and 
'bad' so it is easy to jump between the states.
I am willing to share with you the VM(disks + virsh dump) via a 
filesharing service. Would you be interested in it?


Regards,
János Pásztor

Processed: Re: {Spam?} Bug#1034836: {Spam?} Bug#1034836: initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - unreproducible - moreinfo
Bug #1034836 [cryptsetup-initramfs] initramfs-tools: After bullseye -> bookworm 
upgrade boot stuck in the initramfs shell
Removed tag(s) unreproducible.
Bug #1034836 [cryptsetup-initramfs] initramfs-tools: After bullseye -> bookworm 
upgrade boot stuck in the initramfs shell
Removed tag(s) moreinfo.

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

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

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 14:59:09 +
with message-id 
and subject line Bug#1035774: Removed package(s) from unstable
has caused the Debian Bug report #998988,
regarding dbmix: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 0.9.8-8+rm

Dear submitter,

as the package dbmix has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1035774

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 14:58:04 +
with message-id 
and subject line Bug#1035755: Removed package(s) from unstable
has caused the Debian Bug report #998989,
regarding gbase: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 0.5-2.2+rm

Dear submitter,

as the package gbase has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1035755

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 14:58:04 +
with message-id 
and subject line Bug#1035755: Removed package(s) from unstable
has caused the Debian Bug report #965536,
regarding gbase: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 0.5-2.2+rm

Dear submitter,

as the package gbase has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1035755

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 14:59:09 +
with message-id 
and subject line Bug#1035774: Removed package(s) from unstable
has caused the Debian Bug report #965490,
regarding dbmix: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 0.9.8-8+rm

Dear submitter,

as the package dbmix has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1035774

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#978237: marked as done (xfce4-equake-plugin: FTBFS: build-dependency not installable: xfce4-panel (= 4.14.4-1))

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 14:56:51 +
with message-id 
and subject line Bug#1035752: Removed package(s) from unstable
has caused the Debian Bug report #978237,
regarding xfce4-equake-plugin: FTBFS: build-dependency not installable: 
xfce4-panel (= 4.14.4-1)
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.)


-- 
978237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-equake-plugin
Version: 1.3.8.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: autotools-dev, debhelper (>= 9.0.0), intltool, 
> libcurl4-gnutls-dev, libatk1.0-dev, libcairo2-dev, libfontconfig1-dev, 
> libfreetype6-dev, libgdk-pixbuf2.0-dev, libglib2.0-dev, libgtk2.0-dev, 
> libpango1.0-dev, libxfce4ui-1-dev, libxfce4util-dev, xfce4-panel-dev, 
> build-essential, fakeroot
> Filtered Build-Depends: autotools-dev, debhelper (>= 9.0.0), intltool, 
> libcurl4-gnutls-dev, libatk1.0-dev, libcairo2-dev, libfontconfig1-dev, 
> libfreetype6-dev, libgdk-pixbuf2.0-dev, libglib2.0-dev, libgtk2.0-dev, 
> libpango1.0-dev, libxfce4ui-1-dev, libxfce4util-dev, xfce4-panel-dev, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [461 B]
> Get:5 copy:/<>/apt_archive ./ Packages [552 B]
> Fetched 1970 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  xfce4-panel-dev : Depends: xfce4-panel (= 4.14.4-1) but it is not going to 
> be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://qa-logs.debian.net/2020/12/26/xfce4-equake-plugin_1.3.8.1-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 1.3.8.1-2+rm

Dear submitter,

as the package xfce4-equake-plugin has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1035752

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed (with 2 errors): Re: Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 1033167 -1
Bug #1033167 [usrmerge] usrmerge: messes with /etc/shells
Unable to merge bugs because:
package of #1035820 is '9base' not 'usrmerge'
Failed to forcibly merge 1033167: Did not alter merged bugs.

> affects 1033167 + 9base
Failed to mark 1033167 as affecting package(s): failed to get lock on 
/srv/bugs.debian.org/spool/lock/1033167 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/1033167 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.


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

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

[Helmut Grohne]

Control: forcemerge 1033167 -1 
Control: affects 1033167 + 9base

Hi Andreas,

On Tue, May 09, 2023 at 04:39:21PM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package leaves modifications
> in /etc/shells after upgrading from bullseye to bookworm and purging the
> package.
> 
> 9base/bullseye called add-shell/remove-shell in its postinst/postrm.
> 9base/bookworm no longer does that, but it also does not clean up the
> leftover entries from bullseye in its postinst.

9base/bookworm no longer does, because it now uses dpkg-triggers to
perform the cleanup. It actually does clean up its entries.

> >From the attached log (scroll to the bottom...):
> 
> 0m45.2s ERROR: FAIL: After purging files have been modified:
>   /etc/shells  not owned

You should look closer:

0m45.2s DEBUG: Modified(user, group, mode, size, target): /etc/shells 
expected(root, root, - 100644, 128, None) != found(root, root, - 100644, 140, 
None)

It's a 12 byte difference. That's not 9base's entries. What you see here
is "/usr/bin/sh\n". So this is a /usr-merge bug. We already know it.
Thus force-merging.

> The following (untested) snippet for the postinst should perform the
> neccessary cleanup:
> 
> if [ "$1" = "install" ] || [ "$1" = "upgrade" ]; then
> if dpkg --compare-versions "$2" lt-nl "1:6-14~" ; then
> remove-shell /bin/rc
> remove-shell /usr/lib/plan9/bin/rc
> fi
> fi

No. Please continue to use the declarative approach.

Helmut

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

[Andreas Beckmann]

Package: 9base
Version: 1:6-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package leaves modifications
in /etc/shells after upgrading from bullseye to bookworm and purging the
package.

9base/bullseye called add-shell/remove-shell in its postinst/postrm.
9base/bookworm no longer does that, but it also does not clean up the
leftover entries from bullseye in its postinst.

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

0m45.2s ERROR: FAIL: After purging files have been modified:
  /etc/shellsnot owned


The following (untested) snippet for the postinst should perform the
neccessary cleanup:

if [ "$1" = "install" ] || [ "$1" = "upgrade" ]; then
if dpkg --compare-versions "$2" lt-nl "1:6-14~" ; then
remove-shell /bin/rc
remove-shell /usr/lib/plan9/bin/rc
fi
fi


cheers,

Andreas


9base_1:6-13.log.gz
Description: application/gzip

Bug#1034443: marked as done (python3-brial: uninstallable on arcitectures where sagemath is unavailable, breaks building of singular)

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 14:33:51 +
with message-id 
and subject line Bug#1034443: fixed in brial 1.2.11-2.1
has caused the Debian Bug report #1034443,
regarding python3-brial: uninstallable on arcitectures where sagemath is 
unavailable, breaks building of singular
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.)


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

Package: python3-brial
Version: 1.2.11-2
Severity: serious
X-debbugs-cc: singu...@packages.debian.org

python3-brial recently added a dependency on python3-sage, however python3-sage
is only available on amd64, arm64, i386 and riscv64.

This also means that the build-depends of singular on those architectures are
unsatisfied.

Strangely, when I look at the singular build log the only mentions of brial
I see are in the Debian packaging steps, I don't see any mentions of it from
the upstream build system. Grepping for brial in the polybori source doesn't
reveal anything outside the debian dir either. I maintain a downstream
distribution and, after removing the build-dependency, was able to build
singular there without having any brial related packages installed.

So assuming the dependency on python3-sage is real and unavoidable what I
think needs to happen to get things back in a consistent state is.

* The architecture list of python3-brial needs to be limited to architectures
  where python3-sage is available.
* The build-dependency of singular on python3-brial needs to be either
  removed or limited to architectures where python3-sage is available
* Removal of the old python3-brial packages needs to be requested.
--- End Message ---
--- Begin Message ---
Source: brial
Source-Version: 1.2.11-2.1
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
brial, 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 brial 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, 09 May 2023 13:27:51 +
Source: brial
Architecture: source
Version: 1.2.11-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Peter Michael Green 
Closes: 1034443
Changes:
 brial (1.2.11-2.1) unstable; urgency=medium
 .
   * Non-Maintainer upload.
   * Limit architectures for python3-brial package  to architectures where
 sagemath is available (Closes: #1034443).
Checksums-Sha1:
 1706ff6d379ed0e84ee2c313ffcb45837d7677ed 2444 brial_1.2.11-2.1.dsc
 674845aabf92824b12e73538851300b9804018cb 7904 brial_1.2.11-2.1.debian.tar.xz
 a930667021b263350fc236efc549b69760b7aca9 9716 brial_1.2.11-2.1_source.buildinfo
Checksums-Sha256:
 8dc6510e62f30377f2b7d67824bb9e7370164c056d46affdb102f9ae37a977f7 2444 
brial_1.2.11-2.1.dsc
 396dc9a721f2bcd73af386a1086a481cb1e4f01fa0eca7048266921c3f59e2b4 7904 
brial_1.2.11-2.1.debian.tar.xz
 d2e6d48a64e6946a75cb40e8520342dc338b68b31551a80d2bdb479989065315 9716 
brial_1.2.11-2.1_source.buildinfo
Files:
 1fda843148adea6f81f0aaaffa14a965 2444 math optional brial_1.2.11-2.1.dsc
 414108af739193cf81fbc65e4de5ba46 7904 math optional 
brial_1.2.11-2.1.debian.tar.xz
 d8b0d78ba15b713284c6189f102c3250 9716 math optional 
brial_1.2.11-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmRaU3kUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsJBg//Y5P4ZxiJ2ILpjgmDbsfw8uuFZERl
JI9PjTbYJFlv1HVQxulNt6n2tbfn/kCD2WasyPui04D8CNM2g7d5ZGAjj0rCpu67
Sb4Q/KkMXfgCtDcfnd72ByN9YIHXxXhktDwWGH0xjyh/uqYLsHW/b1/g/BE4lsNI
+u/0+ohbmGdcQ0h9MWUel12HGLHWvu9TXicZMoaEdFMdNhs9AtihU8Dousqo1GXI
uxCemF3c4a2zLX2KG0zvRwKFoxU8nraORBIswWJns6JaWvaNm614jpZKLuAXrt3d
TEVyL7acAFqHyrIHA5bUwigBwowepph/egHiVAYS1YyexF/FTyE+zFXlS8j5PuCP
92SD57ZGh7s5ZHhtraPVjgWSkRKYUsNz22mfxo59tzgXOBv8KV0KDtf5UzwEha0Z
75dlizIx/WLm1LNqMc9+G39zW/Gmryfq4nv96UpDhsFQW6t5Lqd+5z5FTli3vVaI
vszW6Qp9aSp+cbz3O9ESJNWsSWh2EBZwbYlW0gqyqv1VYf1oAlAvQQ/iqiGStPWJ
TdeSXgNVO8OoBGpaLLN1ZchhZZEHRStWG1CZkoeF1SJ+elesHuPZeE/J1CJtXp/D
PrtMA3xVXx

Processed: tagging 1035793

[Debian Bug Tracking System]

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

> tags 1035793 + pending
Bug #1035793 [retroarch-assets] retroarch-assets: missing Depends: 
fonts-droid-fallback
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1029201: openbox-menu: do not release with bookworm

[Bastian Germann]

On Thu, 19 Jan 2023 15:17:26 +0100 mat...@linuxmint.pl wrote:

openbox-menu should not be shipped in bookworm.

Will you also file a RM bug or are you going to update the package for later 
releases?

Bug#1035780: marked as done (jed-common: Fails to upgrade: unable to install new version of '/usr/share/jed/doc/txt/abbrev.txt': No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 09 May 2023 12:18:51 +
with message-id 
and subject line Bug#1035780: fixed in jed 1:0.99.20~pre.178+dfsg-3
has caused the Debian Bug report #1035780,
regarding jed-common: Fails to upgrade: unable to install new version of 
'/usr/share/jed/doc/txt/abbrev.txt': No such file or directory
to be marked as done.

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

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


-- 
1035780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jed-common
Version: 1:0.99.20~pre.178+dfsg-2
Severity: serious

jed-common fails to upgrade from 1:0.99.20~pre.178+dfsg-1 to
1:0.99.20~pre.178+dfsg-2 for me as follows:

Preparing to unpack .../4-jed-common_1%3a0.99.20~pre.178+dfsg-2_all.deb ...
Unpacking jed-common (1:0.99.20~pre.178+dfsg-2) over (1:0.99.20~pre.178+dfsg-1) 
...
dpkg: error processing archive 
/tmp/apt-dpkg-install-OeNOOg/4-jed-common_1%3a0.99.20~pre.178+dfsg-2_all.deb 
(--unpack):
 unable to install new version of '/usr/share/jed/doc/txt/abbrev.txt': No such 
file or directory
[…]
dpkg: dependency problems prevent configuration of jed:
 jed depends on jed-common (= 1:0.99.20~pre.178+dfsg-2); however:
  Version of jed-common on system is 1:0.99.20~pre.178+dfsg-1.

dpkg: error processing package jed (--configure):
 dependency problems - leaving unconfigured
[…]
Errors were encountered while processing:
 jed

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'testing-security'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 
'experimental-debug'), (1, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages jed-common depends on:
ii  slsh  2.3.3-3

jed-common recommends no packages.

Versions of packages jed-common suggests:
ii  emacs-gtk [info-browser]  1:28.2+1-14
ii  info [info-browser]   6.8-6+b1
iu  jed [info-browser]1:0.99.20~pre.178+dfsg-2
ii  konqueror [info-browser]  4:22.12.3-1
ii  pinfo [info-browser]  0.6.13-1.3

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/doc/jed-common/changelog.Debian.gz (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/abbrev.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/color.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/compile.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/dfa.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/edt.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/emacs.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/filelock.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/fold.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/hooks.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/ide-mode.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/jed_faq.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/linux-keys.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/menus.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/mouse.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/pc-keys.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/program.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/recentx.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/rgrep.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/rmail.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/script.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/sessions.txt (from 
jed-common package)
debsums: missing file /usr/share/doc/jed-common/txt/syntax.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/txt/undo.txt (from jed-common 
package)
debsums: missing file /usr/share/doc/jed-common/

Bug#1035805: node-source-map: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: node-source-map
Version: 0.7.0++dfsg2+really.0.6.1-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  bullseye -> bookworm

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

0m39.3s ERROR: WARN: Inadequate results from running adequate!
  node-source-map: broken-symlink /usr/share/doc/node-source-map -> 
../libjs-source-map
  node-source-map: missing-copyright-file 
/usr/share/doc/node-source-map/copyright
  
  MISSING COPYRIGHT FILE: /usr/share/doc/node-source-map/copyright
  # ls -lad /usr/share/doc/node-source-map
  lrwxrwxrwx 1 root root 19 May  3 22:16 /usr/share/doc/node-source-map -> 
../libjs-source-map
  # ls -la /usr/share/doc/node-source-map/
  ls: cannot access '/usr/share/doc/node-source-map/': No such file or directory


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


node-source-map_0.7.0++dfsg2+really.0.6.1-13.log.gz
Description: application/gzip

Processed: tagging 1033258

[Debian Bug Tracking System]

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

> tags 1033258 + pending
Bug #1033258 [src:upx-ucl] upx-ucl: CVE-2023-23456
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 1031874

[Debian Bug Tracking System]

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

> tags 1031874 + pending
Bug #1031874 [src:upx-ucl] upx-ucl: CVE-2023-23457
Ignoring request to alter tags of bug #1031874 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: Bug#1035598 marked as pending in kanboard

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1035598 [kanboard] /var/lib/dpkg/info/kanboard.postinst: 24: 
lighty-enable-mod: not found
Added tag(s) pending.

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

Bug#1035598: marked as pending in kanboard

[Joseph Nahmias]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/kanboard/-/commit/cb7665c9d47bcda87f3579c5242c467372f36afc


properly test for lighty-enable-mod

This fixes a bug in how the postinst/prerm maint scripts check whether to
enable kanboard for lighttpd, which caused it to fail when lighttpd was not
installed.

Closes: #1035598


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1035598

Processed: user debian...@lists.debian.org ...

[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 1035713 google-android-ndk-r23b-installer/23.1.7779620+1675172737
Bug #1035713 [google-android-ndk-r23b-installer] 
google-android-ndk-r23b-installer: broken symlinks: 
/usr/lib/android-sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/linux-x86_64/*/bin/as
 -> /buildbot/src/android/...
The source google-android-ndk-r23b-installer and version 
23.1.7779620+1675172737 do not appear to match any binary packages
Marked as found in versions 
google-android-ndk-r23b-installer/23.1.7779620+1675172737.
> thanks
Stopping processing here.

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

Bug#1034694: gnome-core: Cannot install due to pipewire-audio dependency

[Jochen Sprickerhof]

Hi Witold,

The friendly people in #debian-apt proposed to run:

sudo apt install -o Debug::pkgProblemResolver=true -o 
Debug::pkgDepCache::Marker=1 -o Debug::pkgDepCache::AutoInstall=1 gnome-core

And could you also send your /var/lib/dpkg/status file?

More information on this:

https://salsa.debian.org/apt-team/apt#debugging

Thanks!

Jochen

* Witold Baryluk  [2023-05-08 19:02]:

Package: gnome-core
Version: 1:43+1
Followup-For: Bug #1034694
X-Debbugs-Cc: witold.bary...@gmail.com

Here:

root@debian:~# sudo apt -V --simulate remove pulseaudio
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  bind9-host (1:9.18.12-1)
  bind9-libs (1:9.18.12-1)
  libfstrm0 (0.6.1-1)
  libjemalloc2 (5.3.0-1)
  libmaxminddb0 (1.7.1-1)
  libprotobuf-c1 (1.4.1-1+b1)
  libuv1 (1.44.2-1)
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  liblua5.3-0 (5.3.6-2)
  libpipewire-0.3-modules (0.3.65-3)
  libwireplumber-0.4-0 (0.4.13-1)
  pipewire (0.3.65-3)
  pipewire-bin (0.3.65-3)
  pipewire-pulse (0.3.65-3)
  wireplumber (0.4.13-1)
Suggested packages:
  libspa-0.2-bluetooth (0.3.65-3)
  wireplumber-doc (0.4.13-1)
The following packages will be REMOVED:
  libcanberra-pulse (0.30-10)
  pulseaudio (16.1+dfsg1-2+b1)
The following NEW packages will be installed:
  liblua5.3-0 (5.3.6-2)
  libpipewire-0.3-modules (0.3.65-3)
  libwireplumber-0.4-0 (0.4.13-1)
  pipewire (0.3.65-3)
  pipewire-bin (0.3.65-3)
  pipewire-pulse (0.3.65-3)
  wireplumber (0.4.13-1)
0 upgraded, 7 newly installed, 2 to remove and 0 not upgraded.
Remv libcanberra-pulse [0.30-10]
Remv pulseaudio [16.1+dfsg1-2+b1]
Inst liblua5.3-0 (5.3.6-2 Debian:testing [amd64])
Inst libpipewire-0.3-modules (0.3.65-3 Debian:testing [amd64])
Inst libwireplumber-0.4-0 (0.4.13-1 Debian:testing [amd64])
Inst pipewire-bin (0.3.65-3 Debian:testing [amd64])
Inst pipewire (0.3.65-3 Debian:testing [amd64])
Inst pipewire-pulse (0.3.65-3 Debian:testing [amd64])
Inst wireplumber (0.4.13-1 Debian:testing [amd64])
Conf liblua5.3-0 (5.3.6-2 Debian:testing [amd64])
Conf libpipewire-0.3-modules (0.3.65-3 Debian:testing [amd64])
Conf libwireplumber-0.4-0 (0.4.13-1 Debian:testing [amd64])
Conf pipewire-bin (0.3.65-3 Debian:testing [amd64])
Conf pipewire (0.3.65-3 Debian:testing [amd64])
Conf pipewire-pulse (0.3.65-3 Debian:testing [amd64])
Conf wireplumber (0.4.13-1 Debian:testing [amd64])
root@debian:~#


Regards,
Witold


signature.asc
Description: PGP signature

Bug#1035798: libphp8.2-embed: does not ship SONAME link /usr/lib/libphp.so -> libphp8.2.so

[Andreas Beckmann]

Package: libphp8.2-embed
Version: 8.2.5-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package does not ship the
SONAME link for its library (Policy 8.1).
That link got created later by ldconfig.

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

0m23.8s DEBUG: Starting command: ['nsenter', 
'--net=/run/netns/piuparts-netns-5', 
'--uts=/srv/piuparts/tmp/tmpveqX9D/ns-uts', 'chroot', 
'/srv/piuparts/tmp/tmpveqX9D/chroot', 
'tmp/scripts/pre_remove_40_find_unowned_lib_links']
0m24.4s DUMP:
  UNOWNED SYMLINK /usr/lib/libphp.so -> libphp8.2.so
0m24.4s DEBUG: Command ok: ['nsenter', '--net=/run/netns/piuparts-netns-5', 
'--uts=/srv/piuparts/tmp/tmpveqX9D/ns-uts', 'chroot', 
'/srv/piuparts/tmp/tmpveqX9D/chroot', 
'tmp/scripts/pre_remove_40_find_unowned_lib_links']

After removal of the package a broken symlink remains:

0m29.6s ERROR: FAIL: Broken symlinks:
  /usr/lib/libphp.so -> libphp8.2.so


Andreas


libphp8.2-embed_8.2.5-2.log.gz
Description: application/gzip

Bug#1035795: libricohcamerasdk: does not ship SONAME link /usr/lib//libRicohCameraSDKCpp.so -> libRicohCameraSDKCpp.so.1.1.0

[Andreas Beckmann]

Package: libricohcamerasdk
Version: 1.1.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package does not ship the
SONAME link for its library (Policy 8.1).
That link got created later by ldconfig.

The SONAME of this library is, well, unusual. But there is probably
nothing we can do about it as it resides in non-free.

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

0m20.4s DEBUG: Starting command: ['nsenter', 
'--net=/run/netns/piuparts-netns-9', 
'--uts=/srv/piuparts/tmp/tmpTP2K8k/ns-uts', 'chroot', 
'/srv/piuparts/tmp/tmpTP2K8k/chroot', 
'tmp/scripts/pre_remove_40_find_unowned_lib_links']
0m21.1s DUMP:
  UNOWNED SYMLINK /usr/lib/x86_64-linux-gnu/libRicohCameraSDKCpp.so -> 
libRicohCameraSDKCpp.so.1.1.0
0m21.1s DEBUG: Command ok: ['nsenter', '--net=/run/netns/piuparts-netns-9', 
'--uts=/srv/piuparts/tmp/tmpTP2K8k/ns-uts', 'chroot', 
'/srv/piuparts/tmp/tmpTP2K8k/chroot', 
'tmp/scripts/pre_remove_40_find_unowned_lib_links']

After removal of the package a broken symlink remains:

0m24.4s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libRicohCameraSDKCpp.so -> 
libRicohCameraSDKCpp.so.1.1.0


libRicohCameraSDKCpp.so is probably part of the -dev package, so you
need to remove it from there and add
  Breaks+Replaces: libricohcamerasdk-dev (<< 1.1.0-4~)


Andreas


libricohcamerasdk_1.1.0-3.log.gz
Description: application/gzip

Bug#967144: marked as done (gpaint: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 9 May 2023 12:15:42 +0200
with message-id 
and subject line Re: closing as invalid
has caused the Debian Bug report #967144,
regarding gpaint: Unversioned Python removal in sid/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.)


-- 
967144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gpaint
Version: 0.3.3-6.1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---

On Fri, 5 Mar 2021 11:12:05 +0100 Matthias Klose  wrote:

closing as invalid, no direct python dependency


Really closing now.--- End Message ---

Bug#1034443: python3-brial: uninstallable on arcitectures where sagemath is unavailable

[Tobias Hansen]

On 5/8/23 21:22, Paul Gevers wrote:

Hi Tobias,

On Sat,  6 May 2023 10:24:41 + Tobias Hansen  wrote:


Note that we could also just remove python3-sage and the autopkgtest.


I assume you mean python3-brial here.


Yes indeed.





Nothing in Debian depends on it


Not true (and it's too late in the freeze to do that [1]):
paul@mulciber ~ $ reverse-depends python3-brial
Reverse-Recommends
==
* science-mathematics-dev
* singular-data 



I see. I checked with dak [1] and those were not shown, maybe because they are 
recommends and not depends.

Anyway, I'm fine with the proposed NMU.

Best,

Tobias

[1] https://wiki.debian.org/ftpmaster_Removals

Bug#1035793: retroarch-assets: missing Depends: fonts-droid-fallback

[Andreas Beckmann]

Package: retroarch-assets
Version: 1.7.6+git20221024+dfsg-2
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.

0m19.4s ERROR: FAIL: Broken symlinks:
  /usr/share/libretro/assets/pkg/chinese-font.ttf -> 
../../../fonts/truetype/droid/DroidSansFallbackFull.ttf (retroarch-assets)

Given that the package depends on various other fonts, this is very
likely a missing dependency.


cheers,

Andreas

Bug#1035792: qt6-charts-dev: Missing dependecy on qml6-module-qtcharts

[Christian Marillat]

Package: qt6-charts-dev
Version: 6.4.2-2
Severity: serious

Dear Maintainer,

When trying to build pyside6 I see :

,
| CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Qt6Qml/QmlPlugins/Qt6qtchartsqml2Targets.cmake:96
 (message):
|   The imported target "Qt6::qtchartsqml2" references the file
| 
|  "/usr/lib/x86_64-linux-gnu/qt6/qml/QtCharts/libqtchartsqml2plugin.so"
| 
|   but this file does not exist.  Possible reasons include:
| 
|   * The file was deleted, renamed, or moved to another location.
| 
|   * An install or uninstall procedure did not complete successfully.
| 
|   * The installation package was faulty and contained
| 
|  
"/usr/lib/x86_64-linux-gnu/cmake/Qt6Qml/QmlPlugins/Qt6qtchartsqml2Targets.cmake"
| 
|   but not all the files it references
`

Christian


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

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

Versions of packages qt6-charts-dev depends on:
ii  libqt6charts6 6.4.2-2
ii  libqt6chartsqml6  6.4.2-2
ii  qt6-base-dev  6.4.2+dfsg-7

qt6-charts-dev recommends no packages.

qt6-charts-dev suggests no packages.

-- no debconf information

Bug#1035791: qt6-datavisualization-dev: Missing dependency on qml6-module-qtdatavisualization

[Christian Marillat]

Package: qt6-datavisualization-dev
Version: 6.4.2-2
Severity: serious

Dear Maintainer,

When trying toi build pyside6 I see :

,
| CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Qt6Qml/QmlPlugins/Qt6DataVisualizationQmlpluginTargets.cmake:96
 (message):
|   The imported target "Qt6::DataVisualizationQmlplugin" references the file
| 
|  
"/usr/lib/x86_64-linux-gnu/qt6/qml/QtDataVisualization/libdatavisualizationqmlplugin.so"
| 
|   but this file does not exist.  Possible reasons include:
| 
|   * The file was deleted, renamed, or moved to another location.
| 
|   * An install or uninstall procedure did not complete successfully.
| 
|   * The installation package was faulty and contained
| 
|  
"/usr/lib/x86_64-linux-gnu/cmake/Qt6Qml/QmlPlugins/Qt6DataVisualizationQmlpluginTargets.cmake"
| 
|   but not all the files it references.
`

Christian


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

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

Versions of packages qt6-datavisualization-dev depends on:
ii  libqt6datavisualization6 6.4.2-2
ii  libqt6datavisualizationqml6  6.4.2-2
ii  qt6-base-dev 6.4.2+dfsg-7

qt6-datavisualization-dev recommends no packages.

qt6-datavisualization-dev suggests no packages.

-- no debconf information

Processed: user debian...@lists.debian.org, usertagging 1012464, affects 1012464, affects 1013153 ...

[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 1012464 piuparts
Usertags were: piuparts edos-uninstallable.
Usertags are now: piuparts edos-uninstallable.
> affects 1012464 + libvtk6-dev
Bug #1012464 [libvtk6.3] libvtk6.3: not installable in sid
Added indication that 1012464 affects libvtk6-dev
> affects 1013153 + camitk-actionstatemachine camitk-imp camitk-config
Bug #1013153 [camitk] camitk: vtk[6,7] removal
Added indication that 1013153 affects camitk-actionstatemachine, camitk-imp, 
and camitk-config
> found 1020284 1:2.40.1-1
Bug #1020284 [git-daemon-run] git-daemon-run: fails to purge: deluser -f:  
Unknown option: f
Marked as found in versions git/1:2.40.1-1.
> severity 1020284 serious
Bug #1020284 [git-daemon-run] git-daemon-run: fails to purge: deluser -f:  
Unknown option: f
Severity set to 'serious' from 'important'
> affects 1035282 + live-task-non-free-firmware-pc
Bug #1035282 {Done: Salvatore Bonaccorso } 
[firmware-brcm80211] firmware-brcm80211: broken symlinks: 
/lib/firmware/brcm/brcmfmac4356-sdio.*,*.txt -> brcmfmac4356-sdio.AP6356S.txt
Added indication that 1035282 affects live-task-non-free-firmware-pc
> notfixed 1035696 5.5.7+dfsg-1
Bug #1035696 [cpl-plugin-fors-calib] cpl-plugin-fors-calib: 
fors-kit-5.5.6*.tar.gz is no longer downloadable
No longer marked as fixed in versions cpl-plugin-fors/5.5.7+dfsg-1.
> found 1035696 5.5.7+dfsg-2
Bug #1035696 [cpl-plugin-fors-calib] cpl-plugin-fors-calib: 
fors-kit-5.5.6*.tar.gz is no longer downloadable
Marked as found in versions cpl-plugin-fors/5.5.7+dfsg-2.
> thanks
Stopping processing here.

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

Bug#1035786: cpl-plugin-xshoo-calib: xshoo-kit-3.5.3*.tar.gz is no longer downloadable

[Andreas Beckmann]

Package: cpl-plugin-xshoo-calib
Version: 3.5.3+dfsg-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 cpl-plugin-xshoo-calib (3.5.3+dfsg-1) ...
  --2023-05-08 00:49:57--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.5.3.tar.gz
  Connecting to 10.99.5.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-05-08 00:49:57 ERROR 404: Not Found.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-05-08 00:49:57--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.5.3-1.tar.gz
  Connecting to 10.99.5.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-05-08 00:49:58 ERROR 404: Not Found.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-05-08 00:49:58--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.5.3-2.tar.gz
  Connecting to 10.99.5.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-05-08 00:49:58 ERROR 404: Not Found.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-05-08 00:49:58--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.5.3-3.tar.gz
  Connecting to 10.99.5.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-05-08 00:49:59 ERROR 404: Not Found.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-05-08 00:49:59--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.5.3-4.tar.gz
  Connecting to 10.99.5.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-05-08 00:49:59 ERROR 404: Not Found.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-05-08 00:49:59--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.5.3-5.tar.gz
  Connecting to 10.99.5.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-05-08 00:50:00 ERROR 404: Not Found.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-05-08 00:50:00--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.5.3-6.tar.gz
  Connecting to 10.99.5.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-05-08 00:50:00 ERROR 404: Not Found.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-05-08 00:50:00--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.5.3-7.tar.gz
  Connecting to 10.99.5.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-05-08 00:50:01 ERROR 404: Not Found.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-05-08 00:50:01--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.5.3-8.tar.gz
  Connecting to 10.99.5.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-05-08 00:50:01 ERROR 404: Not Found.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-05-08 00:50:01--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.5.3-9.tar.gz
  Connecting to 10.99.5.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-05-08 00:50:02 ERROR 404: Not Found.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  dpkg: error processing package cpl-plugin-xshoo-calib (--configure):
   installed cpl-plugin-xshoo-calib package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.36-9) ...
  Errors were encountered while processing:
   cpl-plugin-xshoo-calib


cheers,

Andreas

Bug#1035782: nuitka: Nuitka should hard-depend on an earlier python version and thus be uninstallable

[Kay Hayen]

The later versions of Nuitka with less problems didn't make it to unstable
yet, they would only give an error. However, I
expect to make an upload in the next 2 weeks that will then close this bug.

Yours,
Kay

Bug#1035782: nuitka: Nuitka should hard-depend on an earlier python version and thus be uninstallable

[Salvo "LtWorf" Tomaselli]

Package: nuitka
Version: 1.3.5+ds-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: tipos...@tiscali.it

Dear Maintainer,

this is what happens when I tried to run nuitka on localslackirc

nuitka3 --standalone localslackirc
Nuitka-Options:INFO: Used command line options: --standalone localslackirc
Nuitka:WARNING: The version '3.11' is not currently supported. Expect problems.
FATAL: The Python version '3.11' is not supported by '1.3.5', but an upcoming 
release will add it.

It seems the current version is completely incompatible with the version of 
python that is in debian

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

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

Versions of packages nuitka depends on:
ii  base-files   12.4
ii  ccache   4.8+really4.7.5-1
ii  g++  4:12.2.0-3
ii  gcc  4:12.2.0-3
ii  libzstd-dev  1.5.4+dfsg2-5
ii  patchelf 0.14.3-1+b1
ii  python3  3.11.2-1+b1
ii  python3-appdirs  1.4.4-3
ii  python3-dev  3.11.2-1+b1
ii  python3-glob20.5-6
ii  python3-jinja2   3.1.2-1
ii  scons4.4.0+dfsg-1
ii  zlib1g-dev   1:1.2.13.dfsg-1

Versions of packages nuitka recommends:
ii  gdb   13.1-2
ii  libfuse2  2.9.9-6+b1
ii  python3-lxml  4.9.2-1+b1
ii  python3-tqdm  4.64.1-1
ii  strace6.1-0.1

nuitka suggests no packages.

-- no debconf information

Bug#1035781: emacs-common: needs Breaks against incompatible elpa packages from bullseye

[Andreas Beckmann]

Package: emacs-common
Version: 1:28.2+1-14
Severity: serious

There are some elpa packages from bullseye that won't be in bookworm and
that are incompatible with emacs 28, i.e. upgrading emacs will fail if
these packages are still installed.
Therefore emacs-common needs to add Breaks against them s.t. they get
removed during the upgrade to bookworm.

I'm currently building a list of affected packages and will provide a
patch once finished.


Andreas