Re: Release-critical Bugreport for June 9, 2000
At Fri, 9 Jun 2000 05:15:05 -0500,
BugScan reporter <bugscan@debian.org> wrote:
> Package: nvi-m17n (debian/main)
> Maintainer: Susumu OSAWA <susumu-o@debian.or.jp>
> [REMOVE] at next test cycle if no fix is available. (RB)
> 65329 nvi-m17n_2:1.79+19991117-2.1(frozen): build error
In #65329
> > (cd /usr/local/home/buildd/build/nvi-m17n-1.79+19991117/debian/tmp/usr/share/d
> > mv: CHANGELOG: No such file or directory
> > make: *** [install-stamp] Error 1
>
> AFAICS in the build log, the files in the docs.m17n/ dir are never
> installed during "make install", so debian/tmp/usr/share/doc/nvi-m17n/docs.m17n
> is simply empty at the time of the error... Maybe upstream Makefiles
> have changed in this respect and and you have to install those files
> manually from debian/rules.
CHANGELOG file is installed in debian/rules install:
| cp -a docs.m17n/ /usr/local/home/buildd/build/nvi-m17n-1.79+19991117/debian/tmp/usr/share/doc/nvi-m17n/
It looks like there are something different in `cp -a <dir> <dir>'
behavior between m68k and other archs. Anyway, I changed it and NMU
as nvi-m17n 1.79+19991117-2.2 (i386), which is already in incoming.
I suppose it fixes this RC bug, please check it.
> Another problem I've discovered:
>
> > (cd ./build && CC=gcc ADDCPPFLAGS="-O2 -g" ADDLDFLAGS="-lncurses" ./configure
> > loading cache ./config.cache
>
> This means that the source package comes with a build/config.cache.
> This is not good, because autoconf will use the values from that
> cache, but they're only valid for the system where the cache has been
> built (most likely yours). If the package is recompiled on another
> architecture, all configuration setting should be re-checked.
Yep, I fixed it too.
Thanks,
Fumitoshi UKAI
Reply to: