I guess this only applied to Lunar? Which is EOL. So, marking this won't
fix, but correct me if I am wrong.

** Changed in: systemd (Ubuntu)
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/2026292

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

Status in busybox package in Ubuntu:
  Won't Fix
Status in rsyslog package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2026292/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to