Alternative update approach to slackpkg - request for testing/feedback

0XBF · 11-24-2023, 03:12 PM

Quote:

Originally Posted by GazL

Release 3.3 pushed to github.

It will ignore the older versions of duplicate installed packages rather than aborting.

0XBF, give that one a try. I think it'll allow you to do what you want.

Done. I gave it a test by installing several older kernel-huge packages at once. With '/kernel-huge-' blacklisted, "slackscan -u -" runs as expected and doesn't mention the kernel-huge package. When the blacklist is removed, then it offers just the latest version of the kernel-huge package from "slackscan -u -". That will solve my only gripe with slackscan just fine. :-)

Quote:

Originally Posted by GazL

In slackscan the blacklist preforms a slightly different function to slackpkg. In combination with the 'filter' list, it removes packages from the list of available packages rather than telling slackscan to ignore the package entirely, which is why adding a package to the blacklist will generate removals for that package. The 'protect' file is the closest we have to an 'ignore' feature, but it only works for removals. I added it to protect the user from accidentally removing an essential package and breaking their system — hence its name.

If you want to ignore packages in the install/upgrade lists then using 'grep -v' on the slackscan output is the solution.

I figured there was a reason why it wasn't a simple fix to just ignore packages on the blacklist. Your 3.3 version solves the problem just as well though.

The 'protect' file is the only one I don't really use. You gave a bunch of defaults there which is fine. Between the 'scan', 'filter' and 'blacklist' files I have a nice simple setup to keep my machines upgraded from my local mirrors and third party package builds. I ended up making a simple 'dialog' based menu and checklist system that gets lists from slackscan and handles the upgrades. Been working a treat for a few months now.

GazL · 11-24-2023, 06:02 PM

Great. Glad you're happy.

I'm not anticipating any further changes, so if folks want to grab the latest version, now's as good a time as any.

Enjoy.

GazL · 12-08-2023, 12:28 PM

Release 3.4 has been pushed to github

Changes:

slackscan now has a '-c' option to write change statistics to stdout.
To help users identify when changes are ready to be processed, slackscan now uses new exit codes:
0 - successful run, changes identified.
2 - successful run, no changes identified.
16 - Critical error.

Users that use slackscan from within their own scripts will need to ensure that they are updated to reflect the new exit codes.
slackup now shares slackscan's version number (3.4) and they will remain unified going forward.

Example run showing new features:

Code:

# slackscan -c
# Package Change Statistics
#
# Install: 1
# Upgrade: 0
# Remove: 0
# echo $?
0
# slackscan -i -
/local/slackware/mirror/slackware64-15.0/patches/packages/rdfind-1.6.0-x86_64-1_slack15.0.txz
# TERSE=1 slackup -six
gpg: Signature made Wed 06 Dec 2023 20:31:44 GMT using DSA key ID 40102233
gpg: Good signature from "Slackware Linux Project <security@slackware.com>"
Installing: rdfind-1.6.0-x86_64-1_slack15.0: redundant data finder ..... [ 140K]
# slackscan -c
# Package Change Statistics
#
# Install: 0
# Upgrade: 0
# Remove: 0
# echo $?
2
#

GazL · 12-09-2023, 06:32 AM

On reflection I think it might be more in-keeping with how other tools tend to work to have slackscan output the scan statistics by default and give it a '-q' (quiet) option to silence it.

I'll make a quick change before anyone gets used to the behaviour of 3.4.

GazL · 12-09-2023, 07:39 AM

Release 3.5 now pushed.

Default output is now as follows:

Code:

# slackscan
# Package Installs: 0
# Package Upgrades: 0
# Package Removals: 0

can be suppressed with -q.

Apologies to any early-adopters of 3.4 for the disruption, but IMO this is better and more in-keeping with other tools.

slalik · 12-09-2023, 09:30 AM

Do these changes affect slackup? My script doesn't use slackscan directly, only through slackup.

GazL · 12-09-2023, 09:38 AM

Slackup still works as before: same output and exit codes.

The slackup in 3.5 has been changed to call slackscan -q, so you won't see any difference.

If people want it, I could make it output these stats in the comments that get generated when you use slackup with the -c option, but they'll be the stats found by slackscan and not necessarily reflect the output of slackup, which will be further reduced by command-line args. My view is that it's probably best not to.

I could also make slackup return 2 when it generates nothing if folk want that.

GazL · 12-09-2023, 10:31 AM

BTW,

Code:

# slackscan -p current
# Package Installs: 93
# Package Upgrades: 1187
# Package Removals: 62

someone has been busy!

The removals are likely mostly my additional packages as I've not added their directory into the 'current' profile, but that's a lot of changes since 15.0

GazL · Today, 07:49 AM

Release 3.6 is now available.

User visible changes:

New slackscan option '-I' will cause slackscan to ignore the package database (i.e. all installed packages). All available packages will be treated as 'new' (i.e. identifed for install).

This new option may be useful for anyone wanting to create a full list of available packages once slackscan's 'scan', 'filter', and 'blacklist' have been applied.
slackscan will now exit rc=8 if a 'gpg --verify' fails for the CHECKSUMS.md5 file.

Other than those, just some small code cleanups and man-page fixes in this one.