[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: apt-get fails



-----BEGIN PGP SIGNED MESSAGE-----

On Sun, 31 Oct 1999, peter karlsson wrote:

> Martin Fluch:
> 
[[[discussion of the situation described in bug#48806 snipped by]]] 
[[[previous poster]]]
> > Install this package manualy with dpkg -i /var/cache/apt/archives/debconf*
> > and apt-get upgrade should do.
> 
> That seems to cure the problem, but why did it appear in the first place?

A bug somewhere? That's why unstable is called unstable.

It looks like the debconf module in the debconf 0.2.1 package uses the new
interface introduced in 0.2.0 (as stated in the changelog). However, since
there is only 28 hours between the timestamp for 0.2.0 and 0.2.1 in the
changelog (which doesn't take into account time spent propigating to the
mirrors, etc), it turns out to be very likely that people will be
upgrading from 0.1.x. This breaks the debconf module in the debconf
package, which causes dpkg-preconfig to fail, which causes apt to fail.

Specifically from the changelog, in the entry for 0.2.0
>   * confmodule is a new shell library that handles this by making each
                      ^^^
i interpret this to mean that it wasn't present in 0.1.x, and at the least
it wasn't present in whichever 0.1.x i had previously. Perhaps the debconf
module should check if /usr/share/debconf/confmodule exists before trying
to use it, to avoid backward combatability?


- -- 
  finger for PGP public key.




-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBOBywe77M/9WKZLW5AQH1UAQAhPzF4zW/f5u2KJRl21Re3yNMxYFjkmH8
6hZuVPB199MZUXzzM1jN5GX6C89cpKSfxYqjPwyykT4umijreXr0tuk4CXuON8Gv
srPbkJK31gMDUD1v0N1KlgtqxMUUzhQ8zMN9NSh2Pr0APt3vrDYDMSsr8DK5RPrr
J15vufuYr+A=
=QQpK
-----END PGP SIGNATURE-----


Reply to: