Ug. whenever we think we're going down the right track, we find more
information. But I guess, better to know it now then later.
http://irclogs.ubuntu.com/2012/04/03/%23ubuntu-devel.html#t00:19 is a
conversation between cjwatson, myself and infinity.
There, I find out
a. it is perfectly valid and supported to run 'localegen' for locales where no
corresponding language-pack-xx is installed
b. an easy way to check "is this locale currently valid" is to do:
import locale
try:
locale.setlocale(locale.LC_ALL, '') # or a specific locale as the
second argument
except locale.Error
That wont' involve apt (and thus will be quicker).
Because of 'a', cloud-init is not invalid in doing its 'locale-gen' on
possibly un-installed locales, so I think i'd just leave that as it is
for now.
And i think we can just handle package installation via informing the
user on login. This means really that the more difficult to get right
portion of this change (the package installation) can just be skipped.
What do you think, Ben?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859814
Title:
Locale issues with beta-1/2 cloud-images
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/859814/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
