[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.
slackpkg was upgraded - you will need start the upgrade process again...
Hello All , Here's another pet peive . When you live down a metered link & have to RE-DOWNLOAD because of an upgrade to slackpkg .
I there a way to force slackpkg to upgrade it's pkg First ?
Thus NOT having to re-download almost a gig of other packages again ?
Tia , JimL
Code:
Installing package slackpkg-15.0.1-noarch-1.txz:
PACKAGE DESCRIPTION:
# slackpkg (Slackware package upgrade manager)
#
# Slackpkg is an upgrade manager for Slackware packages. It can
# download, upgrade, install, and remove selected packages using an
# official Slackware package repository. With it, you can also
# search in the Slackware Package database and find which package
# has the selected file.
#
# Slackpkg DOES NOT replace the Slackware pkgtools; actually,
# Slackpkg uses pkgtools for the install/upgrade/remove functions.
#
Executing install script for slackpkg-15.0.1-noarch-1.txz.
Package slackpkg-15.0.1-noarch-1.txz installed.
Package slackpkg-15.0-noarch-3 upgraded with new package ./slackpkg-15.0.1-noarch-1.txz.
slackpkg was upgraded - you will need start the upgrade process again...
2021-04-02.08:54:00.Eath+10 ( for VLAT Asia/Vladisvostok) ; use dot as separator.
or Mars hour's i.e. Mars day long. %Y-%d-%h.%H-%M-%S.Mars+01
is lightly sorting. https://en.wikipedia.org/wiki/Timekeeping_on_Mars
Because Mars now is planet of robot's ! Linux now work in Perseverance robot.
Last edited by Roman Dyaba; 04-01-2021 at 07:09 PM.
Reason: text speak grammar and normalise
Location: Russia, 690016 Vladivostok city, street Osipenko home 66, tel: +79247350007
Distribution: Slackware, UbuntuStudio, FreeBSD
Posts: 96
Rep:
@babydr
My i-provider can redirect to best mirror, if it actual state or direct from slackware.com if outdated.
For Russia is mirror.yandex.ru or tsu.ru and it work now right, his make redirect if outdate.
Last edited by Roman Dyaba; 04-01-2021 at 07:06 PM.
I am really looking for a way to process slackpkg First . Especially from within a cron script Before I have download the whole list of packages to be upgraded .
@RadicalDreamer , Thank You , But where is slackpkg going to find 'slackpkg' as in the below , what may I be missing ? The help function does show just this method to upgrade a particulat pkg , But ...
Tia , JimL
Code:
$ slackpkg upgrade slackpkg
Checking local integrity... DONE
Looking for slackpkg in package list. Please wait... DONE
No packages match the pattern for upgrade. Try:
/usr/sbin/slackpkg install|reinstall
I am really looking for a way to process slackpkg First . Especially from within a cron script Before I have download the whole list of packages to be upgraded .
@RadicalDreamer , Thank You , But where is slackpkg going to find 'slackpkg' as in the below , what may I be missing ? The help function does show just this method to upgrade a particulat pkg , But ...
Tia , JimL
Code:
$ slackpkg upgrade slackpkg
Checking local integrity... DONE
Looking for slackpkg in package list. Please wait... DONE
No packages match the pattern for upgrade. Try:
/usr/sbin/slackpkg install|reinstall
It isn't going to upgrade a package that is already installed, so slackpkg should show up when you do
Thus NOT having to re-download almost a gig of other packages again ?
It will only redownload the files that slackpkg needs (changelog, package list, package checksums, etc).
It will find the packages you have already downloaded and it won't download them again.
(Or at least it shouldn't; if it does start to download them again you might have something set up wrong)
Yes, with the default settings all packages able to be upgraded will only be downloaded once (by default they'd be sitting in /var/cache/packages after the first 'upgrade-all' run, which is TEMP in /etc/slackpkg/slackpkg.conf). What it will download again after upgrading slackpkg itself are the file lists etc. So:
Code:
slackpkg update
slackpkg upgrade-all
# everything will be downloaded, but it will upgrade slackpkg first and prompt for a `slackpkg update` command.
slackpkg update
# re-downloading those files
slackpkg upgrade-all
# nothing downloaded here, all packages will already be in $TEMP
Hello All , Here's another pet peive . When you live down a metered link & have to RE-DOWNLOAD because of an upgrade to slackpkg
Thus NOT having to re-download almost a gig of other packages again ?
The packages are not re-download the packages are cached in /var/cache/packages/. The following is the output (abbreviated) of my update from another machine that was at ChangeLog.txt Fri Mar 26 18:05:00 UTC 2021. I upgraded back to an earlier version of slackpkg 15 I had to trigger an upgrade to slackpkg. This output is after the first 'slackpkg update'
Code:
slackpkg -dialog=off upgrade-all
Checking local integrity... DONE
Looking for packages to upgrade. Please wait... DONE
aaa_glibc-solibs-2.33-i586-2.txz
<< snip >>slackpkg-15.0.1-noarch-1.txz<< snip >>
xterm-367-i586-1.txz
Total package(s): 61
Do you wish to upgrade selected packages (Y/n)?
Package: aaa_glibc-solibs-2.33-i586-2.txz
Downloading https://mirrors.slackware.com/slackware/slackware-current/./slackware/a/aaa_glibc-solibs-2.33-i586-2.txz...
<< snip >>
Saving to: ‘//var/cache/packages/./slackware/a/aaa_glibc-solibs-2.33-i586-2.txz’
<< snip >>
Executing install script for slackpkg-15.0.1-noarch-1.txz.
Package slackpkg-15.0.1-noarch-1.txz installed.
Package slackpkg-15.0.1_beta1-noarch-1 upgraded with new package ./slackpkg-15.0.1-noarch-1.txz.
slackpkg was upgraded - you will need start the upgrade process again...
slackpkg update
Updating the package lists...
Downloading...
Downloading https://mirrors.slackware.com/slackware/slackware-current/CHECKSUMS.md5.asc...
<< snip >>
Saving to: ‘/tmp/slackpkg.0tdS3a/CHECKSUMS.md5.asc’
<< snip >>
Formatting lists to slackpkg style...
Package List: using CHECKSUMS.md5 as source
Package descriptions
slackpkg -dialog=off upgrade-all
Checking local integrity... DONE
Looking for packages to upgrade. Please wait... DONE
aaa_glibc-solibs-2.33-i586-2.txz
<< snip >>
xterm-367-i586-1.txz
Total package(s): 60
Do you wish to upgrade selected packages (Y/n)?
Package aaa_glibc-solibs-2.33-i586-2.txz is already in cache - not downloading
Package at-spi2-core-2.40.0-i586-1.txz is already in cache - not downloading
Package ccache-4.2.1-i586-1.txz is already in cache - not downloading
Package curl-7.76.0-i586-1.txz is already in cache - not downloading
Package dbus-glib-0.112-i586-1.txz is already in cache - not downloading
Package dconf-0.40.0-i586-1.txz is already in cache - not downloading
Package dconf-editor-3.38.3-i586-1.txz is already in cache - not downloading
Package epic5-2.1.4-i586-1.txz is already in cache - not downloading
Package fetchmail-6.4.18-i586-1.txz is already in cache - not downloading
Package ffmpeg-4.3.2-i586-2.txz is already in cache - not downloading
Package fig2dev-3.2.8a-i586-1.txz is already in cache - not downloading
Package file-5.40-i586-1.txz is already in cache - not downloading
Package gcr-3.40.0-i586-1.txz is already in cache - not downloading
Package gdk-pixbuf2-2.42.4-i586-1.txz is already in cache - not downloading
Package gegl-0.4.30-i586-1.txz is already in cache - not downloading
Package ghostscript-9.54.0-i586-1.txz is already in cache - not downloading
Package gimp-2.10.24-i586-1.txz is already in cache - not downloading
Package git-2.31.1-i586-1.txz is already in cache - not downloading
Package gjs-1.68.0-i586-1.txz is already in cache - not downloading
Package glib-networking-2.68.0-i586-1.txz is already in cache - not downloading
Package glib2-2.68.0-i586-1.txz is already in cache - not downloading
Package glibc-2.33-i586-2.txz is already in cache - not downloading
Package glibc-i18n-2.33-i586-2.txz is already in cache - not downloading
Package glibc-profile-2.33-i586-2.txz is already in cache - not downloading
Package gobject-introspection-1.68.0-i586-1.txz is already in cache - not downloading
Package gst-plugins-good-1.18.4-i586-2.txz is already in cache - not downloading
Package gtk+3-3.24.28-i586-1.txz is already in cache - not downloading
Package gvfs-1.48.0-i586-1.txz is already in cache - not downloading
Package help2man-1.48.3-i586-1.txz is already in cache - not downloading
Package imagemagick-7.0.11_5-i586-1.txz is already in cache - not downloading
Package inxi-20210329_a539c8fd-noarch-1.txz is already in cache - not downloading
Package jasper-2.0.28-i586-1.txz is already in cache - not downloading
Package kernel-generic-5.11.11-i586-1.txz is already in cache - not downloading
Package kernel-generic-smp-5.11.11_smp-i686-1.txz is already in cache - not downloading
Package kernel-headers-5.11.11_smp-x86-1.txz is already in cache - not downloading
Package kernel-huge-5.11.11-i586-1.txz is already in cache - not downloading
Package kernel-huge-smp-5.11.11_smp-i686-1.txz is already in cache - not downloading
Package kernel-modules-5.11.11-i586-1.txz is already in cache - not downloading
Package kernel-modules-smp-5.11.11_smp-i686-1.txz is already in cache - not downloading
Package kernel-source-5.11.11_smp-noarch-1.txz is already in cache - not downloading
Package libXaw-1.0.14-i586-1.txz is already in cache - not downloading
Package libXres-1.2.1-i586-1.txz is already in cache - not downloading
Package mkinitrd-1.4.11-i586-21.txz is already in cache - not downloading
Package netpbm-10.94.01-i586-1.txz is already in cache - not downloading
Package network-scripts-15.0-noarch-15.txz is already in cache - not downloading
Package pango-1.48.4-i586-1.txz is already in cache - not downloading
Package pygobject3-3.40.1-i586-1.txz is already in cache - not downloading
Package qt5-5.15.2-i586-7.txz is already in cache - not downloading
Package re2c-2.1.1-i586-1.txz is already in cache - not downloading
Package seamonkey-2.53.7-i686-1.txz is already in cache - not downloading
Package sqlite-3.35.3-i586-1.txz is already in cache - not downloading
Package vim-8.2.2678-i586-1.txz is already in cache - not downloading
Package vim-gvim-8.2.2678-i586-1.txz is already in cache - not downloading
Package vte-0.64.0-i586-1.txz is already in cache - not downloading
Package whois-5.5.9-i586-1.txz is already in cache - not downloading
Package xfig-3.2.8a-i586-1.txz is already in cache - not downloading
Package xine-lib-1.2.11-i586-5.txz is already in cache - not downloading
Package xpaint-3.1.3-i586-1.txz is already in cache - not downloading
Package xsnow-3.2.3-i586-1.txz is already in cache - not downloading
Package xterm-367-i586-1.txz is already in cache - not downloading
Package aaa_glibc-solibs-2.33-i586-2.txz is already in cache - not downloading
Upgrading aaa_glibc-solibs-2.33-i586-2...
+==============================================================================
| Upgrading aaa_glibc-solibs-2.33-i586-1 package using ./aaa_glibc-solibs-2.33-i586-2.txz
+==============================================================================
<< snip >>
Package xterm-366-i586-2 upgraded with new package ./xterm-367-i586-1.txz.
Your kernel image was updated, and your /etc/lilo.conf indicates
the use of an initrd for at least one of your kernels. Be sure to
regenerate the initrd for the new kernel and handle any needed
updates to your bootloader.
Press the "Enter" key to continue...
Last edited by chrisretusn; 04-02-2021 at 04:05 AM.
% du -sh Slackware-current/
7.4G Slackware-current/
on my computer without CD or DVD. Only x86_64 architecture + all sources. My reason is my network connection is not very good - it works nice at night. I refresh mirror before upgrades. Slackpkg can work with local directory - and with mass updates ~ 4GB it is really safety device - if you brake mirror no problem - just refresh again. Broken update can be pain in ass.
% du -sh Slackware-current/
7.4G Slackware-current/
on my computer without CD or DVD. Only x86_64 architecture + all sources. My reason is my network connection is not very good - it works nice at night. I refresh mirror before upgrades. Slackpkg can work with local directory - and with mass updates ~ 4GB it is really safety device - if you brake mirror no problem - just refresh again. Broken update can be pain in ass.
It's a good idea. I've been doing just that for ages. I locally mirror -current and 14.2 using AlienBob's outstanding mirror-slackware-current.sh script.
2.1G alienbob/
4.0G alienbob_builds/
77M alienbob_restricted/
517M multilib/
6.6G total
My main reason ability to upgrade all of my Slackware installations from a local source tree instead of upgrading each via an internet source. It's also very convenient to have the source tree locally. The slackware64-current local mirror is synced using a daily cron job. The rest are done manually via scripts as needed.
Thank you for this post. I had not put 2 and 2 together until I saw it.
Quote:
Originally Posted by chrisretusn
It's a good idea. I've been doing just that for ages. I locally mirror -current and 14.2 using AlienBob's outstanding mirror-slackware-current.sh script.
My main reason ability to upgrade all of my Slackware installations from a local source tree instead of upgrading each via an internet source. It's also very convenient to have the source tree locally. The slackware64-current local mirror is synced using a daily cron job. The rest are done manually via scripts as needed.
Yesterday I ran into the problem of slackpkg being upgraded and needing to redo the mirror, blacklist, and slackpkg.conf file. But after that it would not work due to needing an updated GLIB. In my efforts to solve this problem, I saw this thread and used the mirror-slackware-current.sh script which I had downloaded a while back to make an installation USB stick. Then, after searching the changlog for "solibs", I was able to find /a/aaa_glibc-solibs-2.33-x86_64-2.txz. I installed the package with:
I changed my mirror to "file://home/<path>/mirror-slackware-current/Slackware/slackware64-current/" in /etc/slackpkg/mirrors and proceeded to complete the upgrade. No problems with slackpkg after that. Since I had not upgraded my laptop since before kernel-5.4.78, it was a huge upgrade and fairly complicated. I managed to do everything in the wrong order, but it still worked. I confess to being in a fog since daylight savings time.
My only comment is that slackpkg might be able to catch the error about GLIB and provide a more helpful hint. The slackpkg message was the gpg key was outdated and perhaps the selected mirror was also outdated.
@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 ?
@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
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.
Yes you can limit the mirroring, in fact you can only mirror one repository at a time; which repository is controlled by mirror-slackware-current.sh options.
The default is to mirror x86 -current.
I created and modified mirror-slackware-current.conf to use x64_64.
When I run mirror-slackware-current.sh via cron I use
Depending on which Slackware mirror I want to sync I run via bash:
Code:
mirror-slackware-current.sh # slackware64-current
mirror-slackware-current.sh -a x86 # slackware-current
mirror-slackware-current.sh -r 14.2 # slackware64-14.2
mirror-slackware-current.sh -r 14.2 -a x86 # slackware-14.2
Last edited by chrisretusn; 04-03-2021 at 08:35 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.