Spec URL: https://fab.fedorapeople.org/packages/SRPMS/golang-github-chromedp.spec SRPM URL: https://fab.fedorapeople.org/packages/SRPMS/golang-github-chromedp-0.5.3-1.fc31.src.rpm Project URL: https://github.com/chromedp/chromedp Description: A faster, simpler way to drive browsers supporting the Chrome DevTools Protocol. Koji scratch build: fails due to missing dependencies rpmlint output: $ rpmlint golang-github-chromedp-0.5.3-1.fc31.src.rpm golang-github-chromedp.src: W: no-%build-section 1 packages and 0 specfiles checked; 0 errors, 1 warnings. $ rpmlint golang-github-chromedp-devel-0.5.3-1.fc31.noarch.rpm golang-github-chromedp-devel.noarch: W: hidden-file-or-dir /usr/share/gocode/src/github.com/chromedp/chromedp/.goipath 1 packages and 0 specfiles checked; 0 errors, 1 warnings. Fedora Account System Username: fab
Remove the extraneous %files spection - License ok - Latest version packaged - Builds in mock - Conforms to Packaging Guidelines Package approved.
(fedscm-admin): The Pagure repository was created at https://src.fedoraproject.org/rpms/golang-github-chromedp
PS, can you build for all releases?
This should have a runtime dependency on `chromium`, or you can't run tests in dependent packages without specifying it also. Or if you want to allow real chrome for people in RPMfusion, then a Recommends instead. %global godevelheader %{expand: Requires: chromium}
Also, you have %files for the (no-suffix) main package, but it's empty and doesn't have any additional Requires. I don't think it's necessary to produce that main package.
FEDORA-2020-71c410f165 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-71c410f165
FEDORA-2020-df3d194a14 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-df3d194a14
FEDORA-2020-b313edba5f has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b313edba5f
FEDORA-2020-b313edba5f has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2020-b313edba5f \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b313edba5f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-71c410f165 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2020-71c410f165 \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-71c410f165 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-df3d194a14 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2020-df3d194a14 \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-df3d194a14 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-df3d194a14 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-b313edba5f has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-71c410f165 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.