Friday the 13th Massive Upgrade

colorpurple21859 · 07-24-2012, 09:10 AM

This was after the fix. current before massive-upgrade to current after massive-upgrade fix still broke, 13.37 to current after massive-upgrade fix works, Was wondering if anybody else had similar results.

allend · 07-24-2012, 09:53 AM

Quote:

This was after the fix. current before massive-upgrade to current after massive-upgrade fix still broke, 13.37 to current after massive-upgrade fix works, Was wondering if anybody else had similar results.

Yes - as reported in post #141

disturbed1 · 07-24-2012, 10:36 AM

Quote:

Originally Posted by andrew.46

Just noticed the same issue here:

Code:

root@skamandros/home/andrew# cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 3.01a07 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

modprobe sg

Edit/add to one of the rc.* files will take care of that.
I usually add/edit rc.local, that way I won't have to remember the modifications made to the stock Slackware rc. scripts and wonder why things don't work after they are upgraded upstream

Code:

# cdrecord -scanbus 
Cdrecord-ProDVD-ProBD-Clone 3.01a07 (i686-pc-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

=============
# modprobe sg
# cdrecord -scanbus 
Cdrecord-ProDVD-ProBD-Clone 3.01a07 (i686-pc-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
Linux sg driver version: 3.5.34
Using libscg version 'schily-0.9'.
scsibus0:
	0,0,0	  0) 'ATA     ' 'TOSHIBA MK1032GS' 'AS02' Disk
	0,1,0	  1) *
	0,2,0	  2) *
	0,3,0	  3) *
	0,4,0	  4) *
	0,5,0	  5) *
	0,6,0	  6) *
	0,7,0	  7) *
scsibus6:
	6,0,0	600) 'SanDisk ' 'SDDR-117        ' '1.03' Removable Disk
	6,1,0	601) *
	6,2,0	602) *
	6,3,0	603) *
	6,4,0	604) *
	6,5,0	605) *
	6,6,0	606) *
	6,7,0	607) *

xa0c · 07-25-2012, 02:38 PM

Quote:

Originally Posted by eXpander_

Hi,

I found the problem, and I think it is because of Spotify.

Hi. I had the same issue. Actually its not only Spotify problem.
This problem also appears for users, who have google-chrome package from slacky.eu community. If you'll check you will see that it's doinst.sh script contains following lines:

Code:

( cd usr/lib64 ; rm -rf libnss3.so.1d )
( cd usr/lib64 ; ln -sf /usr/lib64/seamonkey/libnss3.so libnss3.so.1d )
( cd usr/lib64 ; rm -rf libnssutil3.so.1d )
( cd usr/lib64 ; ln -sf /usr/lib64/seamonkey/libnssutil3.so libnssutil3.so.1d )
( cd usr/lib64 ; rm -rf libsmime3.so.1d )
( cd usr/lib64 ; ln -sf /usr/lib64/seamonkey/libsmime3.so libsmime3.so.1d )
( cd usr/lib64 ; rm -rf libssl3.so.1d )
( cd usr/lib64 ; ln -sf /usr/lib64/seamonkey/libssl3.so libssl3.so.1d )
( cd usr/lib64 ; rm -rf libplds4.so.0d )
( cd usr/lib64 ; ln -sf /usr/lib64/seamonkey/libplds4.so libplds4.so.0d )
( cd usr/lib64 ; rm -rf libplc4.so.0d )
( cd usr/lib64 ; ln -sf /usr/lib64/seamonkey/libplc4.so libplc4.so.0d )
( cd usr/lib64 ; rm -rf libnspr4.so.0d )
( cd usr/lib64 ; ln -sf /usr/lib64/seamonkey/libnspr4.so libnspr4.so.0d )

As slacky.eu wrote in a package description: this package uses Seamonkey-Solibs package. Thats why additional symlinks were created in /usr/lib64. And when the Mercury turned retrograde, 'mozilla-nss' package appeared

andrew.46 · 07-25-2012, 07:12 PM

Quote:

Originally Posted by disturbed1

modprobe sg

Edit/add to one of the rc.* files will take care of that.

