Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 817072
Summary: | python-2.7.3-3.fc17 FTBFS on ARM | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Robinson <pbrobinson> |
Component: | python | Assignee: | Dave Malcolm <dmalcolm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | dmalcolm, herrold, ivazqueznet, jonathansteffan, lmacken, mail, tomspur |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-2.7.3-6.fc17 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-05 17:40:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 245418 |
Description
Peter Robinson
2012-04-27 15:13:03 UTC
For some reason test_gdb is failing every test case with: AssertionError: 'warning: File "/builddir/build/BUILD/Python-2.7.3/build/debug/python-debug-gdb.py" auto-loading has been declined by your `auto-load safe-path\' set to "/usr".' != '' Appears to relate to this patch set: http://sourceware.org/ml/gdb-patches/2012-03/msg00826.html from which the workaround appears to be to add: 'set auto-load safe-path' to the commands invoked in each selftest. For reference, this was with gdb.armv7hl 0:7.4.50.20120120-40.fc17 Candidate patch committed to git as: http://pkgs.fedoraproject.org/gitweb/?p=python.git;a=commit;h=9261681cd04196e1c4370b4888c9dfeff2b19f66 Building python-2.7.3-5.fc18 for dist-rawhide Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=4035890 Build failed with: AssertionError: '"on" or "off" expected.' != '' (In reply to comment #5) > Build failed with: > AssertionError: '"on" or "off" expected.' != '' This appears to be the error message for a gdb that doesn't understand "auto-load": e.g. with GNU gdb (GDB) Fedora (7.3-43.fc15): (gdb) set auto-load (gdb) set auto-load safe-path "on" or "off" expected. (gdb) set auto-load safe-path / "on" or "off" expected. Looks like F17's gdb has the patch, but rawhide doesn't. It turns out that the gdb in git is more recent than that in the Koji buildroots. The updated gdb that has this feature is built into f17-candidate and is available in updates-testing, but isn't yet in f17 or f18's buildroots for the primary architectures. So this is a case where the secondary architectures are ahead of the primary architectures. I've updated the patch to make it work with both old and new gdb builds (I hope): http://pkgs.fedoraproject.org/gitweb/?p=python.git;a=commit;h=1fa9c84f237d8822d26b9b229a4d68eed5b667c3 and am rebuilding into rawhide: Building python-2.7.3-6.fc18 for dist-rawhide Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=4036938 (In reply to comment #7) > and am rebuilding into rawhide: > Building python-2.7.3-6.fc18 for dist-rawhide > Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=4036938 This built successfully into rawhide, and am building into f17: Building python-2.7.3-6.fc17 for f17-candidate Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=4037025 and trying a scratch build for python3 (which presumably has the same issue). Does this commit fix the build on ARM? (see the notes in comment #7; I did test the patch both with and without the new gdb feature, but the proof of the pudding is in the eating). Just submitted it as a new build http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=781730 Confirmed that python-2.7.3-6.fc17 builds fine on ARM (In reply to comment #8) > This built successfully into rawhide, and am building into f17: > Building python-2.7.3-6.fc17 for f17-candidate > Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=4037025 This build successfully > and trying a scratch build for python3 (which presumably has the same issue). and this scratch build also succeeded, so I've committed and pushed for python3 in master and f17, and am building non-scratch builds: Building python3-3.2.3-5.fc18 for dist-rawhide Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=4040193 Building python3-3.2.3-5.fc17 for f17-candidate Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=4040195 > Does this commit fix the build on ARM? (see the notes in comment #7; I did test > the patch both with and without the new gdb feature, but the proof of the > pudding is in the eating). (In reply to comment #10) > Confirmed that python-2.7.3-6.fc17 builds fine on ARM Thanks! Closing this bug out, as I believe I don't need to do a Bodhi update for this, right?
> Closing this bug out, as I believe I don't need to do a Bodhi update for this,
> right?
We need bodhi updates for F-17. We need the same builds tagged appropriately in mainline as for all secondary arches.
(In reply to comment #11) > Building python3-3.2.3-5.fc18 for dist-rawhide > Building python3-3.2.3-5.fc17 for f17-candidate (both of these builds succeeded) python3-3.2.3-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2012-5785/python3-3.2.3-5.fc17 python-2.7.3-6.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/python-2.7.3-6.fc17 python-2.7.3-6.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. python3-3.2.3-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. This looks like it is all set... closing. |