i regularly create COPR projects, which link an upstream repo .spec in a pagure project.
i want to build @ COPR _after_ modifying the .spec.
there are 2 ways I see doing that.
(1) manually modifying/patching the spec itself (2) having the buildsys auto-apply a patch to the spec, prior to the build
(1) is trivial, _if_ I edit a _fork_; that interferes with workflow, breaking upstream source updates' triggers for autobuilds at COPR
(2) is doable at opensuse's OBS, specifying the patch to be applied to the link-ed project sources
e.g.,
https://build.opensuse.org/package/view_file/home:pgnd:devel:gcc10/gcc10/_li...
what (other) mechanism exists for applying patches to a COPR spec, prior to build?
is there an OBS-style functional equivalent?
On Friday, August 21, 2020 8:11:29 PM CEST PGNet Dev wrote:
i regularly create COPR projects, which link an upstream repo .spec in a pagure project.
i want to build @ COPR _after_ modifying the .spec.
there are 2 ways I see doing that.
(1) manually modifying/patching the spec itself (2) having the buildsys auto-apply a patch to the spec, prior to the build
(1) is trivial, _if_ I edit a _fork_; that interferes with workflow, breaking upstream source updates' triggers for autobuilds at COPR
(2) is doable at opensuse's OBS, specifying the patch to be applied to the link-ed project sources
e.g.,
https://build.opensuse.org/package/view_file/home:pgnd:devel:gcc10/gcc10/_li...
what (other) mechanism exists for applying patches to a COPR spec, prior to build?
is there an OBS-style functional equivalent?
You can trigger the custom build (shell script) [1] using the custom webhook, and do whatever you need to (clone repo, apply patches, etc.). It's not really an equivalent, so -- as I understand it -- most of your requirements are specified in upstream ticket: https://pagure.io/copr/copr/issue/1441
[1] https://docs.pagure.org/copr.copr/custom_source_method.html
Pavel
On 8/23/20 1:33 AM, Pavel Raiskup wrote:
is there an OBS-style functional equivalent?
You can trigger the custom build (shell script) [1] using the custom webhook, and do whatever you need to (clone repo, apply patches, etc.). It's not really an equivalent, so -- as I understand it -- most of your requirements are specified in upstream ticket: https://pagure.io/copr/copr/issue/1441
[1] https://docs.pagure.org/copr.copr/custom_source_method.html
seems I keep bumping into the same issue!
re-reading that lengthy RFE & re: webhook scripting ...
the examples refer to copr cmd line setup of the scripting.
to verify, that _is_ the same functionality as
https://copr.fedorainfracloud.org/coprs/<user>/<project>/package/add/custom
@ online, correct?
buildsys@lists.fedoraproject.org