[Gnewsense-dev] Builder failed to build apt

[Dmitry Samoyloff]

Hello!

I'm trying to build gNewSense-2.3 using the Builder and I noticed a problem in
apt building. This may indicate some hidden issue in my environment, so I
decided to describe it here.

This is errors I've got (note, that I've changed default MIRRORLOCAL and
BASEDIR in config.local from "/srv/..." to "/mnt/providence/deltah-works/..."
and the latter is NFS storage):

$ sudo ./do-update

<...>

make[1]: Entering directory 
`/mnt/providence/deltah-works/gnewsense/tmp/apt-0.7.9ubuntu17gnewsense1'
make[2]: Entering directory 
`/mnt/providence/deltah-works/gnewsense/tmp/apt-0.7.9ubuntu17gnewsense1/doc'
Creating html for dpkg-tech.sgml to ../build/docs/dpkg-tech.html
nsgmls:E: cannot open "/dpkg-tech.sgml" (No such file or directory)
nsgmls:/usr/share/sgml/debiandoc/dtd/sgml/1.0/debiandoc.dcl:67:40:E: end of 
document in prolog
make[2]: *** [../build/docs/dpkg-tech.html] Error 1
make[2]: Leaving directory 
`/mnt/providence/deltah-works/gnewsense/tmp/apt-0.7.9ubuntu17gnewsense1/doc'
make[1]: *** [doc] Error 2
make[1]: Leaving directory 
`/mnt/providence/deltah-works/gnewsense/tmp/apt-0.7.9ubuntu17gnewsense1'
make: *** [build/build-doc-stamp] Error 2
dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit status 
2
+ exit 1

Obviously, the problem is indicated by 'cannot open "/dpkg-tech.sgml"'
message. The leading slash shouldn't be there I suppose. Is this error known?

I've tried to call dpkg-buildpackage manually in the chrooted environment, but
got the same error:

# chroot /mnt/providence/deltah-works/gnewsense/tmp/hardy-i386/
# cd /mnt/providence/deltah-works/gnewsense/tmp/apt-0.7.9ubuntu17gnewsense1/
# export MAINTINFO='gNewSense hackers <address@hidden>'
# dpkg-buildpackage -rfakeroot '-e"$MAINTINFO"' '-m"$MAINTINFO"' -us -uc -ai386 

My brutal fix to move on is like this (in chroot):

# ln -s 
/mnt/providence/deltah-works/gnewsense/tmp/apt-0.7.9ubuntu17gnewsense1/doc/dpkg-tech.sgml
 /

It helped, but it is in no way a proper fix... :-) Does someone have any
thoughts?

-- 
I'm an FSF member -- Help us support software freedom!
<http://www.fsf.org/jf?referrer=7253>