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.
We probably need to keep a backup of packages from a previous update so we can revert back to them if something in a new update to Current breaks something in Plasma 5. What would be an easy and elegant way to do that?
Keep a local archive.
Personally, I use slackpkg for doing updates, with DELALL=off in my /etc/slackpkg/slackpkg.conf.
After an update, I run my script to archive the update.
Code:
# Command to move packages cached after slackpkg is run
mv /var/cache/packages /var/cache/packages$(date +%Y%m%d)
If the local archive starts to get too large, then I run my (easy but not elegant) script to remove all archived packages with more than two newer versions.
Code:
#!/bin/sh
# Script to clean up /var/cache/packages* archive
# Remove any old files
rm /tmp/list*
# Get a list of *.t?z archive files
find /var/cache -name "*.t?z" > /tmp/list1
# Get a list of package names without build, arch, version
cat /tmp/list1 | rev | cut -d"/" -f1 | cut -d"-" -f4- | rev > /tmp/list2
# Get a list of dates
cat /tmp/list1 | cut -d"/" -f4 | sed "s/packages//" > /tmp/list3
# Paste the lists together
paste /tmp/list1 /tmp/list2 /tmp/list3 > /tmp/list4
# Sort the list by package name then date(reverse order)
sort --key=2,3r /tmp/list4 > /tmp/list5
# Get a list of packages with 2 later versions
awk '++dups[$2] > 2' /tmp/list5 > /tmp/list6
# Cut the first column from the list
cut -f1 /tmp/list6 > /tmp/list7
# Delete the older files
while read line; do
rm "$line"{,.asc}
done < /tmp/list7
If you found a way for us to clone Eric, that would be a brilliant Plan To Take Over The World.
Imagine squadrons of Erics building many, many, many packages. Ubuntu would have to run for its money...
Unless then, sadly for us, Eric is just one man.
That would be awesome. I cannot express how much I am indebted to this one guy. Now I'm without Plasma and I have severe withdrawal symptoms. Xfce is awesome but I feel I'm working with my hands tied
That would be awesome. I cannot express how much I am indebted to this one guy. Now I'm without Plasma and I have severe withdrawal symptoms. Xfce is awesome but I feel I'm working with my hands tied
I'm going to give you a prescription for a good sleep cure
I ran the update this morning and KDE failed to start. I should have checked here first......
However, I have a local copy of the current tree not updated. I never update that until all is good. I reverted only the icu4c package and KDE is back in business.
There may yet be other problems, but I am working out of town, leaving again Sunday, so it should only be a minimal impact - if any.
On my 32bit PC the new package icu4c 60.1 crashing alien's libreoffice 5.4.3.
Going back to the previous version icu4c 56.1 is worse. Also crash Httpd and NetworkManager.
Something that you can do is install the previous icu4c package, and then install the new one on top of it (with installpkg, not upgradepkg). Once everything has been recompiled to use the new one, installing the new one again with upgradepkg --reinstall will remove any leftovers from the old one.
Something that you can do is install the previous icu4c package, and then install the new one on top of it (with installpkg, not upgradepkg). Once everything has been recompiled to use the new one, installing the new one again with upgradepkg --reinstall will remove any leftovers from the old one.
Why I feel that our BDFL thought "So, you guys had become sick of testing the kernel and you want some new toys to play with? So be it..."
Then, he pushed the new ICU and everything was broken ...
PS. Please do not search that forum for "who the hell proposed to leave the kernel away for some time?" Or, at least, if you find the response, please try to act civil.
Last edited by Darth Vader; 12-08-2017 at 08:50 AM.
Why I feel that our BDFL thought "So, you guys had become sick of testing the kernel and you want some new toys to play with? So be it..."
Then, he pushed the new ICU and everything was broken ...
PS. Please do not search that forum for "who the hell proposed to leave the kernel away for some time?" Or, at least, if you find the response, please try to act civil.
I'm still in shock that you beat Current to Plasma 5
Well, I intend to try, in one of my computers, to extend the legacy support given by the Eric's Plasma, until to offer me enough support to run that specific program I need.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.