Bug 1017499

Summary: bamf-0.5 is available
Product: [Fedora] Fedora Reporter: Christopher Meng <i>
Component: bamfAssignee: Michel Lind <michel>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: jspaleta, michel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-14 08:45:07 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: 896193    

Description Christopher Meng 2013-10-10 03:41:32 UTC
Hi,

Please update it to the latest 0.5 version for rawhide to help build plank.

Thanks!

Comment 1 Christopher Meng 2013-11-08 15:08:25 UTC
ping after a month.

Comment 2 Christopher Meng 2014-02-11 00:16:48 UTC
Help this one ;)

Comment 3 Michel Lind 2014-02-14 07:55:09 UTC
Hi Christopher,

Apologies for the delay. The update is now almost ready, after swatting a couple of compile-warning-treated-as-error.

I'm double-checking a build failure on Rawhide -- looks like GCC is getting even stricter there (the last statement in a function produces a value, and the function is void, but there was no return statement -- and yet when GCC produces an error it claims there was a return):

http://kojipkgs.fedoraproject.org//work/tasks/9450/6529450/build.log

so for the moment, please use the test package in COPR for testing. I'll try reproducing the Rawhide issue in mock, and if necessary just hack a void return to make GCC happy:

http://copr.fedoraproject.org/coprs/salimma/bamf05/

Comment 4 Michel Lind 2014-02-14 08:45:07 UTC
Aha, turns out it's fixed in a post-release commit (and I was looking at trunk since I was working on a compile warning fix there). Now built for Rawhide.

Do you need an update for F20 as well? It's quite a major update and there are no longer separate GTK2 and GTK3 support, so I guess I'll keep the COPR repo up for F20 testing in case we want to do that.

Comment 5 Christopher Meng 2014-02-14 08:49:06 UTC
I don't need it for f20. But you can build one and push in testing.

Plank doesn't depends on the latest version, but we can have a try(Be careful if you want to add buildroot override.)

Thank you!