Re: CRITICAL ISSUE: libc.so.6 lost in slackpkg upgrade-all

On 15/03/2013 13:27, Rich Shepard wrote:
> On Fri, 15 Mar 2013, Jason Sizemore wrote:
>
>> Also have to agree with OSU. I have always had good luck with them. The
>> OSU open source lab is a great hoster of open source projects. Including
>> Slackware : ) So always get my updates from them. I also use them for
>> Centos stuff at work.  This may be just a one off glitch.
>> http://en.wikipedia.org/wiki/Open_Source_Lab
>
> Jason,
>
>   Yes, it is a one-off. I sucessfully ran slackpkg updates on the Sony 
> Vaio
> before yesterday and on the other hosts on the LAN. The OSUOSL is only a
> couple of hours down the Interstate from me so I use it for all the FOSS
> applications they host there.
>
>   I just read Robby's glibc HOWTO and will follow his instructions later
> this morning. As a non-computer-professional user I can often fix 
> things my
> self based on years of use, but sometimes it's a brand-new situation and
> this mail list always comes through.
>
> Regards,
>
> Rich
>

Hi Rich,

To prevent this from happening in the future:
Edit /etc/slackpkg/blacklist with your favourite editor
Add the following to the file:


    # The gcc compiler suite:
    gcc
    gcc-g++
    gcc-gfortran
    gcc-gnat
    gcc-java
    gcc-objc

    # The GNU libc libraries:
    glibc
    glibc-i18n
    glibc-profile
    glibc-solibs
    glibc-zoneinfo
    glibc-debug


# kernel-ide
kernel-modules
kernel-source
kernel-headers
kernel-firmware
kernel-generic
kernel-huge

This will prevent update-all from updating these libraries. You can 
upgrade them individually.

Best,

John

_______________________________________________
slackware mailing list
[email protected]
https://mailman.lug.org.uk/mailman/listinfo/slackware