On 2017-01-24 I reported a bug in tazpkg at bugs.slitaz.org with ID 172.
On 2017-02-29 I found there a bug report for "Packages Category Displacement pkgs.cgi" with ID 172.
Today there is a bug report for "Grub does not allow for windows dual boot" with ID 172.
Seems that the ID is not incremented when a new bug is reported.

Bug in SliTaz Bug Tracker
(6 posts) (3 voices)-
Posted 8 years ago #
-
Hi,
Thanks for the analyse and feedback. Bug fixed: http://hg.slitaz.org/tazbug/rev/2228e0785489
Please add more bugs .-) http://bugs.slitaz.org/
- Christophe
Posted 8 years ago # -
I just entered a new bug report and a new id (173) was assigned.
Posted 8 years ago # -
Hi HGT,
Currently I can't post the reply on your bug 173 from my smartphone (I use Chrome), just nothing happened. So let me post my reply just here.
tazlocale
should do the work: http://hg.slitaz.org/slitaz-tools/file/781f12e0836c/tinyutils/tazlocaleSome script call the tazlocale without options at a boot time: you should read the message "Setting system locale to..." and then many symlinks should be fixed to point to your system locale.
The other deal, I think we should execute "tazlocale" in the post-install rules for tazpkg package, not only at a boot time, to get correct symlinks right after the package install. It also correct to some other packages affected.
Posted 8 years ago # -
I agree that tazlocale will do the work for the global setting.
The change I suggested will enable muliple users on the same system to get help from tazpkg in their own language, specified with the LANG variable.Posted 8 years ago # -
Oh sorry, I didn't got it then.
Really cool!Posted 8 years ago #
Reply
You must log in to post.