Thanks, that has resolved the issue

.

kristizz · 07-26-2012, 04:08 PM

Holey moley. Changed to current from a clean 13.37 install and did slackpkg clean-system and install-new. Now slackpkg rejects the gpg key and won't upgrade-all. Has anyone else had this issue?

rworkman · 07-26-2012, 05:12 PM

Quote:

Originally Posted by kristizz

Holey moley. Changed to current from a clean 13.37 install and did slackpkg clean-system and install-new. Now slackpkg rejects the gpg key and won't upgrade-all. Has anyone else had this issue?

From slackpkg(8):

Code:

      Slackpkg can be used to upgrade the whole distribution.
       The usual way is to do:

            # slackpkg update
            # slackpkg install-new
            # slackpkg upgrade-all
            # slackpkg clean-system

You'll have to manually upgrade some stuff before slackpkg will work again - exactly what will be left as an exercise to the reader. Consider this a learning experience

chrisretusn · 07-26-2012, 05:52 PM

Quote:

Originally Posted by kristizz

Holey moley. Changed to current from a clean 13.37 install and did slackpkg clean-system and install-new. Now slackpkg rejects the gpg key and won't upgrade-all. Has anyone else had this issue?

Quote:

Originally Posted by rworkman

From slackpkg(8):

Code:

      Slackpkg can be used to upgrade the whole distribution.
       The usual way is to do:

            # slackpkg update
            # slackpkg install-new
            # slackpkg upgrade-all
            # slackpkg clean-system

To add to this learning experience added by Robby. When upgrading from stable to -current or one version to the next using slackpkg it is always a good idea to first upgrade glibc, then the package utilities and slackpkg before doing the above. Not upgrading glibc is the most likely reason you are getting those gpg key errors.

slackpkg update
slackpkg upgrade glibc
slackpkg upgrade findutils pkgtools slackpkg tar xz
slackpkg update <<--- You need to do this if slackpkg has been upgraded in the previous step.
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system

There are other steps depending on your setup. Third party video drives will need to be reinstalled and if your using the generic kernel, you will have to put the symlinks back, mkinitrd will be to be run again, along with lilo of course.

D1ver · 07-26-2012, 06:16 PM

Quote:

Originally Posted by chrisretusn

To add to this learning experience added by Robby. When upgrading from stable to -current or one version to the next using slackpkg it is always a good idea to first upgrade glibc, then the package utilities and slackpkg before doing the above. Not upgrading glibc is the most likely reason you are getting those gpg key errors.

slackpkg update
slackpkg upgrade glibc
slackpkg upgrade findutils pkgtools slackpkg tar xz
slackpkg update <<--- You need to do this if slackpkg has been upgraded in the previous step.
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system

There are other steps depending on your setup. Third party video drives will need to be reinstalled and if your using the generic kernel, you will have to put the symlinks back, mkinitrd will be to be run again, along with lilo of course.

Thank you for this. I've had the gpg error on a couple machines (ended up reinstalling directly from a current mirror). I am currently resisting installing current on the one laptop I actually need to do work.. This might come in handy

mlangdn · 07-26-2012, 06:30 PM

This is also where AlienBob's mirror-slackware.sh script comes in handy. By keeping a local tree of -current, if something goes awry like not following the proper steps, one can upgrade manually from the tree. I had to do that on a test partition I keep of -current. This test partition is plain -current with no 3rd party software.

leeeoooooo · 07-27-2012, 08:28 PM

Quote:

Originally Posted by chrisretusn

To add to this learning experience added by Robby. When upgrading from stable to -current or one version to the next using slackpkg it is always a good idea to first upgrade glibc, then the package utilities and slackpkg before doing the above. Not upgrading glibc is the most likely reason you are getting those gpg key errors.

slackpkg update
slackpkg upgrade glibc
slackpkg upgrade findutils pkgtools slackpkg tar xz
slackpkg update <<--- You need to do this if slackpkg has been upgraded in the previous step.
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system

There are other steps depending on your setup. Third party video drives will need to be reinstalled and if your using the generic kernel, you will have to put the symlinks back, mkinitrd will be to be run again, along with lilo of course.

