How to backout Slackware upgrades?

catkin · 12-10-2010, 09:43 PM

Hello

Is it possible to backout Slackware upgrades?

After the last upgrade, VirtualBox VMs will not start.

Best

Charles

Drakeo · 12-10-2010, 10:55 PM

you want to keep a mirror of Slackware. then use the upgrade text to revert. But if running current and want to go back to stable 13.1 then change your /etc/slackpkg/mirrors file to 13.1 and run slackpkg update then slackpkg upgrade-all then slackpkg install-new slackpkg clean-system this will get rid of all the packages that is not part of the distro.
remember clean get rid of everything even sbopkgs.
there is know reason for 13.1 not to start from what I see. if running current oh yes there is plenty of reasons.

catkin · 12-10-2010, 11:00 PM

Quote:

Originally Posted by Drakeo

there is know reason for 13.1 not to start from what I see.

Thanks Drakeo

Sorry -- should have said this is not -current.

I can't find any reason either but it doesn't work and rolling back the recent upgrade might help get a handle on the problem.

vdemuth · 12-11-2010, 03:48 AM

Saw this on my box, and just downloading the latest Vbox from the website cured the problem, and running current here so it should work on standard 13.1.

catkin · 12-11-2010, 06:09 AM

Quote:

Originally Posted by vdemuth

Saw this on my box, and just downloading the latest Vbox from the website cured the problem, and running current here so it should work on standard 13.1.

Thanks for that vdemuth

I will try the current VirtualBox version soon.

2handband · 12-11-2010, 06:34 AM

Is the VBox kernel module loaded?

Hangdog42 · 12-11-2010, 07:48 AM

I second the idea that it is an installation issue. The changes you reference in your other thread were from the end of October, and since then I've switched from VMware to Vbox using the Slackbuilds.org slackbuilds and I'm not having any trouble with my virtual machines.

catkin · 12-11-2010, 07:51 AM

Quote:

Originally Posted by catkin

Thanks for that vdemuth

I will try the current VirtualBox version soon.

That fixed it

catkin · 12-11-2010, 07:53 AM

Quote:

Originally Posted by 2handband

Is the VBox kernel module loaded?

They were according to /etc/rc.d/rc.vboxdrv status (accidentally omitted from other thread).

catkin · 12-11-2010, 07:57 AM

Quote:

Originally Posted by Hangdog42

I second the idea that it is an installation issue. The changes you reference in your other thread were from the end of October, and since then I've switched from VMware to Vbox using the Slackbuilds.org slackbuilds and I'm not having any trouble with my virtual machines.

Thanks Hangdog42

catkin · 12-11-2010, 08:00 AM

I'm still curious to know if it is possible to back out Slackware upgrades ...

Hangdog42 · 12-11-2010, 08:02 AM

Quote:

Originally Posted by catkin

I'm still curious to know if it is possible to back out Slackware upgrades ...

I think it is just a matter of re-installing the older packages. If I remember correctly, installlpkg doesn't do any sort of version checking, so "upgrading" with an older package removes the newer one and installs the older one.

Of course you do need an accurate list of what was upgraded in the first place and access to the older packages.

catkin · 12-11-2010, 08:37 AM

Quote:

Originally Posted by Hangdog42

I think it is just a matter of re-installing the older packages. If I remember correctly, installlpkg doesn't do any sort of version checking, so "upgrading" with an older package removes the newer one and installs the older one.

Of course you do need an accurate list of what was upgraded in the first place and access to the older packages.

Thanks Hangdog42

I always log the new packages but am less confident of having a record of what the previous packages were or of having the older packages. Would be neat to be able to roll back though; have added it to the TODO list.

allend · 12-11-2010, 09:13 AM

I use slackpkg for my updates and run it with DELALL=off in /etc/slackpkg/slackpkg.conf. After an update I do 'mv /var/cache/packages /var/cache/packages<date>'. This way I have the old packages available to downgrade and can easily check what was changed from the ChangeLog.

Hangdog42 · 12-11-2010, 12:03 PM

Quote:

Originally Posted by allend

I use slackpkg for my updates and run it with DELALL=off in /etc/slackpkg/slackpkg.conf. After an update I do 'mv /var/cache/packages /var/cache/packages<date>'. This way I have the old packages available to downgrade and can easily check what was changed from the ChangeLog.

That's a nice solution. Thanks!