retty version 1.0-2 failed to build in oneiric

Bug #834989 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
retty (Debian)
Fix Released
Unknown
retty (Ubuntu)
Fix Released
High
Unassigned
Oneiric
Fix Released
High
Unassigned

Bug Description

retty version 1.0-2 failed to build in oneiric
Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2710460

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/2710460/+files/buildlog_ubuntu-oneiric-i386.retty_1.0-2_FAILEDTOBUILD.txt.gz

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

rm -f build-stamp
dh_clean
dh_clean: Compatibility levels before 5 are deprecated.
 debian/rules build
/usr/bin/make all
make[1]: Entering directory `/build/buildd/retty-1.0'
cc -Wall -g -c -o blindtty.o blindtty.c
cc -lutil blindtty.o -o blindtty
blindtty.o: In function `main':
/build/buildd/retty-1.0/blindtty.c:35: undefined reference to `forkpty'
collect2: ld returned 1 exit status
make[1]: *** [blindtty] Error 1
make[1]: Leaving directory `/build/buildd/retty-1.0'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110825-2032
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/retty-1.0

Tags: ftbfs oneiric
Matthias Klose (doko)
Changed in retty (Ubuntu):
status: New → Confirmed
importance: Undecided → High
tags: removed: arm-porting-queue
Revision history for this message
Matthias Klose (doko) wrote :

fixed in oneiric

Changed in retty (Ubuntu Oneiric):
status: Confirmed → Fix Released
Changed in retty (Debian):
status: Unknown → New
Changed in retty (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.