Best way to keep Slackware 14.1 current upto date with the latest packages

Quicken2k · 11-07-2014, 07:57 AM

I would like to know what's the best way to keep Slackware 14.1-current updated (patcjes, apps, kde. etc.). I use sbopkg and slackpkg+ here and I really don't have the time to hunt down updates manually.

Mark

Alien Bob · 11-07-2014, 08:40 AM

Is it Slackware 14.1 or slackware-current that you have installed?

Using slackpkg+ , that should not be too hard either way. Slackware-current needs more attention because of the NEW packages and kernels that are added from time to time. Users of slackware-current are considered to be Beta testers and therefore need to know how to fix their system when an update is breaking your system.

For Slackware 14.1 (and older stable release) patched packages are issued from time to time and placed inside the /patches directory, and slackpkg should help you upgrading to them. Slackware-current is our development, you will never see "patches" because instead, the package in the distro itself will just be refreshed with the latest version.

Updates to 3rd party packages like the KDE in my ktown repository, can be managed using slackpkg+

Updates to the packages you built yourself using sbopkg can be maintained by using sbopkg and refreshing its content. Sbopkg will show you what needs to be rebuilt. Remember that there is no repository for slackware-current in SlackBuilds.org and the scripts that the site has for Slackware 14.1 will not always compile on slackware-current.

What is your real question? Did it not work for you? Are you hesitant to use slackpkg+ ? Do you need more pointers and background?

Eric

frankbell · 11-07-2014, 09:35 PM

Uncomment an appropriate repository in /etc/slackpkg/mirrors.

I use this script to update my Slackware machines.

"Install new" appears twice because it was originally the third line, after "upgrade-all." Then I ran into a problem in which "upgrade-all" required something that depended an a package installed by "install-new" (it's long story, but "upgrade-all" broke my system because it depended on a new package not yet installed, but I was able to boot to a Live CD and fix the problem). I left the existing "install-new" where it had been, after "upgrade-all" just in case; that case hasn't happened yet, but it can't hurt. (Now even I'm confused.)

Anyway, the script works when run by root.

Code:

#!/bin/bash
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg install-new
slackpkg clean-system

Do not run this script unattended; it requires human input.

This script will not update software that is not part of the official Slackware package list, that is, software that you may have installed after you installed Slackware.

If you are using packages from Alien Bob or from Slackbuilds, you can edit /etc/slackpkg/blacklist so that slackpkg does not prompt you to remove those packages.

hitest · 11-07-2014, 10:07 PM

I would also add in slackpkg update gpg as the first command.

enorbet · 11-08-2014, 10:35 PM

I am truly sorry if this seems offensive but I can't help but "call 'em as I see 'em". I see this sort of "I don't have time" crap all the time. Odd thing is it is almost always from people who don't use Slackware and post it as some kind of jab, I suppose to bolster their need to be "new, improved and The Shiny Best (in their own eyes)".

