Re: perl locale
Aren't you runnig woody? Two days ago I did an aborted experiment to
dist-upgrade from potato to woody. I kept getting the same messages,
but before that there was a different perl problem, with a little
bit more info (Thanks to the peple on this list I did this upgrade
on a clone of my system, so I am happily using my old potato still).
So I have no idea how to fix this, but there were someone who seemed
to fix the other perl problem (which maybe caused this one). So I
attached the message from this list. It may help...
Hope this helps... -- Viktor
P.s. I just realized, that this guy answered you when you wanted to
upgrede to sid...I still think he can help your second problem too..
Sorry if this is no help...
On Mon, May 14, 2001 at 06:34:01PM -0400, MaD dUCK wrote:
> hey guys,
> whenever i use perl (rename, apt-get/dpkg, anything), i get
>
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = (unset),
> LC_ALL = (unset),
> LANG = "en"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
>
> this is really annoying and i know way to little about perl so as to
> be able to fix this myself. please please ... any tips?
>
> martin; (greetings from the heart of the sun.)
> \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck
> --
> > is there anything else i can contribute?
> the latitude and longitude of the bios writers'
> current position, and a ballistic missile.
> -- alan cox
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
--- Begin Message ---
On Sat, May 12, 2001 at 01:08:03PM -0400, MaD dUCK wrote:
> hey guys,
> i would finally like to pull one of my systems up to testing, but i
> still can't really afford losing it, so i am a little cautious. i
> guess i would simply like to know if anyone of you had previous bad
> experiences with the dist-upgrade. i am on a laptop, currently running
> potato with a custom kernel 2.4.4 and pcmcia-cs build. should i just
> do it? it isn't reversible, is it?
>
I went potato -> woody on my home system about a week ago, and got
sidetracked for a bit by a couple of bugs, both of which are documented
in the Debian bug system. I was able to work through both, and am
very happy with woody on that machine. However, my production server is
gonna stay potato for now :P.
Early in the install, perl got into a state where it could not find
Glob.pm. This hosed installation scripts on several packages, preventing
them from configuring, which blocked many more packages. I was able
to work through this one by figuring out which perl packages *would*
install
and installing them manually via dpkg -i . This went quickly, since the
required packages were alrealy sitting in apt's cache.
I had a hard time getting an xserver to configure (either version 3 SVGA or
the version 4 server). The postinstall script failed. I saw in the
bug data base where Brandon directed the person who reported this bug to
use a specific commandline to run the postinstall script manually. I
did this on my machine. The script still exited with an error, but
something changed, and one more trip through configure resulted in a
correctly configured server.
I am using ximian gnome 1.4, and got into a dependency conflict with
gnomeprint or something to do with gnumeric.
I just ditched gnomeprint and gnumeric rather than spending time figuring
out a fix.
Hope this helps.
Mike
rather than spending time figuring out a fix.
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--- End Message ---
Reply to: