Accepted fox1.4 1.4.31-1 (source i386 all)

2006-03-20 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 10:56:59 +0100 Source: fox1.4 Binary: libfox1.4-doc libfox1.4-dev libfox1.4 Architecture: source i386 all Version: 1.4.31-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted swig1.3 1.3.28-1 (source all i386)

2006-02-28 Thread Torsten Landschoff
Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: swig - Generate scripting interfaces to C/C++ code swig-doc - HTML documentation for SWIG swig-examples - Examples for applications of SWIG swig1.3- Generate scripting interfaces to C/C++ code

Accepted swig1.3 1.3.27-2 (source all i386)

2006-02-03 Thread Torsten Landschoff
Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: swig - Generate scripting interfaces to C/C++ code swig-doc - HTML documentation for SWIG swig-examples - Examples for applications of SWIG swig1.3- Generate scripting interfaces to C/C++ code

Re: Need for launchpad

2006-01-08 Thread Torsten Landschoff
Hi Stephan, On Sun, Jan 08, 2006 at 11:25:28AM +0100, Stephan Hermann wrote: Hehe...well, it's a matter of working behaviour. I never said, that working from the CLI is not faster or more productive sometimes. What I'm trying to say is, that this arrogant elite thinking must go away. We

Accepted swig1.3 1.3.27-1 (source all i386)

2005-11-22 Thread Torsten Landschoff
Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: swig - Generate scripting interfaces to C/C++ code swig-doc - HTML documentation for SWIG swig-examples - Examples for applications of SWIG swig1.3- Generate scripting interfaces to C/C++ code

Accepted openldap2.2 2.2.26-5 (source i386)

2005-10-31 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 31 Oct 2005 09:06:46 +0100 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.26-5 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted ddclient 3.6.2-6 (source all)

2005-10-26 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 26 Oct 2005 20:38:18 +0200 Source: ddclient Binary: ddclient Architecture: source all Version: 3.6.2-6 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL

Accepted ddclient 3.6.2-5 (source all)

2005-10-18 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Oct 2005 22:54:26 +0200 Source: ddclient Binary: ddclient Architecture: source all Version: 3.6.2-5 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL

Accepted ddclient 3.6.2-4 (source all)

2005-10-05 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 5 Oct 2005 11:22:21 +0200 Source: ddclient Binary: ddclient Architecture: source all Version: 3.6.2-4 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL

Accepted fox1.4 1.4.16-2 (source i386 all)

2005-09-23 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 24 Sep 2005 00:23:20 +0200 Source: fox1.4 Binary: libfox1.4-doc libfox1.4-dev libfox1.4 Architecture: source i386 all Version: 1.4.16-2 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted swig1.3 1.3.25-1 (source all i386)

2005-09-22 Thread Torsten Landschoff
Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: swig - Generate scripting interfaces to C/C++ code swig-doc - HTML documentation for SWIG swig-examples - Examples for applications of SWIG swig1.3- Generate scripting interfaces to C/C++ code

Accepted openldap2 2.1.30-12 (source i386)

2005-09-19 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 19 Sep 2005 15:05:23 +0200 Source: openldap2 Binary: libldap2 libldap2-dev Architecture: source i386 Version: 2.1.30-12 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten

Accepted gmt 4.0-2 (source all i386)

2005-09-06 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 6 Sep 2005 09:04:17 +0200 Source: gmt Binary: gmt-examples gmt-tutorial-pdf gmt-doc-pdf gmt gmt-doc Architecture: source all i386 Version: 4.0-2 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL

Accepted gmt 4.0-1 (source all i386)

2005-09-04 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 4 Sep 2005 20:40:54 +0200 Source: gmt Binary: gmt-examples gmt-tutorial-pdf gmt-doc-pdf gmt gmt-doc Architecture: source all i386 Version: 4.0-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL

Re: Who needs libcurl3?

