On Tue, 2012-07-24 at 15:39 +0200, Michal Čihař wrote: > It seems that xcache 2.0.0 which is currently in testing/unstable is > quite buggy. On Debian side, we "only" have bug#682666,
The fix for that appears to be http://xcache.lighttpd.net/changeset/900 , which is really small. > but > there seem to be more segmentation faults fixed by new upstream > version (see changelog [1]). From reading through the upstream tickets and ignoring the bits that appear to be Windows specific, it looks like the segfault fixes are http://xcache.lighttpd.net/changeset/960 and http://xcache.lighttpd.net/changeset/903 - is that correct? If not, please point out what I missed. > I've looked at the changes and some of bug fixes introduce quite big > changes to code so it's hard to create reasonably sized patch to fix > these issues. And in the end the patches would be about size of diff > between 2.0.0 and 2.0.1 (~3.7k lines). That's far larger than the above, which either means I missed something or most that diff isn't needed to fix the segfaults. > [1]: http://xcache.lighttpd.net/browser/tags/2.0.1/ChangeLog Regards, Adam -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
