Pkgtool functions not working anymore

frushiyama · 12-15-2014, 07:15 PM

The function Remove from from pkgtool menu just says that the packages have been removed.
The View option returns to main menu.
I did installpkg on pkgtool from slackware tree and same results.
I am using slackpkg for a while but only saw this problem on pkgtool now, cant say that was after slackpkg .
Any hints on what i can try to find out what is happening?

ljb643 · 12-15-2014, 07:44 PM

If the View option shows you nothing, I wonder if your /var/adm/packages directory is empty? It should contain 1 file for each installed Slackware package.

mlslk31 · 12-15-2014, 09:08 PM

At casual glance, there's not much going on there other than dialog and removepkg, which in turn may make use of things like coreutils, find (findutils), and sed. Are all of these installed and working OK? And then there are the pkgtools themselves, and it probably helps to have bash as /bin/sh as well...

frushiyama · 12-16-2014, 05:25 PM

Quote:

Originally Posted by ljb643

If the View option shows you nothing, I wonder if your /var/adm/packages directory is empty? It should contain 1 file for each installed Slackware package.

No, it is normal, all packages folders are there.

Quote:

Originally Posted by mlslk31

At casual glance, there's not much going on there other than dialog and removepkg, which in turn may make use of things like coreutils, find (findutils), and sed. Are all of these installed and working OK? And then there are the pkgtools themselves, and it probably helps to have bash as /bin/sh as well...

I have this packages:
coreutils-8.21-x86_64-1
findutils-4.4.2-x86_64-1
sed-4.2.2-x86_64-1
All installed.

ljb643 · 12-16-2014, 06:59 PM

Quote:

The View option shows nothing and returns to main menu.

To clarify: Using root, you run pkgtool without arguments. From the menu, you select View and press Enter. You do, or do not get a list of installed packages at this time? (It could take a few seconds to generate the list.)

If you do get a list of packages from View, then you select any package and press Enter. Instead of seeing the package information and file list, you just get the pkgtool main menu again?

Although I agree with mislk31 that points to a possible problem with dialog, coreutils, sed, etc... I'm still suspicious of your /var/log/packages directory. How about trying these commands (not as root):

Code:

cd /var/log/packages
ls | wc -l   
grep -c '^PACKAGE NAME:' * | wc -l
grep -c '^FILE LIST:' * | wc -l

All 3 commands above should display the same number - the number of installed Slackware packages. If one of them shows a different number, you can use a command like this to find the offending files:

Code:

grep --files-without-match '^PACKAGE NAME:' *

frushiyama · 12-16-2014, 07:55 PM

Quote:

Originally Posted by ljb643

To clarify: Using root, you run pkgtool without arguments. From the menu, you select View and press Enter. You do, or do not get a list of installed packages at this time? (It could take a few seconds to generate the list.)

If you do get a list of packages from View, then you select any package and press Enter. Instead of seeing the package information and file list, you just get the pkgtool main menu again?

I do not get list a of files like usualy do, i get the pkgtool menu again.

Quote:

Originally Posted by ljb643

Although I agree with mislk31 that points to a possible problem with dialog, coreutils, sed, etc... I'm still suspicious of your /var/log/packages directory. How about trying these commands (not as root):

Code:

cd /var/log/packages
ls | wc -l   
grep -c '^PACKAGE NAME:' * | wc -l
grep -c '^FILE LIST:' * | wc -l

I have 1319 packages, all the same number from the ls and two grep commands like ljb643 said.

Quote:

Originally Posted by ljb643

All 3 commands above should display the same number - the number of installed Slackware packages. If one of them shows a different number, you can use a command like this to find the offending files:

Code:

grep --files-without-match '^PACKAGE NAME:' *

This had no output.

ljb643 · 12-16-2014, 09:25 PM

OK, thanks, sorry that didn't help except maybe to rule out a messed up package directory, and I'm out of ideas now.

mlslk31 · 12-16-2014, 09:59 PM

I just get fed up and reinstall stuff at this point. I might go in the order bash, pkgtools, coreutils, sed, findutils, util-linux. However pkgtool is a shell script, and there are two create_list_of functions that you can look at, after opening the file in a text editor. Maybe there's some obvious point where the script is failing.

Didier Spaier · 12-18-2014, 10:55 AM

Francis, I just tried and couldn't reproduce your issue.

Could you give some examples of packages with which you encountered these problems?

TLE · 12-18-2014, 04:31 PM

"I do not get list a of files like usualy do, i get the pkgtool menu again."

This is the same for me.
I can delete a package from remove menu but the view-mode does not work, half second and I'll come back to default menu again

SW current/32

mlslk31 · 12-18-2014, 04:49 PM

Maybe there's a language issue, with you posting from Sweden and the original poster posting from Brazil? So I ask blindly: Would it make a difference to start pkgtool as "env LC_ALL=C pkgtool" ?

Otherwise, I can produce this issue exactly only by starting pkgtool like "/bin/zsh pkgtool". A close second would be to remove sed or grep, but that doesn't cause returns to the main menu, it creates empty lists.

Didier Spaier · 12-18-2014, 05:00 PM

Quote:

Originally Posted by mlslk31

Maybe there's a language issue, with you posting from Sweden and the original poster posting from Brazil? So I ask blindly: Would it make a difference to start pkgtool as "env LC_ALL=C pkgtool" ?

Unlikely, IMO

Quote:

Otherwise, I can produce this issue exactly only by starting pkgtool like "/bin/zsh pkgtool". A close second would be to remove sed or grep, but that doesn't cause returns to the main menu, it creates empty lists.

AFAIK this is a bash script, not a zsh script.

frushiyama · 12-18-2014, 05:12 PM

Quote:

Originally Posted by mlslk31

Maybe there's a language issue, with you posting from Sweden and the original poster posting from Brazil? So I ask blindly: Would it make a difference to start pkgtool as "env LC_ALL=C pkgtool" ?

Otherwise, I can produce this issue exactly only by starting pkgtool like "/bin/zsh pkgtool". A close second would be to remove sed or grep, but that doesn't cause returns to the main menu, it creates empty lists.

Calling with env LC_ALL=C pkgtool and menus are back to normal.
My /etc/profile.d/lang.sh is export LANG=pt_BR.UTF-8 .

I use pt_BR.UTF-8 in slackware arm port which is still under pkgtools-14.1-noarch-1 and there this issue did not occur.

mlslk31 · 12-18-2014, 05:13 PM

Surprisingly, this part of pkgtool works with bash, ash, and ksh93. I haven't tried to execute the functions using non-bash shells, and that part might go differently. I even tried grabbing the latest bash out of slackware-current, and that changed nothing: Everything works well here. So my remaining option is to go home and look at it using a slackware-current that was installed just this morning, see if it's different. Either that or somebody would post snippets of script output, and I can see if it looks the same here.

TLE · 12-19-2014, 07:01 AM

Calling with env LC_ALL=C pkgtool is working fine for me

in: /etc/profile.d/lang.sh I have export: LANG=en_US.UTF-8

Same settings in SW 13.37 works fine with pkgtool