Yes, this looks like it does the trick. No more gpg errors.

No, Robby, my system time was not the problem and "slackpkg upgrade findutils pkgtools slackpkg tar xz" only found slackpkg and xz to upgrade, but Mercury is still in retrograde so crossed signals are to be expected.

If this continues as well as it is going under VirtualBox, I'll go ahead and upgrade my eeepc to Slackware 14b!

I used to skip the clean-system step myself, but that's how slackpkg removes the packages that are marked "removed" in the changelog. I just had to make sure my blacklist was updated so slackpkg would ignore not only my '_SBo' packages, but also my 'alien' and slacky 'sl' packages, and my upgraded guile 2.0.5 (which still hasn't been upgraded in the distribution updates).

BTW, I *love* the more verbose changelog entries. Makes for fascinating and exciting reading!

kristizz · 07-28-2012, 03:51 AM

Quote:

Originally Posted by rworkman

From slackpkg(8):

Code:

      Slackpkg can be used to upgrade the whole distribution.
       The usual way is to do:

            # slackpkg update
            # slackpkg install-new
            # slackpkg upgrade-all
            # slackpkg clean-system

You'll have to manually upgrade some stuff before slackpkg will work again - exactly what will be left as an exercise to the reader. Consider this a learning experience

All sorted. Glibc was the main problem. Next time I'll rtfm

matt0512 · 08-03-2012, 08:49 AM

Code:

# cd /var/log/packages
# ls curl* subversion* openssl*
curl-7.27.0-i486-1
openssl-1.0.1c-i486-2
subversion-1.7.5-i486-3

Code:

# ldd /usr/bin/curl |grep -e libcrypto -e libssl
        libssl.so.1 => /lib/libssl.so.1 (0xb73fd000)
        libcrypto.so.1 => /lib/libcrypto.so.1 (0xb7246000)
        libssl.so.0 => not found
        libcrypto.so.0 => not found

Code:

# ldd /usr/bin/svn |grep -e libcrypto -e libssl
        libssl.so.1 => /usr/lib/libssl.so.1 (0xb718c000)
        libcrypto.so.1 => /usr/lib/libcrypto.so.1 (0xb6fd5000)
        libssl.so.0 => not found
        libcrypto.so.0 => not found
        libssl.so.0 => not found
        libcrypto.so.0 => not found
        libssl.so.0 => not found
        libcrypto.so.0 => not found

Maybe it's a newbie question, but why latest curl and subversion packages link to both openssl libraries, the old *.so.0 and the new *.so.1?
I've read that the old libraries are available in openssl-solibs, but openssl package contains only the *.so.1. Aren't the new *.so.1 libraries enough?

willysr · 08-03-2012, 09:59 AM

On my system

Code:

ldd /usr/bin/curl | grep -e libcrypto -e libssl
        libssl.so.1 => /usr/lib/libssl.so.1 (0xb73de000)
        libcrypto.so.1 => /usr/lib/libcrypto.so.1 (0xb7227000)

ldd /usr/bin/svn |grep -e libcrypto -e libssl
        libssl.so.1 => /usr/lib/libssl.so.1 (0xb70db000)
        libcrypto.so.1 => /usr/lib/libcrypto.so.1 (0xb6f24000)

Perhaps you forgot to upgrade aaa_elflibs ?

e5150 · 08-03-2012, 10:23 AM

Quote:

Originally Posted by matt0512

[CODE]Maybe it's a newbie question, but why latest curl and subversion packages link to both openssl libraries, the old *.so.0 and the new *.so.1?
I've read that the old libraries are available in openssl-solibs, but openssl package contains only the *.so.1. Aren't the new *.so.1 libraries enough?

curl (through libcurl) links against libldap, which in turn links against libssl. So I'm guessing libssl.so.1 is what libcurl itself links against, but curl -> libcurl -> libldap -> libssl.so.0. If however, you've upgraded aaa_elflibs (which should contain both the new libldap and libssl.so.0) or openldap-client, then I have no idea...