[Bug 1560577] Re: Confusing new locale-gen behavior

[Gunnar Hjalmarsson]

I made a couple of minor changes to the script (attached). Those changes
would improve it a bit IMO, if going back to the old script is
considered 'too much'. Especially they would prevent that a command like

sudo locale-gen en_US.UTF-8

or

sudo locale-gen --purge

results in a broken locale without the user being aware of what
happened. The modified script also allows multiple (valid) language code
arguments, so

sudo locale-gen en ja

generates the English and Japanese locales, and not only the Japanese.

** Patch added: "locale-gen.diff"
   https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1560577/+attachment/4608146/+files/locale-gen.diff

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1560577

Title:
  Confusing new locale-gen behavior

Status in glibc package in Ubuntu:
  New

Bug description:
  When the locales package was provided by the langpack-locales source
  package, you could call locale-gen with arguments. Examples:

  sudo locale-gen en_US.UTF-8
  (to generate that locale only)

  sudo locale-gen --purge
  (to purge all existing locales and create all locales)

  With the locales package provided by glibc, the equivalent to the
  latter seems to be:

  sudo locale-gen

  What's problematic is that if you add an argument (any argument), the
  existing locales seem to be purged, but nothing is generated. I'd
  consider this to be a pretty serious regression, which will likely
  result in locale issues for many users, if something isn't done to fix
  it. I'm not sure how to best deal with the problem, though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1560577/+subscriptions