On Wed, Aug 17, 2011 at 04:30:29PM +0200, Benjamin Cama wrote: > Le mercredi 17 août 2011 à 14:48 +0200, Aurelien Jarno a écrit : > > On Wed, Aug 17, 2011 at 12:46:25PM +0200, Benjamin wrote: > > > Package: locales-all > > > Version: 2.13-14 > > > Severity: important > > > Tags: sid > > > > > > Hi, > > > > > > Some days ago, locales-all got upgraded on my system during a > > > dist-upgrade, and > > > I didn't notice it. After a reboot some time later, I lost my locale > > > > What do you mean by "I lost my locale"? Did you do something special? > > I mean that after I rebooted, the current locale was now C and I > couldn't change for another one. Accents and others non-ASCII stuff got > screwed up in many applications. > > The only action I took was rebooting some days after upgrading to > 2.13-14 (I don't reboot very often), and that caused this “lost” locale.
My guess is that /usr/lib/locale/locale-archive got correupted. > > > (fr_FR.UTF-8) and dpkg-reconfigure could not generate it back with this > > > > With locales-all, locales are not generated, that's actually the goal of > > locales-all. Which command did you run? > > dpkg-reconfigure locales, choose fr_FR.UTF-8, select it as default for > the system. I never meant to install locales-all at first, I don't know > how it stepped in some months ago. The strange thing is that this > problem only happened when upgrading locales-all to 2.13-14: it didn't > cause any problem before. > > Anyway, with locales-all (2.13-14) installed, I _couldn't_ get any other > locale than C to work. I guess in your case 'dpkg-reconfigure locales-all' should have done the job as it would have rebuild /usr/lib/locale/locale-archive. > > > message: > > > > > > Error: invalid locale settings: LANG=fr_FR.UTF-8 > > > > It means that this locale was not installed on the system. > > Well, the purpose of dpkg-reconfigure locales is to generate the local > so that it's “installed” on the system, isn't it? dpkg-reconfigure locales doesn't do anything except selecting the default locale when locales-all is installed, as the later package provides all locales. > > > Still, I'm wondering why this package was installed, as I don't seem to > > > need > > > it. I found that: > > > > > > Start-Date: 2011-04-25 12:33:45 > > > Commandline: apt-get dist-upgrade > > > Install: locales-all:amd64 (2.11.2-13, automatic), lzma:amd64 (4.43-14, > > > automatic) > > > Upgrade: ca-certificates-java:amd64 (20100412, 20110421~nmu1) > > > End-Date: 2011-04-25 12:34:03 > > > > > > So, maybe this is rather a bug from ca-certificates-java? I don't really > > > know. > > > > > > > Well I don't get it. As fard as I can see nor ca-certificates-java nor > > its dependencies depends on locales-all. > > Me neither. > > After a bit of research: #623672 led to version 20110421~nmu1 as a “fix” > which depends on locales-all. > On my machine, ca-certificates-java was upgraded to version 20110426 the > day after 20110421~nmu1 was installed. But locales-all resisted apt-get > autoremove, I suppose. I don't why. > > Anyway, this seems to be a transitional problem only, maybe you can > close it. > This will be fixed in the next upload, as the locales in locales-all are going to be provided unpacked instead as in an archive like now. This way filesystem corruption can be detected by usual methods like debsums. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
