[SOLVED] There is no *GLOBAL UPDATE* for Slackware 13.1 software, right?

Robert.Thompson · 01-19-2011, 12:49 PM

Hello:

If this is correct, how do you know if there updates available?

Do you need to down load and install the individual updated packages?

Sorry for this but I think that I am confused, or worse, not.

Thanks,

tsg · 01-19-2011, 12:51 PM

I think slackpkg is what you're looking for.

iamthat · 01-19-2011, 01:02 PM

slapt-get

Quote:

root[bonsai]# slapt-get --help
slapt-get - Jason Woodward <woodwardj at jaos dot org>
An implementation of the Debian APT system to Slackware
Usage:
slapt-get [option(s)] [target]

Targets:
--update|-u - retrieve pkg data from MIRROR
--upgrade - upgrade installed pkgs
--dist-upgrade - upgrade to newer release
--install|-i [pkg name(s)] - install specified pkg(s)
--install-set [disk set(s)] - install specified disk set(s)
--remove [pkg name(s)] - remove specified pkg(s)
--show [pkg name(s)] - show pkg(s) description
--filelist [pkg name(s)] - show pkg(s) installed files
--search [expression] - search available pkgs
--list - list pkgs
--available - list available pkgs
--installed - list installed pkgs
--clean - purge cached pkgs
--autoclean - only purge cache of older, unreacheable pkgs
--add-keys - retrieve GPG keys for sources
--help|-h - display this help and exit
--version - print version and license info

Options:
--download-only|-d - only download pkg on install/upgrade
--simulate|-s - show pkgs to be installed/upgraded
--no-prompt|-y - do not prompt during install/upgrade
--prompt|-p - always prompt during install/upgrade
--reinstall - reinstall the pkg
--ignore-excludes - install/upgrade excludes
--no-md5 - do not perform md5 check sum
--no-dep - skip dependency check
--ignore-dep - ignore dependency failures
--print-uris - print URIs only, do not download
--show-stats|-S - show download statistics
--config|-c [] - specify alternate slapt-getrc location
--remove-obsolete - remove obsolete packages
--retry [] - specify number of download retry attempts
--no-upgrade - install package, do not attempt to upgrade

hitest · 01-19-2011, 01:03 PM

Quote:

Originally Posted by Robert.Thompson

Hello:

If this is correct, how do you know if there updates available?

Do you need to down load and install the individual updated packages?

Sorry for this but I think that I am confused, or worse, not.

Thanks,

As mentioned in the previous post slackpkg is the utility that you are looking for. You will need to un-comment one mirror in /etc/slackpkg/mirrors, then save that file. Then issue these commands in this order:

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

These commands will update your 13.1 install and download, install the available security patches for your system. The slackpkg utility comes with Slackware 13.1.

See this link:

http://www.slackpkg.org/documentation.html

hitest · 01-19-2011, 01:04 PM

Quote:

Originally Posted by iamthat

slapt-get

This utility is not officially supported or endorsed by Slackware. I'm not condemning your choice, just pointing this out for the OP.

dugan · 01-19-2011, 01:05 PM

There's slackpkg for the packages in the distribution.

Most of your third party packages are probably from SlackBuilds.org. You can manage those (including updating them) with sbopkg.

Robert.Thompson · 01-19-2011, 02:04 PM

Thank you.

I also went to my new favorite Slackware source of info: http://genek.net/LinuxAdventures/sysadmin/slackpkg.html

Marking as SOLVED

lumak · 01-19-2011, 06:40 PM

All you really have to do is check the /patches directory in any Slackware mirror then run 'upgradepkg --install-new <package>'

The --install-new isn't generally needed for patches because a Full install already has them installed.. Unless Slackware had to randomly update to a package that split it self or requires a new dependency.

This is what slackpkg would do for you. It's just easier to run slackpkg in a chron job and forget about it.

hitest · 01-20-2011, 05:42 AM

Removed by me. redundant post.

dive · 01-20-2011, 10:53 AM

Quote:

Originally Posted by lumak

It's just easier to run slackpkg in a chron job and forget about it.

In most peoples opinion an automated upgrade system like that is not a good idea and can be unsafe. Anyway slackpkg requires user input.

tsg · 01-20-2011, 11:08 AM

Quote:

Originally Posted by dive

In most peoples opinion an automated upgrade system like that is not a good idea and can be unsafe. Anyway slackpkg requires user input.

Slackpkg can be run in batch mode with a default-answer parameter.

PDock · 01-20-2011, 03:50 PM

For those who like to read a change log before jumping in with both feet, there is an alternative to slackpkg via cron.
Go to the Mailing Lists tab at Slackware.com, read the text, subscribe slackware-security. Get you email, look in /var/log/packages, see no match, and forget about it.

2handband · 01-20-2011, 04:05 PM

Quote:

Originally Posted by tsg

Slackpkg can be run in batch mode with a default-answer parameter.

Can you elaborate a little on how that's done?

tsg · 01-21-2011, 08:31 AM

Quote:

Originally Posted by 2handband

Can you elaborate a little on how that's done?

For example:

Code:

slackpkg -batch=on -default_answer=y upgrade-all

Any option in the slackpkg.conf file can be given as a parameter on the command line.

Slax-Dude · 01-21-2011, 08:58 AM

Quote:

Originally Posted by 2handband

Can you elaborate a little on how that's done?

This is the best way to keep your slackware stable updated:

Code:

slackpkg -batch=on update
slackpkg -batch=on -default_answer=y -download_all=on upgrade patches

On stable, all new packages will be on /patches only

Put that in a batch script and run it on shutdown, boot-up, with cron or even manually

EDIT: damn, beaten by tsg (hehehe)