current upgrade precautions (pre-pam)
by wirelessmc from LinuxQuestions.org on (#56Z8H)
I just posted on Alien Pastures below soliciting any precautions or package order dependencies. My two -current installs (KDE5/Plasma & KDE4) are both pre-pam so before I give this a go with slackpkg I wanted to post here first for any issues I might run into or avoid.
Thanks,
--wirelessmc
I maintain two s*64-current installs (one with Plasma/KDE5 and my main development branch still using KDE4). I haven't upgraded either since early February - so they are both pre-pam. I will start with the KDE4 install which I have backed up in anticipation of encountering issues. I have read most of the threads here but before I try this I will also post on LQ soliciting any precautions or package order dependencies.
In theory I should be able to just run slackpkg and everything will just go smoothly but I have backed up my /root and /usr partitions just in case.
Eric - Do you have any advise about package order (or any other dependencies that slackpkg won't account for) before I give this a go? I have installed several Slackbuild packages that I really don't wish to break.
Thanks,
--wirelessmc
I maintain two s*64-current installs (one with Plasma/KDE5 and my main development branch still using KDE4). I haven't upgraded either since early February - so they are both pre-pam. I will start with the KDE4 install which I have backed up in anticipation of encountering issues. I have read most of the threads here but before I try this I will also post on LQ soliciting any precautions or package order dependencies.
In theory I should be able to just run slackpkg and everything will just go smoothly but I have backed up my /root and /usr partitions just in case.
Eric - Do you have any advise about package order (or any other dependencies that slackpkg won't account for) before I give this a go? I have installed several Slackbuild packages that I really don't wish to break.