Hi,
I do backport stuff from rawhide in my coprs a lot. The relatively newly announced fedmsg+rpkg thing is making my life easier than ever. So first of all, kudos!
Now to my problem: some packages update rawhide only and the fedpkg+rpkg integration works like a charm. Other packages however keep all the branches synced and they use the %{fedora} variable to determine different behavior. I'd like to tell copr: Set fedora to 29 even if building for older Fedoras. Can I do that?
Thanks.
On Mon, May 14, 2018 at 12:18 PM, Miro Hrončok mhroncok@redhat.com wrote:
Hi,
I do backport stuff from rawhide in my coprs a lot. The relatively newly announced fedmsg+rpkg thing is making my life easier than ever. So first of all, kudos!
Now to my problem: some packages update rawhide only and the fedpkg+rpkg integration works like a charm. Other packages however keep all the branches synced and they use the %{fedora} variable to determine different behavior. I'd like to tell copr: Set fedora to 29 even if building for older Fedoras. Can I do that?
Thank you for the positive feedback. I need to admit I don't exactly understand the use-case. When a package keeps the branches synced, wouldn't it help to build e.g. for rawhide branch only and ignore incoming push events for all the other branches?
Thanks.
Miro Hrončok
Phone: +420777974800 IRC: mhroncok _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
On 14.5.2018 12:35, Michal Novotny wrote:
Now to my problem: some packages update rawhide only and the fedpkg+rpkg integration works like a charm. Other packages however keep all the branches synced and they use the %{fedora} variable to determine different behavior. I'd like to tell copr: Set fedora to 29 even if building for older Fedoras. Can I do that?Thank you for the positive feedback. I need to admit I don't exactly understand the use-case. When a package keeps the branches synced, wouldn't it help to build e.g. for rawhide branch only and ignore incoming push events for all the other branches?
The use case for example:
fedpkg switches to python3 in rawhide only with a conditional (if fedora
28).
I want to build a fedpkg package for f28 that uses python3.
Currently that would require:
1. fedpkg clone fedpkg && cd fedpkg 2. change the conditional in spec 3. fedpkg srpm 4. copr upload and build 5. script the above or manually do it with every rawhide update
What I'd like to do:
1. add fedpkg package with fedmsg+rpkg integration 2. set fedora to 29 via a configuration dialog 3. keep it running automatically
On Mon, May 14, 2018 at 1:12 PM, Miro Hrončok mhroncok@redhat.com wrote:
On 14.5.2018 12:35, Michal Novotny wrote:
Now to my problem: some packages update rawhide only and the fedpkg+rpkg integration works like a charm. Other packages however keep all the branches synced and they use the %{fedora} variable to determine different behavior. I'd like to tell copr: Set fedora to 29 even if building for older Fedoras. Can I do that?Thank you for the positive feedback. I need to admit I don't exactly understand the use-case. When a package keeps the branches synced, wouldn't it help to build e.g. for rawhide branch only and ignore incoming push events for all the other branches?
The use case for example:
fedpkg switches to python3 in rawhide only with a conditional (if fedora > 28).
I want to build a fedpkg package for f28 that uses python3.
Currently that would require:
- fedpkg clone fedpkg && cd fedpkg
- change the conditional in spec
- fedpkg srpm
- copr upload and build
- script the above or manually do it with every rawhide update
What I'd like to do:
- add fedpkg package with fedmsg+rpkg integration
- set fedora to 29 via a configuration dialog
- keep it running automatically
Can we cover it just by providing "with" and "without" fields for chroots/builds which would then basically translate to --with/--without options for mock, rpkg, and similar tools?
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
On 14.5.2018 14:20, Michal Novotny wrote:
Can we cover it just by providing "with" and "without" fields for chroots/builds which would then basically translate to --with/--without options for mock, rpkg, and similar tools?
Yes! Good idea. Thanks.
On 14.5.2018 15:09, Miro Hrončok wrote:
On 14.5.2018 14:20, Michal Novotny wrote:
Can we cover it just by providing "with" and "without" fields for chroots/builds which would then basically translate to --with/--without options for mock, rpkg, and similar tools?
Yes! Good idea. Thanks.
One more thing. A granularity per package might be desirable here.
On Mon, May 14, 2018 at 3:13 PM, Miro Hrončok mhroncok@redhat.com wrote:
On 14.5.2018 15:09, Miro Hrončok wrote:
On 14.5.2018 14:20, Michal Novotny wrote:
Can we cover it just by providing "with" and "without" fields for chroots/builds which would then basically translate to --with/--without options for mock, rpkg, and similar tools?
Yes! Good idea. Thanks.
OK.
One more thing. A granularity per package might be desirable here.
I will do some basic implementation, probably just with per-chroot granularity. We will add the package specific setting when the new API and new copr-cli comes.
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
On 14.5.2018 15:18, Michal Novotny wrote:
I will do some basic implementation, probably just with per-chroot granularity. We will add the package specific setting when the new API and new copr-cli comes.
Thank you very much. Feel free to let me test it on staging or so.
If this works, I'll gladly buy you a beverage.
On Monday, May 14, 2018 2:20:28 PM CEST Michal Novotny wrote:
Can we cover it just by providing "with" and "without" fields for chroots/builds which would then basically translate to --with/--without options for mock, rpkg, and similar tools?
You could add any other mock option that way, especially --define is important in this context.
Btw. slight -1 since any such feature makes the build reproducibility harder -- build result depends not only on chroot content, but also on some random database values, stored only in (Fedora) copr. So in turn it slightly lowers the overall quality of packages coming from copr and thus rises chances that such package won't ever be merged into Fedora.
Pavel
On Tuesday, May 15, 2018 3:27:38 PM CEST Pavel Raiskup wrote:
On Monday, May 14, 2018 2:20:28 PM CEST Michal Novotny wrote:
Can we cover it just by providing "with" and "without" fields for chroots/builds which would then basically translate to --with/--without options for mock, rpkg, and similar tools?
You could add any other mock option that way, especially --define is important in this context.
Btw. slight -1 since any such feature makes the build reproducibility harder -- build result depends not only on chroot content, but also on some random database values, stored only in (Fedora) copr. So in turn it slightly lowers the overall quality of packages coming from copr and thus rises chances that such package won't ever be merged into Fedora.
No {review,pull-request,discussion}: https://pagure.io/copr/copr/issue/98
Pavel
On Monday, May 14, 2018 12:18:56 PM CEST Miro Hrončok wrote:
Hi,
I do backport stuff from rawhide in my coprs a lot. The relatively newly announced fedmsg+rpkg thing is making my life easier than ever. So first of all, kudos!
Now to my problem: some packages update rawhide only and the fedpkg+rpkg integration works like a charm. Other packages however keep all the branches synced and they use the %{fedora} variable to determine different behavior. I'd like to tell copr: Set fedora to 29 even if building for older Fedoras. Can I do that?
Go to Copr Project -> Settings -> Chrooot [Edit], and fill field 'Packages' with additional package (say 'foo'), which provides additional macros (say /usr/lib/rpm/macros.d/macros.foo) redefining whatever the default in fedora is.
Pavel
copr-devel@lists.fedorahosted.org
-
Michal Novotny -
Miro Hrončok -
Pavel Raiskup