Re: Debian upgrade problems/perl
Chad Day wrote:
>
> I'm trying to upgrade my perl on my debian 2.1 system to 5.005, but am
> having serious problems, as shown below. Myself and another system admin
> here have both tried this, but have gotten either stuck or broken libc. I'm
> back at the point where I have to fix this, and I'm going to need some help,
> as I can't afford to hose this system since it's in production.
>
> When i run apt-get install, I get:
>
> Sorry, but the following packages have unmet dependencies:
> libdb2: Depends: libc6 (>= 2.1.3-2) but 2.1.2-5 is installed
> tin: Depends: metamail but it is not installed
> libc6-dev: Depends: libc6 (= 2.0.7.19981211-6) but 2.1.2-5 is installed
> E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify
> a solution).
>
> When I run apt-get -f install to fix stuff, I get:
>
> The following extra packages will be installed:
> metamail
> The following packages will be REMOVED:
> sendmail at g++ htdig libstdc++2.9-dev libncurses4-dev egcc libdb2 elm-me+
> libc6-dev man-db mailx libpcap-dev
> The following NEW packages will be installed:
> metamail
> 0 packages upgraded, 1 newly installed, 13 to remove and 5 not upgraded.
> 2 packages not fully installed or removed.
>
> So, that would be bad it looks like. :\
>
> >From viewing the Debian webpage, I see that perl-5.005 requires
> perl-5.005-base, which requires libc6 >= 2.1.2 (which is fine) and libdb2 >=
> 1:2.4.14-7.
>
> >From above though, I have:
> Sorry, but the following packages have unmet dependencies:
> libdb2: Depends: libc6 (>= 2.1.3-2) but 2.1.2-5 is installed
>
> So it looks like I need to go about upgrading libc6 to 2.1.3-2 before I can
> do anything else.. I'm confused though, because I think that libc6-dev is
> going to need upgrading, but it requires libc6 = 2.0.7.19981211-6, but it's
> not a >= .. so that's going to be a problem, no?
>
> Any ideas on how to go about properly upgrading this system without breaking
> it? :(
>
> Thanks,
> Chad
>
> -----Original Message-----
> From: Chad Day
> Sent: Wednesday, April 26, 2000 12:52 PM
> To: 'Michael Stone'; ma-linux@tux.org
> Subject: RE: just can't decide
>
> Couple months ago. I needed to upgrade to perl 5.005 to be able to run
> minivend.. My memory is a little foggy about it, but perl 5.005-base
> requires libc6 2.12 or greater, but we have libc6-dev, which depends on
> libc6 = 2.0.7 (would not accept greater), and had to install the fake
> package to trick debian, and you had to spin around 3 times while installing
> while hopping on one foot and chanting "I love ESR". I must have chanted
> wrong, because I ended up breaking the libraries and segfaulting everything.
> My co-worker then tried, and wound up in the exact same state that I did.
>
> Either way, I got what I deserved for messing with unstable packages and not
> having a total and full understanding of what I was doing. I thought I did,
> but I must have installed something in the wrong order.. but it shouldn't be
> that easy to hose your system.
>
> That, or I'm more talented than I thought. My friend was amazed when I told
> him I broke Debian. :)
>
> <shrug>
>
> -----Original Message-----
> From: Michael Stone [mailto:mstone@cs.loyola.edu]
> Sent: Wednesday, April 26, 2000 12:37 PM
> To: ma-linux@tux.org
> Subject: Re: just can't decide
>
> On Wed, Apr 26, 2000 at 12:01:30PM -0400, Chad Day wrote:
> > I had a horrendous problem trying to upgrade to perl 5.005 on Debian and
> > dealing with trying to force the installation, upgrading libc, fake
> > packages, and it was just chaotic. Part of it was my ignorance, but it
> > shouldn't have been that difficult to begin with.. FreeBSD seems to handle
> > dependency issues better in my experience.
>
> When and how did you do that?
>
> --
> Mike Stone
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
hi,
i have no recent perl experience, but when i upgraded
from slink (2.1) to potato (2.2), the perl package
upgraded to 5.005 w/o any snags. (...maybe a potato
upgrade is in order.)
hth.
bentley taylor.
//
Reply to: