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.
After the update today, QMPlay2 loads with a small err notification window saying "QtSvg icon engine plugin doesn't exist. QMPlay2 will not scale up icons!" I've rebuilt QMPlay2 with the latest source code release from QMPlay2's git using the SlackBuild script provided by Alien Bob in his repository. The program seems to load and run fine so I don't see what it is complaining about. ldd shows Qt5 dependencies are satisfied.
Running "slackpkg clean-system" is an important part of keeping up to date with slackpkg, it removes old, obsolete packages that are no longer part of Slackware and yes, good third party packages too since they are not part of Slackware. This is what /etc/slackpkg/blacklist is for. You should put third party packages like those from "ponce" in /etc/slackpkg/blacklist. Then running "slackpkg clean-system" will only remove all other packages that are not or no longer part of Slackware. "slackpkg clean-system" gives you a chance to back out if there are packages listed that you don't want to remove.
To add ponce's packages to blacklist add "[0-9]+ponce" without the quotes to blacklist.
"slackpkg install-new" only searches for "Added" packages in ChangeLog.txt. Once those packages have been added to the system, they no long show up, unless you remove them for some reason.
slackpkg only handles Slackware packages. If you have a lot of third party packages, your should look in to adding slackpkg+ to the mix. The combination of slackgpkg with slackpkg+ make management of slackware with third party packages installed a breeze.
I've been guessing that you are using -current.
Yes, I am running -current and updated through the Mar 13 changelog. I have gone back to KDE Plasma 5 and everything seems to be working fine now. My zoom-linux starts without issue. It is magic. The KDE Plasma desktop has really great appearance and font rendering. It is not as bad a spaghetti system as was KDE4, but it is still too much glitter and too little explanation IMHO.
I have just installed slackpkg+, but I find the directions confusing. According to AlienBob, you should remove "[0-9]+alien" and similar from the /etc/slackpkg/blacklist file. However, the "slackpkg clean-system" command will remove those packages unless they are blacklisted. As you can see, I have 174 packages from the "ponce" repository.
Code:
$ ls /var/log/packages/ | grep ponce | wc -l
174
Here are the lines from /etc/slackpkg/blacklist:
Quote:
# Automated upgrade of kernel packages may not be wanted in some situations;
# uncomment the lines below if that fits your circumstances:
#
kernel-generic
kernel-huge
kernel-modules
kernel-source
kernel-headers
#
# nvidia
nvidia-kernel
nvidia-driver
#
# custom build ffmpeg
ffmpeg
# This one will blacklist all SBo packages:
[0-9]+_SBo
[0-9]+ponce
[0-9]+alien
#
I ran "slackpkg clean-system" after the the major update for ktown becoming vtown appeared to settle down. I just ran it again and don't think I have any non-current packages.
I deal with the "ponce" packages with sbopkg and .sqf queue files. I would not describe this process as a breeze, because my experience is that one must carefully search out all the dependencies and list them in the right order in the .sqf file. There was a script called "sqg" that could generate sqf files (sort of), but I can't find it with sbopkg-38.1. I think it might become available again. I am not sure why parsing the <pkg>.info files on the ponce repository is so difficult, but it seems a dependency list file in the form of one-liners "<pkg> dep1 dep2 dep3" should be feasible and would go a long way to making it easier to create the <pkg>.sqf files.
Basically, it appears my issues are solved for now. Thanks for your comments and help.
Yes, I am running -current and updated through the Mar 13 changelog. I have gone back to KDE Plasma 5 and everything seems to be working fine now. My zoom-linux starts without issue.
Glad it works now.
I deal with the "ponce" packages with sbopkg and .sqf queue files[/QUOTE]
I don't use sbopkg, but I suspect since you do, then you should not install slackpkg+ and continue to blacklist those third party packages.
This is what my blacklist would look like if I did not use slackpkg+
[/code]Regardless, 'slackpkg clean-system' does not remove any third party packages except those that are not blacklisted.
True but slackpkg+ also sometimes suffers from updates even midstream to the point where I always manually check what "clean-system" proposes to delete. One of those I've experienced is at the end, when presented with a handful of options for what to do with .new files, I have routinely selected (P)rompt and got "You have selected do nothing" and have to manually deal with each one.
I still want to know why there is so much "busy work" changing conf files meant at least 90% of the time for user preferences that are unlikely to change. I'm never going to want to even attempt to revert to 14.2 from Current, or ever change rc.local. If I change my mind, I will do what is needed,... then, but why must I do it 2-3 times a week? Who benefits? If anyone thinks I just don't like automation tradeoffs, you could be right so there's that.
One of those I've experienced is at the end, when presented with a handful of options for what to do with .new files, I have routinely selected (P)rompt and got "You have selected do nothing" and have to manually deal with each one.
I've seen that too, it's an annoying bug, but at least there's always `slackpkg new-config`.
True but slackpkg+ also sometimes suffers from updates even midstream to the point where I always manually check what "clean-system" proposes to delete. One of those I've experienced is at the end, when presented with a handful of options for what to do with .new files, I have routinely selected (P)rompt and got "You have selected do nothing" and have to manually deal with each one.
Aside from a few special case things I have very little issues with "clean-system". That's the great thing about having a dialog list to unselect or selected from or you can cancel out and figure out why.
The "You have selected do nothing" happens if you tapped a key or two along the way as the upgrade progressed. I've never seen it happen if I keep my paws away from the keyboard.
Aside from a few special case things I have very little issues with "clean-system". That's the great thing about having a dialog list to unselect or selected from or you can cancel out and figure out why.
Exactly as I mentioned. I always preview and select. It seems suspicion is a healthy POV bias with automation.
Quote:
Originally Posted by chrisretusn
The "You have selected do nothing" happens if you tapped a key or two along the way as the upgrade progressed. I've never seen it happen if I keep my paws away from the keyboard.
Hmmm good point. I guess I need to make a script to toggle screen power-saving off/on so I can stop repeatedly mashing a key to be able to see. This issue seems worse now that I'm using Display Port connection. Often the screen will not recover after a snooze. I'm hoping a better cable might solve that.
Hmmm good point. I guess I need to make a script to toggle screen power-saving off/on so I can stop repeatedly mashing a key to be able to see.
I've gotten in to the habit on waking up my monitor with the Ctrl key, Alt works too.
Quote:
This issue seems worse now that I'm using Display Port connection. Often the screen will not recover after a snooze. I'm hoping a better cable might solve that.
After the update today, QMPlay2 loads with a small err notification window saying "QtSvg icon engine plugin doesn't exist. QMPlay2 will not scale up icons!" I've rebuilt QMPlay2 with the latest source code release from QMPlay2's git using the SlackBuild script provided by Alien Bob in his repository. The program seems to load and run fine so I don't see what it is complaining about. ldd shows Qt5 dependencies are satisfied.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
so there's that.
This issue seems worse now that I'm using Display Port connection. Often the screen will not recover after a snooze. I'm hoping a better cable might solve that.
