Ubuntu

Please merge rsyslog 5.8.0-1 (main) from debian unstable (main)

Reported by Lorenzo De Liso on 2011-05-02
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
rsyslog (Ubuntu)
Wishlist
Martin Pitt

Bug Description

Binary package hint: rsyslog

Please merge rsyslog 5.8.0-1 (main) from debian unstable (main).

Lorenzo De Liso (blackz) wrote :
Changed in rsyslog (Ubuntu):
importance: Undecided → Wishlist
Colin Watson (cjwatson) wrote :

diff -Nru rsyslog-5.8.0/debian/rules rsyslog-5.8.0/debian/rules
--- rsyslog-5.8.0/debian/rules 2011-04-12 14:35:18.000000000 +0200
+++ rsyslog-5.8.0/debian/rules 2011-05-02 17:57:38.000000000 +0200
@@ -30,4 +30,4 @@
        dh_compress -X rsyslog-example.conf

 override_dh_installinit:
- dh_installinit -R -- start 10 2 3 4 5 . start 30 0 6 . stop 90 1 .
+ dh_installinit --upstart-only --name=dmesg --no-start

This causes debian/rsyslog.upstart to no longer be installed, which will break everyone's logging, as far as I can see. At the very least, if this change is intentional, it needs to be explicitly documented - but it looks like a mistake.

Although I'm happy to review patches either way, you might find it easier to avoid making this kind of mistake if you did the merge in bzr?

+ - Patch the upstart job to parse /etc/default/rsyslog as the old init
+ script used to

Since the entire upstart job is one of the "remaining changes" in Ubuntu, there's no need to separately list changes to it. The entry "Replace init script with debian/rsyslog.upstart" is enough.

Changed in rsyslog (Ubuntu):
status: New → Incomplete
Lorenzo De Liso (blackz) wrote :

This attached debdiff fixes the issues you pointed out. Yes, sorry it was a mistake. I generally don't use bzr to merge packages and I prefer the debdiff for the merges.

Changed in rsyslog (Ubuntu):
status: Incomplete → New
Martin Pitt (pitti) wrote :

As I am the default assignee for the merge, I didn't check for bug reports about it. I already have merged it (in fact the diff looks pretty much like your's). I didn't upload it yet because 5.8.0 keeps spamming syslog with

May 4 15:41:28 donald rsyslogd: rsyslogd's groupid changed to 103
May 4 15:41:28 donald rsyslogd: rsyslogd's userid changed to 101
May 4 15:41:28 donald rsyslogd-2039: Could no open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]

over and over again, with pretty much every "real" message that comes in. Do you have the same problem when running this?

Changed in rsyslog (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
status: New → In Progress
Lorenzo De Liso (blackz) wrote :

Hello Martin,

Sorry for the late answer (I already answered you on IRC, though). By the way, I was not having this problem, but now I'm having it as well.

Lorenzo De Liso (blackz) wrote :

err, s/answered/contacted

Clint Byrum (clint-fewbar) wrote :

You both seem to be experiencing bug #459730 . Its possible the new version more readily introduces the problem. I think the appropriate answer is to fix that bug first, then update this merge to include whatever the fix is.

Martin Pitt (pitti) wrote :

So while the old rsyslog just ignored that, the new one seems to refuse operation without it and only logs about /dev/xconsole, and nothing else. Is that a sensible behaviour in the first place?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers