pkgtool: problems with view and remove

scorpion77 · 08-10-2008, 08:53 AM

Hi to all,
I have just solved a problem with the displaying of files and directories with ntfs-3g (http://www.linuxquestions.org/questi...tfs-3g-661133/), but now a more serious problem is introduced. Pkgtool doesn't work as expected, the option View and Remove no longer work. If I decide to use View from KDE Konsole, it remains a black screen and does nothing. If I run it before starting the X server, remains the blinking cursor and does nothing. If you use Remove it displays immediately the following message:

Code:

------PACKAGE REMOVAL COMPLETE-------
| The packages have been removed. A |
| complete log of the files that    |
| were removed has been created in  |
| /var/log/setup/tmp:               |
| PKGTOOL.REMOVED.                  |
|-----------------------------------|
|             <  OK  >              |
-------------------------------------

This is the content of the file /var/log/setup/tmp/PKGTOOL.REMOVED:

No such package: Error:. Can't remove.
No such package: Expected. Can't remove.
No such package: 4. Can't remove.
No such package: arguments,. Can't remove.
No such package: found. Can't remove.
No such package: only. Can't remove.
No such package: 2.. Can't remove.
No such package: Use. Can't remove.
No such package: --help. Can't remove.
No such package: to. Can't remove.
No such package: list. Can't remove.
No such package: options.. Can't remove.

The strange fact is that if I change the language settings in files /etc/profile.d/lang.csh and /etc/profile.d/lang.sh setting setenv LANG it_IT instead of setenv LANG it_IT.utf8, pkgtool works perfectly.

So, I have two options:

1) I choose to see properly file names and directories, but pkgtool doesn't work as expected

2) pkgtool works perfectly, but I can't see properly file names and directories

Which option would you choose?

Obviously I choose the first option, but the doubt comes me that can be a bug of pkgtool, similar to this bug: http://www.linuxquestions.org/questi...hlight=pkgtool. In fact it seems absurd that you have to use a localization as simple as it_IT (which doesn't write all the characters), instead of using it_IT.utf8 as it happens in the others distros.
According to you is it the case to report it to Patrick?

Thanks for the help,

Scorpion77

T3slider · 08-10-2008, 01:13 PM

Does removepkg work as expected?

keefaz · 08-10-2008, 01:21 PM

Scorpion77, so you use the C shell instead of Bash ?
I think it is a Locale issue indeed, from your report
dunno what is it, maybe a basic syntax error on shell init files ?

Could you post /etc/profile.d/lang.csh & /etc/profile.d/lang.sh ?

scorpion77 · 08-10-2008, 05:21 PM

Quote:

Originally Posted by keefaz

Could you post /etc/profile.d/lang.csh & /etc/profile.d/lang.sh ?

Here it is lang.csh:

Code:

#!/bin/csh
# Set the system locale.  (no, we don't have a menu for this ;-)
# For a list of locales which are supported by this machine, type:
#   locale -a

# en_US is the Slackware default locale:
setenv LANG it_IT.utf8

# 'C' is the old Slackware (and UNIX) default, which is 127-bit
# ASCII with a charmap setting of ANSI_X3.4-1968.  These days,
# it's better to use en_US or another modern $LANG setting to
# support extended character sets.
#setenv LANG C

# There is also support for UTF-8 locales, but be aware that
# some programs are not yet able to handle UTF-8 and will fail to
# run properly.  In those cases, you can set LANG=C before
# starting them.  Still, I'd avoid UTF unless you actually need it.
#setenv LANG en_US.UTF-8

# Another option for en_US:
#setenv LANG en_US.ISO8859-1

# One side effect of the newer locales is that the sort order
# is no longer according to ASCII values, so the sort order will
# change in many places.  Since this isn't usually expected and
# can break scripts, we'll stick with traditional ASCII sorting.
# If you'd prefer the sort algorithm that goes with your $LANG
# setting, comment this out.
setenv LC_COLLATE C

# End of /etc/profile.d/lang.csh

Here it is lang.sh:

Code:

#!/bin/sh
# Set the system locale.  (no, we don't have a menu for this ;-)
# For a list of locales which are supported by this machine, type:
#   locale -a

# en_US is the Slackware default locale:
export LANG=it_IT.utf8

# 'C' is the old Slackware (and UNIX) default, which is 127-bit
# ASCII with a charmap setting of ANSI_X3.4-1968.  These days,
# it's better to use en_US or another modern $LANG setting to
# support extended character sets.
#export LANG=C

# There is also support for UTF-8 locales, but be aware that
# some programs are not yet able to handle UTF-8 and will fail to
# run properly.  In those cases, you can set LANG=C before
# starting them.  Still, I'd avoid UTF unless you actually need it.
#export LANG=en_US.UTF-8

# Another option for en_US:
#export LANG=en_US.ISO8859-1

# One side effect of the newer locales is that the sort order
# is no longer according to ASCII values, so the sort order will
# change in many places.  Since this isn't usually expected and
# can break scripts, we'll stick with traditional ASCII sorting.
# If you'd prefer the sort algorithm that goes with your $LANG
# setting, comment this out.
export LC_COLLATE=C

# End of /etc/profile.d/lang.sh

Thanks to all, but I already solved. I need to run pkgtool in this way: LANG=it_IT@euro pkgtool.
I already created an alias in .bashrc for convenience.

keefaz · 08-11-2008, 09:27 AM

Quote:

Originally Posted by scorpion77

[/code]Thanks to all, but I already solved. I need to run pkgtool in this way: LANG=it_IT@euro pkgtool.
I already created an alias in .bashrc for convenience.

Nice to hear your solved your problem yourself!
But out of curiousity, if you use csh shell, why do you edit your .bashrc file or if you use bash shell, why do you edit /etc/profile.d/lang.csh ?