Learn more about these different git repos.
Other Git URLs
If you run a build with {{{fedpkg local}}} it remains silent until the build finishes, and then spits all the build messages in one go. It is quite inconvenient, because builds can get some long time, and watching the build progress can provide you some useful feedback.
{{{fedpkg local}}} should not buffer any output of the build progress and show it as soon as it is produced by the underlying rpmbuild process.
fedpkg prep has the same problem. It also spits the output from stdin and stderr out separately, so if you want to see the output from a failed patch command for the kernel package you have to scroll back a dozen screens or so. My fingers still hurt from doing that a few hundred times last night. :/
fedpkg prep
ugly dirty hack version of a fix (using 'tee') 0001-hack-continuous-fedpkg-local-output-using-tee.patch
Used something close to this, but made the _run_command call be able to take pipes.
Login to comment on this ticket.