LC_ADDRESS: terminology language code `eo' not defined

Bug #289879 reported by Joey Stanford
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
language-pack-eo-base (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: language-pack-eo-base

When installing language-pack-eo-base on Intrepid, you are presented with this error:

Setting up language-pack-eo-base (1:8.10+20081025) ...
Generating locales...
  eo_US.UTF-8... LC_ADDRESS: terminology language code `eo' not defined
failed

===========

joey@c14n:~$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

joey@c14n:~$ apt-cache policy language-pack-eo-base
language-pack-eo-base:
  Installed: 1:8.10+20081025
  Candidate: 1:8.10+20081025
  Version table:
 *** 1:8.10+20081025 0
        500 http://us.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Narcis Garcia (narcisgarcia) wrote :

This error also affected to me in a Ubuntu 8.04.2 Server (Hardy Heron):

Sélection du paquet language-pack-eo-base précédemment désélectionné.
(Lecture de la base de données... 19792 fichiers et répertoires déjà installés.)
Dépaquetage de language-pack-eo-base (à partir de .../language-pack-eo-base_1%3a8.04+20090105_all.deb) ...
Sélection du paquet language-pack-eo précédemment désélectionné.
Dépaquetage de language-pack-eo (à partir de .../language-pack-eo_1%3a8.04+20090105.1_all.deb) ...
Paramétrage de language-pack-eo (1:8.04+20090105.1) ...
Paramétrage de language-pack-eo-base (1:8.04+20090105) ...
Generating locales...
  eo_US.UTF-8... LC_ADDRESS: terminology language code `eo' not defined
failed
  eo.UTF-8... done
Generation complete.

Revision history for this message
Jacob Nordfalk (jacob-nordfalk) wrote :

Just upgraded from 9.10 to 10.04. I got the same error:

Sætter language-pack-eo-base (1:10.04+20100422) op...
Generating locales...
  eo_US.UTF-8... LC_ADDRESS: terminology language code `eo' not defined
failed
  eo.UTF-8... done
Generation complete.

Revision history for this message
David Raymond Christiansen (david-davidchristiansen) wrote :

I just saw this error in 12.04. It can be repeated by running sudo locale-gen, which gives the following output:

Generating locales...
  da_DK.UTF-8... done
  en_AG.UTF-8... done
  en_AU.UTF-8... done
  en_BW.UTF-8... done
  en_CA.UTF-8... done
  en_DK.UTF-8... done
  en_GB.UTF-8... done
  en_HK.UTF-8... done
  en_IE.UTF-8... done
  en_IN.UTF-8... done
  en_NG.UTF-8... done
  en_NZ.UTF-8... done
  en_PH.UTF-8... done
  en_SG.UTF-8... done
  en_US.UTF-8... done
  en_ZA.UTF-8... done
  en_ZM.UTF-8... done
  en_ZW.UTF-8... done
  eo_US.UTF-8... LC_ADDRESS: terminology language code `eo' not defined
failed
  eo.UTF-8... done
  sv_FI.UTF-8... up-to-date
  sv_SE.UTF-8... up-to-date
Generation complete.

$ lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04

$ apt-cache policy language-pack-eo-base
language-pack-eo-base:
  Instalita: 1:12.04+20120417
  Kandidata: 1:12.04+20120417
  Version table:
 *** 1:12.04+20120417 0
        500 http://dk.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in language-pack-eo-base (Ubuntu):
status: New → Confirmed
Revision history for this message
Tom K. C. Chiu (tomchiukc) wrote :

Is it related to something glibc or other system files bug?

Revision history for this message
Tom K. C. Chiu (tomchiukc) wrote :

This bug is still present in 14.10. The failed locale is eo_US.UTF-8 and eo.UTF-8, with the same error. I just add this new language via the GUI.

Revision history for this message
Tom K. C. Chiu (tomchiukc) wrote :

tom@bkgovsrv1:/usr/share/locales$ sudo /usr/sbin/locale-gen --lang eo
Generating locales...
  eo_US.UTF-8... LC_ADDRESS: terminology language code `eo' not defined
failed
  eo.UTF-8... done
Generation complete.
tom@bkgovsrv1:/usr/share/locales$

Revision history for this message
Joey Stanford (joey) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.