Re: Could not early remove libpam0g

["Bill" <bill@widebay.net.au>]

Thanks Shawn,

tried
computer:/# apt-get -f -o APT::Force-LoopBreak dist-upgrade

result
E: Option APT::Force-LoopBreak: Configuration item sepecification must have
an =<val>.

so then I tried
computer:/# dpkg --force-depends -r libpam0g  --> this worked

next
computer:/# apt-get -f dist-upgrade
is this anything to worry about???? --> had following messages

Ambiguous use of package => resolved to "package" => at
/usr/sbin/suidregister line 109.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 131.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 203.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 325.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 38.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 64.
Ambiguous use of package => resolved to "package" => at
/usr/sbin/suidregister line 109.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 131.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 203.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 325.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 38.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 64.
Ambiguous use of package => resolved to "package" => at
/usr/sbin/suidregister line 109.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 131.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 203.
Ambiguous use of {package} resolved to {"package"} at /usr/sbin/suidregister
line 325.

after completed got
E: Sub-process /usr/bin/dpkg recieved a segmentation fault.


Regards
Bill

----- Original Message -----
From: "elyograg" <elyograg@wolsi.com>
To: "Bill" <bill@widebay.net.au>
Cc: <debian-isp@lists.debian.org>
Sent: Tuesday, April 25, 2000 2:13 AM
Subject: Re: Could not early remove libpam0g


> At 03:03 PM 4/24/2000 +1000, Bill wrote:
> >E: This installation run will require temporarily removing the essential
> >package libpam0g 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 libpam0g
>
> Bill,
>
> Try this:
>
> apt-get -f -o APT::Force-LoopBreak dist-upgrade
>
> If that doesn't work, try without the -f.  If you have no luck at all, you
> may have to log in as root (i'd recommend not using su, sudo, etc.) and do
> the following first:
>
> dpkg --force-depends -r libpam0g
>
> The dpkg and apt packages do not depend on this library, so there should
be
> no problem with removing it long enough to get your system upgraded.  Of
> course, any running services might not work very well. :)
>
> Thanks,
> Shawn
>
>
> --
> To UNSUBSCRIBE, email to debian-isp-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
>