[DRE-maint] Bug#725496: Bug#725496: Processed: severity of 725496 is grave

[Francesco Poli]

On Sun, 6 Oct 2013 19:49:48 -0300 Antonio Terceiro wrote:

[...]
> On Mon, Oct 07, 2013 at 12:11:46AM +0200, Francesco Poli wrote:
> > I don't want to ignore that!
[...]
> > If this is all confirmed, please feel free to raise the severity of
> > this bug report again and to file a new bug report against
> > apt-listbugs/0.1.10.
> > This new bug report could be titled something like "should not migrate
> > into testing until the .utf8 issue is solved", and should be of RC
> > severity and be blocked by 725496.

I've just filed this new bug report against apt-listbugs in order to
block its migration into testing.

> > 
> > I apologize, if I gave the impression that I wanted to neglect severe
> > issues!
> 
> The other day I was debugging this, I even asked on #debian-gnome about
> it. I thought it was a local problem with my system, didn't imagine it
> was a general problem.

Hello Antonio, thanks a lot for stepping in!

> 
> So the issue is: for some reason, gdm3 will set $LANG set to xx_YY.utf8
> to old user accounts, what triggers this bug, while new users will have
> $LANG set to xx_YY.UTF-8 which is handled correctly by ruby-gettext.

Awkward...

> 
> The underlying problem is how ruby-gettext maps the current locale into
> a valid Ruby encoding name ("UTF-8" and 'utf-8' are valid Ruby encoding
> names, 'utf8' without the dash is not).

This clarifies things a bit, thanks.

> 
> You can workaround this by clearing the "Language=" setting in
> /var/lib/AccountsService/users/$USER - in the next login, you will get
> LANG=xx_YY.UTF-8 in your environment (even though `locale -a` will still
> list it as xx_YY.utf8). I did this on my system, but telling every user
> out there to do this is not reallistic.

In the meanwhile we can tell the original bug report submitter about
this! I re-added him to the Cc list.

> 
> Anyway, I reported this issue a couple of weeks ago and upstream fixed
> it quickly after that:
> https://github.com/ruby-gettext/gettext/pull/20
> 
> > BTW, do you have any idea of how the issue could be fixed?
> 
> A new upstream release of ruby-gettext should fix this. I'm on it.

This is really great news, thank you very much!
I am looking forward to seeing this new version of ruby-gettext
uploaded to Debian sid.

Thanks for your helpfulness, Antonio!


-- 
 http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
 New GnuPG key, see the transition document!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20131007/81e48639/attachment.sig>