Which ones to pick to delete for botched upgrade ( current )?
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.
Which ones to pick to delete for botched upgrade ( current )?
upgrade all was still in operation, when I switched ttys. which I've done before, leaving whatever is running in the gui running, and nothing happens it just keeps on going.
this time it kicked my out of the gui and show a message on tty1 no server authorization. then when I logged back in to the terminal/console ran startx again then ran update slack ( current ) I got the delete the pid file of course, then I get this list ..
Code:
$ slackall
Checking local integrity... mv: cannot stat '/var/log/scripts/urwid-1.0.3-x86_64-3-upgraded-2019-02-26,07:33:20': No such file or directory
mv: cannot stat '/var/log/scripts/xcalc-1.0.6-x86_64-3-upgraded-2019-02-26,07:33:26': No such file or directory
mv: cannot stat '/var/log/scripts/xcb-proto-1.13-x86_64-2-upgraded-2019-02-26,07:33:27': No such file or directory
mv: cannot stat '/var/log/scripts/xclock-1.0.7-x86_64-3-upgraded-2019-02-26,07:33:28': No such file or directory
mv: cannot stat '/var/log/scripts/xev-1.2.2-x86_64-2-upgraded-2019-02-26,07:33:29': No such file or directory
mv: cannot stat '/var/log/scripts/xfsinfo-1.0.5-x86_64-3-upgraded-2019-02-26,07:33:30': No such file or directory
mv: cannot stat '/var/log/scripts/xhost-1.0.7-x86_64-2-upgraded-2019-02-26,07:33:32': No such file or directory
mv: cannot stat '/var/log/scripts/xlsatoms-1.1.2-x86_64-2-upgraded-2019-02-26,07:33:33': No such file or directory
mv: cannot stat '/var/log/scripts/xmodmap-1.0.9-x86_64-2-upgraded-2019-02-26,07:33:34': No such file or directory
mv: cannot stat '/var/log/scripts/xrdb-1.1.1-x86_64-2-upgraded-2019-02-26,07:33:35': No such file or directory
mv: cannot stat '/var/log/scripts/xstdcmap-1.0.3-x86_64-3-upgraded-2019-02-26,07:33:35': No such file or directory
mv: cannot stat '/var/log/scripts/xvinfo-1.1.3-x86_64-2-upgraded-2019-02-26,07:33:37': No such file or directory
DONE
You have a broken /var/log/packages/ - with two versions of the same package.
The list of packages duplicated in your machine are shown below, but don't
worry about this list - when you select your action, slackpkg will show a
better list:
lxc-2.0.9_d3a03247-x86_64-1
lxc-2.0.9_d3a03247-x86_64-2
mariadb-10.3.12-x86_64-1
mariadb-10.3.13-x86_64-1
meson-0.49.2-x86_64-1
meson-0.49.2-x86_64-2
mozilla-firefox-60.5.1esr-x86_64-1
mozilla-firefox-60.5.2esr-x86_64-1
newt-0.52.20-x86_64-3
newt-0.52.20-x86_64-4
obexftp-0.24.2-x86_64-3
obexftp-0.24.2-x86_64-4
openvpn-2.4.6-x86_64-2
openvpn-2.4.7-x86_64-1
p2c-1.21alpha2-x86_64-4
p2c-2.01-x86_64-1
parallel-20190122-noarch-1
parallel-20190222-noarch-1
pcre-8.42-x86_64-2
pcre-8.43-x86_64-1
pssh-2.3.1-x86_64-3
pssh-2.3.1-x86_64-4
pycairo-1.18.0-x86_64-1
pycairo-1.18.0-x86_64-2
pycups-1.9.74-x86_64-1
pycups-1.9.74-x86_64-2
pycurl-7.43.0.2-x86_64-1
pycurl-7.43.0.2-x86_64-2
pygobject-2.28.7-x86_64-2
pygobject-2.28.7-x86_64-3
pygobject3-3.30.4-x86_64-1
pygobject3-3.30.4-x86_64-2
pykde4-4.14.3-x86_64-7
pykde4-4.14.3-x86_64-8
pyparsing-2.3.1-x86_64-1
pyparsing-2.3.1-x86_64-2
python-appdirs-1.4.3-x86_64-2
python-appdirs-1.4.3-x86_64-3
python-certifi-2018.11.29-x86_64-1
python-certifi-2018.11.29-x86_64-2
python-chardet-3.0.4-x86_64-2
python-chardet-3.0.4-x86_64-3
python-docutils-0.14-x86_64-2
python-docutils-0.14-x86_64-3
python-idna-2.8-x86_64-1
python-idna-2.8-x86_64-2
python-notify2-0.3.1-x86_64-2
python-notify2-0.3.1-x86_64-3
python-packaging-19.0-x86_64-1
python-packaging-19.0-x86_64-2
python-pillow-5.4.1-x86_64-1
python-pillow-5.4.1-x86_64-2
python-pip-19.0.2-x86_64-1
python-pip-19.0.3-x86_64-1
python-requests-2.21.0-x86_64-1
python-requests-2.21.0-x86_64-2
python-sane-2.8.3-x86_64-2
python-sane-2.8.3-x86_64-3
python-setuptools-40.8.0-x86_64-1
python-setuptools-40.8.0-x86_64-2
python-six-1.12.0-x86_64-2
python-six-1.12.0-x86_64-3
python-urllib3-1.24.1-x86_64-1
python-urllib3-1.24.1-x86_64-2
python3-3.6.8-x86_64-1
python3-3.7.2-x86_64-1
rpm-4.14.2.1-x86_64-1
rpm-4.14.2.1-x86_64-2
sip-4.19.8-x86_64-2
sip-4.19.8-x86_64-3
system-config-printer-1.5.11-x86_64-3
system-config-printer-1.5.11-x86_64-4
talloc-2.1.15-x86_64-1
talloc-2.1.15-x86_64-2
tar-1.31-x86_64-1
tar-1.32-x86_64-1
tdb-1.3.17-x86_64-1
tdb-1.3.17-x86_64-2
tevent-0.9.38-x86_64-1
tevent-0.9.38-x86_64-2
urwid-1.0.3-x86_64-3
urwid-1.0.3-x86_64-4
util-linux-2.33.1-x86_64-1
util-linux-2.33.1-x86_64-2
xcalc-1.0.6-x86_64-3
xcalc-1.0.7-x86_64-1
xcb-proto-1.13-x86_64-2
xcb-proto-1.13-x86_64-3
xclock-1.0.7-x86_64-3
xclock-1.0.8-x86_64-1
xev-1.2.2-x86_64-2
xev-1.2.3-x86_64-1
xfsinfo-1.0.5-x86_64-3
xfsinfo-1.0.6-x86_64-1
xfsprogs-4.19.0-x86_64-1
xfsprogs-4.20.0-x86_64-1
xhost-1.0.7-x86_64-2
xhost-1.0.8-x86_64-1
xlsatoms-1.1.2-x86_64-2
xlsatoms-1.1.3-x86_64-1
xmodmap-1.0.10-x86_64-1
xmodmap-1.0.9-x86_64-2
xrdb-1.1.1-x86_64-2
xrdb-1.2.0-x86_64-1
xstdcmap-1.0.3-x86_64-3
xstdcmap-1.0.4-x86_64-1
xvinfo-1.1.3-x86_64-2
xvinfo-1.1.4-x86_64-1
You can (B)lacklist, (R)emove, or (I)gnore these packages.
Select your action (B/R/I):
the ones that have the same version but are tagged at the end -1, -2, or -3, -4 which is the newer one, or which one to delete, keeping the higher (numbered) version?
Reinstalling from a -current ISO kindly provided by alienBoB after the needed backup is most probably the safest and fastest way to recover.
Are you suggesting deleting everything in that list then reinstalling off a current iso from AlienBob?
what is that line? I've seen it in here but when I actually want to use it I can never find it. something like
Code:
installpkg install-new -reinstall pkg name
it being in a loop in this case. or update too just in case the whatever ones are out dated to the current current dvd iso... because it might staill end up with ixed packages from what is installed and what is on a current date 2019-02-24 23:16 as I am down loading one right now.
then just running update again to see if any changes need to take place...
1) Download the latest versions of each of those packages from a Slackware mirror and put them somewhere, e.g. $HOME/packages.
2) Use removepkg to remove the lower-numbered version of each package listed above. Keep the higher-numbered versions. Then,
3) upgradepkg --reinstall $HOME/packages/*.t?z
That should safely take care of the issue. removepkg does not remove any file that is present in another package, so you should still have a functioning system after step 2. Of course, it is always a good idea to do a backup first before operations like this.
It's about time for you to learn the basics of Slackware I think. Do this:
man installpkg
man removepkg
man upgradepkg
Anyway if you want to use -current better follow the ChangeLog for current and use the basic packaging tools. Or (safer) stay on 14.2 for now.
Sorry to be blunt, that's my mood right now.
Best,
I understand moods, and I do not use reinstall new, I do not use them commands enough to even remember them out of repetition, the only ones I've never had to really use I put into them alias to cut back on having to write all of that out each time. hence the alias'es.
and No I am not doing a re-install of basic slack 14.2, it is too out dated for me, for one, and I've been running current for a while. I just ran into this snafu is all. as stated I do not find myself ever having to use these commands ever, I've only seen them being suggested in the forum and now I seem to need to use them. Nothing wrong with asking.
I was mearly asking what to do with the ones I as not sure about . this is not the first time I've had dups in my packages. Just not a complete screw up like this due to some ill-rational behavior from the system to create such a long list.
Keep older version and then try to upgrade again. The correspondence between package description and what is already installed can completely broken - but keeping older you are assured that there are or old files or new. So if you will succeed with repeated upgrade - you should end with new files on disk.
Keep older version and then try to upgrade again. The correspondence between package description and what is already installed can completely broken - but keeping older you are assured that there are or old files or new. So if you will succeed with repeated upgrade - you should end with new files on disk.
that is a good idea... instead of visa versa the way I usually do it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
