Bug#981928: marked as done (gauche-gtk FTBFS: unknown define-cclass qualifier(s) (::base))

[Debian Bug Tracking System]

Your message dated Wed, 12 Apr 2023 06:04:17 +
with message-id 
and subject line Bug#981928: fixed in gauche-gtk 0.6.1-1
has caused the Debian Bug report #981928,
regarding gauche-gtk FTBFS: unknown define-cclass qualifier(s) (::base)
to be marked as done.

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

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


-- 
981928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gauche-gtk
Version: 0.6+git20160927-3
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gauche-gtk.html

...
unknown define-cclass qualifier(s) (::base)
make[2]: *** [Makefile:10: gdkdisplay.c] Error 1
--- End Message ---
--- Begin Message ---
Source: gauche-gtk
Source-Version: 0.6.1-1
Done: NIIBE Yutaka 

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

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

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

Debian distribution maintenance software
pp.
NIIBE Yutaka  (supplier of updated gauche-gtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Apr 2023 14:16:04 +0900
Source: gauche-gtk
Binary: gauche-gtk gauche-gtk-dbgsym
Architecture: source amd64
Version: 0.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: NIIBE Yutaka 
Changed-By: NIIBE Yutaka 
Description:
 gauche-gtk - Gauche bindings for GTK+ GUI Toolkit
Closes: 981928
Changes:
 gauche-gtk (0.6.1-1) unstable; urgency=medium
 .
   * New upstream (Closes: #981928).
   * debian/patches/07-HUGE.patch: Remove.
   * debian/docs: Updated.
Checksums-Sha1:
 4b81041f3b764c066d32bc90cb6d1a9a49e5a5d4 1411 gauche-gtk_0.6.1-1.dsc
 55ca015fbe86a45b33b5418b445d25e5aad17f03 204720 gauche-gtk_0.6.1.orig.tar.gz
 5dbd8df4636c070f19f2325c2404161725603f0c 7348 gauche-gtk_0.6.1-1.debian.tar.xz
 c0f8f748ce5d769adf3b232feab08c10f0c025a8 2902424 
gauche-gtk-dbgsym_0.6.1-1_amd64.deb
 d8fac9583a3b399f7fdc3a2cc2b0df346c6ca3a6 12314 
gauche-gtk_0.6.1-1_amd64.buildinfo
 ccf48c047d7eef21d22781e9f37a7015114c3198 843572 gauche-gtk_0.6.1-1_amd64.deb
Checksums-Sha256:
 a128fdf8549121346e97ff04f7281947cb2c85082ed09e88bf9ee595d7b1b74d 1411 
gauche-gtk_0.6.1-1.dsc
 7df4d5e35429acd6fee7f34ae936fca3e6c698692214ccd01f6bcd052aac5f83 204720 
gauche-gtk_0.6.1.orig.tar.gz
 32ef34a4730aa8bb6680c88fbb148498be5ce8c9abbd6cc0e925a3d3a3b2adc4 7348 
gauche-gtk_0.6.1-1.debian.tar.xz
 fd51be42b07e6f3b159bb4c789d137bebfdf260f0f909d2b1d15cdd4b7baa938 2902424 
gauche-gtk-dbgsym_0.6.1-1_amd64.deb
 7bc66abd8ed85e7a01f535c57276de281ecef47305353f0f3b209e6e2039134b 12314 
gauche-gtk_0.6.1-1_amd64.buildinfo
 d943dff3b43e6debd5820cd26a914ff08e6c4864304227ed0156c2e3a7d1b33c 843572 
gauche-gtk_0.6.1-1_amd64.deb
Files:
 f5e2dcb497405c411aa46298ffebd82f 1411 lisp optional gauche-gtk_0.6.1-1.dsc
 94bff8f7e0e5bb9634a795bb9f5d2727 204720 lisp optional 
gauche-gtk_0.6.1.orig.tar.gz
 ead8f22b4f3ac74664cda5ace120a33a 7348 lisp optional 
gauche-gtk_0.6.1-1.debian.tar.xz
 709114ecf83cd09a2e33bb9dd0aec88e 2902424 debug optional 
gauche-gtk-dbgsym_0.6.1-1_amd64.deb
 c4a0c6699c8d692d4ab4cd48400ee903 12314 lisp optional 
gauche-gtk_0.6.1-1_amd64.buildinfo
 82bba005f4101d3d92df0f74e33694c2 843572 lisp optional 
gauche-gtk_0.6.1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQS3MhxVeHDZjYHXYQFkARSvid5gVAUCZDZFoQAKCRBkARSvid5g
VPWJAQC49nuNtJGN4GvbWRBfQmzCc5z5D1y66nD1Q9t0m8tqpQEAmvxxnK8Wxnn7
O9FKI7ZfdOZzFkXb0ICpkcYU9YaOaA4=
=DmiO
-END PGP SIGNATURE End Message ---

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#1034234: libpam-modules-bin: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Laurent Bigonville]

Le 11/04/23 à 19:53, Sam Hartman a écrit :

control: tags -1 wontfix


"bigon" == bigon   writes:

 bigon> It seems that your package libpam-modules-bin is shipping
 bigon> files (.service, .socket or .timer) in
 bigon> /usr/lib/systemd/system.

I think we're talking about pam_namespace.service.
I don't think dh_installsystemd has anything to do for that file because
it has no Install section.
What harm is caused by pam_namespace.service being in /usr/lib/systemd?
dh_installsystemd also takes care of calling systemctl daemon-reload 
when a new .service file is installed/removed, it also takes care that 
the service is stopped before removing the package (in this case it's a 
short living/oneshot service, but still)



 bigon> debhelper?  As soon as debhelper is supporting (not until
 bigon> bookworm+1 aka Trixie) you will be able to move them back to
 bigon> the newer location.

Um, no doing that before dpkg is fixed to deal with aliasing could
potentially be a really bad idea.
I'm not sure I understand, if all the files are at package level moved 
to /usr instead of / then aliasing in dpkg is not needed, isn't it?


Again, what harm is caused by pam_namespace.service being in
/usr/lib/systemd/system?
How is this a bug?

Processed: Regression is back

[Debian Bug Tracking System]

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

> reopen 1034160
Bug #1034160 {Done: Dmitry Shachnev } [libqt5gui5] 
libkscreenlocker5: Screen locker crashes asking for loginctl command
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions qtbase-opensource-src/5.15.8+dfsg-5.
> thanks
Stopping processing here.

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

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#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#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#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#1031364: marked as done (e2fsprogs: generates filesystems that grub-install doesn't recognize)

[Debian Bug Tracking System]

Your message dated Tue, 11 Apr 2023 18:36:15 +
with message-id 
and subject line Bug#1031364: fixed in vmdb2 0.27-1
has caused the Debian Bug report #1031364,
regarding e2fsprogs: generates filesystems that grub-install doesn't recognize
to be marked as done.

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

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


-- 
1031364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: e2fsprogs
Version: 1.47.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-b...@lists.debian.org, gr...@packages.debian.org

(Please keep debian-b...@lists.debian.org and gr...@packages.debian.org
in the loop.)

Hi,

Spotted via debian-installer tests: grub-install fails with “unknown
filesystem” when trying to run a simple `grub-install /dev/sda` with
an all-default installation.

While there might be something wrong about e2fsprogs-udeb specifically,
possibly only affecting the installer context, I'm not sure what that
means for existing systems, hence the severity.

The “e2fsprogs gets a new upstream release and new flags” hypothesis was
confirmed by building d-i with e2fsprogs-udeb_1.46.6-1_amd64.udeb
rebranded as 1.48, which made the problem disappear.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: vmdb2
Source-Version: 0.27-1
Done: Gunnar Wolf 

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

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

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

Debian distribution maintenance software
pp.
Gunnar Wolf  (supplier of updated vmdb2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Oct 2022 14:48:46 -
Source: vmdb2
Architecture: source
Version: 0.27-1
Distribution: unstable
Urgency: medium
Maintainer: Gunnar Wolf 
Changed-By: Gunnar Wolf 
Closes: 1031364
Changes:
 vmdb2 (0.27-1) unstable; urgency=medium
 .
   [ Gunnar Wolf ]
   * New upstream release
   * Specify ^large_dir, ^metadata_csum_seed parameters to e2fsprogs to fix
 the creation of unbootable systems when older GRUB versions are used
 (Closes: #1031364)
 .
   [ Debian Janitor ]
   * Bump debhelper from old 12 to 13.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
   * Update standards version to 4.6.1, no changes needed.
   * Set upstream metadata fields: Repository.
 .
   [ Gunnar Wolf ]
   * Drop 001_set_architecture_for_later_stages patch (no longer needed,
 incorporated upstream)
Checksums-Sha1:
 ccb0dc20c171f1f2c040bdc5edd5487624ff3882 1378 vmdb2_0.27-1.dsc
 257134c36a809f0ebf33c3cefd93fb6281851ebc 46856 vmdb2_0.27.orig.tar.xz
 1c86dc0183891a9166c726681ca93ab7ff5e2f48 4584 vmdb2_0.27-1.debian.tar.xz
 d8aaa69fa3b6c34454b093c75694b79cba134e45 8990 vmdb2_0.27-1_source.buildinfo
Checksums-Sha256:
 9f3c16a49fac0d4d754b68ef61a6dffadb38a02d972e2ed9bedb6f89db0a326e 1378 
vmdb2_0.27-1.dsc
 5b58c24ed0e4cad76134fd9010c1c538ea7c0c02d19d22bbeb61b1c3274ddfa8 46856 
vmdb2_0.27.orig.tar.xz
 be595e156368568363d740967132fe1cc39e2c4409441540555fd389a168f214 4584 
vmdb2_0.27-1.debian.tar.xz
 f8a299d531f1b261680b88c3225c9b4f45dd41ec803f5aabc52f72dda1a574ea 8990 
vmdb2_0.27-1_source.buildinfo
Files:
 6311f5c1200d7aeaf39246dc9d2397cc 1378 admin optional vmdb2_0.27-1.dsc
 7520655aff6052809c4f2c0ebae4a500 46856 admin optional vmdb2_0.27.orig.tar.xz
 8b2c4c8ff7ef238566718a5ad473c2c0 4584 admin optional vmdb2_0.27-1.debian.tar.xz
 b07fdd00703afeb1e594cbbd49f79f15 8990 admin optional 
vmdb2_0.27-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQRNFAUGU6QC1zaHBJ0kBMlUbhRTYAUCZDWjswAKCRAkBMlUbhRT
YBpsAQCKfMnYTqUjJMDrCPtYIQPnOi+2PkUJ+r8OQcCQyAaH6AD+PdXknSmu7ZBD
EGFo6Fmo+AFCTrsbmW7u0nv9+lnGrQ8=
=oi4Q
-END PGP SIGNATURE End Message ---

Bug#1034079: marked as done (wheel: fails to clean after successful build: rm: cannot remove './docs/_build': Is a directory)

[Debian Bug Tracking System]

Your message dated Tue, 11 Apr 2023 18:36:32 +
with message-id 
and subject line Bug#1034079: fixed in wheel 0.40.0-2
has caused the Debian Bug report #1034079,
regarding wheel: fails to clean after successful build: rm: cannot remove 
'./docs/_build': Is a directory
to be marked as done.

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

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


-- 
1034079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wheel
Version: 0.40.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

wheel/experimental fails to build twice in a row. Cleaning after a
successful build fails:

   dh_clean -O--buildsystem=pybuild
rm -f debian/debhelper-build-stamp
rm -rf debian/.debhelper/
rm -f debian/python3-wheel-whl.debhelper.log 
debian/python3-wheel.debhelper.log
rm -f -- debian/python3-wheel.substvars 
debian/python3-wheel.postinst.debhelper debian/python3-wheel.prerm.debhelper 
debian/python-wheel-common.substvars debian/python3-wheel-whl.substvars 
./docs/_build debian/files
rm: cannot remove './docs/_build': Is a directory
dh_clean: error: rm -f -- debian/python3-wheel.substvars 
debian/python3-wheel.postinst.debhelper debian/python3-wheel.prerm.debhelper 
debian/python-wheel-common.substvars debian/python3-wheel-whl.substvars 
./docs/_build debian/files returned exit code 1
make: *** [debian/rules:12: clean] Error 25

I haven't checked the source, but this looks like debian/clean is
missing a trailing / on the ./docs/_build entry.

This might affect the package in sid, too, but I havent checked that.


Andreas


wheel_0.40.0-1_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: wheel
Source-Version: 0.40.0-2
Done: Stefano Rivera 

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

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

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated wheel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 11 Apr 2023 14:11:59 -0400
Source: wheel
Architecture: source
Version: 0.40.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 1034079
Changes:
 wheel (0.40.0-2) experimental; urgency=medium
 .
   * Correctly clean. (Closes: #1034079)
Checksums-Sha1:
 7bc4dfc3ba2d449b43255dde5ffaa6bf052cdc69 1769 wheel_0.40.0-2.dsc
 9c0be98d620670a590fb953ddcbcf619b508e143 7452 wheel_0.40.0-2.debian.tar.xz
 85375e819e7d9f10addb37a781510ba93926cb2f 8407 wheel_0.40.0-2_source.buildinfo
Checksums-Sha256:
 70bbb7d919885698a2d29acf108d8cb2b3dbd6d48aa0dd3778a9e796b1abf9aa 1769 
wheel_0.40.0-2.dsc
 a482f61ea2187f070a5a00f043d8d4db6e35fb4ffc8c71a0e4c7c8ab9f7aa1c8 7452 
wheel_0.40.0-2.debian.tar.xz
 67f02e21facbcd87bee7915b8853d6493820c2abb0d5b584eded8fce032464ad 8407 
wheel_0.40.0-2_source.buildinfo
Files:
 7a80b9a495400d587f04eb6df154a33d 1769 python optional wheel_0.40.0-2.dsc
 d29124472de079b2ee32f0b225443571 7452 python optional 
wheel_0.40.0-2.debian.tar.xz
 b4f5d567ac84fa9409f4c684c3cfb532 8407 python optional 
wheel_0.40.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZDWjAhQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2AwmAQDzp/6Q8k5Tj4xhZTok8NxW+3m1iN9U
Crlt/m7w1yr92wD9GJRLNmKmng8MWdBri2MDx0ro5i4UVCW8PM3djnyzbAk=
=1nWa
-END PGP SIGNATURE End Message ---

Bug#1034079: marked as done (wheel: fails to clean after successful build: rm: cannot remove './docs/_build': Is a directory)

[Debian Bug Tracking System]

Your message dated Tue, 11 Apr 2023 18:36:24 +
with message-id 
and subject line Bug#1034079: fixed in wheel 0.38.4-2
has caused the Debian Bug report #1034079,
regarding wheel: fails to clean after successful build: rm: cannot remove 
'./docs/_build': Is a directory
to be marked as done.

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

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


-- 
1034079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wheel
Version: 0.40.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

wheel/experimental fails to build twice in a row. Cleaning after a
successful build fails:

   dh_clean -O--buildsystem=pybuild
rm -f debian/debhelper-build-stamp
rm -rf debian/.debhelper/
rm -f debian/python3-wheel-whl.debhelper.log 
debian/python3-wheel.debhelper.log
rm -f -- debian/python3-wheel.substvars 
debian/python3-wheel.postinst.debhelper debian/python3-wheel.prerm.debhelper 
debian/python-wheel-common.substvars debian/python3-wheel-whl.substvars 
./docs/_build debian/files
rm: cannot remove './docs/_build': Is a directory
dh_clean: error: rm -f -- debian/python3-wheel.substvars 
debian/python3-wheel.postinst.debhelper debian/python3-wheel.prerm.debhelper 
debian/python-wheel-common.substvars debian/python3-wheel-whl.substvars 
./docs/_build debian/files returned exit code 1
make: *** [debian/rules:12: clean] Error 25

I haven't checked the source, but this looks like debian/clean is
missing a trailing / on the ./docs/_build entry.

This might affect the package in sid, too, but I havent checked that.


Andreas


wheel_0.40.0-1_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: wheel
Source-Version: 0.38.4-2
Done: Stefano Rivera 

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

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

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated wheel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 11 Apr 2023 14:10:59 -0400
Source: wheel
Architecture: source
Version: 0.38.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 1034079
Changes:
 wheel (0.38.4-2) unstable; urgency=medium
 .
   * Correctly clean. (Closes: #1034079)
Checksums-Sha1:
 182919c0a23a536f3b074a30773a1a35f828b892 1750 wheel_0.38.4-2.dsc
 35fd28f1212b32e9dc4c9c6b9099fcf9ddc48ad8 7364 wheel_0.38.4-2.debian.tar.xz
 d0ef0289b81b2cd8ee10ba6b65219392596bf9cc 8191 wheel_0.38.4-2_source.buildinfo
Checksums-Sha256:
 dfaf5a3d2a558b32236a100f113b6a0be6cfb9ae044e53878bb9e95e73f8ee40 1750 
wheel_0.38.4-2.dsc
 d210a907e20551ee2bed0165937551695c2071275d2b542a36162fc656216513 7364 
wheel_0.38.4-2.debian.tar.xz
 3ca6556d17e001589d57eda0d6f466ac4179dc74ccf5da5b4fc3345907ebede8 8191 
wheel_0.38.4-2_source.buildinfo
Files:
 19e20b15ac3060af123be99a1ac925eb 1750 python optional wheel_0.38.4-2.dsc
 ea4c02e0b174591ce7ad8bd531e4dfcc 7364 python optional 
wheel_0.38.4-2.debian.tar.xz
 97975d8e49815fde650911779b11c7ca 8191 python optional 
wheel_0.38.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZDWizBQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2CzTAQDWbfZwJlsW+HxTzfpXhAqe7iPkqW1F
PRkswCo4QDCmzwEA54DF/PaPI+ISA/FxuElfo7nbjX0khoW4H7fiURhImQQ=
=1kJu
-END PGP SIGNATURE End Message ---

Processed: Bug#1034079 marked as pending in wheel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1034079 [src:wheel] wheel: fails to clean after successful build: rm: 
cannot remove './docs/_build': Is a directory
Ignoring request to alter tags of bug #1034079 to the same tags previously set

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

Processed: oops, duplicate

[Debian Bug Tracking System]

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

> # Sorry for the noise, I'm seeing too much issues lately and forgot to
> # check
> merge 1033147 1034257
Bug #1033147 [src:accountsservice] accountsservice: autopkgtest fails when 
using a bookworm kernel
Bug #1033147 [src:accountsservice] accountsservice: autopkgtest fails when 
using a bookworm kernel
Added tag(s) bookworm-ignore.
Bug #1034257 [src:accountsservice] accountsservice: autopkgtest regression: 
times out when run on bookworm kernel
Merged 1033147 1034257
> thanks
Stopping processing here.

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

Bug#1034079: marked as pending in wheel

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/wheel/-/commit/91490bb17bac824668a6124a924baa1a15bcd28d


Correctly clean. (Closes: #1034079)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1034079

Processed: Bug#1034079 marked as pending in wheel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1034079 [src:wheel] wheel: fails to clean after successful build: rm: 
cannot remove './docs/_build': Is a directory
Added tag(s) pending.

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

Bug#1034079: marked as pending in wheel

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/wheel/-/commit/06a0a4f1fa38f91a535104aac08e6f5f7b366414


Correctly clean. (Closes: #1034079)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1034079

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

Processed: accountsservice: autopkgtest regression: times out when run on bookworm kernel

[Debian Bug Tracking System]

Processing control commands:

> tags -1 bookworm-ignore
Bug #1034257 [src:accountsservice] accountsservice: autopkgtest regression: 
times out when run on bookworm kernel
Added tag(s) bookworm-ignore.

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

Bug#1034209: marked as done (pcscd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)

[Debian Bug Tracking System]

Your message dated Tue, 11 Apr 2023 18:04:09 +
with message-id 
and subject line Bug#1034209: fixed in pcsc-lite 1.9.9-2
has caused the Debian Bug report #1034209,
regarding pcscd: dh_installsystemd doesn't handle files in 
/usr/lib/systemd/system
to be marked as done.

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

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


-- 
1034209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pcscd
Version: 1.9.9-1   
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package pcscd 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u
--- End Message ---
--- Begin Message ---
Source: pcsc-lite
Source-Version: 1.9.9-2
Done: Ludovic Rousseau 

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

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

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

Debian distribution maintenance software
pp.
Ludovic Rousseau  (supplier of updated pcsc-lite package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 11 Apr 2023 19:15:00 +0200
Source: pcsc-lite
Architecture: source
Version: 1.9.9-2
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Rousseau 
Changed-By: Ludovic Rousseau 
Closes: 1034209
Changes:
 pcsc-lite (1.9.9-2) unstable; urgency=medium
 .
   * Fix "dh_installsystemd doesn't handle files in
 /usr/lib/systemd/system" (Closes: #1034209)
   * d/control: remove lsb-base dependency and fix lintian error
Checksums-Sha1:
 70ae117cf2b4a4489b191e0394e2fcc181e408a0 2333 pcsc-lite_1.9.9-2.dsc
 b65d221efc37c6c48aad0df175d125b1fb433b4e 19408 pcsc-lite_1.9.9-2.debian.tar.xz
 e30af2c229cfab90ecfad9d7de5c4e8d14046d38 7668 pcsc-lite_1.9.9-2_amd64.buildinfo
Checksums-Sha256:
 7f41763f994336ce4371b5a67fefda900c7f3e61b52e3acb77b3a70632869cba 2333 
pcsc-lite_1.9.9-2.dsc
 c2655a7e6caf14f7f29345ccc98b61db30f2eb4e6cdea9349f649673a0825eb3 19408 
pcsc-lite_1.9.9-2.debian.tar.xz
 8313ab9f3d9d531f9ec264fa2d70c7f7cc8f818fba8f7460c5366685e2cab91f 7668 
pcsc-lite_1.9.9-2_amd64.buildinfo
Files:
 dbb19daaccfe8e208f4ad829f8e29dfa 2333 misc optional pcsc-lite_1.9.9-2.dsc
 fa6d831cc08e240ee426aea3276569ae 19408 misc optional 
pcsc-lite_1.9.9-2.debian.tar.xz
 732a57691b0eab83b98dc2c2ac2fee1b 7668 misc optional 
pcsc-lite_1.9.9-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEE9eEbn/6REUb0HZU9eKG03+j5xX4FAmQ1nX4UHHJvdXNzZWF1
QGRlYmlhbi5vcmcACgkQeKG03+j5xX74tA//X6b1tQo0Hp87jf3BcjGWfKFIbgKU
Yp3QInJy62jLCwa7PzcYgFQZXsgVufMi88LHi7zPz6vi9m+uYAYgZAuNaCDfqQ/Z
gSPC1/gFZF4QO3vQ1IUJqSV7NW1lxTVX7Am6rDwxWSi7ukYCcs+jJgnBq4SmXNzO
gikPgpnEHTQVO9BMHrCTSP0vpcqvv67dns0qX2TbrEU9fSbA1iD5YYrxH1TGMDud
D7IDJJ7939fIQLyyJ1fz08WLWZWbt0pFEBv5GpWtphSyVKZnvYFKiUBBEWN/4BEC
iWKv7YrgqlBWZqS2G0TDIMGeLIM+HyN+sfatogVDZIPMMMHEawvSJnkOpyuNtINl
X4nxmknGniPDULd/FnC/E/+PZ2ineBhWCjT86AIbTf5H48CwBKBrGXhzXOQ0XJwL
0LKvNFnIWP5vJ1NG9cS71I+qe+akwoumZX/yZtrGh/ieA+vmym6lF8eiIHxh6AZo
Ss/3iLbZ4kHC5KEfIgNKf2R1FTRzUHn8A483K+Bq3lNS8GOnwUcK

Bug#1034090: marked as done (ibus: FTBFS twice in a row: src/ibusenumtypes.h is regenerated too late)

[Debian Bug Tracking System]

Your message dated Tue, 11 Apr 2023 18:03:59 +
with message-id 
and subject line Bug#1034090: fixed in ibus 1.5.28-4
has caused the Debian Bug report #1034090,
regarding ibus: FTBFS twice in a row: src/ibusenumtypes.h is regenerated too 
late
to be marked as done.

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

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


-- 
1034090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ibus
Version: 1.5.28-3
Severity: serious
Justification: fails to build twice in a row

Hi,

ibus/experimental fails to build twice in a row. (I haven't verified
whether the version in sid is also affected by this bug.)

The first build succeeds and a subsequent debian/rules clean removes
src/ibusenumtypes.h (and maybe other required files):

 debian/rules clean
dh clean --with gir,python3
   dh_auto_clean
make -j3 distclean
make[1]: Entering directory '/build/ibus-1.5.28'
Making distclean in src
make[2]: Entering directory '/build/ibus-1.5.28/src'
Making distclean in .
make[3]: Entering directory '/build/ibus-1.5.28/src'
test -z "IBus-1.0.gir IBus-1.0.typelib ibusmarshalers.c ibusmarshalers.h  
ibusenumtypes.c ibusenumtypes.h  ibusresources.c ibusresources.h   
ibus.gresources.xml stamp-ibusmarshalers.h stamp-ibusenumtypes.h " || rm -f 
IBus-1.0.gir IBus-1.0.typelib ibusmarshal
ers.c ibusmarshalers.h  ibusenumtypes.c ibusenumtypes.h  ibusresources.c 
ibusresources.h   ibus.gresources.xml stamp-ibusmarshalers.h 
stamp-ibusenumtypes.h
...

That file doesn't get regenerated before it is used during the second build, 
resulting in:

...
( top_builddir=`cd .. && pwd`; \
cd . && /usr/bin/glib-mkenums --template ibusenumtypes.c.template ibus.h 
ibusaccelgroup.h ibusattribute.h ibusattrlist.h ibusbus.h ibuscomponent.h 
ibusconfig.h ibusconfigservice.h ibusdebug.h ibusemoji.h ibusengine.h 
ibusenginedesc.h ibusenginesimple.h ibuse
rror.h ibusfactory.h ibushotkey.h ibusinputcontext.h ibuskeymap.h ibuskeys.h 
ibuskeysyms-compat.h ibuskeysyms.h ibuslookuptable.h ibusobject.h 
ibusobservedpath.h ibuspanelservice.h ibusproperty.h ibusproplist.h ibusproxy.h 
ibusregistry.h ibusserializable.h i
busservice.h ibusshare.h ibustext.h ibustypes.h ibusunicode.h ibusutil.h 
ibusxevent.h ibusxml.h  | \
sed 's/i_bus_/ibus_/g' | \
sed 's/I_TYPE_BUS_/IBUS_TYPE_/g') > \
ibusenumtypes.c.tmp && mv ibusenumtypes.c.tmp ibusenumtypes.c
( top_builddir=`cd .. && pwd`; \
cd . && /usr/bin/glib-mkenums --template ibusenumtypes.h.template ibus.h 
ibusaccelgroup.h ibusattribute.h ibusattrlist.h ibusbus.h ibuscomponent.h 
ibusconfig.h ibusconfigservice.h ibusdebug.h ibusemoji.h ibusengine.h 
ibusenginedesc.h ibusenginesimple.h ibuse
rror.h ibusfactory.h ibushotkey.h ibusinputcontext.h ibuskeymap.h ibuskeys.h 
ibuskeysyms-compat.h ibuskeysyms.h ibuslookuptable.h ibusobject.h 
ibusobservedpath.h ibuspanelservice.h ibusproperty.h ibusproplist.h ibusproxy.h 
ibusregistry.h ibusserializable.h i
busservice.h ibusshare.h ibustext.h ibustypes.h ibusunicode.h ibusutil.h 
ibusxevent.h ibusxml.h  | \
sed 's/i_bus_/ibus_/g' | \
sed 's/I_TYPE_BUS_/IBUS_TYPE_/g') > \
ibusenumtypes.h.tmp && mv ibusenumtypes.h.tmp ibusenumtypes.h
INFO: Reading ./ibusmarshalers.list...
sed -e "s|\@ENDIAN\@|little|g" \
ibus.gresources.xml.in > ibus.gresources.xml.tmp && \
mv ibus.gresources.xml.tmp ibus.gresources.xml
gcc -DHAVE_CONFIG_H -I. -I..  -DG_LOG_DOMAIN=\"IBUS\" -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/incl
ude -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gio-unix-2.0 
-pthread -DIBUS_CACHE_DIR=\""/var/cache/ibus"\" 
-DIBUS_DATA_DIR=\"/usr/share/ibus\" -DIBUS_DISABLE_DEPRECATION_WARNINGS 
-DIBUS_COMPILATION -DISOCODES_PREFIX=\"/usr\" -DX11_DATA_PREF
IX=\"/usr\"  -DENABLE_EMOJI_DICT -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/build/ibus-1.5.28=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -c -o 
gen_internal_compose_table-gencomposetable.o `test -f 'gencomposet
able.c' || echo './'`gencomposetable.c
In file included from ./ibusobject.h:41,
 from ./ibus.h:31,
 from gencomposetable.c:23:
./ibusdebug.h:49:31: warning: ISO C does not permit named variadic macros 
[-Wvariadic-macros]
   49 | #define ibus_warning(msg, args...) \
  |   ^~~
gcc -DHAVE_CONFIG_H -I. -I..  -DG_LOG_DOMAIN=\"IBUS\" -I/usr/include/glib-2.0 
-I/usr/lib

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 wontfix
Bug #1034234 [libpam-modules-bin] libpam-modules-bin: dh_installsystemd doesn't 
handle files in /usr/lib/systemd/system
Ignoring request to alter tags of bug #1034234 to the same tags previously set

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

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 wontfix
Bug #1034234 [libpam-modules-bin] libpam-modules-bin: dh_installsystemd doesn't 
handle files in /usr/lib/systemd/system
Added tag(s) wontfix.

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

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

[Sam Hartman]

control: tags -1 wontfix

> "bigon" == bigon   writes:

bigon> It seems that your package libpam-modules-bin is shipping
bigon> files (.service, .socket or .timer) in
bigon> /usr/lib/systemd/system.

I think we're talking about pam_namespace.service.
I don't think dh_installsystemd has anything to do for that file because
it has no Install section.
What harm is caused by pam_namespace.service being in /usr/lib/systemd?


bigon> debhelper?  As soon as debhelper is supporting (not until
bigon> bookworm+1 aka Trixie) you will be able to move them back to
bigon> the newer location.

Um, no doing that before dpkg is fixed to deal with aliasing could
potentially be a really bad idea.

Again, what harm is caused by pam_namespace.service being in
/usr/lib/systemd/system?
How is this a bug?

Processed: Bug#1034090 marked as pending in ibus

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1034090 [src:ibus] ibus: FTBFS twice in a row: src/ibusenumtypes.h is 
regenerated too late
Added tag(s) pending.

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

Bug#1034090: marked as pending in ibus

[Gunnar Hjalmarsson]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/ibus/-/commit/0a4196bbc3ad32530af989759116bc5d8b3f4b68


Make ibusenumtypes.h ready after clean

Closes: #1034090


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1034090

Processed: gpgsm: UI asks insane, unanswerable trust questions

[Debian Bug Tracking System]

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

> severity 888025 grave
Bug #888025 [gpgsm] gpgsm: UI asks insane, unanswerable trust questions
Ignoring request to change severity of Bug 888025 to the same value.
> thanks
Stopping processing here.

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

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#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#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#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#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#1034231: marked as done (freedombox: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)

[Debian Bug Tracking System]

Your message dated Tue, 11 Apr 2023 20:08:01 +0530
with message-id <92b0be53-1a09-14c8-2dc0-3a432443f...@medhas.org>
and subject line Re: Bug#1034231: freedombox: dh_installsystemd doesn't handle 
files in /usr/lib/systemd/system
has caused the Debian Bug report #1034231,
regarding freedombox: dh_installsystemd doesn't handle files in 
/usr/lib/systemd/system
to be marked as done.

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

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


-- 
1034231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freedombox
Version: 23.6  
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package freedombox 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u
--- End Message ---
--- Begin Message ---

On 11/04/23 19:01, Sunil Mohan Adapa wrote:
[...]


I will confirm that freedombox is working well as-is in bookworm and 
close this issue.




On a fresh Debian testing VM, I installed the freedombox package 
(currently version 23.6). As soon as the package was installed, I 
noticed that the freedombox daemon was running (due to plinth.service). 
I also found that start/stop scripts has been properly installed by 
dh_installsystemd in /var/lib/dpkg/info/freedombox.postinst.


Hence this bug does not apply to the freedombox package. Closing.

Thank you,

--
Sunil--- End Message ---

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#1034231: freedombox: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Sunil Mohan Adapa]

On 11/04/23 19:01, Sunil Mohan Adapa wrote:
[...]


I will confirm that freedombox is working well as-is in bookworm and 
close this issue.




On a fresh Debian testing VM, I installed the freedombox package 
(currently version 23.6). As soon as the package was installed, I 
noticed that the freedombox daemon was running (due to plinth.service). 
I also found that start/stop scripts has been properly installed by 
dh_installsystemd in /var/lib/dpkg/info/freedombox.postinst.


Hence this bug does not apply to the freedombox package. Closing.

Thank you,

--
Sunil

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#1034227: mpdscribble: 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: mpdscribble
> Version: 0.24-2
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package mpdscribble is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]

The problem seems to be basically the same as in
https://bugs.debian.org/1034236

When systemd.pc is not found, it falls back on hard-coded path in:
https://sources.debian.org/src/mpdscribble/0.24-2/systemd/system/meson.build/#L1-L4

As pkg-config is already part of build-deps, simply adding systemd (for
systemd.pc) should be enough to fix the problem.

Regards,
Andreas Henriksson

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

Processed: fixed version

[Debian Bug Tracking System]

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

> fixed 1027143 2.2.10.1+dfsg-1+deb11u1
Bug #1027143 [src:openimageio] openimageio: CVE-2022-36354 CVE-2022-38143 
CVE-2022-43592 CVE-2022-43593 CVE-2022-43594 CVE-2022-43595 CVE-2022-43596 
CVE-2022-43597 CVE-2022-43598 CVE-2022-43599 CVE-2022-43600 CVE-2022-43601 
CVE-2022-43602 CVE-2022-41639 CVE-2022-41649 CVE-2022-41684 CVE-2022-41794 
CVE-2022-41837 CVE-2022-41838 CVE-2022-41977 CVE-2022-41981 CVE-2022-41988
Marked as fixed in versions openimageio/2.2.10.1+dfsg-1+deb11u1.
>
End of message, stopping processing here.

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

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#1034231: freedombox: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Sunil Mohan Adapa]

Thank you for the bug report and bringing the issue to our attention.

On 11/04/23 13:07, bi...@debian.org wrote:

Package: freedombox
Version: 23.6
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package freedombox is shipping files (.service, .socket or
.timer) in /usr/lib/systemd/system.


We ship many systemd unit files. Only one of the unit files is a 
.service meant for freedombox itself. Others units are meant for other 
packages (most of them configuration extensions). These units must not 
be started/stopped when freedombox package is installed/uninstalled. 
Hence this issue applies only to a single unit: plinth.service.




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.


My understanding of the bug is that dh_installsystemd will not discover 
services listed in /usr/lib and this will not change for bookworm.


Long ago, when lintian was issuing a message about moving unit files 
from /lib to /usr/lib, we have moved the files. We also realized that 
the services were not being automatically started after installing the 
package. So, we implemented a workaround to keep the files in /usr/lib 
but force dh_installsystemd to discover plinth.service. The workaround 
reads like this:


override_dh_installsystemd:
# Do not enable or start any service other than FreedomBox service. Use
# of --tmpdir is a hack to workaround an issue with dh_installsystemd
# (as of debhelper 13.5.2) that still has hardcoded search path of
# /lib/systemd/system for searching systemd services. See #987989 and
# reversion of its changes.
	dh_installsystemd --tmpdir=debian/tmp/usr --package=freedombox 
plinth.service




With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.


I believe that the freedombox package does not need any changes for 
bookworm. Could you please confirm that there are no changes planned for 
dh_installsystemd that would make our workaround not work anymore?


I will confirm that freedombox is working well as-is in bookworm and 
close this issue.


[...]

Thank you for your contributions,

--
Sunil

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&literal=0&perpkg=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#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#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#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#1032990: marked as done (sssd-common" subids nsswitch.conf entry breaks user sub[ug]ids)

[Debian Bug Tracking System]

Your message dated Tue, 11 Apr 2023 12:49:13 +
with message-id 
and subject line Bug#1032990: fixed in sssd 2.8.2-4
has caused the Debian Bug report #1032990,
regarding sssd-common" subids nsswitch.conf entry breaks user sub[ug]ids
to be marked as done.

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

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


-- 
1032990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: podman
Version: 4.3.1.
System information:
Distributor ID: Debian
Description:Debian GNU/Linux bookworm/sid
Release:testing
Codename:   bookworm

Description: "podman unshare chown 1:1 ~/somefile" fails

Steps to reproduce:
1. touch ~/somefile
2. podman unshare chown 1:1 ~/somefile

Actual result:
chown: changing ownership of '/home/admin/somefile': Invalid argument

Expected result:
podman unshare runs successfully

Additional information:
$ id
uid=1002(admin) gid=1003(admin) groups=1003(admin),27(sudo)

$ cat /etc/subuid
debian:165536:65536
admin:10:65536

$ cat /etc/subgid
debian:165536:65536
admin:10:65536

strace:

touch ~/somefile; podman unshare strace -fvvs1024 chown 1:1 ~/somefile
execve("/usr/bin/chown", ["chown", "1:1", "/home/admin/somefile"],
["SHELL=/bin/bash", "SSH_AUTH_SOCK=/tmp/ssh-XX1LfLTb/agent.2335",
"SSH_AGENT_PID=2336", "PWD=/home/admin", "XDG_SESSION_TYPE=web",
"COCKPIT_REMOTE_PEER=:::172.27.0.2", "HOME=/home/admin",
"LANG=C.UTF-8",
"LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.avif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*."...,
"XDG_SESSION_CLASS=user", "TERM=xterm-256color", "USER=admin", "SHLVL=1",
"XDG_SESSION_ID=4", "XDG_RUNTIME_DIR=/run/user/1002",
"GSETTINGS_BACKEND=memory",
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1002/bus",
"_=/usr/bin/podman", "_CONTAINERS_ROOTLESS_UID=1002",
"_CONTAINERS_ROOTLESS_GID=1003", "XDG_CONFIG_HOME=/home/admin/.config",
"TMPDIR=/var/tmp", "_CONTAINERS_USERNS_CONFIGURED=done",
"CONTAINERS_GRAPHROOT=/home/admin/.local/share/containers/storage",
"CONTAINERS_RUNROOT=/run/user/1002/containers"]) = 0
brk(NULL)   = 0x562be050c000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f71192ff000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
newfstatat(3, "", {st_dev=makedev(0xfe, 0x1), st_ino=4564,
st_mode=S_IFREG|0644, st_nlink=1, st_uid=65534, st_gid=65534,
st_blksize=4096, st_blocks=112, st_size=54706, st_atime=1678811270 /*
2023-03-14T16:27:50.48000+ */, st_atime_nsec=48000,
st_mtime=1678724869 /* 2023-03-13T16:27:49.420145979+ */,
st_mtime_nsec=420145979, st_ctime=1678724869 /*
2023-03-13T16:27:49.420145979+ */, st_ctime_nsec=420145979},
AT_EMPTY_PATH) = 0
mmap(NULL, 54706, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f71192f1000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0Ps\2\0\0\0\0\0@
\0\0\0\0\0\0\0XD\35\0\0\0\0\0\0\0\0\0@\08\0\16\0@\0@\0?\0\6\0\0\0\4\0\0\0@
\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0\20\3\0\0\0\0\0\0\20\3\0\0\0\0\0\0\10\0\0\0\0\0\0\0\3\0\0\0\4\0\0\0\220\n\32\0\0\0\0\0\220\n\32\0\0\0\0\0\220\n\32\0\0\0\0\0\34\0\0\0\0\0\0\0\34\0\0\0\0\0\0\0\20\0\0\0\0\0\0\0\1\0\0\0\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\08S\2\0\0\0\0\08S\2\0\0\0\0\0\0\20\0\0\0\0\0\0\1\0\0\0\5\0\0\0\0`\2\0\0\0\0\0\0`\2\0\0\0\0\0\0`\2\0\0\0\0\0\274L\25\0\0\0\0\0\274L\25\0\0\0\0\0\0\20\0\0\0\0\0\0\1\0\0\0\4\0\0\0\0\260\27\0\0\0\0

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#1033933: marked as done (llvm-16-dev: cmake findpackage(LLVM) fails due to missing /usr/lib/llvm-16/lib/libomptarget.so.16)

[Debian Bug Tracking System]

Your message dated Tue, 11 Apr 2023 12:33:34 +
with message-id 
and subject line Bug#1033933: fixed in llvm-toolchain-16 1:16.0.1-1~exp2
has caused the Debian Bug report #1033933,
regarding llvm-16-dev: cmake findpackage(LLVM) fails due to missing 
/usr/lib/llvm-16/lib/libomptarget.so.16
to be marked as done.

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

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


-- 
1033933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: llvm-16-dev
Version: 1:16.0.0-1~exp5
Severity: serious

cmake llvm detection is broken due to missing dependencies:

The following minimal CMakeLists.txt

project(foo)
find_package(LLVM 16 REQUIRED)

fails with

CMake Error at /usr/lib/llvm-16/lib/cmake/llvm/LLVMExports.cmake:1809 (message):
  The imported target "omptarget" references the file

 "/usr/lib/llvm-16/lib/libomptarget.so.16"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/llvm-16/lib/cmake/llvm/LLVMExports.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/llvm-16/cmake/LLVMConfig.cmake:359 (include)
  CMakeLists.txt:2 (find_package)


-- Configuring incomplete, errors occurred!


This blocks the packaging of spirv-llvm-translator-16.


Andreas
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-16
Source-Version: 1:16.0.1-1~exp2
Done: Gianfranco Costamagna 

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

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

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
llvm-toolchain-16 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 11 Apr 2023 14:09:36 +0200
Source: llvm-toolchain-16
Built-For-Profiles: noudeb
Architecture: source
Version: 1:16.0.1-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Gianfranco Costamagna 
Closes: 1033933
Changes:
 llvm-toolchain-16 (1:16.0.1-1~exp2) experimental; urgency=medium
 .
   [ Sylvestre Ledru ]
   * cherry pick changes from snapshot for sccache
 .
   [ Gianfranco Costamagna ]
   * Use parallel=2 on riscv64
   * Add omptarget again to optional interfaces (Closes: #1033933)
   * Adapt test when llvm is built without Z3 support (error message changed)
Checksums-Sha1:
 192b8d46b6d2bcaf352b3bbff03ce53c04afc3e3 8155 
llvm-toolchain-16_16.0.1-1~exp2.dsc
 97284c850d6c4e7a003f88117bb14d415a66b14d 164308 
llvm-toolchain-16_16.0.1-1~exp2.debian.tar.xz
 d8dda24589eb28f35c86f688e3c5daecf73d169a 11686 
llvm-toolchain-16_16.0.1-1~exp2_source.buildinfo
Checksums-Sha256:
 054c6fe3f498c789b21b1856b7e4f437ed8b20d3d535112a62910f6988f8b623 8155 
llvm-toolchain-16_16.0.1-1~exp2.dsc
 bc6f2f1935aa2780c2010bad68ee3fa257c5b6ddc049ee09723bef4144386a85 164308 
llvm-toolchain-16_16.0.1-1~exp2.debian.tar.xz
 33a7eca911970efb8df1f65984a9aafc38519678024aa22b38fd642c5cdc8423 11686 
llvm-toolchain-16_16.0.1-1~exp2_source.buildinfo
Files:
 8d231836e09f1ea969109c2fbd574d45 8155 devel optional 
llvm-toolchain-16_16.0.1-1~exp2.dsc
 7bc639465302404295d02cb0f34c7a96 164308 devel optional 
llvm-toolchain-16_16.0.1-1~exp2.debian.tar.xz
 34a0b030fdb467f9e070580267ea6bcc 11686 devel optional 
llvm-toolchain-16_16.0.1-1~exp2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmQ1TnEACgkQ808JdE6f
XdlpmRAAq6vEw88gHvRgmnUn64/I4SKgDjphdzrCAOzBQQUfAwgZs76tt5U4aLTj
Y/4mtPX4zWJPFRwVJDggX7/ODI39WNo27a8ZkxESp4s7MNG53QAj/WxyfRZKcOkW
J/tp2RQyaNVCpLQPmSegE8zVMIGX9LhaQn/uoJvZNWbpcyFF58IfYPuYOiDEbedy
G4ox9Rp8163+E+XjFtZghpD8JOs/WXMieq02cLLm3Z8v9uv0iZVx7Krtm2IIxswA
J3oo5xlQSSq1n1gsW1XSzZTkHSKnTyAsfJkF3cWA1WvSrvUGevxTrFaxEQ3xFipM
7J70BvVEjl3C+MM1DZSAbl+HtO0Loo1tGg00tJPCkcj2qUIx+nz8W4E1rypND++X
8wqz5Ib4mBz1Nwr0Mj5DFm+BvaxMiSj1xjCgz1oJFqpahGXQ7lNvM6/eFA7uLCss
iDobpNNVkzlLrhS93RYlqNO/+E//gtVXM6171C2JYffH

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#1031439: marked as done (gcc-sh-elf: FTBFS: make[6]: *** No rule to make target '../libsframe/libsframe.la', needed by 'libbfd.la'. Stop.)

[Debian Bug Tracking System]

Your message dated Tue, 11 Apr 2023 10:34:05 +
with message-id 
and subject line Bug#1031439: fixed in gcc-sh-elf 4.1
has caused the Debian Bug report #1031439,
regarding gcc-sh-elf: FTBFS: make[6]: *** No rule to make target 
'../libsframe/libsframe.la', needed by 'libbfd.la'.  Stop.
to be marked as done.

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

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


-- 
1031439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-sh-elf
Version: 4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[6]: Entering directory '/<>/bld/bfd/po'
> make[6]: Nothing to be done for 'all'.
> make[6]: Leaving directory '/<>/bld/bfd/po'
> /bin/sh ./libtool --tag=CC --tag=disable-static  --mode=link 
> x86_64-linux-gnu-gcc -Wall -fcf-protection -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wc,-static-libgcc  -module -avoid-version -bindir /usr/libexec/gcc/sh-elf/12 
> -Wl,--version-script=../../src/lto-plugin/lto-plugin.map-Xcompiler 
> '-static-libstdc++' -Xcompiler '-static-libgcc' '-Wl,-z,relro' '-Wl,-z,now' 
> -o liblto_plugin.la -rpath /usr/libexec/gcc/sh-elf/12 lto-plugin.lo  
> -Wc,../libiberty/pic/libiberty.a 
> yes
> checking whether the compiler supports the __inline keyword... make[6]: 
> Entering directory '/<>/bld/bfd'
> rm -f bfd-tmp.h
> cp bfd-in3.h bfd-tmp.h
> /bin/sh ../../src/bfd/../move-if-change bfd-tmp.h bfd.h
> rm -f bfd-tmp.h
> touch stmp-bfd-h
> rm -f tofiles
> make[6]: *** No rule to make target '../libsframe/libsframe.la', needed by 
> 'libbfd.la'.  Stop.
> make[6]: *** Waiting for unfinished jobs
> f=""; \
> for i in elf32-sh.lo elf-vxworks.lo elf32.lo elf.lo elflink.lo elf-attrs.lo 
> elf-strtab.lo elf-eh-frame.lo elf-sframe.lo dwarf1.lo dwarf2.lo coff-sh.lo 
> cofflink.lo coffgen.lo elf32-gen.lo plugin.lo cpu-sh.lo  archive64.lo ; do \
>   case " $f " in \
> *" $i "*) ;; \
> *) f="$f $i" ;; \
>   esac ; \
> done ; \
> echo $f > tofiles
> /bin/sh ../../src/bfd/../move-if-change tofiles ofiles
> libtool: link: x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  .libs/lto-plugin.o  
>   -static-libgcc -Wl,--version-script=../../src/lto-plugin/lto-plugin.map 
> -static-libstdc++ -static-libgcc -Wl,-z -Wl,relro -Wl,-z -Wl,now 
> ../libiberty/pic/libiberty.a   -Wl,-soname -Wl,liblto_plugin.so -o 
> .libs/liblto_plugin.so
> touch stamp-ofiles
> rm -f libcpp.a
> make[6]: Leaving directory '/<>/bld/bfd'
> x86_64-linux-gnu-ar cru libcpp.a charset.o directives.o errors.o expr.o 
> files.o identifiers.o init.o lex.o line-map.o macro.o mkdeps.o pch.o symtab.o 
> traditional.o
> make[5]: *** [Makefile:1955: all-recursive] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/gcc-sh-elf_4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230216&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: gcc-sh-elf
Source-Version: 4.1
Done: John Scott 

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

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

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

Debian distribution maintenance software
pp.
John Scott  (supplier of updated gcc-sh-elf package)

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


-BEGIN PGP SIGNED MESSA

Processed: Re: Bug#1034222: tirex: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1034222 [tirex] tirex: dh_installsystemd doesn't handle files in 
/usr/lib/systemd/system
Added tag(s) pending.

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

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

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 4/11/23 09:37, bi...@debian.org wrote:

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.


This has been fixed in git.

Due to ongoing work in git, there were already a few unreleased changes 
which we'd rather not revert unless the RMs demand it.


Kind Regards,

Bas

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

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

Processed: reassign 1034225 to nvme-stas ..., tagging 1034225

[Debian Bug Tracking System]

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

> reassign 1034225 nvme-stas 2.2.1-1
Bug #1034225 [nvme-staspass-extension-tomb] nvme-staspass-extension-tomb: 
dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Warning: Unknown package 'nvme-staspass-extension-tomb'
Bug reassigned from package 'nvme-staspass-extension-tomb' to 'nvme-stas'.
No longer marked as found in versions 1.3-2.
Ignoring request to alter fixed versions of bug #1034225 to the same values 
previously set
Bug #1034225 [nvme-stas] nvme-staspass-extension-tomb: dh_installsystemd 
doesn't handle files in /usr/lib/systemd/system
Marked as found in versions nvme-stas/2.2.1-1.
> retitle 1034225 nvme-stas: dh_installsystemd doesn't handle files in 
> /usr/lib/systemd/system
Bug #1034225 [nvme-stas] nvme-staspass-extension-tomb: dh_installsystemd 
doesn't handle files in /usr/lib/systemd/system
Changed Bug title to 'nvme-stas: dh_installsystemd doesn't handle files in 
/usr/lib/systemd/system' from 'nvme-staspass-extension-tomb: dh_installsystemd 
doesn't handle files in /usr/lib/systemd/system'.
> tags 1034225 - bookworm
Bug #1034225 [nvme-stas] nvme-stas: dh_installsystemd doesn't handle files in 
/usr/lib/systemd/system
Removed tag(s) bookworm.
> thanks
Stopping processing here.

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

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

Bug#1034235: ceph-iscsi: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[bigon]

Package: ceph-iscsi
Version: 3.5-2 
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package ceph-iscsi 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

Package: freedombox
Version: 23.6  
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package freedombox 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

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.

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

Package: mpdscribble
Version: 0.24-2
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package mpdscribble 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

Bug#1034225: nvme-staspass-extension-tomb: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[bigon]

Package: nvme-staspass-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 nvme-staspass-extension-tomb 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

Package: pvpgn
Version: 1.8.5-3   
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package pvpgn 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

Package: tirex
Version: 0.7.0-2
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package tirex 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

Bug#1034220: shadowsocks-libev: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[bigon]

Package: shadowsocks-libev
Version: 3.3.5+ds-9
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package shadowsocks-libev 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

Package: debomatic
Version: 0.26-1
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package debomatic 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

Bug#1034217: qbittorrent-nox: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[bigon]

Package: qbittorrent-nox
Version: 4.5.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 qbittorrent-nox 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

Package: cfengine3
Version: 3.21.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 cfengine3 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

Bug#1034216: boinc-client: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[bigon]

Package: boinc-client
Version: 7.20.5+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 boinc-client 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

Package: drkonqi
Version: 5.27.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 drkonqi 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

Bug#1034214: tcmu-runner: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[bigon]

Package: tcmu-runner
Version: 1.5.4-4   
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package tcmu-runner 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

Bug#1034213: arno-iptables-firewall: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[bigon]

Package: arno-iptables-firewall
Version: 2.1.1-7   
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package arno-iptables-firewall 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

Bug#1034212: amazon-ec2-net-utils: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[bigon]

Package: amazon-ec2-net-utils
Version: 2.3.0-2   
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package amazon-ec2-net-utils 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

Package: booth
Version: 1.0-283-g9d4029a-1 
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package booth 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

Bug#1034210: python3-charon: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[bigon]

Package: python3-charon
Version: 4.13.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 python3-charon 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u

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

[bigon]

Package: pcscd
Version: 1.9.9-1   
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package pcscd 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.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u