Please wait...error: line 10: Dependency tokens must begin with alpha-numeric
On AIX if you run the command updtvpkg to update the rpm database you can have a error like:
I dont have much time to digg more deeper on this problem but from what I found is happens because the updtvpkg try to calculate the library dependency and happens to find the file above .nfs0BF6 in a folder scanned by the command.
If you check the command, it is a script, you will see the following part:
This specific part:
You can run it on the terminal is responsible for the first part of the scan, is where that bad fille was showing.
To temporally fix the issue I just edited the command, make a backup before:
Notice that for the lslpp command I put a new pipe filtering with grep -v nfs0BF6
So the script will continue to execute normally.
You can face similar error so this post can help.
Please wait...error: line 10: Dependency tokens must begin with alpha-numeric, '_' or '/': Provides: .nfs0BF6
I dont have much time to digg more deeper on this problem but from what I found is happens because the updtvpkg try to calculate the library dependency and happens to find the file above .nfs0BF6 in a folder scanned by the command.
If you check the command, it is a script, you will see the following part:
Packager: auto-generated"
# Check for local shared libraries
/usr/bin/lslpp -Ou -qfc | /usr/bin/cut -d':' -f3 | /usr/bin/cut -d' ' -f1 |\
/usr/opt/rpm/lib/rpm/find-provides | while read shobj
do
echo "Provides: $shobj"
done
This specific part:
/usr/bin/lslpp -Ou -qfc
You can run it on the terminal is responsible for the first part of the scan, is where that bad fille was showing.
To temporally fix the issue I just edited the command, make a backup before:
# Check for local shared libraries
/usr/bin/lslpp -Ou -qfc|grep -v nfs0BF6| /usr/bin/cut -d':' -f3 | /usr/bin/cut -d' ' -f1 |\
/usr/opt/rpm/lib/rpm/find-provides | while read shobj
do
echo "Provides: $shobj"
done
Notice that for the lslpp command I put a new pipe filtering with grep -v nfs0BF6
So the script will continue to execute normally.
You can face similar error so this post can help.
Comentários
Postar um comentário