Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-context-0.0.1-1.fc21.src.rpm Description: Package gorilla/context stores values shared during a request lifetime. For example, a router can set variables extracted from the URL and later application handlers can access those values, or it can be used to store sessions values to be saved at the end of a request. There are several others common uses. Fedora Account System Username: lsm5 Koji build: http://koji.fedoraproject.org/koji/taskinfo?taskID=5857155 $ rpmlint SPECS/golang-context.spec 0 packages and 1 specfiles checked; 0 errors, 0 warnings. $ rpmlint SRPMS/golang-context-0.0.1-1.fc21.src.rpm 1 packages and 0 specfiles checked; 0 errors, 0 warnings. $ rpmlint RPMS/x86_64/golang-context-0.0.1-1.fc21.x86_64.rpm golang-context.x86_64: E: no-binary golang-context.x86_64: W: only-non-binary-in-usr-lib golang-context.x86_64: E: script-without-shebang /usr/lib64/golang/src/cmd/context/context.go golang-context.x86_64: E: script-without-shebang /usr/lib64/golang/src/cmd/context/doc.go golang-context.x86_64: E: script-without-shebang /usr/lib64/golang/src/cmd/context/context_test.go 1 packages and 0 specfiles checked; 4 errors, 1 warnings.
permissions fixed. Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-context-0.0.1-2.fc21.src.rpm
This section from your spec longs for explanations: %global _enable_debug_package 0 %global debug_package %{nil} %global __os_install_post /usr/lib/rpm/brp-compress %{nil}
A couple of points: * as a matter of naming convention, lets include as much of the import path into the package name as possible. Escpecially something like the gorilla project that has a number of libraries - golang-github-gorilla-context ? - golang-gorilla-context ? * Since the $GOROOT/src is not presently a symlink to a noarch place, then there is no point to _not_ include the precompiled *.a files * The path in $GOROOT/src that the source files is being landed does not line up with the import path expected. Also, source in GOROOT should be in $GOROOT/src/pkg, not ./src/cmd/. That directory is for 'go' command itself. - expected: "github.com/gorilla/context" - rpm: "context" * The global debug lines are not needed. There is some rpm magic that attempts to strip the *.a archives, but they are not gcc *.a, and do not strip as such. As for the __spec_install_post, I have not found it useful for binaries/libraries built by golang compiler. But are needed for building the compiler itself. * Include a meta Provide: for the import paths provided in this library. Require: golang("github.com/gorilla/context")
I changed the spec file name because rpmlint was giving me some invalid spec name error. Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-github-gorilla-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-github-gorilla-context-0.0.1-3.fc21.src.rpm Few things I'm unsure of (see inline replies) (In reply to Vincent Batts from comment #3) > A couple of points: > - golang-github-gorilla-context ? I've used this for the new package name. > * Since the $GOROOT/src is not presently a symlink to a noarch place, then > there is no point to _not_ include the precompiled *.a files I'm sorry I didn't see any *.a files in the package. Am I missing something? > * The path in $GOROOT/src that the source files is being landed does not > line up with the import path expected. Also, source in GOROOT should be in > $GOROOT/src/pkg, not ./src/cmd/. That directory is for 'go' command itself. > - expected: "github.com/gorilla/context" > - rpm: "context" Done (hopefully). Check it out. > * The global debug lines are not needed. There is some rpm magic that > attempts to strip the *.a archives, but they are not gcc *.a, and do not > strip as such. As for the __spec_install_post, I have not found it useful > for binaries/libraries built by golang compiler. But are needed for building > the compiler itself. Should be done. Again, unsure about the *.a archives > * Include a meta Provide: for the import paths provided in this library. > Require: golang("github.com/gorilla/context") Did you mean Provides instead of Require in the latter line (??). Let me know if I got it wrong. I have put a: Provides: golang("github.com/gorilla/context") = %{version}-%{release} $ rpmlint RPMS/x86_64/golang-github-gorilla-context-0.0.1-3.fc21.x86_64.rpm golang-github-gorilla-context.x86_64: E: no-binary golang-github-gorilla-context.x86_64: W: only-non-binary-in-usr-lib 1 packages and 0 specfiles checked; 1 errors, 1 warnings.
cool. So as for the allusion to *.a files that aren't present, it is because your spec did not precompile them and I was encouraging such. Here is an example of a library that is packaged http://pastebin.test.redhat.com/161221 One additional note. the %{version} ought to reflect the git commit hash. Likely in the form of git%{shortcommit} Since many libraries will not have tagged version or otherwise, best to include as much trace-ability as possible.
(In reply to Vincent Batts from comment #6) > cool. So as for the allusion to *.a files that aren't present, it is because > your spec did not precompile them and I was encouraging such. Here is an > example of a library that is packaged http://pastebin.test.redhat.com/161221 I'm getting "cannot find package github.com/gorilla/context". Could you please check what I'm doing wrong. The build fails at the go install %{import_path} stage. Here's the revised spec: http://pastebin.test.redhat.com/161267 And here's the build output: http://pastebin.test.redhat.com/161268 > > > One additional note. the %{version} ought to reflect the git commit hash. > Likely in the form of git%{shortcommit} > Since many libraries will not have tagged version or otherwise, best to > include as much trace-ability as possible. Taken care of in the new spec.
Looks like the revised spec pastebin I sent earlier isn't available anymore. Here's the same spec again: http://pastebin.test.redhat.com/161713
http://pastebin.test.redhat.com/pastebin.php?diff=161724 is a diff of the spec including the reason for that build failure, and a couple of additional fixes to get a built rpm.
Thanks Vincent! Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-github-gorilla-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-github-gorilla-context-git708054d-4.fc21.src.rpm $ rpmlint SPECS/golang-github-gorilla-context.spec 0 packages and 1 specfiles checked; 0 errors, 0 warnings. $ rpmlint SRPMS/golang-github-gorilla-context-git708054d-4.fc21.src.rpm 1 packages and 0 specfiles checked; 0 errors, 0 warnings. $ rpmlint RPMS/x86_64/golang-github-gorilla-context-git708054d-4.fc21.x86_64.rpm golang-github-gorilla-context.x86_64: W: binaryinfo-readelf-failed /usr/lib64/golang/pkg/linux_amd64/github.com/gorilla/context.a readelf: Error: Unable to read in 0xb7c2 bytes of section headers golang-github-gorilla-context.x86_64: W: devel-file-in-non-devel-package /usr/lib64/golang/pkg/linux_amd64/github.com/gorilla/context.a 1 packages and 0 specfiles checked; 0 errors, 2 warnings.
Vincent: Once I install the generated RPM, if I try to build it again, I get this error: http://pastebin.test.redhat.com/161774 If I uninstall the RPM and build it again, the build goes fine. Is this expected behavior?
I'm investigating a solution. While it is not uncommon for an rpm to need to be removed to get an accurate compile of that rpm, I feel this ought not be the case. The issue is because when the rpm _is_ installed, then the 'github.com/gorilla/context' is showing in the GOROOT and is up-to-date. So when the rpmbuild is setting a GOPATH and attempting to build that, nothing happens. After a review of the archlinux and debian packaging guidelines and helpers, it looks like they'll have the same issue. I'll take the action item to iron this out.
Lokesh, see http://pastebin.test.redhat.com/162710 This iteration of found directories should be sufficient for most libraries, but could report an error if it find a directory that is not compilable (testing data or such)
Vincent, thanks a lot, it worked! Also, I'm guessing, $plat in the spec you sent would be interchangeable with %{pkgarch} (I picked this one up from your goyaml specfile) rpmlint complained of .a archives not being in a devel package, so devel package generated as well. Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-github-gorilla-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-github-gorilla-context-git708054d-5.fc21.src.rpm $ rpmlint SPECS/golang-github-gorilla-context.spec 0 packages and 1 specfiles checked; 0 errors, 0 warnings. $ rpmlint SRPMS/golang-github-gorilla-context-git708054d-5.fc21.src.rpm 1 packages and 0 specfiles checked; 0 errors, 0 warnings. $ rpmlint RPMS/x86_64/golang-github-gorilla-context-git708054d-5.fc21.x86_64.rpm golang-github-gorilla-context.x86_64: W: only-non-binary-in-usr-lib 1 packages and 0 specfiles checked; 0 errors, 1 warnings. $ rpmlint RPMS/x86_64/golang-github-gorilla-context-devel-git708054d-5.fc21.x86_64.rpm golang-github-gorilla-context-devel.x86_64: W: summary-not-capitalized C github-gorilla-context pkg archive files golang-github-gorilla-context-devel.x86_64: W: binaryinfo-readelf-failed /usr/lib64/golang/pkg/linux_amd64/github.com/gorilla/context.a readelf: Error: Unable to read in 0xb7c2 bytes of section headers golang-github-gorilla-context-devel.x86_64: W: no-documentation 1 packages and 0 specfiles checked; 0 errors, 3 warnings.
devel package summary warning removed. Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-github-gorilla-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-github-gorilla-context-git708054d-6.fc21.src.rpm
rpmbuild should now work regardless of package installation status Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-github-gorilla-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-github-gorilla-context-git708054d-7.fc21.src.rpm Koji Build: http://koji.fedoraproject.org/koji/taskinfo?taskID=5916441 Vincent: it looked like your Comment 9 spec file worked when RPM wasn't installed prior and not otherwise, while the Comment 13 spec file worked for the reverse case. So, I combined them like so: unset GOROOT GOPATH GOOS GOARCH if [ ! -d %{goroot}/src/pkg/%{import_path} ]; then GOPATH=$(readlink -f ./tmp-gopath/) go install %{import_path} else GOPATH=$(readlink -f ./tmp-gopath/) pushd $GOPATH/src for dir in $(find %{import_path} -type d) ; do mkdir -p $GOPATH/pkg/%{pkgarch}/$(dirname $dir) go build -o $GOPATH/pkg/%{pkgarch}/${dir}.a %{import_path} done popd fi Hope it's valid. Let me know. Matt: $ rpmlint RPMS/x86_64/golang-github-gorilla-context-git708054d-7.fc21.x86_64.rpm golang-github-gorilla-context.x86_64: W: only-non-binary-in-usr-lib 1 packages and 0 specfiles checked; 0 errors, 1 warnings. $ rpmlint RPMS/x86_64/golang-github-gorilla-context-devel-git708054d-7.fc21.x86_64.rpm golang-github-gorilla-context-devel.x86_64: W: binaryinfo-readelf-failed /usr/lib64/golang/pkg/linux_amd64/github.com/gorilla/context.a readelf: Error: Unable to read in 0xb7c2 bytes of section headers golang-github-gorilla-context-devel.x86_64: W: no-documentation 1 packages and 0 specfiles checked; 0 errors, 2 warnings.
More changes in %prep as per Matt. Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-github-gorilla-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-github-gorilla-context-git708054d-8.fc21.src.rpm
I think there's a few more issues there -- I'll try to get them all in one pass to eliminate more back-and-forth work for you. (Tomorrow, though. Long enough day already. :)
Directory ownership corrected: Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-github-gorilla-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-github-gorilla-context-git708054d-10.fc21.src.rpm
only devel package generated Provides: golang("%{import_path}") = %{version}-%{release} has been moved to devel package Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-github-gorilla-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-github-gorilla-context-git708054d-11.fc21.src.rpm
this looks good for now, based on the current state of golang-packaging-guidelines for fedora/RHEL. We'll continue firming those guidelines up. But for now, this 'git708054d-11' iteration looks good. Since the resulting RPM will provide 'golang("github.com/gorilla/context")', then any other libraries/binaries needing to build with this need only to Require: golang("github.com/gorilla/context")
1. Excitingly, each individual component of the directory needs to be owned by the package -- %{goroot}/src/pkg/%{import_path} covers github.com/gorilla/context, but we also need %{goroot}/src/pkg/github.com and %{goroot}/src/pkg/github.com/gorilla, then %{goroot}/pkg/%{pkgarch}/github.com. --- 2. The snapshot version should go in the Version, not the Release, shouldn't it? (Since upstream does not seem to actually have any version numbers, use 0.). Otherwise, if they ever _do_ have a 1.0 release, we'll have trouble with a package with a version of "git....". (Is this confusing for packagers? Yes. It's overloading the Release field with two different purposes.) --- 3. I'm getting an empty debuginfo package. We should either generate no debuginfo or generate a meaningful one. (I'm not sure offhand what the options are there for Go.)
(In reply to Matthew Miller from comment #22) > 1. > > Excitingly, each individual component of the directory needs to be owned by > the package -- > > %{goroot}/src/pkg/%{import_path} covers github.com/gorilla/context, but we > also need > %{goroot}/src/pkg/github.com and %{goroot}/src/pkg/github.com/gorilla, then > %{goroot}/pkg/%{pkgarch}/github.com. so in the case of github.com/{gorilla/{context,mux},kr/pty}} .. do all 3 own github.com? ..and both mux and context own gorilla? .. I have updated my spec to reflect this. > > --- > > 2. > > The snapshot version should go in the Version, not the Release, shouldn't > it? (Since upstream does not seem to actually have any version numbers, use > 0.). Otherwise, if they ever _do_ have a 1.0 release, we'll have trouble > with a package with a version of "git....". (Is this confusing for > packagers? Yes. It's overloading the Release field with two different > purposes.) I'm not sure I understand you fully here, when you say snapshot version, do you mean the shortcommit, or something else? The shortcommit does go into the Version from what I can see. My personal opinion: Even if upstream comes with version numbers, it could be better to just stick with shortcommits, since version numbers may not change across commits, having the commit number would help us pinpoint the exact version? Maybe I haven't considered everything when I'm saying this. I haven't made this change in the spec yet though, also, could you take a look at the earlier versions I had in the spec file changelog, and let me know if you'd prefer it that way > > --- > > 3. > > I'm getting an empty debuginfo package. We should either generate no > debuginfo or generate a meaningful one. (I'm not sure offhand what the > options are there for Go.) I put %global debug_package %{nil} right on top Some additional fixes from release 11 including: devel package BuildRequires golang. Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-github-gorilla-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-github-gorilla-context-git708054d-12.fc21.src.rpm
(In reply to Lokesh Mandvekar from comment #23)ub.com. > so in the case of github.com/{gorilla/{context,mux},kr/pty}} .. do all 3 own > github.com? ..and both mux and context own gorilla? .. I have updated my > spec to reflect this. Yeah, all of them would own the directory, unless there is some reason to have a common github (or common gorilla) package which would own them and then be a Requires. > I'm not sure I understand you fully here, when you say snapshot version, do > you mean the shortcommit, or something else? The shortcommit does go into > the Version from what I can see. Yes, shortcommit. See http://fedoraproject.org/wiki/Packaging:SourceURL#Github If the release corresponds to a github Tag with a sane numeric version, you must use that version to populate the Version field in the spec file. If it does not, look at the source code to see if a version is indicated there, and use that value. If no numeric version is indicated in the code, you may set Version to 0, and treat the package as a "pre-release" package (and make use of the %{shortcommit} macro). See Packaging:NamingGuidelines#Pre-Release_packages for details. > My personal opinion: Even if upstream comes with version numbers, it could > be better to just stick with shortcommits, since version numbers may not > change across commits, having the commit number would help us pinpoint the > exact version? Maybe I haven't considered everything when I'm saying this. That's why the shortcommit does go in the release string. I see your point, but I'm just following the guidelines here. > > I'm getting an empty debuginfo package. We should either generate no > > debuginfo or generate a meaningful one. (I'm not sure offhand what the > > options are there for Go.) > I put %global debug_package %{nil} right on top I think it's *probably* possible to get them working. Vincent, do you have any opinion? (This approach is better than generating empty debuginfo, though).
version and release tags updated: Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-github-gorilla-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-github-gorilla-context-0-0.13.git708054d.fc21.src.rpm
Oop, sorry, got another one I didn't catch before. For the docs, get rid of %docdir %{_docdir}/%{name}-%{version} %doc %{_docdir}/%{name}-%{version}/LICENSE %doc %{_docdir}/%{name}-%{version}/README.md and instead just do %doc LICENSE README.md which takes care of putting it into the right place. I *think* everything else is good to go.
Spec URL: http://lsm5.fedorapeople.org/rpmbuild/SPECS/golang-github-gorilla-context.spec SRPM URL: http://lsm5.fedorapeople.org/rpmbuild/SRPMS/golang-github-gorilla-context-0-0.14.git708054d.fc21.src.rpm
I have to say, the git%{hash} needs to be in %{version}, not %{release}. This leaves the version as 0, so the docdir like /usr/share/doc/golang-github-gorilla-context-devel-0. Not awful, but not clear either. And rather than making up an arbitrary version number (0), use the %Y%M%d of when the snapshot was taken. This allows for sorting ascending. (20130626.git708054d.14.el6 or similar)
(In reply to Vincent Batts from comment #28) > I have to say, the git%{hash} needs to be in %{version}, not %{release}. This makes some sense, but putting it in version is actually the official packaging guideline -- http://fedoraproject.org/wiki/Packaging:SourceURL#Github. (Also, for the docdir in specific, see http://fedoraproject.org/wiki/Changes/UnversionedDocdirs)
Review passed with the following caveat. - This package matches in-development ideas for a Go Language packaging standard and may need to be revised as those are finalized. Of particular note: - this library is packaged as static, and therefore just produces a -devel package (and as with Haskell packages, does not have a virtual provides for a -static package). - no debuginfo package is generated (because of the above) - we don't have standard compile flags for Go
No SCM request found.
Ohh yes...sorry New Package SCM Request ======================= Package Name: golang-github-gorilla-context Short Description: A golang registry for global request variables Owners: lsm5 Branches: f19 f20 el6 InitialCC:
Git done (by process-git-requests).
golang-github-gorilla-context-0-0.14.git708054d.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.14.git708054d.fc20
golang-github-gorilla-context-0-0.14.git708054d.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.14.git708054d.fc19
golang-github-gorilla-context-0-0.14.git708054d.fc19 has been pushed to the Fedora 19 testing repository.
golang-github-gorilla-mux-0-0.5.gite718e93.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-github-gorilla-mux-0-0.5.gite718e93.fc19
golang-github-gorilla-context-0-0.15.git708054d.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.15.git708054d.fc20
golang-github-gorilla-context-0-0.15.git708054d.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.15.git708054d.fc19
golang-github-gorilla-mux-0-0.6.gite718e93.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-github-gorilla-mux-0-0.6.gite718e93.fc19
golang-github-gorilla-context-0-0.15.git708054d.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.15.git708054d.el6
golang-github-gorilla-context-0-0.17.git708054d.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.17.git708054d.fc20
golang-github-gorilla-context-0-0.17.git708054d.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.17.git708054d.fc19
golang-github-gorilla-context-0-0.17.git708054d.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.17.git708054d.el6
golang-github-gorilla-mux-0-0.7.gite718e93.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-github-gorilla-mux-0-0.7.gite718e93.fc19
golang-github-gorilla-context-0-0.18.git708054d.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.18.git708054d.fc20
golang-github-gorilla-context-0-0.18.git708054d.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.18.git708054d.fc19
golang-github-gorilla-context-0-0.18.git708054d.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.18.git708054d.el6
golang-github-gorilla-context-0-0.19.git708054d.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.19.git708054d.fc20
golang-github-gorilla-context-0-0.19.git708054d.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.19.git708054d.fc19
golang-github-gorilla-context-0-0.19.git708054d.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/golang-github-gorilla-context-0-0.19.git708054d.el6
Package golang-github-gorilla-context-0-0.19.git708054d.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing golang-github-gorilla-context-0-0.19.git708054d.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11872/golang-github-gorilla-context-0-0.19.git708054d.el6 then log in and leave karma (feedback).
golang-github-gorilla-mux-0-0.9.gite718e93.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-github-gorilla-mux-0-0.9.gite718e93.fc19
Package Change Request ====================== Package Name: golang-github-gorilla-context InitialCC: golang-sig
Done.
golang-github-gorilla-context-0-0.19.git708054d.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
golang-github-gorilla-mux-0-0.9.gite718e93.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
golang-github-gorilla-context-0-0.19.git708054d.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
golang-github-gorilla-context-0-0.19.git708054d.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.