System: Mandriva 2008.1 (Cooker), x86_64

After trying to install a small application, I failed to notice that
it was also uninstalling stuff from the system (idiotic dependencies)
- had _nothing_ to do with using cooker. I managed to stop the
removals after a few files removed, so damage limited. However, it
managed to break / delete the use of RPM and URPMI.

Now when I try to install an application (the ones below) I get the
following error:

"rpm: error while loading shared libraries: librpm-4.4.so: cannot open
shared object file: No such file or directory"

The following files were removed before interrupted by me.

removing package drakxtools-curses-10.6.23-1mdv2008.1.x86_64
removing package lib64gwsoap0-3.5.9-4mdv2008.1.x86_64
removing package perl-URPM-3.11-1mdv2008.1.x86_64
removing package urpmi-5.6-1mdv2008.1.noarch
removing package libwnck-2.21.92-1mdv2008.1.x86_64
removing package usermode-1.94-1mdv2008.1.x86_64
removing package lib64bonoboui2_0-2.21.90-1mdv2008.1.x86_64
removing package hylafax-5.2.0-2mdv2008.1.x86_64
removing package pan-0.132-3mdv2008.1.x86_64
removing package gnome-python-canvas-2.21.1-1mdv2008.1.x86_64
removing package perl-Gtk2-Notify-0.04-2mdv2008.1.x86_64
removing package openoffice.org64-core-2.3.99.4-2mdv2008.1.x86_64
removing package lib64rpm4.4-4.4.2.3-0.rc1.2mdv2008.1.x86_64
removing package rpmdrake-4.3.1-1mdv2008.1.noarch
removing package lib64kdesdk1-3.5.9-2mdv2008.1.x86_64
removing package lib64kdegames1-3.5.9-1mdv2008.1.x86_64
removing package lib64gs8-8.61-59mdv2008.1.x86_64
removing package compiz-decorator-gtk-0.7.0-3mdv2008.1.x86_64
removing package tetex-3.0-46mdv2008.1.x86_64

