how to restore an updated current to a prior date?
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
1. Does blender need an recompile?
2. Explain how exactly blender messes up.
3. Investigate exactly when blender broke and either correct the issue or report it upstream so it can be fixed, try compiling older versions of the suspect updated packages and upgrading them over the new ones until you find out where this started.
4. Start keeping backups so you can restore after a bad update.
5. Reinstall 14.2.
My guess its either 1. or started with mesa, llvm, xorg-server or xf86-video-*.
I already re-compiled it from source via slackbuilds, BLENDER then had the other one blender via slackbuilds installed, then downloaded it from the sight that does not need compiling and tried that one too and all three ways I gets things like this. oh and reinstall slack again - to go backwords I'd need to use the old dvd-iso I have but that'd take me way back .. it'd be a last resort - putting a pin in that option for now.
My guess its either 1. or started with mesa, llvm, xorg-server or xf86-video-*.
Video updates yep that is my guess too, that is why I was hoping I could backtrack it or whatever term is used to get it back the other versions of video drivers JUST before that update.
BW-userx, this is life with -current. It's for testing. It's *NOT* for production. If you have SBo applications on top of -current, they will break all the time and need rebuilding all the time. This is part of the testing process.
14.2 is not a backward step. 14.2 is the up-to-date release of Slackware. It would probably be a good investment of your time to start again with 14.2. Sorry if you were misled by the name '-current', but that is the traditional name for a testing branch. For example:
Quote:
"FreeBSD-CURRENT is the “bleeding edge” of FreeBSD development and FreeBSD-CURRENT users are expected to have a high degree of technical skill. Less technical users who wish to track a development branch should track FreeBSD-STABLE instead."
So I'd love to get the install prior to this one to see if that is what actually effected blender or not.
Unless you saved the old packages and/or files, it's gone. Using Eric's mirroring script does not do any sort of versioning control (which would get crazy huge with binary packages and the source tarballs). Once the mirror is updated, the old information is gone and is irretrievable.
As 55020 stated, -current is a testbed for Slackware and breakages are bound to happen. Every update is a potential broken package. Unless you have good reasons for it, it might be better to go back to 14.2. Any updates there should not break anything (except for the possibility of kernel updates and the 3rd-party packages that would need the kernel modules recompiled).
soooo -- installing just the 14.2 then it too updates after install due to the slackpkg update gpg - update install-new upgrade-all - so what is that all about then? then every so often if I remember correctly it still gets updates if one is using the # Slackware64-14.2 mirror sights. yes?
if yes - then is that to say that it is then stable?
2. is there a way to use Ailen Bob mirror-Slackware-current.sh to just mirror that standard 14.2 to create a DVD-iso for them updates to be put into a USB boot install stick?
all I got a get ( i think) is a proper rsync web address to use and place that in the script instead, and maybe a little tinkering to get that to work.
it still gets updates if one is using the # Slackware64-14.2 mirror sights. yes?
Yes. 14.2 gets security and bugfixes regularly. The security and bugfix updates for stable releases like 14.2 are carefully created so they don't break any existing programs.
Quote:
Originally Posted by BW-userx
is there a way to use Ailen Bob mirror-Slackware-current.sh to just mirror that standard 14.2
The answer is inside mirror-Slackware-current.sh itself.
Code:
# The slackware release we're mirroring (defaults to 'current').
# You can use the script's '-r' switch to alter this to another release,
# for instance mirror Slackware 13.37 by passing '-r 13.37' to the script.
So for example:
./mirror-Slackware-current.sh -r 14.2
yeah I think I got it, I just added it within the config file so I do not have to use that switch as I tried that before with the -f to pickup where I left off when trying this 14.2 yesterday and kept getting a error cannot use it with the -i or -r error. don't remember correctly. Only that it would not do both at the same time. So I set it aside until now.
Code:
receiving incremental file list
ChangeLog.txt
sent 50 bytes received 87,085 bytes 2,387.26 bytes/sec
total size is 389,651 speedup is 4.47
Wed Mar 22 12:48:04 CDT 2017 [26537]: No difference found, continuing anyway...
*** Using rsync.osuosl.org::slackware/slackware64-14.2 ***
this way I can take a few days to get that "latest" updates so when I install it I do not have to worry about time constants in updating it. This public wifi resets itself every 2 hrs.
1) There is only one good reason to run Slackware-current and that is to help testing it. I mean testing the stuff included in the genuine system started from a full Slackware-stable clean installation (most recent version) and then applying all updates listed in the ChangeLog for Slackware-current, preferably in the order in which they appear:
Remove all packages tagged "Removed."
Install all packages tagged "Added."
Upgrade all packages tagged "Rebuilt." or "Upgraded".
If something (part of Slackware) doesn't work as expected, then of course report it with all needed information to help investigating, but there should be no need for a rollback, unless/until it appears in the Changelog tagged as Removed or Upgraded or Rebuilt or Added.
2) That doesn't mean that one is not allowed to try third party packages like blender on top of a Slackware-current system, but then the user is on his or her own if something doesn't work after an update. There is a thread SBo scripts not building on current but as said in its first post: report issues here only if you have already tried the scripts from our repository and they won't build on a clean and full installation of Slackware current. If I am correct that is not the case for the system of BW-userx mentioned in this thread, that includes many other third party packages and customization.
Personally I am not even eager to bother if some of the very few SlackBuilds I maitan @ SBo doesn't compile in Slackware-current, until an expression like "beta" or "release candidate" appears in the Changelog. But of course others may do or feel otherwise.
PS I am writing this not to tell BW-userx how he should manage his systems, but rather to inform the many people that seem to consider (wrongly, in my opinion) running Slackware-current as a way to get a stable system with the "latest and the greatest" software releases.
Last edited by Didier Spaier; 03-22-2017 at 01:28 PM.
well I have a current dvd iso laying about so I burned it to a USB Stick installed Slack again this is the 14.2 release. 8:19.75 minutes installed.
now my user cannot keep networkManager connected to a connection, root does. lxdm didn't let me login root or user had to set it back to gdm (default loging manager) that is just for starters. lol ..
well I have a current dvd iso laying about so I burned it to a USB Stick installed Slack again this is the 14.2 release. 8:19.75 minutes installed.
now my user cannot keep networkManager connected to a connection, root does. lxdm didn't let me login root or user had to set it back to gdm (default loging manager) that is just for starters. lol ..
all this for blender .. woo hoo
lxdm works well here and as already said gdm is not shipped in Slackware... What really puzzles me is that your system can still boot
Last edited by Didier Spaier; 03-22-2017 at 04:15 PM.
well I have a current dvd iso laying about so I burned it to a USB Stick installed Slack again this is the 14.2 release. 8:19.75 minutes installed.
It's either -current or 14.2, not both. They are two entirely different things. 14.2 is the latest "stable" and -current is "unstable" and will eventually be the next stable release (probably 14.3 or 15.0).
If this is indeed 14.2, did you recompile those programs? If they were compiled on -current, it is very possible they're broken on 14.2.
It's either -current or 14.2, not both. They are two entirely different things. 14.2 is the latest "stable" and -current is "unstable" and will eventually be the next stable release (probably 14.3 or 15.0).
If this is indeed 14.2, did you recompile those programs? If they were compiled on -current, it is very possible they're broken on 14.2.
it is the download for current 14.2 prior to mirror change to make it current but it is not current current because current is not stable it is testing but 14.2 is current stable not to say that it is not current but it is current 14.2 is yes it is current but not testing current that is unstable current wtf change that naming conventions it is so confusing. Even you got confused.
and no I have not gotten that far yet as to recompiled anything I am waiting until I get that post update downloaded first. I did only recompile the lxdm but have not tested that yet. but that does not explain why Network Manager does not stay connected in my user account.
I'll figure it out later. (so yes I am in ROOT - don't tell no one its a secret... snicker snicker)
it is the download for current 14.2 prior to mirror change to make it current but it is not current current because current is not stable it is testing but 14.2 is current stable not to say that it is not current but it is current 14.2 is yes it is current but not testing current that is unstable current wtf change that naming conventions it is so confusing. Even you got confused.
Can I suggest you use "latest", "fully patched", or "up-to-date" 14.2 rather than "current"? Otherwise you'll just confuse everyone.
Can I suggest you use "latest", "fully patched", or "up-to-date" 14.2 rather than "current"? Otherwise you'll just confuse everyone.
this is that DVD-iso that one downloads off of the mirrors that I have that is 14.2 it is a few months old for sure, but is that not the reason for the update after install to make it the very latest 14.2 using the mirror listings in /etc/slackpkg/mirrors where it is divided up into 2 sections one is 14.2 and the other one on the lower half is current?
therefore it should resolve into that fully patched or up-to-date 14.2 when that install-new and upgrade-all have completed?
when that is fished taking place is when I will do the recompiling of Blender first to see if Blender stops doing that bleeding and strange behavior. Then recompile everything else I do suppose.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
