[SOLVED] slackpkg was upgraded - you will need start the upgrade process again...
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
One should study the script, you will get your answers. This is how I figured things out.
Not necessary
Code:
% ./mirror-slackware-current.sh -h
-----------------------------------------------------------------
$Id: mirror-slackware-current.sh,v 1.93 2018/06/16 10:02:33 root Exp root $
-----------------------------------------------------------------
Usage:
./mirror-slackware-current.sh [OPTION] ...
or:
SLACKROOTDIR=/your/repository/dir ./mirror-slackware-current.sh [OPTION] ...
The SLACKROOTDIR is the directory that contains the directories
slackware-<RELEASE> and slackware-<RELEASE>-iso
Current value of SLACKROOTDIR : /media/piotr/5FB77A1F7EDC9AFB/Slackware-current
You can change the script defaults in a file 'mirror-slackware-current.conf'
The script's parameters are:
-h This help.
-a <arch> Architecture to mirror (defaults to 'x86',
can be 'x86_64' or 'arm' too).
-b <number> Limit bandwidth usage to <number> KBytes/sec.
-c Check for newer version of this script.
-e Use 'boot-load-size=32' instead of the value 4.
(32 is a more standard value, but a value of 4
will let the ISO boot with old 'broken' BIOSes).
-f Force sync and the creation of new ISO image(s)
even if no update of the ChangeLog.txt was found.
This is how you resume after an aborted attempt.
Note: this will also create any missing local
directories needed for the mirror.
-i Only generate ISO images from our local copy;
do not attempt to contact the remote server.
-l <localdir> The root directory where you keep your local
Slackware mirror; this directory contains
slackware-<RELEASE> and slackware-<RELEASE>-iso
-m <uri> The rsync URI that you want to use instead of
the script default. Example:
-m mirrors.tuxq.com::slackware/slackware-current
(no trailing slash!)
-n Only show the changes in the ChangeLog.txt
but don't sync anything and don't generate ISOs.
-o <iso_type> The type of ISO that you want to generate.
iso_type can be one of:
CDROM: produce 4 CDROM images (KDE on CD4)
MINI : produce a mini CDROM (netinstall) image
DVD : produce a single DVD image
ALL : produce CDROM and DVD images
NONE : produce no images at all (just sync).
The default iso_type is CDROM.
-p Remove old ISO's before building the new ones
(in case you're suffering from low free space).
-r <release> The release ('current' by default); use '-r 12.2'
if you want to mirror and image slackware 12.2
-q Non-verbose output (for cron jobs).
-s Additional ssh options, in case rsync needs to
login to the remote server using ssh. Example:
-s "-l alien -o IdentityFile=/home/alien/.ssh/id_rsa"
-u Create a hybrid ISO (can be dd-ed to USB stick).
-v Verbose progress indications.
-w Write a .conf file containing script defaults.
It will be created in the script's directory,
as 'mirror-slackware-current.conf'
-X <xfile> File 'xfile' contains a list of exclude patterns
for directories that you do not want mirrored.
Note: this will override the default exclusion of
the 'pasture' directory so if you still want that
excluded, add it explicitly to the file 'xfile'.
If your intention is *not* to exclude '/pasture'
from the mirror, use '-X none'.
@ALL , Thank you for all of your insights & recommnedations . I've one question before traipsing off & Mirroring that stack of wonderful software using AlienBob's outstanding mirror-slackware-current.sh script .
Can I limit the mirroring to JUST a couple of repositories ?
Not having studied or used his script before .
Tia , JimL
I keep repos of both 14.2 and -current (just the 64bit versions) using Alien Bob's mirror-slackware-current.sh script. I have this as my conf file for the script (to override the defaults in the script itself since Alien Bob prefers people using the conf rather than editing the script directly):
Yeah you're right, not necessary to post the "-h" output.
Quote:
Originally Posted by chrisretusn
One should study the script, you will get your answers. This is how I figured things out.
Running mirror-slackware-current.sh -h will get you started, BUT, you should read the script, at least the top two sections and create and mirror-slackware-current.conf file, read it and modify it to fit your needs.
There is useful information in both the script and configuration file not available with "-h"
Last edited by chrisretusn; 04-04-2021 at 05:06 AM.
@bassmadrigal & @chrisretusn , Again Thank you Both , For your time and insights . The one thing missing from the "-h" & the "-w" base conf files notes are a description of the syntax for the "-X" files contents as pertains to , I'll dig around in the guts of the script & see , what it expects as delimiters & for commenting .
@bassmadrigal & @chrisretusn , Again Thank you Both , For your time and insights . The one thing missing from the "-h" & the "-w" base conf files notes are a description of the syntax for the "-X" files contents as pertains to , I'll dig around in the guts of the script & see , what it expects as delimiters & for commenting .
Agn , Thank You . JimL
The exclude file is for rsync. lookup "--exclude-from=FILE", "FILTER RULES" and "INCLUDE/EXCLUDE PATTERN RULES" in the rsync man page. I don't use it for mirror-slackware-current.sh, the default "EXCLUDES="--exclude pasture" in mirror-slackware-current.conf is sufficient for my purposes.
Here are two examples I use "--exclude-from=FILE" with.
First is the exclude file for my daily backups.
Code:
# racermach exclude file
# Note name/" exclude directory
# name/* excludes all below but keeps the directory
# name/*/* exclude all below but keeps two levels directories
# Device and virtual directories
- /dev/*
- /proc/*
- /sys/*
# tmp directories
- /tmp/*
- /var/tmp/*
- .local/share/tmp/*
# run directories.
- /run/*
- /var/run/*/*
- /var/run/*.pid
- /var/run/*.?ock*
- /var/run/utmp
# Manual and removable media mount points.
- /mnt/*/*
- /media/*
# General home directory excludes, includes /root
- .dbus/
- .gvfs/
- .cache/
- .ccache/
- .local/share/Trash/
- .Trash-*
# Obviously we do not want to back this up.
- /home/backup/*
# This is a lot to back everyday
- /home/chris/VirtualBoxVMs/*/*
# Don't backup torrent downloads. If need be move to another location.
- /home/chris/Downloads/Torrents/*
# Skip this too. Can be recreated.
- /home/slackware/*/*
# Exclude the slackbuild tmp directories
- /home/non-slack/slackbuilds/*/tmp/
The second the exclude file I use to backup just the slackware64-current local mirror packages before the mirror is updated.
Code:
# slackware64-current exclude file
# Note name/" exclude directory
# name/* excludes all below but keeps the directory
# name/*/* exclude all below but keeps two levels directories
+ extra/**.t?z
+ slackware64/**.t?z
+ patches/**.t?z
+ testing/**.t?z
+ */
- *
@chrisretusn , Thank You , Your last post answered quite Well what I needed , And the (blunt) hint that the config files are read by rsync & to goto that manpage , Helped me see the syntax needed .
I'll play around with the filtering and how small I can get the replication down to .
I'm really remiss in grabbing more than is needed to do updates .
marking as as solved .
Tnx , Agn . JimL
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.