Description of problem: Whilst fedpkg builds stuff and writes the output rpms in the project directory in which you're running it, it does not assemble the rpm there, but rather assembles it in ~/rpmbuild/BUILDROOT. It should be consistent and assemble the RPMs there too, because: (1) The homedir may be remotely based. (2) The homedir may be subject to quotas or size limits that can get overrun. (3) The homedir may not support all types of file. The problem I just encountered was that whilst my work directory had sufficient space to build the cross-gcc rpms, my homedir doesn't - after 12G of stuff was written, I ran out of space and mail started getting bounced and my desktop programs started misbehaving. Version-Release number of selected component (if applicable): fedpkg-1.32-1.fc27.noarch
I think you mean the local command, right?
I missed commands prep, compile, install, verify-files.
PR: https://pagure.io/rpkg/pull-request/368/
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
fedpkg-1.35-1.el7 rpkg-1.56-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b9c5bded6e
fedpkg-1.35-1.el6 rpkg-1.56-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-8d36e5f524
fedpkg-1.35-1.fc27 rpkg-1.56-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-4b83678c28
fedpkg-1.35-1.fc28 rpkg-1.56-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-ba8314548a
(In reply to cqi from comment #1) > I think you mean the local command, right? Yes.
What does the change actually do? Does it require you to supply: --buildrootdir=/foo/bar to fedpkg every time you run it? Can it be set in a config file somewhere?
fedpkg-1.35-1.fc27, rpkg-1.56-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-4b83678c28
fedpkg-1.35-1.el7, rpkg-1.56-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b9c5bded6e
fedpkg-1.35-1.el6, rpkg-1.56-1.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-8d36e5f524
fedpkg-1.35-1.fc28, rpkg-1.56-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-ba8314548a
fedpkg-1.35-1.fc28, rpkg-1.56-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
fedpkg-1.35-1.fc27, rpkg-1.56-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
fedpkg-1.35-1.el7, rpkg-1.56-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
fedpkg-1.35-1.el6, rpkg-1.56-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.