Bug#1034055: fwknop-apparmor-profile: AppArmor profile installed in systemd system service path

[Laurent Bigonville]

Le 7/04/23 à 20:19, Francois Marier a écrit :

On 2023-04-07 at 07:23:07, Laurent Bigonville (bi...@debian.org) wrote:

It seems that you install the apparmor profile in the path for systemd system 
service

The following change should be reverted:
https://salsa.debian.org/debian/fwknop/-/commit/d3a5aaef39fedc1bb94e26921afbf63f79b31af7

Hm, that does look like a mistake. I don't remember what might have caused
me to make that change.

I guess the apparmor profile hasn't been in use for a while then. It seems
like it's too late in the release process to re-add it in bookworm.

Here's what I'm thinking of doing:

- move it to /usr/share/apparmor/extra-profiles/ (so it's not turned on by
   default) for bookworm
- move it back to /etc/apparmor.d/ after bookworm

Alternatively, I could also not change anything for bookworm since it's not
enabled as an AppArmor profile and it will be ignored as a systemd unit
file.

What do you think?


Sorry for the late answer.

I see that you moved the file to /usr/share/apparmor/extra-profiles/, 
for now it's OK I guess, might be indeed be too late to enable the 
profile so late in the development cycle


An other option for bookworm+1 is to move the file back to 
/etc/apparmor.d/ AND merge the profile back in the main package so it's 
installed along side the daemon and kill fwknop-apparmor-profile (that 
package only ships one file AFAICS)


Apparmor profile can be put in complain/non-enforcing mode if the user 
really wants to.

Bug#1034278: mirror listing update for linux.purple-cat.net

[Mike Hosken]

Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: linux.purple-cat.net
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Mike Hosken 
Country: NZ New Zealand
Location: Dunedin 
Sponsor: Unifone NZ https://unifone.net.nz/
Comment: Updated information as not on list anymore. Ip address has changed. 
Also full Debian ports repo on debian-ports and Debian archive on debian-archive




Trace Url: http://linux.purple-cat.net/debian/project/trace/
Trace Url: 
http://linux.purple-cat.net/debian/project/trace/ftp-master.debian.org
Trace Url: http://linux.purple-cat.net/debian/project/trace/linux.purple-cat.net

Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

[Lucas Nussbaum]

Hi,

On 12/04/23 at 09:16 +0800, Paul Wise wrote:
> On Wed, 2023-03-29 at 08:05 +0200, Christian Marillat wrote:
> 
> > For several days sf.php no longer works:
> > 
> > ,
> > > uscan warn: In watchfile debian/watch, reading webpage
> > >   https://qa.debian.org/watch/sf.php/synfig/ failed: 500 Error
> > `
> 
> This issue is caused by the underlying SourceForge infrastructure
> (their files RSS feed) starting to apply rate limiting and returning
> HTTP 429 Too Many Requests errors, which the Debian QA redirector
> easily hits, depending on how much use the service has per day.
> 
> We could have individual contributors rewrite every single one of their
> SourceForge debian/watch files to use the SourceForge files RSS feeds.
> 
> Alternatively we could move the code for the SourceForge redirector
> into uscan so that individual uscan users get separate rate limit
> buckets, rather than having one large Debian rate limit bucket.
> 
> Unfortunately these changes will not fix the problem of UDD getting
> errors all the time. To fix that, UDD would need to gain a distributed
> architecture with multiple IP addresses all contacting SourceForge.
> That may cause overloads of the SourceForge server resources though,
> which would probably lead to uscan getting blocked again.
> 
> So maybe we need to discuss this with SourceForge again.

There's specific code in the UDD uscan wrapper[1] to handle github's
rate limiting. We could have something similar for either sf.net, or the
sf.net redirector. Before I work on that, it would be great if someone
could change the sf.net redirector to return 429 instead of 500 when
sf.net returns 429, so that this specific case is easier to identify.

[1] https://salsa.debian.org/qa/udd/-/blob/master/rimporters/upstream.rb#L161

Lucas

Bug#1034102: UDD patches: incorrect handling of Forwarded?

[Lucas Nussbaum]

Hi Ross,

On 08/04/23 at 16:59 -0700, Ross Vandegrift wrote:
> Package: qa.debian.org
> Severity: normal
> X-Debbugs-Cc: rvandegr...@debian.org
> 
> Hello,
> 
> I think there are some issues with the Forwarded handling here:
>   https://udd.debian.org/patches.cgi?src=e17=0.25.4-2
> 
> DEP3 has this description for Forwarded:
> 
> > Any value other than "no" or "not-needed" means that the patch has been
> > forwarded upstream. Ideally the value is an URL proving that it has been
> > forwarded and where one can find more information about its inclusion 
> > status.
> > 
> > If the field is missing, its implicit value is "yes" if the "Bug" field is
> > present, otherwise it's "no". The field is really required only if the patch
> > is vendor specific, in that case its value should be "not-needed" to 
> > indicate
> > that the patch must not be forwarded upstream (whereas "no" simply means 
> > that
> > it has not yet been done).
> 
> The patch linked above is tagged Forwarded=yes - which is not ideal, but not
> invalid.  Looking for more info, I found that the html source has:
> 
> > invalid
> 
> This doesn't show up in firefox - was this was meant to go into the content
> of the span?

It works for me in firefox?

> And as far that error - to my reading, DEP3 doesn't require a Bug when
> Forwarded=yes.  Bug's presence or absence only changes the implicit value.
> 
> A note that Forwarded=yes without a Bug is not informative would be helpful. 
> :)

There was a lengthy discussion in #1028503 about that.

Lucas

Bug#1013448: pcre2 relies on write+execute mappings unnecessarily

[Trent W. Buck]

FYI,

systemd's MemoryDenyWriteExecute=yes breaks "git grep" because of pcre2jit.

An easy test command is something like this:

$ journalctl --user -fn0 &   # so you see the error
$ systemd-run --property=MemoryDenyWriteExecute=yes --user git -C 
/srv/vcs/kb grep -Fwi mutt

--error--> git[2289491]: fatal: Couldn't JIT the PCRE2 pattern 'mutt', got 
'-48'

A real-world use case is hardening gitit.service,
a git-based wiki .
With MemoryDenyWriteExecute=yes, gitit works perfectly, EXCEPT for search 
(which uses "git grep" under the hood).

Is there a way for a sysadmin to disable pcre2jit at runtime, e.g. with an 
environment variable?
I understand it makes pcre2 slower, but I might actually prefer to make that 
security-vs-speed tradeoff.
I looked at https://manpages.debian.org/pcre2jit but only found compile-time 
options.


See also https://github.com/systemd/systemd/issues/5970

Bug#1034277: ITP: golang-github-mazznoer-colorgrad -- Go (Golang) color scales library for maps, charts, data-visualization & creative coding

[Yinuo Deng]

Package: golang-github-mazznoer-colorgrad
Severity: wishlist

* Package name: golang-github-mazznoer-colorgrad
  Version : 0.9.1
  Upstream Author : Nor Khasyatillah
* URL : https://github.com/mazznoer/colorgrad
* License : MIT
  Programming Lang: Go
  Description : Go (Golang) color scales library for maps, charts, 
data-visualization & creative coding


Go (Golang) color scales library for maps, charts, data-visualization & 
creative coding


This is a dependency of fx, which is request in #1018794.

Bug#1034276: unblock: fwknop/2.6.10-16

[Francois Marier]

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

Please unblock package fwknop

[ Reason ]
The AppArmor profile was incorrectly installed in the systemd
system service path:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034055

[ Impact ]
I'm not sure whether it would cause any actual problems, but it is likely a
policy violation and the bug reporter did file it as an RC bug.

[ Tests ]
I upgraded to the version I uploaded to unstable yesterday and confirmed
that the file is in the new location:

  $ dpkg -L fwknop-apparmor-profile | grep usr.sbin.fwknopd
  /usr/share/apparmor/extra-profiles/usr.sbin.fwknopd

[ Risks ]
Trivial fix. I made it so that the AppArmor profile is not automatically
enabled either to avoid changing (i.e. fixing) the behavior compared to what
it was in -15.

So this should be a no-op in terms of functionality.

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


unblock fwknop/2.6.10-16
diff -Nru fwknop-2.6.10/debian/changelog fwknop-2.6.10/debian/changelog
--- fwknop-2.6.10/debian/changelog	2023-01-10 21:23:46.0 -0800
+++ fwknop-2.6.10/debian/changelog	2023-04-10 20:52:01.0 -0700
@@ -1,3 +1,12 @@
+fwknop (2.6.10-16) unstable; urgency=high
+
+  * Install apparmor profile in /usr/share/apparmor/extra-profiles/
+instead of the systemd service directory. Note that the profile
+will not be used unless manually copied into /etc/apparmor.d/
+(Closes: #1034055).
+
+ -- Francois Marier   Mon, 10 Apr 2023 20:52:01 -0700
+
 fwknop (2.6.10-15) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru fwknop-2.6.10/debian/fwknop-apparmor-profile.install fwknop-2.6.10/debian/fwknop-apparmor-profile.install
--- fwknop-2.6.10/debian/fwknop-apparmor-profile.install	2023-01-10 21:23:46.0 -0800
+++ fwknop-2.6.10/debian/fwknop-apparmor-profile.install	2023-04-10 20:52:01.0 -0700
@@ -1 +1 @@
-extras/apparmor/usr.sbin.fwknopd	/usr/lib/systemd/system/
+extras/apparmor/usr.sbin.fwknopd	/usr/share/apparmor/extra-profiles/

Bug#1034275: ITP: node-react-transition-group -- ReactJS component to expose simple components

[Yadd]

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

* Package name: node-react-transition-group
  Version : 4.4.5
  Upstream Contact:
  https://github.com/reactjs/react-transition-group/issues
* URL : https://github.com/reactjs/react-transition-group
* License : BSD-3-Clause
  Programming Lang: JavaScript
  Description : ReactJS component to expose simple components

node-react-transition-group provides a set of components for managing
component states (including mounting and unmounting) over time,
specifically designed with animation in mind.

React Transition Group is not an animation library like
React-Motion, it does not animate styles by itself. Instead it
exposes transition stages, manages classes and group elements and
manipulates the DOM in useful ways, making the implementation of
actual visual transitions much easier.

node-react-transition-group is a dependency of Jupyterlab and will be
maintained under JS Team umbrella.

Bug#990464: Kdump is unable to use NVME

[Kody Barks]

On Wed, 16 Feb 2022 13:08:58 -0300 "Guilherme G. Piccoli" <
gpicc...@igalia.com> wrote:
> On Mon, 27 Dec 2021 09:44:24 -0600 Kody Barks 
> wrote:
> > Kernel 5.10, and an upgrade to Bullseye. This issue is still not fixed.
>
> Hi Kody, can you please share the outputs of the following 3 commands?
>
> lspci -nns :09:00.0
> lspci -nns :41:00.0
> lspci -nns :42:00.0
>
> Also, do you remember of a specific kernel version that ever worked with
> these drivers on kdump?
> Thanks,
>
>
> Guilherme
>
>
> P.S. Please don't forget to CC me when responding, I'm not sure if I'd
> receive responses to the bug only, I'm not subscribed it seems.
>
>
here ya go:
root@TESSA:~# lspci -nns :09:00.0
09:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd
NVMe SSD Controller SM981/PM981/PM983 [144d:a808]
root@TESSA:~# lspci -nns :41:00.0
41:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd
NVMe SSD Controller SM961/PM961/SM963 [144d:a804]
root@TESSA:~# lspci -nns :42:00.0
42:00.0 Non-Volatile memory controller [0108]: Intel Corporation Optane SSD
900P Series [8086:2700]

no, this has never worked. my system crashes frequently, and without kdump,
i have no means of figuring out why.

Bug#1034160: The regression is back to kscreenlocker

[Adilson dos Santos Dantas]

I got this bug again after upgrading to qt5 5.15.8+dfsg-6. The same
behavior of plasma screen locker freezing and showing the message to use
loginctl to unlock.

Downgrading to 5.15.8+dfsg-5 solves it. Since it affects this package
again, I'm reopening this bug report.

-- 
Adilson dos Santos Dantas
http://www.adilson.net.br
http://twitter.com/adilsond

Bug#1034274: ITP: ukui-app-widget -- ukui-app-widget is a qml appwidget framework. It can display a view for quick browsing, which is mainly to display the most important data and functions of the app

[xibowen]

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

* Package name: ukui-app-widget
  Version : 1.0.1
  Upstream Contact: wangyan 
* URL : https://gitee.com/openkylin/ukui-app-widget
* License : GPL, BSD
  Programming Lang: C++
  Description : ukui-app-widget is a qml appwidget framework. It can
display a view for quick browsing, which is mainly to display the most
important data and functions of the application.

Bug#1034273: toybox: FTBFS if V=1 in environment

[Steve Langasek]

Package: toybox
Version: 0.8.9+dfsg-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch

Hi Antoni,

We've found that the new upstream version of toybox fails to build from
source in Ubuntu, because the Ubuntu builders export V=1 in the build
environment, and toybox's build system fails under these conditions.

The following patch makes debian/rules clear $V in the environment, allowing
the package to build.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru toybox-0.8.9+dfsg/debian/rules toybox-0.8.9+dfsg/debian/rules
--- toybox-0.8.9+dfsg/debian/rules  2023-02-18 11:07:34.0 -0800
+++ toybox-0.8.9+dfsg/debian/rules  2023-04-11 18:56:39.0 -0700
@@ -4,6 +4,8 @@
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 
+export V=
+
 %:
dh $@
 

Bug#1031694: Libxisf in kde neon

[Carlos De Maine]

Hi

I've packaged this in KDE neon so that Kstars and indi can utilise it.

https://invent.kde.org/neon/neon-packaging/libxisf[1]

It should hit the archives later today.

Cheers
Carlos


[1] https://invent.kde.org/neon/neon-packaging/libxisf

Bug#1034272: corectrl: Crash: missing runtime dep qml-module-qtquick-window2

[Boyuan Yang]

Package: corectrl
Severity: grave
Version: 1.3.3+ds-1
X-Debbugs-CC: t...@debian.org matthias.geiger1...@tutanota.de

Hi,

Forwarded from https://www.phoronix.com/news/CoreCtrl-In-Debian-Ubuntu-23.04 :

% corectrl
[11-04-23 21:40:40.595][W] glxinfo command failed
QQmlApplicationEngine failed to load component
qrc:/qml/main.qml:11:1: Type ApplicationWindow unavailable
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/QtQuick/Controls.2/Material/ApplicationWindow.qml:38:1: module
"QtQuick.Window" is not installed
[11-04-23 21:40:43.014][W] QML engine failed to load main interface!
[11-04-23 21:40:43.014][W] Initialization failed
[11-04-23 21:40:43.014][W] Exiting...
terminate called without an active exception
[1]5228 IOT instruction  corectrl


This error will disappear once qml-module-qtquick-window2 is installed.
Looks like corectrl is (at least) missing this runtime dependency.

Best Regards,
Boyuan Yang


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

Bug#1034271: libqt5core5a: upgrade to 5.15.8+dfsg-6 causes alt-F2 krunner start to never show dialogue box

[Arthur Marsh]

Package: libqt5core5a
Version: 5.15.8+dfsg-6
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

[UPGRADE] libqt5concurrent5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5core5a:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5dbus5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5gui5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5network5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5opengl5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5opengl5-dev:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5printsupport5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5sql5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5sql5-mysql:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5sql5-psql:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5sql5-sqlite:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5test5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5widgets5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5xml5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] qt5-gtk-platformtheme:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] qt5-qmake:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] qt5-qmake-bin:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] qtbase5-dev:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] qtbase5-dev-tools:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6

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

using alt-F2 results in krunner consuming a large amount of CPU time then 
not appearing in the top monitor, but using alt-F2 again repears the same
increasing CPU and eventual dropping out from being the most CPU bound process

Downgrading back to 5.15.8+dfsg-5 resolved the problem.

   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.0
  APT prefers experimental
  APT policy: (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-rc6+ (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libqt5core5a depends on:
ii  libc6  2.36-9
ii  libdouble-conversion3  3.2.1-1
ii  libgcc-s1  13-20230320-1
ii  libglib2.0-0   2.75.2-1
ii  libicu72   72.1-3
ii  libpcre2-16-0  10.42-1
ii  libstdc++6 13-20230320-1
ii  libzstd1   1.5.4+dfsg2-5
ii  shared-mime-info   2.2-1
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages libqt5core5a recommends:
ii  qttranslations5-l10n  5.15.8-2

Versions of packages libqt5core5a suggests:
ii  libthai0  0.1.29-1

-- no debconf information

Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

[Paul Wise]

On Wed, 2023-03-29 at 08:05 +0200, Christian Marillat wrote:

> For several days sf.php no longer works:
> 
> ,
> > uscan warn: In watchfile debian/watch, reading webpage
> >   https://qa.debian.org/watch/sf.php/synfig/ failed: 500 Error
> `

This issue is caused by the underlying SourceForge infrastructure
(their files RSS feed) starting to apply rate limiting and returning
HTTP 429 Too Many Requests errors, which the Debian QA redirector
easily hits, depending on how much use the service has per day.

We could have individual contributors rewrite every single one of their
SourceForge debian/watch files to use the SourceForge files RSS feeds.

Alternatively we could move the code for the SourceForge redirector
into uscan so that individual uscan users get separate rate limit
buckets, rather than having one large Debian rate limit bucket.

Unfortunately these changes will not fix the problem of UDD getting
errors all the time. To fix that, UDD would need to gain a distributed
architecture with multiple IP addresses all contacting SourceForge.
That may cause overloads of the SourceForge server resources though,
which would probably lead to uscan getting blocked again.

So maybe we need to discuss this with SourceForge again.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1034269: plasma-desktop-data: org.kde.plasma.taskmanager plasmoid sometimes crashes plasmashell after launching application

[Nathan Sharp]

Package: plasma-desktop-data
Version: 4:5.27.2-1
Severity: important
Tags: upstream
X-Debbugs-Cc: nwsh...@live.com

This is likely fixed upstream but renderes KDE/plasma difficult to use
currently in Debian. It would be a shame if this issue ends up in the
final Bookworm release.

systemd[1139]: Started app-firefox-f2324bba17ef4914af8cd48d372e92ba.scope - 
Firefox - Web Browser.
plasmashell[251820]: 
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286:
 Unable to assign [undefined] to QString
