ror, Could not early
remove e2fsprogs
apt told me to set the APT::Force-LoopBreak-parameter.
I tied this: apt-config -o APT::Force-LoopBreak=true
or this: apt-config -o APT::Force-LoopBreak="true"
or this: apt-config -o APT::Force-LoopBreak="1"
and so on
Could not early
remove e2fsprogs
apt told me to set the APT::Force-LoopBreak-parameter.
I tied this: apt-config -o APT::Force-LoopBreak=true
or this: apt-config -o APT::Force-LoopBreak="true"
or this: apt-config -o APT::Force-LoopBreak="1"
and so on
Nothi
Well, I bit the bullet and went ahead with it. My sytem seems to be
sane, although I did get many scary warnings from dpkg during the
upgrade. I also got many complaints from perl about problems setting
the locales for several packages, but I suppose that has nothing to do
with the original
e e2fsprogs 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 e2fsprogs"
> ---
>
> From 'man apt-get':
>
> ---
> Force-LoopBrea
, but
if you really want to do it, activate the APT::Force-LoopBreak option.
E: Internal Error, Could not early remove e2fsprogs"
---
From 'man apt-get':
---
Force-LoopBreak
Never Enable this option unless you -really- know what
you are
doing. It per-
On Sat, 30 Sep 2000, Thomas J. Hamman wrote:
> Okay, so I can't dist-upgrade because of a problem that I shouldn't work
> around because it's "A GRAVE BUG" and I don't "-really- know" what I'm
> doing -- so, what am I supposed to do?
In this case you may activate the option, however, I recommend
is
often bad, but if you really want to do it, activate the
APT::Force-LoopBreak option.
E: Internal Error, Could not early remove libpam-modules
Looking in man apt.conf, I see this:
Force-LoopBreak
Never Enable this option unless you -really- know
what you are doing. It permits
7 matches
Mail list logo