Bug#1016414: abinit: autopkgtest failure

[Sebastiaan Couwenberg]

reassign -1 src:abinit 9.6.2-1

On 8/29/22 00:51, Adrian Bunk wrote:

Usually that's a strong indication about ABI breakage in a library.

I know nothing about Fortran ABI rules, but nf90_def_var_oneDim()
gaining 3 (optional) parameters in 4.6.0 is suspiciously close
to #3 in the backtrace.

>

Please check with upstream whether a soname bump might be necessary
for libnetcdff.


No other netcdf-fortran rdeps have shown issues which leads me to 
suspect it is an issue in abinit.


I only ended up taking care of netcdf-fortran because that was split of 
from netcdf which is a dependency of gdal. I don't actually use any of 
the netcdf packages, so I'm not willing to spend much time on them.


Kind Regards,

Bas

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

Bug#1018692: ntp fails to start in an LXC

[Mike]

Package: ntp
Version: 1:4.2.8p12+dfsg-4
Severity: minor

Upon upgrading an LXC to Debian 10.12, the ntp package was left
half-configured because the service would not start.  Output was:


systemd[1]: Starting Network Time Service...
systemd[607]: ntp.service: Failed to set up mount namespacing: Permission denied
systemd[607]: ntp.service: Failed at step NAMESPACE spawning 
/usr/lib/ntp/ntp-systemd-wrapper: Permission denied
systemd[1]: ntp.service: Control process exited, code=exited, 
status=226/NAMESPACE
systemd[1]: ntp.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Network Time Service.


Workaround:
Set "PrivateTmp=false" in /lib/systemd/system/ntp.service.

This seems safe, since it's in an LXC already.  I need no further assistance,
just reporting it for others' reference.


Environment:

Linux ... 4.19.0-21-amd64 #1 SMP Debian 4.19.249-2 (2022-06-30) x86_64 GNU/Linux

||/ Name Version   Architecture Description
+++--=--===
ii  libnss-systemd:amd64 241-7~deb10u8 amd64nss module providing 
dynamic user and group name resolution
ii  libpam-systemd:amd64 241-7~deb10u8 amd64system and service 
manager - PAM module
ii  libsystemd0:amd64241-7~deb10u8 amd64systemd utility library
ii  ntp  1:4.2.8p12+dfsg-4 amd64Network Time Protocol 
daemon and utility programs
ii  systemd  241-7~deb10u8 amd64system and service 
manager
ii  systemd-sysv 241-7~deb10u8 amd64system and service 
manager - SysV links

Bug#1018689: override: python3:python/standard

[Daniel Lewart]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: debian-b...@lists.debian.org, pyth...@packages.debian.org

Debian FTP Master(s) and Matthias,

Currently, python3 is Priority: optional.

The following Buster packages have Priority: standard:
  * python
  * python-minimal
  * python2.7
  * python3-reportbug

Now the following Priority:standard packages depend on python3
(directly or indirectly):
  * apt-listchanges
  * python3-reportbug
  * reportbug

Therefore, I think that python3 should change from:
Priority: optional
to:
Priority: standard

Thank you!
Daniel Lewart
Urbana, Illinois

Bug#1018693: manpage translation missing

[Osamu Aoki]

Source: adduser
Version: 3.128
Severity: normal

symptoms: piuparts run fails with:

0m17.8s ERROR: WARN: Broken symlinks:
  /usr/share/man/da/man8/addgroup.8.gz -> adduser.8.gz (adduser)
  /usr/share/man/da/man8/delgroup.8.gz -> deluser.8.gz (adduser)
  /usr/share/man/de/man8/addgroup.8.gz -> adduser.8.gz (adduser)
  /usr/share/man/de/man8/delgroup.8.gz -> deluser.8.gz (adduser)
  /usr/share/man/es/man8/delgroup.8.gz -> deluser.8.gz (adduser)
  /usr/share/man/fr/man8/addgroup.8.gz -> adduser.8.gz (adduser)
  /usr/share/man/fr/man8/delgroup.8.gz -> deluser.8.gz (adduser)
  /usr/share/man/it/man8/addgroup.8.gz -> adduser.8.gz (adduser)
  /usr/share/man/it/man8/delgroup.8.gz -> deluser.8.gz (adduser)
  /usr/share/man/pl/man8/addgroup.8.gz -> adduser.8.gz (adduser)
  /usr/share/man/pl/man8/delgroup.8.gz -> deluser.8.gz (adduser)
  /usr/share/man/pt/man8/addgroup.8.gz -> adduser.8.gz (adduser)
  /usr/share/man/pt/man8/delgroup.8.gz -> deluser.8.gz (adduser)
  /usr/share/man/ru/man8/addgroup.8.gz -> adduser.8.gz (adduser)
  /usr/share/man/ru/man8/delgroup.8.gz -> deluser.8.gz (adduser)
  /usr/share/man/sv/man8/delgroup.8.gz -> deluser.8.gz (adduser)
---

observation:
20a9f34 ("remove debconf", 2022-07-13)
This essentially stopped building translated manpages (I guess)

(This removed old debian/po/* but existing po/* seems to be not used for
building manapage)

As a result, translated manpage files such as
/usr/share/man/da/man8/adduser.8.gz are missing in current binary debs
while source contain po4a for manpage.

All these links are generated by debian/links and create dangling links. 

I don't see fix for these in salsa pending, yet.

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

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

Bug#1017132: opentracing-cpp: diff for NMU version 1.6.0-2.1

[Stephen Gelman]

On Aug 28, 2022 at 4:29:03 AM, Luca Falavigna  wrote:

> Control: tags 1017132 + patch
> Control: tags 1017132 + pending
>
>
> Dear maintainer,
>
> I've prepared an NMU for opentracing-cpp (versioned as 1.6.0-2.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.
>
> Regards,
> Luca
>

This is awesome, thanks so much! It was on my todo list to fix but I hadn’t
gotten around to it yet… Would you be interested in creating a MR for your
changes to salsa? If not that’s fine, just let me know and I will pull in
the changes myself.

Stephen

Bug#1018694: [udd] upload_date stalled

[Nilesh Patra]

Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: eribe...@debian.org

Hi,

The last upload_date that I can see from `bapase' seems to be 17th of August.
Same case while checking `date' from `upload_history'.

Could you consider checking what might be wrong?

Best,
Nilesh

Bug#1018690: override: python3-reportbug:python/optional

[Daniel Lewart]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: debian-b...@lists.debian.org, 
python3-report...@packages.debian.org

Debian FTP Master(s) and Reportbug Maintainers,

Currently, python3-reportbug is Priority: standard.

It has only one reverse dependency: reportbug (Priority: standard).

Debian Policy 2.5 Priorities:
https://www.debian.org/doc/debian-policy/ch-archive.html#priorities
states:
"The priority of a package is determined solely by the functionality
it provides directly to the user. The priority of a package should
not be increased merely because another higher-priority package
depends on it; ..."

I think that applies in this case.

Please change the python3-reportbug Priority from standard to optional.

Thank you!
Daniel Lewart
Urbana, Illinois

Bug#1017749: certbot: /usr/share/doc/certbot/README.rst.gz is not useful for Debian users

[Harlan Lieberman-Berg]

On Fri, Aug 19, 2022 at 7:51 PM Borden  wrote:
> The file /usr/share/doc/certbot/README.rst.gz provides a generic overview of 
> certbot and advice to refer to the official documentation at 
> https://certbot.eff.org/instructions?ws=apache=debiantesting . However, 
> will be confusing for new users because the instructions direct them to 
> install certbot from snap and _uninstall_ this package.
>
> Either encourage the eff.org to provide instructions that don't involve 
> removing this package or the README needs to provide specific instructions 
> for Debian users (for example: ignore steps 1 to 6 in the official 
> documentation and start where it says "Choose how you'd like to run Certbot")

Hello,

This is something that I've spoken to the EFF about before.  At the
time, they weren't willing to officially sign off on the distros'
packages because they were worried about the additional support
burden.  That being said, I think things have been stable for a long
period of time now and the overall velocity of feature releases has
slowed down, so I will approach them again.

Thank you for the prompt!

Sincerely,

Bug#1001904: mesaflash: Maintainer address bounces

[Petter Reinholdtsen]

[Jeff Epler]
> Is there a specific sender address that it will suffice to whitelist, or
> does the list need to permit mail from any address, regardless of
> subscription status?

Not really, as any user is expected to be able reach the maintainer
using that address, and such sender can come from anywhere.

Is this still a problem, or is the maintainer address now moderating
non-subscribers and allowing their messages to get through?
-- 
Happy hacking
Petter Reinholdtsen

Bug#1017542: systemd-cryptsetup@vda5_crypt.service: Control process exited, code=exited, status=1/FAILURE

[ng]

I installed dracut,  and ran 'sudo dracut -f' more than twice, with 
reboots,  but it didn't fixed the issue.  It remains the same.


(I sent this mail over 2 weeks ago to your personal email by mistake, 
I'm sorry).



El 17/8/22 a las 16:24, Michael Biebl escribió:

Can you try dracut as your initramfs generator?
It supports
http://systemd.io/INITRD_INTERFACE/

Specifically this part should be relevant to you:

"
If the executable /run/initramfs/shutdown exists systemd will use it 
to jump back into the initrd on shutdown. /run/initramfs/ should be a 
usable initrd environment to which systemd will pivot back and the 
shutdown executable in it should be able to detach all complex storage 
that for example was needed to mount the root file system.

"

Bug#1012587: Chance to bring back to testing?

[Bernhard]

Dear maintainer

Only a careful question:
Is there a chance to bring this package back to testing?
I need this package to maintain my YubiKey.

Thank you for the support
Bernhard

Bug#1018259: nmu: libidn2_2.3.3-1

[Johannes Schauer Marin Rodrigues]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: jo...@debian.org, ond...@debian.org, si...@josefsson.org, 
k...@debian.org

Hi,

due to a bug in debhelper (see #1015263) the libidn2-0 package gained a
wrong dependency on sgml-base. Since there was no upload of libidn2
since the bug got fixed in debhelper, the current version on unstable
still wrongly depends on sgml-base. This breaks di-builds because
sgml-base doesn't exist in udeb context. This added dependency also
hurts bootstrapping and breaks our DPKG_ROOT CI. Please rebuilds libidn2
with the current debhelper version.

nmu libidn2_2.3.3-1 . ANY . unstable . -m "rebuild with debhelper after 
#1015263 was fixed"

Thanks!

cheers, josch

Bug#1018261: confmodule should be distributed separately from debconf

[Gioele Barabucci]

Package: debconf
Version: 1.5.79
Tags: patch
Control: affects -1 cdebconf

Dear debconf maintainers,

could you please ship `/usr/share/debconf/confmodule{,.sh}` in a 
separate package, for example debconf-common?


Having a separate, shared confmodule is a necessary step in enabling the 
transition towards cdebconf.


Patches to create a separate `debconf-common` package, and to adjust 
confmodule to be debconf-implementation agnostic, are available at


https://salsa.debian.org/gioele/debconf/-/commits/debconf-common-pkg

Regards,

--
Gioele Barabucci

Bug#983228: unknown-horizons: Syntax warning while installing update

[Tobias Frost]

Control: reassign -1 src:unknown-horizons
Conrtol: found -1 2019.1-3

On Sun, 28 Aug 2022 10:26:50 +0200 Tobias Frost  wrote:
> Control: reassign -1 src:fife
> Control: forcemerge 993132 -1
> Control: affects -1 unknown-horizons
> 
> This seems to be #993132.


crap… I see that also with a fife package containing the pacth for #993132.
re-reassiging undoing my mess…

--
tobi

Bug#1017132: opentracing-cpp: diff for NMU version 1.6.0-2.1

[Luca Falavigna]

Control: tags 1017132 + patch
Control: tags 1017132 + pending


Dear maintainer,

I've prepared an NMU for opentracing-cpp (versioned as 1.6.0-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards,
Luca

diff -Nru opentracing-cpp-1.6.0/debian/changelog opentracing-cpp-1.6.0/debian/changelog
--- opentracing-cpp-1.6.0/debian/changelog	2021-11-07 06:42:53.0 +0100
+++ opentracing-cpp-1.6.0/debian/changelog	2022-08-28 11:11:38.0 +0200
@@ -1,3 +1,11 @@
+opentracing-cpp (1.6.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/catch_SIGSTKSZ.patch:
+- Fix FTBFS with glibc 2.34 (Closes: #1017132).
+
+ -- Luca Falavigna   Sun, 28 Aug 2022 11:11:38 +0200
+
 opentracing-cpp (1.6.0-2) unstable; urgency=medium
 
   * Upload to unstable
diff -Nru opentracing-cpp-1.6.0/debian/patches/catch_SIGSTKSZ.patch opentracing-cpp-1.6.0/debian/patches/catch_SIGSTKSZ.patch
--- opentracing-cpp-1.6.0/debian/patches/catch_SIGSTKSZ.patch	1970-01-01 01:00:00.0 +0100
+++ opentracing-cpp-1.6.0/debian/patches/catch_SIGSTKSZ.patch	2022-08-28 11:11:38.0 +0200
@@ -0,0 +1,40 @@
+Index: opentracing-cpp-1.6.0/3rd_party/include/opentracing/catch2/catch.hpp
+===
+--- opentracing-cpp-1.6.0.orig/3rd_party/include/opentracing/catch2/catch.hpp
 opentracing-cpp-1.6.0/3rd_party/include/opentracing/catch2/catch.hpp
+@@ -6571,6 +6571,17 @@ namespace Catch {
+ int id;
+ const char* name;
+ };
++
++// 32kb for the alternate stack seems to be sufficient. However, this value
++// is experimentally determined, so that's not guaranteed.
++#if defined(_SC_SIGSTKSZ_SOURCE) || defined(_GNU_SOURCE)
++// on glibc > 2.33 this is no longer constant, see
++// https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;h=85e84fe53699fe9e392edffa993612ce08b2954a;hb=HEAD
++static constexpr std::size_t altStackSize = 32 * 1024;
++#else
++static constexpr std::size_t altStackSize = std::max(static_cast(SIGSTKSZ), 32 * 1024)
++#endif
++
+ static SignalDefs signalDefs[] = {
+ { SIGINT,  "SIGINT - Terminal interrupt signal" },
+ { SIGILL,  "SIGILL - Illegal instruction signal" },
+@@ -6597,7 +6608,7 @@ namespace Catch {
+ isSet = true;
+ stack_t sigStack;
+ sigStack.ss_sp = altStackMem;
+-sigStack.ss_size = SIGSTKSZ;
++sigStack.ss_size = altStackSize;
+ sigStack.ss_flags = 0;
+ sigaltstack(, );
+ struct sigaction sa = { };
+@@ -6628,7 +6639,7 @@ namespace Catch {
+ bool FatalConditionHandler::isSet = false;
+ struct sigaction FatalConditionHandler::oldSigActions[sizeof(signalDefs)/sizeof(SignalDefs)] = {};
+ stack_t FatalConditionHandler::oldSigStack = {};
+-char FatalConditionHandler::altStackMem[SIGSTKSZ] = {};
++char FatalConditionHandler::altStackMem[altStackSize] = {};
+ 
+ } // namespace Catch
+ 
diff -Nru opentracing-cpp-1.6.0/debian/patches/series opentracing-cpp-1.6.0/debian/patches/series
--- opentracing-cpp-1.6.0/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ opentracing-cpp-1.6.0/debian/patches/series	2022-08-28 11:11:38.0 +0200
@@ -0,0 +1 @@
+catch_SIGSTKSZ.patch


signature.asc
Description: PGP signature

Bug#1018268: gnome-shell-extension-gamemode: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-gamemode
Version: 7-1
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension's apt/dpkg dependencies say it is compatible with all
versions of GNOME Shell, but its metadata disagrees and does not list
GNOME Shell 43 as a compatible version. Depending what has changed,
it might need either a simple metadata update or code changes.

GNOME Shell 43 is available in experimental (as a beta version) and is
expected to be uploaded to unstable soon (transition:
https://bugs.debian.org/1018118).

I'd recommend adding dependencies on

gnome-shell (>= x), gnome-shell (<< y~)

for suitable values of x and y, so that it can only be co-installed with
versions of GNOME Shell for which compatibility has been checked.
For version 7-1 the appropriate dependency seems to be

gnome-shell (>= 3.38), gnome-shell (<< 43~)

but obviously this will change when compatibility with version 43
is added.

smcv

Bug#1018269: gnome-shell-extension-hamster: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-hamster
Version: 0.10.0+git20210628-3
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension has not been checked for compatibility with GNOME Shell
43. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018270: gnome-shell-extension-hide-activities: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-hide-activities
Version: 42-2
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension's apt/dpkg dependencies say it is compatible with GNOME
Shell 43~beta-1 (currently available in experimental), but its metadata
disagrees and does not list 43 as a compatible version. Depending what
has changed, it might need either a simple metadata update or code changes.

After updating it for gnome-shell 43 compatibility, I'd recommend giving
it a dependency on gnome-shell (<< 44~) so that it won't be co-installable
with GNOME Shell 44 (including alphas/betas) during the Debian 13 cycle.

smcv

Bug#1018282: gnome-shell-extension-top-icons-plus: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-top-icons-plus
Version: 27-7
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension has not been checked for compatibility with GNOME Shell
43. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018283: gnome-shell-extension-vertical-overview: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-vertical-overview
Version: 9-1
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension has not been checked for compatibility with GNOME Shell
43. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018233: fife: X Error of failed request: GLXBadDrawable

[Tobias Frost]

Debugging into it:

It seems to be related to the GPU. On my Desktop -- using a nvidia GTX 3060Ti 
card --
I see this failure.

On my old Thinkpad Edge E130 (i910), I can start unknown-horizons…

-- 
tobi

Bug#983841: libvirt-php 0.5.4-3+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 983841 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: libvirt-php
Version: 0.5.4-3+deb10u1

Explanation: fix segmentation fault in libvirt_node_get_cpu_stats

Bug#990739: iptables-netflow 2.3-5+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 990739 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: iptables-netflow
Version: 2.3-5+deb10u1

Explanation: fix DKMS build failure regression caused by Linux upstream changes 
in the 4.19.191 kernel

Bug#991120: postsrsd 1.5-2+deb10u2 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 991120 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: postsrsd
Version: 1.5-2+deb10u2

Explanation: fix potential denial of service issue when Postfix sends certain 
long data fields such as multiple concatenated email addresses [CVE-2021-35525]

Bug#1018290: /usr/sbin/update-tirfs: does not run hook scripts in /etc/initramfs/post-update.d

[Victor Westerhuis]

Package: tiny-initramfs
Version: 0.1-5
Severity: normal
File: /usr/sbin/update-tirfs
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Contrary to section 8.3 of the Debian Kernel Handbook [1], 
/usr/sbin/update-tirfs does not run the hook scripts in 
/etc/initramfs/post-update.d. Together with a bug in systemd-boot (#1014581)
this led to my system trying and failing to boot without an initramfs.

I did not know whether to make the severity of this bug normal or serious.
While it does violate a 'must' directive in the Kernel Handbook, I don't know
whether that carries the same severity as violating a directive from the Policy.

Regards,

Victor Westerhuis


- -- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (100, 'experimental'), (1, 
'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_NL.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US:en:nl_NL:nl
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tiny-initramfs depends on:
ii  tiny-initramfs-core  0.1-5+b12

tiny-initramfs recommends no packages.

tiny-initramfs suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE6OxII3T+o0Ujs6ECQz2Rq5dHQPsFAmMLWO0THHZpY3RvckB3
ZXN0ZXJodS5pcwAKCRBDPZGrl0dA+yvGEACaLdiF9/QD61nv7cjjcLeE4bqqLBBR
WhVA1INGoJX27qf+o0WQVKUCe0/PqzgMjSp6wW2Ta8lrj3HaxdjutEIwIVC3VrxG
4R48X4EJzZjIqIZWPiPxvTDXJeVH1ar8KTYbyQNhZY5r8uCtIfiqgh2DUc/vRt5p
DW57YmIo6UAl2p0gRxQfi3ULaqTI4Mslp6bfVZQ8MWXNuf1tabY3mts2vPL/K7cp
/XMHLv567XQJqGYz1SJdb4LizpgD+OauoThFdTk37dJVXU6gvY8QPUMaN7wIZp2g
kR54jPWR3cFiHCrHZdHl6D2cwwSr44wnL6qxBUS1+wvORVS6tNBpJHROxScKYpHk
QDYsJrgqlcef4KSxUxXF5MR6kDR8ylX+2WFUrPjYNUiC3NSQCl0NaG3iXv/7KU/+
zkQyYYzbagtueYsMzL6MUlpE51nnpM6R2DwLg19/Yzsm4xgTVU6K6NtHNu1lU9mo
MfseeGMf6ZUmN44SYVLdehd+mXT8C9KXYYmS9aRAPUL8dybQFmIWGz15dmpsyeUA
DkYARyS0oBtKZUQKFAMkV/fxgL0f4JPvrWRAjejxtAtjKWS4/5PIjYwx+zQql5+T
8tSPOcZYmJuQA4WyOhghBNwqn/dfT3EvLZ8nfNTPmbJsO/oukgnwU6cmb7NCPKNq
VbAfSz54YMmfWQ==
=Lc76
-END PGP SIGNATURE-
>From 4f8089ba3ab39d55b19447712224972afabfc908 Mon Sep 17 00:00:00 2001
From: Victor Westerhuis 
Date: Sun, 28 Aug 2022 13:37:50 +0200
Subject: Run hook scripts in /etc/initramfs/post-update.d

According to the Debian Kernel Handbook, section 8.3, "initramfs
builders must call these scripts using run-parts after they create,
update or delete an initramfs."

Because update-tirfs uses `set -e`, there is no need to check if the
preceding invocation of mktirfs was successful.
---
 debian/extra/update-tirfs | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/debian/extra/update-tirfs b/debian/extra/update-tirfs
index c79898d..e5f69f2 100755
--- a/debian/extra/update-tirfs
+++ b/debian/extra/update-tirfs
@@ -61,6 +61,9 @@ if [ x"$VERSION" = x"all" ] ; then
 if ! [ -r "${V}" ] ; then continue ; fi
 V=${V#/boot/vmlinu?-}
 mktirfs -o /boot/initrd.img-"${V}" "${V}"
+if [ -d /etc/initramfs/post-update.d ]; then
+  run-parts --arg="${V}" --arg=/boot/initrd.img-"${V}" 
/etc/initramfs/post-update.d
+fi
   done
 else
   if ! ls /boot/vmlinu[xz]-"${VERSION}" >/dev/null 2>&1 ; then
@@ -68,4 +71,7 @@ else
 exit 1
   fi
   mktirfs -o /boot/initrd.img-"${VERSION}" "${VERSION}"
+  if [ -d /etc/initramfs/post-update.d ]; then
+run-parts --arg="${VERSION}" --arg=/boot/initrd.img-"${VERSION}" 
/etc/initramfs/post-update.d
+  fi
 fi
-- 
2.37.2

Bug#1007764: gcc-defaults: please support DPKG_ROOT

[Johannes Schauer Marin Rodrigues]

Hi,

On Wed, 17 Aug 2022 18:20:36 +0200 Johannes Schauer Marin Rodrigues 
 wrote:
> On Wed, 16 Mar 2022 13:30:26 +0100 Johannes Schauer Marin Rodrigues 
>  wrote:
> > when creating chroots for new architectures that are in the process of being
> > bootstrapped without yet having emulation support from qemu, it is not
> > possible to run maintainer scripts inside the foreign architecture chroot
> > because foreign architecture ELF binaries cannot be executed. The solution 
> > to
> > that problem is to run maintainer scripts from outside the chroot and use 
> > the
> > DPKG_ROOT environment variable to instruct the maintainer script on which
> > chroot to operate. By default, for normal installations, that environment
> > variable is set, but empty.
> > 
> > Apart from init-system-helpers and pam, all packages in the
> > Essential:yes set have support for DPKG_ROOT already. To start building
> > packages we also need to install build-essential.
> > 
> > Please consider applying the patch from this merge request:
> > 
> > https://salsa.debian.org/toolchain-team/gcc-defaults/-/merge_requests/4
> > 
> > We tested it in our CI environment and it produces a bit-by-bit
> > identical chroot with DPKG_ROOT compared to a normal installation.
> > 
> > https://salsa.debian.org/helmutg/dpkg-root-demo/
> > 
> > Since the DPKG_ROOT variable is empty on normal installations, the patch
> > should have no effect in the normal case.
> 
> I wanted to send a friendly ping about this bug. I see that since I filed this
> bug, you uploaded three new versions of gcc-defaults. Please consider applying
> the changes of above merge request against gcc-defaults on salsa. Here is the
> diff in plain text for your convenience:
> 
> --- a/debian/g++.postinst.in
> +++ b/debian/g++.postinst.in
> @@ -2,9 +2,9 @@
> 
>  # remove the doc dir, if it's still a directory and replace with a symlink
>  pkg=`basename $0 .postinst`
> -if [ ! -L  /usr/share/doc/$pkg ]; then
> -rm -rf /usr/share/doc/$pkg
> -ln -s cpp /usr/share/doc/$pkg
> +if [ ! -L  "$DPKG_ROOT/usr/share/doc/$pkg" ]; then
> +rm -rf "$DPKG_ROOT/usr/share/doc/$pkg"
> +ln -s cpp "$DPKG_ROOT/usr/share/doc/$pkg"
>  fi
> 
>  # fix for report #138038: remove old diversions

I uploaded an NMU of gcc-defaults with the maximum delay of 15 days. Please
cancel if you disagree. Full debdiff attached.

Thanks!

cheers, joschdiff -Nru gcc-defaults-1.200/debian/changelog gcc-defaults-1.200+nmu1/debian/changelog
--- gcc-defaults-1.200/debian/changelog	2022-07-22 17:31:39.0 +0200
+++ gcc-defaults-1.200+nmu1/debian/changelog	2022-08-28 08:23:21.0 +0200
@@ -1,3 +1,10 @@
+gcc-defaults (1.200+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Support DPKG_ROOT in g++ postinst (closes: #1007764)
+
+ -- Johannes Schauer Marin Rodrigues   Sun, 28 Aug 2022 08:23:21 +0200
+
 gcc-defaults (1.200) unstable; urgency=medium
 
   * Stop building gccbrig, removed in GCC 12.
diff -Nru gcc-defaults-1.200/debian/g++.postinst.in gcc-defaults-1.200+nmu1/debian/g++.postinst.in
--- gcc-defaults-1.200/debian/g++.postinst.in	2020-11-17 19:53:07.0 +0100
+++ gcc-defaults-1.200+nmu1/debian/g++.postinst.in	2022-08-28 08:23:21.0 +0200
@@ -2,9 +2,9 @@
 
 # remove the doc dir, if it's still a directory and replace with a symlink
 pkg=`basename $0 .postinst`
-if [ ! -L  /usr/share/doc/$pkg ]; then
-rm -rf /usr/share/doc/$pkg
-ln -s cpp /usr/share/doc/$pkg
+if [ ! -L  "$DPKG_ROOT/usr/share/doc/$pkg" ]; then
+rm -rf "$DPKG_ROOT/usr/share/doc/$pkg"
+ln -s cpp "$DPKG_ROOT/usr/share/doc/$pkg"
 fi
 
 # fix for report #138038: remove old diversions


signature.asc
Description: signature

Bug#1018267: gnome-shell-extension-freon: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-freon
Version: 48+dfsg-1
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension's dependencies say it is compatible with GNOME Shell
43~beta-1 (currently available in experimental), but its metadata
disagrees and does not list 43 as a compatible version. Depending how
it has been affected by changes in upstream GNOME Shell, it might need
real code changes, or just a metadata update.

Even if its JavaScript code is compatible with Shell 43, debian/control
will need updating for the final release of Shell 43. (I'd recommend using
gnome-shell (<< 44~) rather than gnome-shell (<< 44) as the upper bound for
the version range after it has been confirmed to be compatible with 44,
so that alphas and betas of 44 are treated as 44.)

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018266: gnome-shell-extension-easyscreencast: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-easyscreencast
Version: 1.6.3-1
Severity: important
Tags: bookworm sid fixed-upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43
Forwarded: https://github.com/EasyScreenCast/EasyScreenCast/pull/340

This extension looks like it needs code changes for GNOME Shell 43,
which is currently in experimental and should be going to unstable soon.
Upstream version 1.7.0 seems to have the required changes (I have not
tested it, I don't use this extension myself).

After updating it for gnome-shell 43 compatibility, I'd recommend giving
it a dependency on gnome-shell (<< 44~) so that it won't be co-installable
with GNOME Shell 44 (including alphas/betas) during the Debian 13 cycle.
The current dependency on gnome-shell (<< 43) is co-installable with
gnome-shell (= 43~beta-1), which seems unintended.

smcv

Bug#1018273: gnome-shell-extension-panel-osd: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-panel-osd
Version: 1.0.50.gc032923-2
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension's apt/dpkg dependencies say it is compatible with all
versions of GNOME Shell, but its metadata disagrees and does not list
GNOME Shell 43 as a compatible version. Depending what has changed,
it might need either a simple metadata update or code changes.

GNOME Shell 43 is available in experimental (as a beta version) and is
expected to be uploaded to unstable soon (transition:
https://bugs.debian.org/1018118).

I'd recommend adding dependencies on

gnome-shell (>= x), gnome-shell (<< y~)

for suitable values of x and y, so that it can only be co-installed with
versions of GNOME Shell for which compatibility has been checked.
For version 1.0.50.gc032923-2 the appropriate dependency seems to be

gnome-shell (>= 3.10), gnome-shell (<< 43~)

but obviously this will change when compatibility with version 43
is added.

smcv

Bug#1018271: gnome-shell-extension-impatience: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-impatience
Version: 0.4.8-1
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension's dependencies say it is compatible with GNOME Shell
43~beta-1 (currently available in experimental), but its metadata disagrees
and does not list 43 as a compatible version.

Even if its JavaScript code is compatible with Shell 43, debian/control
will need updating for the final release of Shell 43. (I'd recommend using
gnome-shell (<< 44~) rather than gnome-shell (<< 44) as the upper bound for
the version range after it has been confirmed to be compatible with 44,
so that alphas and betas of 44 are treated as 44.)

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018272: gnome-shell-extension-kimpanel: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-kimpanel
Version: 0.0~git20220602.3318bdf-1
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension has not been checked for compatibility with GNOME Shell
43. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018284: gnome-shell-extension-volume-mixer: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-volume-mixer
Version: 41.1+dfsg-2
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension has not been checked for compatibility with GNOME Shell
43. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

Looking at upstream issue reports, it seems that some features already
do not work correctly with GNOME 42, so code changes are probably necessary?

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018285: gnome-shell-extension-weather: unmaintained upstream

[Simon McVittie]

Source: gnome-shell-extension-weather
Version: 0.0~git20210509.d714eb1-4
Severity: important
Tags: upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: unmaintained-upstream

The Gitlab project https://gitlab.com/jenslody/gnome-shell-extension-openweather
referred to by this package's Homepage field has been archived, meaning
that it no longer accepts code contributions or issue reports.

For this extension to have a future, someone (perhaps its Debian maintainer
or perhaps unrelated) will need to fork the project and continue development.

smcv

Bug#1018265: Possibly related: debian bug 949315

[Steinar Bang]

Related bug info:

When I googled the problem I ended up in debian bug 949315, which is
closed and fixed, and as far as I can tell, was fixed in cups 2.3.3op1,
and bullseye is 2.3.3op2.

The way I found debian bug 949315, was:

I first found cups-filters issue 
https://github.com/OpenPrinting/cups-filters/issues/193

cups-filters issue 193 linked to a cups issue 
https://github.com/apple/cups/issues/5740

cups-filters #193 has a fix attached that was rejected, because there
was a fix in cups.

cups issue #5470 in turn, linked to a debian pull request 
https://github.com/OpenPrinting/cups/pull/23

pull request #23 refers to: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949315

And bug 949315 is closed as fixed.

The pull request had milestone v2.3.3op1 so that's why I'm guessing the
fix came in 2.3.3op1.

Bug#1018287: python3-requests-cache: The "pip3 check" complains dependency of the attr module.

[Takahide Nojima]

Package: python3-requests-cache
Version: 0.9.1-1
Severity: normal

Dear Maintainer,

 I found 'pip3 check' complaints against python3-requests-cache-0.9.1-1
like below,
"requests-cache 0.9.1 has requirement attrs<22.0,>=21.2, but you have
attrs 22.1.0."

 I used pip3 of the python3-pip package.

 I guess that rootcause might be that /usr/lib/python3/dist-
packages/requests_cache-0.9.1.dist-info/METADATA has
Requires-Dist: attrs (>=21.2,<22.0).

 I've checked 'pip3 check' doesn't complain when I installed not using
python3-requests-cache package, but only using pip3 install like below,

 pip3 install --user requests-cache

 As your reference, I write the "pip3 list --user" result below,

pip3 list --user | egrep '^(requests-cache|attr)'
attrs 22.1.0
requests-cache 0.9.6

 Would you please fix this bug against the python3-requests-cache
package?

Thank you in advance,
Takahide Nojima


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

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

Versions of packages python3-requests-cache depends on:
ii  python3    3.10.6-1
ii  python3-appdirs    1.4.4-2
ii  python3-attr   22.1.0-1
ii  python3-cattr  1.10.0-1
ii  python3-requests   2.27.1+dfsg-1
ii  python3-url-normalize  1.4.3-2
ii  python3-urllib3    1.26.9-1

python3-requests-cache recommends no packages.

Versions of packages python3-requests-cache suggests:
pn  python-requests-cache-doc  
pn  python3-pymongo    
pn  python3-redis  

-- no debconf information

Bug#1018288: waagent: Debian specific patch breaks kali support

[Raphaël Hertzog]

Package: waagent
Version: 2.7.3.0-1
Severity: important
User: de...@kali.org
Usertags: origin-kali

Hello,

this patch broke kali support:
https://salsa.debian.org/cloud-team/waagent/-/commit/dd8f1771d89bd255f96938f080b02b889da79ad7

The import of "DebianOSBaseUtil" has been dropped while it's clearly used
further down the road:

if distro_name == "kali":
return DebianOSBaseUtil()

Please re-add the import statement. There's a merge request lying around
since one year:
https://salsa.debian.org/cloud-team/waagent/-/merge_requests/3

But that merge request restores it in the wrong order so that would still
keep a diff compared to upstream. I have ask the MR submitter to update
it.

Cheers,

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

Kernel: Linux 5.18.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
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)
LSM: AppArmor: enabled

Versions of packages waagent depends on:
ii  bind9-host [host]  1:9.18.6-1
ii  ca-certificates20211016
ii  eject  2.38.1-1
ii  fdisk  2.38.1-1
ii  iptables   1.8.8-1
ii  net-tools  1.60+git20181103.0eebece-1
ii  openssh-server 1:9.0p1-1+b1
ii  openssl3.0.5-2
ii  parted 3.5-1
ii  python33.10.6-1
ii  python3-distro 1.7.0-1
ii  python3-pkg-resources  59.6.0-1.2
ii  sudo   1.9.11p3-1
ii  util-linux 2.38.1-1

waagent recommends no packages.

waagent suggests no packages.

Bug#1015487: libfiu: ftbfs with LTO (link time optimization) enabled

[Alberto Bertogli]

On Thu, Aug 18, 2022 at 11:00:24AM -0700, Chris Lamb wrote:

Hey Alberto,

Just briefly reaching out to you just in case this slipped your mind
during your time away from the internet. Hopefully, it's quite an easy
fix.


Indeed it had sneakily gone away from my TODO list, so thanks for the 
reminder!




On 20 July 2022 00:18:29 GMT-06:00, Chris Lamb  wrote:

Hi Alberto,

Any ideas why libfiu fails to build with -flto=auto -ffat-lto-objects
(etc.) enabled?


Just FYI I have extremely limited connectivity until the end of the
month, so I'm afraid I won't have a chance to look before then :(



cc -I../../libfiu/ -L../../libfiu/ -D_XOPEN_SOURCE=600 -D_GNU_SOURCE
-fPIC -DFIU_ENABLE=1 -g -O2 -ffile-prefix-map=/<>=.
-flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat
-Werror=format-security -std=c99 -pedantic -Wall -std=c99 -pedantic
-Wall tests/strdup.c -lfiu -o tests/strdup.bin
LD_LIBRARY_PATH=../libfiu/
LD_PRELOAD=./libs/fiu_run_preload.so:./libs/fiu_posix_preload.so
./test-enable_stack
test-enable_stack: test-enable_stack.c:39: main: Assertion `func2() ==
1' failed.


From this it seems the issue is with the stack trace collection. If LTO
is doing some inlining for example (which wouldn't surprise me) then it
could cause the test to fail.


That's exactly what's happening: "-flto=auto -O2" was causing one of the 
functions of the stack to be inlined, and causing the tests to fail.


Patch 
https://blitiri.com.ar/git/r/libfiu/c/902b282375587352dccf6467fa740330d6900e54/ 
(currently on the `next` branch, I'll move it to `master` once you 
confirm it fixes the issue in the automated builds too) should fix this 
issue.


Thanks a lot!
Alberto


PS: That patch can be downloaded in text format from
https://blitiri.com.ar/git/r/libfiu/c/902b282375587352dccf6467fa740330d6900e54.patch

Bug#1018259: nmu: libidn2_2.3.3-1

[Cyril Brulebois]

Johannes Schauer Marin Rodrigues  (2022-08-28):
> due to a bug in debhelper (see #1015263) the libidn2-0 package gained a
> wrong dependency on sgml-base. Since there was no upload of libidn2
> since the bug got fixed in debhelper, the current version on unstable
> still wrongly depends on sgml-base. This breaks di-builds because
> sgml-base doesn't exist in udeb context. This added dependency also
> hurts bootstrapping and breaks our DPKG_ROOT CI. Please rebuilds libidn2
> with the current debhelper version.
> 
> nmu libidn2_2.3.3-1 . ANY . unstable . -m "rebuild with debhelper after 
> #1015263 was fixed"

I'm a little confused.

d-i builds are all green:
  https://d-i.debian.org/daily-images/daily-build-overview.html

and more importantly, src:libidn2 doesn't build any udeb.


Note that I'm not objecting to the rebuild, I'm just not sure the context
is right… libnl3 was building a broken udeb though, for which I uploaded
a workaround:
  
https://tracker.debian.org/news/1353402/accepted-libnl3-370-02-source-into-unstable/


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


signature.asc
Description: PGP signature

Bug#671719: Carriers can deadlock stoping delivery and removal of goods

[Tobias Frost]

Source: widelands
Followup-For: Bug #671719
Control: forwarded -1 https://github.com/widelands/widelands/issues/2309
Control: close -1

Upstream says it is resolved…
Closing it therefore, please reopen (or provide upstream more information) if 
you can still reproduce it.


-- 
tobi

Bug#17140: Saving extra food

[Tobias Frost]

Source: freeciv
Followup-For: Bug #17140
Control: tags -1 upstream

This ancient bug does not look like actionable to me…
Therefore closing it.

If it is still a missing feature, please discuss with upstream directly.

-- 
tobi

Bug#1018259: nmu: libidn2_2.3.3-1

[Cyril Brulebois]

Johannes Schauer Marin Rodrigues  (2022-08-28):
> The current version of libidn2-0 in unstable still wrongly depends on
> sgml-base. A rebuild of src:libidn2 against the version of debhelper
> that is currently in the archive will fix this problem.

Sure, that's the part I agree with.

> I added you to CC because you commented on #1015263 saying "This breaks
> d-i builds". The thing that doesn't have a udeb is sgml-base (which you
> pointed out in the same message).

Let's backpedal a bit, my message had:

> Judging by the current list of `apt-cache rdepends sgml-base`, this
> problem has already spread quite a bit.

This breaks d-i builds, (at least) via libnl udebs picking up a
dependency on sgml-base, which doesn't exist in a udeb context.

There, “this” = buggy sgml-base dependency spreading, which broke d-i
builds *via libnbl udebs* (which was worked around); that wasn't meant
to mean that libidn2 itself was breaking d-i builds. It can't, as it
doesn't build udebs, so it's no factor.

Hope that clarifies.


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


signature.asc
Description: PGP signature

Bug#1017958: tiff: Don't build with LERC on i386

[GCS]

Control: tags -1 +moreinfo

Hi Jeremy, Adam,

First of all, it was nice to see you both in person at DebConf 22.
Hope we will meet again.

On Tue, Aug 23, 2022 at 5:09 PM Jeremy Bicha  wrote:
> Is having lerc compression support critical enough on i386 to justify
> making extra work for Ubuntu? It already is not critical enough to be
> enabled on some Debian release architectures.
 Well, there were eleven tiff uploads this year (meaning one upload by
21 days on average) and two uploads in 2021. You already have a quite
simple patch to apply. How much burden would that be on Ubuntu? Can I
do the tiff uploads for Ubuntu as well? That would get some pressure
out of you guys.

> Most people using Debian should be using amd64.
 I don't have statistics, but that's the most common machine type
nowadays. It doesn't mean it's not allowed to use any other
architecture with Debian.

Regards,
Laszlo/GCS

Bug#1014084: unknown-horizons: Crashes with "AttributeError: module 'collections' has no attribute 'Iterable'"

[Tobias Frost]

Control: block -1 by 1018233
Control: affects 1018233 unknown-horizons

Tried to look into it, however cant debug it until #1018233 is solved.

--
tobi

Bug#983228: unknown-horizons: Syntax warning while installing update

[Tobias Frost]

Control: reassign -1 src:fife
Control: forcemerge 993132 -1
Control: affects -1 unknown-horizons

This seems to be #993132.

Bug#1018274: gnome-shell-extension-panel-osd: unmaintained upstream

[Simon McVittie]

Source: gnome-shell-extension-panel-osd
Version: 1.0.50.gc032923-1
Severity: important
Tags: upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: unmaintained-upstream

The Gitlab project https://gitlab.com/jenslody/gnome-shell-extension-panel-osd
referred to by this package's Homepage field has been archived, meaning
that it no longer accepts code contributions or issue reports.

For this extension to have a future, someone (perhaps its Debian maintainer
or perhaps unrelated) will need to fork the project and continue development.

smcv

Bug#1018275: gnome-shell-extension-pixelsaver: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-pixelsaver
Version: 1.28-3
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension has not been checked for compatibility with GNOME Shell
43. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018276: gnome-shell-extension-shortcuts: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-shortcuts
Version: 1.3.2-1
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43
Forwarded: 
https://gitlab.com/paddatrapper/shortcuts-gnome-extension/-/commit/287d8c9ebb5cfc0bc8ee1e7c3a5860a0858590b0

This extension's apt/dpkg dependencies say it is compatible with all
versions of GNOME Shell, but its metadata disagrees and does not list
GNOME Shell 43 as a compatible version. From the upstream git repo, it
looks like it only needs a metadata update and not any more substantial
code changes.

GNOME Shell 43 is available in experimental (as a beta version) and is
expected to be uploaded to unstable soon (transition:
https://bugs.debian.org/1018118).

I'd recommend adding dependencies on

gnome-shell (>= x), gnome-shell (<< y~)

for suitable values of x and y, so that it can only be co-installed with
versions of GNOME Shell for which compatibility has been checked.
For version 1.3.2-1 the appropriate dependency seems to be

gnome-shell (>= 3.22), gnome-shell (<< 43~)

but obviously this will change when compatibility with version 43
is added.

smcv

Bug#1018286: gnome-shell-extension-weather: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-weather
Version: 0.0~git20210509.d714eb1-4
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension has not been checked for compatibility with GNOME Shell
43. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018246: freeradius 3.0.17+dfsg-1.1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018246 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: freeradius
Version: 3.0.17+dfsg-1.1+deb10u1

Explanation: fix side-channel leak where 1 in 2048 handshakes fail 
[CVE-2019-13456], denial of service issue due to multithreaded BN_CTX access 
[CVE-2019-17185], crash due to non-thread safe memory allocation

Bug#1018250: eboard 1.1.3-0.4~deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018250 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: eboard
Version: 1.1.3-0.4~deb10u1

Explanation: fix segfault on engine selection

Bug#1018184: python-udatetime 0.0.16-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018184 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: python-udatetime
Version: 0.0.16-1+deb10u1

Explanation: properly link against libm library

Bug#1018185: ruby-riddle 2.3.1-2~deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018185 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: ruby-riddle
Version: 2.3.1-2~deb10u1

Explanation: allow use of "LOAD DATA LOCAL INFILE"

Bug#1018199: evemu 2.7.0-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018199 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: evemu
Version: 2.7.0-1+deb10u1

Explanation: fix build failure with recent kernel versions

Bug#1018178: gnucash 3.4-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018178 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: gnucash
Version: 3.4-1+deb10u1

Explanation: fix build failure with recent tzdata

Bug#1018179: librose-db-object-perl 0.815-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018179 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: librose-db-object-perl
Version: 0.815-1+deb10u1

Explanation: fix test failure after 6/6/2020

Bug#1018182: libhttp-cookiejar-perl 0.008-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018182 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: libhttp-cookiejar-perl
Version: 0.008-1+deb10u1

Explanation: fix build failure by increasing the expiry date of a test cookie

Bug#1018241: esorex 3.13.1-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018241 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: esorex
Version: 3.13.1-1+deb10u1

Explanation: fix testsuite failures on armhf and ppc64el caused by incorrect 
libffi usage

Bug#1018244: libnet-freedb-perl 0.10-2~deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018244 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: libnet-freedb-perl
Version: 0.10-2~deb10u1

Explanation: change the default host from the defunct freedb.freedb.org to 
gnudb.gnudb.org

Bug#1016733: buster-pu: package nvidia-graphics-drivers-legacy-390xx/390.154-1~deb10u1

[Adam D. Barratt]

On Wed, 2022-08-24 at 20:41 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sat, 2022-08-06 at 14:30 +0200, Andreas Beckmann wrote:
> > Another new upstream release, fixing some CVEs, again ...
> > This is a rebuild of the package from sid with no further changes.
> > Packaging changes include a simplification of the generation of the
> > -source package, i.e. less duplication of cofiguration that neweds
> > to
> > be
> > kept in sync. There is also an autopkgtest for the -source package
> > now,
> > but it might fail like the -dkms one on buster.
> > 
> > The buster upload will get an additional rebuild-for-buster
> > changelog
> > entry for version 390.154-1~deb10u1.
> > 
> 
> Please go ahead, bearing in mind that the window for getting fixes
> into the final buster point release closes over the coming weekend.
> 

Quick reminder that that's nowish. :)

Regards,

Adam

Bug#1018289: perl: FTBFS on hurd-i386: NDBM not getting linked against libgdbm-compat

[Samuel Thibault]

Package: perl
Version: 5.34.0-5
Severity: important

Hello,

perl currently FTBFS on hurd-i386: 

https://buildd.debian.org/status/fetch.php?pkg=perl=hurd-i386=5.34.0-5=1661681924=0

Failed 3 tests out of 2528, 99.88% okay.
../ext/NDBM_File/t/ndbm.t
../ext/ODBM_File/t/odbm.t
../lib/DBM_Filter/t/01error.t


They're all of the same kind:


ext/NDBM_File/t/ndbm . #   Failed 
test 'use NDBM_File;'
#   at ../../t/lib/dbmt_common.pl line 20.
# Tried to use 'NDBM_File'.
# Error:  Can't load '../../lib/auto/NDBM_File/NDBM_File.so' for module 
NDBM_File: ../../lib/auto/NDBM_File/NDBM_File.so: undefined symbol: dbm_nextkey 
at ../../lib/XSLoader.pm line 93.
#   at ../../lib/NDBM_File.pm line 12.
# Compilation failed in require at ../../t/lib/dbmt_common.pl line 20.
# BEGIN failed--compilation aborted at ../../t/lib/dbmt_common.pl line 20.
NDBM_File must define either a TIEHASH() or a new() method at 
../../t/lib/dbmt_common.pl line 38.
Compilation failed in require at t/ndbm.t line 5.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 2.
FAILED at test 1


dbm_nextkey is properly in libgdbm_compat.so, but NDBM_File.so is not
getting linked against it:


./miniperl -Ilib make_ext.pl lib/auto/NDBM_File/NDBM_File.so  MAKE="make" 
LIBPERL_A=libperl.a LINKTYPE=dynamic
Warning (mostly harmless): No library found for -lndbm
Warning (mostly harmless): No library found for -ldbm
Warning (mostly harmless): No library found for -lucb
Generating a Unix-style Makefile
Writing Makefile for NDBM_File
make[3]: Entering directory '/<>/build-static/ext/NDBM_File'
Running Mkbootstrap for NDBM_File ()
chmod 644 "NDBM_File.bs"
/<>/build-static/ext/NDBM_File/../../miniperl "-I../../lib" 
-MExtUtils::Command::MM -e 'cp_nonempty' -- NDBM_File.bs 
../../lib/auto/NDBM_File/NDBM_File.bs 644
"../../miniperl" "-I../../lib" "../../lib/ExtUtils/xsubpp" -noprototypes 
-typemap 
'/<>/build-static/ext/NDBM_File/../../lib/ExtUtils/typemap' 
-typemap '/<>/build-static/ext/NDBM_Fi
mv NDBM_File.xsc NDBM_File.c
i686-gnu-gcc -c   -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-DAPPLLIB_EXP="/usr/lib/i386-gnu/perl-base" -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wforma
rm -f ../../lib/auto/NDBM_File/NDBM_File.so
i686-gnu-gcc  -shared -Wl,-z,relro -L/usr/local/lib -fstack-protector-strong  
NDBM_File.o  -o ../../lib/auto/NDBM_File/NDBM_File.so  \
  \

chmod 755 ../../lib/auto/NDBM_File/NDBM_File.so


while on linux ports it looks like that:

rm -f ../../lib/auto/NDBM_File/NDBM_File.so
x86_64-linux-gnu-gcc  -shared -Wl,-z,relro -L/usr/local/lib 
-fstack-protector-strong  NDBM_File.o  -o ../../lib/auto/NDBM_File/NDBM_File.so 
 \
   -lgdbm -lgdbm_compat   \


Notably on hurd there aren't the "harmless" messages about -ldbm ; it's
supposed to use -lgdbm_compat, as hinted from hints/linux.pl, sourced
from hints/gnu.pl, but for some reason this isn't working any more?

Samuel

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), 
(500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 5.19.0 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_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)
LSM: AppArmor: enabled

Versions of packages perl depends on:
ii  dpkg   1.21.9
ii  libperl5.345.34.0-5
ii  perl-base  5.34.0-5
ii  perl-modules-5.34  5.34.0-5

Versions of packages perl recommends:
ii  netbase  6.3

Versions of packages perl suggests:
pn  libtap-harness-archive-perl  
ii  libterm-readline-gnu-perl1.42-2+b1
ii  make 4.3-4.1
ii  perl-doc 5.34.0-5

-- no debconf information

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.

Bug#1018263: gawk: CONVFMT used instead of OFMT for 'print $0'

[Francesco Potortì]

Package: gawk
Version: 1:5.1.0-1
Severity: normal
X-Debbugs-Cc: none, Francesco Potortì 

Dear Maintainer,

I observe this:

$  echo 8.746 | gawk '{$1+='463405.85';print $0}'
463415

This one round the result to six significant digits, as teh default output 
format is "%.6g".  To
change this for 'print' , one should change OFMT, like this:

$  echo 8.746 | gawk 'BEGIN{OFMT="%.12g"}{$1+='463405.85';print $0}'
463415

But this has no effect.  This is a bug.  TO get the right effect, one has to 
change CONVFMT,
like this:

$  echo 8.746 | gawk 'BEGIN{CONVFMT="%.12g"}{$1+='463405.85';print $0}'
463414.596

-- 
Francesco Potortì (ricercatore)Voice:  +39.050.621.3058
ISTI - Area della ricerca CNR  Mobile: +39.348.8283.107
via G. Moruzzi 1, I-56124 Pisa Skype:  wnlabisti
(gate 20, 1st floor, room C71) Web:http://fly.isti.cnr.it



-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (101, 'unstable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gawk depends on:
ii  libc6 2.34-4
ii  libgmp10  2:6.2.1+dfsg1-1
ii  libmpfr6  4.1.0-3
ii  libreadline8  8.1.2-1.2
ii  libsigsegv2   2.14-1

gawk recommends no packages.

Versions of packages gawk suggests:
ii  gawk-doc  5.1.0-1

-- no debconf information

Bug#966108: genesisplusgx: FTBFS with GCC 10: multiple definition of ... due to -fno-common

[Tobias Frost]

Control: fixed -1 1.7.4+git20160410-3
Control: tags -1 +pending 

Fixed in the VCS: https://salsa.debian.org/games-team/genesisplusgx

(Uploaded already, but unsure if the buildds will pick it up yet)

Bug#1018265: cups picks manual tray on HP Color LaserJet M252dw

[Steinar Bang]

Package: cups
Version: 2.3.3op2-3+deb11u2
Severity: important
X-Debbugs-Cc: s...@dod.no

Dear Maintainer,

When printing, the printer picks what it calls "Tray 1", which is a slot in the
front of the printer, where sheets can be fed one at a time. After feeding a
sheet in, I have to press "OK" on the printer's front panel display.

This has to be repeated for each sheet printed and makes it cumbersome to use
the printer.

I have opened "System->Administration->Print Settings" from the debian menu.

I have double clicked on the printer HP_Color_LaserJet_Pro_M252dw_501595_

In "Printer Properties"->"Print Options" there is the setting "Media source".

"Media source" is a dropdown with the values
 Automatic
 Manual
 Tray 1
 Tray 2

I have tried the settings "Automatic" (the default) and "Tray 1" and
"Tray 2" and all of them uses the manual tray, which the printer display
calls "Tray 1".

There was no change. The printer still printed from the manual tray

I had expected "Tray 2" and "Automatic" to pick "Tray 2", which is the regular
paper tray.

Cups report the printer as HP Color LaserJet Pro M252dw, driverless, cups-
filters 1.28.7 (so driverless.ppd is in use. This is a network printer with
PostScript).

I don't know when this behaviour started, but I can't remember needing to feed
paper manually in December/November 2021, when I printed the Christmas letters.

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

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

Versions of packages cups depends on:
ii  cups-client2.3.3op2-3+deb11u2
ii  cups-common2.3.3op2-3+deb11u2
ii  cups-core-drivers  2.3.3op2-3+deb11u2
ii  cups-daemon2.3.3op2-3+deb11u2
ii  cups-filters   1.28.7-1+deb11u1
ii  cups-ppdc  2.3.3op2-3+deb11u2
ii  cups-server-common 2.3.3op2-3+deb11u2
ii  debconf [debconf-2.0]  1.5.77
ii  ghostscript9.53.3~dfsg-7+deb11u2
ii  libavahi-client3   0.8-5
ii  libavahi-common3   0.8-5
ii  libc6  2.31-13+deb11u3
ii  libcups2   2.3.3op2-3+deb11u2
ii  libgcc-s1  10.2.1-6
ii  libstdc++6 10.2.1-6
ii  libusb-1.0-0   2:1.0.24-3
ii  poppler-utils  20.09.0-3.1
ii  procps 2:3.3.17-5

Versions of packages cups recommends:
ii  avahi-daemon  0.8-5
ii  colord1.4.5-3

Versions of packages cups suggests:
pn  cups-bsd   
pn  cups-pdf   
pn  foomatic-db-compressed-ppds | foomatic-db  
pn  smbclient  
ii  udev   247.3-7

-- debconf information:
  cupsys/raw-print: true

Bug#1018280: gnome-shell-extension-tiling-assistant: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-tiling-assistant
Version: 35-1
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension has not been checked for compatibility with GNOME Shell
43. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018281: calamares: Add accessibility support

[Roland Clobus]

Package: calamares
Version: Add accessibility support
Severity: wishlist
Tags: a11y

Hello Jonathan,

on the Debian-live mailing list [1] the question was raised to add an
alternative installer inside the live image.
In the following replies, the question was raised whether that installer would
have accessibility support, since Calamares doesn't have any.

Would it be possible/feasible to add accessibility support to Calamares?

With kind regards,
Roland Clobus

[1] https://lists.debian.org/debian-live/2022/08/msg00017.html


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (50, 'unstable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages calamares depends on:
ii  kpackagetool5  5.97.0-1
pn  libboost-python1.74.0  
ii  libc6  2.34-4
ii  libcrypt1  1:4.4.28-2
ii  libgcc-s1  12.1.0-8
ii  libkf5configcore5  5.97.0-2
ii  libkf5coreaddons5  5.97.0-1
ii  libkf5package5 5.97.0-1
ii  libkf5parts5   5.97.0-1
pn  libkpmcore11   
pn  libkpmcore12   
ii  libparted2 3.5-1
ii  libpwquality1  1.4.4-1+b1
ii  libpython3.10  3.10.6-1
ii  libqt5core5a   5.15.4+dfsg-5
ii  libqt5dbus55.15.4+dfsg-5
ii  libqt5gui5 5.15.4+dfsg-5
ii  libqt5network5 5.15.4+dfsg-5
ii  libqt5qml5 5.15.4+dfsg-4
ii  libqt5quick5   5.15.4+dfsg-4
ii  libqt5quickwidgets55.15.4+dfsg-4
ii  libqt5svg5 5.15.4-2
pn  libqt5webkit5  
ii  libqt5widgets5 5.15.4+dfsg-5
ii  libqt5xml5 5.15.4+dfsg-5
ii  libstdc++6 12.1.0-8
ii  libyaml-cpp0.7 0.7.0+dfsg-8
ii  os-prober  1.81

Versions of packages calamares recommends:
ii  btrfs-progs 5.18.1-1
ii  squashfs-tools  1:4.5.1-1

calamares suggests no packages.

Bug#1018279: python3-testpath: Empty binary package

[Gordon Ball]

Package: python3-testpath
Version: 0.6.0+dfsg-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: gor...@chronitis.net


The package is empty except for the changelog.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Bug#1018277: gnome-shell-extension-sound-device-chooser: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-sound-device-chooser
Version: 43-1
Severity: important
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

This extension has not been checked for compatibility with GNOME Shell
43. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018278: gnome-shell-extension-system-monitor: needs update for GNOME Shell 43

[Simon McVittie]

Package: gnome-shell-extension-system-monitor
Version: 40-4
Severity: important
Tags: bookworm sid upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43
Forwarded: 
https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/issues/749

This extension has not been checked for compatibility with GNOME Shell
43, and from the upstream issue report linked above, it seems that it
will need code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME Shell
43 transition (see https://bugs.debian.org/1018118 for details). This bug
will be raised to serious severity when the transition is ready to go ahead.

smcv

Bug#1018265: Tried fix from cups-filters issue #193, but it didn't work

[Steinar Bang]

I tried the fix in https://github.com/OpenPrinting/cups-filters/issues/193
but it didn't work.

What I did was:
 1. Edit /etc/cups/ppd/HP_Color_LaserJet_Pro_M252dw_501595_.ppd with the
following changes:

--- HP_Color_LaserJet_Pro_M252dw_501595_.ppd2022/08/28 10:29:57 1.1
+++ HP_Color_LaserJet_Pro_M252dw_501595_.ppd2022/08/28 10:47:19
@@ -144,8 +144,8 @@
 *DefaultInputSlot: Auto
 *InputSlot Auto/Automatic: "<>setpagedevice"
 *InputSlot Manual/Manual: "<>setpagedevice"
-*InputSlot Tray1/Tray 1: "<>setpagedevice"
-*InputSlot Tray2/Tray 2: "<>setpagedevice"
+*InputSlot Tray-1/Tray 1: "<>setpagedevice"
+*InputSlot Tray-2/Tray 2: "<>setpagedevice"
 *CloseUI: *InputSlot
 *% ColorModel from urf-supported
 *OpenUI *ColorModel/Print Color Mode: PickOne

 2. Restart cups with
 systemctl restart cups

 3. Try printing a testpage from the printers properties, with the
printer's media source set to "Automatic" (the default)

 4. The printer was waiting for the manual tray/slot to be fed, and "OK"
to be pressed on the front panel

 5. I fed the printer a sheet of paper and pressed "OK"

 6. I selected "Tray 2" as the media source and pressed "Apply"

 7. I tried printing a test page

 8. Again the printer was waiting for the manual tray/slot to be fed,
and "OK" to be pressed on the front panel

 9. I fed the printer a sheet of paper and pressed "OK"

10. I selected "Tray 1" as the media source and pressed "Apply" (just to
have tried it)

11. Again the printer was waiting for the manual tray/slot to be fed,
and "OK" to be pressed on the front panel

When I checked the diffs again after the experiment, I found that my
changes to /etc/cups/ppd/HP_Color_LaserJet_Pro_M252dw_501595_.ppd
had been overwritten.

Bug#1017795: mmdebstrap hangs when apt cannot resolve dependencies

[Johannes Schauer Marin Rodrigues]

Control: tag -1 + patch

Hi,

On Sun, 21 Aug 2022 09:52:41 +0200 Gioele Barabucci  wrote:
> I can replicate this issue with the following invocation of mmdebstrap:

thank you! I'm attaching the patch that fixes this problem because I cannot
upload a new mmdebstrap version yet as I have to wait for systemd to migrate to
testing first.

Thanks!diff --git a/mmdebstrap b/mmdebstrap
index 9894a9e..fb7c412 100755
--- a/mmdebstrap
+++ b/mmdebstrap
@@ -979,46 +979,59 @@ sub run_apt_download_progress {
 my $flags = fcntl($wfh, F_GETFD, 0)or error "fcntl F_GETFD: $!";
 fcntl($wfh, F_SETFD, $flags & ~FD_CLOEXEC) or error "fcntl F_SETFD: $!";
 my $fd = fileno $wfh;
-# 2022-05-02, #debian-apt on OFTC, times in UTC+2
-# 16:57 < josch> DonKult: how is -oDebug::pkgDpkgPm=1 -oDir::Log=/dev/null
-#a "fancy no-op"?
-# 11:52 < DonKult> josch: "fancy no-op" in sofar as it does nothing to the
-#  system even through its not in a special mode ala
-#  simulation or download-only. It does all the things it
-#  normally does, except that it just prints the dpkg calls
-#  instead of execv() them which in practice amounts means
-#  it does nothing (the Dir::Log just prevents libapt from
-#  creating the /var/log/apt directories. As the code
-#  creates them even if no logs will be placed there…). As
-#  said, midterm an apt --print-install-packages or
-#  something would be nice to avoid running everything.
-run_apt_progress({
-ARGV => [
-'apt-get',
-'--yes',
-'-oDebug::pkgDpkgPm=1',
-'-oDir::Log=/dev/null',
-$options->{dryrun}
-? '-oAPT::Get::Simulate=true'
-: (
-"-oAPT::Keep-Fds::=$fd",
-"-oDPkg::Tools::options::'cat >&$fd'::InfoFD=$fd",
-"-oDpkg::Pre-Install-Pkgs::=cat >&$fd",
-# no need to lock the database if we are just downloading
-"-oDebug::NoLocking=1",
-# no need for pty magic if we write no log
-"-oDpkg::Use-Pty=0",
-),
-@{ $options->{APT_ARGV} },
-],
-});
+# run_apt_progress() can raise an exception which would leave this function
+# without cleaning up the other thread we started, making mmdebstrap hang
+# in case run_apt_progress() fails -- so wrap this in eval() instead
+eval {
+# 2022-05-02, #debian-apt on OFTC, times in UTC+2
+# 16:57 < josch> DonKult: how is -oDebug::pkgDpkgPm=1
+#-oDir::Log=/dev/null a "fancy no-op"?
+# 11:52 < DonKult> josch: "fancy no-op" in sofar as it does nothing to
+#  the system even through its not in a special mode
+#  ala simulation or download-only. It does all the
+#  things it normally does, except that it just prints
+#  the dpkg calls instead of execv() them which in
+#  practice amounts means it does nothing (the Dir::Log
+#  just prevents libapt from creating the /var/log/apt
+#  directories. As the code creates them even if no
+#  logs will be placed there…). As said, midterm an apt
+#  --print-install-packages or something would be nice
+#  to avoid running everything.
+run_apt_progress({
+ARGV => [
+'apt-get',
+'--yes',
+'-oDebug::pkgDpkgPm=1',
+'-oDir::Log=/dev/null',
+$options->{dryrun}
+? '-oAPT::Get::Simulate=true'
+: (
+"-oAPT::Keep-Fds::=$fd",
+"-oDPkg::Tools::options::'cat >&$fd'::InfoFD=$fd",
+"-oDpkg::Pre-Install-Pkgs::=cat >&$fd",
+  # no need to lock the database if we are just downloading
+"-oDebug::NoLocking=1",
+# no need for pty magic if we write no log
+"-oDpkg::Use-Pty=0",
+),
+@{ $options->{APT_ARGV} },
+],
+});
+};
+my $err = '';
+if ($@) {
+$err = "apt download failed: $@";
+}
 # signal the child process that we are done
 close $wfh;
 # and then read from it what it got
 my @listofdebs = <$fh>;
 close $fh;
 if ($? != 0) {
-error "status child failed";
+$err = "status child failed";
+}
+if ($err) {
+error $err;
 }
 # remove trailing newlines

Bug#1018265: cups picks manual tray on HP Color LaserJet M252dw

[Brian Potkin]

On Sun 28 Aug 2022 at 11:24:51 +0200, Steinar Bang wrote:

> Package: cups
> Version: 2.3.3op2-3+deb11u2
> Severity: important
> X-Debbugs-Cc: s...@dod.no

Thank you for your report, Steinar.
 
> Dear Maintainer,
> 
> When printing, the printer picks what it calls "Tray 1", which is a slot in 
> the
> front of the printer, where sheets can be fed one at a time. After feeding a
> sheet in, I have to press "OK" on the printer's front panel display.
> 
> This has to be repeated for each sheet printed and makes it cumbersome to use
> the printer.
> 
> I have opened "System->Administration->Print Settings" from the debian menu.
> 
> I have double clicked on the printer HP_Color_LaserJet_Pro_M252dw_501595_
> 
> In "Printer Properties"->"Print Options" there is the setting "Media source".
> 
> "Media source" is a dropdown with the values
>  Automatic
>  Manual
>  Tray 1
>  Tray 2
> 
> I have tried the settings "Automatic" (the default) and "Tray 1" and
> "Tray 2" and all of them uses the manual tray, which the printer display
> calls "Tray 1".
> 
> There was no change. The printer still printed from the manual tray
> 
> I had expected "Tray 2" and "Automatic" to pick "Tray 2", which is the regular
> paper tray.
> 
> Cups report the printer as HP Color LaserJet Pro M252dw, driverless, cups-
> filters 1.28.7 (so driverless.ppd is in use. This is a network printer with
> PostScript).
> 
> I don't know when this behaviour started, but I can't remember needing to feed
> paper manually in December/November 2021, when I printed the Christmas 
> letters.

Please take this issue upstream:

  https://github.com/OpenPrinting/cups-filters/issues

would be worth a try. A short explanation of the issue plus a link
to the Debian bug report should be sufficient.

Regards,

Brian.

Bug#1014581: systemd-boot: kernel hook schould use conforming name

[Victor Westerhuis]

On Tue, 19 Jul 2022 21:29:06 +0200 Michael Biebl  wrote:

Am 12.07.22 um 18:16 schrieb Michael Biebl:
> Control: tags -1 + moreinfo
> 
> Am 08.07.22 um 11:14 schrieb Norbert Lange:

>> Package: systemd-boot
>> Version: 251.2-7
>> Severity: normal
>> X-Debbugs-Cc: nolang...@gmail.com
>>
>> Dear Maintainer,
>>
>> The kernel hook in /etc/kernel/{post,pre}inst.d should
>> be named correctly, to quote the kernel-handbook [1]:
>>
>>>    hook scripts for boot loaders must be named using
>>  the prefix zz- and no other packages may use this prefix
>>
>> so zz-systemd-boot whould be correct.
> 
> This looks super ugly :-/

> At the very least they should have picked numerical prefixes...
> 
> That said, why does the kernel hook need to run late/last? I.e., does 
> this actually cause any real issues? If so, can you elaborate.
> 

I looked into this a bit more and it is still not obvious/clear to me, 
why the kernel hook for systemd needs to use the zz prefix (i.e. run 
late/last). The systemd kernel hook copies the vmlinux-* binary to 
/boot/efi, but this file is available once the linux-image-* package has 
been unpacked.


That said, I could understand if the initramfs hook needs to run last, 
i.e. /etc/initramfs/post-update.d/systemd-boot. As this hook will copy 
the initrd to /boot/efi and initramfs hooks *do* modify the initrd image.
The kernel handbook doesn't mention anything in that regard though, so 
it seems to be incomplete/wrong for the purposes of systemd-boot?
I recently switched from initramfs-tools to tiny-initramfs to generate 
my initramfs. update-tirfs, contrary to the policy, does not run the 
hooks in /etc/initramfs/post-update.d. However, at least when a kernel 
is being installed, updated or removed these hooks are allowed to skip 
doing any work anyway, according to section 8.5 of the Debian kernel 
handbook.


This means that only step 3, running the hooks in 
/etc/kernel/post{inst,rm}.d are required to do anything.


The issue is that tiny-initramfs sorts after systemd-boot, so the initrd 
is only generated after systemd-boot has tried to copy it already, 
leading to a missing initrd on the first try.


I've solved the issue locally by moving systemd-boot's 
/etc/kernel/post{inst,rm}.d hooks to the name prescribed by policy.


I will also file a corresponding bug (with patch) against tiny-initramfs 
to fix the running of the hooks in /etc/initramfs/post-update.d.



I'm reluctant to blindly change anything without understanding why.
So would welcome further input from someone who is familiar with that topic.

Regards,
Michael



Regards,
--
Victor Westerhuis 


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1018226: dlt-daemon 2.18.6-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018226 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: dlt-daemon
Version: 2.18.6-1+deb11u1

Explanation: fix double free issue [CVE-2022-31291]

Bug#1018227: gri 2.12.27-1.1~deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1018227 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: gri
Version: 2.12.27-1.1~deb11u1

Explanation: use ps2pdf instead of convert for converting from ps to pdf

Bug#1018259: nmu: libidn2_2.3.3-1

[Johannes Schauer Marin Rodrigues]

Quoting Cyril Brulebois (2022-08-28 13:18:05)
> Johannes Schauer Marin Rodrigues  (2022-08-28):
> > due to a bug in debhelper (see #1015263) the libidn2-0 package gained a
> > wrong dependency on sgml-base. Since there was no upload of libidn2
> > since the bug got fixed in debhelper, the current version on unstable
> > still wrongly depends on sgml-base. This breaks di-builds because
> > sgml-base doesn't exist in udeb context. This added dependency also
> > hurts bootstrapping and breaks our DPKG_ROOT CI. Please rebuilds libidn2
> > with the current debhelper version.
> > 
> > nmu libidn2_2.3.3-1 . ANY . unstable . -m "rebuild with debhelper after 
> > #1015263 was fixed"
> 
> I'm a little confused.
> 
> d-i builds are all green:
>   https://d-i.debian.org/daily-images/daily-build-overview.html
> 
> and more importantly, src:libidn2 doesn't build any udeb.
> 
> 
> Note that I'm not objecting to the rebuild, I'm just not sure the context
> is right… libnl3 was building a broken udeb though, for which I uploaded
> a workaround:
>   
> https://tracker.debian.org/news/1353402/accepted-libnl3-370-02-source-into-unstable/

The current version of libidn2-0 in unstable still wrongly depends on
sgml-base. A rebuild of src:libidn2 against the version of debhelper that is
currently in the archive will fix this problem.

I added you to CC because you commented on #1015263 saying "This breaks d-i
builds". The thing that doesn't have a udeb is sgml-base (which you pointed out
in the same message).

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1016837: avahi 0.8-5+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1016837 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: avahi
Version: 0.8-5+deb11u1

Explanation: fix display of URLs containing '&' in avahi-discover; do not 
disable timeout cleanup on watch cleanup; fix NULL pointer crashes when trying 
to resolve badly-formatted hostnames [CVE-2021-3502]

Bug#1016786: systemd 247.3-7+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1016786 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: systemd
Version: 247.3-7+deb11u1

Explanation: drop bundled copy of linux/if_arp.h, fixing build failures with 
newer kernel headers; support detection for ARM64 Hyper-V guests; detect 
OpenStack instance as KVM on arm

Bug#1017777: glibc 2.31-13+deb11u4 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 101 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: glibc
Version: 2.31-13+deb11u4

Explanation: fix an off-by-one buffer overflow/underflow in getcwd() 
[CVE-2021-3999]; fix several overflows in wide character functions; add a few 
EVEX optimized string functions to fix a performance issue (up to 40%) with 
Skylake-X processors; make grantpt usable after multi-threaded fork; ensure 
that libio vtable protection is enabled

Bug#719236: dh-python: shebang rewriting can't ignore paths with -X

[Étienne Millon]

Hi,
Thanks for the reply. I think we can close this one then.

On Thu, Aug 18, 2022 at 6:43 PM Stefano Rivera  wrote:

> Control: tag -1 + wontfix
> Control: severity -1 wishlist
>
> Hi Etienne (2013.08.09_16:53:34_+0200)
> > I am trying to use shebang rewriting on a package (rss2email) which
> > ships two binaries in /usr/bin, one written in python3 and one written
> > in python2.
>
> Fortunately this isn't a thing one needs to do any more :)
>
> > but unfortunately it gets rewritten anyway. It seems to me that for
> > shebang rewriting, -X is ignored, but I'm not sure if this is supposed
> > to work or not.
>
> Nope, -X is only expected to apply to byte-compilation.
>
> SR
>
> --
> Stefano Rivera
>   http://tumbleweed.org.za/
>   +1 415 683 3272
>

Bug#958729: testdisk: Please consider migrating away from old -dbg debug packages

[Aurelien Jarno]

control: tag -1 +pending

Dear maintainer,

On 2020-04-24 14:37, Boyuan Yang wrote:
> Source: testdisk
> Version: 7.1-5
> Severity: minor
> X-Debbugs-CC: kelb...@debian.org
> 
> Dear Debian testdisk maintainer,
> 
> I noticed that your package is still shipping a testdisk-dbg package, which is
> the old-style debug package. Please consider migrating to the new automatic
> -dbgsym package.
> 
> The detail about this migration can be found at 
> https://wiki.debian.org/AutomaticDebugPackages .

I have uploaded a NMU fixing this issue to DELAYED/15, as it is one of
the last packages preventing the switch of libc6-dbg to a dbgsym
package. Please find the corresponding debdiff attached. Also please
feel free to ask me to delay or cancel this NMU.

Regards,
Aurelien


-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru testdisk-7.1/debian/changelog testdisk-7.1/debian/changelog
--- testdisk-7.1/debian/changelog   2019-08-21 22:24:34.0 +0200
+++ testdisk-7.1/debian/changelog   2022-08-28 13:39:34.0 +0200
@@ -1,3 +1,11 @@
+testdisk (7.1-5+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Replace testdisk-dbg package by automatic testdisk-dbgsym package.
+Closes: #958729.
+
+ -- Aurelien Jarno   Sun, 28 Aug 2022 11:39:34 +
+
 testdisk (7.1-5) unstable; urgency=medium
 
   * Re-upload with the correct patch to build on kfreebsd-*
diff -Nru testdisk-7.1/debian/control testdisk-7.1/debian/control
--- testdisk-7.1/debian/control 2019-08-11 16:18:55.0 +0200
+++ testdisk-7.1/debian/control 2022-08-28 13:38:31.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Jean-Michel Kelbert 
 Uploaders: Roland Stigge 
-Build-Depends: debhelper (>= 9), e2fslibs-dev (>= 1.35-3), libncurses5-dev, 
libncursesw5-dev, ntfs-3g-dev [!hurd-i386], libjpeg-dev, uuid-dev, zlib1g-dev, 
dh-autoreconf, pkg-config
+Build-Depends: debhelper (>= 9.20160114), e2fslibs-dev (>= 1.35-3), 
libncurses5-dev, libncursesw5-dev, ntfs-3g-dev [!hurd-i386], libjpeg-dev, 
uuid-dev, zlib1g-dev, dh-autoreconf, pkg-config
 Standards-Version: 4.3.0
 
 Package: testdisk
@@ -64,20 +64,3 @@
   * Microsoft ASF (.wma)
   * Sigma/Foveon X3 raw picture (.x3f)
   * zip archive (.zip)
-
-Package: testdisk-dbg
-Section: debug
-Priority: optional
-Architecture: any
-Depends: testdisk (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
-Suggests: libc6-dbg, e2fslibs-dbg, libcomerr2-dbg, libjpeg-dbg,
- libncursesw5-dbg, libssl0.9.8-dbg, zlib1g-dbg
-Description: Partition scanner and disk recovery tool, and PhotoRec file 
recovery tool
- TestDisk checks the partition and boot sectors of your disks.
- It is very useful in forensics, recovering lost partitions.
- .
- PhotoRec is file data recovery software designed to recover
- lost pictures from digital camera memory or even Hard Disks.
- It has been extended to search also for non audio/video headers.
- .
- This package includes the debugging symbols.
diff -Nru testdisk-7.1/debian/rules testdisk-7.1/debian/rules
--- testdisk-7.1/debian/rules   2019-08-06 15:39:36.0 +0200
+++ testdisk-7.1/debian/rules   2022-08-28 13:39:34.0 +0200
@@ -13,7 +13,7 @@
dh_auto_configure -- --enable-sudo --with-sudo-bin=/usr/bin/sudo 
--with-ncurses-includes=/usr/include/ncursesw --without-ewf
 
 override_dh_auto_install:
-   dh_auto_install
+   dh_auto_install --destdir=debian/tmp
rm -f $(CURDIR)/debian/tmp/usr/share/doc/testdisk/ChangeLog
rm -f $(CURDIR)/debian/tmp/usr/share/doc/testdisk/COPYING
rm -f $(CURDIR)/debian/tmp/usr/share/doc/testdisk/INSTALL
@@ -23,4 +23,4 @@
-rm -f src/*.d
 
 override_dh_strip:
-   dh_strip --dbg-package=testdisk-dbg
+   dh_strip --dbgsym-migration='testdisk-dbg (<< 7.1-5+nmu1~)'


signature.asc
Description: PGP signature

Bug#1017698: Acknowledgement (emacsen-common: core dump with unsorted double linked list corrupted)

[Tom Overlund]

I also got a segfault on upgrading to emacs 28.1. I fixed it by installing the 
emacs-el package -- which is 
recommended, but I default install all packages without recommends. Apparently 
this has something to do with 
native compilation, which requires the el source files:

https://github.com/kelleyk/ppa-emacs/issues/23

emacs-el should be changed from recommended to a hard dependency.

Bug#1018259: nmu: libidn2_2.3.3-1

[Johannes Schauer Marin Rodrigues]

Quoting Cyril Brulebois (2022-08-28 14:20:48)
> Johannes Schauer Marin Rodrigues  (2022-08-28):
> > The current version of libidn2-0 in unstable still wrongly depends on
> > sgml-base. A rebuild of src:libidn2 against the version of debhelper
> > that is currently in the archive will fix this problem.
> 
> Sure, that's the part I agree with.
> 
> > I added you to CC because you commented on #1015263 saying "This breaks
> > d-i builds". The thing that doesn't have a udeb is sgml-base (which you
> > pointed out in the same message).
> 
> Let's backpedal a bit, my message had:
> 
> > Judging by the current list of `apt-cache rdepends sgml-base`, this
> > problem has already spread quite a bit.
> 
> This breaks d-i builds, (at least) via libnl udebs picking up a
> dependency on sgml-base, which doesn't exist in a udeb context.
> 
> There, “this” = buggy sgml-base dependency spreading, which broke d-i
> builds *via libnbl udebs* (which was worked around); that wasn't meant
> to mean that libidn2 itself was breaking d-i builds. It can't, as it
> doesn't build udebs, so it's no factor.
> 
> Hope that clarifies.

Ah cool, thanks! Yes, then d-i is not a reason at all to binNMU src:libidn2.

The wrong dependency on sgml-base remains as a reason to do it.

Thank you!

cheers, josch

signature.asc
Description: signature

Bug#1018297: surf: Switch to webkit 4.1

[Jeremy Bicha]

Source: surf
Version: 2.1+git20220504-1
Tags: bookworm sid patch

In my follow-up email, I'm attaching patches to allow building surf
with webkit2gtk 4.1.

The webkit2gtk 4.1 API is the same as webkit2gtk 4.0 but uses libsoup3
instead of libsoup2.4.

Eventually, we want to speed up our builds of webkit2gtk by dropping
the 4.0 option.

Thank you,
Jeremy Bicha

Bug#1013744: bullseye-pu: package ifenslave/2.13~deb11u1

[Jonathan Wiltshire]

Control: tag -1 confirmed moreinfo

On Sat, Jun 25, 2022 at 10:51:24AM +0200, Salvatore Bonaccorso wrote:
> In the same upload a couple of other bugfixes were done which seem
> sensible to include, so instead of cherry-picking the two changes I
> would like to propose a rebase to 2.13 for bullseye as well:

Please go ahead. I'd also be happy with a straight rebuild of testing,
given the minimal changes.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Bug#1016413: bullseye-pu: package libreoffice/1:7.0.4-4+deb11u3

[Rene Engelhard]

Hi again,

Am 28.08.22 um 17:56 schrieb Rene Engelhard:

Am 28.08.22 um 17:46 schrieb Rene Engelhard:

Am 31.07.22 um 16:44 schrieb Rene Engelhard:
This is now https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016420 
(where the upstream bug which that one is marked as forwarded to has 
also the reasoning why support for < 3.16 was dropped which makes the 
patch bigger).


I now did a minimal patch (attached.) in case the original patch is 
deemed to big (which I can understand)




Hrmf. doesn't build (for whatever reason). Will investigate...


OK, got it, forgot adapt the internal EApi.h. Patch attached.

Regards,

Renediff --git a/changelog b/changelog
index 41633702..08449161 100644
--- a/changelog
+++ b/changelog
@@ -1,3 +1,10 @@
+libreoffice (1:7.0.4-4+deb11u3) stable; urgency=medium
+
+  * debian/patches/fix-e_book_client_connect_direct_sync-sig.diff:
+as name says (closes: #1016420)
+
+ -- Rene Engelhard   Sun, 28 Aug 2022 18:32:57 +0200
+
 libreoffice (1:7.0.4-4+deb11u2) stable; urgency=medium
 
   * debian/patches/hrk-euro.diff: add EUR to .hr i18n;
diff --git a/patches/fix-e_book_client_connect_direct_sync-sig.diff 
b/patches/fix-e_book_client_connect_direct_sync-sig.diff
new file mode 100644
index ..a12f915d
--- /dev/null
+++ b/patches/fix-e_book_client_connect_direct_sync-sig.diff
@@ -0,0 +1,32 @@
+diff --git a/connectivity/source/drivers/evoab2/EApi.h 
b/connectivity/source/drivers/evoab2/EApi.h
+index 8c05f95fa2ce..daed075ba80b 100644
+--- a/connectivity/source/drivers/evoab2/EApi.h
 b/connectivity/source/drivers/evoab2/EApi.h
+@@ -147,7 +147,11 @@ EAPI_EXTERN const gchar* (*eds_check_version) (guint 
required_major, guint requi
+ EAPI_EXTERN const gchar* (*e_source_get_uid) (ESource *source);
+ EAPI_EXTERN ESource* (*e_source_registry_ref_source) (ESourceRegistry 
*registry, const gchar *uid);
+ EAPI_EXTERN EBookClient* (*e_book_client_new) (ESource *source, GError 
**error);
++#if EDS_CHECK_VERSION ( 3, 16, 0)
++EAPI_EXTERN EBookClient* (*e_book_client_connect_direct_sync) 
(ESourceRegistry *registry, ESource *source, guint32 
wait_for_connected_seconds, GCancellable *cancellable, GError **error);
++#else
+ EAPI_EXTERN EBookClient* (*e_book_client_connect_direct_sync) 
(ESourceRegistry *registry, ESource *source, GCancellable *cancellable, GError 
**error);
++#endif
+ EAPI_EXTERN gboolean (*e_client_open_sync) (EClient *client, gboolean 
only_if_exists, GCancellable *cancellable, GError **error);
+ EAPI_EXTERN ESource* (*e_client_get_source) (EClient *client);
+ EAPI_EXTERN gboolean (*e_book_client_get_contacts_sync) (EBookClient *client, 
const gchar *sexp, GSList **contacts, GCancellable *cancellable, GError 
**error);
+diff --git a/connectivity/source/drivers/evoab2/NResultSet.cxx 
b/connectivity/source/drivers/evoab2/NResultSet.cxx
+index 77d53939c1aa..dc73574d8368 100644
+--- a/connectivity/source/drivers/evoab2/NResultSet.cxx
 b/connectivity/source/drivers/evoab2/NResultSet.cxx
+@@ -477,7 +477,10 @@ class OEvoabVersion38Helper : public OEvoabVersion36Helper
+ protected:
+ virtual EBookClient * createClient( ESource *pSource ) override
+ {
+-return e_book_client_connect_direct_sync (get_e_source_registry (), 
pSource, nullptr, nullptr);
++  if (eds_check_version( 3, 16, 0 ) == nullptr)
++  return e_book_client_connect_direct_sync (get_e_source_registry 
(), pSource, 10, nullptr, nullptr);
++  else
++  return e_book_client_connect_direct_sync (get_e_source_registry 
(), pSource, 10, nullptr, nullptr);
+ }
+ };
+ 
diff --git a/patches/series b/patches/series
index fa58e363..69db8a90 100644
--- a/patches/series
+++ b/patches/series
@@ -62,3 +62,4 @@ b0404f80577de9ff69e58390c6f6ef949fdb0139.patch
 0002-CVE-2022-26307-make-hash-encoding-match-decoding.patch
 0003-CVE-2022-26306-add-Initialization-Vectors-to-passwor.patch
 0004-CVE-2022-2630-6-7-add-infobar-to-prompt-to-refresh-t.patch
+fix-e_book_client_connect_direct_sync-sig.diff

Bug#1018265: cups picks manual tray on HP Color LaserJet M252dw

[Steinar Bang]

> Brian Potkin :

> Please take this issue upstream:

>   https://github.com/OpenPrinting/cups-filters/issues

> would be worth a try. A short explanation of the issue plus a link
> to the Debian bug report should be sufficient.

Ok done!

The cups-filters issue, is:
 https://github.com/OpenPrinting/cups-filters/issues/478

Bug#941248: Amended patch proposed.

[Tim Woodall]

I'd like to propose a slightly modified patch:

diff -urN bash-5.1.orig/debian/etc.bash.bashrc bash-5.1/debian/etc.bash.bashrc
--- bash-5.1.orig/debian/etc.bash.bashrc2022-03-27 18:36:06.0 
+
+++ bash-5.1/debian/etc.bash.bashrc 2022-03-27 18:36:06.0 +
@@ -4,7 +4,7 @@
 # this file has to be sourced in /etc/profile.

 # If not running interactively, don't do anything
-[ -z "$PS1" ] && return
+[[ $- = *i* ]] || return

 # check the window size after each command and, if necessary,
 # update the values of LINES and COLUMNS.
@@ -17,7 +17,7 @@

 # set a fancy prompt (non-color, overwrite the one in /etc/profile)
 # but only if not SUDOing and have SUDO_PS1 set; then assume smart user.
-if ! [ -n "${SUDO_USER}" -a -n "${SUDO_PS1}" ]; then
+if ! [ -n "${SUDO_USER:-}" -a -n "${SUDO_PS1:-}" ]; then
   PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
 fi


which avoids the assumption that an interactive shell always has PS1 set
(unlikely to be false but not impossible)

Bug#1018293: terminus: needs update for GNOME Shell 43

[Simon McVittie]

Package: terminus
Version: 1.17.0-1
Severity: important
Tags: bookworm sid patch
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-43

terminus contains a GNOME Shell extension which isn't flagged as compatible
with GNOME Shell 43, so it will not be loaded by GNOME Shell 43 with
default settings. GNOME 43 is the version that we plan to ship in bookworm.

Ubuntu has a patch which just adds Shell 43 as a supported version in the
metadata:
https://patches.ubuntu.com/t/terminus/terminus_1.17.0-1ubuntu1.patch
Hopefully that's sufficient? (I haven't checked, I don't use terminus
myself.)

I don't know how vital this extension is for terminus' functionality. If
it's optional then this bug can be downgraded to normal or minor.
Conversely, if the extension is essential to terminus' functionality on
GNOME, then this bug should probably go up to grave when GNOME Shell 43
goes to unstable (see https://bugs.debian.org/1018118).

smcv

Bug#1018296: ftpsync: rsync 3.2.5-1 breaks ftpsync

[Chris Boot]

Package: ftpsync
Version: 20180513+nmu1
Severity: important

Hi all,

I discussed this a few days ago in #debian-ftp; I think the bug is
probably in rsync but ftpsync is how I ran across it.

My mirror syncs against free.hands.com / ftp.uk.debian.org. With rsync
3.2.5-1 my mirror fails to sync: stage1 executes fine but stage 2 fails
with the following error from rsync:

ERROR: rejecting excluded file-list name: project
rsync error: protocol incompatibility (code 2) at flist.c(994)
[Receiver=3.2.5]
rsync error: protocol incompatibility (code 2) at io.c(1644)
[sender=3.2.3]
(from rsync-ftpsync.error.0)

The ftpsync output around this time is:

Aug 28 07:47:04 tarquin ftpsync[753936]: Running stage2: rsync --quiet
--log-file /srv/debmirror/log/rsync-ftpsync.log
--filter=exclude_/Archive-Update-in-Progress-tarquin.boo.tc
--filter=protect_/Archive-Update-in-Progress-tarquin.boo.tc
--filter=exclude_/Archive-Update-Required-tarquin.boo.tc
--filter=protect_/Archive-Update-Required-tarquin.boo.tc
--filter=exclude_/project/trace/tarquin.boo.tc
--filter=protect_/project/trace/tarquin.boo.tc
--filter=exclude_/project/trace/tarquin.boo.tc-stage1
--filter=protect_/project/trace/tarquin.boo.tc-stage1
--filter=exclude_/project/trace/_hierarchy
--filter=protect_/project/trace/_hierarchy
--filter=exclude_/project/trace/_traces
--filter=protect_/project/trace/_traces --filter=include_/project/
--filter=protect_/project/ --filter=include_/project/trace/
--filter=protect_/project/trace/ --filter=include_/project/trace/*
--bwlimit=0 -prltvHSB8192 --safe-links --chmod=D755,F644 --timeout 120
--stats --no-human-readable --no-inc-recursive --exclude=.~tmp~/
--filter=include_/dists/**/binary-arm64/
--filter=include_/dists/**/installer-arm64/
--filter=include_/dists/**/Contents-arm64.gz
--filter=include_/dists/**/Contents-udeb-arm64.gz
--filter=include_/dists/**/Contents-arm64.diff/
--filter=include_/indices/**/arch-arm64.files
--filter=include_/indices/**/arch-arm64.list.gz
--filter=include_/pool/**/*_arm64.deb
--filter=include_/pool/**/*_arm64.udeb
--filter=include_/pool/**/*_arm64.changes
--filter=include_/dists/**/binary-amd64/
--filter=include_/dists/**/installer-amd64/
--filter=include_/dists/**/Contents-amd64.gz
--filter=include_/dists/**/Contents-udeb-amd64.gz
--filter=include_/dists/**/Contents-amd64.diff/
--filter=include_/indices/**/arch-amd64.files
--filter=include_/indices/**/arch-amd64.list.gz
--filter=include_/pool/**/*_amd64.deb
--filter=include_/pool/**/*_amd64.udeb
--filter=include_/pool/**/*_amd64.changes
--filter=include_/dists/**/binary-i386/
--filter=include_/dists/**/installer-i386/
--filter=include_/dists/**/Contents-i386.gz
--filter=include_/dists/**/Contents-udeb-i386.gz
--filter=include_/dists/**/Contents-i386.diff/
--filter=include_/indices/**/arch-i386.files
--filter=include_/indices/**/arch-i386.list.gz
--filter=include_/pool/**/*_i386.deb
--filter=include_/pool/**/*_i386.udeb
--filter=include_/pool/**/*_i386.changes
--filter=include_/dists/**/source/ --filter=include_/pool/**/*.tar.*
--filter=include_/pool/**/*.diff.* --filter=include_/pool/**/*.dsc
--filter=include_/dists/**/binary-all/
--filter=include_/dists/**/installer-all/
--filter=include_/dists/**/Contents-all.gz
--filter=include_/dists/**/Contents-udeb-all.gz
--filter=include_/dists/**/Contents-all.diff/
--filter=include_/indices/**/arch-all.files
--filter=include_/indices/**/arch-all.list.gz
--filter=include_/pool/**/*_all.deb --filter=include_/pool/**/*_all.udeb
--filter=include_/pool/**/*_all.changes
--filter=exclude_/dists/**/binary-*/
--filter=exclude_/dists/**/installer-*/
--filter=exclude_/dists/**/Contents-*.gz
--filter=exclude_/dists/**/Contents-udeb-*.gz
--filter=exclude_/dists/**/Contents-*.diff/
--filter=exclude_/indices/**/arch-*.files
--filter=exclude_/indices/**/arch-*.list.gz
--filter=exclude_/pool/**/*_*.deb --filter=exclude_/pool/**/*_*.udeb
--filter=exclude_/pool/**/*_*.changes --filter=exclude_/dists/**/source/
--filter=exclude_/pool/**/*.tar.* --filter=exclude_/pool/**/*.diff.*
--filter=exclude_/pool/**/*.dsc free.hands.com::debian
/srv/debmirror/debian/ --max-delete=4 --delay-updates --delete
--delete-delay --delete-excluded
Aug 28 07:47:41 tarquin ftpsync[753936]: Back from rsync with returncode
2
Aug 28 07:47:41 tarquin ftpsync[753936]: ERROR: Sync step 2 went wrong,
got errorcode 2. Logfile: /srv/debmirror/log/ftpsync.log
Aug 28 07:47:41 tarquin ftpsync[753936]: Mirrorsync done with errors
(from ftpsync.log.0)

The relevant parts of my ftpsync.conf are:

RSYNC_HOST=free.hands.com
RSYNC_PATH="debian"
ARCH_INCLUDE="arm64 amd64 i386 source"

Reverting to rsync 3.2.4-1+b1 allows the sync to complete as normal. The
logs above are from a diffrent machine than the one I'm reporting on
where I have allowed rsync to update to 3.2.5-1, and which I can use for
testing.

Cheers,
Chris

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable'), (1, 

Bug#1018297: surf: Switch to webkit 4.1

[Jeremy Bicha]

Attached.

Thank you,
Jeremy Bicha
From 8b3f38aa3e953302f1c29c92fa89d3448b18ff74 Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Sun, 28 Aug 2022 12:07:21 -0400
Subject: [PATCH 1/2] Add patch to build with webkit2gtk 4.1 instead of 4.0

---
 debian/patches/Switch-to-webkitgtk-4.1.patch | 28 
 debian/patches/series|  1 +
 2 files changed, 29 insertions(+)
 create mode 100644 debian/patches/Switch-to-webkitgtk-4.1.patch

diff --git a/debian/patches/Switch-to-webkitgtk-4.1.patch b/debian/patches/Switch-to-webkitgtk-4.1.patch
new file mode 100644
index 000..c6121b0
--- /dev/null
+++ b/debian/patches/Switch-to-webkitgtk-4.1.patch
@@ -0,0 +1,28 @@
+From: Jeremy Bicha 
+Date: Sun, 28 Aug 2022 12:06:37 -0400
+Subject: Switch to webkitgtk 4.1
+
+4.1 is the same as 4.0 except that it uses libsoup3 instead of libsoup2.4
+---
+ config.mk | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/config.mk b/config.mk
+index c98442b..0141b6f 100644
+--- a/config.mk
 b/config.mk
+@@ -13,10 +13,10 @@ LIBDIR = $(LIBPREFIX)/surf
+ X11INC = $(shell $(PKG_CONFIG) --cflags x11)
+ X11LIB = $(shell $(PKG_CONFIG) --libs x11)
+ 
+-GTKINC = $(shell $(PKG_CONFIG) --cflags gtk+-3.0 gcr-3 webkit2gtk-4.0)
+-GTKLIB = $(shell $(PKG_CONFIG) --libs gtk+-3.0 gcr-3 webkit2gtk-4.0)
+-WEBEXTINC = $(shell $(PKG_CONFIG) --cflags webkit2gtk-4.0 webkit2gtk-web-extension-4.0 gio-2.0)
+-WEBEXTLIBS = $(shell $(PKG_CONFIG) --libs webkit2gtk-4.0 webkit2gtk-web-extension-4.0 gio-2.0)
++GTKINC = $(shell $(PKG_CONFIG) --cflags gtk+-3.0 gcr-3 webkit2gtk-4.1)
++GTKLIB = $(shell $(PKG_CONFIG) --libs gtk+-3.0 gcr-3 webkit2gtk-4.1)
++WEBEXTINC = $(shell $(PKG_CONFIG) --cflags webkit2gtk-4.1 webkit2gtk-web-extension-4.1 gio-2.0)
++WEBEXTLIBS = $(shell $(PKG_CONFIG) --libs webkit2gtk-4.1 webkit2gtk-web-extension-4.1 gio-2.0)
+ 
+ # includes and libs
+ INCS = $(X11INC) $(GTKINC)
diff --git a/debian/patches/series b/debian/patches/series
index 29bab95..76d7659 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,3 +4,4 @@ terminal.patch
 read.patch
 build_options.patch
 useragent.patch
+Switch-to-webkitgtk-4.1.patch
-- 
2.37.2

From f5be647eb01b037a1adaf80b47ec481b5552f529 Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Sun, 28 Aug 2022 12:07:44 -0400
Subject: [PATCH 2/2] Build-Depend on libwebkit2gtk-4.1-dev

Closes: #1018297
---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 9da4c19..519e407 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Build-Depends: debhelper-compat (= 13),
libgcr-3-dev,
libglib2.0-dev,
libgtk-3-dev,
-   libwebkit2gtk-4.0-dev,
+   libwebkit2gtk-4.1-dev,
pkg-config
 Standards-Version: 4.6.1
 Maintainer: Reiner Herrmann 
-- 
2.37.2

Bug#1013426: Cannot be built twice

[Tobias Frost]

Control: tags -1 pending patch

Hi Marko,

On Thu, 23 Jun 2022 15:14:24 +0300 Marko Lindqvist  wrote:
> Package: freeciv
> Version: 2.6.6-1
> 
> As debian/rules deletes dependencies/lua-5.3 directory when building
> the package, later attempts to do another build from the same tree
> fails.
> You should not delete the directory. According to the comment, the
> purpose is to make sure those sources are never used, as a fallback if
> lua is not found from the system. That's better achieved by adding the
> configure option --enable-sys-lua=yes (to override freeciv-2.6 default
> of --enable-sys-lua=test). It will also give more sensible errors than
> the missing directory, if those errors ever occur.
> 
> (This was causing me trouble when I started looking at the debian
> freeciv build failure at x32 - I should have something for that soon)
> 
> 
>  - ML
> 

thanks for your report!

Yes, reoving 3rd party stuff is the usual made to have a stron proof that 
the build system is indeed using the system packages.

And thanks for the hint with --enable-sys-lua=system.

However, my expectation was that with that switch the build system will
not even take a look at dependencies/lua-5.3, which was unfortunatly not
true:
- configure.ac lists it unconditionally in CONFIG_FILES
- dependencies/Makefile.am has some logic to detect the sys_lua flag,
  but this seems broken: On my local machine, it set 
LUASUBDIR = lua-5.3 and therefore including it into the build…

So, even with the switch, the build system needs it at least at
configure time, which is the reason why it failed at the second time.
(make distclean was the command that failed; as the removal of lua
was only directly before the build, it worked the first time.)

I've patched those files and now I can built twice :)

(tagging patch: The changes required are commited to the salsa repo)

-- 
Cheers,
tobi

Bug#944780: Many more cases where this fails - proposed patch included

[Tim Woodall]

This same problem happens for SUBSHELL_PAREN, SUBSHELL_COMSUB,
SUBSHELL_PIPE and SUBSHELL_COPROC as well as SUBSHELL_ASYNC

Test case (This must be sourced to see SHLVL == 1 which causes
/etc/bash.bashrc to be sourced in a shell started by ssh)

$ cat test.sh
test1="bash -c 'echo \$SHLVL'"
test2="{ bash -c 'echo \$SHLVL' ; }"

do_test()
{
echo "** Testing $1 $2"
eval $2
wait
echo "* DONE *"
echo
}

do_coproctest()
{
echo "** Testing COPROC $1"
eval coproc $1
IFS= read -ru ${COPROC[0]} x; printf '%s\n' "$x"
wait
echo "* DONE *"
echo
}


do_test BASIC "$test1"
do_test BASIC "$test2"

#ASYNC
do_test ASYNC "$test1 &"
do_test ASYNC "$test2 &"

#PAREN
do_test PAREN "( $test1 )"
do_test PAREN "( $test2 )"

#COMSUB
do_test COMSUB "echo \$( $test1 )"
do_test COMSUB "echo \$( $test2 )"

#PIPE
do_test PIPE "$test1 | cat"
do_test PIPE "$test2 | cat"

#PROCSUB
do_test PROCSUB "cat <( $test1 )"
do_test PROCSUB "cat <( $test2 )"

#COPROC
do_coproctest "$test1"
do_coproctest "$test2"

##

Proposed patch:
diff -urN bash-5.1.orig/execute_cmd.c bash-5.1/execute_cmd.c
--- bash-5.1.orig/execute_cmd.c 2020-10-12 14:16:13.0 +
+++ bash-5.1/execute_cmd.c  2020-10-12 14:16:13.0 +
@@ -5487,7 +5487,12 @@
#if 0 /* TAG: bash-5.2 psmith 10/11/2020 */
 if (nofork && pipe_in == NO_PIPE && pipe_out == NO_PIPE && 
(subshell_environment & SUBSHELL_PIPE) == 0)

#else
-  if (nofork && pipe_in == NO_PIPE && pipe_out == NO_PIPE)
+  if (nofork && pipe_in == NO_PIPE && pipe_out == NO_PIPE &&
+ (subshell_environment & SUBSHELL_ASYNC) == 0 &&
+ (subshell_environment & SUBSHELL_PAREN) == 0 &&
+ (subshell_environment & SUBSHELL_COMSUB) == 0 &&
+ (subshell_environment & SUBSHELL_PIPE) == 0 &&
+ (subshell_environment & SUBSHELL_COPROC) == 0)
#endif
  adjust_shell_level (-1);

#

It seems absurd that:
bash -c 'echo $SHLVL'
{ bash -c 'echo $SHLVL' ; }

should both have SHLVL == 2 but if they are executed async then the
first one runs with SHLVL == 1 but not the second.

The proposed patch causes them all to run at SHLVL == 2 which then
avoids the issue of SHLVL == 1 causing /etc/bash.bashrc to be sourced
when running under ssh.

It also fixes issues with make running in interactive shells
unexpectedly.

Without the fix:
$ cat Makefile.test
all:
  echo $$SHLVL
$ make -f Makefile.test
echo $SHLVL
1
$ make -f Makefile.test | cat
echo $SHLVL
0
$


This does not change the behaviour reported in #702559


#

N.B. The sourcing of /etc/bash.bashrc is most easily seen by:

$ ( bash -uc : )
/etc/bash.bashrc: line 8: PS1: unbound variable
$

This issue of unbound variables in bash.bashrc was reported in #941248

###
Results of running test.sh in bullseye:
(If it is sourced the results are, as expected, one lower)

# ./test.sh
** Testing BASIC bash -c 'echo $SHLVL'
3
* DONE *

** Testing BASIC { bash -c 'echo $SHLVL' ; }
3
* DONE *

** Testing ASYNC bash -c 'echo $SHLVL' &
2
* DONE *

** Testing ASYNC { bash -c 'echo $SHLVL' ; } &
3
* DONE *

** Testing PAREN ( bash -c 'echo $SHLVL' )
2
* DONE *

** Testing PAREN ( { bash -c 'echo $SHLVL' ; } )
3
* DONE *

** Testing COMSUB echo $( bash -c 'echo $SHLVL' )
2
* DONE *

** Testing COMSUB echo $( { bash -c 'echo $SHLVL' ; } )
3
* DONE *

** Testing PIPE bash -c 'echo $SHLVL' | cat
2
* DONE *

** Testing PIPE { bash -c 'echo $SHLVL' ; } | cat
3
* DONE *

** Testing PROCSUB cat <( bash -c 'echo $SHLVL' )
3
* DONE *

** Testing PROCSUB cat <( { bash -c 'echo $SHLVL' ; } )
3
* DONE *

** Testing COPROC bash -c 'echo $SHLVL'
2
* DONE *

** Testing COPROC { bash -c 'echo $SHLVL' ; }
3
* DONE *

##
with the proposed patch applied:

** Testing BASIC bash -c 'echo $SHLVL'
3
* DONE *

** Testing BASIC { bash -c 'echo $SHLVL' ; }
3
* DONE *

** Testing ASYNC bash -c 'echo $SHLVL' &
3
* DONE *

** Testing ASYNC { bash -c 'echo $SHLVL' ; } &
3
* DONE *

** Testing PAREN ( bash -c 'echo $SHLVL' )
3
* DONE *

** Testing PAREN ( { bash -c 'echo $SHLVL' ; } )
3
* DONE *

** Testing COMSUB echo $( bash -c 'echo $SHLVL' )
3
* DONE *

** Testing COMSUB echo $( { bash -c 'echo $SHLVL' ; } )
3
* DONE *

** Testing PIPE bash -c 'echo $SHLVL' | cat
3
* DONE *

** Testing PIPE { bash -c 'echo $SHLVL' ; } | cat
3
* DONE *

** Testing PROCSUB cat <( bash -c 'echo $SHLVL' )
3
* DONE *

** Testing PROCSUB cat <( { bash -c 'echo $SHLVL' ; } )
3
* DONE *

** Testing COPROC bash -c 'echo $SHLVL'
3
* DONE *

** Testing COPROC { bash -c 'echo $SHLVL' ; }
3
* DONE *

Bug#1018300: ITP: gcloud-aio -- (Asyncio OR Threadsafe) Google Cloud Client Library for Python

[Jelmer Vernooij]

Package: wnpp
Severity: wishlist
Owner: Jelmer Vernooij 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: gcloud-aio
  Version : 7.0.1
  Upstream Author : Vi Engineering 
* URL : https://github.com/talkiq/gcloud-aio/
* License : MIT
  Programming Lang: Python
  Description : Async Python Client for Google Cloud Storage

asyncio python library for accessing Google Cloud Storage.

This is a dependency for the Debian Janitor.

Bug#1016413: bullseye-pu: package libreoffice/1:7.0.4-4+deb11u3

[Rene Engelhard]

Hi,

Hrmpf.

This happens if you try to build a minimal patch (and doing the diffs 
and tests in different trees) in parallel to sending the diff :/ And 
that in time pressure to do it today because I won't have time next week 
probably for it and then the timeframe for 11.5 closes...


Am 28.08.22 um 18:46 schrieb Rene Engelhard:
 which contained a cut and paste error I introduced when redoing it 
after deciding I do the version check again for complenetess' sake...


That doesn't work either. EDS_CHECK_VERSION is not available from only 
libebook, we'd need libedataserver for it too.


As I don't want to add that

Reverted that and hardcoded it anyway. >= 3.16 is a given anyway.

Really working patch attached.
Sorry again.

Regards,

Rene
diff --git a/changelog b/changelog
index 41633702..82ecac2d 100644
--- a/changelog
+++ b/changelog
@@ -1,3 +1,10 @@
+libreoffice (1:7.0.4-4+deb11u3) stable; urgency=medium
+
+  * debian/patches/fix-e_book_client_connect_direct_sync-sig.diff:
+as name says (closes: #1016420)
+
+ -- Rene Engelhard   Sun, 28 Aug 2022 19:22:27 +0200
+
 libreoffice (1:7.0.4-4+deb11u2) stable; urgency=medium
 
   * debian/patches/hrk-euro.diff: add EUR to .hr i18n;
diff --git a/patches/fix-e_book_client_connect_direct_sync-sig.diff 
b/patches/fix-e_book_client_connect_direct_sync-sig.diff
new file mode 100644
index ..bc3ecf31
--- /dev/null
+++ b/patches/fix-e_book_client_connect_direct_sync-sig.diff
@@ -0,0 +1,26 @@
+diff --git a/connectivity/source/drivers/evoab2/EApi.h 
b/connectivity/source/drivers/evoab2/EApi.h
+index 8c05f95fa2ce..928786d79f00 100644
+--- a/connectivity/source/drivers/evoab2/EApi.h
 b/connectivity/source/drivers/evoab2/EApi.h
+@@ -147,7 +147,7 @@ EAPI_EXTERN const gchar* (*eds_check_version) (guint 
required_major, guint requi
+ EAPI_EXTERN const gchar* (*e_source_get_uid) (ESource *source);
+ EAPI_EXTERN ESource* (*e_source_registry_ref_source) (ESourceRegistry 
*registry, const gchar *uid);
+ EAPI_EXTERN EBookClient* (*e_book_client_new) (ESource *source, GError 
**error);
+-EAPI_EXTERN EBookClient* (*e_book_client_connect_direct_sync) 
(ESourceRegistry *registry, ESource *source, GCancellable *cancellable, GError 
**error);
++EAPI_EXTERN EBookClient* (*e_book_client_connect_direct_sync) 
(ESourceRegistry *registry, ESource *source, guint32 
wait_for_connected_seconds, GCancellable *cancellable, GError **error);
+ EAPI_EXTERN gboolean (*e_client_open_sync) (EClient *client, gboolean 
only_if_exists, GCancellable *cancellable, GError **error);
+ EAPI_EXTERN ESource* (*e_client_get_source) (EClient *client);
+ EAPI_EXTERN gboolean (*e_book_client_get_contacts_sync) (EBookClient *client, 
const gchar *sexp, GSList **contacts, GCancellable *cancellable, GError 
**error);
+diff --git a/connectivity/source/drivers/evoab2/NResultSet.cxx 
b/connectivity/source/drivers/evoab2/NResultSet.cxx
+index 77d53939c1aa..83e792538fc0 100644
+--- a/connectivity/source/drivers/evoab2/NResultSet.cxx
 b/connectivity/source/drivers/evoab2/NResultSet.cxx
+@@ -477,7 +477,7 @@ class OEvoabVersion38Helper : public OEvoabVersion36Helper
+ protected:
+ virtual EBookClient * createClient( ESource *pSource ) override
+ {
+-return e_book_client_connect_direct_sync (get_e_source_registry (), 
pSource, nullptr, nullptr);
++return e_book_client_connect_direct_sync (get_e_source_registry (), 
pSource, 10, nullptr, nullptr);
+ }
+ };
+ 
diff --git a/patches/series b/patches/series
index fa58e363..69db8a90 100644
--- a/patches/series
+++ b/patches/series
@@ -62,3 +62,4 @@ b0404f80577de9ff69e58390c6f6ef949fdb0139.patch
 0002-CVE-2022-26307-make-hash-encoding-match-decoding.patch
 0003-CVE-2022-26306-add-Initialization-Vectors-to-passwor.patch
 0004-CVE-2022-2630-6-7-add-infobar-to-prompt-to-refresh-t.patch
+fix-e_book_client_connect_direct_sync-sig.diff

Bug#989696: mk-build-deps: --remove should also remove changes and buildinfo files

[Tobias Frost]

Control: tags -1 patch

https://salsa.debian.org/debian/devscripts/-/merge_requests/277

This might be not more than a "works for tobi" state, as I'm not
knowledgeable in perl…

It is probably not working if build_arch != host_arch, however,
mk_build_deps does not like that today either.

Bug#1017884: reportbug: qemu-system-x86_64 freezes after i access samba server on a windows-xp host

[أسامة مخزوم]

> You have:
>
> -net nic,model=rtl8139 -net user
> -net user,smb=...
>
> The -net thing comes in pairs (one is guest side, another is host side).
> You have 3 of them, and the last one is not paired with the guest side.
>
> I suspect this is your problem - qemu does not know how to handle the
> unpaired -net user.

you were right, i change it now and it works. seems AQEMU generates
buggy qemu's cmds, i have used it for the vm but i copy cmdline only

shall i report separate bug for aqemu ?


> The whole -net syntax is obsolete - partly because of this common
> misunderstanding and partly because whole architecture behind -net is
> wrongly designed. You should use -netdev..-device instead of -net..-net.
> (Unfortunately, many old guides in the internet still suggest to use
> -net, but this is something we can't change in a moment).


> Now, you use both -net user,smb=... which redirects ports used by
> windows networking to custom samba instance with its own configuration,
> with nothing shared from host samba. Yet you attach your smb.conf file.
> Why?

I was just mistaken about samba and qemu , thought it used smbd for
its internals...

Bug#1018291: ITP: libcrypt-argon2-perl -- Perl interface to the Argon2 key derivation functions

[Joenio Marques da Costa]

Package: wnpp
Severity: wishlist
Owner: Joenio Marques da Costa 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libcrypt-argon2-perl
  Version : 0.012
  Upstream Author : Leon Timmermans 
* URL : https://metacpan.org/release/Crypt-Argon2
* License : CC0-1.0
  Programming Lang: Perl
  Description : Perl interface to the Argon2 key derivation functions

The Crypt::Argon2 implements the Argon2 key derivation function, which is
suitable to convert any password into a cryptographic key. This is most often
used to secure storage of passwords but can also be used to derive a
encryption key from a password. It offers variable time and memory costs as
well as output size.

A command-line tool `argon2-calibrate` to find the appropriate parameters is
included in this package.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools and reportbug(1).

Bug#941901: octavia 3.0.0-3+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 941901 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: octavia
Version: 3.0.0-3+deb10u1

Explanation: fix client certificate checks [CVE-2019-17134]; correctly detect 
that the agent is running on Debian; fix template that generates vrrp check 
script; add additional runtime dependencies; ship additional configuration 
directly in the agent package

Bug#1018292: ncrystal: ftbfs on riscv64, armel, mipsel

[Bo YU]

Source: ncrystal
Version: 2.7.3+ds1-4
Severity: normal
Tags: ftbfs, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org,
debian-...@lists.debian.org, debian-m...@lists.debian.org

Dear ncrystal Maintainer,

The packages has ftbfs issues on riscv64, armel, mipsel due to missing 
link atomic. The full buildd log is here:

https://buildd.debian.org/status/fetch.php?pkg=ncrystal=armel=2.7.3%2Bds1-4=1643836600=0
https://buildd.debian.org/status/fetch.php?pkg=ncrystal=mipsel=2.7.3%2Bds1-4=1643851129=0
https://buildd.debian.org/status/fetch.php?pkg=ncrystal=riscv64=2.7.3%2Bds1-4=1643838103=0

The patch attached is trying to fix those build fail and it has been 
verified in real riscv64 hardware and armel & mipsel qemu.

Please let me know if there are any issues.


-- 
Regards,
--
  Bo YU

--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -276,7 +276,7 @@
 endif()
 
 set_target_common_props( NCrystal )
-target_link_libraries( NCrystal PRIVATE common )
+target_link_libraries( NCrystal PRIVATE common -latomic)
 target_include_directories(NCrystal PRIVATE "${PROJECT_SOURCE_DIR}/ncrystal_core/src"
  PUBLIC   $
 $ )


signature.asc
Description: PGP signature

Bug#1017740: transition: draco

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2022-08-19 20:49:50 +0200, Timo Röhling wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear release team,
> 
> I'd like to transition draco after its SONAME bump.
> The ben file looks good:
> https://release.debian.org/transitions/html/auto-draco.html
> 
> All reverse dependencies build sucessfully on amd64.

Please go ahead

Cheers
-- 
Sebastian Ramacher