On Mon, Aug 28, 2006 at 04:44:27PM -0700, Wart wrote:
rpmlint complains about the 'sv' language code being invalid,
but I'm
not sure what should be used in its place. To further confuse matters,
it complains about this on a 'sw' (swahili) file:
E: tuxpaint-stamps incorrect-locale-sv
/usr/share/locale/sw/LC_MESSAGES/tuxpaint-stamps.mo
Something is broken here, but I don't think it is tuxpaint-stamps.
$ rpm -qf /usr/share/locale/sv
glibc-common-2.4-8
$ rpm -qf /usr/share/locale/sw
file /usr/share/locale/sw is not owned by any package
$ rpm -qf /usr/share/locale/sw/LC_MESSAGES/*
iso-codes-0.49-1
iso-codes-0.49-1
tuxpaint-0.9.15b-1.fc5
And iso-codes is a core package. (One I've never noticed before...)
I'm guessing glibc-common *should* own /usr/share/locale/sw, but I
have nothing to back that up. Unowned directories are not cool
though...
Looking into this a little deeper, it appears to be a common problem.
$ rpm -qf /usr/share/locale/* | grep 'is not owned' | wc -l
162
I wonder if %find_lang is buggy.
In any case, I think I'm going to submit the package as-is. If it is
broken, it is no more broken that tuxpaint itself...
Steve
--
Steven Pritchard - K&S Pritchard Enterprises, Inc.
Email: steve(a)kspei.com
http://www.kspei.com/
Phone: (618)398-3000 Mobile: (618)567-7320