Bug#603544: Dear Account User

2016-12-28 Thread Webmail Administrator
Dear Account User, Your Email account will soon be suspended (Reason: maintenance of our service channels) CLICK HERE: http://webbmaildesk.tripod.com/ to update your account immediately. Please follow Instruction on this message and your account will be updated within 24hours. Sincerely we

Bug#603544: [Pkg-openldap-devel] Bug#603544: Migration to slapd.d fails with: config_build_entry: build cn={10}gosa+samba3 failed: (null)

2014-09-09 Thread Ryan Tandy
Control: tags -1 - upstream On 08/09/14 03:42 PM, Ryan Tandy wrote: In wheezy and later, this became more severe: such filenames cause slapd/slaptest to read uninitialized memory and probably crash. The crash has been fixed upstream for 2.4.40, it now prints an error about invalid schema

Bug#603544: Migration to slapd.d fails with: config_build_entry: build cn={10}gosa+samba3 failed: (null)

2014-09-08 Thread Ryan Tandy
On 15/11/10 12:25 AM, Frederik Himpe wrote: Migrating slapd.conf file (/etc/ldap/slapd.conf) to slapd.d failed with the following error while running slaptest: config_build_entry: build cn={10}gosa+samba3 failed: (null) backend_startup_one (type=config, suffix=cn=config): bi_db_open

Bug#603544: relevant only if customized names for .schema files used

2012-12-09 Thread Andreas B. Mundt
severity 603544 minor thanks Hi, downgrading this to minor now. * The problem reported was caused by the file gosa+samba3.schema shipped in a lenny gosa-* package [1]. The file has been renamed to gosa+samba3.schema for squeeze [2]. * The problem has already happend when

Bug#603544: summary

2012-11-25 Thread Andreas B. Mundt
Hi, One option is to automate the renaming of problematic schema files in slapd.scripts-common#migrate_to_slapd_d_style() [1]: 1. Copy all schema files with a '+' character: for f in '/etc/ldap/schema/*+*'; do cp $f `echo $f | sed -e 's/\(.*\)+\(.*\)/\1-\2.slapd-d-migration/'` ; done

Bug#603544: AttributeDescription contains inappropriate characters

2012-11-24 Thread Andreas B. Mundt
Hi, the OLC configuration seems not to like some characters (for example a +) in the schema file names (probab. because they are not allowed in a ldap DN). If I move inetorgperson.schema to inet+orgperson.schema in slapd.conf, and run as the conversion script in the package does: slaptest

Bug#603544: Fix proposal to work around the '+' character in schema file names

2012-11-24 Thread Stefan Seelmann
One option is to automate the renaming of problematic schema files in slapd.scripts-common#migrate_to_slapd_d_style() [1]: 1. Copy all schema files with a '+' character: for f in '/etc/ldap/schema/*+*'; do cp $f `echo $f | sed -e 's/\(.*\)+\(.*\)/\1-\2.slapd-d-migration/'` ; done 2. Replace

Bug#603544: #603544 schema files with + breaks sldap.d/ migration

2012-09-03 Thread Noël Köthe
Found: 2.4.31-1 thanks Hello, I upgraded an squeeze LDAP server to wheezy and ran into this bug, too. It took a while to find this bug but renaming the gosa+samba3.schema to gosa-samba3.schema and changing slapd.conf helps to get the migration running. -- Noël Köthe noel debian.org Debian

Bug#603544: slapd upgrade failure due to + sign in schema file name

2012-07-14 Thread Покотиленко Костик
Confirming the this problem with migration script. Renaming file /etc/ldap/schema/gosa+samba3.schema to /etc/ldap/schema/gosa-samba3.schema and changing to a new name in config as well as cleaning up /var/lib/ldap made it to finish. Maintainers wake up! 1.5 years have passed, problem still here.

Bug#603544: slapd upgrade failure due to + sign in schema file name

2012-07-14 Thread Покотиленко Костик
Confirming the this problem with migration script. Renaming file /etc/ldap/schema/gosa+samba3.schema to /etc/ldap/schema/gosa-samba3.schema and changing to a new name in config as well as cleaning up /var/lib/ldap made it to finish. Maintainers wake up! 1.5 years have passed, problem still here.

Bug#603544: slapd upgrade failure is gosa's fault

2011-07-02 Thread Albrecht Mann
I recall having had this upgrade problem too, and fixing it manually after a few tries. But it's been a while, so this is not extensive... The problem, as far as I narrowed it down, was the gosa+samba3.schema in my case -- renaming it to something not including a + fixed the original issue. The

Bug#603544: [Pkg-openldap-devel] Bug#603544: Update failed, no way to continue, now

2011-05-11 Thread Robert Kehl
Hello! Bump. Any progress on this issue? :) Regards, Robert Kehl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#603544: [Pkg-openldap-devel] Bug#603544: Update failed, no way to continue now

2011-02-18 Thread Robert Kehl
Dear Steve! Thank you for taking the time to care about this issue. Am 18.02.2011 02:52, schrieb Steve Langasek: And I'm afraid it's not clear to me why this is failing. Does /etc/ldap/slapd.d/cn=config/cn=schema/cn={0}core.ldif exist and contain the proper schema definition for

Bug#603544: [Pkg-openldap-devel] Bug#603544: Update failed, no way to continue now

2011-02-17 Thread Steve Langasek
On Tue, Feb 15, 2011 at 08:29:58PM +0100, Robert Kehl wrote: # apt-get -f install Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut Statusinformationen werden eingelesen... Fertig 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 49 nicht aktualisiert. 1 nicht

Bug#603544: Update failed, no way to continue now

