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

Bug#46233: Can't install perl-5.005 on fresh potato system



Package: apt
Version: 0.3.13

I started from a new chroot slink installation of base-2.1.tgz, then
`apt-get dist-upgrade' to potato, followed by the installation and
purging of a few packages.  Then I needed perl, so I decide to install
perl-5.005 and got the following:

# apt-get install perl-5.005
Reading Package Lists... Done
Building Dependency Tree... Done
The following extra packages will be installed:
  perl-5.005-base perl-base 
The following NEW packages will be installed:
  perl-5.005 perl-5.005-base 
1 packages upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 2146kB of archives. After unpacking 5652kB will be used.
Do you want to continue? [Y/n] 
Get:1 http://http.us.debian.org unstable/main perl-5.005-base 5.005.03-4 [412kB]
Get:2 http://http.us.debian.org unstable/main perl-base 5.004.05-1 [1346B]     
Get:3 http://http.us.debian.org unstable/main perl-5.005 5.005.03-4 [1733kB]   
Fetched 2146kB in 4m33s (7862B/s)                                              
E: This installation run will require temporarily removing the essential package perl-base due to a Conflicts/Pre-Depends loop. This is often bad, but if you really want to do it, activate the APT::Force-LoopBreak option.
E: Internal Error, Could not early remove perl-base

A post to -devel generated the following response:

> Date: Wed, 29 Sep 1999 00:58:41 -0400
> From: Raul Miller <raul@usatoday.com>
> To: Peter S Galbraith <GalbraithP@dfo-mpo.gc.ca>
> Subject: Re: Dependency error installing perl-5.005 on fresh potato.
> 
> Send a copy of /var/lib/dpkg/info/status to the apt folks.
> 
> To hide the problem, you can do:
> 
> dpkg --configure --pending
> apt-get -f install
> 
> [But please send in a bug report with the status file first.]

Therefore, I am sending this bug report against apt.  The status file
is at http://www.debian.org/~psg/status.apt-bug and will be deleted
when the bug is closed.



Reply to: