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 914155 - libvmime: FTBFS in rawhide
Summary: libvmime: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libvmime
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker F19FTBFS 926039
TreeView+ depends on / blocked
 
Reported: 2013-02-22 09:42 UTC by Dennis Gilmore
Modified: 2013-03-23 19:07 UTC (History)
4 users (show)

Fixed In Version: libvmime-0.9.2-0.6.20130320git.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-23 19:04:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dennis Gilmore 2013-02-22 09:42:00 UTC
Your package libvmime failed to build from source in current rawhide.

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

Build logs:
root.log: http://kojipkgs.fedoraproject.org/work/tasks/7159/4967159/root.log
build.log: http://kojipkgs.fedoraproject.org/work/tasks/7159/4967159/build.log
state.log: http://kojipkgs.fedoraproject.org/work/tasks/7159/4967159/state.log
NOTE: build logs are cleaned up after 1 week

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

Comment 1 Tomas Mraz 2013-03-22 17:05:30 UTC
Apparently a fresh checkout from the upstream git repository will be needed to make it work with new GnuTLS.

Comment 2 Robert Scheck 2013-03-22 17:07:14 UTC
Yes, I am working on this already. However upstream dropped scons in favor of cmake and they still have some cmake issues, because upstream is obviously neither perfectly knowledged in cmake nor in autotools :-( I am already in touch with them and try to push an update this weekend.


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