07-21-06 12:12 AM
Bill Marcum wrote this gem. Seriously... :
> On Wed, 19 Jul 2006 18:33:59 -0700, Bitey
> <bitey@batcave.rafters> wrote:
> This message is usually caused by an error in a package install or
> remove script. The scripts are found in
> /var/lib/dpkg/info/packagename.*
>
> If you are using a testing or unstable version, you may have to wait a
> few days for a bug fix. Or if you can find the script that causes the
> error, you could insert an "exit 0".
Thank you for your reply. I have narrowed it down to an error while
installing the following:
The following NEW packages will be installed:
samba samba-common samba-dbg
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get
6591kB/11.1MB of archives. After unpacking 40.4MB of additional disk space
will be used. Get:1 http://security.debian.org stable/updates/main
samba-dbg 3.0.14a-3sarge2 [6591kB] Fetched 6591kB in 37s (176kB/s)
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
another process (Reading database ... dpkg: error processing
/var/cache/apt/archives/samba-common_3.0.14a-3sarge2_i386.deb (--unpack):
files list file for package `samba' contains empty filename
Errors were encountered while processing:
/var/cache/apt/archives/samba-common_3.0.14a-3sarge2_i386.deb
Processing was halted because there were too many errors. E: Sub-process
/usr/bin/dpkg returned an error code (1) RESULT=100
The line that starts with 'debconf: DbDriver "config":' has me stumped.
Locked by another process?? Can you (or anyone) shed some light on how I
would find out which process is locked and why?
--
A Bitey Copyleft Production ;p~~~
[ Post a follow-up to this message ]
|