plasmashell[251820]: 25 -- exe=/usr/bin/plasmashell
plasmashell[251820]: 13 -- platform=xcb
plasmashell[251820]: 11 -- display=:0
plasmashell[251820]: 20 -- appname=plasmashell
plasmashell[251820]: 17 -- apppath=/usr/bin
plasmashell[251820]: 10 -- signal=11
plasmashell[251820]: 11 -- pid=251820
plasmashell[251820]: 18 -- appversion=5.27.2
plasmashell[251820]: 19 -- programname=Plasma
plasmashell[251820]: 31 -- bugaddress=sub...@bugs.kde.org
plasmashell[251820]: KCrash: crashing... crashRecursionCounter = 2
plasmashell[251820]: KCrash: Application Name = plasmashell path = /usr/bin pid 
= 251820
plasmashell[251820]: KCrash: Arguments: /usr/bin/plasmashell --no-respawn
plasmashell[251820]: KCrash: Attempting to start 
/usr/lib/x86_64-linux-gnu/libexec/drkonqi
kded5[1347]: Registering ":1.302/StatusNotifierItem" to system tray
plasmashell[251820]: QSocketNotifier: Invalid socket 22 and type 'Read', 
disabling...
plasmashell[251820]: QSocketNotifier: Invalid socket 24 and type 'Read', 
disabling...
plasmashell[251820]: QSocketNotifier: Invalid socket 26 and type 'Read', 
disabling...
plasmashell[251820]: Unable to start Dr. Konqi
plasmashell[251820]: Re-raising signal for core dump handling.
kded5[1347]: Service  ":1.302" unregistered
kwin_x11[1348]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 
20925, resource id: 4194826, major code: 15 (QueryTree), minor code: 0
kwin_x11[1348]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 
21025, resource id: 4194321, major code: 15 (QueryTree), minor code: 0
kwin_x11[1348]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 
21124, resource id: 4194339, major code: 15 (QueryTree), minor code: 0
systemd-coredump[385070]: [] Process 251820 (plasmashell) of user 1000 dumped 
core.
Module libsystemd.so.0 from deb systemd-252.6-1.amd64
Module libudev.so.1 from deb systemd-252.6-1.amd64
Stack trace of thread 251820:
#0  0x7f37356a9ccc __pthread_kill_implementation (libc.so.6 + 0x8accc)
#1  0x7f373565aef2 __GI_raise (libc.so.6 + 0x3bef2)
#2  0x7f3737be1b46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 
+ 0x5b46)
#3  0x7f373565af90 __restore_rt (libc.so.6 + 0x3bf90)
#4  0x7f37356a9ccc __pthread_kill_implementation (libc.so.6 + 0x8accc)
#5  0x7f373565aef2 __GI_raise (libc.so.6 + 0x3bef2)
#6  0x7f373565af90 __restore_rt (libc.so.6 + 0x3bf90)
#7  0x7f37356a4d34 __futex_abstimed_wait_common64 (libc.so.6 + 0x85d34)
#8  0x7f37356a73f8 __pthread_cond_wait_common (libc.so.6 + 0x883f8)
#9  0x7f37358d1a2b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer 
(libQt5Core.so.5 + 0xd1a2b)
#10 0x7f373760bd58 n/a (libQt5Quick.so.5 + 0x20bd58)
#11 0x7f373760d013 n/a (libQt5Quick.so.5 + 0x20d013)
#12 0x7f3735f493f5 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 
0x1493f5)
#13 0x7f3725dda055 n/a (libcorebindingsplugin.so + 0x3f055)
#14 0x7f3736762fae 
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 
0x162fae)
#15 0x7f3735ab16f8 
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 
0x2b16f8)
#16 0x7f3735f3e5cd 
_ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE
 (libQt5Gui.>
#17 0x7f3735f11cac 
_ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
 (libQt5Gui.s>
#18 0x7f37308fbeba n/a (libQt5XcbQpa.so.5 + 0x6deba)
#19 0x7f37343db7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9)
#20 0x7f37343dba38 n/a (libglib-2.0.so.0 + 0x54a38)
#21 0x7f37343dbacc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc)
#22 0x7f3735b09836 
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
 (libQt5Core.so.5 + 0x30>
#23 0x7f3735ab017b 
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 
0x2b017b)
#24 0x7f3735ab82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 
0x2b82d6)
#25 0x56306f13adc3 n/a (plasmashell + 0x26dc3)
#26 0x7f373564618a __libc_start_call_main (libc.so.6 + 0x2718a)
#27 0x7f3735646245 __libc_start_main_impl (libc.so.6 + 0x27245)
#28 0x56306f13aee1 n/a (plasmashell + 0x26ee1)

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 

Bug#1034268: cvc5: Please package the python modules

[Celelibi]

Source: cvc5
Severity: normal
X-Debbugs-Cc: celel...@gmail.com

Hello,
There are two Python API to CVC5. The base API that closely match the
C++ one, and the pythonic API.

The base API is part of the main repository and should be built
automatically with the rest of the code. I guess it could be packaged as
a separate python3-cvc5 package with very little effort.

The pythonic API is another repository and uses the base API.
https://github.com/cvc5/cvc5_pythonic_api

I don't think packaging the base API would be too much additional work,
since it's from the same source code that produces the packages cvc5,
libcvc5-dev, libcvc5-1 and libcvc5parser1.

Having the pythonic API would be even better, but not necessary.

Best regards,
Celelibi

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

Kernel: Linux 6.1.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
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

-- no debconf information

Bug#1034236: mpd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Florian Schlichting]

I'm AFK this week so won't be able to do an upload either. I agree that putting 
the unit files where systemd.pc says they should go is probably the right thing 
to do. However it feels nonsensical to move files from /usr/lib to /lib only so 
they can be moved back by the /usr-merge; reading #1031695 I don't see anybody 
saying this is a sensible thing to do...

I think we should take a step back and think about how a freshly installed mpd 
package should look like. I think it may actually be a feature that the system 
mpd.service is not enabled and started on a fresh install. On most 
desktop/laptop machines, leaving the system service off and enabling the user 
service is probably the better thing to do. How long has dh-installsystemd been 
disregarding our unit files? We may want to add --no-enable when we apply that 
patch.

So I think in the case of mpd, perhaps nothing is severely broken currently and 
this bug doesn't require fixing for bookworm. Instead, it can perhaps be 
downgraded and fixed with the next regular upload, after the release?

(In addition to fresh installs, we may also want to think about upgrades - do 
running daemons get restarted? Also in the --user case?)

Florian

Am 11. April 2023 21:01:02 MESZ schrieb Geoffroy Youri Berret 
:
>On 4/11/23 17:57, Max Kellermann wrote:
>> On 2023/04/11 17:40, Andreas Henriksson  wrote:
>>> I think 2 is better myself and I'm attaching a proof of concept
>>> debdiff to implement it. (You might want to make a cleaner version.)
>> 
>> Agree.  I think your patch looks quite clean, and if it were submitted
>> to me, I'd merge it (the same would probably be necessary for the user
>> units).
>
>Here is an updated version (with user unit patch).
>
>I did not get through all the thread in #1031695 then I'm not sure about user 
>unit location, but relying on systemd.pc ship them in /usr/lib/systemd/user/, 
>hopes it's fine.
>
>Please review, I'm not super confident with my meson expertise.
>
>I wont be able push these changes until next week, then please go ahead if 
>needed.
>
>Cheers,
>k

Bug#1034267: installation-guide: Location of the install logs is "unfindable"

[Karl O. Pinc]

Source: installation-guide
Severity: minor

Hi,

Information on where the debian installer puts the installation logs
after a successfull install is buried in the section 6.3.9. Troubleshooting.

It's pretty hard to find out where the install logs are.  At least if
you're googling about or reading the installation guide.  (The
directory /var/log/installer/ is pretty self-explainatory but you have
to look there.)

I had planned to submit a patch with new index entries "logs,
installation" and "installation logs".  But there is no index.

So I don't know the right way to fix this.  I suppose the section heading
could be changed to "Troubleshooting and Logging".  But that seems
clunky.

Regards,
Karl

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

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

Bug#1034266: ITP: pam-session-timelimit -- permit configuring time limits for user sessions

[Steve Langasek]

Package: wnpp
Severity: wishlist
Owner: Steve Langasek 

* Package name: pam-session-timelimit
  Version : 0.5
  Upstream Author : Steve Langasek
* URL : https://github.com/vorlonofportland/pam_session_timelimit
* License : LGPLv3
  Programming Lang: C
  Description : PAM module to permit configuring time limits for user 
sessions

This module lets you pass session time limit information to pam_systemd.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1034244: unblock (pre-approval): lua-readline/3.2-2

[Sebastian Ramacher]

Control: tags -1 moreinfo confirmed

On 2023-04-11 12:15:40 +0300, Sergei Golovan wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: lua-readl...@packages.debian.org
> Control: affects -1 + src:lua-readline
> 
> I'd like to upload lua-readline with a bugfix for #1034078 (see [1]).

Please go ahead and remove the moreinfo tag once the new version is
available in unstable.

Cheers

> 
> [ Reason ]
> This upload fixes #1034078. The patch is made upstream and taken
> from newly released version 3.3.
> 
> [ Impact ]
> This bug is a regression in version 3.2 which significantly
> worsens user experience (standard Ctrl+D isn't interpreted as EOF).
> 
> [ Tests ]
> There aren't automated tests, but manual testing using upstream test
> code doesn't reveal any other regressions/bugs.
> 
> [ Risks ]
> The code change is trivial, the bug currently affects the prosody
> packhage in a way that its admin cannot simply exit from the
> prosody server management console.
> 
> [ Checklist ]
>   [+] all changes are documented in the d/changelog
>   [+] I reviewed all changes and I approve them
>   [+] attach debdiff against the package in testing
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034078
> 
> unblock lua-readline/3.2-2

> diff --git a/debian/changelog b/debian/changelog
> index 4456e53..7450934 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,10 @@
> +lua-readline (3.2-2) unstable; urgency=medium
> +
> +  * Fix regression which does not allow to use Ctrl-D (EOF) to close
> +readline session (closes: #1034078).
> +
> + -- Sergei Golovan   Sun, 09 Apr 2023 12:28:12 +0300
> +
>  lua-readline (3.2-1) unstable; urgency=medium
>  
>* New upstream release.
> diff --git a/debian/patches/eof.patch b/debian/patches/eof.patch
> new file mode 100644
> index 000..2ac8eeb
> --- /dev/null
> +++ b/debian/patches/eof.patch
> @@ -0,0 +1,39 @@
> +Author: Upstream
> +Description: Patch restores processing EOF (Ctrl+D), when readline()
> + returns NULL, distinguishable from an empty string.
> +Debian-Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034078
> +
> +--- a/C-readline.c
>  b/C-readline.c
> +@@ -65,7 +65,13 @@
> + /* rl_cleanup_after_signal(); rl_clear_signals();  no effect :-( 1.3 */
> + /* lua_pushstring(L, line); */
> + /* 3.2 did lua_pushstring create a copy of the string ? */
> +-lua_pushfstring(L, "%s", line);   /* 3.2 */
> ++/* lua_pushfstring(L, "%s", line);   3.2 */
> ++if (line == NULL) { /* 3.3 fix by zash.se, Prosody developer */
> ++lua_pushnil(L);
> ++} else {
> ++lua_pushfstring(L, "%s", line);
> ++// lua_pushstring(L, line); should be fine as well
> ++}
> + if (tty_stream != NULL) { fclose(tty_stream); }
> + free(line);  /* 3.2 fixes memory leak */
> + return 1;
> +@@ -135,13 +141,15 @@
> + return 0;
> + }
> + 
> +-static int c_write_history(lua_State *L) {  /* filename in, returncode out 
> */
> ++/* unused ...
> ++static int c_write_history(lua_State *L) {  //  filename in, returncode out
> + size_t len;
> + const char *filename  = lua_tolstring(L, 1, );
> + lua_Integer rc = write_history(filename);
> + lua_pushinteger(L, rc);
> + return 1;
> + }
> ++*/
> + 
> + static int c_history_truncate_file(lua_State *L) { /* filename,num in rc 
> out */
> + size_t len;
> diff --git a/debian/patches/series b/debian/patches/series
> new file mode 100644
> index 000..84626e5
> --- /dev/null
> +++ b/debian/patches/series
> @@ -0,0 +1 @@
> +eof.patch


-- 
Sebastian Ramacher

Bug#1034265: unblock: fsarchiver/0.8.7-1

[Michael Biebl]

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

Please unblock package fsarchiver

[ Reason ]
Creating file systems with recent versions of
btrfs-progs/e2fsprogs/xfsprogs
on recent kernels might make use of kernel/fs features like nrext64 or 
orphan_file.
Older versions of fsarchiver will not know how to handle those fs
features and fail to save/restore a backup.
See e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033117



[ Impact ]
Not shipping an up-to-date fsarchiver might result in failures when
trying to backup/restore xfs/btrfs/ext4 partitions that were created
with features that are unknown to fsarchiver.

[ Tests ]
fsarchiver ships an autopkgtest for ext4 and xfs.
Those tests use the default settings when creating a new file system and
they triggered the ext4 related incompatible changes
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033117

[ Risks ]
fsarchiver is a leaf package, so its effect on other packages is
minimal.

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

The debdiff was created filtering out auto* noise using
git diff debian/0.8.6-2 ':!config.guess' ':!config.sub' ':!*Makefile.in' 
':!configure' ':!aclocal.m4'

unblock fsarchiver/0.8.7-1
diff --git a/ChangeLog b/ChangeLog
index 39bfbda..35ebc94 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,13 @@
 fsarchiver: Filesystem Archiver for Linux [http://www.fsarchiver.org]
 =
+* 0.8.7 (2023-03-19):
+  - Implement support for option "uuid=" for vfat (Marcos Mello)
+  - Update list of btrfs supported features (Marcos Mello)
+  - Add support for the "nrext64" feature on XFS (Marcos Mello)
+  - Do not error out on deleted files when option -A is used (Marcos Mello)
+  - Handle termination by signal in exec_command() (Marcos Mello)
+  - Add support for the "orphan_file" feature in EXT4 (Marcos Mello)
+  - Do not try to save xattrs if not supported by the filesystem (Marcos Mello)
 * 0.8.6 (2021-02-27):
   - Add support for EXT4 fast_commit feature (Marcos Mello)
   - Add support for XFS features inobtcount and bigtime (Marcos Mello)
diff --git a/INSTALL b/INSTALL
index 8865734..e82fd21 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,8 +1,8 @@
 Installation Instructions
 *
 
-   Copyright (C) 1994-1996, 1999-2002, 2004-2016 Free Software
-Foundation, Inc.
+   Copyright (C) 1994-1996, 1999-2002, 2004-2017, 2020-2021 Free
+Software Foundation, Inc.
 
Copying and distribution of this file, with or without modification,
 are permitted in any medium without royalty provided the copyright
@@ -225,7 +225,7 @@ order to use an ANSI C compiler:
 
 and if that doesn't work, install pre-built binaries of GCC for HP-UX.
 
-   HP-UX 'make' updates targets which have the same time stamps as their
+   HP-UX 'make' updates targets which have the same timestamps as their
 prerequisites, which makes it generally unusable when shipped generated
 files such as 'configure' are involved.  Use GNU 'make' instead.
 
diff --git a/compile b/compile
index 23fcba0..df363c8 100755
--- a/compile
+++ b/compile
@@ -3,7 +3,7 @@
 
 scriptversion=2018-03-07.03; # UTC
 
-# Copyright (C) 1999-2020 Free Software Foundation, Inc.
+# Copyright (C) 1999-2021 Free Software Foundation, Inc.
 # Written by Tom Tromey .
 #
 # This program is free software; you can redistribute it and/or modify
diff --git a/configure.ac b/configure.ac
index ec838a3..2948877 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3,8 +3,8 @@
 
 AC_PREREQ(2.59)
 
-AC_INIT([fsarchiver], 0.8.6)
-AC_DEFINE([PACKAGE_RELDATE], "2021-02-27", [Define the date of the release])
+AC_INIT([fsarchiver], 0.8.7)
+AC_DEFINE([PACKAGE_RELDATE], "2023-03-19", [Define the date of the release])
 AC_DEFINE([PACKAGE_FILEFMT], "FsArCh_002", [Define the version of the file 
format])
 AC_DEFINE([PACKAGE_VERSION_A], 0, [Major version number])
 AC_DEFINE([PACKAGE_VERSION_B], 8, [Medium version number])
diff --git a/debian/changelog b/debian/changelog
index f006387..466725d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+fsarchiver (0.8.7-1) unstable; urgency=medium
+
+  * New upstream version 0.8.7
+- Fixes compatibility with e2fsprogs >= 1.47. (Closes: #1033117)
+  * Update debian/watch.
+Use the GitHub API when checking for new upstream releases.
+  * Bump Standards-Version to 4.6.2
+  * Update obsolete Build-Depends e2fslibs-dev => libext2fs-dev
+
+ -- Michael Biebl   Tue, 28 Mar 2023 20:34:29 +0200
+
 fsarchiver (0.8.6-2) unstable; urgency=medium
 
   [ Julian Andres Klode ]
diff --git a/debian/control b/debian/control
index e190dd3..e83f49a 100644
--- a/debian/control
+++ b/debian/control
@@ -10,12 +10,12 @@ Build-Depends: 

Bug#1034264: bullseye-pu: package nvidia-modprobe/470.182.03-1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

Hi,

along with the nvidia-graphics-drivers* packages, I'd like to upgrade
nvidia-modprobe to a new upstream release this time, too.
It's unusual that nvidia-modprobe sees any updates (besides the version
bump) in the older release branches when the corresponding driver
package gets updated, so in order not to have an nvidia-modprobe that
unneccessarily deviates from upstream behavior, lets update that, too.

The corresponding change has been cherry-picked into sid (there is no
530 release yet that includes it, since the last 530 release is a week
older than the 525/470/450 releases that included this change). It is not
yet in bookworm.

+nvidia-modprobe (470.182.03-1) bullseye; urgency=medium
+
+  * New upstream release.
+- Updated nvidia-modprobe to create symbolic links in /dev/char when
+  creating the /dev/nvidia* device nodes. This resolves an issue that
+  prevented the device nodes from working with newer versions of runc:
+  https://github.com/opencontainers/runc/issues/3708
+  * Update Lintian overrides.
+  * Upload to bullseye.
+
+ -- Andreas Beckmann   Tue, 11 Apr 2023 22:21:56 +0200


Andreas
diff --git a/debian/changelog b/debian/changelog
index 5eca61c..b3176cc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+nvidia-modprobe (470.182.03-1) bullseye; urgency=medium
+
+  * New upstream release.
+- Updated nvidia-modprobe to create symbolic links in /dev/char when
+  creating the /dev/nvidia* device nodes. This resolves an issue that
+  prevented the device nodes from working with newer versions of runc:
+  https://github.com/opencontainers/runc/issues/3708
+  * Update Lintian overrides.
+  * Upload to bullseye.
+
+ -- Andreas Beckmann   Tue, 11 Apr 2023 22:21:56 +0200
+
 nvidia-modprobe (470.103.01-1~deb11u1) bullseye; urgency=medium
 
   * Rebuild for bullseye.
diff --git a/debian/copyright b/debian/copyright
index ff0d5ff..26ebb3f 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -9,7 +9,8 @@ Disclaimer:
  NVIDIA drivers in non-free.
 
 Files: *
-Copyright: Copyright (C) 2004-2017 NVIDIA Corporation
+Copyright:
+ Copyright (C) 2004-2023 NVIDIA Corporation
 License: Expat
 
 Files: modprobe-utils/pci-enum.h
@@ -25,7 +26,8 @@ Copyright: (C) Copyright IBM Corporation 2006
 License: Expat
 
 Files: debian/*
-Copyright: © 2014-2022 Andreas Beckmann 
+Copyright:
+ © 2014-2023 Andreas Beckmann 
 License: Expat
 
 License: Expat
diff --git a/debian/gbp.conf b/debian/gbp.conf
index f5b3a2c..47d7377 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,2 +1,5 @@
+[DEFAULT]
+debian-branch = bullseye
+
 [import-orig]
 upstream-vcs-tag = %(version)s
diff --git a/debian/nvidia-modprobe.lintian-overrides 
b/debian/nvidia-modprobe.lintian-overrides
index ecc59fc..d19f35e 100644
--- a/debian/nvidia-modprobe.lintian-overrides
+++ b/debian/nvidia-modprobe.lintian-overrides
@@ -1 +1 @@
-elevated-privileges usr/bin/nvidia-modprobe 4755 root/root
+elevated-privileges 4755 root/root [usr/bin/nvidia-modprobe]
diff --git a/debian/source/lintian-overrides b/debian/source/lintian-overrides
index 8ebed74..f462e54 100644
--- a/debian/source/lintian-overrides
+++ b/debian/source/lintian-overrides
@@ -1,2 +1,2 @@
 # upstream provides no signatures
-debian-watch-does-not-check-gpg-signature
+debian-watch-does-not-check-openpgp-signature
diff --git a/modprobe-utils/nvidia-modprobe-utils.c 
b/modprobe-utils/nvidia-modprobe-utils.c
index 7437751..1a2144f 100644
--- a/modprobe-utils/nvidia-modprobe-utils.c
+++ b/modprobe-utils/nvidia-modprobe-utils.c
@@ -1,5 +1,5 @@
 /*
- * Copyright (c) 2013, NVIDIA CORPORATION.
+ * Copyright (c) 2013-2023, NVIDIA CORPORATION.
  *
  * Permission is hereby granted, free of charge, to any person
  * obtaining a copy of this software and associated documentation
@@ -42,6 +42,7 @@
 #include "nvidia-modprobe-utils.h"
 #include "pci-enum.h"
 
+#define NV_DEV_PATH "/dev/"
 #define NV_PROC_MODPROBE_PATH "/proc/sys/kernel/modprobe"
 #define NV_PROC_MODULES_PATH "/proc/modules"
 #define NV_PROC_DEVICES_PATH "/proc/devices"
@@ -502,6 +503,75 @@ int nvidia_get_file_state(int minor)
 return state;
 }
 
+/*
+ * Symbolically link the /dev/char/ file to the given
+ * device node.
+ */
+static int symlink_char_dev(int major, int minor, const char *dev_path)
+{
+char symlink_path[NV_MAX_CHARACTER_DEVICE_FILE_STRLEN];
+char dev_rel_path[NV_MAX_CHARACTER_DEVICE_FILE_STRLEN];
+struct stat link_status;
+struct stat dev_status;
+int ret;
+
+ret = snprintf(symlink_path, NV_MAX_CHARACTER_DEVICE_FILE_STRLEN,
+   NV_CHAR_DEVICE_NAME, major, minor);
+
+if (ret < 0 || ret >= NV_MAX_CHARACTER_DEVICE_FILE_STRLEN)
+{
+return 0;
+}
+
+/* Verify that the target device node exists and is a character device. */
+if (stat(dev_path, _status) != 0 || !S_ISCHR(dev_status.st_mode))

Bug#1020480: Ready to Implement

[Soren Stoutner]

The dependencies are finally in place so this can be implemented.

To make things simpler for dictionary packagers, we are using a virtual 
package and an unversioned path for the conversion tool so that dictionary 
packagers don’t have to make modifications to their packages when the versions 
of Qt change in Debian.

All you should need to do is the following:

1.  Build-depend on `convert-bdic`.
2.  Use /usr/bin/convert-bdic to do the dictionary conversion.
3.  Place the .bdic files in /usr/share/hunspell-bdic.

More detailed information can be found in the dictionary packager 
documentation at:

file:///usr/share/doc/dictionaries-common-dev/dsdt-policy.html#hunspell-bdic

Thanks,

Soren

-- 
Soren Stoutner
so...@stoutner.com


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

Bug#1033319: Suggestions for ReleaseCheckList

[Paul Gevers]

Hi Adrian,

On 22-03-2023 12:08, Adrian Bunk wrote:

Suggestions for both
https://wiki.debian.org/Teams/ReleaseTeam/ReleaseCheckList
https://wiki.debian.org/Teams/ReleaseTeam/ReleaseCheckList/BookwormCheckList


They are Wiki's ;). But thanks for discussing it first.


   Before the release

Add "Notify the LTS team of the new debian-archive-keyring"


Do you have an example e-mail? Would everybody in the LTS team know what 
this means for them (I don't).



   After the release
 [ ] Propose a micronews item on the #debian-publicity IRC channel


Again, maybe an example? I'm not sure what you expect here from us.


Should this be a subitem of "Notify the publicity team"
in "While Releasing"?


I guess that makes sense.


   After the release
 [ ] Update the Project History document and upload to stable-p-u

This could be moved to (and uploaded) "Before the release".


Are you sure? That means we'd be predicting the future in a history 
document. I guess you mean once the date is fixed and assuming we 
release on schedule.



   After the release
 [ ] Check with udd maintainers that the hardcoded values are updated (see 
SuitesAndReposExtension#udd)
 [ ] Check with buildd team that buildds know about trixie. (see 
SuitesAndReposExtension#wanna-build)
 [ ] Check with other service/package maintainers that all the other 
hardcoded suite names or codenames are updated

IMHO these should be moved to "Before the release", otherwise there might be
stress for people who realize at short notice that urgent work has to be done.


But these things can't be *done* before the release, right? So maybe 
*add* a "notify" on these topics?



It should link to SuitesAndReposExtension, or be replaced with a list whom to 
notify,


Incomplete sentence?

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034263: RFS: urlwatch/2.26-1 -- monitors webpages for you

[Maxime Werlen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "urlwatch":

 * Package name : urlwatch
   Version  : 2.26-1
   Upstream contact : Thomas Perl 
 * URL  : https://thp.io/2008/urlwatch/
 * License  : BSD-3-clause
 * Vcs  : https://salsa.debian.org/mwerlen/urlwatch
   Section  : web

The source builds the following binary packages:

  urlwatch - monitors webpages for you

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/urlwatch/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/u/urlwatch/urlwatch_2.26-1.dsc

Changes since the last upload:

 urlwatch (2.26-1) unstable; urgency=medium
 .
   * New upstream release
   * Update copyright years
   * Update required python version
   * Update patches
   * Update standards
   * Remove old NEWS file, now unnecessary

Regards,

signature.asc
Description: PGP signature

Bug#1034262: buffer overflow on peculiar drive

[Antoine Beaupre]

Package: nwipe
Version: 0.34-1+b1
Severity: normal
Tags: patch

I've used nwipe probably dozens of times on various times, and it
works fairly reliably. So I was surprised to find out it chokes on
this tiny little SSD drive here:

anarcat@angela:~$ sudo nwipe /dev/sdc
*** buffer overflow detected ***: terminated
Aborted
anarcat@angela:~[SIGABRT]$

Well isn't this odd! This is a fiarly normal drive:

anarcat@angela:~$ sudo smartctl -i -qnoserial /dev/sdc
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-7-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Crucial/Micron RealSSD m4/C400/P400
Device Model: M4-CT512M4SSD1
Firmware Version: 040H
User Capacity:512 110 190 592 bytes [512 GB]
Sector Size:  512 bytes logical/physical
Rotation Rate:Solid State Device
Form Factor:  2.5 inches
TRIM Command: Available, deterministic
Device is:In smartctl database 7.3/5319
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:Tue Apr 11 15:42:51 2023 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

And speaking of smartctl, I suspect it's where nwipe chokes, because
as it turns out it crashes right after calling it, according to
strace:


anarcat@angela:~$ sudo strace -s8192 nwipe /dev/sdc
execve("/usr/sbin/nwipe", ["nwipe", "/dev/sdc"], 0x7ffda312d030 /* 15 vars */) 
= 0
brk(NULL)   = 0x55afbf726000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbb351ae000
[...]
read(3, "smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-7-amd64] (local 
build)\nCopyright (C) 2002-22, Bruce Allen, Christian Franke, 
www.smartmontools.org\n\n", 4096) = 150
read(3, "=== START OF INFORMATION SECTION ===\nModel Family: Crucial/Micron 
RealSSD m4/C400/P400\nDevice Model: M4-CT512M4SSD1\nSerial Number:
REDACTED\nLU WWN Device Id: 5 00a075 109210beb\nFirmware Version: 040H\n", 
4096) = 223
read(3, "User Capacity:512\342\200\257110\342\200\257190\342\200\257592 
bytes [512 GB]\nSector Size:  512 bytes logical/physical\nRotation Rate:
Solid State Device\n", 4096) = 137
read(3, "Form Factor:  2.5 inches\nTRIM Command: Available, 
deterministic\nDevice is:In smartctl database 7.3/5319\nATA Version is: 
  ACS-2, ATA8-ACS T13/1699-D revision 6\nSATA Version is:  SATA 3.0, 6.0 Gb/s 
(current: 6.0 Gb/s)\nLocal Time is:Tue Apr 11 15:44:34 2023 EDT\nSMART 
support is: Available - device has SMART capability.\nSMART support is: 
Enabled\n\n", 4096) = 366
read(3, "", 4096)   = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=72484, si_uid=0, 
si_status=0, si_utime=0, si_stime=0} ---
close(3)= 0
wait4(72484, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 72484
writev(2, [{iov_base="*** ", iov_len=4}, {iov_base="buffer overflow detected", 
iov_len=24}, {iov_base=" ***: terminated\n", iov_len=17}], 3*** buffer overflow 
detected ***: terminated
) = 45
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbb351ad000
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
gettid()= 72472
getpid()= 72472
tgkill(72472, 72472, SIGABRT)   = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=72472, si_uid=0} ---
+++ killed by SIGABRT +++
Aborted

Of you look at the spaces in the "User Capacity" field more closely,
you'll notice it's actually a little odd. Those are not mere spaces in
those thousands separators, they are actually `U+202F NARROW NO-BREAK
SPACE` (represented by \342\200\257 in strace), according to
unicode(1). That, in itself, shouldn't be a problem: my terminal,
foot(1), is handling that fine, for example. But I bet it's the cause
of the overflow here.

Looking at gdb:

(gdb) bt
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, 
no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1  0x77d8dd2f in __pthread_kill_internal (signo=6, 
threadid=) at ./nptl/pthread_kill.c:78
#2  0x77d3eef2 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/posix/raise.c:26
#3  0x77d29472 in __GI_abort () at ./stdlib/abort.c:79
#4  0x77d822d0 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x77e9c210 "*** %s ***: terminated\n")
at ../sysdeps/posix/libc_fatal.c:155
#5  0x77e1af32 in __GI___fortify_fail (
msg=msg@entry=0x77e9c1b6 "buffer overflow detected")
at ./debug/fortify_fail.c:26
#6  0x77e19a40 in __GI___chk_fail () at ./debug/chk_fail.c:28
#7  0x77e19322 in __strcpy_chk (dest=dest@entry=0x55573622 "", 
src=src@entry=0x7fffe850 "125009210BEBUU", 
destlen=destlen@entry=21) at ./debug/strcpy_chk.c:30
#8  

Bug#1034261: autofs attempts communication with portmapper (port 111) even for NFS4 mounts

[Tobias Rupf]

Package: autofs
Version: 5.1.8-1+b2
Severity: normal
Tags: upstream

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
upgrdae from bullseye to testing

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I use autoount to mount a nfs4 share. Normal mount with mount command does work
automount did work in bullseye but not in testing

   * What was the outcome of this action?
relevant error meessage from automount: get_portmap_client: error 0x3 getting
portmap client
A workaround is to add the option "port=2049" to the automount map as suggested
here: https://www.suse.com/support/kb/doc/?id=20650
With this option automount is working again, but it shouldn't be required for
NFS v4 mounts when no portmapper is required and running

   * What outcome did you expect instead?
successful mount when moving into mount directory without the extra port option

If you don't want to fix the automount program itself maybe the otion can be
added to the script /etc/auto.net for nfs4 mounts

*** End of the template - remove these template lines ***


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

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

Versions of packages autofs depends on:
ii  init-system-helpers  1.65.2
ii  libc62.36-8
ii  libnsl2  1.3.0-2
ii  libtirpc31.3.3+ds-1
ii  libxml2  2.9.14+dfsg-1.1+b3
ii  ucf  3.0043+nmu1

Versions of packages autofs recommends:
ii  e2fsprogs   1.47.0-2
ii  kmod30+20221128-1
ii  nfs-common  1:2.6.2-4

autofs suggests no packages.

-- no debconf information

Bug#1034260: update reportbug for bookworm release

[Paul Gevers]

Package: reportbug

Dear maintainer,

To avoid the need to update reportbug in a bookworm point release and 
prevent bug 992332 from happening in this release, can we have a version 
of reportbug that does the right thing in bookworm?


Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#978043: Bug#1016827: Fixed

[ng]

Please delete this email and the one I'm quoting; sent to Bug#978043, it 
was by accident.



> Hi
>
> Well, at least for linux 5.10.162-1 the bug is still present, kernel
> panic at the very end of reboot/power off process,  can be sorted out
> with the 'ccp.dmaengine=0' parameter.
>
> That's all I  can share,  the archlinux bug report I quoted didn't had
> any activity since feb 2022, and the lkml I also quoted had the same
> luck.  All I know is that using linux from backports works correctly
> with debian's default parameters.
>
>
> (Oops, once again, sending the email to the wrong receipt)
>
>
> > Source-Version: 6.1.15-1
> >
> > Hi
> >
> > On Mon, Apr 10, 2023 at 09:01:13AM -0300, ng wrote:
> >> Morning.
> >>
> >> I just booted into linux 6.1.15-1~bpo11+1 and it was already fixed,
> >> no need
> >> to use use 'ccp.dmaengine=0' anymore.  Great!
> >>
> >> Bug resolved.
> > Thanks, marking it as fixed accordingly, though would be nice to
> > better understand the issue and to verify if it get fixed as well in
> > the 5.10.y stable series.
> >
> > Regards,
> > Salvatore
>
>

Bug#1034255: libgtk-4-1: Getting Bail out! Gdk:ERROR random crashes on x11, which makes the app closes itself

[Simon McVittie]

Control: retitle -1 libgtk-4-1: intermittent crashes on X11 in 
sync_counter_for_end_frame: assertion failed: 
(impl->toplevel->extended_update_counter != None)
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/-/issues/5440

On Tue, 11 Apr 2023 at 14:00:07 -0300, Thiago Bellini Ribeiro wrote:
> Bail out! Gdk:ERROR

For future reference, this is the least interesting/distinctive part of the
assertion failure message, and the least useful to distinguish between
different crashes. The parts that matter most are the function that has the
assertion (in this case sync_counter_for_end_frame) and the assertion itself
(in this case impl->toplevel->extended_update_counter != None).

smcv

Bug#1016827: Fixed

[ng]

Hi

Well, at least for linux 5.10.162-1 the bug is still present, kernel 
panic at the very end of reboot/power off process,  can be sorted out 
with the 'ccp.dmaengine=0' parameter.


That's all I  can share,  the archlinux bug report I quoted didn't had 
any activity since feb 2022, and the lkml I also quoted had the same 
luck.  All I know is that using linux from backports works correctly 
with debian's default parameters.



(Oops, once again, sending the email to the wrong receipt)



Source-Version: 6.1.15-1

Hi

On Mon, Apr 10, 2023 at 09:01:13AM -0300, ng wrote:

Morning.

I just booted into linux 6.1.15-1~bpo11+1 and it was already fixed, 
no need

to use use 'ccp.dmaengine=0' anymore.  Great!

Bug resolved.

Thanks, marking it as fixed accordingly, though would be nice to
better understand the issue and to verify if it get fixed as well in
the 5.10.y stable series.

Regards,
Salvatore

Bug#1034259: ftp.debian.org: add SRM key to https://ftp-master.debian.org/keys.html

[Paul Gevers]

Package: ftp.debian.org
Severity: normal

Dear ftp masters,

Like every release cycle, we'd like to have the Release Team key
mentioned on https://ftp-master.debian.org/keys.html

The key can be found in
/usr/share/keyrings/debian-archive-bookworm-stable.gpg
once the bookworm version of `debian-archive-keyring` is installed.

Paul

Bug#1034236: mpd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Geoffroy Youri Berret]

On 4/11/23 17:57, Max Kellermann wrote:

On 2023/04/11 17:40, Andreas Henriksson  wrote:

I think 2 is better myself and I'm attaching a proof of concept
debdiff to implement it. (You might want to make a cleaner version.)


Agree.  I think your patch looks quite clean, and if it were submitted
to me, I'd merge it (the same would probably be necessary for the user
units).


Here is an updated version (with user unit patch).

I did not get through all the thread in #1031695 then I'm not sure about 
user unit location, but relying on systemd.pc ship them in 
/usr/lib/systemd/user/, hopes it's fine.


Please review, I'm not super confident with my meson expertise.

I wont be able push these changes until next week, then please go ahead 
if needed.


Cheers,
kdiff -Nru mpd-0.23.12/debian/changelog mpd-0.23.12/debian/changelog
--- mpd-0.23.12/debian/changelog2023-01-21 21:32:37.0 +0100
+++ mpd-0.23.12/debian/changelog2023-04-11 19:36:16.0 +0200
@@ -1,3 +1,11 @@
+mpd (0.23.12-2) UNRELEASED; urgency=medium
+
+  [ Andreas Henriksson ]
+  * Add debian/patches/systemdsystemunitdir.patch
+  * Add systemd build-dep for systemd.pc
+
+ -- Geoffroy Youri Berret   Tue, 11 Apr 2023 19:36:16 +0200
+
 mpd (0.23.12-1) unstable; urgency=medium
 
   * New upstream version 0.23.12
diff -Nru mpd-0.23.12/debian/control mpd-0.23.12/debian/control
--- mpd-0.23.12/debian/control  2023-01-21 21:32:37.0 +0100
+++ mpd-0.23.12/debian/control  2023-04-11 19:36:16.0 +0200
@@ -55,6 +55,7 @@
libsoxr-dev,
libsqlite3-dev,
libsystemd-dev [linux-any],
+   systemd [linux-any],
libupnp-dev (>= 1.8~),
liburing-dev [linux-any],
libvorbis-dev [!armel],
diff -Nru mpd-0.23.12/debian/patches/series mpd-0.23.12/debian/patches/series
--- mpd-0.23.12/debian/patches/series   2023-01-21 21:32:37.0 +0100
+++ mpd-0.23.12/debian/patches/series   2023-04-11 19:36:16.0 +0200
@@ -1,3 +1,4 @@
 # Debian-specific
 systemd_honor_MPDCONF.patch
 mpd.service.documentation.user.patch
+systemdsystemunitdir.patch
diff -Nru mpd-0.23.12/debian/patches/systemdsystemunitdir.patch 
mpd-0.23.12/debian/patches/systemdsystemunitdir.patch
--- mpd-0.23.12/debian/patches/systemdsystemunitdir.patch   1970-01-01 
01:00:00.0 +0100
+++ mpd-0.23.12/debian/patches/systemdsystemunitdir.patch   2023-04-11 
19:36:16.0 +0200
@@ -0,0 +1,28 @@
+--- a/systemd/system/meson.build
 b/systemd/system/meson.build
+@@ -1,5 +1,11 @@
+ systemd_system_unit_dir = get_option('systemd_system_unit_dir')
+ if systemd_system_unit_dir == ''
++  systemd = dependency('systemd', required: false)
++  if systemd.found()
++  systemd_system_unit_dir = 
systemd.get_pkgconfig_variable('systemdsystemunitdir')
++  endif
++endif
++if systemd_system_unit_dir == ''
+   systemd_system_unit_dir = join_paths(get_option('prefix'), 'lib', 
'systemd', 'system')
+ endif
+ 
+--- a/systemd/user/meson.build
 b/systemd/user/meson.build
+@@ -1,5 +1,11 @@
+ systemd_user_unit_dir = get_option('systemd_user_unit_dir')
+ if systemd_user_unit_dir == ''
++  systemd = dependency('systemd', required: false)
++  if systemd.found()
++systemd_user_unit_dir = 
systemd.get_pkgconfig_variable('systemduserunitdir')
++  endif
++endif
++if systemd_user_unit_dir == ''
+   systemd_user_unit_dir = join_paths(get_option('prefix'), 'lib', 'systemd', 
'user')
+ endif
+ 

Bug#978043: Bug#1016827: Fixed

[ng]

Hi

Well, at least for linux 5.10.162-1 the bug is still present, kernel 
panic at the very end of reboot/power off process,  can be sorted out 
with the 'ccp.dmaengine=0' parameter.


That's all I  can share,  the archlinux bug report I quoted didn't had 
any activity since feb 2022, and the lkml I also quoted had the same 
luck.  All I know is that using linux from backports works correctly 
with debian's default parameters.



(Oops, once again, sending the email to the wrong receipt)



Source-Version: 6.1.15-1

Hi

On Mon, Apr 10, 2023 at 09:01:13AM -0300, ng wrote:

Morning.

I just booted into linux 6.1.15-1~bpo11+1 and it was already fixed, 
no need

to use use 'ccp.dmaengine=0' anymore.  Great!

Bug resolved.

Thanks, marking it as fixed accordingly, though would be nice to
better understand the issue and to verify if it get fixed as well in
the 5.10.y stable series.

Regards,
Salvatore

Bug#1034258: opensc: with the new opensc version in Debian testing/sid I am unable to use the new Italian CNS

[Davide Prina]

Package: opensc
Version: 0.23.0-0.2
Severity: normal
X-Debbugs-Cc: davide.pr...@null.net

Dear Maintainer,

with the new opensc version found in Debian testing/sid I was unable to use the 
new Italian CNS.
I think that the wrong type card is selected (it is selected the CNS Generic 
one with type:23002), but I'm unable to force the use of the correct one.

First I list all the differences I have found.
Then I will show what I have done to let the new Italian CNS work correctly in 
a .deb I have created months ago.

I show rows starting with OK for the working opensc and with KO for the not 
working opensc

KO Manufacturer ID: IC: Infineon; mask: Oberthur Card Systems
OK Manufacturer ID: IC: Infineon; mask: IDEMIA (Oberthur)

KO Key length: 1024
OK Key length: 2048

KO  token flags: token initialized
OK  token flags: login required, token initialized, PIN initialized, 
user PIN locked

KO  firmware version   : 0.0
OK  firmware version   : 32.0

KO  pin min/max: 4/8
OK  pin min/max: 5/8

KO [pkcs15-tool] card.c:sc_connect_card: card info name:'CNS card', type:23002, 
flags:0x0, max_send/recv_size:255/256
OK [pkcs15-tool] card.c:sc_connect_card: card info name:'CNS card', type:23003, 
flags:0x0, max_send/recv_size:65535/65536

I think that the problem is the type, the 23003 work and the 23002 do not work.

I have try to foce the use of type:23003 in /etc/opensc/opensc.conf but I was 
unable to have it.
I have made some configuration, but no one work to force the type, I can
only force the card name to not check all possible cards.

I show here the log in witch the type is selected

KO) in this one it select the wrong type
[pkcs15-tool] apdu.c:sc_single_transmit: returning with: 0 (Success)
[pkcs15-tool] apdu.c:sc_transmit: returning with: 0 (Success)
[pkcs15-tool] card.c:sc_unlock: called
[pkcs15-tool] reader-pcsc.c:pcsc_unlock: called
[pkcs15-tool] iso7816.c:iso7816_check_sw: File or application not found
[pkcs15-tool] card-cac.c:cac_select_file_by_type: returning with: -1201 (File 
not found)
[pkcs15-tool] card.c:sc_connect_card: trying driver 'itacns'
[pkcs15-tool] card.c:match_atr_table: ATR : 
3b:ff:18:00:00:81:31:fe:45:00:6b:05:05:20:00:01:21:01:43:4e:53:10:31:80:79
[pkcs15-tool] card.c:match_atr_table: ATR try : 
3b:f4:18:00:ff:81:31:80:55:00:31:80:00:c7
[pkcs15-tool] card.c:match_atr_table: ignored - wrong length
[pkcs15-tool] card-itacns.c:itacns_match_card: Matching 3b against atr[0] == 3b
[pkcs15-tool] card-itacns.c:itacns_match_card: Matching 31 against atr[6] == 31
[pkcs15-tool] card-itacns.c:itacns_match_card: Matching 0 against atr[9] == 0
[pkcs15-tool] card-itacns.c:itacns_match_card: Matching 6b against atr[10] == 6b
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 1 against atr[15] 
== 1
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 43 against atr[18] 
== 43
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 4e against atr[19] 
== 4e
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 53 against atr[20] 
== 53
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 31 against atr[22] 
== 31
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 80 against atr[23] 
== 80
[pkcs15-tool] card.c:sc_connect_card: matched: Italian CNS
[pkcs15-tool] card-itacns.c:itacns_init: called
[pkcs15-tool] card.c:match_atr_table: ATR : 
3b:ff:18:00:00:81:31:fe:45:00:6b:05:05:20:00:01:21:01:43:4e:53:10:31:80:79
[pkcs15-tool] card.c:match_atr_table: ATR try : 
3b:f4:18:00:ff:81:31:80:55:00:31:80:00:c7
[pkcs15-tool] card.c:match_atr_table: ignored - wrong length
[pkcs15-tool] card-itacns.c:itacns_match_card: Matching 3b against atr[0] == 3b
[pkcs15-tool] card-itacns.c:itacns_match_card: Matching 31 against atr[6] == 31
[pkcs15-tool] card-itacns.c:itacns_match_card: Matching 0 against atr[9] == 0
[pkcs15-tool] card-itacns.c:itacns_match_card: Matching 6b against atr[10] == 6b
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 1 against atr[15] 
== 1
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 43 against atr[18] 
== 43
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 4e against atr[19] 
== 4e
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 53 against atr[20] 
== 53
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 31 against atr[22] 
== 31
[pkcs15-tool] card-itacns.c:itacns_match_cns_card: Matching 80 against atr[23] 
== 80
[pkcs15-tool] card.c:sc_connect_card: card info name:'CNS card', type:23002, 
flags:0x0, max_send/recv_size:255/256

OK) in this one it select the working type
[pkcs15-tool] apdu.c:sc_single_transmit: returning with: 0 (Success)
[pkcs15-tool] apdu.c:sc_transmit: returning with: 0 (Success)
[pkcs15-tool] card.c:sc_unlock: called
[pkcs15-tool] reader-pcsc.c:pcsc_unlock: called
[pkcs15-tool] iso7816.c:iso7816_check_sw: File or application not found
[pkcs15-tool] card-cac.c:cac_select_file_by_type: returning with: -1201 (File 
not found)
[pkcs15-tool] 

Bug#979308: This Bug is already fixed in Ubuntu

[mails . bugs . debian . org]

Ubuntu fixed this bug with


jq (1.6-2.1ubuntu1) hirsute; urgency=medium

 [ Alex Murray ]
 * Fix fromdate when local time is during daylight savings (LP: #1910162)
   - d/p/fix-ftbfs-when-localtime-is-dst.patch: Backport upstream patch
 which ensures fromdate uses the correct time during daylight savings

-- Christian Ehrhardt   Tue, 05 Jan 
2021 08:03:50 +0100

Bug#979308: This Bug is already fixed in Ubuntu

[Gunter Ohrner]

Ubuntu fixed this bug with


jq (1.6-2.1ubuntu1) hirsute; urgency=medium

 [ Alex Murray ]
 * Fix fromdate when local time is during daylight savings (LP: #1910162)
   - d/p/fix-ftbfs-when-localtime-is-dst.patch: Backport upstream patch
 which ensures fromdate uses the correct time during daylight savings

-- Christian Ehrhardt   Tue, 05 Jan 
2021 08:03:50 +0100

Bug#1034257: accountsservice: autopkgtest regression: times out when run on bookworm kernel

[Paul Gevers]

Source: accountsservice
Version: 22.08.8-6
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: timeout

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails when run on a 
bookworm kernel. Last month I started to upgrade the workers of 
ci.debian.net on some architectures. The architectures that I upgraded 
now fail with a timeout. I could reproduce the issue on amd64 locally (I 
run bookworm) while on ci.d.n it still passes (amd64 on ci.d.n still 
runs bullseye). Please let me know if you have difficulty getting 
information from the test and you want me to extract something from the 
testbed.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/arm64/a/accountsservice/32778735/log.gz

autopkgtest [22:30:43]: test pygi.py: [---
autopkgtest [01:17:24]: ERROR: timed out on command "su -s /bin/bash 
debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || 
true;  . ~/.profile >/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.cjt8dc2h/downtmp/build.ItQ/src"; mkdir 
-p -m 1777 -- "/tmp/autopkgtest-lxc.cjt8dc2h/downtmp/pygi.py-artifacts"; 
export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.cjt8dc2h/downtmp/pygi.py-artifacts"; 
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.cjt8dc2h/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.cjt8dc2h/downtmp/autopkgtest_tmp"; 
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; 
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=4; unset LANGUAGE 
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES 
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT 
LC_IDENTIFICATION LC_ALL;cd "$buildtree"; chmod +x 
/tmp/autopkgtest-lxc.cjt8dc2h/downtmp/build.ItQ/src/debian/tests/pygi.py; 
exec /tmp/autopkgtest-lxc.cjt8dc2h/downtmp/wrapper.sh 
--script-pid-file=/tmp/autopkgtest_script_pid 
--stderr=/tmp/autopkgtest-lxc.cjt8dc2h/downtmp/pygi.py-stderr 
--stdout=/tmp/autopkgtest-lxc.cjt8dc2h/downtmp/pygi.py-stdout -- 
/tmp/autopkgtest-lxc.cjt8dc2h/downtmp/build.ItQ/src/debian/tests/pygi.py 
;" (kind: test)

autopkgtest [01:17:24]: test pygi.py: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034149: unblock: glib2.0/2.74.6-2

[Paul Gevers]

Hi,

On 11-04-2023 15:21, Simon McVittie wrote:

Uploaded and built on all release architectures. There seem to be reports
of autopkgtest regressions, I'm not sure which of those are flaky and which
(if any) are genuine issues.


A brief inspection suggests they are all flaky. I rescheduled most of them.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#200715: ITP - stepmania

[Andres Salomon]

I briefly used this about a year ago (but ended up not using it, so I'm 
not interested in maintaining it).


But FYI, here's what I used to build it on bullseye. It's suppose to 
builds against ffmpeg, but the ffmpeg API has moved on since the last 
Stepmania release in 2018. I ended up just disabling ffmpeg.



Build-deps:
cmake libgtk2.0-dev libjpeg-dev libmad0-dev libvorbis-dev nasm 
libudev-dev
libbz2-dev libva-dev libglew-dev libpulse-dev libjack-dev  
libasound2-dev

libavcodec-dev libavformat-dev libswscale-dev


cd Build && cmake -D WITH_FFMPEG=OFF .. && make -j4 && make install

Bug#1034256: mpv drops frames when you pause the video at least 10 seconds then play again.

[acer]

Package: mpv
Version: 0.35.1-3
Severity: normal
X-Debbugs-Cc: elcan.osmano...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   
I think it happened after the 0.35.1-3 update. at least I noticed the bug after 
that update.

I played a video, then paused it for a wile. after resuming the playback I 
noticed a lot of framedrops (frameskips). the bug is repeatable. just play a 
video, then pause it for at least 10 seconds. resume the playback. I did test 
it on more than 10 videos with h264 h265 codecs,with and without vaapi or  mpv 
config files. all of the results were the same.

the outcome was framedrops after pausing the video for more than 10 seconds.

the outcome I expected was to resume the playback without framedrops.
*** End of the template - remove these template lines ***


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

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

Versions of packages mpv depends on:
ii  libarchive13  3.6.2-1
ii  libasound21.2.8-1+b1
ii  libass9   1:0.17.1-1
ii  libavcodec59  7:5.1.2-3
ii  libavdevice59 7:5.1.2-3
ii  libavfilter8  7:5.1.2-3
ii  libavformat59 7:5.1.2-3
ii  libavutil57   7:5.1.2-3
ii  libbluray21:1.3.4-1
ii  libc6 2.36-8
ii  libcaca0  0.99.beta20-3
ii  libcdio-cdda2 10.2+2.0.1-1
ii  libcdio-paranoia2 10.2+2.0.1-1
ii  libcdio19 2.1.0-4
ii  libdrm2   2.4.114-1+b1
ii  libdvdnav46.1.1-1
ii  libegl1   1.6.0-1
ii  libgbm1   22.3.6-1+deb12u1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-2
ii  libjpeg62-turbo   1:2.1.5-2
ii  liblcms2-22.14-2
ii  liblua5.2-0   5.2.4-3
ii  libmujs2  1.3.2-1
ii  libpipewire-0.3-0 0.3.65-3
ii  libplacebo208 4.208.0-3
ii  libpulse0 16.1+dfsg1-2+b1
ii  librubberband23.1.2+dfsg0-1
ii  libsdl2-2.0-0 2.26.4+dfsg-1
ii  libsixel1 1.10.3-3
ii  libswresample47:5.1.2-3
ii  libswscale6   7:5.1.2-3
ii  libuchardet0  0.0.7-1
ii  libva-drm22.17.0-1
ii  libva-wayland22.17.0-1
ii  libva-x11-2   2.17.0-1
ii  libva22.17.0-1
ii  libvdpau1 1.5-2
ii  libvulkan11.3.239.0-1
ii  libwayland-client01.21.0-1
ii  libwayland-cursor01.21.0-1
ii  libwayland-egl1   1.21.0-1
ii  libx11-6  2:1.8.4-2
ii  libxext6  2:1.3.4-1+b1
ii  libxinerama1  2:1.1.4-3
ii  libxkbcommon0 1.5.0-1
ii  libxpresent1  1.0.0-2+b10
ii  libxrandr22:1.5.2-2+b1
ii  libxss1   1:1.2.3-1
ii  libxv12:1.0.11-1.1
ii  libzimg2  3.0.4+ds1-1
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages mpv recommends:
ii  xdg-utils  1.1.3-4.1
ii  yt-dlp 2023.03.04-1

Versions of packages mpv suggests:
pn  libcuda1  

-- no debconf information

Bug#1034255: libgtk-4-1: Getting Bail out! Gdk:ERROR random crashes on x11, which makes the app closes itself

[Thiago Bellini Ribeiro]

Package: libgtk-4-1
Version: 4.8.3+ds-2
Severity: important
Tags: upstream
X-Debbugs-Cc: hackedbell...@gmail.com

I sometimes experience this when closing a tab on gnome-console (kgx). I also
got this when trying to shift+del a selection of files on nautilus. In both
cases the whole app will crash and close.
It is really random, but since I work in my terminal a lot I usually get 1 or 2
crashes per day.

Just had a situation here in gnome-console and got this:
2023-04-11T13:44:37.203800-03:00 behemoth org.gnome.Console[3584]:
Gdk:ERROR:../../../gdk/x11/gdksurface-x11.c:606:sync_counter_for_end_frame:
assertion failed: (impl->toplevel->extended_update_counter != None)
2023-04-11T13:44:37.203843-03:00 behemoth org.gnome.Console[3584]: Bail out!
Gdk:ERROR:../../../gdk/x11/gdksurface-x11.c:606:sync_counter_for_end_frame:
assertion failed: (impl->toplevel->extended_update_counter != None)

This is the related upstream issue:
https://gitlab.gnome.org/GNOME/gtk/-/issues/5440


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

Kernel: Linux 6.1.0-7-amd64 (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 libgtk-4-1 depends on:
ii  adwaita-icon-theme43-1
ii  hicolor-icon-theme0.17-2
ii  libc6 2.36-9
ii  libcairo-gobject2 1.16.0-7
ii  libcairo-script-interpreter2  1.16.0-7
ii  libcairo2 1.16.0-7
ii  libcloudproviders00.3.1-2
ii  libcolord21.4.6-2.2
ii  libcups2  2.4.2-3
ii  libepoxy0 1.5.10-1
ii  libfontconfig12.14.1-4
ii  libfribidi0   1.0.8-2.1
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1+b1
ii  libglib2.0-0  2.74.6-2
ii  libgraphene-1.0-0 1.10.8-1
ii  libgtk-4-common   4.8.3+ds-2
ii  libharfbuzz0b 6.0.0+dfsg-3
ii  libjpeg62-turbo   1:2.1.5-2
ii  libpango-1.0-01.50.12+ds-1
ii  libpangocairo-1.0-0   1.50.12+ds-1
ii  libpangoft2-1.0-0 1.50.12+ds-1
ii  libpng16-16   1.6.39-2
ii  libtiff6  4.5.0-5
ii  libwayland-client01.21.0-1
ii  libwayland-egl1   1.21.0-1
ii  libx11-6  2:1.8.4-2
ii  libxcursor1   1:1.2.1-1
ii  libxdamage1   1:1.1.6-1
ii  libxext6  2:1.3.4-1+b1
ii  libxfixes31:6.0.0-2
ii  libxi62:1.8-1+b1
ii  libxinerama1  2:1.1.4-3
ii  libxkbcommon0 1.5.0-1
ii  libxrandr22:1.5.2-2+b1
ii  shared-mime-info  2.2-1

Versions of packages libgtk-4-1 recommends:
ii  iso-codes4.13.0-1
ii  libgtk-4-bin 4.8.3+ds-2
ii  librsvg2-common  2.54.5+dfsg-1

Versions of packages libgtk-4-1 suggests:
ii  gvfs  1.50.3-1
pn  libgtk-4-media-gstreamer | libgtk-4-media-ffmpeg  

-- no debconf information

Bug#1034254: polybar: Doesn't launch (even without any config modifications) after install.

[rootsquid]

Package: polybar
Version: 3.6.3-1
Severity: normal
X-Debbugs-Cc: rootsqui...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***
   After I've installed debian sid I was looking for to use polybar and install
it from official repository.
  used sudo apt-get polybar

  Receive errors after typing just 'polybar':

notice: Parsing config file: /etc/polybar/config.ini
notice: Listening for IPC messages (PID: 39118)
warn: No monitor specified, using "DP-0"
notice: Loading module 'xworkspaces' of type 'internal/xworkspaces'
notice: Loading module 'xwindow' of type 'internal/xwindow'
notice: Loading module 'filesystem' of type 'internal/fs'
notice: Loading module 'pulseaudio' of type 'internal/pulseaudio'
notice: pulseaudio: using default sink alsa_output.pci-_00_1f.3.analog-
stereo
notice: Loading module 'xkeyboard' of type 'internal/xkeyboard'
notice: Loading module 'memory' of type 'internal/memory'
notice: Loading module 'cpu' of type 'internal/cpu'
notice: Loading module 'wlan' of type 'internal/network'
error: Disabling module "wlan" (reason: No interface found for type 'wireless')
notice: Loading module 'eth' of type 'internal/network'
notice: module/eth: Discovered wired interface enp0s31f6
notice: Loading module 'date' of type 'internal/date'
notice: Loaded 9 modules
notice: Loaded font "monospace" (name=Noto Sans Mono, offset=2,
file=/usr/share/fonts/truetype/noto/NotoSansMono-Regular.ttf)
error: background_manager: Failed to copy slice of root pixmap (XCB_MATCH (8))
error: Fatal Error in eventloop: XCB_MATCH (8)
notice: Termination signal received, shutting down...
error: ./src/components/eventloop.cpp:187: libuv error for
'uv_loop_close(m_loop.get())': resource busy or locked

*** End of the template - remove these template lines ***


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

Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 polybar depends on:
ii  libasound2 1.2.8-1+b1
ii  libc6  2.36-9
ii  libcairo2  1.16.0-7
ii  libcurl4   7.88.1-8
ii  libfontconfig1 2.14.1-4
ii  libfreetype6   2.12.1+dfsg-4
ii  libgcc-s1  12.2.0-14
ii  libjsoncpp25   1.9.5-4
ii  libmpdclient2  2.20-1+b1
ii  libnl-3-2003.7.0-0.2+b1
ii  libnl-genl-3-200   3.7.0-0.2+b1
ii  libpulse0  16.1+dfsg1-2+b1
ii  libstdc++6 12.2.0-14
ii  libuv1 1.44.2-1
ii  libxcb-composite0  1.15-1
ii  libxcb-cursor0 0.1.4-1
ii  libxcb-ewmh2   0.4.1-1.1
ii  libxcb-icccm4  0.4.1-1.1
ii  libxcb-randr0  1.15-1
ii  libxcb-xkb11.15-1
ii  libxcb-xrm01.0-3+b1
ii  libxcb11.15-1

polybar recommends no packages.

polybar suggests no packages.

-- no debconf information

Bug#1034253: RFS: dhcpdump/1.8-7~bpo11+1 -- Parse DHCP packets from interface

[Boian Bonev]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "dhcpdump":

 * Package name : dhcpdump
   Version  : 1.8-7~bpo11+1
   Upstream contact : [fill in name and email of upstream]
 * URL  : http://www.mavetju.org/download/
 * License  : BSD-2-clause
 * Vcs  : [fill in URL of packaging vcs]
   Section  : admin

The source builds the following binary packages:

  dhcpdump - Parse DHCP packets from interface

To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/dhcpdump/

Alternatively, you can download the package with 'dget' using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/d/dhcpdump/dhcpdump_1.8-7~bpo11+1.dsc

Changes since the last upload:

 dhcpdump (1.8-7~bpo11+1) bullseye-backports; urgency=medium
 .
   * Rebuild for bullseye-backports.

Regards,
-- 
  Boian Bonev


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

Bug#1034237: gammu-smsd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Boian Bonev]

On Tue, 2023-04-11 at 15:03 +0200, Andreas Henriksson wrote:
> On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
...

> > It seems that your package gammu-smsd is shipping files (.service, .socket
> > or
> > .timer) in /usr/lib/systemd/system.
> [...]
> 
> The culprit seems to be here:
> https://sources.debian.org/src/gammu/1.42.0-7/debian/rules/#L32
> 
> ```
> -DSYSTEMD_SERVICES_INSTALL_DIR=/usr/lib/systemd/system \
> ```
> 
> By removing this line you'll let cmake auto-detect the correct path via
> ./cmake/FindSystemD.cmake which uses pkg-config.
> 
> Make sure you also build-dep on the package containing systemd.pc
> (you already seem to have pkg-config itself in build-deps).
> 
> Also note that you need to adjust:
> https://sources.debian.org/src/gammu/1.42.0-7/debian/gammu-smsd.install/#L5

Thanks for this.

My concern is that involves moving files between lib and usr/lib - as far as I
am aware this is a big problem with the current state of usrmerge, isn't it?

There is no systemd.pc, libsystemd.pc contains prefix=/usr - how that is going
to change anything?

I did try to apply the proposed change and cmake breaks in a bad way without
the -DSYSTEMD_SERVICES_INSTALL_DIR; I have kept that and changed the path,
please review my changes on salsa.

--
With best regards,
b.




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

Bug#1034252: colord: please consider splitting out colord-sane

[Stephen Kitt]

Package: colord
Version: 1.4.5-3
Severity: wishlist
Tags: patch

Dear Maintainer,

colord-sane scans for SANE devices every time colord scans for
devices, e.g. on my system whenever a USB device is connected (or
wakes up). This wakes my multi-function printer up, which is noisy and
wasteful (it's a laser printer, so it heats up every time this
happens). See https://github.com/hughsie/colord/issues/118 and the
links there for more on this.

Would it be possible to split colord-sane out to a separate package?
The attached patch implements this. This has the side-benefit that the
main colord package no longer depends on libsane1.

Regards,

Stephen


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

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

Versions of packages colord depends on:
ii  acl  2.2.53-10
ii  adduser  3.118
ii  colord-data  1.4.5-3
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-2
ii  libc62.31-13+deb11u5
ii  libcolord2   1.4.5-3
ii  libcolorhug2 1.4.5-3
ii  libdbus-1-3  1.12.24-0+deb11u1
ii  libglib2.0-0 2.66.8-1
ii  libgudev-1.0-0   234-1
ii  libgusb2 0.3.5-1
ii  liblcms2-2   2.12~rc1-2
ii  libpolkit-gobject-1-00.105-31+deb11u1
ii  libsane1 1.0.31-4.1
ii  libsqlite3-0 3.34.1-3
ii  libsystemd0  247.3-7+deb11u1
ii  policykit-1  0.105-31+deb11u1

colord recommends no packages.

colord suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: missing file /usr/libexec/colord-sane (from colord package)
diff --git a/debian/changelog b/debian/changelog
index 462aaf30..2b9039f5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+colord (1.4.6-2.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Split SANE support out to a separate package, to allow installation of
+colord without triggering SANE devices (this wakes up network
+multi-function printers supported by SANE whenever colord scans for
+supported devices).
+
+ -- Stephen Kitt   Tue, 11 Apr 2023 17:23:30 +0200
+
 colord (1.4.6-2.2) unstable; urgency=medium
 
   * Non-maintainer upload
diff --git a/debian/colord-plugin-sane.install 
b/debian/colord-plugin-sane.install
new file mode 100644
index ..5ef0687f
--- /dev/null
+++ b/debian/colord-plugin-sane.install
@@ -0,0 +1,2 @@
+usr/lib/*/colord-plugins/libcolord_sensor_sane.so
+usr/libexec/colord-sane
diff --git a/debian/colord.install b/debian/colord.install
index 42cc99bc..6ad61798 100644
--- a/debian/colord.install
+++ b/debian/colord.install
@@ -1,7 +1,8 @@
 lib/systemd/system/*.service
 lib/udev/rules.d/
 usr/bin/
-usr/lib/*/colord-plugins
+usr/lib/*/colord-plugins/libcolord_sensor_camera.so
+usr/lib/*/colord-plugins/libcolord_sensor_scanner.so
 usr/lib/*/colord-sensors/libcolord_sensor_colorhug.so
 usr/lib/*/colord-sensors/libcolord_sensor_dtp94.so
 usr/lib/*/colord-sensors/libcolord_sensor_dummy.so
@@ -9,7 +10,6 @@ usr/lib/*/colord-sensors/libcolord_sensor_huey.so
 usr/lib/systemd/user/
 usr/lib/tmpfiles.d/
 usr/libexec/colord
-usr/libexec/colord-sane
 usr/libexec/colord-session
 usr/share/bash-completion
 usr/share/dbus-1
diff --git a/debian/control b/debian/control
index 9f190d09..6df76ed1 100644
--- a/debian/control
+++ b/debian/control
@@ -116,6 +116,27 @@ Description: system service to manage device colour 
profiles -- argyll sensor pl
  This package contains a sensor plugin that uses the Argyll tools, allowing
  colord to support colourimeters that are supported by Argyll.
 
+Package: colord-plugin-sane
+Architecture: linux-any
+Depends:
+ ${misc:Depends},
+ ${shlibs:Depends},
+Replaces:
+ colord (<< 1.4.6-2.2~),
+Breaks:
+ colord (<< 1.4.6-2.2~),
+Enhances:
+ colord,
+Description: system service to manage device colour profiles -- SANE plugin
+ colord is a system service that makes it easy to manage, install and generate
+ colour profiles to accurately colour manage input and output devices.
+ .
+ It provides a D-Bus API for system frameworks to query, a persistent data
+ 

Bug#1032975: Aw: Steffen, please raise your opinion about igdiscover

[Steffen Möller]

Hi Andreas,

I am afraid I cannot put the extra effort into those packages and, admittedly, 
the NCBI software suite is just a bit intimidating, too. Please remove those 
packages from testing and if nobody shows any interest in the required updates 
then eventually those packages should also be removed from unstable.

Thank you tons,
Steffen

Bug#1034236: mpd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Max Kellermann]

On 2023/04/11 17:40, Andreas Henriksson  wrote:
> I think 2 is better myself and I'm attaching a proof of concept
> debdiff to implement it. (You might want to make a cleaner version.)

Agree.  I think your patch looks quite clean, and if it were submitted
to me, I'd merge it (the same would probably be necessary for the user
units).

Maybe I'd go as far and remove the Meson options; they should never
have been there in the first place.  When those options were authored
and submitted to me long ago (in 2011 by commit 83f6498aac), I didn't
know systemd exposes those directories in its pkg-config file.

Bug#1034251: ansible: package should recommend python3-passlib

[Jens Meißner]

Package: ansible
Version: 7.3.0+dfsg-1
Severity: normal
X-Debbugs-Cc: heptal...@gmx.de

Hello,

some Ansible functions like the Jinja2 filter password_hash() are using
the Python module python3-cryptography which is deprecated. Ansible is
printing the following deprecation warning:

[DEPRECATION WARNING]: Encryption using the Python crypt module is
deprecated. The Python crypt module is deprecated and will be removed
from Python 3.13. Install the passlib library for continued encryption
functionality. This feature will be removed in version 2.17. Deprecation
warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.

This warning can be fixed by installing the package python3-passlib. So
ansible should recommend python3-passlib.

Regards,
Jens

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

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

Versions of packages ansible depends on:
ii  ansible-core   2.14.3-1
ii  openssh-client 1:9.2p1-2
ii  python33.11.2-1+b1
ii  python3-distutils  3.11.2-2
ii  python3-dnspython  2.3.0-1
ii  python3-httplib2   0.20.4-3
ii  python3-jinja2 3.1.2-1
ii  python3-netaddr0.8.0-2
ii  python3-yaml   6.0-3+b2

Versions of packages ansible recommends:
ii  python3-argcomplete   2.0.0-1
ii  python3-cryptography  38.0.4-3
ii  python3-jmespath  1.0.1-1
ii  python3-kerberos  1.1.14-3.1+b7
ii  python3-libcloud  3.4.1-5
ii  python3-selinux   3.4-1+b5
ii  python3-winrm 0.3.0-4
ii  python3-xmltodict 0.13.0-1

Versions of packages ansible suggests:
pn  cowsay   
pn  sshpass  

-- no debconf information

Bug#1034226: cloudflare-ddns: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andrea Pappacoda]

Hi all,

Il giorno mar 11 apr 2023 alle 09:37:27 +02:00:00, bi...@debian.org ha 
scritto:
It seems that your package cloudflare-ddns is shipping files 
(.service, .socket or

.timer) in /usr/lib/systemd/system.

This is not supported by the version of dh_installsystemd/debhelper 
currently
in unstable and bookworm (See: #1031695). That means that currently 
your

service might not be enabled at boot and/or started as expected.


Thanks for the info! Having to install stuff outside of /usr kinda 
sucks, but I guess we don't have alternatives :/


Il giorno mar 11 apr 2023 alle 16:31:32 +02:00:00, Andreas Henriksson 
 ha scritto:

The culprit seems to be hard-coded paths in the upstream build system
at:
https://sources.debian.org/src/cloudflare-ddns/2.0.0-3/exe/meson.build/#L70

Since I wasn't sure about how configure_file directive in meson works
and the documentation at
https://mesonbuild.com/Reference-manual_functions.html#configure_file
says install_dir takes a subdirectory I had to try it out.

The attached debdiff should solve the problem.


Thanks you very much for the patch! Using systemd.pc certainly is the 
most appropriate thing to do, but the way you've approached this makes 
systemd a required dependency on Linux, which I'd prefer to avoid. I'll 
simply make th dependency `required: false`, so that files get 
installed only if systemd.pc is found on the system; this has the 
advantage of not making systemd required, and could also potentially 
work on non-Linux systems with systemd-compatible software (yeah, 
InitWare[1] is, or was, a thing).


I'll fix this upstream and in the Debian package as soon as possible, 
thanks again :)


[1]: https://github.com/InitWare/InitWare

--
OpenPGP key: 66DE F152 8299 0C21 99EF  A801 A8A1 28A8 AB1C EE49

Bug#1034236: mpd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

Hello Max Kellermann,

On Tue, Apr 11, 2023 at 04:13:28PM +0200, Max Kellermann wrote:
> On 2023/04/11 15:11, Andreas Henriksson  wrote:
> > The culprit seems to be that mpd falls back on hard-coded path (instead
> > of failing) when systemd.pc is not found!
> 
> What does this have to do with systemd.pc?  It isn't used anywhere.

Right, I overlooked this which is indeed a problem.

Currently there's only a meson_option.txt you can set which means:
1. implement `pkg-config --variable=systemdsystemunitdir systemd`
   in debian/rules and pass it in via the existing option.
2. implement checking systemdsystemunitdir from systemd.pc in meson
   and have the build system do the right thing without any options.

I think 2 is better myself and I'm attaching a proof of concept
debdiff to implement it. (You might want to make a cleaner version.)

Regards,
Andreas Henriksson
diff -Nru mpd-0.23.12/debian/changelog mpd-0.23.12/debian/changelog
--- mpd-0.23.12/debian/changelog2023-01-21 21:32:37.0 +0100
+++ mpd-0.23.12/debian/changelog2023-04-11 17:30:42.0 +0200
@@ -1,3 +1,11 @@
+mpd (0.23.12-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add debian/patches/systemdsystemunitdir.patch
+  * Add systemd build-dep for systemd.pc
+
+ -- Andreas Henriksson   Tue, 11 Apr 2023 17:30:42 +0200
+
 mpd (0.23.12-1) unstable; urgency=medium
 
   * New upstream version 0.23.12
diff -Nru mpd-0.23.12/debian/control mpd-0.23.12/debian/control
--- mpd-0.23.12/debian/control  2023-01-21 21:32:37.0 +0100
+++ mpd-0.23.12/debian/control  2023-04-11 17:30:42.0 +0200
@@ -55,6 +55,7 @@
libsoxr-dev,
libsqlite3-dev,
libsystemd-dev [linux-any],
+  systemd [linux-any],
libupnp-dev (>= 1.8~),
liburing-dev [linux-any],
libvorbis-dev [!armel],
diff -Nru mpd-0.23.12/debian/patches/series mpd-0.23.12/debian/patches/series
--- mpd-0.23.12/debian/patches/series   2021-11-11 15:58:40.0 +0100
+++ mpd-0.23.12/debian/patches/series   2023-04-11 17:25:58.0 +0200
@@ -1,3 +1,4 @@
 # Debian-specific
 systemd_honor_MPDCONF.patch
 mpd.service.documentation.user.patch
+systemdsystemunitdir.patch
diff -Nru mpd-0.23.12/debian/patches/systemdsystemunitdir.patch 
mpd-0.23.12/debian/patches/systemdsystemunitdir.patch
--- mpd-0.23.12/debian/patches/systemdsystemunitdir.patch   1970-01-01 
01:00:00.0 +0100
+++ mpd-0.23.12/debian/patches/systemdsystemunitdir.patch   2023-04-11 
17:30:33.0 +0200
@@ -0,0 +1,16 @@
+Index: mpd-0.23.12/systemd/system/meson.build
+===
+--- mpd-0.23.12.orig/systemd/system/meson.build
 mpd-0.23.12/systemd/system/meson.build
+@@ -1,5 +1,11 @@
+ systemd_system_unit_dir = get_option('systemd_system_unit_dir')
+ if systemd_system_unit_dir == ''
++  systemd = dependency('systemd', required: false)
++  if systemd.found()
++  systemd_system_unit_dir = 
systemd.get_pkgconfig_variable('systemdsystemunitdir')
++  endif
++endif
++if systemd_system_unit_dir == ''
+   systemd_system_unit_dir = join_paths(get_option('prefix'), 'lib', 
'systemd', 'system')
+ endif
+ 

Bug#1032975: Steffen, please raise your opinion about igdiscover

[Andreas Tille]

Hi Steffen,

we really need your insight into the package created by you.  Please
raise your opinion whether this package is sensible at all as it is now.
If not I'd ask for removal from testing immediately (since this mail
refreshed the autoremoval counter.)

Thanks a lot
Andreas.

-- 
http://fam-tille.de

Bug#1034250: ITS: libsml - offering to take over maintainership

[Joachim Zobel]

Source: libsml
Severity: important
X-Debbugs-Cc: am...@ubuntu.com, andreas.m...@warperbbs.de

Dear Maintainer.

There has been no reply to my bug #1028076 and the following conditions are
met.

1. There is no visible activity regarding the package for six months.
2. The last upload was an NMU and there was no maintainer upload within one
   year (Met according to the version number 0.1.1+git20180125-1.1)
3. Bugs exist for more than one major missing upstream version and the first
   bug is older than one year (#946525 was reported on Tue, 10 Dec 2019).

Therefore the package is in my opinion eligible for package salvaging and I am
offering to take over maintenance.


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

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

Bug#1034249: pvpgn: Do not exit the postinst script early if not in "configure" state

[Laurent Bigonville]

Package: pvpgn
Version: 1.8.5-3
Severity: important

Hello,

Currently the postinst maintainer script exits early if it is not run in
"configure" mode:

#
# Skip, if we are not in "configure" state
#
if [ "$1" != "configure" ]; then
echo "I: Skipping configuration"
exit 0
fi

DIRS="bak/charinfo bak/charsave bnmail chanlogs charinfo
  charsave ladders reports status teams users"

for DIR in $DIRS; do
mkdir -p /var/lib/pvpgn/$DIR
done

INMHO, this is not good as debhelper snippets might not be properly
executed (ie. the ones from dh_installsystemd or dh_installinit)

The script should be changed to something like:


DIRS="bak/charinfo bak/charsave bnmail chanlogs charinfo
  charsave ladders reports status teams users"

if [ "$1" = "configure" ]; then
for DIR in $DIRS; do
mkdir -p /var/lib/pvpgn/$DIR
done
fi

Kind regards,
Laurent Bigonville

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

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

Versions of packages pvpgn depends on:
ii  libc6  2.36-9
pn  libcdb1
pn  libmariadb3
pn  libpq5 
ii  libsqlite3-0   3.40.1-2
ii  sysvinit-utils [lsb-base]  3.06-4
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages pvpgn recommends:
pn  tinycdb  
ii  wget 1.21.3-1+b2

Versions of packages pvpgn suggests:
pn  default-mysql-server | virtual-mysql-server  
pn  fortune  

Bug#1034184: [Pkg-owncloud-maintainers] Bug#1034184: nextcloud-desktop: CVE-2023-28999

[Hefee]

control: tags -1 + moreinfo 

Hey,

thanks for your intial work in this bug. I added some more digging work into 
it that ends up with a lot of question marks...
 
Do you know for sure, that the merge request #5560 fixes the CVE-2023-28999? At 
least I looked at the merge request and it is a very big one that touches 34 
files (660 lines added/483 lines removed) and the commits have white space 
changes and add a new metadata version (1.2). Do we need this new metadata 
version in order to fix the CVE? In total this does not looks like just a 
bugfix 
but as a feature branch. It does not looks like, we can simply ship this big 
patch to bookworm/bullseye :( 

The commit that adds a new metadata version:
https://github.com/nextcloud/desktop/pull/5560/commits/
1b0a93eabc8f1322ef299cba3c4db81944c7d2c6

At least there are other merge requests that touches E2EE in Nextcloud 
Desktop:
https://github.com/nextcloud/desktop/pull/5534

and than there are these new issues with 3.8.0 and EE2E, that scares me to 
back port additionally:
https://github.com/nextcloud/desktop/issues/5564

Additionally it does not apply clean on the v3.7.3 - so more work needs to put 
into getting this into Debian. 

regards,

hefee


> The following vulnerability was published for nextcloud-desktop.
> 
> CVE-2023-28999[0]:
> | Nextcloud is an open-source productivity platform. In Nextcloud
> | Desktop client 3.0.0 until 3.8.0, Nextcloud Android app 3.13.0 until
> | 3.25.0, and Nextcloud iOS app 3.0.5 until 4.8.0, a malicious server
> | administrator can gain full access to an end-to-end encrypted folder.
> | They can decrypt files, recover the folder structure and add new
> | files.#8203; This issue is fixed in Nextcloud Desktop 3.8.0,
> | Nextcloud Android 3.25.0, and Nextcloud iOS 4.8.0. No known
> | workarounds are available.
> 
> https://github.com/nextcloud/security-advisories/security/advisories/GHSA-88
> 75-wxww-3rr8 https://github.com/nextcloud/desktop/pull/5560
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2023-28999
> https://www.cve.org/CVERecord?id=CVE-2023-28999
> 
> Please adjust the affected versions in the BTS as needed.
> 
> ___
> Pkg-owncloud-maintainers mailing list
> pkg-owncloud-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-owncloud-mainta
> iners



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

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

[Jeremy Bícha]

Subject: release-notes: screen reader
Package: release-notes
Tags: a11y bookworm sid
X-Debbugs-CC: debian-gtk-gn...@lists.debian.org

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

If you depend on a screen reader, we suggest that you install a
desktop like MATE instead of GNOME.

Other Info
-
Debian Bookworm has GTK 4.8 and libadwaita 1.2. This issue is not
significantly improved yet even with GTK 4.10 and libadwaita 1.3. My
guess is that it won't be possible to fix this issue with Debian
Bookworm Stable Updates once it is fixed upstream because the amount
of changes will be too much. We hope that GTK4 apps will be accessible
for Debian Trixie.

There is a test case at
https://launchpad.net/bugs/2015760

Thank you,
Jeremy Bícha

Bug#1034223: powerman: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

Hello Laurent Bigonville,

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: powerman
> Version: 2.3.27-2  
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package powerman is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
> 
> This is not supported by the version of dh_installsystemd/debhelper currently
> in unstable and bookworm (See: #1031695). That means that currently your
> service might not be enabled at boot and/or started as expected.
[...]

Note that debian/rules has:

```
override_dh_installinit:
dh_installinit --no-start --no-enable

override_dh_installsystemd:
dh_installsystemd --no-start --no-enable
```

So do you agree that the severity of this bug report should be downgraded
(maybe even closed)?

Regards,
Andreas Henriksson

Bug#1034226: cloudflare-ddns: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: cloudflare-ddns
> Version: 2.0.0-3   
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package cloudflare-ddns is shipping files (.service, 
> .socket or
> .timer) in /usr/lib/systemd/system.
[...]

The culprit seems to be hard-coded paths in the upstream build system
at:
https://sources.debian.org/src/cloudflare-ddns/2.0.0-3/exe/meson.build/#L70

Since I wasn't sure about how configure_file directive in meson works
and the documentation at
https://mesonbuild.com/Reference-manual_functions.html#configure_file
says install_dir takes a subdirectory I had to try it out.

The attached debdiff should solve the problem.

While at it I also adressed the hardcoded sysuser directory at:
https://sources.debian.org/src/cloudflare-ddns/2.0.0-3/exe/meson.build/#L90

See attached file which you might want to improve (for example you could
make systemd a build-option even on linux if you care).

Regards,
Andreas Henriksson

diff -Nru cloudflare-ddns-2.0.0/debian/changelog 
cloudflare-ddns-2.0.0/debian/changelog
--- cloudflare-ddns-2.0.0/debian/changelog  2023-01-16 22:16:37.0 
+0100
+++ cloudflare-ddns-2.0.0/debian/changelog  2023-04-11 16:17:38.0 
+0200
@@ -1,3 +1,12 @@
+cloudflare-ddns (2.0.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * add debian/patches/systemdsystemunitdir.patch
+  * debian/cloudflare-ddns.install: install lib/systemd/system
+  * Add systemd build-dep, for systemd.pc
+
+ -- Andreas Henriksson   Tue, 11 Apr 2023 16:17:38 +0200
+
 cloudflare-ddns (2.0.0-3) unstable; urgency=medium
 
   * d/.install: fix build on non-Linux with dh-exec
diff -Nru cloudflare-ddns-2.0.0/debian/cloudflare-ddns.install 
cloudflare-ddns-2.0.0/debian/cloudflare-ddns.install
--- cloudflare-ddns-2.0.0/debian/cloudflare-ddns.install2023-01-16 
22:10:06.0 +0100
+++ cloudflare-ddns-2.0.0/debian/cloudflare-ddns.install2023-04-11 
16:17:38.0 +0200
@@ -1,5 +1,5 @@
 #!/usr/bin/dh-exec
-[linux-any] usr/lib/systemd/
+[linux-any] lib/systemd/system
 [linux-any] usr/lib/sysusers.d/
 etc/
 usr/bin/
diff -Nru cloudflare-ddns-2.0.0/debian/control 
cloudflare-ddns-2.0.0/debian/control
--- cloudflare-ddns-2.0.0/debian/control2023-01-16 22:10:06.0 
+0100
+++ cloudflare-ddns-2.0.0/debian/control2023-04-11 16:17:38.0 
+0200
@@ -11,6 +11,7 @@
 libsimdjson-dev (>= 0.9.0),
 meson (>= 0.53.0),
 pkg-config,
+   systemd,
 ronn
 Standards-Version: 4.6.2
 Homepage: https://github.com/Tachi107/cloudflare-ddns
diff -Nru cloudflare-ddns-2.0.0/debian/patches/series 
cloudflare-ddns-2.0.0/debian/patches/series
--- cloudflare-ddns-2.0.0/debian/patches/series 1970-01-01 01:00:00.0 
+0100
+++ cloudflare-ddns-2.0.0/debian/patches/series 2023-04-11 16:13:19.0 
+0200
@@ -0,0 +1 @@
+systemdsystemunitdir.patch
diff -Nru cloudflare-ddns-2.0.0/debian/patches/systemdsystemunitdir.patch 
cloudflare-ddns-2.0.0/debian/patches/systemdsystemunitdir.patch
--- cloudflare-ddns-2.0.0/debian/patches/systemdsystemunitdir.patch 
1970-01-01 01:00:00.0 +0100
+++ cloudflare-ddns-2.0.0/debian/patches/systemdsystemunitdir.patch 
2023-04-11 16:17:38.0 +0200
@@ -0,0 +1,37 @@
+Index: cloudflare-ddns-2.0.0/exe/meson.build
+===
+--- cloudflare-ddns-2.0.0.orig/exe/meson.build
 cloudflare-ddns-2.0.0/exe/meson.build
+@@ -66,8 +66,10 @@ if ronn.found()
+   )
+ endif
+ 
+-if host_machine.system() == 'linux'
+-  systemddir = 'lib'/'systemd'/'system'
++systemd = dependency('systemd', required: host_machine.system() == 'linux')
++if systemd.found()
++  systemdsystemunitdir = 
systemd.get_pkgconfig_variable('systemdsystemunitdir')
++systemdsysusersdir = systemd.get_pkgconfig_variable('sysusersdir')
+ 
+   configure_file(
+   input: 'systemd'/'cloudflare-ddns.service.in',
+@@ -77,16 +79,16 @@ if host_machine.system() == 'linux'
+   'libdir': get_option('prefix')/get_option('libdir')
+   },
+   install: true,
+-  install_dir: systemddir
++  install_dir: systemdsystemunitdir
+   )
+ 
+   install_data(
+   'systemd'/'cloudflare-ddns.timer',
+-  install_dir: systemddir
++  install_dir: systemdsystemunitdir
+   )
+ 
+   install_data(
+   'sysusers.d'/'cloudflare-ddns.conf',
+-  install_dir: 'lib'/'sysusers.d'
++  install_dir: systemdsysusersdir
+   )
+ endif

Bug#1034236: mpd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Max Kellermann]

On 2023/04/11 15:11, Andreas Henriksson  wrote:
> The culprit seems to be that mpd falls back on hard-coded path (instead
> of failing) when systemd.pc is not found!

What does this have to do with systemd.pc?  It isn't used anywhere.

Bug#1034228: zcfan: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: zcfan
> Version: 1.2.1-1
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package zcfan is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]

The culprit seems to be the wrong path hardcoded at:
https://sources.debian.org/src/zcfan/1.2.1-1/Makefile/#L44

Preferably you would find out this path by querying systemd.pc for it,
ie. pkg-config --variable=systemdsystemunitdir systemd

(Note: You'll also need to build-dep on pkg-config and systemd, for
systemd.pc)

Regards,
Andreas Henriksson

Bug#1034052: winetricks: winetrick searches for 32 bit wine as wine32, not wine

[Jens Reyer]

control: tags -1 moreinfo

Hi,


On 07.04.23 15:49, Thomas Dorner wrote:

While setting up a new Wine environment winetricks aborted with the
following error:


I can't reproduce this issue.  What steps exactly did you issue that failed?

With the same packages installed I successfully did the following tests:

rm -rf .wine
wineboot
winetricks vcrun2019

rm -rf .wine
winetricks vcrun2019

rm -rf .wine
regedit





it looks like wine32 is missing, you should install it.
multiarch needs to be enabled first.  as root, please
execute "dpkg --add-architecture i386 && apt-get update &&
apt-get install wine32:i386"


This is an error message from Wine. Winetricks doesn't look for "wine32".

Please remove the hardlink again and report the output of "wine --version".

You may also reinstall wine (apt purge wine wine32 wine64 && apt install 
wine wine32 wine64) and check again.



Thanks and greets
jre

Bug#1034221: caddy: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: caddy
> Version: 2.6.2-4
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package caddy is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]

The culprit seems to be wrong path at:
https://sources.debian.org/src/caddy/2.6.2-4/debian/caddy.install/#L2-L3

Please note that if you change it to /lib/systemd/system now, you'll
likely need to reverse that change again in the future.

Preferably the correct path is derived from the value given by
pkg-config --variable=systemdsystemunitdir systemd

You could use this via making your debian/caddy.install executable
and integrating dh-exec. You'll have to decide if you think it's
worth it or not.

Regards,
Andreas Henriksson

Bug#1034229: wsdd2: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: wsdd2
> Version: 1.8.7+dfsg-1  
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package wsdd2 is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]

The culprit seems to be the hard-coded path at:
https://sources.debian.org/src/wsdd2/1.8.7%2Bdfsg-1/Makefile/#L31

As this path will change again in the future, please consider
finding out the path from the proper source via:
pkg-config --variable=systemdsystemunitdir systemd

(Note: you'll need to build-dep on pkg-config and systemd, for
systemd.pc)

Regards,
Andreas Henriksson

Bug#1034230: fail2ban: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: fail2ban
> Version: 1.0.2-1   
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package fail2ban is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]

Wrong path is used at:
https://sources.debian.org/src/fail2ban/1.0.2-1/debian/rules/#L50

Note that the path will likely change again in the future, so rather
than hard-coding a path please consider finding the path via:
pkg-config --variable=systemdsystemunitdir systemd

(Note: you'll need to build-dep on pkg-config and systemd, for
systemd.pc)

Regards,
Andreas Henriksson

Bug#1033936: fwupd: FuEngine failed to get releases for UEFI dbx ... requires >= 1.8.14

[Sergio Gelato]

This probably even affects sid, as it only has version 1.8.12.

I would also like for fwupd updates to be distributed via -updates
just like tzdata, clamav, etc.

Bug#1034232: nvme-cli: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: nvme-cli
> Version: 2.3-2 
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package nvme-cli is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]

The culprit seems to be here:
https://sources.debian.org/src/nvme-cli/2.4%2Breally2.3-2/meson.build/#L27

(making the systemddir build option unusable.)

The proper solution would involve pkg-config and systemd.pc
which should be queried for the systemdsystemunitdir variable.
(Note: do not forget to build-dep on pkg-config and systemd.)

This should give you a bunch of packages to choose from as examples of
how to implement that using meson:
https://codesearch.debian.net/search?q=get_option.*systemdsystemunitdir=0=1

Regards,
Andreas Henriksson

Bug#1034233: tlp: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: tlp
> Version: 1.5.0-1   
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package tlp is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]

The problem seems to originate from:
https://sources.debian.org/src/tlp/1.5.0-1/debian/rules/#L9

The upstream default value is actually correct for Debian (at the
moment):
https://sources.debian.org/src/tlp/1.5.0-1/Makefile/#L17

However, this will change in the future... so I think a better solution
would be to actually retrieve the value from systemd.pc.

You should be able to do this by:
* build-dep on pkg-config and systemd (for systemd.pc)
* Modify debian/rules `export TLP_SYSD=/usr/lib/systemd/system` to:
export TLP_SYSD=$(shell pkg-config --variable=systemdsystemunitdir systemd)
* Update https://sources.debian.org/src/tlp/1.5.0-1/debian/tlp.install/#L5

Regards,
Andreas Henriksson

Bug#1034166: unblock: gnome-shell/43.4-1

[Simon McVittie]

Control: tags -1 - moreinfo
Control: retitle -1 unblock: gnome-shell/43.4-1

On Mon, 10 Apr 2023 at 18:41:07 +0200, Sebastian Ramacher wrote:
> On 2023-04-10 15:27:52 +0100, Simon McVittie wrote:
> > I'd like to upload a new upstream bug fix release of gnome-shell.
> 
> Please go ahead and remove the moreinfo tag once the version is
> available in unstable.

Uploaded and built on all release architectures.

smcv

Bug#1034167: unblock: mutter/43.4-1

[Simon McVittie]

Control: retitle -1 unblock: mutter/43.4-1
Control: tags -1 - moreinfo

On Mon, 10 Apr 2023 at 18:45:17 +0200, Sebastian Ramacher wrote:
> On 2023-04-10 15:29:08 +0100, Simon McVittie wrote:
> > I'd like to upload a new upstream bug fix release of mutter.
> 
> Please go ahead and remove the moreinfo tag once the version is
> available in unstable.

Uploaded and built on all release architectures.

smcv

Bug#1034149: unblock: glib2.0/2.74.6-2

[Simon McVittie]

Control: tags -1 - moreinfo
Control: retitle -1 unblock: glib2.0/2.74.6-2

On Mon, 10 Apr 2023 at 18:23:06 +0200, Sebastian Ramacher wrote:
> On 2023-04-10 13:17:32 +0100, Simon McVittie wrote:
> > I've been using this proposed glib2.0 update for a few days and I'd like
> > to upload it to unstable. There's nothing RC here, but it seems safer and
> > easier to do several small bugfix updates rather than one large one.
> 
> Please go ahead and remove the moreinfo tag once the package is
> available in unstable.

Uploaded and built on all release architectures. There seem to be reports
of autopkgtest regressions, I'm not sure which of those are flaky and which
(if any) are genuine issues.

smcv

Bug#1034234: libpam-modules-bin: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: libpam-modules-bin
> Version: 1.5.2-6   
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package libpam-modules-bin is shipping files (.service, 
> .socket or
> .timer) in /usr/lib/systemd/system.
[...]

wrong variable name (systemdsystemunitdir):
https://sources.debian.org/src/pam/1.5.2-6/configure.ac/?hl=646#L646

overridden by wrong path:
https://sources.debian.org/src/pam/1.5.2-6/debian/rules/#L33

Regards,
Andreas Henriksson

Bug#1034247: mtree-netbsd: Wrong BSD-4-clause

[Bastian Germann]

Source: mtree-netbsd
Version: 20180822-7
Severity: important

The 3rd clause of NetBSD's BSD-4-clause is misrepresented in debian/copright. That file has UCB's advertisement clause 
instead.


Please remove 3rd and 4th clauses (reference BSD-2-Clause) according to http://www.netbsd.org/about/redistribution.html 
from pack_dev.[ch]: "Third parties are encouraged to change the license on any files which have a 4-clause license 
contributed to the NetBSD Foundation to a 2-clause license. We would also encourage you to inform us about these files, 
so that we can continue to track the many places in which NetBSD is used."


For the files getid.c, mtree.8, and spec.c that have the BSD-3-clause license with a different copyright holder, please 
reference that license instead.

Bug#1034236: mpd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: mpd
> Version: 0.23.12-1 
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package mpd is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]

The culprit seems to be that mpd falls back on hard-coded path (instead
of failing) when systemd.pc is not found!

https://sources.debian.org/src/mpd/0.23.12-1/systemd/system/meson.build/#L1-L4

Fixing the problem should be as easy as adding a build-dep on the
package that contains systemd.pc (systemd).

Regards,
Andreas Henriksson

Bug#1034237: gammu-smsd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: gammu-smsd
> Version: 1.42.0-7  
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package gammu-smsd is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]

The culprit seems to be here:
https://sources.debian.org/src/gammu/1.42.0-7/debian/rules/#L32

```
-DSYSTEMD_SERVICES_INSTALL_DIR=/usr/lib/systemd/system \
```

By removing this line you'll let cmake auto-detect the correct path via
./cmake/FindSystemD.cmake which uses pkg-config.

Make sure you also build-dep on the package containing systemd.pc
(you already seem to have pkg-config itself in build-deps).


Also note that you need to adjust:
https://sources.debian.org/src/gammu/1.42.0-7/debian/gammu-smsd.install/#L5

Regards,
Andreas Henriksson

Bug#1025069: pavucontrol

[Alban Browaeys]

Also could you also give the wireplumber log 
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3086#note_1829660

Cheers,
Alban

Le mardi 11 avril 2023 à 14:30 +0200, Alban Browaeys a écrit :
> Le dimanche 09 avril 2023 à 15:03 -0500, Lucas a écrit :
> > I should have let you know when I created it, but I still have no
> > feedback from a bug report I wrote to the pipewire developers:
> > https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3131.
> > 
> 
> 
> "Multichannel Output" Profile disappeared after I ran JACK (ardour),
> and I only see again now on a fresh startup.
> 
> Do you mean it disappeared from pavucontrol when you run JACK from
> ardour ?
> 
> What I meant is that you cannot run pipewire and jackd at the same
> time ? I cannot work as one will prevent the other from accessing the
> ALSA sound device.
> If you want to run JACK application whne running pipewire you can
> only do so by pipewire-jackd and disabling jackd. 
> This is not a pipewire bug. jackd also cannot work if the sound
> device is already taken by an alsa program or any other daemon
> plugging to the alsa interface (pipewire, pulseaudio), it could work
> because for one pulseaudio aut suspend itself from time to time so
> the alsa sound device is free when so. But then when pulseaudio will
> resume and your jackd daemon is holding on the alsa sound device
> pulseaudio will not work. This is not supported (for pulseaudio you
> could use the pasuspend tool, still it is  hack).
> 
> 
> Also:
> Gnome Settings Output Device contains nothing to select, while Input
> allows "Analog Input - STUDIO-CAPTURE" and "STUDIO-CAPTURE Pro". The
> only way to have output audio working is to use pavucontrol and
> select either of the STUDIO-CAPTURE Profile Configurations
> "Multichannel Output", or "Pro Audio".  
> and:
> That "Multichannel Output" Profile disappeared after I ran JACK
> (ardour), and I only see again now on a fresh startup.
> seems to be two different issue. You should report both in two
> diffrent bug report else it the bug report will get confusing soon.
> My reply was about the second issue (which to me look like a normal
> behavior).
> 
> 
> For the first one, I am a bit confused. You mean that even in
> pavucontrol if you do not switch to the STUDIO-CAPTURE Profile
> Configurations "Multichannel Output", or "Pro Audio" you cannot set a
> sound output device?
> 
> If you bug report upstream you could try to run pipewire built from
> source (you just have to stop pipewire related systemd user services,
> ie systemctl --user stop pipewire.service, etc).
> Also there is a newer pipewire version 0.3.76 in Debian rc-buggy
> (experimental).
> 
> 
> > I guessed it was a "port detection" issue after reading this
> > response on the original poster's bug report:
> > https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3086#note_1831991
> > 
> 
> Could you provide the same debug logs as this bug reporter did?
> 
> loginctl user-status | grep State
> lsof /dev/snd/*
> fuser -v /dev/snd/*
> aplay -l
> journalctl --user -b --unit pipewire.service
> 
> and maybe also 
> journalctl --user -b --unit pipewire-pulse.service
> pipewire --version
> 
> 
> and why not the output when running gnome-control-center from a
> terminal:
> gnome-control-center --verbose sound
> 
> Still could you try with pipewire-jack instead of jackd (even if you
> prefer to run jackd only while running a jack application.
> 
> Cheers
> Alban
> 
> > 
> > On Sun, Apr 9, 2023 at 1:33 PM Lucas  wrote:
> > > On Fri, Apr 7, 2023 at 7:57 PM Alban Browaeys
> > >  wrote:
> > > >
> > > > Do you have jackd installed and runnning at the same time as
> > > pipewire-
> > > > pulse?
> > > > Maybe you want to try piepwire-jack instead?
> > > >
> > > > Cheers,
> > > > Alban
> > > >
> > > 
> > > I appreciate the suggestion, but since I also use multiple
> > > devices
> > > with JACK, it's only running when I want to record and use a
> > > specific
> > > profile/device.  Ardour will start it using the last used
> > > (default)
> > > profile, but only when I've not already started JACK from
> > > qjackctl to
> > > use another profile.  I think having it always running may
> > > complicate
> > > this setup I've grown accustomed to.  Are you aware of any issues
> > > trying to stop JACK (to use other rates and devices) when using
> > > pipewire-jack?
> > > 
> > > Thanks,
> > >   Lucas
> > 
> > 
> > -- 
> > Protect your digital freedom and privacy, eliminate DRM, learn more
> > at http://www.defectivebydesign.org/what_is_drm
> > On a related note, also see
> > https://www.fsf.org/campaigns/surveillance
> 

Bug#1034240: pass-extension-tomb: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 10:00:16AM +0200, bi...@debian.org wrote:
> Package: pass-extension-tomb
> Version: 1.3-2
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package pass-extension-tomb is shipping files (.service, 
> .socket or
> .timer) in /usr/lib/systemd/system.
[...]

The culprit seems to be here:
https://sources.debian.org/src/pass-tomb/1.3-2/Makefile/#L21

(and also line 36)


```
@install -Dm0644 pass-close@.service 
"$(DESTDIR)$(LIBDIR)/systemd/system/pass-close@.service"
```

To get the correct path you could use:
```
pkg-config  --variable=systemdsystemunitdir systemd
```

(Note: do not forget to also build-dep on the package containing systemd.pc as 
well as pkg-config itself.)

Regards,
Andreas Henriksson

Bug#1034238: fapolicyd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 02:23:32PM +0200, Andreas Henriksson wrote:
> On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> > Package: fapolicyd
> > Version: 1.1.7-3   
> > Severity: serious
> > Tags: sid bookworm
> > User: debhel...@packages.debian.org
> > Usertags: systemd-files-in-usr-bookworm
> > 
> > Dear Maintainer,
> > 
> > It seems that your package fapolicyd is shipping files (.service, .socket or
> > .timer) in /usr/lib/systemd/system.
> [...]
> 
> The problem seems to come from the more or less hardcoded path in
> configure.at at:
> https://sources.debian.org/src/fapolicyd/1.1.7-3/configure.ac/#L74
> 
> ```
> dnl FIXME some day pass this on the command line
> def_systemdsystemunitdir=${prefix}/lib/systemd/system
> AC_SUBST([systemdsystemunitdir], [$def_systemdsystemunitdir])
> ```
> 
> For example how to use value from systemd.pc, see a random example:
> https://sources.debian.org/src/pam/1.5.2-6/configure.ac/?hl=646#L641-L649
> (Note: you'll also need a build-dep on package containing systemd.pc)

Actually this example might be broken ... should probably use
variable=systemdsystemunitdir rather than variable=systemdunitdir


> 
> Regards,
> Andreas Henriksson

Bug#1034246: bullseye-pu: package usb.ids/2023.01.16-0+deb11u1

[Aurelien Jarno]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: usb@packages.debian.org
Control: affects -1 + src:usb.ids

[ Reason ]
This new upstream version of the USB ID database adds a few USB devices.

[ Impact ]
New USB devices will not be displayed with a human readable name for
package using this database.

[ Tests ]
There is no test associated with this database. This package only
contains data, no code.

[ Risks ]
Risks are very low, such update are routinely done in stable.

[ Checklist ]
  [ ] *all* changes are documented in the d/changelog
  [ ] I reviewed all changes and I approve them
  [ ] attach debdiff against the package in (old)stable
  [ ] the issue is verified as fixed in unstable

[ Changes ]
I would like to do an update of the usb.ids package to add/update around
~150USB devices to the usb.ids database. Those changes are already in
testing/sid for more than 2 months.

I have figured out that it's easier to just upload the package from
testing/sid with a new changelog entry, however it comes with a new
Standards-Version and debhelper compat level. Those have no impact on
the resulting binary package.

[ Other info ]
I have already uploaded the package to the archive. Thanks for
considering.

Bug#1025069: pavucontrol

[Alban Browaeys]

Le dimanche 09 avril 2023 à 15:03 -0500, Lucas a écrit :
> I should have let you know when I created it, but I still have no
> feedback from a bug report I wrote to the pipewire developers:
> https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3131.
> 


"Multichannel Output" Profile disappeared after I ran JACK (ardour),
and I only see again now on a fresh startup.

Do you mean it disappeared from pavucontrol when you run JACK from
ardour ?

What I meant is that you cannot run pipewire and jackd at the same time
? I cannot work as one will prevent the other from accessing the ALSA
sound device.
If you want to run JACK application whne running pipewire you can only
do so by pipewire-jackd and disabling jackd. 
This is not a pipewire bug. jackd also cannot work if the sound device
is already taken by an alsa program or any other daemon plugging to the
alsa interface (pipewire, pulseaudio), it could work because for one
pulseaudio aut suspend itself from time to time so the alsa sound
device is free when so. But then when pulseaudio will resume and your
jackd daemon is holding on the alsa sound device pulseaudio will not
work. This is not supported (for pulseaudio you could use the pasuspend
tool, still it is  hack).


Also:
Gnome Settings Output Device contains nothing to select, while Input
allows "Analog Input - STUDIO-CAPTURE" and "STUDIO-CAPTURE Pro". The
only way to have output audio working is to use pavucontrol and select
either of the STUDIO-CAPTURE Profile Configurations "Multichannel
Output", or "Pro Audio".  
and:
That "Multichannel Output" Profile disappeared after I ran JACK
(ardour), and I only see again now on a fresh startup.
seems to be two different issue. You should report both in two diffrent
bug report else it the bug report will get confusing soon.
My reply was about the second issue (which to me look like a normal
behavior).


For the first one, I am a bit confused. You mean that even in
pavucontrol if you do not switch to the STUDIO-CAPTURE Profile
Configurations "Multichannel Output", or "Pro Audio" you cannot set a
sound output device?

If you bug report upstream you could try to run pipewire built from
source (you just have to stop pipewire related systemd user services,
ie systemctl --user stop pipewire.service, etc).
Also there is a newer pipewire version 0.3.76 in Debian rc-buggy
(experimental).


> I guessed it was a "port detection" issue after reading this response
> on the original poster's bug report:
> https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3086#note_1831991
> 

Could you provide the same debug logs as this bug reporter did?

loginctl user-status | grep State
lsof /dev/snd/*
fuser -v /dev/snd/*
aplay -l
journalctl --user -b --unit pipewire.service

and maybe also 
journalctl --user -b --unit pipewire-pulse.service
pipewire --version


and why not the output when running gnome-control-center from a
terminal:
gnome-control-center --verbose sound

Still could you try with pipewire-jack instead of jackd (even if you
prefer to run jackd only while running a jack application.

Cheers
Alban

> 
> On Sun, Apr 9, 2023 at 1:33 PM Lucas  wrote:
> > On Fri, Apr 7, 2023 at 7:57 PM Alban Browaeys
> >  wrote:
> > >
> > > Do you have jackd installed and runnning at the same time as
> > pipewire-
> > > pulse?
> > > Maybe you want to try piepwire-jack instead?
> > >
> > > Cheers,
> > > Alban
> > >
> > 
> > I appreciate the suggestion, but since I also use multiple devices
> > with JACK, it's only running when I want to record and use a
> > specific
> > profile/device.  Ardour will start it using the last used (default)
> > profile, but only when I've not already started JACK from qjackctl
> > to
> > use another profile.  I think having it always running may
> > complicate
> > this setup I've grown accustomed to.  Are you aware of any issues
> > trying to stop JACK (to use other rates and devices) when using
> > pipewire-jack?
> > 
> > Thanks,
> >   Lucas
> 
> 
> -- 
> Protect your digital freedom and privacy, eliminate DRM, learn more
> at http://www.defectivebydesign.org/what_is_drm
> On a related note, also see
> https://www.fsf.org/campaigns/surveillance

Bug#1034238: fapolicyd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Andreas Henriksson]

On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: fapolicyd
> Version: 1.1.7-3   
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package fapolicyd is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]

The problem seems to come from the more or less hardcoded path in
configure.at at:
https://sources.debian.org/src/fapolicyd/1.1.7-3/configure.ac/#L74

```
dnl FIXME some day pass this on the command line
def_systemdsystemunitdir=${prefix}/lib/systemd/system
AC_SUBST([systemdsystemunitdir], [$def_systemdsystemunitdir])
```

For example how to use value from systemd.pc, see a random example:
https://sources.debian.org/src/pam/1.5.2-6/configure.ac/?hl=646#L641-L649
(Note: you'll also need a build-dep on package containing systemd.pc)

Regards,
Andreas Henriksson

Bug#1034203: snmp: specifying -Op /at all/ segfaults all snmpcmd(1) commands

[Craig Small]

On Tue, 11 Apr 2023 at 11:48, наб  wrote:

> This happens in all these configurations:
>   $ snmptranslate -Op .1
>   Segmentation fault
>   $ snmptranslate -Op
>   Segmentation fault
>   $ snmpget -Op
>   Segmentation fault
>

Hi наб,
  Thanks for the report. I have passed this to upstream at
https://github.com/net-snmp/net-snmp/issues/554
The programs all use the same parser so it's not surprising they all have
this issue. The additional issue for snmptranslate
might be something extra.

It happens with the upstream pre2 release of 5.9.4 as well so it's not
Debian-specific unless it's my build options.

 - Craig

Bug#950920: (no subject)

[Gregor Riepl]

I've committed a patch that will make the problems go away and shouldn't 
cause any issues when the dtype already matches the expectation, i.e. 
when the platform's int type is equal or greater than np.int64.


There is a slight risk with the type conversion though: When the input 
is very large and uses indices > 2³¹-1. This will cause data loss on 
32-bit architectures without any warning. I did some simple tests and 
found that this will cause failures in other places (memory allocation, 
for example), but that's not very reliable.


Unfortunately, I couldn't find a way to do an efficient "unsafe" 
conversion with a warning in numpy - a lot of boilerplate and 
performance loss would be needed to do this manually.


The Fedora developers already reported the issue upstream, by the way:
https://github.com/mikedh/trimesh/issues/690

Bug#1034134: [pre-approval] unblock: glibc/2.36-9

[Aurelien Jarno]

control: tags -1 -moreinfo

On 2023-04-10 18:30, Sebastian Ramacher wrote:
> Control: tags -1 moreinfo confirmed
> 
> On 2023-04-10 11:02:23 +0200, Aurelien Jarno wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > X-Debbugs-Cc: gl...@packages.debian.org, debian-gl...@lists.debian.org
> > Control: affects -1 + src:glibc
> > 
> > [ Reason ]
> > An RC bug reported by a user (#1033931) triggered a routing update of
> > the glibc package from the upstream stable tree, which contains the fix.
> > 
> > The upstream stable tree also includes a fix to the daylight computation
> > affecting at least the Africa/Tripoli timezone, as well as a fix to the
> > testsuite on POWER when compiling with -mcpu=power10 (which is not the
> > case of Debian).
> > 
> > This is also the occasion to update the debconf translation that has
> > been received since the toolchain freeze.
> 
> Please go ahead and remove the moreinfo tag once the version is
> available in unstable.

The update is now available in unstable, and has been built on all
release architectures.

Cheers
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#1034245: pre-approval: unblock: openvswitch/3.1.1 (CVE-2023-1668)

[Thomas Goirand]

Hi,

I would very much prefer to upload the latest point release from 
upstream, however, if the release team prefers, here's a debdiff, 
attached to this message, containing a more targeted fix.


Note that the debdiff contains a "quilt refresh" of the 
ovs-ctl-ipsec.patch already present in Bookworm, as I saw offsets when 
doing "quilt push" (which may be annoying depending on your build env). 
Not sure (because uploaded by Luca) how it got in.


Please let me know your decision (ie: latest point release from upstream 
or this patch).


Cheers,

Thomas Goirand (zigo)diff -Nru openvswitch-3.1.0/debian/changelog openvswitch-3.1.0/debian/changelog
--- openvswitch-3.1.0/debian/changelog  2023-02-21 23:02:16.0 +0100
+++ openvswitch-3.1.0/debian/changelog  2023-04-11 11:54:40.0 +0200
@@ -1,3 +1,11 @@
+openvswitch (3.1.0-2) unstable; urgency=high
+
+  * CVE-2023-1668: Remote traffic denial of service via crafted packets with IP
+proto 0. Applied upstream patch: ofproto-dpif-xlate: Always mask ip proto
+field (Closes: #1034042).
+
+ -- Thomas Goirand   Tue, 11 Apr 2023 11:54:40 +0200
+
 openvswitch (3.1.0-1) unstable; urgency=medium
 
   [ Luca Boccassi ]
diff -Nru 
openvswitch-3.1.0/debian/patches/CVE-2023-1668_ofproto-dpif-xlate_Always_mask_ip_proto_field.patch
 
openvswitch-3.1.0/debian/patches/CVE-2023-1668_ofproto-dpif-xlate_Always_mask_ip_proto_field.patch
--- 
openvswitch-3.1.0/debian/patches/CVE-2023-1668_ofproto-dpif-xlate_Always_mask_ip_proto_field.patch
  1970-01-01 01:00:00.0 +0100
+++ 
openvswitch-3.1.0/debian/patches/CVE-2023-1668_ofproto-dpif-xlate_Always_mask_ip_proto_field.patch
  2023-04-11 11:54:40.0 +0200
@@ -0,0 +1,425 @@
+Subject: CVE-2023-1668: ofproto-dpif-xlate: Always mask ip proto field.
+ The ofproto layer currently treats nw_proto field as overloaded to mean
+ both that a proper nw layer exists, as well as the value contained in
+ the header for the nw proto.  However, this is incorrect behavior as
+ relevant standards permit that any value, including '0' should be treated
+ as a valid value.
+ .
+ Because of this overload, when the ofproto layer builds action list for
+ a packet with nw_proto of 0, it won't build the complete action list that
+ we expect to be built for the packet.  That will cause a bad behavior
+ where all packets passing the datapath will fall into an incomplete
+ action set.
+ .
+ The fix here is to unwildcard nw_proto, allowing us to preserve setting
+ actions for protocols which we know have support for the actions we
+ program.  This means that a traffic which contains nw_proto == 0 cannot
+ cause connectivity breakage with other traffic on the link.
+Author: Aaron Conole 
+Date: Fri, 31 Mar 2023 17:17:27 -0400
+Reported-by: David Marchand 
+Reported-at: https://bugzilla.redhat.com/show_bug.cgi?id=2134873
+Acked-by: Ilya Maximets 
+Signed-off-by: Aaron Conole 
+Signed-off-by: Ilya Maximets 
+Origin: upstream, 
https://github.com/openvswitch/ovs/commit/61b39d8c4797f1b668e4d5e5350d639fca6082a9.patch
+Bug-Debian: https://bugs.debian.org/1034042
+Last-Update: 2023-04-11
+
+diff --git a/include/openvswitch/meta-flow.h b/include/openvswitch/meta-flow.h
+index 045dce8f5fa..3b0220aaa25 100644
+--- a/include/openvswitch/meta-flow.h
 b/include/openvswitch/meta-flow.h
+@@ -2366,6 +2366,10 @@ void mf_format_subvalue(const union mf_subvalue 
*subvalue, struct ds *s);
+ void field_array_set(enum mf_field_id id, const union mf_value *,
+  struct field_array *);
+ 
++/* Mask the required l3 prerequisites if a 'set' action occurs. */
++void mf_set_mask_l3_prereqs(const struct mf_field *, const struct flow *,
++struct flow_wildcards *);
++
+ #ifdef __cplusplus
+ }
+ #endif
+diff --git a/lib/meta-flow.c b/lib/meta-flow.c
+index c576ae6202a..474344194fa 100644
+--- a/lib/meta-flow.c
 b/lib/meta-flow.c
+@@ -3676,3 +3676,28 @@ mf_bitmap_not(struct mf_bitmap x)
+ bitmap_not(x.bm, MFF_N_IDS);
+ return x;
+ }
++
++void
++mf_set_mask_l3_prereqs(const struct mf_field *mf, const struct flow *fl,
++   struct flow_wildcards *wc)
++{
++if (is_ip_any(fl) &&
++((mf->id == MFF_IPV4_SRC) ||
++ (mf->id == MFF_IPV4_DST) ||
++ (mf->id == MFF_IPV6_SRC) ||
++ (mf->id == MFF_IPV6_DST) ||
++ (mf->id == MFF_IPV6_LABEL) ||
++ (mf->id == MFF_IP_DSCP) ||
++ (mf->id == MFF_IP_ECN) ||
++ (mf->id == MFF_IP_TTL))) {
++WC_MASK_FIELD(wc, nw_proto);
++} else if ((fl->dl_type == htons(ETH_TYPE_ARP)) &&
++   ((mf->id == MFF_ARP_OP) ||
++(mf->id == MFF_ARP_SHA) ||
++(mf->id == MFF_ARP_THA) ||
++(mf->id == MFF_ARP_SPA) ||
++(mf->id == MFF_ARP_TPA))) {
++/* mask only the lower 8 bits. */
++wc->masks.nw_proto = 0xff;
++}
++}
+diff --git a/ofproto/ofproto-dpif-xlate.c b/ofproto/ofproto-dpif-xlate.c
+index 

Bug#1030930: podman: DNS resolution fails in 'podman build' but works in 'podman run'

[Kevin P. Fleming]

On Mon, Apr 10, 2023, at 17:52, Reinhard Tartler wrote:
> Control: tag -1 + unreproducible moreinfo
> 
> Hi Kevin,
> 
> great to hear from you in this space!
> 
> On Thu, Feb 9, 2023 at 8:36 AM Kevin P. Fleming  wrote:
>> Package: podman
>> Version: 4.3.1+ds1-5+b1
>> Severity: important
>> 
>> Dear Maintainer,
>> 
>> I am seeing DNS resolution fail when using 'podman build' but succeed when
>> using 'podman run', with a Dockerfile which contains the same commands I run
>> manually in the 'podman run'-launched shell.
>> 
>> Dockerfile
>> --
>> FROM alpine:3.10
>> RUN cat /etc/resolv.conf
>> RUN apk add tar
>  
> Unfortunately, I can't reproduce. Please help me to reproduce this issue. 
> Also, maybe upstream has an idea, can you please report this issue at 
> https://github.com/containers/podman/issues/new/choose. In any case, here is 
> the output that I get:
> 
> siretart@x1:/tmp/dnstest$ cat >> Containerfile
> FROM alpine:3.10
> RUN cat /etc/resolv.conf
> RUN apk add tar
> siretart@x1:/tmp/dnstest$ cat Containerfile
> FROM alpine:3.10
> RUN cat /etc/resolv.conf
> RUN apk add tar
> siretart@x1:/tmp/dnstest$ podman build .
> STEP 1/3: FROM alpine:3.10
> Resolved "alpine" as an alias 
> (/etc/containers/registries.conf.d/shortnames.conf)
> Trying to pull docker.io/library/alpine:3.10...
> Getting image source signatures
> Copying blob 396c31837116 done  
> Copying config e7b300aee9 done  
> Writing manifest to image destination
> Storing signatures
> STEP 2/3: RUN cat /etc/resolv.conf
> search int.tauware.de
> nameserver 10.0.2.3
> nameserver 192.168.88.3
> --> 2ce59772eaf
> STEP 3/3: RUN apk add tar
> fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/main/x86_64/APKINDEX.tar.gz
> fetch 
> http://dl-cdn.alpinelinux.org/alpine/v3.10/community/x86_64/APKINDEX.tar.gz
> (1/1) Installing tar (1.32-r1)
> Executing busybox-1.30.1-r5.trigger
> OK: 6 MiB in 15 packages
> COMMIT
> --> 7c1bfd9e030
> 7c1bfd9e030f07b05cc9427a97c0bc5ff73bca5436bce389ad81da1a64f64a11

Confirmed; I can no longer reproduce the problem. Something somewhere in the 
stack got fixed :-)

