This creates a blacklist of package names from regexp in original
file (/etc/slackpkg/blacklist) and uses the precreated list for
later comparison
Signed-off-by: Robby Workman <rworkman@slackware.com>
We decided to jump from 2.83.x straight to 15.0 to match the
version of Slackware for which it's intended: 15.0
That's not to imply that this version of slackpkg won't work
just fine with earlier Slackware releases: it should; however,
you definitely want this version of slackpkg for Slackware 15.0
As of slackpkg shipped with Slackware 15.0, it is no longer
supported to add packages to /etc/slackpkg/blacklist using
the slackpkg executable; this should only be done with an
editor pointing at /etc/slackpkg/blacklist
* Modify checkchangelog() function to only check CHECKSUMS.md5.asc.
* Remove unneeded check of ChangeLog.txt from checkchangelog() function.
* Move fetching of ChangeLog.txt to updatefilelists() function.
* Modify check-updates to output need to update to stderr so cron
jobs will notify sysadmin.
Signed-off-by: Robby Workman <rworkman@slackware.com>
This reverts commit fcc58ff506
because it breaks lxc container creation; ponce stated on LQ
that "seems that forcing $CONF under $ROOT is what break things
here: $CONF in the template is used to have a temporary location,
outside of the container, in which to store the template, a
blacklist and a mirror configuration for the container creation"
This adds ./$PKGMAIN/ to a blacklisted set line, which
ought to say turn kde/ into ./slackware64/kde as it listed in the
temp pkglist. I've tightened up the patches/pasture/extra etc. lines
too.
Signed-off-by: Robby Workman <rworkman@slackware.com>
This should fix blacklisting of entire package sets; thanks much
to David Woodfall (dive) for this. Note that the sample blacklist
file has changed to reflect the new syntax for blacklisting sets
(add a trailing slash, e.g. "kde/")
Blacklisted sets now need a trailing / (eg. kde/)
Anything with a trailing slash is excluded from having \s added to it.
Then the slash is removed so the set is picked up by the old
functionality.
Signed-off-by: Robby Workman <rworkman@slackware.com>
- Allow blacklisting of individual packages without collateral
damage (e.g. glibc ---> glibc-*). This changes the prior behavior
of the blacklist function; previously, adding "glibc" to the
blacklist would cause glibc, glibc-profile, glibc-zoneinfo, et al
to be ignored by slackpkg. The new behavior is that *only* the
glibc package is ignored. If you want to blacklist all packages
whose names begin with glibc, you would need to add "glibc.*" to
the blacklist now. Also note that any special characters, e.g. "+",
will need to be escaped in the blacklist file. (David Woodfall)
- Add support for listing .new files without PAGER (David Woodfall)
- Remove switch.ch mirrors
- Add config option to allow *not* saving .orig configs (Darren Austin)
- Mention possible stale mirror if CHECKSUMS.md5 gpg verify fails
- Clarify that a press of "Enter" is needed to confirm kernel change
(Mario Preksavec)
- doinst.sh Don't remove ChangeLog.txt upon upgrade/reinstall.
(Patrick Volkerding)
- mirrors-x86*.sample: Remove bjtu.edu.cn mirror
- Fix for /var/log/packages/ possibly being a symlink to elsewhere
- Use CHECKSUMS.md5.asc to determine ChangeLog newness
(Patrick Volkerding)
In short, it seems impossible to blacklist some packages without
catching other undesirable packages. As an example, blacklisting
glibc will also catch glibc-zoneinfo (and the other glibc-*)
packages. It would be good to have the ability to blacklist only
the glibc package without it catching the others.
With this change, if sysadmin wants the blacklist to be "greedy,"
then adding "glibc.*" to the blacklist will do that.
Reported-by: Peter Hyman <pete@peterhyman.com>
Signed-off-by: Robby Workman <rworkman@slackware.com>
When admins choose to allow slackpkg new-config to overwrite
currently installed config files with the .new counterparts
from an upgraded package, slackpkg has traditionally created
backups of the config files first, with the backups being
written out with .orig extensions. This commit does not change
the default behavior, but it does allow it to be turned off.
TLDR: set "ORIG_BACKUPS" to "off" in /etc/slackpkg/slackpkg.conf
if you do not wish to have .orig files left over
Signed-off-by: Robby Workman <rworkman@slackware.com>
Existence of /etc/lilo.conf coupled with executable /sbin/lilo
probably indicates lilo usage on the system, so that seems like
a reasonable compromise for everyone fussing about slackpkg's
offer to run /sbin/lilo for them after kernel upgrades even
though they use grub or whatever else.
This should never be an issue on a properly installed
system (assuming slackpkg is installed on the system),
but it doesn't hurt anything either to be safe.
** This was my mistake; my mail client munged the patch, so
I had to apply it all by hand. The extra (old) line of
'showmenu' options was what I'd copied to compare the
new options, and I forgot to delete it when committing.
Mea culpa. --rworkman
