Tried to use Swaret to upgrade packages the other day and it got 1/4 of the way thru and started to show failure for all of the packages installed.

When I tried to run I not get the following:

Looks like Swaret hosed glibc?!!?

yes, it did. bad luck indeed for you.

yeeessssss...

So what would be the best way to fix glibc, a reinstall?

Read http://rlworkman.net/howtos/glibc-recovery

Eric

So I followed the directions here and I'm getting this error message:

From the instructions from the URL above, I though that i would be able to reinstall glibc with no problems, but still not the case.

Any ideas on how to troubleshoot?

thanks

So, what program gives you this error? Swaret? Because the slackware package manager will never show this error. If that is true, the problem lies with swaret, not Slackware.

Eric

By any chance are you using swaret to upgrade to -current?

Hey JackVSJock,

As an alternative to Swaret have you considered Slackupdate?

Get it here: http://darklinux.net/slackupdate

I had some trouble with Swaret so I went back to Slackupdate
and I really like it. About glibc - couldn't you just replace the package from installation cd and then look to see if there is a newer version?

hth,

The GNUinator

This error came when I booted off of the Slackware 10.2 cd and tried to install glibc from the disk following the directions from the URL above.

Hmmmm....can't remember off of my head how the swaret.conf file is set up cause I can't even log into the system right now.

Thank god for Linux live disks, cause I used those to rescue my data
off of the machine (remember to back up data!!!).

Anyways, again, this is the error that I'm getting when I'm trying
to boot off of Slackware 10.2 install disk and install glibc.


thanks

Considering the significant changes to Slackware going on in -current in preparation for the next release, it may be helpful to create a locked sticky with a title like "If you are thinking of upgrading to -current using Swaret - DON'T!!". Add some clueful links and hope some people read it more intently than they seem to read the change logs.

Just a thought.

Also - some of the same people seem have been involved in threads over the past year-and-a-half regarding swaret breaking something. At what point will you folks finally decide that there's a reason this tool get such bad press.

Not to mention the fact that swaret probably did exactly what you told it to. This time around that just happens to be a very bad thing if you want a functional system.

Agreed...Its no fun having my Slackware box down...



Well, most people probably try to use Swaret and the other automated package managers because of the interest of time...Although this is the final straw for me and I'll have to start using installpkg/upgradepkg, but I've had problems with those as well too...

I understand. When I moved to slackware from Suse 3 years ago, I used swaret for a short period of time and I never broke anything with it. Many people use it without a problem - or at least don't admit it if they do. To me, swaret seems to run counter to the slackware way of doing things and I think if people just bit the bullet and tried to learn the slackware tools they would be better off in the long run. At the very least, they may gain some knowledge that would let them safely use swaret if they want to because they will be able to better recognize circumstances where it may be an unwise upgrade tool.

I only admin a home network, but I find keeping local versions of the stable and -current trees up-to-date using rsync to be very simple and not time consuming at all. There are several scripts out there that will do this for you. If you have the disc space I highly recommend it. I can perform NFS installs and upgrades very easily as a result.

People will also cling to swaret for dependency resolution, yet slackware does not have nearly the dependency problems that RPM or Deb based Distros have. It's a solution in search of a problem in my opinion, and reminds me of how new users of linux keep looking for a defrag tool because windows had a problem with fragmented files so then linux must as well.

Anyway, enough soap-box ranting from me. Good luck getting your box sorted.

Hiya GUNinator -- It's unfortunate that some of our favourite Slackware upgrade tools are acting unpleasant lately, and I went and had a quick look at the site you mention up there.
While it seems unlikely to me, does this 'slackupdate' tool have any problems working with Slack 11.0 ?? It too is somewhat out of date by the looks of the website..
Thanks for any comments.
(Yes folks, I am looking into 'rsync' too; Swaret has not yet destroyed my system, so I still like it; and Slackpkg just plain doesn't work. If pkgtool only had a remote-location selection, huh? )

I've followed these directions:

Can't I just do a simple installpkg from disk 1 of the install disks for Slackware 10.2?