Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #342168

Bug#1036022: altos,lprint: undeclared file conflict on /usr/lib/x86_64-linux-gnu/systemd/system

Show all headers | View raw

Package: altos,lprint
Severity: serious
X-Debbugs-Cc: anbe@debian.org

Hi,

while Andreas usually files bugs about file conflicts, his tooling seems
to have missed this one. It's quite special. While altos ships
/usr/lib/x86_64-linux-gnu/systemd/system as a directory containing a
systemd unit, lprint ships this location as a regular file containing a
systemd unit. So this is a case of a directory versus regular file
conflict and it is the only instance in the archive. Trying to unpack
both results in an error from dpkg, e.g.:

| Unpacking altos (1.9.16-1) ...
| dpkg: error processing archive /tmp/apt-dpkg-install-buVwGL/106-altos_1.9.16-1_amd64.deb (--unpack):
|  trying to overwrite '/usr/lib/x86_64-linux-gnu/systemd/system', which is also in package lprint 1.1.0-2
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Quite evidently, this is wrong on multiple levels. systemd does not
search multiarch paths for service units and the way lprint packages up
its service file is just plain wrong. I think both altos and lprint need
to be fixed to properly place their unit files.

Helmut

Back to linux.debian.bugs.rc | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Bug#1036022: altos,lprint: undeclared file conflict on /usr/lib/x86_64-linux-gnu/systemd/system Helmut Grohne <helmut@subdivi.de> - 2023-05-13 11:30 +0200
  Bug#1036022: marked as done (altos,lprint: undeclared file  conflict on /usr/lib/x86_64-linux-gnu/systemd/system) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-05-14 21:00 +0200
  Bug#1036022: marked as done (altos,lprint: undeclared file  conflict on /usr/lib/x86_64-linux-gnu/systemd/system) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-05-23 00:40 +0200

csiph-web