slack64-current multilib slackpkg upgrade

portia · 01-05-2010, 10:05 AM

A few weeks ago I made my slack64-current multilib. As per tutorial I blacklisted glibc and gcc in /etc/slackpkg/blacklist:

Code:

# run "lilo" after upgrade). If you think the same, uncomment the lines
# below 
#
kernel-ide
kernel-modules
kernel-source
kernel-headers

#
# aaa_elflibs can't be updated.
#
aaa_elflibs
glibc
gcc
#
# Now we can

When I did slackpkg update and upgrade-all

I got all the gcc* glibc* kernel* packages available for an upgrade. What am I doing wrong?

If I actually upgrade the kernel that way and then run lilo, will it keep the lilo.conf entry of the old kernel? Will it remove the old kernel from the system?

TIA

Didier Spaier · 01-05-2010, 10:35 AM

At present slackpkg understand only full package names in blacklist.

So you should either list all packages whose name begin with glibc of gcc, or set "DEFAULT_ANSWER=n" in /etc/slackpkg/slackpkg.conf

slackass · 01-05-2010, 10:53 AM

Try this:

gcc
gcc-g++
gcc-gfortran
gcc-gnat
gcc-java
gcc-objc
glibc
glibc-i18n
glibc-profile
glibc-solibs
glibc-zoneinfo

samac · 01-05-2010, 11:41 AM

Quote:

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

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

This is what I have.

samac

portia · 01-05-2010, 02:47 PM

Did the trick - thanks!