Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
AFAIK such a thing is not kept by any "Rolling release" distro. What is your specific requirement for it?
The only thing I have ever felt the need for is the previous properly working version, in the event that some update introduces issues (e.g. vlc earlier this year). By backing up the most recent working OS to disk, you have that. It would be silly not to if you're using sdcards.
Ok at slackware.co.uk there is a cumulative repo, so you can go downgrading some package that you upgraded and the it had troubles for some reason. I have my BananaPi PRO where I use it for my asterisk server and mistakely
run slackpkg upgrade from 14.2+ current version to final 15.0 then for some reason i realized that it wont work, but too late, and some aaa and few other packages have been upgraded already. Now the trouble is that going back
is a pain as I dont have anymore the packages which were installed at the time, and the -current from that time moved forward and is now 15.0 . So doing an upgrade remotely without being there is a bit too critical for me.
The BPi still works ok, but some base stuff like cp, tar, sed are no longer working complaining that libacl does not find the correct glibc. So I saw I have 2 libacl versions installed and a link pointing to it.
Anyway long story short, I would like to correct my system and or revert it back or upgrade it. But without a working base tools installpkg, removepkg are not fully working.
The BPi still works ok, but some base stuff like cp, tar, sed are no longer working complaining that libacl does not find the correct glibc. So I saw I have 2 libacl versions installed and a link pointing to it.
14.2+ was the armv7-a port that ultimately became Slackware ARM 15.0.
From what you've said, it seems that you just need to upgrade to the 15.0 package set and any patches.
On another Slackware box, or within the 15.0 installer:
Code:
mkdir /mnt/bpistorage
mount /dev/whatever /mnt/bpistorage
ROOT=/mnt/bpistorage upgradepkg /path/to/slackwarearm-15.0/slackware/<series>/package*z
Upgrade the 'a' series first.
If there was a repo, you could revert like this:
Code:
cd /var/log/removed_packages
ls -ltr
and upgradepkg back to the previous versions of the most recently touched packages.
Hi drmozes, many thanks for this tip, but I think this wont work from remote. I am far away from my pi right now and will try to do that once i get close to the board. I think this would be a too risky task for doing it
over network from another side of the world.
No sure, i could even try it earlier but I am just scared that doing it over network for some reason it loose the connection and then even worst the tmux or screen got screwed up and then i am done .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.