Hello,

I just upgraded to pkgtool 10.1 (a sign that we will soon see version 10.1?) and now the view option will simply not work. If I try it in a xterm, I will see the "Scanning"
message and then the screen will just go blank. If I try it in a tty the
"Scanning" message simply will not go away. The delete package option works
without problems.

Does anyone know what maybe the problem?

cccc828

strange the view option was supposed to work faster with the upgrade...I haven't tried it out yet but I will as soon as I get a little spare time to mess around

I have the same problem so you're not alone. Guess we may have to rollback to version 10.0

Mine seems to work fine. Just upgraded from the current tree 30 minutes ago.

Mine is also toast. Oh well. Back to 10.0.

I'm not sure why you folks are having trouble with the improved pkgtool but on my system it now takes 5 seconds instead of 2 minutes to view the installed pacakges. As a result, I'll be sticking with the new pkgtool.

Hmmm, I wonder... Did any of you guys/gals (who have trouble with the new 10.1 pkgtool) upgrade from Slack 9.x to 10.0? I'm just wondering if upgrading from a pre 10.x version may have something to do with the slow view. Of course I doubt that a version upgrade has anything to do with the problem, but I've seen stranger things before.

Mine also doesn't work and I'm on a Zipslack10 based install.

Nope I installed 10.0 from scratch. Does anyone have an idea how to debug pkgtool?

cccc828

I have been on -current for some time now, so 'technically' I did upgrade from 9.0, but ever so slowly over time.

Hmmm, which kernel are you using? I'm using 2.6.9 (which I custom compiled for my system). Prior to the new updated pkgtool the view feature took about 2 minutes to display anything on my screen. Once I updated to the 10.1 version of pkgtool my 2 minute wait dropped to 5 seconds. Of course unlike you, I don't have everything in my Slack 10 updated to current... I only pick and choose what I need/want to update.

p.s. My 2.6.9 kernel is also patched with the vm-pages patch.

I am using a 2.6.9 kernel, and have been on the 2.6.x series since 2.6.2.

pkgtool also used to take 2 mins to load 'View', but since the upgrade, all I get is a blank screen, after about 5 secs.

I've had the same problem for well over 2 months now. But i just go to 'Remove' and browse there instead...

My kernel was 2.4.27, and now its 2.4.28. Pkgtool 10.1 (on two machines)

That is what I do if I want to find out what is/is not installed.

But 'View' was useful for seeing where a particular package was putting everything. I was trying to compile ooO with -prefix=/usr , and wanted to see if everything was installing where I wanted it. I ended up just opening the .tgz package and looking that way, but it is a good way of finding out install paths of already installed software, of which you may not have the original .tgz anymore.

I am sure it is a conflict somewhere, maybe those of us who it doesn't work for can find the 'common link' in our slackware boxen.

So it is not the 2.6.x kernel.. Maybe it is only -current users that experience this error? Or anyone else install dropline 2.8.1 - maybe it is a problem with one of their 'replacement' packages? (although I doubt it as it still occurs without X even running)

TK.

I'm running -current with a custom 2.6.9 kernel (upgraded to current from a fresh full 10.0 install a few weeks ago, but with *no* Dropline now or ever) and I'm also suffering from the 'View' not working in pkgtool (the same as the problems described by the first poster in this thread).

So, not Dropline and not likely to be the kernel. What else?

I have got a custom 2.6.7 kernel and never installed dropline.

umm by the way: First removing pkgtool with removepkg and they trying to install it again with installpkg _does not_ work. Sigh... Let's see where I can find the source; Maybe a manual recompile will help; I will report if it worked.

[Update:] I "installed" pkgtools by simplay unpacking the _pkgtools.tar.gz in /slackware/slackware-current/source/a/pkgtools/. I did not really find a way to "compile" pkgtools.
[Update 2:] Umm I forgot pkgtools are just shell-scripts......

cccc828