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.
Strange. My slackpkg does not detect kernel packages to update. It's upgraded only firmware package.
But i didn't blacklist kernel packages:
Code:
#grep kernel /etc/slackpkg/blacklist
# Automated upgrade of kernel packages may not be wanted in some situations;
# kernel-headers should *not* be blacklisted:
#kernel-generic.*
#kernel-huge.*
#kernel-modules.*
#kernel-source
To be sure:
Code:
# grep -v ^# /etc/slackpkg/blacklist | sed '/^$/d'
Note:
kernel package is : linux-*
kernel-* is only for Slackware-current
Hmmm... this could be because I didn't remove the previous kernels in /patches, figuring it would be safer to leave a fallback for a bit in case of regressions.
Hmmm... this could be because I didn't remove the previous kernels in /patches, figuring it would be safer to leave a fallback for a bit in case of regressions.
Hmmm... this could be because I didn't remove the previous kernels in /patches, figuring it would be safer to leave a fallback for a bit in case of regressions.
No luck with blacklisting 5.15.117 at all. I think it has to do with the order slackpkg builds its pkglist as moving the 5.15.117 entries below the 5.15.139 ones in /var/lib/slackpkg/pkglist (or just removing them), it finally shows up as an upgrade. I think this stems from the order of https://slackware.osuosl.org/slackwa...s/PACKAGES.TXT
Edit: Also note it's not in the Changelog, but the old kernels got moved to patches/packages/old-linux-5.15.117: https://mirrors.slackware.com/slackw...inux-5.15.117/, presumably to help slackpkg users (see above posts).
Last edited by drumz; 11-22-2023 at 02:48 PM.
Reason: Additional information added.
Also note it's not in the Changelog, but the old kernels got moved to patches/packages/old-linux-5.15.117: https://mirrors.slackware.com/slackw...inux-5.15.117/, presumably to help slackpkg users (see above posts).
Thanks, Mr. Volkerding. Upgraded to the new kernel without incident.
Edit: Also note it's not in the Changelog, but the old kernels got moved to patches/packages/old-linux-5.15.117: https://mirrors.slackware.com/slackw...inux-5.15.117/, presumably to help slackpkg users (see above posts).
I don't happen to use slackpkg, but I do use a few homegrown scripts to manage upgrades on my systems, and I don't recall if I've seen this convention in previously releases, but it would probably be worth documenting this convention somewhere, or at least mention it in the Changelog.
Funny thing, I noticed the old-linux-5.15.117 directory in an rsync log a day or two after a previous rsync that had the newer kernel.
If this particular location is convenient for slackpkg users, then I guess that's helpful, but pasture seems like the expected home for old packages that might still be important for rollbacks.
'slackscan' users will need to adjust there blacklists again for this new location. I'll work on a permanent fix and report back in my 'slackscan' thread.
2 updates (x86_64). Including a (* Security fix *)! : 2 Upgraded
Code:
Fri Nov 24 20:52:02 UTC 2023
patches/packages/vim-9.0.2127-x86_64-1_slack15.0.txz: Upgraded.
Fixed security issues.
Thanks to marav for the heads-up.
For more information, see:
https://www.cve.org/CVERecord?id=CVE-2023-48231
https://www.cve.org/CVERecord?id=CVE-2023-48232
https://www.cve.org/CVERecord?id=CVE-2023-48233
https://www.cve.org/CVERecord?id=CVE-2023-48234
https://www.cve.org/CVERecord?id=CVE-2023-48235
https://www.cve.org/CVERecord?id=CVE-2023-48236
https://www.cve.org/CVERecord?id=CVE-2023-48237
(* Security fix *)
patches/packages/vim-gvim-9.0.2127-x86_64-1_slack15.0.txz: Upgraded.
Tue Nov 28 22:13:48 UTC 2023
patches/packages/mozilla-thunderbird-115.5.1-x86_64-1_slack15.0.txz: Upgraded.
This is a bugfix release.
For more information, see:
https://www.mozilla.org/en-US/thunderbird/115.5.1/releasenotes/
1 updates (x86_64). Including a (* Security fix *)! : 1 Upgraded
Code:
Thu Nov 30 21:21:55 UTC 2023
patches/packages/samba-4.18.9-x86_64-1_slack15.0.txz: Upgraded.
This is a security release in order to address the following defect:
An information leak vulnerability was discovered in Samba's LDAP server.
Due to missing access control checks, an authenticated but unprivileged
attacker could discover the names and preserved attributes of deleted objects
in the LDAP store. Upgrading to this package will not prevent this
information leak - if you are using Samba as an Active Directory Domain
Controller, you will need to follow the instructions in the samba.org link
given below.
For more information, see:
https://www.samba.org/samba/security/CVE-2018-14628.html
https://www.cve.org/CVERecord?id=CVE-2018-14628
(* Security fix *)
Wed Dec 6 20:29:23 UTC 2023
patches/packages/rdfind-1.6.0-x86_64-1_slack15.0.txz: Upgraded.
Redundant data finder utility, needed to build the kernel-firmware package.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
