Package: emifreq-applet
Severity: important
Version: 0.18-2
User: [EMAIL PROTECTED]
Usertags: qa-doublebuild

Hi,                                                                             
                                                                                
                                                              
                                                                                
                                                                                
                                                              
Lucas Nussbaum has rebuilt the whole archive on i386 and your package FTBFS if
built twice in a row with the following error:


rm -f config.status
make[1]: Leaving directory `/build/user/emifreq-applet-0.18'
rm -f debian/stamp-makefile-build
rm -f debian/stamp-autotools-files
cd . && \
          rm -f intltool-extract intltool-merge intltool-update 
po/.intltool-merge-cache; \
          if test -d doc; then find doc -name '*.omf.out' -exec rm -f \{\} \; ; 
fi; \
          if test -d help; then find help -name '*.omf.out' -exec rm -f \{\} \; 
; fi
 dpkg-source -b emifreq-applet-0.18
dpkg-source: building emifreq-applet using existing 
emifreq-applet_0.18.orig.tar.gz
dpkg-source: building emifreq-applet in emifreq-applet_0.18-2.diff.gz
dpkg-source: cannot represent change to po/nl.gmo: binary file contents changed
dpkg-source: warning: ignoring deletion of file emifreq-applet.spec
dpkg-source: building emifreq-applet in emifreq-applet_0.18-2.dsc
dpkg-source: unrepresentable changes to source

The full build-log can be found at: 
http://people.debian.org/~lucas/logs/2007/05/15/00_Failed_2/


About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems. All
packages have been rebuilt twice in a row, with unpack, build, clean,
build.



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

Reply via email to