Bug#1033632: qa.debian.org: sourceforge redirector for debian/watch files fails with a 500 error

[Peter Blackman]

On 06/04/2023 11:44, Christian Marillat wrote:

On 06 avril 2023 11:26, Peter B  wrote:


I think this problem is now resolved.
The big red ERROR texts in the Watch column on my DDPO page are slowly going 
away.

I don't know. I re-written my watch files to check sourceforge.net
instead of qa.debian.org

Christian


Hi Christian,

Seems I spoke too soon!  While uscan usually works when I try it locally,
now seems to fail randomly on my QA page.

Cheers,
Peter

Bug#1034245: pre-approval: unblock: openvswitch/3.1.1 (CVE-2023-1668)

[Thomas Goirand]

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

Dear release team,

I'd like to upload OpenVSwitch 3.1.1 as the fix for CVE-2023-1668.

The upstream last point release contains only bugfixes, however,
the diff is still kind of significant.

The upstream diff contained lots of noise, like documentation,
tests, an update of the configure script and so on, that made the
diff more difficult to read. I have therefore filtered the diff for
all of this, and rm these in the attached diff:

- rhel (folder)
- Documentation/ref/ovs-actions.7.rst
- config.h.in
- build-aux
- configure
- tests (folder)

Does the release team agree that it's ok to upload 3.1.1, or should
I aim for a more targeted fix?

