Bug 1225487 - python-cassandra-driver FTBFS on BE arches
Summary: python-cassandra-driver FTBFS on BE arches
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-cassandra-driver
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: ZedoraTracker PPCTracker
TreeView+ depends on / blocked
 
Reported: 2015-05-27 13:25 UTC by Jakub Čajka
Modified: 2015-05-27 19:40 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2015-05-27 19:40:02 UTC


Attachments (Terms of Use)
proposed fix (1016 bytes, patch)
2015-05-27 13:25 UTC, Jakub Čajka
no flags Details | Diff

Description Jakub Čajka 2015-05-27 13:25:09 UTC
Created attachment 1030563 [details]
proposed fix

python-cassandra-driver fails to build on 64-bit BE arches due to chmod-ing not existing files. And on 32-bit BE arch(s390) build fails due mv having SOURCE == DESTINATION, as 32-bit systems have %{python2_sitelib} == %{python2_sitearch} (according to actual result and https://fedoraproject.org/wiki/Packaging:Python)

Failed builds:

http://s390.koji.fedoraproject.org/koji/buildinfo?buildID=287989
http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=2510375 (scratch build, as regular shadow build seems failed due to broken perl deps
http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=2485340 )

In attachment is patch witch should resolve both issues. Package seems to build fine with patch on all arches:
http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=3009725
http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=2510330
http://koji.fedoraproject.org/koji/taskinfo?taskID=9855402
http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1806666

Comment 1 Lubomir Rintel 2015-05-27 19:40:02 UTC
Applied to master -- thank you!

Feel free to merge into other branches if you wish. If you don't have permissions, please just reopen the bug.


Note You need to log in before you can comment on or make changes to this bug.