conflict on syslog.service when moving between rsyslog and busybox-syslogd
Bug #2026292 reported by
Dan Bungert
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) |
Won't Fix
|
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/
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/
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 | #1 |
Revision history for this message
| Dan Bungert (dbungert) wrote | #2 |
| Changed in busybox (Ubuntu): | |
| status: | New → Won't Fix |
| Changed in rsyslog (Ubuntu): | |
| status: | New → Won't Fix |
| Changed in systemd (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| Nick Rosbrook (enr0n) wrote | #3 |
| Changed in systemd (Ubuntu): | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
This script is a reproducer, assuming it installs the affected busybox-syslogd. Debian sid (systemd 253) passes.