Slackware Current transition to next version (15?) - How would this work
 

I hope these questions makes sense. If not, please let me know and I'll do my best to clarify further.


Slackware current is constantly being updated, new kernels, package updates, etc.

Q1) Will there be a point where packages will stop being updated and the existing Current moves to the next version (15.0 or what ever)?

Q2) Will my existing installation of Current be migrated to the new version or will I need to do a clean install to get off current?

Once the next stable release is out current and stable will be the same for a short time, during that time you can change your current mirrors to the stable tree and everything should be smooth sailing.

1. Yes.

2. No.
At some point -current will be declared the next Stable release. If you have kept your -current installation up to date, you have the latest Stable version.

In the past, once the new Stable announcement has been made, the development team takes a couple of weeks off, well deserved, and then the process starts all over again, starting where they left off when the announcment was made. At that point you can leave your installation alone or you can continue to update it as the new -current which works towards the next stable releasae. Up to you. :)

Thanks for the information.

I was hoping it would be as simple as switching mirrors.

That's what I plan to do with most of my -current boxes. :)

actually thats a very pertinent question and its something I am going to have to face .

Some schools of thought if i have interpreted it correctly suggest knowing what your pkgs are and just do a fresh install eg :

https://docs.slackware.com/howtos:sl...:systemupgrade

Now I got current in September 2019 (so its not that old) but my kernel is: 4.19.75

if i look at the logs (current 64 bit) Thu Jan 9 21:57:44 UTC 2020 i see mention of
a/kernel-generic-5.4.10-i586-1.txz: Upgraded.


Now my approach to slackware is the gino d'acampo method "minimum effort maximum satisfaction"
.


I have been using slpkg (not slackpkg) with current 64 bit and i have at present a system where no package have deps clashes and everything works in harmony . Previously when i tried slackpkg it didn't go well.


So for me keeping it succinctly if i go the upgrade route i need to go from kernel 4.19.75 to maybe 5.4.10 everything in between and hope all the packages I have balanced & working don't break .



I just wonder if its worth the effort

secondly is there a "spoon fed" tutorial for not assuming anything ( i mean it may be obvious to you but not me) in a logical order.

Is that the kernel you are running on a 64-bit system?


Did you mean slackpkg+ ?


I use slackpkg for my 64-bit system to keep Slackware up to date

I do the same for my Slackware64-current systems.

Same here. I've been using slackpkg for years with no problems, though some updates will have updated config files (bind, apache, sendmail, ssh, etc) and "batch config overwrites" can (and usually will) cause headaches if you're not paying attention.

Tried slackpkg years ago and didn't care for it, so I do it "the old fashion way."
:)
upgradepkg --reinstall --install-new whatever-the-package-name.t?z

Indeed, as do I from time to time depending on the circumstances. However when needing to update multiple packages on multiple machines slackpkg is sooo much easier ;)

ho @gordie

bash-5.0$ uname -r
4.19.75
bash-5.0$ uname -m
x86_64
bash-5.0$

no i don't mean slackpkg+ i mean this : https://slackbuilds.org/repository/1.../?search=slpkg

once setup it eg
# Set Slackware release "stable" or "current". Default is "stable".
RELEASE=current

in /etc/slpkg/slpkg.conf etc

it is capable of installing a package and all its deps eg see attached image . i also use slackbuilds but slpkg is of occasion niffty

im aware of slackpkg:

[slackpkg is to be used to install official slackware packages from the official Slackware servers and to manage updates and upgrades. This tools is very useful for keeping a system up-to-date and for doing a distribution version upgrade without having to do a complete reinstall or having to download and burn a disk.
When attempting a version upgrade with slackpkg read the file UPGRADE.TXT from the installation disk to determine instala order and avoid breaking your system.]

its the last 4 words that worry me

Well if it's any help (I doubt it will be) I updated my kernel from 5.4.8 to 5.4.10 on my laptops along with everything else and everything is fine.

The wording is for upgrades.. From 14.1 to 14.2 or to current, etc.

In this case you're running current so when it branches into the next release all you should need to do (as confirmed) is (if using slackpkg) switch from the "Current" mirror to the new stable mirror and you're stable assuming you're up to date.

At least that's my understanding based on the comments provided. I'm comfortable with it

If you're really concerned, you could create a restore image via Clonezilla (or what ever)

If you have a problem after upgrading, revert back nothing lost except a little down time and some external storage space