I copied over some of these files to a memory card using Knoppix
(won't allow me to write to any Linux partition) using the files from
the Mandriva install DVD, but they can't install when back in Mandriva
- the error above occurs.

Any suggestions on how to fix this. There are one or two _small_
things broken, but most the system is actually running fine.
Re-installing the entire OS is the least favourite option, considering
how much of the system it will break.

Darius

On Fri, 29 Feb 2008 13:03:32 +0000, Darius wrote:

> After trying to install a small application, I failed to notice that
> it was also uninstalling stuff from the system (idiotic dependencies)
> - had _nothing_ to do with using cooker. I managed to stop the
> removals after a few files removed, so damage limited. However, it
> managed to break / delete the use of RPM and URPMI.

Hahaha! HAR! Yet another reason to NOT use an RPM-based distro.

It's called dependency-hell.

--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".

On 2008-02-29, Darius <Darius@> wrote:
> System: Mandriva 2008.1 (Cooker), x86_64
>
> After trying to install a small application, I failed to notice that
> it was also uninstalling stuff from the system (idiotic dependencies)
> - had _nothing_ to do with using cooker. I managed to stop the
> removals after a few files removed, so damage limited. However, it
> managed to break / delete the use of RPM and URPMI.

[...]

> Any suggestions on how to fix this. There are one or two _small_
> things broken, but most the system is actually running fine.
> Re-installing the entire OS is the least favourite option, considering
> how much of the system it will break.
>
> Darius

Does the installation disc have a 'repair' or 'upgrade' option? I think
either of those should reinstall the missing files for you.

Then check that you haven't set up any software 'sources' that aren't
specifically for your 64-bit 'cooker' system.

The whole point of a 'cooker' system is to pass lots of time finding and
mending problems, isn't it? Use an official release if you want it to do
anything reliably.

--
-- ^^^^^^^^^^
-- Whiskers
-- ~~~~~~~~~~

Dan C <youmustbejoking@lan.invalid> writes:

> On Fri, 29 Feb 2008 13:03:32 +0000, Darius wrote:
>
>> After trying to install a small application, I failed to notice that
>> it was also uninstalling stuff from the system (idiotic dependencies)
>> - had _nothing_ to do with using cooker. I managed to stop the
>> removals after a few files removed, so damage limited. However, it
>> managed to break / delete the use of RPM and URPMI.
>
> Hahaha! HAR! Yet another reason to NOT use an RPM-based distro.
>
> It's called dependency-hell.

Actually not.

It's a URPMI based distro and it understands the relationship
between RPMs just as well as a DEB based distro.

The OP started an install and stopped it with control-c.
For all we know, after it removed what it needed to it
might have proceeded to install what it needed and there
would have been no problem.

Darius wrote:

> System: Mandriva 2008.1 (Cooker), x86_64
>
> After trying to install a small application, I failed to notice that
> it was also uninstalling stuff from the system (idiotic dependencies)

I'm intrigued to know exactly what you were trying to install to make urpmi
uninstall itself?

> - had _nothing_ to do with using cooker. I managed to stop the
> removals after a few files removed, so damage limited. However, it
> managed to break / delete the use of RPM and URPMI.

That's because you uninstalled rpm/urpmi

> Now when I try to install an application (the ones below) I get the
> following error:
>
> "rpm: error while loading shared libraries: librpm-4.4.so: cannot open
> shared object file: No such file or directory"

see above

> I copied over some of these files to a memory card using Knoppix
> (won't allow me to write to any Linux partition) using the files from
> the Mandriva install DVD, but they can't install when back in Mandriva
> - the error above occurs.

see above

> Any suggestions on how to fix this.

The quickest way would be to re-install the os. The next quickest would be
an upgrade-install. Or you can unpack the relative rpms from your dvd, find
the correct places to put the particular files within the rpm and copy them
there. I know which I'd be doing.

> There are one or two _small_
> things broken, but most the system is actually running fine.
> Re-installing the entire OS is the least favourite option, considering
> how much of the system it will break.

How will re-installing the os break your system exactly?

--
sid
RLU 300284
Mandriva 2008.1/cooker X86_64
2.6.24.2

Dan C wrote:

> On Fri, 29 Feb 2008 13:03:32 +0000, Darius wrote:
>
>> After trying to install a small application, I failed to notice that
>> it was also uninstalling stuff from the system (idiotic dependencies)
>> - had _nothing_ to do with using cooker. I managed to stop the
>> removals after a few files removed, so damage limited. However, it
>> managed to break / delete the use of RPM and URPMI.
>
> Hahaha! HAR! Yet another reason to NOT use an RPM-based distro.

Bzzt, Wrong answer. Yet another reason not to listen to your biased opinion
in a news group for a distro you don't even like. ;)

> It's called dependency-hell.

If you use urpmi with distro sources there is *no* dependency problems. If
you stop urpmi when it's half way through a task then you're asking for
grief. Particularly when it has already uninstalled itself, <snigger>/

Of course the above is only true if you have, at least, an idea of what
you're trying to do in the first place.


--
sid
RLU 300284
Mandriva 2008.1 X86_64
2.6.24.2

On Fri, 29 Feb 2008 17:37:48 +0000, Dan Espen wrote:

>>> removals after a few files removed, so damage limited. However, it
>>> managed to break / delete the use of RPM and URPMI.

>> Hahaha! HAR! Yet another reason to NOT use an RPM-based distro.
>> It's called dependency-hell.

> Actually not.
> It's a URPMI based distro and it understands the relationship
> between RPMs just as well as a DEB based distro.

It's an RPM based distro, as I said. URPMI is just a shiny front end for
RPM, added by Mandriva. What do the URPMI database/repositories contain?
That's right.... RPM files.

> The OP started an install and stopped it with control-c.
> For all we know, after it removed what it needed to it
> might have proceeded to install what it needed and there
> would have been no problem.

That part may very well be true.


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".

On Fri, 29 Feb 2008 17:59:19 +0000, sid wrote:

>> Hahaha! HAR! Yet another reason to NOT use an RPM-based distro.

> Bzzt, Wrong answer. Yet another reason not to listen to your biased opinion
> in a news group for a distro you don't even like. ;)

It wasn't an "answer", and it wasn't wrong. My opinion is no more biased
than yours, is it?

As far as not liking the distro, that's not entirely accurate either. I
have a sweet/sour feeling about Mandriva. I cut my teeth on Mandrake, and
used it almost exclusively for a couple of years, enjoying it immensely.
Then it started to unravel a bit, and by the time the name-change came
about, the distro was really headed for the toilet. Haven't looked at it
in a few versions, but I do understand from reading that it has improved
somewhat from it's low point. The reason I don't use it any more is that
it does too much hand-holding, and the RPM issues that are too limiting.

>> It's called dependency-hell.

> If you use urpmi with distro sources there is *no* dependency problems. If
> you stop urpmi when it's half way through a task then you're asking for
> grief. Particularly when it has already uninstalled itself, <snigger>/

Agreed.

> Of course the above is only true if you have, at least, an idea of what
> you're trying to do in the first place.

I assume you mean the above comment towards the OP, who clearly is
clueless, and probably destined to stay that way.


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".

Dan C <youmustbejoking@lan.invalid> writes:

> On Fri, 29 Feb 2008 17:37:48 +0000, Dan Espen wrote:
>
>>>> removals after a few files removed, so damage limited. However, it
>>>> managed to break / delete the use of RPM and URPMI.
>
>>> Hahaha! HAR! Yet another reason to NOT use an RPM-based distro.
>>> It's called dependency-hell.
>
>> Actually not.
>> It's a URPMI based distro and it understands the relationship
>> between RPMs just as well as a DEB based distro.
>
> It's an RPM based distro, as I said. URPMI is just a shiny front end for
> RPM, added by Mandriva. What do the URPMI database/repositories contain?
> That's right.... RPM files.

Don't be dumb.

Dependency hell is when you go to install something and
it tells you you need to install something else.
You install that and you
find out you need still more.

That does not occur with URPMI.
You ask to install a package and it figures out
everything you need and installs it all.

I don't think it's any different than deb or whatever you
think is better.

Dan C wrote:

> On Fri, 29 Feb 2008 17:59:19 +0000, sid wrote:
>
>>> Hahaha! HAR! Yet another reason to NOT use an RPM-based distro.
>
>> Bzzt, Wrong answer. Yet another reason not to listen to your biased
>> opinion
>> in a news group for a distro you don't even like. ;)
>
> It wasn't an "answer", and it wasn't wrong. My opinion is no more biased
> than yours, is it?

Ah, but you don't find me on a.l.o.s slating tar.gz package management, or
any of the other things I find unreasonable about slack. :-j
>
> As far as not liking the distro, that's not entirely accurate either. I
> have a sweet/sour feeling about Mandriva.

I know :)

> I cut my teeth on Mandrake,

Snap


> and
> used it almost exclusively for a couple of years, enjoying it immensely.
> Then it started to unravel a bit, and by the time the name-change came
> about, the distro was really headed for the toilet.

Funnily enough, that was about when it started to turn around.

> Haven't looked at it
> in a few versions, but I do understand from reading that it has improved
> somewhat from it's low point.

It has :)

> The reason I don't use it any more is that
> it does too much hand-holding,

It's better than slack in that regard imo, because you have the choice to
have your hand held or you are perfectly free to "go commando" if that is
your want. As with everything in the linux world you are free to choose how
you go about stuff, choice being a good thing.

> and the RPM issues that are too limiting.

Eh? Urpmi is the real clincher for me. with properly configured sources
there is something like 12000 packages that can be installed simply
with "sudo urpmi package-name". It's so easy and so cool to be able to show
users from the dark side how well a computer can work :)

>>> It's called dependency-hell.
>
>> If you use urpmi with distro sources there is *no* dependency problems.
>> If you stop urpmi when it's half way through a task then you're asking
>> for grief. Particularly when it has already uninstalled itself,
>> <snigger>/
>
> Agreed.
>
>> Of course the above is only true if you have, at least, an idea of what
>> you're trying to do in the first place.
>
> I assume you mean the above comment towards the OP, who clearly is
> clueless, and probably destined to stay that way.

See, you are right some of time ;)

--
sid
RLU 300284
Mandriva 2008.1 X86_64
2.6.24.2