Kurt Roeckx <[EMAIL PROTECTED]> writes: > I'm a little confused about the status of bug #434645. As far as I can > see it's not a bug in bug in libapache2-mod-shib, and the problem is in > liblog4cpp4 (#432729)
> But the bug is marked "etch", meaning that only the version in etch has > the problem, which I think just isn't right. I think the etch tag is > wrong and should be removed. This looks like a bug you just want to > keep around until #432729 is fixed. > I also have to wonder why #432729 is just set to important, since it > breaks other packages. Yeah, this is all very confusing and I don't know how to represent it in the BTS. Shibboleth uses log4cpp in a threaded environment and appears to be about the only application that does so, at least in this intensive of a way. So log4cpp's thread-safe problems mostly only affect Shibboleth, so I'm not sure if it's kosher to mark the log4cpp bug grave. However, this problem makes Shibboleth largely unusable under load, so for Shibboleth this is a serious bug. The problems in log4cpp are also present in etch, so ideally the patch provided in the log4cpp bug should also be applied to the version in etch in a stable update. I'm not at all sure how to use the BTS properly to represent all of this, so I'm quite happy to follow your preferences. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
