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.
According to ChangeLog.txt for -current. I noted this with current for several years, the standard version is used until we are getting "closer" to a new release. The definition of "closer" has a humongous window.
It appears that Slackware 15.0 started with mozilla-firefox-91.5.1esr-x86_64-1.txz, thus the same for Slackware -current.
15.0 ChangeLog.txt
Code:
Thu Feb 10 01:46:55 UTC 2022
patches/packages/mozilla-firefox-91.6.0esr-x86_64-1_slack15.0.txz: Upgraded.
-current ChangeLog.txt
Code:
Thu Feb 10 01:46:55 UTC 2022
xap/mozilla-firefox-97.0-x86_64-1.txz: Upgraded.
Several upgrades...
Fri Jul 7 23:06:07 UTC 2023
xap/mozilla-firefox-115.0.1-x86_64-1.txz: Upgraded.
Wed Jul 12 20:41:16 UTC 2023
xap/mozilla-firefox-115.0.2esr-x86_64-1.txz: Upgraded.
Currently on mozilla-firefox-121.0-x86_64-1cgs.txz. I build it using the source tree build, replacing standard firefox source tarball vice the tarball used with -current. Takes about 4 hours on this molasses machine. In the SlackBuild I add a comment near the top, date of upgrade and add a tag to the build. I don't change the 'else' part since I don't use a localized build. If I did, simply to modify.
Code:
if [ -z $MOZLOCALIZE ]; then
/sbin/makepkg -l y -c n $TMP/mozilla-firefox-$VERSION-$ARCH-${BUILD}cgs.txz
else
/sbin/makepkg -l y -c n $TMP/mozilla-firefox-$VERSION-$ARCH-${BUILD}_$MOZLOCALIZE.txz
fi
I would like to see -current use the standard firefox, but I understand why the shift to ESR in preparation for the next release.
Last edited by chrisretusn; 12-20-2023 at 07:22 AM.
That's odd. On my laptop, active mode gave me powersave (/etc/default/cpufreq had schedutil).
EDIT: there's a separate setting called "energy_performance_preference," and that does default to performance. In my case, powersave was the scheduling governor.
Seems this was fixed now.
Quote:
a/sysvinit-scripts-15.1-noarch-9.txz: Rebuilt.
rc.cpufreq: also default to "performance" for amd-pstate-epp.
Thanks to pghvlaans.
Let's quote the just posted announcement by Daniel Kiper:
Quote:
Hi all,
GRUB maintainers are proud to announce GRUB 2.12 that has been just released.
You can find list of new features and major fixes since release 2.06 in the
NEWS file.
We would like to thank all the people who have contributed to the project.
I built and installed grub-12.0 in Slint64-15.0 for the targets i386-pc, i386-efi, x86_64-efi, and x86-64-emu and that seems to work.
But for the builds to succeed I used a temporary workaround (temporary until fixed upstream): include these lines in the SlackBuild before the ./configure commands
Code:
# Temporary fix, cf. https://lists.gnu.org/archive/html/grub-devel/2023-12/msg00053.html
# as I got the same error but applying this patch didn't help here.
sed -i 's;$(top_srcdir)/grub-core/extra_deps.lst ;;g' grub-core/Makefile.* || exit
Last edited by Didier Spaier; 12-21-2023 at 05:33 PM.
Reason: Added a pic
Postfix stable release 3.8.4 (Security: this release adds support to defend against an email spoofing attack (SMTP smuggling) on recipients at a Postfix server)
* docutils/MANIFEST.in
- Include tox.ini and docutils.conf in the source package
(cf. bug #467 and bug #461).
* tools/rst2odt_prepstyles.py
- Moved to ``docutils/writers/odf_odt/prepstyles.py``.
Replaced with a provisional backwards compatibility script.
* ensure no (less) development files in package and
no html-files in egg-directory.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,090
Rep:
I'm sure that this is already contemplated/planned, but wouldn't it be nice if Qt6 appeared in a not-to-distant future (maybe in /testing to begin with)?
More and more applications depend on Qt6. A recent announcement from the mkvtoolnix developers:
Quote:
2023-12-10: Dropped support for Qt 5. Qt 6.2.0 or newer is now the minimum requirement for building MKVToolNix starting with v82.
I'm aware of the SBo script for Qt6, but I lack the necessary hardware stated in the README file:
Quote:
Qt6 requires 16GB of RAM to build, and a minimum of 40GB of available
disk storage.
I had to upgrade these packages because their upgrade is needed by a package released in Slackbuilds.org.
The upgrade seems no giving issues with the current configuration.
To build these releases I used the same slackbuilds available in slackware64-current/source:
1) the slackbuild of python-requests works as is without any changes
2) the one of python-urllib3 required a little edit since urllib3 has dropped the deprecated setup.py
I replaced the line 'python3 setup.py ...' with the following (taken from other slackbuilds):
kgha did you know ponce posts these precompiled packages: https://ponce.cc/slackware/qt6_and_deps/current/x86_64/
they've worked for me. I installed them as a dep to try out that opensource ai chat implementation that someone posted a slackbuild for in these forums.
removed them , but ponce's qt6 worked for me
How much difference from the default shell with desktop effects turned off?
In particular, over narrow band (< 100kbps) and high latency (> 1s) links ... since I find the default shell fast enough when I use it to access servers about 3000km away through connections with bandwidths on the order of 100Mbps.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.