mirror of
git://slackware.nl/current.git
synced 2024-11-18 10:08:17 +01:00
6371ee337f
d/Cython-0.28.5-x86_64-1.txz: Upgraded.
d/help2man-1.47.7-x86_64-1.txz: Upgraded.
d/meson-0.48.0-x86_64-1.txz: Upgraded.
d/python-setuptools-40.4.3-x86_64-1.txz: Upgraded.
l/M2Crypto-0.30.1-x86_64-1.txz: Upgraded.
l/cairo-1.15.14-x86_64-1.txz: Upgraded.
l/librsvg-2.44.4-x86_64-1.txz: Upgraded.
l/pycairo-1.17.1-x86_64-1.txz: Upgraded.
l/pycurl-7.43.0.2-x86_64-1.txz: Upgraded.
l/pyparsing-2.2.1-x86_64-1.txz: Upgraded.
n/ModemManager-1.8.2-x86_64-1.txz: Upgraded.
n/bind-9.12.2_P2-x86_64-1.txz: Upgraded.
This update fixes security issues:
There was a long-existing flaw in the documentation for ms-self, krb5-self,
ms-subdomain, and krb5-subdomain rules in update-policy statements. Though
the policies worked as intended, operators who configured their servers
according to the misleading documentation may have thought zone updates were
more restricted than they were; users of these rule types are advised to
review the documentation and correct their configurations if necessary. New
rule types matching the previously documented behavior will be introduced in
a future maintenance release.
named could crash during recursive processing of DNAME records when
deny-answer-aliases was in use. This flaw is disclosed in CVE-2018-5740.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5740
(* Security fix *)
n/httpd-2.4.35-x86_64-1.txz: Upgraded.
This release fixes bugs and regressions in httpd-2.4.34, adds an
apache2ctl -> apachectl symlink, and no longer automatically
overwrites rc.httpd when upgraded.
|
||
|---|---|---|
| .. | ||
| a | ||
| ap | ||
| d | ||
| e | ||
| f | ||
| installer | ||
| k | ||
| kde | ||
| kdei | ||
| 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: fuzzy:~# grep bin/cp /var/log/packages/* /var/log/packages/cpio-2.4.2.91-i386-1:bin/cpio /var/log/packages/fileutils-4.1-i386-2:bin/cp /var/log/packages/gcc-2.95.3-i386-2:usr/bin/cpp /var/log/packages/gnome-applets-1.4.0.5-i386-1:usr/bin/cpumemusage_applet From this, you can see that 'cp' came from the fileutils-4.1-i386-2 package. The source will be found in a corresponding subdirectory. In this case, that would be ./a/bin. Don't be fooled into thinking that the _bin.tar.gz in this directory is the package with the source code -- anything starting with '_' is just a framework package full of empty files with the correct permissions and ownerships for the completed package to use. Many of these packages now have scripts that untar, patch, and compile the source automatically. These are the 'SlackBuild' scripts. Moving back to the example above, you can figure out which package the bin/cp source came from by examining the SlackBuild script. Have fun! --- Patrick J. Volkerding volkerdi@slackware.com