It reminds me of the story of the Young Bull and the Old Bull and for exactly the same kinds of attitude and performance. It cracks me up (when it doesn't just piss me off) to see people say they don't have time to maintain their system but apparently think they do have the time to repair it when it breaks - Stitch in time, et al. Seriously, do you expect your car to work reliably like that? Would you honestly fail to do routine maintenance but just have it washed and waxed regularly?

Time spent as an investment, not an optional "cost", is performance wise and productive on many levels.

So, OP, please inform as to what version of Slack you use(d), when, and for how long.

moisespedro · 11-08-2014, 10:40 PM

enorbet, I think you overthought what he posted.

Quicken2k · 11-09-2014, 08:37 AM

Quote:

Originally Posted by Alien Bob

Is it Slackware 14.1 or slackware-current that you have installed?

Using slackpkg+ , that should not be too hard either way. Slackware-current needs more attention because of the NEW packages and kernels that are added from time to time. Users of slackware-current are considered to be Beta testers and therefore need to know how to fix their system when an update is breaking your system.

For Slackware 14.1 (and older stable release) patched packages are issued from time to time and placed inside the /patches directory, and slackpkg should help you upgrading to them. Slackware-current is our development, you will never see "patches" because instead, the package in the distro itself will just be refreshed with the latest version.

Updates to 3rd party packages like the KDE in my ktown repository, can be managed using slackpkg+

Updates to the packages you built yourself using sbopkg can be maintained by using sbopkg and refreshing its content. Sbopkg will show you what needs to be rebuilt. Remember that there is no repository for slackware-current in SlackBuilds.org and the scripts that the site has for Slackware 14.1 will not always compile on slackware-current.

What is your real question? Did it not work for you? Are you hesitant to use slackpkg+ ? Do you need more pointers and background?

Eric

How did you know there was a real question?

Let me clarify this. Using slackpkg+ I did slackpkg upgrade ktown it installed kde 4.14, however it's listing kde 4.10 as an upgrade. This is where I'm confused.

p.s since installing kde 4.14 the dolphin file manger fails to start.

EYo · 11-09-2014, 09:00 AM

Hi Quicken2k,

To be blunt, I searched and found that you did ask this question before:
http://www.linuxquestions.org/questi...6/#post5198671

The answer is there. In fact there are quite a few informative threads, Yet Another Downgrade Question.

If it's 14.1 and not current, here's another helpful link

:
http://www.linuxquestions.org/questi...4/#post5247158

linuxtinker · 11-09-2014, 09:04 AM

In your /etc/slackpkg/slackpkgplus.conf do you have your PKGS_PRIORITY= set up in the right order, also make sure you are using the correct Repos for your version of slack ex: 14.1/x86_64 or current/x86_64. A little more description of your Setup may help.. 14.1 Current x86_64 ??? also may want to post your slackpkgplus.conf file..

Quicken2k · 11-09-2014, 12:50 PM

Quote:

Originally Posted by linuxtinker

In your /etc/slackpkg/slackpkgplus.conf do you have your PKGS_PRIORITY= set up in the right order, also make sure you are using the correct Repos for your version of slack ex: 14.1/x86_64 or current/x86_64. A little more description of your Setup may help.. 14.1 Current x86_64 ??? also may want to post your slackpkgplus.conf file..

Sorry forgot about the other post

Code:

slackpkgplus.conf

# If you want a multilib system, uncomment the multilib repository and set:
#PKGS_PRIORITY=( multilib:.* )
#
# (Use /usr/doc/slackpkg+-*/setupmultilib.sh to setup a multilib configuration)

# List repositories you want to use (defined below)
# remember to launch 'slackpkg update' if you modify that row.
REPOPLUS=( slackpkgplus alienbob ktown slacky )


# Define mirrors (uncomment one or more mirror; remember to add it to REPOPLUS)
# Note: only multilib,alienbob,restricted,slacky repositories support GPG. If you add others
#       you may need to disable gpg check in slackpkg.conf

# Slackware 14.1 - x86_64
#MIRRORPLUS['multilib']=http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1/x86_64/
MIRRORPLUS['alienbob']=http://taper.alienbase.nl/mirrors/people/alien/sbrepos/14.1/x86_64/
MIRRORPLUS['restricted']=http://taper.alienbase.nl/mirrors/people/alien/restricted_sbrepos/14.1/x86_64/
MIRRORPLUS['slacky']=http://repository.slacky.eu/slackware64-14.1/
MIRRORPLUS['ktown']=http://taper.alienbase.nl/mirrors/alien-kde/current/latest/x86_64/

# use this to keep the slackpkg+ package updated
MIRRORPLUS['slackpkgplus']=http://slakfinder.org/slackpkg+/

# Slackware current - x86_64
#MIRRORPLUS['multilib']=http://taper.alienbase.nl/mirrors/people/alien/multilib/current/
#MIRRORPLUS['zerouno']=http://www.z01.eu/repo-slack/slackware64-current/

# Local repository:
#MIRRORPLUS['alienbob']=file://repositories/alien/sbrepos/14.1/x86/
#
# Local packages (you do not need metadata nor 'slackpkg update' command):
#MIRRORPLUS['myrepo']=dir://repositories/mypackages/


#
# Supported Repositories (see /usr/doc/slackpkg+-* for details):
#

#Supports GPG
#slackpkgplus:  http://slakfinder.org/slackpkg+/
#multilib:      http://taper.alienbase.nl/mirrors/people/alien/multilib/{13.37,14.0,14.1,current}/
#alienbob:      http://taper.alienbase.nl/mirrors/people/alien/sbrepos/{13.37,14.0,14.1,current}/{x86,x86_64}/
#ktown:         http://taper.alienbase.nl/mirrors/alien-kde/{13.37,14.0,14.1,current}/latest/{x86,x86_64}/
#restricted:    http://taper.alienbase.nl/mirrors/people/alien/restricted_sbrepos/{13.37,14.0,14.1,current}/{x86,x86_64}/
#slacky:        http://repository.slacky.eu/slackware{,64}-{13.37,14.0,14.1}/
#mled:          http://www.microlinux.fr/slackware/MLED-{14.0,14.1}-{32,64}bit/
#mles:          http://www.microlinux.fr/slackware/MLES-{14.0,14.1}-{32,64}bit/
#msb:           http://slackware.org.uk/msb/{14.0,14.1}/{1.6,1.8}/{x86,x86_64}/
#slackers:      http://www.slackers.it/repository/
#slacke17:      http://ngc891.blogdns.net/pub/slacke17/slackware{,64,arm}-{14.0,14.1}/
#studioware:    http://studioware.org/files/packages/slackware{,64}-{13.37,14.0,14.1}/
#slackonly:      http://slackonly.com/pub/packages/14.1-x86_64/
#
#Does NOT support GPG
#salixos(*):    http://download.salixos.org/{i486,x86_64}/{13.37,14.0,14.1}/
#salixext:      http://people.salixos.org/ralvex/repository/x86_64/{14.0,14.1}/
#rlworkman(*):  http://rlworkman.net/pkgs/{13.37,14.0,14.1}/
#slackel:       http://www.slackel.gr/repo/{i486,x86_64}/current/

blacklist.conf

Code:

  GNU nano 2.3.6                                          File: blacklist                                                                                            

# This is a blacklist file. Any packages listed here won't be
# upgraded, removed, or installed by slackpkg.
#
# The correct syntax is:
#
# To blacklist the package xorg-server-1.6.3-x86_64-1 the line will be:
# xorg-server
#
# DON'T put any space(s) before or after the package name or regexp.
# If you do this, the blacklist will NOT work.

#
# Automated upgrade of kernel packages aren't a good idea (and you need to
# run "lilo" after upgrade). If you think the same, uncomment the lines
# below
#
#kernel-firmware
#kernel-generic
#kernel-generic-smp
#kernel-headers
#kernel-huge
#kernel-huge-smp
#kernel-modules
#kernel-modules-smp
#kernel-source

#
# aaa_elflibs can't be updated.
#
aaa_elflibs

# You can blacklist using regular expressions.
#
# Don't use *full* regex here, because all of the following
# will be checked for the regex: series, name, version, arch,
# build and fullname.
#
# This one will blacklist all SBo packages:
[0-9]+_SBo
[0-9]+alien

slackpkg file-search kde output: (truncated)

Code:

  upgrade                                           okular-4.14.2-x86_64-1alien --> okular-4.10.5-x86_64-1  
  upgrade                                           oxygen-gtk2-1.4.5-x86_64-1alien --> oxygen-gtk2-1.4.0-x86_64-1  
  upgrade                                           oxygen-gtk3-1.3.1-x86_64-1alien --> oxygen-gtk3-1.2.0-x86_64-1  
  upgrade                                           oxygen-icons-4.14.2-x86_64-1alien --> oxygen-icons-4.10.5-x86_64-1  
  upgrade                                           pairs-4.14.2-x86_64-1alien --> pairs-4.10.5-x86_64-1

That upgrade is a downgrade. It also didn't install all of KDE 4.14 still alot in the list that says it's uninstalled.

Sorry, again if this is all a little confusing.

Quicken2k
Mark

bassmadrigal · 11-10-2014, 09:22 AM

Quote:

Originally Posted by Quicken2k

Code:

slackpkgplus.conf

# If you want a multilib system, uncomment the multilib repository and set:
#PKGS_PRIORITY=( multilib:.* )

Well, there's your problem. You don't have any priorities set up. That means it's just going to look for changes to your current packages. Change that to be something like:

Code:

PKGS_PRIORITY=( multilib:.* ktown:.* alienbob:.* slacky:.*)

This will put all those repositories at a higher priority than stock slackware, which should remove your "upgrade" problem.