Hi Ferenc, 

On Mon, May 09, 2005 at 12:21:32AM +0200, Ferenc Engard wrote:
 
> While I have upgraded my system, slapd upgrade asked some questions, 
> including directory to dump databases. The text said the default is
> /var/backups/slapd-VERSION. Reading that, I simply pushed enter. After
> that, the preinst script have failed, rendering slapd unconfigured.
> Meanwhile, apt has upgraded my libldap2 package.

Which debconf frontend to you use? I hit the same problem with the
readline frontend which does not seem to use the default value if you
just push enter but instead the empty value. Maybe the configuration
script should just replace the empty value by the default value again.

> After that I have recognized that the error is that there is no default
> for this setting despite of the description, I tried to set this with
> dpkg-reconfigure, but it didn't asked this question again (maybe there
> is a switch for that, just I didn't found it). I had to manually edit

That could be considered a bug, yes. The question is only asked before
upgrading, running dpkg-reconfigure will not ask for it but create a new
OpenLDAP directory.

> /var/cache/debconf/config.dat (and that was not easy to find that this
> file is what I have to edit :( ).

Hint: You could also use debconf-communicate for stuff like that.

> The game was not over: because of my libldap2 was upgraded, but slapd
> was not installed yet, slapcat didn't run. For some unknown reason the
> 
> apt-get install slapd=2.1.23-1 libldap2=2.1.23-1
> 
> command said 'E: Version '2.1.23-1' for 'slapd' was not found', although
> my old packages were still in the cache directory.

apt does not use packages in the cache directory unless they are still
in the packages list for that package source. IOW: Because 2.1.23-1 is
no longer in the Debian archive apt-get just forgets that they are still
available somewhere in your cache. But you can use dpkg to install them.

> In the end, I successfully downgraded with dpkg. I still sucked with
> that the dumpdir already existed, and preinst didn't like it, but it was
> a piece of cake after these all.

Erm, you mean, that you upgraded to 2.2.23 again afterwards? 

> The most screamy was when it seemed that I cannot downgrade, and I
> system was useless. Do somebody have a tip what could cause that?
 
My understanding of dpkg and apt-get says that at the time the preinst
is run the old packages should still be installed. To get the broken
state you describe, the system must have continued the installation
despite the error in the slapd preinst. Which is in fact not expected to
ever happen. 

I'll safeguard against an empty value for the dump dir...

Greetings

        Torsten

Attachment: signature.asc
Description: Digital signature

Reply via email to