LinuxQuestions.org - Requests for -current (14.2-->15.0)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Requests for -current (14.2-->15.0) (https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/)

Quote:

Originally Posted by baldzhang (Post 6169724)

last firmware package: kernel-firmware-20200923_afbfb5f-noarch-1.txz, is missing symbol links.

upstream remove them, could be created by copy-firmware.sh.

This is caused by these 3 commits:

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

+++ kernel-firmware.makeonly.SlackBuild 2020-09-29 07:45:49.232774011 -0700

@@ -49,15 +49,15 @@

 rm -rf $PKG

 mkdir -p $TMP $PKG

 

-cd $PKG

+cd $TMP

+rm -rf linux-firmware

 git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

 # Better determine these the same way as above.

 DATE="$(lynx -dump -width=256 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=HEAD | grep "  committer " | head -n 1 | rev | cut -f 3 -d ' ' | rev | tr -d -)"

 HEADISAT="$(lynx -dump -width=256 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=HEAD | grep "    commit  " | head -n 1 | cut -f 2 -d ] | cut -b 1-7)"

-find . -name ".git*" -exec rm -rf "{}" \+

+cd linux-firmware

 chown -R root:root .

-mkdir -p lib

-mv linux-firmware lib/firmware

+make DESTDIR=$PKG install

 

 # Remove sources for carl9170fw:

 ( cd $PKG/lib/firmware

And this is my second option, which clones the repository into the package directory (like the original SlackBuild) and then runs "make install". Of course "make" spews out lots of warnings because it tries to copy files over themselves. But other than the warnings there is no harm. Additionally, the links get created correctly. This also preserves all the license and documentation files.

Code:

$ diff -u kernel-firmware.orig.SlackBuild kernel-firmware.allfiles.SlackBuild 

--- kernel-firmware.orig.SlackBuild    2019-09-29 16:48:35.000000000 -0700

+++ kernel-firmware.allfiles.SlackBuild 2020-09-29 07:37:00.068972213 -0700

@@ -58,6 +58,8 @@

 chown -R root:root .

 mkdir -p lib

 mv linux-firmware lib/firmware

+cd lib/firmware

+make DESTDIR=$PKG install

 

 # Remove sources for carl9170fw:

 ( cd $PKG/lib/firmware

In my opinion, upstream needs a "make" flag to install documentation and license files...

(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:

Originally Posted by drumz (Post 6170819)

Code:

--- kernel-firmware.orig.SlackBuild    2019-09-29 16:48:35.000000000 -0700

+++ kernel-firmware.makeonly.SlackBuild 2020-09-29 07:45:49.232774011 -0700

@@ -49,15 +49,15 @@

 rm -rf $PKG

 mkdir -p $TMP $PKG

 

-cd $PKG

+cd $TMP

+rm -rf linux-firmware

 git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

 # Better determine these the same way as above.

 DATE="$(lynx -dump -width=256 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=HEAD | grep "  committer " | head -n 1 | rev | cut -f 3 -d ' ' | rev | tr -d -)"

 HEADISAT="$(lynx -dump -width=256 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=HEAD | grep "    commit  " | head -n 1 | cut -f 2 -d ] | cut -b 1-7)"

-find . -name ".git*" -exec rm -rf "{}" \+

+cd linux-firmware

 chown -R root:root .

-mkdir -p lib

-mv linux-firmware lib/firmware

+make DESTDIR=$PKG install

 

 # Remove sources for carl9170fw:

 ( cd $PKG/lib/firmware

Code:

$ diff -u kernel-firmware.orig.SlackBuild kernel-firmware.allfiles.SlackBuild 

--- kernel-firmware.orig.SlackBuild    2019-09-29 16:48:35.000000000 -0700

+++ kernel-firmware.allfiles.SlackBuild 2020-09-29 07:37:00.068972213 -0700

@@ -58,6 +58,8 @@

 chown -R root:root .

 mkdir -p lib

 mv linux-firmware lib/firmware

+cd lib/firmware

+make DESTDIR=$PKG install

 

 # Remove sources for carl9170fw:

 ( cd $PKG/lib/firmware

Thanks for the patches, that solved my problem with the missing "nouveau"-modules
I've disabled (greylisted) the update for the kernel-firmware package for now
and will watch if there are any changes.
kind regards

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:

Originally Posted by ziprun (Post 6171669)

nothing in slackware needs , then why add a heavy size package ?

ever can install if need from slackbuilds

Quote:

Originally Posted by ziprun (Post 6171669)

One of the dev team members mentioned earlier in regards to another package is that they aren't experts in all packages, and some packages deserve the better maintenance a dedicated maintainer can provide than what Pat and team can.

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:

Originally Posted by ziprun (Post 6171669)

AlienBob maintains great OpenJDK 7/8 packages, and there are SlackBuilds in SBo for other Java versions, even newer ones. So, Java is available.

Quote:

Originally Posted by TurboBlaze (Post 6171829)

PHP 7.4.11
https://www.php.net/ChangeLog-7.php
https://www.php.net/downloads

I think you missed this

Quote:

Originally Posted by Slackware current's ChangeLog

Tue Sep 29 18:11:08 UTC 2020
n/php-7.4.11-x86_64-1.txz: Upgraded.
This update fixes bugs and two security issues:
Core: PHP parses encoded cookie names so malicious `__Host-` cookies
can be sent.
OpenSSL: Wrong ciphertext/tag in AES-CCM encryption for a 12 bytes IV.
For more information, see:
https://cve.mitre.org/cgi-bin/cvenam...=CVE-2020-7070
https://cve.mitre.org/cgi-bin/cvenam...=CVE-2020-7069
(* Security fix *)

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:

Originally Posted by USUARIONUEVO (Post 6171321)

ruby in problems
CVE-2020-25613
https://github.com/ruby/webrick/commit/8946bb38b4
patch here --> https://raw.githubusercontent.com/ar.../webrick.patch

Fixed in Ruby 2.7.2:
https://www.ruby-lang.org/en/news/20...-7-2-released/