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 993189 - qgis: FTBFS in rawhide
Summary: qgis: FTBFS in rawhide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: qgis
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Volker Fröhlich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F20FTBFS
TreeView+ depends on / blocked
 
Reported: 2013-08-05 16:53 UTC by Dennis Gilmore
Modified: 2013-09-30 20:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-27 09:38:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dennis Gilmore 2013-08-05 16:53:12 UTC
Your package qgis failed to build from source in current rawhide.

http://koji.fedoraproject.org/koji/taskinfo?taskID=5764544

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild

Comment 1 Volker Fröhlich 2013-09-14 12:15:56 UTC
OK, still broken, now that Grass is OK again. QGIS 2.0 is just around the corner. I'll submit that.

Comment 2 Fedora End Of Life 2013-09-16 15:54:27 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 3 Volker Fröhlich 2013-09-27 09:38:17 UTC
I just built QGIS 2.0 for F20, hence closing this bug. There's an error associated with un-bundling python-httplib2 though, that I'll fix as soon as possible.

Comment 4 Volker Fröhlich 2013-09-30 20:14:25 UTC
The aforementioned issue is sorted out in release #2.


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