The diff upstream more specific to this CVE is:
https://github.com/openvswitch/ovs/commit/61b39d8c4797f1b668e4d5e5350d639fca6082a9

I would still prefer to include all bugfixes though, if possible.
Please let me know ASAP, as this is a grave security fix.
Also note that I've already sent to the security team the fix for
the version in Bullseye (and I'll probably also attempt to fix
in Buster, maybe later on...).

Cheers,

Thomas Goirand (zigo)
diff -u -N -r openvswitch-3.1.0/aclocal.m4 openvswitch-3.1.1/aclocal.m4
--- openvswitch-3.1.0/aclocal.m42023-02-16 17:31:22.310879633 +0100
+++ openvswitch-3.1.1/aclocal.m42023-04-06 17:12:17.243817086 +0200
@@ -1,6 +1,6 @@
-# generated automatically by aclocal 1.16.2 -*- Autoconf -*-
+# generated automatically by aclocal 1.16.5 -*- Autoconf -*-
 
-# Copyright (C) 1996-2020 Free Software Foundation, Inc.
+# Copyright (C) 1996-2021 Free Software Foundation, Inc.
 
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -14,13 +14,13 @@
 m4_ifndef([AC_CONFIG_MACRO_DIRS], [m4_defun([_AM_CONFIG_MACRO_DIRS], 
[])m4_defun([AC_CONFIG_MACRO_DIRS], [_AM_CONFIG_MACRO_DIRS($@)])])
 m4_ifndef([AC_AUTOCONF_VERSION],
   [m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnl
-m4_if(m4_defn([AC_AUTOCONF_VERSION]), [2.69],,
-[m4_warning([this file was generated for autoconf 2.69.
+m4_if(m4_defn([AC_AUTOCONF_VERSION]), [2.71],,
+[m4_warning([this file was generated for autoconf 2.71.
 You have another version of autoconf.  It may work, but is not guaranteed to.
 If you have problems, you may need to regenerate the build system entirely.
 To do so, use the procedure documented by the package, typically 
'autoreconf'.])])
 
-# Copyright (C) 2002-2020 Free Software Foundation, Inc.
+# Copyright (C) 2002-2021 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -35,7 +35,7 @@
 [am__api_version='1.16'
 dnl Some users find AM_AUTOMAKE_VERSION and mistake it for a way to
 dnl require some minimum version.  Point them to the right macro.
-m4_if([$1], [1.16.2], [],
+m4_if([$1], [1.16.5], [],
   [AC_FATAL([Do not call $0, use AM_INIT_AUTOMAKE([$1]).])])dnl
 ])
 
@@ -51,14 +51,14 @@
 # Call AM_AUTOMAKE_VERSION and AM_AUTOMAKE_VERSION so they can be traced.
 # This function is AC_REQUIREd by AM_INIT_AUTOMAKE.
 AC_DEFUN([AM_SET_CURRENT_AUTOMAKE_VERSION],
-[AM_AUTOMAKE_VERSION([1.16.2])dnl
+[AM_AUTOMAKE_VERSION([1.16.5])dnl
 m4_ifndef([AC_AUTOCONF_VERSION],
   [m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnl
 _AM_AUTOCONF_VERSION(m4_defn([AC_AUTOCONF_VERSION]))])
 
 # AM_AUX_DIR_EXPAND -*- Autoconf -*-
 
-# Copyright (C) 2001-2020 Free Software Foundation, Inc.
+# Copyright (C) 2001-2021 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -110,7 +110,7 @@
 
 # AM_CONDITIONAL-*- Autoconf -*-
 
-# Copyright (C) 1997-2020 Free Software Foundation, Inc.
+# Copyright (C) 1997-2021 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -141,7 +141,7 @@
 Usually this means the macro was only invoked conditionally.]])
 fi])])
 
-# Copyright (C) 1999-2020 Free Software Foundation, Inc.
+# Copyright (C) 1999-2021 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -332,7 +332,7 @@
 
 # Generate code to set up dependency tracking.  -*- Autoconf -*-
 
-# Copyright (C) 1999-2020 Free Software Foundation, Inc.
+# Copyright (C) 1999-2021 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -400,7 +400,7 @@
 
 # Do all the work for Automake. -*- Autoconf -*-
 
-# Copyright (C) 1996-2020 Free Software Foundation, Inc.
+# Copyright (C) 

Bug#1034244: unblock (pre-approval): lua-readline/3.2-2

[Sergei Golovan]

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

I'd like to upload lua-readline with a bugfix for #1034078 (see [1]).

[ Reason ]
This upload fixes #1034078. The patch is made upstream and taken
from newly released version 3.3.

[ Impact ]
This bug is a regression in version 3.2 which significantly
worsens user experience (standard Ctrl+D isn't interpreted as EOF).

[ Tests ]
There aren't automated tests, but manual testing using upstream test
code doesn't reveal any other regressions/bugs.

[ Risks ]
The code change is trivial, the bug currently affects the prosody
packhage in a way that its admin cannot simply exit from the
prosody server management console.

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

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034078

unblock lua-readline/3.2-2
diff --git a/debian/changelog b/debian/changelog
index 4456e53..7450934 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+lua-readline (3.2-2) unstable; urgency=medium
+
+  * Fix regression which does not allow to use Ctrl-D (EOF) to close
+readline session (closes: #1034078).
+
+ -- Sergei Golovan   Sun, 09 Apr 2023 12:28:12 +0300
+
 lua-readline (3.2-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/patches/eof.patch b/debian/patches/eof.patch
new file mode 100644
index 000..2ac8eeb
--- /dev/null
+++ b/debian/patches/eof.patch
@@ -0,0 +1,39 @@
+Author: Upstream
+Description: Patch restores processing EOF (Ctrl+D), when readline()
+ returns NULL, distinguishable from an empty string.
+Debian-Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034078
+
+--- a/C-readline.c
 b/C-readline.c
+@@ -65,7 +65,13 @@
+   /* rl_cleanup_after_signal(); rl_clear_signals();  no effect :-( 1.3 */
+   /* lua_pushstring(L, line); */
+   /* 3.2 did lua_pushstring create a copy of the string ? */
+-  lua_pushfstring(L, "%s", line);   /* 3.2 */
++  /* lua_pushfstring(L, "%s", line);   3.2 */
++  if (line == NULL) { /* 3.3 fix by zash.se, Prosody developer */
++  lua_pushnil(L);
++  } else {
++  lua_pushfstring(L, "%s", line);
++  // lua_pushstring(L, line); should be fine as well
++  }
+   if (tty_stream != NULL) { fclose(tty_stream); }
+   free(line);  /* 3.2 fixes memory leak */
+   return 1;
+@@ -135,13 +141,15 @@
+   return 0;
+ }
+ 
+-static int c_write_history(lua_State *L) {  /* filename in, returncode out */
++/* unused ...
++static int c_write_history(lua_State *L) {  //  filename in, returncode out
+   size_t len;
+   const char *filename  = lua_tolstring(L, 1, );
+ lua_Integer rc = write_history(filename);
+   lua_pushinteger(L, rc);
+   return 1;
+ }
++*/
+ 
+ static int c_history_truncate_file(lua_State *L) { /* filename,num in rc out 
*/
+   size_t len;
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..84626e5
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+eof.patch

Bug#1034243: unblock: heat/19.0.0-2 (fix for CVE-2023-1625 / #1034186)

[Thomas Goirand]

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

Please unblock package heat

[ Reason ]
This last upload fixes CVE-2023-1625 / #1034186 (information leak in the
Heat API).

[ Impact ]
Before this patch, "openstack stack show" shows parameters that
are supposed to be hidden, like for example passwords (see the
launchpad entry https://launchpad.net/bugs/1999665 that is rather
explicit).

[ Tests ]
Building the package and the Debian CI contains upstream unit tests.
Also, the patch comes directly from upstream that runs functional
tests in their CI, which makes me confident nothing broke with this
patch. See test results at:
https://review.opendev.org/c/openstack/heat/+/873465

[ Risks ]
Not much risks as the patch only affects "stack show".

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

Cheers,

Thomas Goirand (zigo)

unblock heat/19.0.0-2
diff -Nru heat-19.0.0/debian/changelog heat-19.0.0/debian/changelog
--- heat-19.0.0/debian/changelog2022-10-06 10:14:02.0 +0200
+++ heat-19.0.0/debian/changelog2023-04-11 10:21:00.0 +0200
@@ -1,3 +1,12 @@
+heat (1:19.0.0-2) unstable; urgency=high
+
+  * CVE-2023-1625: information leak in API. Added upstream patch:
+Honor-hidden-parameter-in-stack_environment_show-command.patch
+(Closes: #1034186).
+  * Removed obsolete depends on lsb-base.
+
+ -- Thomas Goirand   Tue, 11 Apr 2023 10:21:00 +0200
+
 heat (1:19.0.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru heat-19.0.0/debian/control heat-19.0.0/debian/control
--- heat-19.0.0/debian/control  2022-10-06 10:14:02.0 +0200
+++ heat-19.0.0/debian/control  2023-04-11 10:21:00.0 +0200
@@ -113,7 +113,6 @@
  python3-pastescript,
  uwsgi-plugin-python3,
  ${misc:Depends},
- ${ostack-lsb-base},
  ${python3:Depends},
 Description: OpenStack orchestration service - API server
  Heat is a service to orchestrate multiple composite cloud applications using
@@ -130,7 +129,6 @@
  python3-pastescript,
  uwsgi-plugin-python3,
  ${misc:Depends},
- ${ostack-lsb-base},
  ${python3:Depends},
 Description: OpenStack orchestration service - CFN API
  Heat is a service to orchestrate multiple composite cloud applications using
@@ -174,7 +172,6 @@
  adduser,
  heat-common (=${binary:Version}),
  ${misc:Depends},
- ${ostack-lsb-base},
  ${python3:Depends},
 Description: OpenStack orchestration service - engine
  Heat is a service to orchestrate multiple composite cloud applications using
diff -Nru heat-19.0.0/debian/debian_control_vars 
heat-19.0.0/debian/debian_control_vars
--- heat-19.0.0/debian/debian_control_vars  2022-10-06 10:14:02.0 
+0200
+++ heat-19.0.0/debian/debian_control_vars  1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-ostack-lsb-base= lsb-base
diff -Nru 
heat-19.0.0/debian/patches/CVE-2023-1625_Honor-hidden-parameter-in-stack_environment_show-command.patch
 
heat-19.0.0/debian/patches/CVE-2023-1625_Honor-hidden-parameter-in-stack_environment_show-command.patch
--- 
heat-19.0.0/debian/patches/CVE-2023-1625_Honor-hidden-parameter-in-stack_environment_show-command.patch
 1970-01-01 01:00:00.0 +0100
+++ 
heat-19.0.0/debian/patches/CVE-2023-1625_Honor-hidden-parameter-in-stack_environment_show-command.patch
 2023-04-11 10:21:00.0 +0200
@@ -0,0 +1,74 @@
+Description: CVE-2023-1625L Honor hidden parameter in 'stack environment show' 
command
+ Backport note:
+ This includes change I0abbd535aacc03446ada0fa806dfdfdaa4522afe which
+ fixed the wrong explanation in the release note file.
+Author: Chengen Du 
+Date: Tue, 20 Dec 2022 18:00:00 +0800
+Bug: https://launchpad.net/bugs/1999665
+Bug-Debian: https://bugs.debian.org/1034186
+Story: 2010484
+Task: 47052
+Change-Id: Ifc51ff6a4deab05002ccded59383416f9a586aa0
+Origin: upstream, https://review.opendev.org/c/openstack/heat/+/873465
+Last-Update: 2023-04-11
+
+diff --git a/heat/engine/service.py b/heat/engine/service.py
+index fdd4975..9019ddb 100644
+--- a/heat/engine/service.py
 b/heat/engine/service.py
+@@ -12,6 +12,7 @@
+ #under the License.
+ 
+ import collections
++import copy
+ import datetime
+ import functools
+ import itertools
+@@ -1354,7 +1355,16 @@
+ :rtype: dict
+ """
+ s = self._get_stack(cnxt, stack_identity, show_deleted=True)
+-return s.raw_template.environment
++tmpl = templatem.Template.load(cnxt, s.raw_template_id, 
s.raw_template)
++param_schemata = tmpl.all_param_schemata(tmpl.files)
++env = copy.deepcopy(s.raw_template.environment)
++for section in [env_fmt.PARAMETERS, env_fmt.PARAMETER_DEFAULTS]:
++for param_name in env.get(section, {}).keys():
++if (param_name not in param_schemata
++or not param_schemata[param_name].hidden):
++

Bug#1034242: unblock: tirex/0.7.0-3

[Bas Couwenberg]

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

Please unblock package tirex

It moves the systemd services back to /lib/systemd to fix #1034222.

[ Reason ]
Fix service activation by debhelper.

[ Impact ]
Services not activated as expected.

[ Tests ]
N/A

[ Risks ]
Low, leaf package.

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

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

The pending changes in git are also included which we'd rather not have to 
revert.

unblock tirex/0.7.0-3
diff -Nru tirex-0.7.0/debian/changelog tirex-0.7.0/debian/changelog
--- tirex-0.7.0/debian/changelog2022-08-03 10:27:51.0 +0200
+++ tirex-0.7.0/debian/changelog2023-04-11 10:20:03.0 +0200
@@ -1,3 +1,14 @@
+tirex (0.7.0-3) unstable; urgency=medium
+
+  * Team upload.
+  * Add Rules-Requires-Root to control file.
+  * Update lintian overrides.
+  * Bump Standards-Version to 4.6.2, no changes.
+  * Move systemd services to /lib/systemd.
+(closes: #1034222)
+
+ -- Bas Couwenberg   Tue, 11 Apr 2023 10:20:03 +0200
+
 tirex (0.7.0-2) unstable; urgency=medium
 
   [ Frederik Ramm ]
diff -Nru tirex-0.7.0/debian/control tirex-0.7.0/debian/control
--- tirex-0.7.0/debian/control  2022-06-21 07:23:56.0 +0200
+++ tirex-0.7.0/debian/control  2023-01-18 17:21:22.0 +0100
@@ -9,10 +9,11 @@
libipc-sharelite-perl,
libjson-perl,
libmapnik-dev
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/debian-gis-team/tirex
 Vcs-Git: https://salsa.debian.org/debian-gis-team/tirex.git
 Homepage: https://wiki.openstreetmap.org/wiki/Tirex
+Rules-Requires-Root: no
 
 Package: tirex
 Section: utils
diff -Nru tirex-0.7.0/debian/patches/rules-requires-root.patch 
tirex-0.7.0/debian/patches/rules-requires-root.patch
--- tirex-0.7.0/debian/patches/rules-requires-root.patch1970-01-01 
01:00:00.0 +0100
+++ tirex-0.7.0/debian/patches/rules-requires-root.patch2022-11-29 
19:11:38.0 +0100
@@ -0,0 +1,12 @@
+Description: Fix FTBFS Rules-Requires-Root: no.
+Author: Bas Couwenberg 
+Forwarded: not-needed
+
+--- a/Makefile
 b/Makefile
+@@ -1,4 +1,4 @@
+-INSTALLOPTS=-g root -o root
++INSTALLOPTS=
+ build: Makefile.perl
+   cd backend-mapnik; $(MAKE) $(MFLAGS)
+   $(MAKE) -f Makefile.perl
diff -Nru tirex-0.7.0/debian/patches/series tirex-0.7.0/debian/patches/series
--- tirex-0.7.0/debian/patches/series   2021-10-07 17:46:27.0 +0200
+++ tirex-0.7.0/debian/patches/series   2022-11-29 19:10:50.0 +0100
@@ -1 +1,2 @@
 0001-Make-sure-usr-libexec-directory-extists.patch
+rules-requires-root.patch
diff -Nru tirex-0.7.0/debian/rules tirex-0.7.0/debian/rules
--- tirex-0.7.0/debian/rules2021-10-08 10:02:58.0 +0200
+++ tirex-0.7.0/debian/rules2022-11-29 19:04:47.0 +0100
@@ -9,7 +9,4 @@
 %:
dh $@ --with apache2
 
-override_dh_auto_install:
-   dh_auto_install --destdir=debian/tmp
-
 .PHONY: templates
diff -Nru tirex-0.7.0/debian/tirex.install tirex-0.7.0/debian/tirex.install
--- tirex-0.7.0/debian/tirex.install2021-10-07 17:46:27.0 +0200
+++ tirex-0.7.0/debian/tirex.install2023-04-11 10:03:09.0 +0200
@@ -24,7 +24,7 @@
 debian/etc/tirex/tirex.conf  etc/tirex
 debian/etc/tirex/renderer/mapnik.confetc/tirex/renderer
 debian/tmpfiles.d/tirex.conf usr/lib/tmpfiles.d
-debian/tirex-master.service  usr/lib/systemd/system/
-debian/tirex-backend-manager.service usr/lib/systemd/system/
+debian/tirex-master.service  lib/systemd/system/
+debian/tirex-backend-manager.service lib/systemd/system/
 usr/libexec/tirex-backend-mapnik
 usr/libexec/tirex-backend-test
diff -Nru tirex-0.7.0/debian/tirex.lintian-overrides 
tirex-0.7.0/debian/tirex.lintian-overrides
--- tirex-0.7.0/debian/tirex.lintian-overrides  2021-10-08 09:39:26.0 
+0200
+++ tirex-0.7.0/debian/tirex.lintian-overrides  2022-11-29 19:18:57.0 
+0100
@@ -1,2 +1,6 @@
 # This package only provides systemd unit files:
 package-supports-alternative-init-but-no-init.d-script
+
+# False positive, lat/lon
+typo-in-manual-page lon long *
+

Bug#1031695: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Laurent Bigonville]

FTR, I opened RC bugs against all the impacted packages so they will 
hopefully be fixed for bookworm


See: 
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=debhelper%40packages.debian.org=systemd-files-in-usr-bookworm

Bug#1034241: [INTL:ro] Romanian debconf templates translation of apt-listchanges

[Remus-Gabriel Chelu]

Package: apt-listchanges
Version: N/A
Severity: wishlist
Tags: l10n, patch

Dear Maintainer,

Please find attached the Romanian translation of the «apt-listchanges» debconf 
templates file.

Thanks,
Remus-Gabriel

apt-listchanges_debconf_ro.po
Description: Binary data

Bug#1034239: vterm-mode make-process fails in an unshare(1)?

[Trent W. Buck]

Package: elpa-vterm
Version: 0.0.2+git20230217.3e5a9b7-1
Severity: normal

I've wanted to try vterm for a couple of years, but not enough to trust melpa 
with a C compiler.
I noticed it's in bookworm, but I'm still on bullseye, so I spun up a container 
to test it.
Unfortunately, it's not working at all in the container:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  vterm--set-pty-name(# nil)
  vterm-mode()
  vterm--internal(pop-to-buffer-same-window nil)
  vterm(nil)
  funcall-interactively(vterm nil)
  command-execute(vterm)
  command-line-1(("-f" "toggle-debug-on-error" "-f" "vterm"))
  command-line()
  normal-top-level()

The command I ran was this:

mmdebstrap bookworm /dev/null --customize-hook='chroot $1 env -i TERM=vt100 
PATH=/bin emacs -f toggle-debug-on-error -f vterm; false' 
--include=emacs-nox,elpa-vterm,ncurses-base,usrmerge

I also tried some other variations, like this (no improvement):

mmdebstrap --aptopt='Acquire::http::Proxy "http://[::1]:3142;' 
--dpkgopt=force-unsafe-io --variant=apt bookworm /dev/null  
--customize-hook='chroot $1 env PAGER=cat LOGNAME=root USERNAME=root USER=root 
HOME=/root emacs -f toggle-debug-on-error -f vterm; false' 
--include=emacs-nox,elpa-vterm,ncurses-base

I tried doing C-u C-M-x on vterm-mode, then stepping through it.
When I did that, Emacs crashed (segfault, dump core).

Here's the backtrace of that:

bash5$ coredumpctl list --since=-1h
TIME PIDUIDGID SIG COREFILE EXE 
 SIZE
Tue 2023-04-11 17:28:22 AEST 1970182 10 10 SIGSEGV inaccessible 
/tmp/mmdebstrap.PtAiFer3xS/usr/bin/emacs-nox-
Tue 2023-04-11 17:39:46 AEST 1974335 10 10 SIGSEGV inaccessible 
/tmp/mmdebstrap.APQHGHHtCi/usr/bin/emacs-nox-
bash5$ coredumpctl info 1970182 1974335
   PID: 1970182 (emacs)
   UID: 10 (10)
   GID: 10 (10)
Signal: 11 (SEGV)
 Timestamp: Tue 2023-04-11 17:28:21 AEST (29min ago)
  Command Line: emacs -f toggle-debug-on-error -f vterm
Executable: /tmp/mmdebstrap.PtAiFer3xS/usr/bin/emacs-nox
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/gnome-terminal-server.service
  Unit: user@1000.service
 User Unit: gnome-terminal-server.service
 Slice: user-1000.slice
 Owner UID: 1000 (twb)
   Boot ID: 3f4a7af4e0db401887a00190ddffd551
Machine ID: 029d2e3fb4ee4d5eaa67c315db3ba66d
  Hostname: hera
   Storage: 
/var/lib/systemd/coredump/core.emacs.10.3f4a7af4e0db401887a00190ddffd551.1970182.168119810100.zst
 (inaccessible)
   Package: systemd/252.6-1
  build-id: ec45aeba740496bc309cc07882b0a061a3ad64f7
   Message: Process 1970182 (emacs) of user 10 dumped core.

Module /usr/bin/emacs-nox from deb systemd-252.6-1.amd64
Module 
/root/.emacs.d/eln-cache/28.2-15c5d1e2/ielm-2a8237b7-eb124f6e.eln from deb 
systemd-252.6-1.amd64
Module 
/root/.emacs.d/eln-cache/28.2-15c5d1e2/misearch-3d1286b0-5dfbae2a.eln from deb 
systemd-252.6-1.amd64
Module 
/usr/lib/emacs/28.2/native-lisp/28.2-15c5d1e2/comp-cstr-ef162ef7-d21e459f.eln 
from deb systemd-252.6-1.amd64
Module 
/usr/lib/emacs/28.2/native-lisp/28.2-15c5d1e2/warnings-28e75f4d-870b026e.eln 
from deb systemd-252.6-1.amd64
Module 
/usr/lib/emacs/28.2/native-lisp/28.2-15c5d1e2/rx-627d8c83-dfb131e2.eln from deb 
systemd-252.6-1.amd64
Module 
/usr/lib/emacs/28.2/native-lisp/28.2-15c5d1e2/cl-extra-d7051cba-b4a2a77f.eln 
from deb systemd-252.6-1.amd64
Module 
/usr/lib/emacs/28.2/native-lisp/28.2-15c5d1e2/comp-7672a6ed-15edf202.eln from 
deb systemd-252.6-1.amd64
Module 
/root/.emacs.d/eln-cache/28.2-15c5d1e2/radix-tree-669a468d-fa18562f.eln from 
deb systemd-252.6-1.amd64
Module 
/root/.emacs.d/eln-cache/28.2-15c5d1e2/help-fns-d233c6e8-7adaac53.eln from deb 
systemd-252.6-1.amd64
Module 
/root/.emacs.d/eln-cache/28.2-15c5d1e2/cl-print-79bf9fb1-244c7280.eln from deb 
systemd-252.6-1.amd64
Module 
/usr/lib/emacs/28.2/native-lisp/28.2-15c5d1e2/help-mode-d4dbae3d-aaa71a7e.eln 
from deb systemd-252.6-1.amd64
Module 
/root/.emacs.d/eln-cache/28.2-15c5d1e2/backtrace-f58a28c5-7ec5fbcd.eln from deb 
systemd-252.6-1.amd64
Module 
/root/.emacs.d/eln-cache/28.2-15c5d1e2/debug-bee52b4d-68f66c17.eln from deb 
systemd-252.6-1.amd64
Module 
/root/.emacs.d/eln-cache/28.2-15c5d1e2/kmacro-048feaec-498151b6.eln from deb 
systemd-252.6-1.amd64
Module 
/root/.emacs.d/eln-cache/28.2-15c5d1e2/pp-5d47c1cc-de730a1a.eln from deb 

Bug#1034208: Partman may reset user's choice for ESP partitions use

[Pascal Hambourg]

Package: partman-efi
Severity: minor

Boot method: USB stick
Image version: debian-bookworm-DI-rc1-amd64-netinst.iso

Dear maintainer,

as discussed in #debian-boot (you asked for it), I observed that partman 
resets the method set by the user on ESP partitions after setting LVM or 
RAID (and possibly encryption, I forgot to test).


Prerequisite: existing ESP partition(s).

Steps to reproduce:
- Select manual partitioning. All ESP partitions are set "use as: ESP" 
by default.

- Select an existing ESP partition and set it "do not use".
- Enter LVM or RAID setup.
- Leave LVM or RAID setup (no need to make any change).

Outcome: the EFI partition is set to "use as: ESP" again.

This is caused by /lib/partman/init.d/50efi rewriting "efi" to $id/ 
method when being re-run after leaving LVM/RAID setup.


Suggested fix: do not rewrite $id/method if 
/var/lib/partman/uefi_check_done exists, either by moving the check 
before the device loop (my preferred) or by adding a check before 
writing the method.


Use case: on multiboot systems I have multiple ESP partitions (possibly 
on multiple disks) and wish to force which one will be used for 
installation, so I need to disable the others.

Bug#1034205: wayout: does not do anything

[Willow Barraco]

Wayout is a daemon and must keep running for the output to be preserved.
The call | wayout is an example to demonstrate it take its input from
stdin.
Wayout display things above the wallpaper. It is not an overlay that is
present above other surfaces.
If the pipe shut down, then the stdin is broken, and so Wayout shutdown.

I think what you can do is to prepare a fifo file that Wayout will read.
You then can feed this file from outside, the way you want.

Bug#1034207: okular: typewriter annotation ignores some letters

[Janusz S . Bień]

Package: okular
Version: 4:20.12.3-2
Severity: normal
X-Debbugs-Cc: none, Janusz S. Bień 

Looks like the annotation ignores non-ASCII letters, cf. the attachment.

-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'unstable'), (500, 'stable'), (100, 'bullseye-fasttrack'), (100, 
'bullseye-backports-staging')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-21-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 okular depends on:
ii  kinit 5.78.0-2
ii  kio   5.78.0-5
ii  libc6 2.31-13+deb11u5
ii  libfreetype6  2.10.4+dfsg-1+deb11u1
ii  libjpeg62-turbo   1:2.0.6-4
ii  libkf5activities5 5.78.0-2
ii  libkf5archive55.78.0-2
ii  libkf5bookmarks5  5.78.0-2
ii  libkf5codecs5 5.78.0-2
ii  libkf5completion5 5.78.0-3
ii  libkf5configcore5 5.78.0-4
ii  libkf5configgui5  5.78.0-4
ii  libkf5configwidgets5  5.78.0-2
ii  libkf5coreaddons5 5.78.0-4
ii  libkf5crash5  5.78.0-3
ii  libkf5i18n5   5.78.0-2
ii  libkf5iconthemes5 5.78.0-2
ii  libkf5itemviews5  5.78.0-2
ii  libkf5jobwidgets5 5.78.0-2
ii  libkf5kexiv2-15.0.0   20.12.0-1
ii  libkf5kiocore55.78.0-5
ii  libkf5kiowidgets5 5.78.0-5
ii  libkf5parts5  5.78.0-3
ii  libkf5pty55.78.0-2
ii  libkf5purpose-bin 5.78.0-2
ii  libkf5purpose55.78.0-2
ii  libkf5service-bin 5.78.0-2
ii  libkf5service55.78.0-2
ii  libkf5textwidgets55.78.0-2
ii  libkf5wallet-bin  5.78.0-2
ii  libkf5wallet5 5.78.0-2
ii  libkf5widgetsaddons5  5.78.0-2
ii  libkf5windowsystem5   5.78.0-2
ii  libkf5xmlgui5 5.78.0-2
ii  libokular5core9   4:20.12.3-2
ii  libphonon4qt5-4   4:4.11.1-4
ii  libpoppler-qt5-1  20.09.0-3.1+deb11u1
ii  libqmobipocket2   4:20.12.0-1
ii  libqt5core5a  5.15.2+dfsg-9
ii  libqt5dbus5   5.15.2+dfsg-9
ii  libqt5gui55.15.2+dfsg-9
ii  libqt5printsupport5   5.15.2+dfsg-9
ii  libqt5svg55.15.2-3
ii  libqt5texttospeech5   5.15.2-2
ii  libqt5widgets55.15.2+dfsg-9
ii  libqt5xml55.15.2+dfsg-9
ii  libspectre1   0.2.9-1
ii  libstdc++610.2.1-6
ii  phonon4qt54:4.11.1-4
ii  zlib1g1:1.2.11.dfsg-2+deb11u2

Versions of packages okular recommends:
ii  cups-bsd  2.3.3op2-3+deb11u2

Versions of packages okular suggests:
ii  ghostscript9.53.3~dfsg-7+deb11u4
pn  okular-extra-backends  
ii  poppler-data   0.4.10-1
ii  texlive-binaries   2020.20200327.54578-7
ii  unrar  1:6.0.3-1+deb11u1

-- no debconf information



test.pdf
Description: Adobe PDF document


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