LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-04-2019, 09:19 AM   #1
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Rep: Reputation: 42
Problem Testing Upgrading Slackware 14.2+


Testing Slackware-Current-That-Will-Become 15. Sorry, bad title, and I dont know how to edit it.

I'm updating a test box at work, and I seem to have crashed it pretty bad:

Quote:
Upgrading: aaa_base-14.2-x86_64-5: Basic Linux filesystem package ....................... [ 90K]
Package aaa_elflibs-15.0-x86_64-10.txz is already in cache - not downloading
Upgrading aaa_elflibs-15.0-x86_64-10...
Package aaa_terminfo-6.1_20190720-x86_64-1.txz is already in cache - not downloading
Upgrading aaa_terminfo-6.1_20190720-x86_64-1...
Upgrading: aaa_terminfo-6.1_20190720-x86_64-1: a basic collection of terminfo entries ... [850K]
tput: unknown terminal "xterm-256color"
expr: syntax error
expr: syntax error
Package aalib-1.4rc5-x86_64-6.txz is already in cache - not downloading
Upgrading aalib-1.4rc5-x86_64-6...
tput: unknown terminal "xterm-256color"
expr: syntax error
tput: unknown terminal "xterm-256color"
Upgrading: Usage: installpkg [options] <package_filename>

Installpkg is used to install a .t{gz,bz,lz,xz} package like this:
installpkg slackware-package-1.0.0-i486-1.tgz (or .tbz, .tlz, .txz)

options: --warn (warn if files will be overwritten, but do not install)
--root /mnt (install someplace else, like /mnt)
--infobox (use dialog to draw an info box)


My TERM is indeed set to xterm-256color, I have no idea why. I probably changed it, but so long ago that I dont remember.

Last edited by codeguy; 08-04-2019 at 03:23 PM. Reason: 15 is not released
 
Old 08-04-2019, 09:40 AM   #2
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Original Poster
Rep: Reputation: 42
The box is a remote headless box. My update looks like:

Quote:
add to mirrors: file://mnt/share/
slackpkg update
slackpkg upgrade glibc-solibs pkgtools slackpkg

re-add to mirrors: file://mnt/share/
slackpkg update

slackpkg install-new
slackpkg clean-system
slackpkg upgrade-all
 
Old 08-04-2019, 09:47 AM   #3
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Original Poster
Rep: Reputation: 42
I notice, the instructions here: https://docs.slackware.com/howtos:sl...:systemupgrade

Quote:
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system
And I did:

Quote:
# slackpkg install-new
# slackpkg clean-system
# slackpkg upgrade-all
Did I delete something that might have been needed during the update?
 
Old 08-04-2019, 10:00 AM   #4
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Original Poster
Rep: Reputation: 42
I manually reinstalled the new aaa_terminfo and ncurses, but slackpkg upgrade-all was still very upset by TERM=xterm-256color. I ran "export TERM=xterm", and then it took off and ran fine.
 