2005-07-19 Thread Torsten Landschoff
On Mon, Jul 18, 2005 at 09:28:27PM -0400, Stephen Frost wrote: That's not too helpful. I don't really want to support code I did not understand. I'd rather write it myself or have Steve care about problems in it... The idea is to get upstream to include/support it... The theory sound

Accepted openldap2.2 2.2.26-4 (i386 source)

2005-07-19 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 19 Jul 2005 20:52:17 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.26-4 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Re: Who needs libcurl3? (was libcurl3-dev: A development package linked again gnutls needed)

2005-07-18 Thread Torsten Landschoff
On Sun, Jul 17, 2005 at 03:19:54PM -0400, sean finney wrote: Why not building curl --without-sssl and --with-gnutls=/usr? Maybe a NMU? this is definitely NOT a reason to NMU libcurl. remember that it is your package that is broken. of course you could still file a The same issues as

Re: Who needs libcurl3? (was libcurl3-dev: A development package linked again gnutls needed)

2005-07-18 Thread Torsten Landschoff
On Sun, Jul 17, 2005 at 11:09:04PM +0300, Don Armstrong wrote: On Sun, 17 Jul 2005, Elimar Riesebieter wrote: apt-get remove --purge libssl0.9.7 gives me tons of packages. Just an estimation: We need to repack half of all packages then? NO.[1] All that needs to happen is that GPLed

Re: Who needs libcurl3?

2005-07-18 Thread Torsten Landschoff
Hi Goswin, On Mon, Jul 18, 2005 at 01:06:01PM +0200, Goswin von Brederlow wrote: I guess the savest way is to have a libldap-nossl-dev and libldap-ssl-dev. The former should have anything ssl derived removed. No problem. But then I can just build libldap without ssl as the library built

Re: Who needs libcurl3?

2005-07-18 Thread Torsten Landschoff
On Mon, Jul 18, 2005 at 09:06:20AM -0400, Stephen Frost wrote: No, that was *worse*. We tried that before. The answer really is reasonably simple- just modify libldap2 to use GNUTLS. That was done w/ an older version of things involved. I expect it'll be done for the newer stuff.

Re: Who needs libcurl3? (was libcurl3-dev: A development package linked again gnutls needed)

2005-07-18 Thread Torsten Landschoff
On Mon, Jul 18, 2005 at 09:29:46AM -0400, sean finney wrote: The same issues as with libcurl applied to libldap2. They were considered a bug in libldap2 back then because half the distribution links it. Gave me a lot of recurring head aches. yes, and the same with libmysqlclient, which

Re: Who needs libcurl3?

2005-07-18 Thread Torsten Landschoff
Hi Stephen, On Mon, Jul 18, 2005 at 10:53:02AM -0400, Stephen Frost wrote: Working on that. At least theoretically - when I get time, yada, yada. Steve Langasek had offered to help with this too. I'll poke him about it on IRC and see if he's still willing to help. That's not too helpful.

Re: skills of developers

2005-07-16 Thread Torsten Landschoff
Hi *, What kind of discussion is this? We can't effort more bureaucrazy (typo intended) in the project. Let the people doing the work do the work instead of first measuring their ability. If you are not able to maintain a package basically you wont. Or you wont for long as somebody will take

[RFC] Auto-Accept libs with just changed SONAME?

2005-07-16 Thread Torsten Landschoff
Hi *, During one of the talks of Debconf (I think it was about shared library packaging) there was a complaint that tracking upstreams SONAME changes means that your library package will end up in NEW each time it really changed. I'd like to suggest fixing the scripts to only flag packages as

Re: [RFC] Auto-Accept libs with just changed SONAME?

2005-07-16 Thread Torsten Landschoff
On Sat, Jul 16, 2005 at 05:22:04PM +0200, Joerg Jaspert wrote: And? Hows that bad? It means that volunteers have to spend time on this. In any case. And maintainer has to wait etc. I wonder why we don't automate more stuff in Debian. After all we have all the abilities to do it. I'd like

