On Tue, 2009-09-01 at 23:48 +0200, Michael Biebl wrote:
Andreas Barth wrote:
Rainer asked me, to block rsyslog 4.4.0 as it apparently also had other issues
(iirc there was also a segfault during udp reception, but Rainer knows the
details), so it was not this specific bug report which alone
Quick answer: I feel much better about 4.4.x right now. I will probably
release 4.4.1 today.
FYI: 4.4.1 has been released: http://www.rsyslog.com/Article399.phtml
Rainer
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
* Michael Biebl (bi...@debian.org) [090901 20:58]:
Rainer Gerhards wrote:
On a client-server configuration, since my upgrading to the last unstable
version (on the client, the server is from stable),
i started to get warnings with logcheck like this :
Aug 25 15:09:01 86Aug 25 15:09:01
Andreas Barth wrote:
* Michael Biebl (bi...@debian.org) [090901 20:58]:
This is a rather important regression, so I'm raising the severity to
serious,
to ensure that 4.4.0-1 does not enter testing (as 4.4.0 seems to have a few
more
other issues, so it's better to block it)
Can you
* Michael Biebl (bi...@debian.org) [090902 00:04]:
Otherwise I'd just downgrade this bug report to important again, to not block
the mysql transition and will upload 4.4.1 asap when it's released.
It isn't necessary to downgrade the bug - I can always decide to
ignore it during this specific
Processing commands for cont...@bugs.debian.org:
severity 543505 serious
Bug #543505 [rsyslog] rsyslog: Wrong priority format for remote action
Severity set to 'serious' from 'important'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
6 matches
Mail list logo