Old 08-04-2019, 10:55 AM   #5
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Original Poster
Rep: Reputation: 42
Nope, not the order of clean-system/upgrade-all. I tested on a VM (which I've snapshot so I can roll back and try again), I tested the update in correct order:
Quote:
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system
I still get the same problem.
I also found all the boxes I connect to have the same TERM=xterm-256color
Is that a default? Am I just consistent?
 
Old 08-04-2019, 12:40 PM   #6
jr_bob_dobbs
Member
 
Registered: Mar 2009
Distribution: Slackware, Linux From Scratch, Bedrock
Posts: 361
Blog Entries: 51

Rep: Reputation: 35
DUDE! Slackware 15??????? FINALLY!

Just checked www.slackware.com... Slackware 15 is not mentioned.

I am confused. Are my hopes dashed?
 
Old 08-04-2019, 01:38 PM   #7
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Original Poster
Rep: Reputation: 42
Yep, sorry. I could have titled the post "Upgrade problem with slackware-current", but then when slackware 16 came out you wouldn't know if I was talking about slackware-current-to-be-15 or slackware-current-to-be-16. So I titled it "slackware-15". I probably should call it "slackware-beta-15".
 
Old 08-04-2019, 02:17 PM   #8
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,615

Rep: Reputation: 6041Reputation: 6041Reputation: 6041Reputation: 6041Reputation: 6041Reputation: 6041Reputation: 6041Reputation: 6041Reputation: 6041Reputation: 6041Reputation: 6041
Quote:
Originally Posted by codeguy View Post
I probably should call it "slackware-beta-15".
There is no such thing at the moment as a Beta release of Slackware 15. Your thread title will confuse people in the long run anyway. Better call it "Slackware 14.2+" as that is the formal name:
Code:
$ cat /etc/slackware-version
Slackware 14.2+
 
Old 08-04-2019, 02:53 PM   #9
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: FreeBSD/Slackware-14.2+/ArcoLinux
Posts: 8,981

Rep: Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874
first off, go into your orginal post and click edit, then advance you should see where you can change your title part.

second slackpkg clean-system, removes everything that is not part of the original install, not including updates, but 3rd party install of anything in the package dir.

three what seems to be the actual issue,a terminal did not get updated?
Code:
tput: unknown terminal "xterm-256color"
look in your .bashrc, and if you find anything that says that comment it out, if not try doing an update in a different terminal. then if it works you know you'll need to trouble shoot that one terminal that you had that message.
 
Old 08-04-2019, 03:46 PM   #10
mumahendras3
LQ Newbie
 
Registered: Feb 2018
Location: Indonesia
Distribution: Obarun, Slackware
Posts: 19

Rep: Reputation: Disabled
Code:
tput: unknown terminal "xterm-256color"
Try checking if the /usr/share/terminfo/x/xterm-256color file exists or not. I got that same error at my Slackware-current installation when that file is missing. Perhaps you can set TERM=linux first, then reinstall the ncurses package and make sure /usr/share/terminfo/x/xterm-256color (and potentially other terminfo files) are not missing.
 
Old 08-04-2019, 05:16 PM   #11
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Original Poster
Rep: Reputation: 42
I cannot find anyplace where I set TERM. I checked my local pc at home (which is running slackware-current), and the server that I'm ssh'ing into (which was on 14.2). Nothing in .bash_profile (and no .bashrc).


/usr/share/terminfo/x/xterm-256color does exist:
Quote:
root@athenavm:~# ll /usr/share/terminfo/x/xterm-256color
-rw-r--r-- 1 root root 2.4K Jul 22 13:40 /usr/share/terminfo/x/xterm-256color
root@athenavm:~#
root@athenavm:~# slackpkg upgrade-all

Checking local integrity... tput: unknown terminal "xterm-256color"
tput: unknown terminal "xterm-256color"
/tput: unknown terminal "xterm-256color"
DONE
tput: unknown terminal "xterm-256color"
Looking for packages to upgrade. Please wait... tput: unknown terminal "xterm-256color"
tput: unknown terminal "xterm-256color"
/tput: unknown terminal "xterm-256color"

 
Old 08-04-2019, 05:23 PM   #12
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: FreeBSD/Slackware-14.2+/ArcoLinux
Posts: 8,981

Rep: Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874
what terminal (brand) are you using?
echo $TERM what do you get in the terminal that is giving you this error?

read this.
https://better-coding.com/solved-xte...terminal-type/

Code:
$ echo $TERM
xterm-256color
that is what I am showing on my terminal.
 
Old 08-04-2019, 06:20 PM   #13
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Original Poster
Rep: Reputation: 42
My PC at home is running xfce and I'm using xfce4-terminal.
After connecting to the remote box:
Quote:
root@athenavm:~# echo $TERM
xterm-256color
Sure, changing my term makes it work. That's not the question.

On the broken vm, top fails (just like in your link). If I change TERM=xterm and finish the update, then reset TERM=xterm-256color then top works fine.

I was able to install packages up to aaa_terminfo-6.1_20190720-x86_64-1, then it died.
 
Old 08-04-2019, 07:13 PM   #14
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: FreeBSD/Slackware-14.2+/ArcoLinux
Posts: 8,981

Rep: Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874Reputation: 1874
when you say it just died, what do you mean?
finished installing that update then stopped leaving nothing but a prompt?

I do not ssh, but I'd think if you need to set your term = xterm update system then I'd not reset it back. Because next log in it should already be back to where it was leaving you with having to set term=xterm again any ways. Just like using any terminal, here I do this then close Eterm and open it again and it is back to Eterm again.
Code:
userx@slack.it.netters:~
$ echo $TERM
Eterm
userx@slack.it.netters:~
$ export TERM=xterm
userx@slack.it.netters:~
$ echo $TERM
xterm

userx@slack.it.netters:~
$ echo $TERM
Eterm
the it just died does leave me slightly confused, a little more detail on that would be nice.

Last edited by BW-userx; 08-04-2019 at 07:23 PM.
 
Old 08-04-2019, 07:22 PM   #15
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Original Poster
Rep: Reputation: 42
If your TERM=xterm-256color and you run "slackpkg upgrade-all" you'll get when I got in my first post.
If your TERM=xterm and you run "slackpgk upgrade-all" your a happy camper.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Testing Testing My Linux Counter rtrahan Linux - Newbie 3 02-23-2009 05:25 AM
testing iptables performance testing pavan.daemon Linux - Networking 2 09-28-2007 05:22 PM
Replace 'etch' with 'testing' in /etc/apt/sources.list to track 'testing' branch? Akhran Debian 3 04-09-2007 10:45 AM
Sarge-testing To Etch-testing? SMurf7 Debian 3 02-21-2006 10:59 PM
Setup as getting debian testing files from ftp - will it stay with testing BrianHenderson Debian 2 09-02-2004 06:06 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:08 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration