Re: Bug#508764: perl: Lots of locale warnings during upgrade
unmerge 508764
retitle 508764 perl: Lots of locale warnings during libc upgrade
thanks
On Mon, Dec 15, 2008 at 09:26:49AM +0100, Sven Joachim wrote:
> On 2008-12-15 04:15 +0100, Michael Biebl wrote:
> > I did a test upgrade from etch -> lenny. As soon as the new libc6 has
> > been unpacked, I get lots of those warnings:
> >
> > 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.
>
> > The sheer amount of those warnings, makes it hard to spot any real
> > important messages.
>
> The warning messages come from Perl, it should really stop this
> chattering IMHO. See #221790.
Sorry for the delay. I believe the same issue affects lenny->squeeze
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.
I only now noticed that setting the environment variable PERL_BADLANG=0
will disable these messages. See 'perldoc perllocale' for more
information; quoting:
Perl's moaning about locale problems can be silenced by setting the
environment variable PERL_BADLANG to a zero value, for example "0".
This method really just sweeps the problem under the carpet: you
tell Perl to shut up even when Perl sees that something is wrong.
Do not be surprised if later something locale-dependent misbehaves.
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.
--
Niko Tyni ntyni@debian.org
Reply to: