Steps to reproduce: 1. If UTF-8 locale isn't yet defined, run this as root: localedef -i en_US -f UTF-8 en_US.UTF-8 2. Set the locale and run qpkg: export LC_ALL=en_US.UTF-8 qpkg -i -v someebuild
confirmed... qpkg hangs on EVERY locale other then "POSIX".. BUT it not hangs only the time is TOOO long... after some inspecting it is on sed command in section # not installed packages (yet :-) starting at line 306 and exactly the section if [ ${arg} ]; then ... on line 312 on command sed -e "s: :\n:g in locale affected console a) this command works for 1-100000 caracters without problems tested by command echo ... | cut -b1-100000| sed -e ... after this the time of execution time is too long... I have no idea why 100000 characters is the limit... my test program for experimenting... #!/bin/sh upak=`find /usr/portage/ -iname "*.ebuild" 2>/dev/null|grep -v --regex="/usr/portage/[^/]*\.ebuild"` #upak=`echo ${upak}|sed -e "s: :\n:g"|grep jboss` #upak=`echo ${upak}|cut -b1-100000 |sed -e "s: :\n:g"` upak=`echo ${upak}|sed -e "s: :\n:g"` echo ${upak}
this is still valid, any idea?
Yes, this is still valid, just checked with the latest stable version of qpkg.
> qpkg hangs on EVERY locale other then "POSIX".. Not really. It does hang on ru_RU.UTF-8 for me but works just fine on ru_RU.KOI8-R...
How about just setting LC_ALL to POSIX in qpkg? Either that, or changing LC_ALL temporarily when running sed. Afaik, there are no ebuilds in portage that contain locale specific information. Or are there?
this tool is deprecated
If this tool is deprecated, please print a warning to stderr saying exactly that and which tool to use instead.
