Hi Torsten,

On Mon, 9 May 2005, Torsten Landschoff wrote:

>> 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

I use the readline frontend, too.

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

I will look at it, I didn't hear about this cmd so far... :)

>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.

Understood. Anyway, I hope nobody will make up some day with the idea
that some process should delete the cache dir regularly, as with
debian it is nearly impossible to get a (even not-so-far) old binary
package if you don't have it in your cache.

>
>> 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?

Oh, yes, sorry, that logical step was dropped you of the list.

>
>> 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 just use debian, and don't understand package handling deeply, but I
experienced that after a (preinst) install script fails, many packages
still get installed and configured. I do not know the algorithm of
which packages are allowed to be installed, but it seems that libldap2
was installed, and it made my old ldap package useless...

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

It is a good idea.

Thanks for the fast reply, I hope I could help:
Ferenc


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to