mirror of
git://slackware.nl/current.git
synced 2025-01-14 08:01:11 +01:00
8f0b1c57c9
a/glibc-solibs-2.27-x86_64-3.txz: Rebuilt.
a/pkgtools-15.0-noarch-16.txz: Rebuilt.
upgradepkg: clean up --help output and add options
upgradepkg: accept -help option (not just --help)
upgradepkg: don't omit error messages in --terse mode
upgradepkg: only print missing new package in old%new mode
upgradepkg.8: move information about config file handling from BUGS to the
DESCRIPTION section
Thanks to Xsane.
ap/vim-8.1.0039-x86_64-1.txz: Upgraded.
l/glibc-2.27-x86_64-3.txz: Rebuilt.
When installing the package, remove old versions of the glibc shared
libraries. In addition to eliminating residue on the system from old
package versions, this change will make it possible in the future to
revert to older glibc packages using upgradepkg.
l/glibc-i18n-2.27-x86_64-3.txz: Rebuilt.
l/glibc-profile-2.27-x86_64-3.txz: Rebuilt.
n/gnupg2-2.2.8-x86_64-1.txz: Upgraded.
Sanitize the diagnostic output of the original file name in verbose mode.
By using a made up file name in the message it was possible to fake status
messages. Using this technique it was for example possible to fake the
verification status of a signed mail.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12020
(* Security fix *)
xap/vim-gvim-8.1.0039-x86_64-1.txz: 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