Upstream bug in log4cpp

[Russ Allbery]

"Cantor, Scott" <cantor.2 at osu.edu> writes:

> I think Scott Koranda was going to file this, but in case there's any
> confusion, he identified a bug that I believe I patched in my log4shib
> fork, but hasn't been fixed in log4cpp, which Debian's Shibboleth SP
> packages rely on.

Thanks for the heads up.

I have to admit that given the lack of anything at all happening with the
log4cpp packages (and, apparently, with upstream), I'm increasingly
tempted to just package log4shib and switch all the Shibboleth packages
over to it.  I'm sure that would make you more comfortable as well.

I should probably bring that up in debian-devel first because of the code
duplication.  I'm sure someone will ask if there's any way of merging the
projects; I assume that's pretty much at the same spot it was several
years ago, where they seemed basically uninterested in the issues you were
raising?

(Given the lack of a new release, I wonder if log4cpp is really
effectively orphaned.)

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>