[Pkg-cyrus-sasl2-debian-devel] New upstream version

[Fabian Fagerholm]

On Mon, 2006-05-29 at 11:14 -0300, Henrique de Moraes Holschuh wrote: 
> On Sat, 27 May 2006, Roberto C. Sanchez wrote:
> > Before we start trying to tackle the bugs, are we going to start of by
> > updating the packages to the latest upstream release?
> 
> Yes, please.  It should fix an extreme host of issues...  And we finally
> will have proper ldap auxprop...

...once we have weeded out the new bugs and the build issues with
OpenLDAP... ;-)

Anyway, I just committed what I have so far picked out of my testing
work into the SVN repository [0]. It's far from done though, it's not
nearly usable for anything yet. I have more coming, such as making sure
the right files are in the right packages... :P

However, it should give a feel for where we're going. See the threads
from last year and the start of this year ([1], [2]) where I made an
outline of how I'd like the package to look. You will immediately notice
the name changes which we agreed on before, and in addition I plan to
also change the modules packages split somewhat. The -gssapi-heimdal
package is erroneously named at the moment, because it's actually MIT
Kerberos5 that is getting built and krb4 is not.

At this moment it's mostly boring and tedious work, getting the package
foundation in shape, but I'd like to have a solid foundation to stand on
before we start tackling the easier things such as tweaking the
build-deps (for example the libdb thing below) reautotoolizing and the
very hard things such as finding and correcting bugs in the code. Plus
integrating the changes that we want to carry over from the old package.

Also note that the package is dpatch-enabled, so that's the way to make
Debian-specific changes, not by committing changes to the upstream
source.

One last thing: don't wish too much for this package to get into etch.
We can't expect the rdeps to rebuild and shake out all the resulting
bugs with the current release schedule. Better make a good job and
prepare for a libsasl2 transition post-etch.

> One question, though: which BDB version to use?  Did upstream update the
> code to 4.4 already and stated it is officially supported (by adding it to
> the autoconf stuff?)

AFAIK, they didn't update it yet. I've run it with 4.2 although 4.1 is
the latest that upstream has stated that the code is updated for.
However, I don't think we should rely on upstream here. We need to work
with the libdb maintainers to find something that is stable in the
Debian universe, and then sync with that, pushing the fixes upstream.


[0] svn.debian.org/svn/pkg-cyrus-sasl2
[1] http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/2005-December/000000.html
[2] http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/2006-January/000010.html

-- 
Fabian Fagerholm <fabbe at paniq.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20060529/c1d58c55/attachment.pgp