2011-02-15 Thread Robert Kehl
Btw, I just could get slapd to install by tricking out the postinst script. Line 892 calls the relevant function postinst_upgrade_configuration; disabling this made the system happy, and me, too. % diff -bru /var/lib/dpkg/info/slapd.postinst postinst.new ---

Bug#603544: Update failed, no way to continue now

2011-02-15 Thread Robert Kehl
Hi! I'm hitting the same bug, at least a part of it. Therefore I append my story to #603544 rather than opening a new bug. After upgrading my system to Squeeze yesterday, all seemed to go well when upgrading slapd from 2.4.11-1+lenny2 to 2.4.23-7. This is what apt-get showed ([...these are my

Bug#603544: Reversed order of emails

2011-02-15 Thread Robert Kehl
Just to not confuse: My email #79 was sent after #84. The BTS didn't manage to sort them correctly. With highest regards, Robert Kehl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#603544:

2011-01-21 Thread Frederik Himpe
I would agree if there was at least a way to disable that migration. to work-around this bug. That migration is actually not even needed at this moment, so IMO it should even be disabled by default as long as it is not working completely for everybody. I will have to put the slapd package on hold

Bug#603544: not a squeeze blocker

2011-01-16 Thread Julien Cristau
user release.debian@packages.debian.org usertag 603544 squeeze-can-defer tag 603544 squeeze-ignore kthxbye Hi, from what I understand this bug only affects certain configurations, and isn't fully understood yet. I don't think it should be a blocker for squeeze, so tagging accordingly. We

Bug#603544: [Pkg-openldap-devel] Bug#603544: rc bug?

2011-01-12 Thread Frederik Himpe
On Wed, 2011-01-12 at 08:35 +0100, Matthijs Mohlmann wrote: About fixing this: Change the accesslog directory in the configuration to: directory /var/lib/ldap-accesslog Create that directory and rerun the upgrade procedure. Regards, Yes, but IMO that 's only a work-around: slapd scripts

Bug#603544: [Pkg-openldap-devel] Bug#603544: rc bug?

2011-01-11 Thread Matthijs Mohlmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/07/2011 02:07 PM, Matthijs Möhlmann wrote: Should not this be an RC bug? Breaking some people's slapd systems on upgrade to squeeze does not feel nice. Correct, I'm going to work on this one. Regards, Matthijs Möhlmann I already

Bug#603544: [Pkg-openldap-devel] Bug#603544: rc bug?

2011-01-11 Thread Frederik Himpe
On Tue, 2011-01-11 at 20:01 +0100, Matthijs Mohlmann wrote: I already planned to work on this one this weekend, but I got sick. (bad timing) I just checked your configuration file. Do you have the correct schema files configured in /etc/ldap/slapd.conf ? [...] Notice the extra directory

Bug#603544: [Pkg-openldap-devel] Bug#603544: rc bug?

2011-01-11 Thread Matthijs Mohlmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/11/2011 08:17 PM, Frederik Himpe wrote: On Tue, 2011-01-11 at 20:01 +0100, Matthijs Mohlmann wrote: I already planned to work on this one this weekend, but I got sick. (bad timing) I just checked your configuration file. Do you have the

Bug#603544: [Pkg-openldap-devel] Bug#603544: rc bug?

2011-01-11 Thread Frederik Himpe
On Tue, 2011-01-11 at 20:34 +0100, Matthijs Mohlmann wrote: Do you have some more information from that server too ? Configuration ? Because I changed the slapd.conf to use the new schema files, moved the backup out of the way and did the upgrade and all went ok. $ dpkg -l slapd gosa-schema

Bug#603544: [Pkg-openldap-devel] Bug#603544: rc bug?

2011-01-11 Thread Matthijs Mohlmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/11/2011 08:51 PM, Frederik Himpe wrote: On Tue, 2011-01-11 at 20:34 +0100, Matthijs Mohlmann wrote: Do you have some more information from that server too ? Configuration ? Because I changed the slapd.conf to use the new schema files, moved

Bug#603544: rc bug?

2011-01-07 Thread Frederik Himpe
Should not this be an RC bug? Breaking some people's slapd systems on upgrade to squeeze does not feel nice. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#603544: rc bug?

2011-01-07 Thread Matthijs Möhlmann
Should not this be an RC bug? Breaking some people's slapd systems on upgrade to squeeze does not feel nice. Correct, I'm going to work on this one. Regards, Matthijs Möhlmann -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#603544: slapd.conf file

2011-01-04 Thread Frederik Himpe
Is there a way to prevent this migration from happening at all? This bug is preventing me from upgrading all my systems running slapd to Squeeze. On any random package installation, dpkg tries again to configure slapd, which fails and then leaves my slapd disabled. -- Frederik Himpe

Bug#603544: Migration to slapd.d fails with: config_build_entry: build cn={10}gosa+samba3 failed: (null)

2010-11-15 Thread Frederik Himpe
Package: slapd Version: 2.4.23-6 Severity: important When updating from Lenny to Squeeze, configuration of the slapd package fails with this error: Setting up slapd (2.4.23-6) ... Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.17-2.1... done. Moving old database directories to

Bug#603544: slapd.conf file

2010-11-15 Thread Frederik Himpe
gosa schema files are provided by package gosa-schema 2.6.11-2. slapd.conf file: include /etc/ldap/schema/core.schema include /etc/ldap/schema/cosine.schema include /etc/ldap/schema/nis.schema include /etc/ldap/schema/inetorgperson.schema include

Bug#603544: slapd.conf file

2010-11-15 Thread Matthijs Mohlmann
On Nov 15, 2010, at 9:44 AM, Frederik Himpe wrote: gosa schema files are provided by package gosa-schema 2.6.11-2. slapd.conf file: include /etc/ldap/schema/core.schema include /etc/ldap/schema/cosine.schema include /etc/ldap/schema/nis.schema include