You are not logged in.
Hey There,
Because of the locale problem in pacman (for Turkish locale), i have to change my locales everytime.. It's said that it has been resolved in Pacman 3.1 but today I just upgraded to Pacman 3.0.5.. Can someone tell me why it's not fixed in 3.0.5 or why we should we wait ?
Quis custodiet ipsos custodiet?
Offline
http://bugs.archlinux.org/task/7235?histring=turkish
Oh this didn't make it to cvs then ? I asked on the ML : http://www.archlinux.org/pipermail/pacm … 08546.html
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Shoot. I missed this bug when doing the 3.0.5 release- sorry about that. 3.1 is still a ways off- we need a lot of small usability fixes to it before it is ready to be put into the wild. I don't want to set a for-sure timetable, as I haven't really ran it over with anyone else, but would think late July or early August is a possibility.
Offline
Until then, no pacman release like 3.0.6 released ? is there a possibility for the patch to be added ?
Quis custodiet ipsos custodiet?
Offline
I'm sure that, if possible, there will be backports made.
Offline
Well, I don't know if 3.0.6 could be released just because of one non critical fix (it doesn't affect everyone and there is the very easy workaround of using LANG=C).
Still, I should have checked it was applied in cvs after finding the bug, sorry for that.
In the meantime, it's very easy to make to fix it yourself.
Otherwise you can get the package here : http://chantry.homelinux.org/~xav/pkg/p … pkg.tar.gz
or the pkgbuild here with the patch : http://chantry.homelinux.org/~xav/pkg/pacman.tar.gz
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
It's amazing.. When I do,
pacman -Syu
the problem doesn't appears. But when I do, other things such as
pacman -Ss or pacman -Qs
the problem occurs again.. :S
Quis custodiet ipsos custodiet?
Offline
It's amazing.. When I do,
pacman -Syu
the problem doesn't appears. But when I do, other things such as
pacman -Ss or pacman -Qs
the problem occurs again.. :S
Hmm, yes, that's very odd indeed.. Not sure why, because I would think that pacman.conf needs to be read in any cases (thus parse_config called). Strange..
I updated my package because of this : http://archlinux.org/news/334/ (warning, this fixed a critical issue, but caused a new problem : http://bugs.archlinux.org/task/7484 )
but kept the same revision number.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline