On Sun, Apr 15, 2007 at 11:03:05AM -0700, Russ Allbery wrote: > Steve Langasek <[EMAIL PROTECTED]> writes:
> > On Fri, Apr 13, 2007 at 09:17:09AM -0700, Russ Allbery wrote: > >> Could you schedule a binNMU for libauthen-sasl-cyrus-perl to pick up the > >> new Cyrus SASL libraries? > > Which new SASL libraries are those? From what I see, cyrus-sasl2 hasn't > > revved since the etch freeze. > Those ones. It looks like libauthen-sasl-cyrus-perl shipped in etch > linked against the libraries in oldlibs because I wasn't paying close > enough attention. Ok. What's the consequence of this for the package? I.e., is this just that there's a dep on libsasl2 instead of on libsasl2-2, or are there differences in the functionality of libauthen-sasl-cyrus-perl because of having built for an old version? (If the latter, there may be other packages in need of a rebuild; if the former, I'm not sure if it's even worth a rebuild at all just for this?) > I'm not sure if it's also worth rebuilding it in stable for the next > stable point release. (Not sure what the policy is on that.) Depends on the answers to the above, I imagine. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
