mirror of
git://slackware.nl/current.git
synced 2024-12-27 09:59:16 +01:00
e0375de323
a/hwdata-0.381-noarch-1.txz: Upgraded. a/kernel-generic-6.6.25-x86_64-1.txz: Upgraded. a/kernel-huge-6.6.25-x86_64-1.txz: Upgraded. a/kernel-modules-6.6.25-x86_64-1.txz: Upgraded. d/cmake-3.29.1-x86_64-1.txz: Upgraded. d/kernel-headers-6.6.25-x86-1.txz: Upgraded. d/llvm-18.1.3-x86_64-1.txz: Upgraded. k/kernel-source-6.6.25-noarch-1.txz: Upgraded. kde/kstars-3.7.0-x86_64-1.txz: Upgraded. l/enchant-2.6.9-x86_64-1.txz: Upgraded. l/libclc-18.1.3-x86_64-1.txz: Upgraded. l/sof-firmware-2024.03-noarch-1.txz: Upgraded. n/gnutls-3.8.5-x86_64-1.txz: Upgraded. n/httpd-2.4.59-x86_64-1.txz: Upgraded. This update fixes security issues: HTTP/2 DoS by memory exhaustion on endless continuation frames. HTTP Response Splitting in multiple modules. HTTP response splitting. For more information, see: https://downloads.apache.org/httpd/CHANGES_2.4.59 https://www.cve.org/CVERecord?id=CVE-2024-27316 https://www.cve.org/CVERecord?id=CVE-2024-24795 https://www.cve.org/CVERecord?id=CVE-2023-38709 (* Security fix *) n/nghttp2-1.61.0-x86_64-1.txz: Upgraded. This update fixes security issues: nghttp2 library keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it can accept after a HEADERS frame. For more information, see: https://github.com/nghttp2/nghttp2/security/advisories/GHSA-x6x3-gv8h-m57q https://www.kb.cert.org/vuls/id/421644 https://www.cve.org/CVERecord?id=CVE-2024-28182 (* Security fix *) x/xdg-desktop-portal-1.18.3-x86_64-1.txz: Upgraded. isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. usb-and-pxe-installers/usbboot.img: Rebuilt. |
||
---|---|---|
.. | ||
a | ||
ap | ||
d | ||
e | ||
f | ||
installer | ||
k | ||
kde | ||
l | ||
n | ||
t | ||
tcl | ||
x | ||
xap | ||
xfce | ||
y | ||
buildlist-from-changelog.sh | ||
make_world.sh | ||
README.TXT |
This is the source used for Slackware. To look for a particular bit of source (let's say for 'cp'), first you would look for the full path: fuzzy:~# which cp /bin/cp Then, you grep for the package it came from. Note that the leading '/' is removed, and ^ and $ mark the beginning and end of the pattern to match: fuzzy:~# grep ^bin/cp$ /var/lib/pkgtools/packages/* /var/lib/pkgtools/packages/coreutils-9.0-x86_64-3:bin/cp From this, you can see that 'cp' came from the coreutils-9.0-x86_64-3 package. The source will be found in a corresponding subdirectory. In this case, that would be ./a/coreutils/. All of these packages have scripts that extract, patch, and compile the source automatically. These are the 'SlackBuild' scripts. Have fun! --- Patrick J. Volkerding volkerdi@slackware.com