New cyrus-sasl2 packages

Gerfried Fuchs alfie at ist.org
Tue Oct 17 11:27:24 UTC 2006


* "Roberto C. Sanchez" <roberto at connexer.com> [2006-10-17 06:56]:
> On Tue, Oct 17, 2006 at 10:52:08AM +0200, Gerfried Fuchs wrote:
>> * "Roberto C. Sanchez" <roberto at connexer.com> [2006-10-16 01:18]:
>> > Mail-Followup-To: ...
>>  quite helfpul, if you ask me. :)  I'm not sure if you wanted that, but
>> I'm following your wish.
>> 
> I'm cutting down the addresses to which this reply goes :-)

 Could you pretty please remove the challenge handling of the list?
Maintainer addresses for packages have to be reachable directly, and the
list address is used in the Maintainer field of the packages.  Besides
that is slows down the throughput of bugreports and the likes, it also
works quite effectively against the meaning of a team - that is, that
everyone in the team can help with reports and such, because they don't
even see it right ahead.

> You bring up a good point.  However, I'd like to point out that the fact
> that a feature is disabled in SASL (namely LDAP support)

 Was that done with a library version change?  Because this sounds like
a highly incompatible change to me.  Is this disabling discussed with
upstream and do they know that you need to change the libarary
versioning?

> and ends up cause *unrelated* breakage in etpan-ng and libetpan, means
> that there is in fact some sort of latent bug in those packages.

 Are you sure that it is indeed unrelated?  From what I've read on some
archive is that it was forgotten to add versioned symbols _at all_ in
sasl.  Did you try your test builds with those, or not?

> If you like, you are free to lower the severity of the bugs.

 As you can see, it is closed already by the release team, because it's
neither a bug within the Debian system, nor does it seem to be a bug
with a considering stable package (you said yourself that you still are
working on it), nor am I at all convinced that the problem lies within
etpan-ng.

> However, the fact that there exists a not-so-exotic circumstance under
> which those packages fail to build means that furher investigation
> should conducted.

 Feel free, but still I don't think it's in the etpan code, sorry.  Is
etpan-ng the only package which seemingly has problems with those
changes?  From what I've read I doubt that - so it is quite an
interesting approach to seek the reason for the breakage in other places
than the library itself.  If it's changed in an incompatible way it
should be tagged as such.  Are you sure you only disabled the ldap
support and changed nothing else?

 So long,
Alfie
-- 
<jstr> Streu ruhig weiter Saly in meine Wunden (Drecks-Kezboard).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20061017/3f919370/attachment-0001.pgp


More information about the Pkg-cyrus-sasl2-debian-devel mailing list