1.36 again

[Theodore Ts'o]

On Mon, Feb 28, 2005 at 12:39:35PM -0500, Bill Rugolsky Jr. wrote:
> On Sat, Feb 26, 2005 at 11:38:12AM -0500, Theodore Ts'o wrote:
> > E2fsprogs.spec *is* supposed to be a distro-neutral spec file, but I
> > don't regularly use an rpm-based distribution these days, so I am
> > depending on others to report bugs and suggest patches.  It would be
> > helpful though if people actually *tried* to use it as opposed making
> > incorrect assertions on the mailing list.  :-)
> 
> Sorry Ted, ENOCAFFEINE.  It turns out that rpmbuild -ta is incompatible
> with my ~/.rpmmacro file (which include %{name} in the paths).  Using
> the standard layout, the  %find_lang fails on FC3.  As penance, I'll
> figure out what's wrong and offer up a patch. :-)

I think I know what's going on here.  My fault; when I moved the .gmo
files to the source tree, instead of making them be pure generated
file (the GNU i18n tools and makefiles having rather loose definitions
of backwards compatibility, and this was recommended by the GNU i18n
maintainer as the best way to be compatible with systems using older
versions of the tools), I forgot to fix the gen-tarball script so it
wouldn't remove the .gmo files from the source tarball.

As a result, the reason why %find_lang doesn't work is that the .gmo
files aren't present, and the po Makefile doesn't generate normally
anymore (since that would break on, for example, on old Slackware
systems that don't have the most recent version of the GNU i18n
tools).  I didn't notice this problem since I normally build out of my
BK tree, and while I do a test build of the generated final tarball, I
didn't test "make install".

The fix is to either backout the change which supresses the generation
of the .gmo files (which should work for FC3, since it should have a
recent enough version of the i18n so that it's compatible with the
po/Makefile.in.in shipped with e2fsprogs), or to spin a new release of
e2fsprogs that actually has the .gmo files.  I suspect I'll probably
put out an e2fsprogs 1.37 fairly rapidly to avoid this problem on
other distributions.

						- Ted