Re: Call for testers for rpmautospec in staging

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Apr 09, 2020 at 05:43:36PM +0200, Miro Hrončok wrote:
> On 09. 04. 20 15:43, Pierre-Yves Chibon wrote:
> > We have written some documentation on how `rpmautospec` works and how you
> > can opt in at:https://docs.pagure.org/Fedora-Infra.rpmautospec/
> 
> Thanks for working on this \o/
> 
> I will definitively try this out soon.
> 
> 
> Here is one important concern I have before I dive in.
> 
> From the docs:
> 
> https://docs.pagure.org/Fedora-Infra.rpmautospec/principle.html
> > The plugin then installs and calls rpmautospec in the chroot.
> 
> https://docs.pagure.org/Fedora-Infra.rpmautospec/install.html
> > The Koji plugin rpmautospec_builder is meant to be installed on all the Koji
> > builders running the buildSRPMFromSCM task
> 
> I suppose this means the "koji-builder-plugin-rpmautospec" is installed on
> the Koji builder and "rpmautospec" package is installed inside the mock
> chroot of the buildSRPMFromSCM task, right?
> 
> I've looked at your stg Koji builds:
>   https://koji.stg.fedoraproject.org/koji/tasks?owner=pingou&state=all
> 
> homebank seem to use rpmautospec:
>   https://src.stg.fedoraproject.org/rpms/homebank/blob/master/f/homebank.spec
> 
> The buildSRPMFromSCM task root.log has:
> 
> ================================================================================
>  Package                   Arch    Version                          Repo   Size
> ================================================================================
> Installing:
>  rpmautospec               noarch  0.1.2-1.fc33                     build 8.8 k
> Installing dependencies:
...
>  python3                   aarch64 3.8.1-1.fc32                     build  31 k
...

> I am not entirely sure if the buildSRPMFromSCM task in a side tag is using
> that side tag's builds for itself, but if it does, my specific concern is
> that the entire stack of packages rpmautospec depends on has a runtime
> dependency on python(abi) = 3.8, so when we'll start bootstrapping Python
> 3.9 in a side tag, the plugin won't be installable yet, hence every "Python
> package" (including the Python interpreter) in the dep chain of
> "rpmautospec" might not be able to use this.
> 
> Is my conclusion correct?

I actually cannot comment on this, it may be worth opening a koji ticket to ask
if this is the case or not and if it is if they can think of a way to deal with
this.

Random thought: Could both python versions be made available in the side-tag?

On the bright, I take your questions as you'd be interested in using this ;-)


Pierre
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux