I wanted to get security updates that have been added to Slack 14.1 so I thought that slackpkg may work for that but wanted to make sure I did not misunderstand how it works.

If I have it pointed to a mirror that looks in /slackware/slackware64-14.1/ then if I run slackpkg upgrade all will that get only the packages that have been updated ? Should you run install-new first ?

Will this cluster bomb the system or is this going to work?



I found a few threads that seem to indicate that this is supposed to work

Here's my script for updating Slackware. I got it from one of the members of my LUG. Enjoy.

If you have installed additional programs from Slackbuids, Alien Bob's repos, or other sources, you might want to take a look at the comments in /etc/slackpkg/blacklist. After the upgrade script runs, it will ask you whether you want to keep or overwrite the config files for upgraded packages. I normally select "p" for prompt and get prompted for each file, so I can elect not to overwrite those that I have modified.

You can run the commands separately or as a script. If as a script, do not run it unattended, as it requires user interaction.

Well that sounds promising

I will try it on the 14.2 RC1 box I am building

I should mention that my 14.1 box is anything but bog standard. Well anyway I have multimedia editing software and virtualization software installed. I tried the 14.2 RC1 in a virtual machine first So far so good.

Actually now that I think about it I got all kinds of things I don't think about until I need them

I am not looking forward to upgrading to 14.2 (well actually I am, just hate to break everything)

That's why I run --Current. Sometimes--very rarely--stuff breaks, because it's a testing version, but I can live with that if I don't have to upgrade from one version to another.

The last time I tried a Slackware version upgrade, I ended up running Debian because I broke the upgrade and took the easy way out. I got no beef with Debian--it's my second favorite after Slack--but I'm quite happy with --Current.

I've always managed the "upgrade" by having a separate /home partition and doing a full install (but not formatting /home). I save /etc and /var to /home/user/ for quick reference and then recompile any SBo packages after the install. I also document system changes, so it's not too time consuming (usually an hour or two) to get the system back to a similar state.

1 members found this post helpful.

1. Use mirror for 14.1
2. Run
If you don't upgrade to new version, you don't need install-new or clean-system.

1 members found this post helpful.

Hello,

To get security updates for Slackware stable, you can also use slackpkg upgrade patches.

--
SeB

1 members found this post helpful.

I think the slackpkg upgrade patches is what I am looking for.

If that updates the security related stuff that is what I am looking for.

Stable Slackware tree gets updates only in /patches, so "slackpkg upgrade-all" and "slackpkg upgrade patches" are equal.

2 members found this post helpful.

And current doesn't have any packages in patches so what is slackpkg upgrade patches actually used for?

patches is used for stable (released) versions. In case of current the new packages replaces the old one in whatever subdirectory (a, ap, etc.) it was. Phenixia2003 pointed out that this command can be used for Slackware stable , i.e. not for Slackware current.

1 members found this post helpful.

But, as it was pointed out already, I use
slackpkg update
slackpkg install-new
slackpkg upgrade-all
to upgrade 14.1 on my little netbook and nothing is missed because of it being in the patches directory.
The exact wording was
so "slackpkg upgrade-all" and "slackpkg upgrade patches" are equal.
I agree so I asked the obvious. What is slackpkg upgrade packages really good for?

Not sure if this is related but I tried the slackpkg upgrade patches and now when I try to run GL games like doo3 I get weird errors.

glxgears runs so I don't know what the deal is but here is the error I get

/usr/local/bin/doom3: line 6: /usr/local/games/doom3/doom.x86: No such file or directory

bash-4.2# cd /usr/local/games/doom3
bash-4.2# ls
CHANGES base doom3 doomded.x86 openurl.sh
License.txt d3xp doom3-dedicated libgcc_s.so.1 pb
README doom.x86 doom3.png libstdc++.so.6 version.info

as you can see doom.x86 is where it is supposed to be.

Same sort of thing happens with other games.

bash-4.2# heretic2
bash: /usr/local/bin/heretic2: No such file or directory

bash-4.2# cd /usr/local/bin/
bash-4.2# ls
doom3 qemu-microblazeel qemu-sparc32plus qemu-system-ppc
doom3-dedicated qemu-mips qemu-sparc64 qemu-system-ppc64
heretic2

I am stumped

You can get "No such file or directory" if you try to run x86_64 binary on i?86 architecture or vise versa (without multilib).
Are you sure the system before update was Slackware64 (64-bit) and not Slackware (32-bit)?

This is not related to slackpkg upgrade patches. The issue you encounter is that you have upgraded your slackware64/multilib without blacklisting the multilib version of packages glibc/gcc. Therefore, slackpkg has superseded some of them to the version found in patches directory, and more precisely the packages below :

To fix that, you need to reinstall the multilib version of these packages. To prevent that kind of issue in the future, you must blacklist the multilib version of gcc/glibc by adding the lines below in /etc/slackpkg/blacklist :
Alternatively, you can use the plugin slackpkg+ to manage the multilib (and more). For more about it, read this page.

Note: As opposed to slackpkg upgrade patches, slackpkg upgrade-all would have superseded all mutlilib version of glibc/gcc packages with their pure 64-bit counterpart found in entire slackware64 tree, and not just in patches directory.

--
SeB

2 members found this post helpful.