Re: no time for all debian tasks was: interacting with the press

2005-07-14 Thread Torsten Landschoff
Hi Anand, On Fri, Jul 15, 2005 at 12:32:54AM +1000, Anand Kumria wrote: Thanks for your comments -- however I don't think anyone should be able afraid to point out when a debian developer is obviously not able to satisfy all the Debian-related demands on their time; let alone their

Re: interacting with the press

2005-07-13 Thread Torsten Landschoff
On Wed, Jul 13, 2005 at 08:40:17AM +1000, Anand Kumria wrote: Or, should you find the demands on your time too pressing, why not use this opportunity to step-aside as the Debian press contact. Suggestions like these are just way off. Please adjust your attitude. Greetings Torsten

Accepted fox1.4 1.4.16-1 (i386 source all)

2005-07-13 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 13 Jul 2005 22:49:21 +0200 Source: fox1.4 Binary: libfox1.4-doc libfox1.4-dev libfox1.4 Architecture: source i386 all Version: 1.4.16-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted avra 1.0.1-0.1 (i386 source)

2005-07-05 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 29 Jun 2005 11:04:43 +0200 Source: avra Binary: avra Architecture: source i386 Version: 1.0.1-0.1 Distribution: unstable Urgency: low Maintainer: Jefferson E. Noxon [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL

Accepted openldap2.2 2.2.26-3 (i386 source)

2005-07-03 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 3 Jul 2005 10:41:37 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.26-3 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted openldap2 2.1.30-11 (i386 source)

2005-07-03 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 3 Jul 2005 10:52:07 +0200 Source: openldap2 Binary: libldap2 libldap2-dev Architecture: source i386 Version: 2.1.30-11 Distribution: unstable Urgency: high Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten

Accepted openldap2.2 2.2.26-2 (i386 source)

2005-07-01 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 1 Jul 2005 12:53:18 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.26-2 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted lam 7.1.1-3.1 (i386 source all)

2005-06-28 Thread Torsten Landschoff
-By: Torsten Landschoff [EMAIL PROTECTED] Description: lam-mpidoc - Documentation for the Message Passing Interface standard lam-runtime - LAM runtime environment for executing parallel programs lam4 - Shared libraries used by LAM parallel programs lam4-dev - Development of parallel programs

Accepted openldap2.2 2.2.26-1 (i386 source)

2005-06-21 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 21 Jun 2005 12:06:40 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.26-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

[HELP] libldap2 2.1.30 breakage?, guru for ld.so needed

2005-05-30 Thread Torsten Landschoff
Hi *, People following the OpenLDAP packages might remember this change: openldap2 (2.1.30-7) unstable; urgency=high * Stephen Frost [EMAIL PROTECTED] + debian/move_files: make libldap a symlink to libldap_r, as carrying two versions of this library around is more trouble

Re: [HELP] libldap2 2.1.30 breakage?, guru for ld.so needed

2005-05-30 Thread Torsten Landschoff
Hi Stephen, On Mon, May 30, 2005 at 09:16:15AM -0400, Stephen Frost wrote: Have you actually got a specific problem with the changes I did, or really, the results of them? There were a couple problems where people had old libldap2's hanging around (which is a rather serious mistake

Accepted openldap2.2 2.2.23-7 (i386 source)

2005-05-30 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 30 May 2005 08:08:37 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.23-7 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted openldap2.2 2.2.23-8 (i386 source)

2005-05-30 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 30 May 2005 08:48:10 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.23-8 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted openldap2 2.1.30-10 (i386 source)

2005-05-30 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 30 May 2005 10:22:52 +0200 Source: openldap2 Binary: libldap2 libldap2-dev Architecture: source i386 Version: 2.1.30-10 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten

Accepted openldap2.2 2.2.23-6 (i386 source)

2005-05-29 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 29 May 2005 18:23:20 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.23-6 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted openldap2 2.1.30-9 (i386 source)

2005-05-29 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 29 May 2005 19:03:46 +0200 Source: openldap2 Binary: libldap2 libldap2-dev Architecture: source i386 Version: 2.1.30-9 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten

Accepted mocka 9905-3 (i386 source)

2005-05-01 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 1 May 2005 13:15:44 +0200 Source: mocka Binary: mocka Architecture: source i386 Version: 9905-3 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL

Accepted openldap2.2 2.2.23-3 (i386 source)

2005-04-20 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Apr 2005 01:29:57 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.23-3 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Re: What do you win by moving things to non-free?

2005-04-19 Thread Torsten Landschoff
On Mon, Apr 18, 2005 at 10:08:50AM -0300, Margarita Manterola wrote: How about having a new section, open-source, or something, for the things that fall in the category described above? (i.e. software that is _almost_ free, but has some small limitation over some freedom) Let's call it free

Re: Recurring problems since upgrade of openldap2 (2.1 - 2.2)

2005-04-19 Thread Torsten Landschoff
Hi Michael, On Wed, Apr 20, 2005 at 12:09:15AM +0200, Michael Tautschnig wrote: I don't know which package I should file this bug against, but since the upgrade of the openldap2-packages I'm seeing these errors quite frequently: chown:

Accepted openldap2.2 2.2.23-2 (i386 source)

2005-04-14 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 14 Apr 2005 19:57:11 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.23-2 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted openldap2 2.1.30-6 (i386 source all)

2005-04-12 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 12 Apr 2005 21:16:44 +0200 Source: openldap2 Binary: libslapd2-dev libldap2 libldap2-dev Architecture: source all i386 Version: 2.1.30-6 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED

Re: Thoughts about changing Debian's release process

2005-04-07 Thread Torsten Landschoff
On Thu, Apr 07, 2005 at 10:46:35AM +1000, Andrew Pollock wrote: That's not true. If you can script it, FAI can do it. It just becomes a post-installation task. Using packages.d.o as an example, it's just going to be a predominantly an Apache configuration and some scripts, right? So

Re: Thoughts about changing Debian's release process

2005-04-07 Thread Torsten Landschoff
On Thu, Apr 07, 2005 at 09:36:36AM +0200, Wouter Verhelst wrote: sausage-machine style. Then of course you need to keep it up to date as well. I think that last phrase is the major problem... Yep, likewise. I still think having each part of our infrastructure as a package would be a good

Re: debconf and locale specific characters

2005-04-06 Thread Torsten Landschoff
Hi Alban, On Wed, Apr 06, 2005 at 05:15:34AM +0200, Alban Browaeys wrote: It is save to assume that the data from debconf is in the charset of the current locale? Then foo=`echo $RET|iconv -t UTF8` after the db_get would suffice. Of course the locale could change between config and

Re: Native package with two changelogs

2005-04-06 Thread Torsten Landschoff
On Wed, Apr 06, 2005 at 02:16:08PM +0200, Benjamin Mesing wrote: I have a package which I develop on my own and which is debian native. However due to historical reasons, I have a CHANGELOG file which is not the debian/changelog file. How should I handle this case? I am in favour of

debconf and locale specific characters

2005-04-05 Thread Torsten Landschoff
Hi there, My OpenLDAP 2.2 packages have a problem if the user enters something using his locale specific character (like äöü) into the organization field which is queried using debconf cf. http://bugs.debian.org/236097 The LDIF RFC demands that character data is either in 7 bit ASCII or in

Thoughts about changing Debian's release process

2005-04-05 Thread Torsten Landschoff
Hi Adrian, On Mon, Apr 04, 2005 at 08:54:11PM +0200, Adrian Bunk wrote: [the usual discussion about release procedures] I'd like to point out that these discussions lead nowhere just as many others. Changing Debian is currently: - discussing the problems - discussing approaches to solve

Re: Thoughts about changing Debian's release process

2005-04-05 Thread Torsten Landschoff
Hi Andreas, On Tue, Apr 05, 2005 at 10:04:38AM +0200, Andreas Tille wrote: My point: We need the possibility to recreate the current Debian infrastructure for proposing changes to the current situation. Not only this, we need the possibility to setup an alternate machine quickly in case of

Re: debconf and locale specific characters

2005-04-05 Thread Torsten Landschoff
On Tue, Apr 05, 2005 at 06:50:45AM -0700, Steve Langasek wrote: I agree there's a (slim) chance of the charset changing between config and postinst, so recoding in the config script itself is best. After thinking about it I don't think anymore it is that good an idea to do that. If debconf

Re: Right of a maintainer not to respect FHS

2005-04-04 Thread Torsten Landschoff
Hi Pierre, On Mon, Apr 04, 2005 at 09:28:22AM +0200, Pierre THIERRY wrote: I have a problem with a bug filed on r-doc-html (#300765). The documentation was entirely in /usr/lib, and it seems that all R packages have all their files under /usr/lib, whatever their type or purpose. How is that

Accepted openldap2.2 2.2.23-0.pre6 (i386 source)

2005-04-01 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 1 Apr 2005 12:26:35 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.23-0.pre6 Distribution: experimental Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED

Accepted openldap2.2 2.2.23-1 (i386 source)

2005-04-01 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 1 Apr 2005 18:50:21 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.23-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Re: [RFC] OpenLDAP automatic upgrade

2005-03-24 Thread Torsten Landschoff
Hi Quanah, On Mon, Mar 21, 2005 at 05:58:01PM -0800, Quanah Gibson-Mount wrote: You can find the patch for adding -q to slapadd on OpenLDAP 2.2 here: http://www.stanford.edu/services/directory/openldap/configuration/openldap-build-42.html Great, thanks! Applied it to the subversion

Re: [RFC] OpenLDAP automatic upgrade

2005-03-21 Thread Torsten Landschoff
Hi Quanah, On Thu, Mar 17, 2005 at 03:39:09PM -0800, Quanah Gibson-Mount wrote: Is there a way to enforce this without editing DB_CONFIG? I'd rather set an environment variable or something like that. Writing that into DB_CONFIG in the maintainer scripts always poses the risk that it'll

Re: Another load of typos

2005-03-17 Thread Torsten Landschoff
Hi Christian, On Wed, Mar 16, 2005 at 06:11:11PM +0100, Christian Perrier wrote: Sigh, I *knew* someone would say this..:-) Well, I may be unlucky enough for the tutorial about i18n/l10n handling for maintainers and translators I proposed at debconf to be accepted. If it is, I *will*

Re: [RFC] OpenLDAP automatic upgrade

2005-03-17 Thread Torsten Landschoff
Hi Quanah, On Wed, Mar 16, 2005 at 05:59:03PM -0800, Quanah Gibson-Mount wrote: The patches for BDB 4.2.52 are freely available from Sleepycat. They are required to be in place if you want a stable BDB 4.2.52 distribution. I would be very surprised if the package maintainer hadn't already

Re: [RFC] OpenLDAP automatic upgrade

2005-03-17 Thread Torsten Landschoff
On Thu, Mar 17, 2005 at 12:10:23AM -0300, Henrique de Moraes Holschuh wrote: In short, I cannot find a single reason to run OpenLDAP against BDB 4.3, and even the current OpenLDAP release notes that BDB 4.2 is required. I can find many reasons to not use BDB 4.3. Not good. That might

Migration back from libdb4.3 - libdb4.2, libdb4.3 broken

2005-03-17 Thread Torsten Landschoff
On Thu, Mar 17, 2005 at 08:38:31PM -0300, Henrique de Moraes Holschuh wrote: I think so. Jumping into a new BDB version like it was done for 4.3 is *always* foolhardy at best, IMHO. But it would be a very good idea to track down some other opinions about BDB 4.3 first, as people will not

Re: [RFC] OpenLDAP automatic upgrade

2005-03-16 Thread Torsten Landschoff
On Tue, Mar 15, 2005 at 05:04:26PM -0800, Quanah Gibson-Mount wrote: The first. Basically upstream changes the database format quite often. I am even not entirely sure if the database format stays compatible in the 2.1 or 2.2 line but I'd expect it to. The 2.2.23 Debian packages uses

Re: [RFC] OpenLDAP automatic upgrade

2005-03-16 Thread Torsten Landschoff
Hi Quanah, On Tue, Mar 15, 2005 at 01:07:29PM -0800, Quanah Gibson-Mount wrote: I currently maintain Stanford University's directory service, which is based on OpenLDAP. I also am a member of the OpenLDAP core team, and I hold down another job with Symas Corporation doing a variety of

Re: [RFC] OpenLDAP automatic upgrade

2005-03-15 Thread Torsten Landschoff
welcome any comments you have. I'll try to find some time. On Tue, Mar 15, 2005 at 01:36:17AM +0100, Torsten Landschoff wrote: a) the preinst checks if the database format has changed between the old version and the version that we are upgrading to is this an underlying database format change

[RFC] OpenLDAP automatic upgrade

2005-03-14 Thread Torsten Landschoff
Hi there, As you might have noticed or not we are working on getting OpenLDAP 2.2 into unstable. The packages are mostly working fine (as available in experimental) but what is missing is a really tested upgrade path from OpenLDAP 2.0 (in stable) and 2.1 (in testing, unstable). My proposal how

Accepted fox1.2 1.2.13-1 (i386 source all)

2005-03-14 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 14 Mar 2005 14:09:00 +0100 Source: fox1.2 Binary: libfox1.2-dev libfox1.2 libfox1.2-doc Architecture: source i386 all Version: 1.2.13-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Re: automake/autoconf in build-dependencies

2005-03-13 Thread Torsten Landschoff
Hi Kurt, On Sun, Mar 13, 2005 at 03:40:23PM +0100, Kurt Roeckx wrote: That's the point, actually: If I build-depend on autoconf, I *cannot* know that it will actually build after the next update to autoconf, because most likely nobody will try it. If it's known that a new major version

Re: Do not make gratuitous source uploads just to provoke the buildds!

2005-03-13 Thread Torsten Landschoff
On Sun, Mar 13, 2005 at 05:19:25PM +0100, Goswin von Brederlow wrote: And last I feel the sorting by name is actualy harmfull. That should be exchanged with the time of upload, i.e. FIFO if the rest matches. We all know FIFO isn't the best but it is simple, fair, predictable and does not

Re: is xprint still used by mozilla, etc?

2005-03-11 Thread Torsten Landschoff
On Thu, Mar 10, 2005 at 09:18:19PM -0500, Joey Hess wrote: Like I said at the head of this thread I explicitly added xprt-xprintorg to the deaktop task on user request. However, nothing I've seen so far seems to be a solid reason to keep it. OTOH, if the high priority debconf question goes

debconf in while read foo; ... loop?

2005-03-11 Thread Torsten Landschoff
Hi there, I am having a problem with using debconf in a maintainer script. Namely I am iterating over the list of directories configured for the ldap server and in the loop I am using db_get to query debconf. Problem: The answer from debconf never arrives since stdin is reading the pipe of the

Accepted openldap2.2 2.2.23-0.pre5 (i386 source)

2005-03-11 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 11 Mar 2005 18:54:57 +0100 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.23-0.pre5 Distribution: experimental Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED

Accepted fox1.2 1.2.4-2 (i386 source all)

2005-03-08 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 3 Mar 2005 21:01:26 +0100 Source: fox1.2 Binary: libfox1.2-dev libfox1.2 libfox1.2-doc Architecture: source i386 all Version: 1.2.4-2 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted openldap2.2 2.2.23-0.pre4 (i386 source)

2005-03-01 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 15:17:52 +0100 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.23-0.pre4 Distribution: experimental Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED

Accepted openldap2.2 2.2.23-0.pre3 (i386 source)

2005-02-27 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 27 Feb 2005 17:44:03 +0100 Source: openldap2.2 Binary: libldap2.2 slapd ldap-utils Architecture: source i386 Version: 2.2.23-0.pre3 Distribution: experimental Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Re: svn.debian.org: Automatically putting log message into debian/changelog?

2005-02-25 Thread Torsten Landschoff
Hi Joey, On Thu, Feb 24, 2005 at 04:42:49PM -0500, Joey Hess wrote: I've done this for years using the attached script (which will work with both svn and cvs (less well), and can also tag releases). Thanks, that was exactly what I looking for. I already had scheduled some hacking for this. :)

Updating config files: permissions!?

2005-02-25 Thread Torsten Landschoff
Hi *, During upgrades the slapd package (for example) has to do some adjustments on config files (it asks the user for permission of course). Problem: How do I make sure the new config files have the same permissions!? Currently I do chmod --reference=OLD NEW chown

Accepted openldap2.2 2.2.23-0.pre2 (i386 source)

2005-02-25 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Feb 2005 14:44:59 +0100 Source: openldap2.2 Binary: libldap2.2 slapd ldap-utils Architecture: source i386 Version: 2.2.23-0.pre2 Distribution: experimental Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

Accepted openldap2.2 2.2.23-0.pre1 (i386 source)

2005-02-25 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 23 Feb 2005 19:29:38 +0100 Source: openldap2.2 Binary: libldap2.2 slapd ldap-utils Architecture: source i386 Version: 2.2.23-0.pre1 Distribution: experimental Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed

svn.debian.org: Automatically putting log message into debian/changelog?

2005-02-23 Thread Torsten Landschoff
Hi *, I wonder if it would be possible to write a script that automatically updates debian/changelog each time somebody updates any files belonging to the package. I can't stand writing stuff in debian/changelog and then pasting it into the svn log message. What I think of is this: - user

Re: svn.debian.org: Automatically putting log message into debian/changelog?

2005-02-23 Thread Torsten Landschoff
On Wed, Feb 23, 2005 at 06:08:02PM +0100, Roland Bauerschmidt wrote: Torsten Landschoff wrote: I wonder if it would be possible to write a script that automatically updates debian/changelog each time somebody updates any files belonging to the package. I can't stand writing stuff in debian

Accepted openldap2 2.1.30-5 (i386 source all)

2005-02-23 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 23 Feb 2005 00:08:40 +0100 Source: openldap2 Binary: libslapd2-dev libldap2 libldap2-dev Architecture: source all i386 Version: 2.1.30-5 Distribution: experimental Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED

Accepted swig1.3 1.3.24-1 (i386 source all)

2005-02-20 Thread Torsten Landschoff
Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: swig - Generate scripting interfaces to C/C++ code swig-doc - HTML documentation for SWIG swig-examples - Examples for applications of SWIG swig1.3- Generate scripting interfaces to C/C++ code

Re: /etc under svk

2005-02-12 Thread Torsten Landschoff
Hi Enrico, On Fri, Feb 11, 2005 at 06:36:04PM +0100, Enrico Zini wrote: a tip to share: # Install svk apt-get install svk # Initialize a depot in /root/.svk svk depotmap --init [...] Wanted to do that - but! Does svk handle symlinks? Thinking of /etc/rc?.d and

Accepted swig1.3 1.3.22-6 (i386 source all)

2005-02-08 Thread Torsten Landschoff
Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: libswig1.3.22 - Runtime support libraries for swig generated wrappers libswig1.3.22-chicken - Runtime support libraries for swig generated wrappers

Accepted swig1.3 1.3.22-5 (i386 source all)

2004-11-20 Thread Torsten Landschoff
Distribution: unstable Urgency: medium Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: libswig1.3.22 - Runtime support libraries for swig generated wrappers libswig1.3.22-chicken - Runtime support libraries for swig generated wrappers

Accepted swig1.3 1.3.22-4 (i386 source all)

2004-11-09 Thread Torsten Landschoff
Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: libswig1.3.22 - Runtime support libraries for swig generated wrappers libswig1.3.22-chicken - Runtime support libraries for swig generated wrappers

Re: possible mass bug filing: spamassassin 3

2004-10-07 Thread Torsten Landschoff
On Wed, Oct 06, 2004 at 04:11:26PM +0200, Marco d'Itri wrote: Sorry, but the basic problem I'm speaking about has nothing to do with volatile - but just that requiring substancially more memory might be a bad idea. We still have inn1 and inn2 parallel (and I'm a happy user of inn1), for

Accepted fox1.2 1.2.4-1 (i386 source all)

2004-10-01 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 17 Sep 2004 20:51:03 +0200 Source: fox1.2 Binary: libfox1.2-dev libfox1.2 libfox1.2-doc Architecture: source i386 all Version: 1.2.4-1 Distribution: experimental Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED

Accepted swig1.3 1.3.22-1 (i386 source all)

2004-09-25 Thread Torsten Landschoff
Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: swig - Generate scripting interfaces to C/C++ code swig-doc - HTML documentation for SWIG swig-examples - Examples for applications of SWIG swig1.3- Generate scripting interfaces to C/C++ code

Accepted gmt-doc-ps 3.4.4-1 (all source)

2004-08-28 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 28 Aug 2004 22:54:05 +0200 Source: gmt-doc-ps Binary: gmt-doc-ps gmt-tutorial-ps Architecture: source all Version: 3.4.4-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten

Accepted fox 1.0.52-2 (i386 source all)

2004-08-01 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 1 Aug 2004 14:40:09 +0200 Source: fox Binary: libfox1.0 libfox-doc libfox1.0-dev libfox1.0-dbg Architecture: source all i386 Version: 1.0.52-2 Distribution: unstable Urgency: medium Maintainer: Torsten Landschoff [EMAIL

Accepted fox 1.0.52-1 (i386 source all)

2004-07-03 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 4 Jul 2004 00:18:22 +0200 Source: fox Binary: libfox1.0 libfox-doc libfox1.0-dev libfox1.0-dbg Architecture: source all i386 Version: 1.0.52-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED

Accepted openldap2 2.1.30-1 (i386 source all)

2004-05-24 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 24 May 2004 23:33:21 +0200 Source: openldap2 Binary: libslapd2-dev slapd libldap2 ldap-utils libldap2-dev Architecture: source i386 all Version: 2.1.30-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL

Accepted swig1.3 1.3.21-5 (i386 source all)

2004-05-21 Thread Torsten Landschoff
Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: libswig1.3.21 - Runtime support libraries for swig generated wrappers libswig1.3.21-chicken - Runtime support libraries for swig generated wrappers

Accepted gmt-manpages 3.4.4-1 (all source)

2004-05-20 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 21 May 2004 00:14:50 +0200 Source: gmt-manpages Binary: gmt-manpages Architecture: source all Version: 3.4.4-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff

Accepted openldap2 2.1.29-1 (i386 source all)

2004-04-12 Thread Torsten Landschoff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 12 Apr 2004 15:27:55 +0200 Source: openldap2 Binary: libslapd2-dev slapd libldap2 ldap-utils libldap2-dev Architecture: source i386 all Version: 2.1.29-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL

Accepted swig1.3 1.3.21-2 (i386 source all)

2004-03-31 Thread Torsten Landschoff
: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: libswig1.3.21 - Runtime support libraries for swig generated wrappers swig - Generate scripting interfaces to C/C++ code swig-doc - HTML documentation for SWIG swig-examples - Examples

<    1   2   3   4   >