Problem Testing Upgrading Slackware 14.2+

BW-userx · 08-04-2019, 07:26 PM

if you are ssh'ing in and the other side does it too have a .bashrc, or which side controls that? in that side I'd try setting in that something that would auto set your term to xterm so you can always be a happy camper whenever you're ssh'ing to update your system or even locally.

I update in Eterm too and have no issues btw. though it is an off shoot of xterm, now that I think about it.

codeguy · 08-04-2019, 07:38 PM

That helps me. But that doesn't help any other unsuspecting users. Maybe slackpkg could warn and exit. Or maybe set a compatible TERM for itself. Or maybe install that one package correctly regardless of TERM. Then nobody else would have to care.

BW-userx · 08-04-2019, 07:42 PM

the install scripts are scripts so they can be modified and submitted. I personally have never had this issue. this is the first time I've ever seen it.

mumahendras3 · 08-05-2019, 09:52 AM

I think somehow your system cannot find the apropriate xterm-256color terminfo. try running:

Code:

infocmp -I xterm-256color

and see if it can find the apropriate terminfo file and display the compiled capabilities info.

codeguy · 08-05-2019, 10:34 AM

Sorry, I already revert the VM and re-upgraded it. I have other setup/config/testing I need to get done.
I have scheduled downtime this Saturday night that I don't want to miss.

dugan · 08-12-2019, 06:10 PM

My guess:

The part that caused the problem was the doinst.sh file that was in the aaa_terminfo package. It has nothing to do with slackpkg; you would have had the same problem if you'd used upgradepkg instead of slackpkg.