Quote:
Anyway...Oh well. Let's leave it at that. :rolleyes: |
Quote:
Code:
# slackpkg install-new I guess a third point is in order, READ, ChangeLog.txt before doing an update. This avoids most show stoppers. |
Quote:
solved the problem: Some parts of "nouveau" are missing, so there was no hw-acceleration anymore ... At this occasion I tried the proprietary nvidia-driver (450.66), that worked with X but when going back to runlevel 3 there was no signal for the monitor! Just a "black screen" with no chance to get back a screen! rebooting over ssh and removing that driver "solved" that self-made problem |
|
Quote:
Quote:
Q. Hello roadside assist, my new Slackware model does not go. Can you help? A. Does the engine go? Q. Yes. What do I try next? A. Does the engine rev when you press the accelerator? Q. Yes. What do I try next? A. Is the car in gear? Q. Yes. What do I try next? A. Then it should be going. Have you made any mods? Q. I wanted a low profile look and took the wheels off. Would that make a difference? |
Quote:
just read this in the release notes, might interest a lot of people (that should have enough time to update their keys): it's there since a few releases but pasting again won't hurt Code:
Future deprecation notice |
Quote:
If Pat were to leave KDE PIM and akonadi out, they could reside on SBo (if someone wanted to add and support them). |
Quote:
Basically, what you refer as KDE PIM, is a part of KDE Applications, which KDE Applications are released as whole by KDE. And I believe that we shall respect the upstream decisions. Really matters that the installed size of Slackware is 40GB or 39GB? Anyways, thanks to the Full Recommended Install Doctrine (to permit me to quote His Holiness Enorbet) really does not matter. If I get Plasma5, I would love to get the whole hog and myself to choose what to install. So, I am not against that "KDE PIM" to lives in a separate series. But, just because some radicals does not need or want KDE PIM, that shall not force me to not use this PIM or to make difficult for me to use it. I honestly love those KDE PIM features, you have problems with that? Then just not not install them and do not force others to be near impossible to use them. Oh, wait... I forgot about lightning bolts. |
Quote:
|
Small nitpick: in smartmontools.SlackBuild please write /sbin/makepkg instead of just makepkg for fakeroot users among us.
|
libsigc++-2.10.4
https://download.gnome.org/sources/l...-2.10.4.tar.xz |
gcr-3.38.0
https://download.gnome.org/sources/g...-3.38.0.tar.xz Actually there is also the version 3 of libsigc++ but I am not sure if it is directly upgradable. libsigc++-3.0.4 https://download.gnome.org/sources/l...+-3.0.4.tar.xz |
|
Quote:
I have no care whether the applications that could be considered KDE-Pim are included or excluded. |
Quote:
Quote:
|
Great, I have not saw that info reading fast on the web site. It is probably a different API version and maybe someday something will
ask for it. |
Quote:
|
Mesa is now 20.2.0
|
Quote:
Code:
make DESTDIR=$PKG FIRMWAREDIR=/lib/firmware install |
Quote:
|
Quote:
https://git.kernel.org/pub/scm/linux...1448684b6b9fdd https://git.kernel.org/pub/scm/linux...a8fe0f3f88c9f6 https://git.kernel.org/pub/scm/linux...727749765f88b7 Investigating further, this "WHENCE" file contains other "Link" lines that have always been ignored by the current SlackBuild. As USUARIONUEVO has already mentioned a few times, the SlackBuild should call "make" instead of "mv linux-firmware lib/firmware". So the proper "request for current" is: Pat, please apply one of the following 2 patches to kernel-firmware.SlackBuild so that it utilizes the included Makefile to properly install the links: So this one was my first attempt to purely use the included Makefile. However, by comparing the resulting package it does not install any of the documentation or license files (including GPL-2 and GPL-3!): Code:
--- kernel-firmware.orig.SlackBuild 2019-09-29 16:48:35.000000000 -0700 Code:
$ diff -u kernel-firmware.orig.SlackBuild kernel-firmware.allfiles.SlackBuild (If you wanted to get REALLY fancy you could test for the existence of linux-firmware in $TMP and do a "git pull" instead of "git clone", but that also kind of breaks the "clean system" mentality.) |
Quote:
I've disabled (greylisted) the update for the kernel-firmware package for now and will watch if there are any changes. kind regards |
ruby in problems
CVE-2020-25613 https://github.com/ruby/webrick/commit/8946bb38b4 patch here --> https://raw.githubusercontent.com/ar.../webrick.patch |
oepncl 3.0 is released
OpenCL 1.2 applications should be able to run unchanged on OpenCL 3.0 drivers/devices. OpenCL 2.x software can also run on OpenCL 3.0 implementations assuming the driver supports all CL2 features used by the application. opencl 3 , support more hardware and features. https://www.khronos.org/blog/opencl-...l-sdk-released |
|
|
Can I please have an answer if slackware 15 will have OpenJDK 8 or OpenJDK 11? I've asked before, and nobody opposed it, but I just would like a reason against adding OpenJDK to slackware because it's now fully GPL and everything. So there should be no issue with adding it now.
|
Quote:
ever can install if need from slackbuilds |
Quote:
If openjdk was added, it is likely that a stable release wouldn't see any major version bumps, meaning when openjdk20 eventually comes out, users would need to replace the stock package with a 3rd-party one (like with php5 in 14.2 and users who want to run php7). I don't know enough about jdk to know how complicated packaging is or how easy it is to support multiple versions or whether a version bump is potentially disrupting (meaning the version in stable would likely not get the next major release), but if it ends up not being added reasons like these may be cause. (Plus, as USUARIONUEVO, mentioned, it's not currently a dependency for any programs within Slackware, which gives Pat less of a reason to look into including it.) |
Quote:
|
|
Quote:
Quote:
|
|
dconf-editor-3.36.7
https://download.gnome.org/sources/d...-3.36.7.tar.xz But better if we can upgrade to latest 3.38.x |
Quote:
https://www.ruby-lang.org/en/news/20...-7-2-released/ |
Small nitpick: in oprofile.SackBuild, --with-kernel-support is an unrecognized option.
|
librsvg-2.50.1
https://download.gnome.org/sources/l...-2.50.1.tar.xz |
gobject-introspection-1.66.1
https://download.gnome.org/sources/g...-1.66.1.tar.xz |
From the changelog the move to GNU make 4.3 was reverted on the 27th of January. Would it be worth revisiting that seeming that some of the performance improvement seem to big wins?
From the distri silverhaze release notes: Quote:
|
Request bump to kernel 5.8 or newer. I know, I know. 5.4.x is "longterm" but it doesn't look like it will get this fix backported.
[radeonsi/Navi] Google Maps causes amdgpu to crash https://gitlab.freedesktop.org/mesa/mesa/-/issues/2481 Not sure how many of you have bumped into this issue with amdgpu. When amdgpu pops, X.org and DE freezes. Only remedy is to remoe in (ssh etc) and reboot. My RX 5700 XT has been running excellent except for this one issue (so far!). Sure, google is evil, but their mapping app is really good. |
Quote:
|
for 64-bit: 5.4 is fault, 5.8 is way. no more to say.
|
|
Quote:
|
I have amdgpu as well and would like to see a formal kernel post 5.4 somewhere though I understand LTS is the best case.
5.9 SHOULD be LTS based on the pattern of previous releases and the fact that LTS releases usually come in the last release of the calendar year. Here's hoping for us amdgpu users that 5.9 will make it into 15 |
Quote:
see it later today. |
Quote:
|
Quote:
|
Quote:
|
Quote:
I'm kidding of course, but desktopupdateaphobia set in quite a while ago I'm afraid! |
All times are GMT -5. The time now is 12:59 AM. |