Senhores,
Faz algum tempo que estou tendo problemas com o installpkg ou upgradepkg. Quando
utilizo algum dos dois comandos para instalar algum pacote, recebo mensagens como as
mostradas abaixo:
==============================================
cat: adm: No such file or directory cat: doc: No such file or directory cat: lib: No
such file or directory cat: mail: No such file or .
. directory cat: man: No such file or directory cat: sh: No such file or directory
cat: cat1:: No such file or directory cat: .
. alsactl.1.bz2: No such file or directory cat: date.1.bz2: No such file or directory
cat: fuser.1.bz2: No such file or directory cat: .
. lpr-cups.1.bz2: No such file or directory cat: ls.1.bz2: No such file or directory
cat: cat2:: No such file or directory cat: cat3:: No .
. such file or directory cat: cat4:: No such file or directory cat: cat5:: No such
file or directory cat: cat6:: No such file or directory .
. cat: cat7:: No such file or directory cat: cat8:: No such file or directory cat:
badblocks.8.bz2: No such file or directory cat: .
. checkpc.8.bz2: No such file or directory cat: ldconfig.8.bz2: No such file or
directory cat: mkisofs.8.bz2: No such file or directory .
. cat: mount.8.bz2: No such file or directory cat: warnquota.8.bz2: No such file or
directory cat: cat9:: No such file or directory cat: .
. catn:: No such file or directory cat: etc:: No such file or directory cat: X11: Is a
directory
==============================================
Isso porque eu reduzi a lista pra n�o ficar t�o grande. Os pacotes s�o instalados sem
problemas, mas ainda n�o consegui identificar o erro. Os arquivos de que ele reclama
est�o l�. Exemplo:
[EMAIL PROTECTED]:~# locate alsactl.1.bz2
/var/man/cat1/alsactl.1.bz2
Como parece que o erro vem de algum "cat" no script, procurei o que pudesse ser:
==============================================
[EMAIL PROTECTED]:~# grep cat /sbin/installpkg
# Redistribution and use of this script, with or without modification, is
cat << EOF
if cat $TMP/scan$$/install/doinst.sh | grep ' rm -rf ' 1>/dev/null 2>/dev/null ;
then
cat $TMP/scan$$/install/doinst.sh | grep ' rm -rf ' >
$TMP/scan$$/install/delete
echo "The following locations will be completely WIPED OUT to allow symbolic"
echo "links to be made. (We're talking 'rm -rf') These locations may be files,"
echo "locations that you want to save before you install this package:"
cat $TMP/scan$$/install/delete | cut -f 3,7 -d ' ' | tr ' ' '/'
# Locate package description file:
# First check the usual locations outside the package, since this is faster:
cat $DESCRIPTION | grep "^$packagebase:" | cut -f 2- -d : | cut -b2- 1>
$TMP/tmpmsg$$ 2> /dev/null
cat $DESCRIPTION | grep "^$shortname:" | cut -f 2- -d : | cut -b2- 1>>
$TMP/tmpmsg$$ 2> /dev/null
LENGTH=`cat $TMP/tmpmsg$$ | wc -l`
cat << EOF > $TMP/controlns$$
cat $DESCRIPTION | grep "^$packagebase:" | uniq
cat $DESCRIPTION | grep "^$shortname:" | uniq
dialog --title "Installing package ==>$shortname<== $PMSG" --infobox "`cat
$TMP/tmpmsg$$`" 0 0
dialog --title "Installing package ==>$shortname<== $PMSG" --infobox "`cat
$TMP/tmpmsg$$`" 0 0
dialog --title "Installing package ==>$shortname<== $PMSG" --infobox "`cat
$TMP/tmpmsg$$`" 0 0
dialog --title "Package Name: ==>$shortname<== $PMSG" --menu "`cat $TMP/tmpmsg$$`"
0 0 3 \
REPLY="`cat $TMP/reply$$`"
cat $TMP/tmplist$$ | grep -v "/$" | while read file ; do
cat $DESCRIPTION | grep "^$packagebase:" >> $ADM_DIR/packages/$shortname 2> /dev/null
cat $DESCRIPTION | grep "^$shortname:" >> $ADM_DIR/packages/$shortname 2> /dev/null
if [ "`cat $TMP/$shortname | grep '^./' | wc -l | tr -d ' '`" = "1" ]; then
cat $TMP/$shortname >> $ADM_DIR/packages/$shortname
cat $TMP/$shortname | grep -v '^./$' | cut -b3- >> $ADM_DIR/packages/$shortname
# /install/doinst.sh and /install/slack-* are reserved locations for the package
system.
==============================================
Mas n�o consegui localizar o que pode ser o problema. Apesar de os pacotes serem
instalados sem problemas quando utilizo os comandos na m�o, isso me gera problemas
quanto tento atualizar o gnome dropline por exemplo, porque como o return code da
instala��o do primeiro pacote � diferente de zero, ele n�o continua.
N�o me lembro quando isso come�ou a acontecer... se foi depois de atualizar/instalar
alguma coisa... :(
Algu�m tem uma dica?
Obrigado.
Andr� Aun
--
GUS-BR - Grupo de Usu�rios Slackware - BR
http://www.slackwarebrasil.org/
http://www.linuxmag.com.br/mailman/listinfo/slack-users
