[Slapt-get-devel] What about a

[Jason Woodward]

Hi Shingoshi,

>   1. gslapt is started and the system forgets to ask for a root passwd
>   (a real pain in KDE - the passwd isn't stored for non-KDE apps). It
>   will start an update (not an upgrade) and then promptly crash at the
>   end, without showing which packages have  updates available.

If you can reproduce this, run gslapt from an open terminal and let me know the output.  Also,
if this is still happening it would be interesting to see the output of

ls -la /etc/slapt-get /var/slapt-get

>   2. A package doesn't download/install properly. Gslapt will just
>   crash, as in closing. Any selections then have to be remade. (This is
>   the BIG one which occurs frequently. Especially if you deselect a
>   package that's required by another.)

Can you find out which package is failing?  It may be something the package is trying to do in
the install script that is causing installpkg (and family) to return non-zero.  If it is the
package trying to do something in the install.sh script (such as interactive prompts, etc) then
the package author needs to be informed.


take care,
jason
--
Jason Woodward
woodwardj at jaos.org