Source: tinc
Version: 1.0.10-1
Severity: serious
User: [email protected]
Usertags: qa-ftbfs-20091028 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[3]: Entering directory 
> `/build/user-tinc_1.0.10-1-amd64-cpcXdf/tinc-1.0.10'
> make[3]: Nothing to be done for `install-exec-am'.
> make[3]: Nothing to be done for `install-data-am'.
> make[3]: Leaving directory 
> `/build/user-tinc_1.0.10-1-amd64-cpcXdf/tinc-1.0.10'
> make[2]: Leaving directory 
> `/build/user-tinc_1.0.10-1-amd64-cpcXdf/tinc-1.0.10'
> make[1]: Leaving directory 
> `/build/user-tinc_1.0.10-1-amd64-cpcXdf/tinc-1.0.10'
> dh_installdirs -ptinc 
> dh_installdocs -ptinc ./README ./NEWS ./AUTHORS ./THANKS  
> dh_installexamples -ptinc 
> dh_installman -ptinc  
> dh_installinfo -ptinc  
> dh_installmenu -ptinc 
> dh_installcron -ptinc 
> dh_installinit -ptinc  -n 
> dh_installdebconf -ptinc 
> dh_installemacsen -ptinc   
> dh_installcatalogs -ptinc 
> dh_installpam -ptinc 
> dh_installlogrotate -ptinc 
> dh_installlogcheck -ptinc 
> dh_installchangelogs -ptinc  ./ChangeLog 
> dh_installudev -ptinc 
> dh_lintian -ptinc 
> dh_install -ptinc  
> dh_link -ptinc  
> dh_installmime -ptinc 
> mv -v doc/tinc/*.html debian/tinc/usr/share/doc/tinc/
> mv: cannot stat `doc/tinc/*.html': No such file or directory
> make: *** [binary-post-install/tinc] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2009/10/28/tinc_1.0.10-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to