conflict on syslog.service when moving between rsyslog and busybox-syslogd

Bug #2026292 reported by Dan Bungert
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
busybox (Ubuntu)
Won't Fix
Undecided
Unassigned
rsyslog (Ubuntu)
Won't Fix
Undecided
Unassigned
systemd (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Suppose a system with systemd 252 and rsyslog installed. Install busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to be removed (but not purged). The install of busybox-syslogd will fail as follows:

Failed to preset unit, file "/etc/systemd/system/syslog.service" already exists and is a symlink to "/lib/systemd/system/rsyslog.service".

The failure can also be seen in the reverse direction - busybox-syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog.

With systemd 253, we instead see:
Removed "/etc/systemd/system/syslog.service".

Workarounds:
* use systemd 253 when available
* purge the existing system-log-daemon before installing the new one

Revision history for this message
Dan Bungert (dbungert) wrote :
Revision history for this message
Dan Bungert (dbungert) wrote :

This script is a reproducer, assuming it installs the affected busybox-syslogd. Debian sid (systemd 253) passes.

Dan Bungert (dbungert)
Changed in busybox (Ubuntu):
status: New → Won't Fix
Changed in rsyslog (Ubuntu):
status: New → Won't Fix
Nick Rosbrook (enr0n)
Changed in systemd (Ubuntu):
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.