Hello,

today I downloaded and ran swaret on my slack 10.0 installation.
I ran it in this way:
swaret --set VERSION=current
swaret --update
swaret --upgrade
All has worked well.

After rebooting I cannot log in. I am receiving
"GLIBC_2.3.4 not found (required by bash)" message.
What can I do? Plese help me, thanks,

Piotr Z.

qazwsxedc wrote:
> Hello,
>
> today I downloaded and ran swaret on my slack 10.0 installation.
> I ran it in this way:
> swaret --set VERSION=current
> swaret --update
> swaret --upgrade
> All has worked well.
>
> After rebooting I cannot log in. I am receiving
> "GLIBC_2.3.4 not found (required by bash)" message.
> What can I do? Plese help me, thanks,
>
> Piotr Z.
>

Since you shell do not work, you first have to boot from a bootable CD
that have the necessary slackware tools (the second slackware CD of 10.0
is such); mount your root partition and install the missing package with
the -root option; you can see precisely on what files bash depend by
running ldd /path/to/bash.

Olive

qazwsxedc wrote:

> today I downloaded and ran swaret on my slack 10.0 installation.
> I ran it in this way:
> swaret --set VERSION=current
> swaret --update
> swaret --upgrade
> All has worked well.

Similar things used to happen to me with Debian after an apt-get
dist-upgrade. *** Broken fucking packages ***...

To prevent this, I switched to Slackware whose package manager doesn't
handle dependencies. I'm fine since.

Swaret, slapt-get and the likes remind me of a French expression: "chercher
la merde". Looks like you found it.

Believe me: you're better off checking dependencies manually. It's not that
hard, and you always have things under control.

Cheers,

Niki Kovacs
--
I'm not as think as you stoned I am.

On Sun, 25 Sep 2005 07:59:06 +0200, Niki Kovacs <mickey@mouse.com> wrote:
<snip>
>
> Believe me: you're better off checking dependencies manually. It's not that
> hard, and you always have things under control.

I second this advise, for a long time I ran redhat systems on my other
machines and slackware on my own. The more I fooled around with any
package system that uses dependencies the more I realised how insane
they are and worthless in the long run. The only thing they are good for
is maintaining the distibutions default package set IMHO.

--

/dTd
gpg-key: http://badlands-nwn.com/tbdownloads/dtd-pub-key.asc

dTd wrote:

> I second this advise, for a long time I ran redhat systems on my other
> machines and slackware on my own. The more I fooled around with any
> package system that uses dependencies the more I realised how insane
> they are and worthless in the long run. The only thing they are good for
> is maintaining the distibutions default package set IMHO.

Funny thing. Right now I'm busy compiling transcode (a nightmare), and I
surprise myself thinking: "I-need-a-package-manager,
I-need-a-package-manager, I-need-a-package-manager,
I-need-a-package-manager, I-need-a-package-manager,
I-need-a-package-manager, I-need-a-package-manager,
I-need-a-package-manager, I-need-a-package-manager,
I-need-a-package-manager, I-need-a-package-manager,
I-need-a-package-manager, I-need-a-package-manager,
I-need-a-package-manager, I-need-a-package-manager,
I-need-a-package-manager, I-need-a-package-manager,
I-need-a-package-manager, I-need-a-package-manager,
I-need-a-package-manager, I-need-a-package-manager,
I-need-a-package-manager"

../configure --enable-kitchensink --enable-hairdryer --enable-dishwasher
--disable-rhinoceros

ERROR: cannot find shared library libhairdry.so
*** Error 2 ***

\

Niki Kovacs
--
I'm not as think as you stoned I am.

Many thanks, your solution functioned very well.

Thank you,
Piotr.

PD. I uninstalled swaret

On Sun, 25 Sep 2005 16:24:51 +0200, Niki Kovacs <mickey@mouse.com> wrote:
> dTd wrote:
>
>> I second this advise, for a long time I ran redhat systems on my other
>> machines and slackware on my own. The more I fooled around with any
>> package system that uses dependencies the more I realised how insane
>> they are and worthless in the long run. The only thing they are good for
>> is maintaining the distibutions default package set IMHO.
>
> Funny thing. Right now I'm busy compiling transcode (a nightmare), and I
> surprise myself thinking: "I-need-a-package-manager,
> I-need-a-package-manager, I-need-a-package-manager,
> I-need-a-package-manager, I-need-a-package-manager,
> I-need-a-package-manager, I-need-a-package-manager,
> I-need-a-package-manager, I-need-a-package-manager,
> I-need-a-package-manager, I-need-a-package-manager,
> I-need-a-package-manager, I-need-a-package-manager,
> I-need-a-package-manager, I-need-a-package-manager,
> I-need-a-package-manager, I-need-a-package-manager,
> I-need-a-package-manager, I-need-a-package-manager,
> I-need-a-package-manager, I-need-a-package-manager,
> I-need-a-package-manager"
>
> ./configure --enable-kitchensink --enable-hairdryer --enable-dishwasher
> --disable-rhinoceros
>
> ERROR: cannot find shared library libhairdry.so
> *** Error 2 ***
>
>\
>
> Niki Kovacs
nscode must get the prize for the most interdependent piece of software
available. Realising it's job it's understandable. After reading the
docs though, it does say that not all codecs nor features are required
for a good working install of transcode. I have a package I made a while
back if you're interested

--

/dTd
gpg-key: http://badlands-nwn.com/tbdownloads/dtd-pub-key.asc

Niki Kovacs wrote:

> Believe me: you're better off checking dependencies manually. It's not
> that hard, and you always have things under control.

Just a quick note: swaret runs ldd on all of the binaries that are
upgraded/installed, then looks up any missing libraries to find out what
package needs to be installed to resolve those dependencies. Most people
like this fact, since "Not Found" is normally a bad sign. People who don't
want it can always turn that feature off.

All of the glib (and related) problems are when people try to jump too many
version numbers (like 10.0 to 10.2) or sync to current. However, Pat does
not guarantee that things won't break. Tell me how to fix this and I will.

If you use swaret and want to keep it safe, just set your version to what
you installed, then use swaret to keep up with security fixes.

LinuxSneaker

> "GLIBC_2.3.4 not found (required by bash)

swaret doesn't prevent shooting yourself in the leg..
and if you're upgrading bash before glibc... well.. that's you
ignorance, but don't blame swaret for killing your syste

swaret dependency checking is working fairly well, however it yo
don't understand how/why/what swaret is doing, then you'll fin
fedora or ubuntu much friendlier..

Message posted via
====================
www.linuxpackages.net/foru
www.linuxpackages.ne
Expanding the world of Slackwar
=====================