On 19.03.2013 12:58, intrigeri wrote: > Control: tag -1 + moreinfo > > Hi, > > Michael Biebl wrote (05 Mar 2013 23:16:56 GMT) : >> It has a one-line fix to future-proof rsyslog's systemd service file to >> work with newer systemd versions. > >> +rsyslog (5.8.11-3) unstable; urgency=low >> + >> + * debian/patches/04-systemd_journal.patch: The journal has replaced >> + systemd-kmsg-syslogd and systemd-stdout-bridge. Stopping a non-existing >> + service will generate an error in newer versions of systemd, so remove >> + that from ExecStartPre. >> + >> + -- Michael Biebl <biebl@debian.org> Tue, 05 Mar 2013 23:06:57 +0100 > > I confirm the systemd-kmsg-syslogd service does not exist on my Wheezy > system, so that ExecStartPre is indeed useless. > > I'm inclined to recommend the release team to allow this trivial > change to go in Wheezy, but I'd like to be pointed to an actual > example (future) problem this change would solve. > > So, Michael, what's the actual potential harm, in practice, of keeping > the useless ExecStartPre? More complicated upgrade path to Jessie? > Running Wheezy + a newer systemd? Anything else? right, backports are one issue, partial upgrades another. With the ExecStartPre, the rsyslog service will fail to start with newer systemd versions. While we could add Breaks to systemd, having a fixed package already in wheezy sounds like the better alternative to me. Breaks seem to have the tendency to confuse APT, so if they can be avoided, it seems worthwile to me to include this fix. FWIW, I've notified the syslog-ng maintainer and hope we'll get the same fix for syslog-ng into wheezy. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Attachment:
signature.asc
Description: OpenPGP digital signature