Re: Bug#508764: perl: Lots of locale warnings during upgrade
- To: Sven Joachim <firstname.lastname@example.org>
- Cc: Michael Biebl <email@example.com>, firstname.lastname@example.org, email@example.com
- Subject: Re: Bug#508764: perl: Lots of locale warnings during upgrade
- From: Niko Tyni <firstname.lastname@example.org>
- Date: Wed, 22 Sep 2010 14:04:22 +0300
- Message-id: <20100922110422.GA19536@madeleine.local.invalid>
- In-reply-to: <20100917201820.GA12748@madeleine.local.invalid>
- References: <email@example.com> <firstname.lastname@example.org> <20100917201820.GA12748@madeleine.local.invalid>
On Fri, Sep 17, 2010 at 11:18:20PM +0300, Niko Tyni wrote:
> On Mon, Dec 15, 2008 at 09:26:49AM +0100, Sven Joachim wrote:
> > On 2008-12-15 04:15 +0100, Michael Biebl wrote:
> > > perl: warning: Setting locale faile
> > > perl: warning: Please check that your locale settings:
> > > LANGUAGE = (unset)
> > > LC_ALL = (unset)
> > > LANG = "de_DE.UTF-8"
> > > are support and installed on your system.
> > > perl: warning: Falling back to the standard locale ("C").
> > You see this because the old locales package is not compatible with the
> > new libc6 and has been auto-deconfigured. These messages go away after
> > the new locales package has been configured, which unfortunately does
> > happen rather late during dist-upgrades.
> While I don't think the chattering should be disabled in the general
> case (which is what #221790 is about, so unmerging), I certainly see the
> point for silencing it during package upgrades where the locale problem
> is very often transient.
> Cc'ing the dpkg maintainers. What do you think about making dpkg set
> PERL_BADLANG=0 when running maintainer scripts? I think that's the only
> place where it could be done.
Alternatively, I suppose I could patch perl to also quelch the warnings
when DPKG_RUNNING_VERSION is set (or should it rather be one of the
DPKG_MAINTSCRIPT_* variables ?).
This seems somewhat cleaner to me, but opinions would be welcome.
FWIW, I see mandb outputs similar warnings so the issue isn't limited
to just perl.
Niko Tyni email@example.com