On 07/09/2010 18:53, Steve Langasek wrote:
> severity 595464 minor
Are you sure ? For now, in some situation, there is no way to upgrade the
package without manually editing debconf files...
> thanks
>
> On Sat, Sep 04, 2010 at 09:04:04AM +0200, Vincent Danjean wrote:
>> The only working tip has been to manually edit /var/cache/debconf/config.dat
>> and set slapd/move_old_database to true.
>> And then:
>> r...@ogmios:/home/vdanjean# dpkg -a --configure
>> Paramétrage de slapd (2.4.23-4) ...
>> Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.17-2.1... done.
>> Moving old database directories to /var/backups:
>> - directory dc=danjean,dc=fr... done.
>> Loading from /var/backups/slapd-2.4.17-2.1:
>> - directory dc=danjean,dc=fr... done.
>> - chowning database directory (openldap:openldap)... done
>> Migrating slapd.conf to slapd.d configuration style... done.
>> Starting OpenLDAP: slapd.
>
>> You should really propose easiest way to upgrade slapd when non standard
>> configuration is found (at least, a way to leave the package in a installed
>> state even if the config migration is not completed).
>> Perhaps, reasking the slapd/move_old_database question can be a solution (at
>> least for interactive upgrade)
>
> This has nothing to do with non-standard configurations, and everything to
> do with the fact that you had set slapd/move_old_database to 'false' in
> debconf. Why did you do this? This is a low-priority debconf question that
> defaults to 'true'.
I installed the virtual machine a few weeks ago. I do not remember changing
debconf priority nor answering to this question (I discovered it when looking
at the postinst when the upgrade fails).
> It is possible to handle this migration by hand if you choose (not a good
> idea IMHO, but possible). You just need to leave the directory in place, so
> slapadd has somewhere to write since it won't create the path for you.
I do not understand what you say here. I tried to move away my subdirectory
(/var/lib/ldap/danjean) as the error message says. Then I got another error
message (see my bug report).
> Marking the package as "installed" when the maintainer scripts have failed
> to upgrade the directory to a DB version that will actually run with the
> current slapd would be an error.
But, but leaving no way to handle the upgrade when the configuration is
non standard (ie having two or more databases in /var/lib/ldap) is also,
IMHO, an error.
For example, when db-config found an error (no database, ...), it asks again
the questions but with a higher priority. It could be a solution here.
If I have the time, I will retry to install an old version of slapd and
redone the upgrade because I really do not remember anwsering the
debconf question and changing its default value.
Regards,
Vincent
--
Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble
Téléphone: +33 4 76 61 20 11 ENSIMAG - antenne de Montbonnot
Fax: +33 4 76 61 20 99 ZIRST 51, avenue Jean Kuntzmann
Email: vincent.danj...@imag.fr 38330 Montbonnot Saint Martin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
