1
0
Fork 0
mirror of git://slackware.nl/current.git synced 2025-02-15 08:50:09 +01:00
slackware-current/source
Patrick J Volkerding 85ea736cfd Sun Feb 9 21:47:04 UTC 2025
a/openssl11-solibs-1.1.1zb_p2-x86_64-1.txz:  Upgraded.
a/pkgtools-15.1-noarch-28.txz:  Rebuilt.
  removepkg: when using --verbose, don't remove files in parallel because it
  causes occasional screen corruption. This change only affects --verbose,
  and actually hardly slows that down.
ap/qpdf-11.10.0-x86_64-1.txz:  Upgraded.
ap/vim-9.1.1094-x86_64-1.txz:  Upgraded.
d/cbindgen-0.28.0-x86_64-1.txz:  Upgraded.
d/python-pip-25.0.1-x86_64-1.txz:  Upgraded.
d/rust-bindgen-0.71.1-x86_64-1.txz:  Upgraded.
l/SDL2-2.32.0-x86_64-1.txz:  Upgraded.
l/gegl-0.4.54-x86_64-1.txz:  Upgraded.
l/libffi-3.4.7-x86_64-1.txz:  Upgraded.
l/liboggz-1.1.2-x86_64-1.txz:  Upgraded.
n/openssl11-1.1.1zb_p2-x86_64-1.txz:  Upgraded.
  Apply patch to fix a low severity security issue:
  Fix timing side-channel in ECDSA signature computation.
  There is a timing signal of around 300 nanoseconds when the top word of
  the inverted ECDSA nonce value is zero. This can happen with significant
  probability only for some of the supported elliptic curves. In particular
  the NIST P-521 curve is affected. To be able to measure this leak, the
  attacker process must either be located in the same physical computer or
  must have a very fast network connection with low latency.
  This CVE was fixed by the second 1.1.1zb release that is only available to
  subscribers to OpenSSL's premium extended support. The patch was prepared
  by backporting from the OpenSSL-3.0 repo.
  Thanks to Ken Zalewski for the patch!
  For more information, see:
    https://www.cve.org/CVERecord?id=CVE-2024-13176
  (* Security fix *)
xap/vim-gvim-9.1.1094-x86_64-1.txz:  Upgraded.
xfce/xfce4-settings-4.20.1-x86_64-1.txz:  Upgraded.
2025-02-09 23:35:25 +01:00
..
a Sun Feb 9 21:47:04 UTC 2025 2025-02-09 23:35:25 +01:00
ap Sun Feb 9 21:47:04 UTC 2025 2025-02-09 23:35:25 +01:00
d Sun Feb 9 21:47:04 UTC 2025 2025-02-09 23:35:25 +01:00
e Tue Jul 23 18:54:25 UTC 2024 2024-07-23 22:50:05 +02:00
f Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
installer Fri Dec 27 23:07:45 UTC 2024 2024-12-28 01:14:53 +01:00
k Sat Feb 8 23:52:14 UTC 2025 2025-02-09 02:21:16 +01:00
kde Fri Feb 7 20:33:45 UTC 2025 2025-02-07 22:26:55 +01:00
l Sun Feb 9 21:47:04 UTC 2025 2025-02-09 23:35:25 +01:00
n Sun Feb 9 21:47:04 UTC 2025 2025-02-09 23:35:25 +01:00
t Tue Dec 31 19:47:47 UTC 2024 2024-12-31 21:29:46 +01:00
tcl Thu Dec 5 22:00:02 UTC 2024 2024-12-05 23:45:17 +01:00
x Sat Feb 1 21:14:13 UTC 2025 2025-02-02 00:13:05 +01:00
xap Tue Feb 4 19:19:28 UTC 2025 2025-02-04 21:03:58 +01:00
xfce Sun Feb 9 21:47:04 UTC 2025 2025-02-09 23:35:25 +01:00
y Mon Dec 23 23:43:54 UTC 2024 2024-12-24 01:04:05 +01:00
buildlist-from-changelog.sh Fri Oct 8 03:23:28 UTC 2021 2021-10-08 08:59:45 +02:00
make_world.sh Wed Jun 8 19:15:34 UTC 2022 2022-06-09 07:00:13 +02:00
README.TXT Wed Feb 2 08:21:48 UTC 2022 2022-02-02 11:59:53 +01:00

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