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 was serious. > > Rainer, were you already able to nail down these issues and how far away is > the > 4.4.1 release? Quick answer: I feel much better about 4.4.x right now. I will probably release 4.4.1 today. In Depth: the segfault is not yet found, but it turns out that it was present in 4.2.0 as well. Also, only one person reported it so far and only on one of his (many) systems, this bug seems to be very related to the environment. I think this is especially true as 4.2.0 was in far more widespread use and as such I should have heard about the bug earlier/from more people if it would be likely to occur. So I conclude it is OK (though not optimal) to do a new release with this bug. I am still fighting with it. My next step is to try isolate a version where it was not present (I somewhat think it may even be present in v3 as well). To the rest of 4.4.x release, I made a mistake when I handled the beta. I moved the beta branch to quickly to a new release, without doing a stable in between. I thought I had sorted this problem out, but when I made the 4.3.2 beta stable, I obviously missed backporting some bug fixes that were present in the "newer betas". I think all of them have now been found and sorted out. There still is a chance that I may be wrong, but git log review plus absence of any more bug reports makes me think I am right. So, all in all, it probably is a good time to do a 4.4.1 release. Rainer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
