guppy version 0.1.9-2ubuntu1 failed to build on amd64 with GCC-4.6/oneiric

Bug #770882 reported by Matthias Klose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
guppy (Ubuntu)
Fix Released
High
Barry Warsaw
Oneiric
Fix Released
High
Barry Warsaw

Bug Description

guppy version 0.1.9-2ubuntu1 failed to build on amd64 with GCC-4.6/oneiric
Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110413/+buildjob/2452423

Details about the rebuild:
https://lists.ubuntu.com/archives/ubuntu-devel/2011-April/033042.html

Direct link to the build log: https://launchpad.net/ubuntu/+archive/test-rebuild-20110413/+buildjob/2452423/+files/buildlog_ubuntu-natty-amd64.guppy_0.1.9-2ubuntu1_FAILEDTOBUILD.txt.gz

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

  File "guppy/heapy/Use.py", line 359, in test
    self._parent.test.test_all.test_main(debug)
  File "guppy/heapy/test/test_all.py", line 33, in test_main
    f(debug=debug)
  File "guppy/heapy/test/test_dependencies.py", line 9, in test_main
    test.test_main()
  File "guppy/sets/test.py", line 1785, in test_main
    test_nums(range(36))
  File "guppy/sets/test.py", line 1761, in test_nums
    f()
  File "guppy/sets/test.py", line 389, in test1
    """
AssertionError
make: *** [install/python-guppy-lib] Error 1
dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary-arch gave error exit status 2
******************************************************************************
Build finished at 20110423-0836
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/guppy-0.1.9

Related branches

Matthias Klose (doko)
Changed in guppy (Ubuntu):
importance: Undecided → High
Changed in guppy (Ubuntu):
milestone: none → oneiric-alpha-3
Changed in guppy (Ubuntu Oneiric):
milestone: oneiric-alpha-3 → none
status: New → Confirmed
tags: added: universe
Revision history for this message
Dave Walker (davewalker) wrote :

This builds fine for me, can it be given back to the test build PPA please?

Changed in guppy (Ubuntu Oneiric):
status: Confirmed → In Progress
Revision history for this message
Matthias Klose (doko) wrote :

still fails

Changed in guppy (Ubuntu Oneiric):
status: In Progress → Confirmed
Barry Warsaw (barry)
Changed in guppy (Ubuntu Oneiric):
status: Confirmed → In Progress
assignee: nobody → Barry Warsaw (barry)
milestone: none → ubuntu-11.10-beta-2
Revision history for this message
Barry Warsaw (barry) wrote :

Upstream bug report: https://sourceforge.net/tracker/?func=detail&aid=3408228&group_id=105577&atid=641821

But actually, this is a problem with Python 2.7 and amd64. The package builds just fine for me on i386 with both versions of Python, but under amd64, Python 2.7 gives several failures. I can disable the specific tests when running on amd64 with Python 2.7, but this probably points out deeper problems in upstream. Unfortunately, it doesn't look like much has happened in upstream lately.

Or should we just not build the package for Python 2.7 on amd64?

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package guppy - 0.1.9-2ubuntu2

---------------
guppy (0.1.9-2ubuntu2) oneiric; urgency=low

  * Disable tests which are incompatible with Python 2.7 on amd64.
    (LP: #770882)
 -- Barry Warsaw <email address hidden> Mon, 12 Sep 2011 18:14:03 -0400

Changed in guppy (Ubuntu Oneiric):
status: In Progress → 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.