Murray,
While they both do involve a failure of the configuration process for the slapd
package during an upgrade, I think the original bug report and your problem
have separate root causes.
In particular, the problem discussed in the original bug report relates
to problems caused by invalid
Can I join this problem?
I've upgraded from Edgy to Karmic - this is a development machine so I'm
not too worried failure, however everything seemed to work okay which
was pretty amazing as I came through a number of EOL supported releases.
Anyways, the point of doing this upgrade was to test my
** Attachment added: Murray's slapd.conf (no passwords)
http://launchpadlibrarian.net/39441242/slapd.conf
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: openldap (Ubuntu)
Status: Incomplete = Confirmed
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in ubuntu.
--
Hello,
Sorry for not responding quickly!
I no longer use the directory server with OpenLDAP or slapd or ldap.
If later, I take this program, I will come to you to report any problems.
In case it is absolutely necessary to test this program for its operation, asks
me;
I take the time needed for
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification
What information is it that you want?
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in ubuntu.
--
Ubuntu-server-bugs mailing list
How did you create the initial configuration?
If there are nodomain entries, it means that the domainame of the system
wasn't setup correclty when slapd was *first* installed.
How did you add the dc=company,dc=com sub-tree? Is it a different
database definition?
Could you attach the content of
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
** Changed in: openldap (Ubuntu)
Importance: Undecided = Low
--
[apport] package slapd failed to install/upgrade:
Removing the two stray dc=nodomain entries from the .ldif, and rerunning
dpkg --configure slapd, everything now completes. I'll sacrifice another
machine to see if I can catch where the nodomain entries are coming from
in the first place.
--
[apport] package slapd failed to install/upgrade:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it without more information.
Could you attach the content of the file /etc/ldap/slapd.conf (with
relevant private information such as passwords and rootdn obfuscated)?
** Changed in:
** Changed in: openldap (Ubuntu)
Sourcepackagename: openldap2.3 = openldap
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in ubuntu.
Hello,
I justed tested upgrading from Dapper to Hardy once with slapd installed
but not configured, and once with the LDAP db populated and the system
configured to use it for authentication. Both upgrades worked without
issue.
I didn't test from Feisty to Gutsy, just FYI :-).
--
[apport]
13 matches
Mail list logo
