[Bug 831110] [NEW] giftrans version 1.12.2-16ubuntu1 failed to build in oneiric

Launchpad Bug Tracker 831110 at bugs.launchpad.net
Thu Sep 15 15:17:25 UTC 2011


You have been subscribed to a public bug by Mahyuddin Susanto (udienz):

giftrans version 1.12.2-16ubuntu1 failed to build in oneiric
Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2694020

Details about the rebuild:
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110816-oneiric.html

Direct link to the build log: https://launchpad.net/ubuntu/+archive
/test-rebuild-20110816/+build/2694020/+files/buildlog_ubuntu-oneiric-
amd64.giftrans_1.12.2-16ubuntu1_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 228 lines into the build log:

dh build
   dh_testdir
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory `/build/buildd/giftrans-1.12.2'
cc -g -Wall -Werror -pedantic-errors -Wfatal-errors -Wwrite-strings -fno-merge-constants -fstrict-aliasing -O2 -ogiftrans giftrans.c
giftrans.c: In function 'writedata':
giftrans.c:273:9: error: variable 'nbytes' set but not used [-Werror=unused-but-set-variable]
compilation terminated due to -Wfatal-errors.
cc1: all warnings being treated as errors

make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory `/build/buildd/giftrans-1.12.2'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110820-2024
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/giftrans-1.12.2

** Affects: giftrans (Ubuntu)
     Importance: High
         Status: Confirmed

** Affects: giftrans (Ubuntu Oneiric)
     Importance: High
         Status: Confirmed


** Tags: ftbfs oneiric
-- 
giftrans version 1.12.2-16ubuntu1 failed to build in oneiric
https://bugs.launchpad.net/bugs/831110
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.




More information about the Ubuntu-sponsors mailing list