As I review building SCL packages using COPR, it seems the convention is to
build a SRPM with %scl set and then expose that to a COPR build. Is there
no way using tito and a git repo to just tell COPR to build everything
(source and binary) but pass in the value of the %scl macro? This would let
me
Our security folks are curious how actively maintained the httpd24
collection is and how soon we can expect updates to it to be made available
in the event of, say, a zero-day exploit.
--
Doran L. Barton - Senior Developer at Bluehost
"We build bodies that last a lifetime."
-- Seen in a fit
We are working on automating RPM builds (including SCL builds) using
Bamboo. Our automated scripts work great when we run them at the command
line, but when we run them via Bamboo, they fail because there is a
line that calls 'spec2scl' and spec2scl has code in it like this:
if len(args.specfi