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:
cracklib aarch64 2.9.6-21.fc31 build 83 k
fipscheck aarch64 1.5.0-7.fc31 build 26 k
fipscheck-lib aarch64 1.5.0-7.fc31 build 14 k
gdbm-libs aarch64 1:1.18.1-1.fc32 build 54 k
git-core aarch64 2.25.0-1.fc32 build 4.9 M
ima-evm-utils aarch64 1.2.1-2.fc31 build 56 k
koji noarch 1.20.0-1.fc32 build 149 k
less aarch64 551-2.fc31 build 156 k
libblkid aarch64 2.35-1.fc32 build 152 k
libcomps aarch64 0.1.14-1.fc32 build 77 k
libedit aarch64 3.1-31.20191231cvs.fc32 build 104 k
libfdisk aarch64 2.35-1.fc32 build 200 k
libmount aarch64 2.35-1.fc32 build 177 k
libnsl2 aarch64 1.2.0-5.20180605git4a062cf.fc31 build 58 k
libpwquality aarch64 1.4.2-1.fc32 build 101 k
libsmartcols aarch64 2.35-1.fc32 build 118 k
libtirpc aarch64 1.2.5-0.fc32 build 97 k
libutempter aarch64 1.1.6-17.fc31 build 26 k
libuuid aarch64 2.35-1.fc32 build 28 k
openssh aarch64 8.1p1-3.fc32 build 438 k
openssh-clients aarch64 8.1p1-3.fc32 build 596 k
openssl aarch64 1:1.1.1d-5.fc32 build 645 k
pam aarch64 1.3.1-21.fc32 build 662 k
python-pip-wheel noarch 19.3.1-1.fc32 build 1.2 M
python-setuptools-wheel noarch 41.6.0-1.fc32 build 282 k
python3 aarch64 3.8.1-1.fc32 build 31 k
python3-cffi aarch64 1.13.2-1.fc32 build 245 k
python3-chardet noarch 3.0.4-14.fc32 build 194 k
python3-cryptography aarch64 2.8-2.fc32 build 524 k
python3-dateutil noarch 1:2.8.0-7.fc32 build 291 k
python3-idna noarch 2.8-5.fc32 build 97 k
python3-kerberos aarch64 1.3.0-7.fc32 build 32 k
python3-koji noarch 1.20.0-1.fc32 build 290 k
python3-libcomps aarch64 0.1.14-1.fc32 build 50 k
python3-libs aarch64 3.8.1-1.fc32 build 7.8 M
python3-ply noarch 3.11-6.fc32 build 104 k
python3-pyOpenSSL noarch 19.0.0-5.fc32 build 92 k
python3-pycparser noarch 2.19-1.fc32 build 125 k
python3-pysocks noarch 1.7.1-3.fc32 build 35 k
python3-requests noarch 2.22.0-7.fc32 build 112 k
python3-requests-kerberos noarch 0.12.0-8.fc32 build 26 k
python3-rpm aarch64 4.15.1-2.fc32 build 98 k
python3-rpmautospec noarch 0.1.2-1.fc33 build 42 k
python3-setuptools noarch 41.6.0-1.fc32 build 588 k
python3-six noarch 1.14.0-1.fc32 build 36 k
python3-urllib3 noarch 1.25.7-2.fc32 build 173 k
rpm-sign-libs aarch64 4.15.1-2.fc32 build 26 k
tss2 aarch64 1331-2.fc31 build 570 k
util-linux aarch64 2.35-1.fc32 build 2.7 M
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?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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
