LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Updating Current (http://www.linuxquestions.org/questions/slackware-14/updating-current-4175455311/)

Woodsman 03-23-2013 07:15 PM

Updating Current
 
I haven't updated my Current virtual machine since Feb. 25. Shame on me. The result is thus far I am unable to update Current.

Every time I try to update glibc-solibs I get a slew of doinst.sh errors about /usr/bin/* No such file or directory and the system becomes unusable.

First I tried updating everything with slackpkg. Boink.

Next I tried updating according to UPGRADE.TXT. Boink.

Then seeing that coreutils was updated before glibc, next I tried updating coreutils, rebooting, and then updating glibc-solibs. Boink.

What is the grand poobah secret handshake to get this updated?

I have a backup of the VM and restoring to the original Feb. 25 state is easy enough. Yes, I could blow everything away and install fresh, but now I'm curious what is happening and why.

Thanks. :)

willysr 03-23-2013 09:17 PM

do you have multilib installed?

Woodsman 03-23-2013 09:22 PM

No, I don't. The VM is 32-bit.

As I have backups of the VM, I decided to try a fresh install. Using the defaults, the install script spews errors such as:

/sbin/ldconfig: /lib/libattr.so.1 is not an ELF file - it has the wrong magic bytes at the start
/sbin/ldconfig: /lib/libuuid.so.1.3.0 is not an ELF file - it has the wrong magic bytes at the start
/sbin/ldconfig: /lib/libcomm_err.so.2.1 is not an ELF file - it has the wrong magic bytes at the start
/sbin/ldconfig: /lib/libdevmapper_event.so.1.02 is not an ELF file - it has the wrong magic bytes at the start

When I try to update the system I saw this message repeated many times:

/sbin/ldconfig: /usr/lib is not a symbolic link

I'm confused!

willysr 03-23-2013 09:37 PM

perhaps a corrupted package or wrong mirror site being used

Woodsman 03-23-2013 09:43 PM

I don't think so. I tried a different mirror and nothing changed at my local repo.

Has anybody else tried a fresh install with the DVD?

Edit: Looks like the problem is the 32-bit disk. No ELF errors with the 64-bit disk. Would somebody please confirm before I notify the BDFL?

volkerdi 03-23-2013 10:03 PM

Quote:

Originally Posted by Woodsman (Post 4917480)
Edit: Looks like the problem is the 32-bit disk. No ELF errors with the 64-bit disk. Would somebody please confirm before I notify the BDFL?

If you figure out what happened, you could just mention it here. If the 32-bit install was broken for everyone, I'd think someone would have told me by now.

Alien Bob 03-24-2013 07:21 AM

I guess with "Looks like the problem is the 32-bit disk. No ELF errors with the 64-bit disk." you are referring to an unofficial slackware-current install DVD ISO? Which one are you using (timestamp, md5sum, origin) ?

Eric

Woodsman 03-24-2013 11:41 AM

I haven't figured out what happened. :)

All I know is I see the ELF messages with the 32-bit DVD and not with the 64-bit DVD and I can't update the VM in any way I tried. :(

Typically I don't use a DVD to update. I use my local repo, created with rsync and upstream mirrors. Typically I sync with tds.net but I also resynced against osuosl.org in the hope I would notice errors.

In this case I also tested a DVD that I made from the local repo. Same results.

I checked the md5sums per the instructions in CHECKSUMS.md5. Everything looks fine.

Could be PEBKAC, but I haven't changed anything that I'm aware in my rsync and updating process. Been using the same process for years. Could be that I have not updated Current in several weeks and something related. Could be some weird corruption in the VM. I don't know. I have a test partition on my system that I use when Currrent gets closer to release, but I have been hesitant to update the partition after the results with the VM. Because Current can sometimes be volatile, I always first update the VM before updating the partition. I'll make a backup and then see what happens.

Woodsman 03-24-2013 01:27 PM

An update:

I updated my physical Current partitions without a hitch. I updated directly from my local repo and with slackpkg. I didn't even bother changing to init 1.

That leaves the VM as suspicious. As I never had a problem before yesterday, I'm at a loss what might be the problem. The only change I remember since the last time I updated the VM is I updated to KDE 4.10.1, which means I updated Qt from 4.8.2 to 4.8.4, which means I probably should have rebuilt VirtualBox, but with that all said, none of my other VMs exhibit any problems and the Current 64-bit DVD does not exhibit any of the errors I'm seeing.

I created a new 32-bit Current VM and I again saw the same ELF errors trying to install Current.

I will rebuild VirtualBox against Qt 4.8.4, but I suspect that won't change anything.

I hate being confused! :scratch:

hitest 03-24-2013 02:49 PM

Interesting. I am running 32 bit -current using a DVD ISO I created using Eric's -current build script. I updated my install this morning with the latest updates and all went without a hitch. I've also upgraded to -current using the official 32 bit 14.0 ISO. Very odd. I will assume you used slackpkg install-new when upgrading. Maybe take a look at slackpkg clean-system? Best of luck. :)


All times are GMT -5. The time now is 07:28 AM.