DA, OpenLDAP 2.1, Debian
Guido Trotter <[email protected]>
| Newsgroups | gmane.network.directoryadmin |
|---|---|
| Message-ID | <[email protected]> |
Hi, I'm sending this mail from the point of view of the Debian maintainer of Directory Administrator. Currently DA has its last version (1.5.1) both in Debian unstable (sid) and in Debian Testing (sarge), while packages for woody are kindly provided and maintained by Christof Meerwald. This situation makes sense: woody is quite different (from a debian policy point of view) from sid/sarge and probably backporting the current source would require backporting at least debhelper, if not something else. Anyway, as we all know, DA 1.5.1 is incompatible with OpenLDAP 2.1 (which is also in testing), unless one throws away the schemacheck feature. (Not a nice thing). This, for debian, is not of great impact: I expect that most users will use an unstable workstation to manage a server which runs woody, or a woody workstation with unofficial .debs to manage a server with the woody version of OpenLDAP installed. This is going to change quite soon: our beloved release manager has posted an article (http://lists.debian.org/debian-devel-announce-0308/msg00010.html) in which he states that the project is aiming its next release for December, the 1st (one year and a half after the release of woody). Since from that moment on OpenLDAP 2.1 will be the default one, as shipped by Debian, and also most debian users will have whatever version of DA Debian stable will ship, I'm writing here to ask what the release plans for the next DA are. Reading the article it seems that this september will be the last chance to upload a new version of DA and make it go into sarge: do you think it will be possible to do this, somehow, and so to ship Debian sarge with a version of DA compatible with it's version of OpenLDAP, and maybe also with its samba (which is currently 3.0.0beta2-1)? After the stable release we can obviously keep the current pratice of maintaining an updated version in unstable/testing, and a backport for stable, but since it won't have the same visibility I think that releasing a good version with sarge may be a good goal. Thanks, Guido
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/TG5uhImxTYgHUpsRAuNzAJ9XMYkwyZS4LJWhOS8C6/GSCJRs8QCdF9Zh UXEoR545hhsQndOShPUPG2A= =k5mB -----END PGP SIGNATURE-----