[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#322986: marked as done (locales: locales installation should be done earlier)

Your message dated Wed, 25 Apr 2007 23:56:18 +0200
with message-id <20070425215618.GA25214@.madism.org>
and subject line Bug#322986: locales: locales installation should be done earlier
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: locales
Version: 2.3.5-3
Severity: wishlist

I'm not sure which package this bug applies to. I noticed when
upgrading many packages at once (apt-get install a b c d...), one will
see many error messages, until finally we get here to installing
locales, with the same error message

Setting up locales (2.3.5-3) ...
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LC_MESSAGES = "C",
        LC_COLLATE = "C",
        LC_CTYPE = "zh_TW.Big5",
        LANG = "zh_TW.Big5"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Generating locales (this might take a while)...
  zh_TW.BIG5...^[OM done
Generation complete.

And from then on, the rest of the hundreds of packages I put on that
apt-get install line didn't produce such worrisome messages.

Therefore, somehow the locales stuff should be done earlier in the process...
-- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-k7
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5 (charmap=BIG5)

Versions of packages locales depends on:
ii  debconf                       1.4.57     Debian configuration management sy
ii  libc6 [glibc-2.3.5-3]         2.3.5-3    GNU C Library: Shared libraries an

locales recommends no packages.

-- debconf information:
* locales/default_environment_locale: zh_TW
* locales/locales_to_be_generated: zh_TW BIG5

--- End Message ---
--- Begin Message --- 
On Sun, Aug 14, 2005 at 01:50:39AM +0800, Dan Jacobson wrote:
> Package: locales
> Version: 2.3.5-3
> Severity: wishlist
> 
> I'm not sure which package this bug applies to. I noticed when
> upgrading many packages at once (apt-get install a b c d...), one will
> see many error messages, until finally we get here to installing
> locales, with the same error message
> 
> Setting up locales (2.3.5-3) ...
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
>         LANGUAGE = (unset),
>         LC_ALL = (unset),
>         LC_MESSAGES = "C",
>         LC_COLLATE = "C",
>         LC_CTYPE = "zh_TW.Big5",
>         LANG = "zh_TW.Big5"
>     are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> locale: Cannot set LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
> Generating locales (this might take a while)...
>   zh_TW.BIG5...^[OM done
> Generation complete.
> 
> And from then on, the rest of the hundreds of packages I put on that
> apt-get install line didn't produce such worrisome messages.
> 
> Therefore, somehow the locales stuff should be done earlier in the process...


  This is not a bug, here is the why: packages are supposed to "install
and work" (from a dpkg PoV) in any locale, it being C (which is often
the choice people do for root anyway) fr_FR en_GB or whatever choice you
did.

  Hence, the fact that locales are "not working" (in a sense that only C
is available for some time) temporarily during an upgrade is non
problematic, and we won't add pre-depends that would be worse.

  Problem is, perl is a dumbass that spits out a lot of warnings if the
locale is not available, and well, there is nothing we can do about
that. I suppose the "problem" is with debconf, that is mostly in perl
AFAICT, but well, when it shows its templates (configure time) locales
will be in a working state, so user will see the templates in the
correct locale.

  Closing the bug, feel free to open a bug on debconf on that matter.
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: pgp3qqtYgSzLN.pgp
Description: PGP signature


--- End Message ---
Reply to: