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.
Slackware "fixed" this problem over 2yrs ago via....
________________________________________________________________________________
Sun Mar 17 20:40:15 UTC 2019
kde/ktorrent-4.3.1-x86_64-4.txz: Rebuilt.
Embed a copy of the GeoIP database since the download link no longer works.
_________________________________________________________________________________
Yes, I know that this issue was fixed in Slackware-current (next to be Slackware 15.0) in 2019 AD, BUT it wasn't fixed 'till today in Slackware 14.2 which was released 8 (eight) years ago - in 2016 AD.
My request is for fixing this via /patches in the 8 years old Slackware 14.2
Last edited by LuckyCyborg; 01-03-2023 at 10:20 AM.
Granted, the fix is not in the slackware(64)-14.2 ISO
However, it _is_ in the slackware(64)-14.2 repository.
If one were to make a fresh install of the 14.2 ISO,
does not setting the slackpkg mirror to the 14.2 repository
and upgrading to the status of 14.2 as it exists right now
upgrade to the fixed kde/ktorrent-4.3.1-x86_64-4.txz
which has been there for over 3.5yrs ?
What purpose is served by moving or copying that package into /patches ?
Granted, the fix is not in the slackware(64)-14.2 ISO
However, it _is_ in the slackware(64)-14.2 repository.
Nope, there is no such patched KTorrent package in the Slackware 14.2 repository.
Quote:
Originally Posted by glennmcc
If one were to make a fresh install of the 14.2 ISO,
does not setting the slackpkg mirror to the 14.2 repository
and upgrading to the status of 14.2 as it exists right now
upgrade to the fixed kde/ktorrent-4.3.1-x86_64-4.txz
which has been there for over 3.5yrs ?
What purpose is served by moving or copying that package into /patches ?
Man, seems like like you confuse the Slackware releases and how works the Slackware-current.
The package fix you talk was released for previous Slackware-current, in the year 2019 and the package you talk about was removed from -current along with all KDE4, when was the switch to Plasma5 .
Today, this package you talk about does not exists anymore, unless you look in the cumulative repositories, because IT WAS REMOVED from -current long time ago, on Mon Dec 7 21:49:58 UTC 2020, by upgrading to kde/ktorrent-5.2.0-x86_64-1.txz
AND, that particular patch was NOT backported until today to Slackware 14.2, where's kde/ktorrent-4.3.1-x86_64-2.txz on Tuesday, January 03, 2023 .
BTW, you are the BDFL? Nope? Then, why you comment? I do not asked you about your opinion. I asked punctually Mr. Volkerding to be kind to fix something in Slackware 14.2. Please note that I started my post with "Dear BDFL," and in my humble opinion this means to who I intended to talk to.
Last edited by LuckyCyborg; 01-03-2023 at 11:34 AM.
This release adds a month's worth of new translations and fixes from KDE's contributors.
The bugfixes are typically small but important and include:
Code:
- kscreenlocker: Fix wallpaper not loading (leaving the background black)
- Libdiscover: fix permission text not being translated
- Plasma Addons Alternatecalendar: always use day name in full label
Gentlemen, please excuse my ignorance, but it's still maintained Slackware 14.2 after 8 years?
As others have said, at the time of this writing all 14.x as well as 15.0 are still being supported with security patches. That being said, those security patches depend upon upstream sources providing new versions still possible to compile in those today rather old environments. There are examples of packages, like mozilla-firefox and mozilla-thunderbird where newer versions no longer compile from sources on Slackware 14.x. Those packages no longer get security updates even though these versions of Slackware are still supported.
To my knowledge, there is no official list of packages no longer being updated for these still supported Slackware versions.
There are some third party solutions for some of the packages no longer updated by Slackware. One such example is https://gist.github.com/ruario/9672798 which downloads and repackages prebuilt binary versions of Mozilla Firefox.
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Rep:
rxvt-unicode-9.31
Code:
9.31 Mon 02 Jan 2023 18:13:16 CET
- implement a fix for CVE-2022-4170 (reported and analyzed by David Leadbeater).
While present in version 9.30, it should not be exploitable. It is exploitable
in versions 9.25 and 9.26, at least, and allows anybody controlling output to
the terminal to execute arbitrary code in the urxvt process.
- the background extension no longer requires off focus fading support
to be compiled in.
- the confirm-paste extension now offers a choice betwene pasting the original
or a sanitized version, and also frees up memory used to store the paste text
immediately.
- fix compiling without frills.
- fix rewrapMode: never.
- fix regression that caused urxvt to no longer emit responses
to OSC color queries other than OSC 4 ones.
- fix regression that caused urxvt to no longer process OSC 705.
- restore CENTURY to be 1900 to "improve" year parsing in urclock (or at
least go back to the old interpretation) (based on an analysis
by Tommy Pettersson).
- exec_async (used e.g. by the matcher extension to spawn processes) now
sets the URXVT_EXT_WINDOWID variable to the window id of the terminal.
- implement -fps option/refreshRate resource to change the default 60 Hz
maximum refresh limiter. I always wanted an fps option, but had to
wait for a user requesting it.
- new clickthrough extension.
- perl now also requires Xext.
- X region and shape extension functionality has been exposed to perl
extensions.
- RENDER extension no longer depends on ENABLE_XIM_ONTHESPOT.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
