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

Re: apt-get dist-upgrade errors


As it seems to me you are using a testing system with some unstable
In your case you have three possibilities:
1. try to uninstall libcomerr2 (and all packages depending on it) and
then install the e2fsprogs from testing (1.33+1.34-WIP-2003.05.21-2).
2. install the e2fsprogs from unstable (1.34+1.35-WIP-2003.08.21-3)
(as you did for libcomerr2)
3. force one of the two packages to overwrite the the file (dpkg -i
--force-overwrite packagename.deb). But in this case I don't like this
because I don't know if the .so-file is the same version in both
packages and so I don't know if it is a good idea to simply overwrite

I chose the second possibility because i.e. evolution 1.4 depends on
libcomerr2 and as I said I didn't like the overwriting thing in this

Hope this helps.

On Wed, 2003-09-17 at 16:09, ben wrote:
> I know it's not laptop specific but:
> when I attempt to do an upgrade of e2fsprogs I get this error:
> zeus:/# apt-get install e2fsprogs
> Reading Package Lists... Done
> Building Dependency Tree... Done
> 1 packages upgraded, 0 newly installed, 0 to remove and 282  not upgraded.
> Need to get 0B/396kB of archives. After unpacking 213kB will be used.
> (Reading database ... 76737 files and directories currently installed.)
> Preparing to replace e2fsprogs 1.32-2 (using 
> .../e2fsprogs_1.33+1.34-WIP-2003.05.21-2_i386.deb) ...
> Unpacking replacement e2fsprogs ...
> dpkg: error processing 
> /var/cache/apt/archives/e2fsprogs_1.33+1.34-WIP-2003.05.21-2_i386.deb 
> (--unpack):
>  trying to overwrite `/lib/libcom_err.so.2.1', which is also in package 
> libcomerr2
> dpkg-deb: subprocess paste killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/e2fsprogs_1.33+1.34-WIP-2003.05.21-2_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> Has anyone else encountered this or knows how I can get around it?
> I was thinking about removing libcomerr2 but wasn't sure.
> cheers,
> Ben

Reply to: