Hello,

I uploaded new version of ispell-uk package and got this:
http://buildd.debian.org/fetch.cgi?p...amp=1222276435

....
localedef -i uk_UA -f KOI8-U /build/buildd/ispell-uk-1.5.5/debian/locale/uk_UA
character map file `KOI8-U' not found: No such file or directory
cannot read character map directory `/usr/share/i18n/charmaps': No suchfile or directory
make: *** [locale-stamp] Error 1

This is because this buildd had 'locales-all' package installed that provides 'locales' but
does not contain files required to build ispell-uk. Here maybe I can fix this by checking
if system has uk_UA.{UTF-8,KOI8-U} and do not generate them, locales-all contains those
both locales.

But there are other package that build-depend on the 'locales' package (unversioned):
bash
choose-mirror
console-data
dbus-java
gcc-3.3
gcc-3.4
gcc-4.1
gcc-4.2
gcc-4.3
gcc-snapshot
gcj-4.2
gcj-4.3
gdc-4.1
gdc-4.2
gnat-4.1
gnat-4.3
gpc-4.1
ipolish
ispell-uk
m17n-db
manpages-tr
maxima
pennmush
python2.4
python2.5
sbcl
sympa
webcit
These packages have locales in Build-Depends-Indep:
cvs2svn
ispell-lt
localechooser
modconf

Some of those packages try to build locales, others try to grep SUPPORTED file that
is not available in locales-all package.

There are also some binary packages that depend/suggest locales package, i did not
check what for.

The question is: what to do with this?

I see two possibilities:
1. File RC bugs against packages that build-depend on 'locales' and FTBFS with locales-all.
Then those packages can build-conflict with locales all or check if needed locales
already exist. This may require patching of upstream code and may cause troubles when
list of supported locales in locales-all package change.
Also one may need to check binary packages that depend on locales package.
And one will need to edit Developers Reference section 6.7.6:
http://www.us.debian.org/doc/develop...tml#bpp-locale

2. File RC bug against locales-all package requesting removing of "Provides" field. Other
packages can (Build-)Depend on locales | locales-all if it is enough forthem.

Any ideas?

Regards,
Eugeniy Meshcheryakov

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkjajOsACgkQKaC6+zmozOK6HwCgkfnrMUGmCh VKaJyopY16veCR
ARsAni79vzEWPz4hh/bMUDgYa4vT6Clx
=HdgM
-----END PGP SIGNATURE-----