On Mon, 9 Oct 2023 at 09:37, Florian Weimer <fwei...@redhat.com> wrote:
> * Stephen Smoogen:
>
> > could you add how you got it and how you ran it? I am trying to figure
> > out why a el8 config was pulled into a f38 system?
>
> This does it for me:
>
> $ mock -r c8s-x86_64 --init
>
>
OK my first problem was I misparsed your first email in thinking you were
build f38 and somehow pulling in c8s
> Even after:
>
> $ mock -r c8s-x86_64 --scrub all
>
>
So my system was out of date and I started with mock 5.0
INFO: calling preinit hooks
INFO: Using bootstrap image: fedora:latest
INFO: Pulling image: fedora:latest
INFO: Copy content of container fedora:latest to
/var/lib/mock/c8s-build-repo_356879-bootstrap/root
INFO: mounting fedora:latest with podman image mount
INFO: image fedora:latest as
/var/lib/containers/storage/overlay/f29face791dfb00155b668c68409ac8022a17e31230363148ee8145fd7cda6ab/merged
INFO: umounting image fedora:latest
(/var/lib/containers/storage/overlay/f29face791dfb00155b668c68409ac8022a17e31230363148ee8145fd7cda6ab/merged)
with podman image umount
INFO: Package manager dnf detected and used (fallback)
INFO: Bootstrap image not marked ready
Start(bootstrap): installing dnf tooling
I then went to 5.2 which gave the same issue but then went to the same
error everyone is seeing. The above errors were similar which I think made
me a possible realize the problem if both of you set up your configs the
same way.. you are mixing and matching koji which are using different
setups. The CentOS Stream Koji is set up to default to an older version of
mock while the Fedora one usually uses a newer option. In this case, the
config you are getting from the CentOS Stream Koji assumes that
bootstrapping is done one way, and the newer mock defaults to a different
way. The config to compare yours to is in
`/etc/mock/templates/centos-stream-8.tpl`
I did a bootstrap again with `mock -r centos-stream+epel-8-x86_64 --init`
which worked. Looking in the /etc/mock/templates file I see the additional
sets:
config_opts['chroot_setup_cmd'] = 'install tar gcc-c++ redhat-rpm-config
redhat-release which xz sed make bzip2 gzip gcc coreutils u
nzip diffutils cpio bash gawk rpm-build info patch util-linux findutils
grep'
config_opts['dist'] = 'el8' # only useful for --resultdir variable subst
config_opts['releasever'] = '8'
config_opts['package_manager'] = 'dnf'
config_opts['extra_chroot_dirs'] = [ '/run/lock', ]
config_opts['bootstrap_image'] = 'quay.io/centos/centos:stream8'
config_opts['dnf_vars'] = { 'stream': '8-stream',
'contentdir': 'centos',
}
so I think the bootstrap image needs to be added to make things work.. I
have attached a config where I combined the two together to work. [You will
need to put the number of teh buildroot you want to use versus latest to
match the original config]
> Package versions:
>
> mock-core-configs-39.1-1.fc38.noarch
> mock-filesystem-5.2-1.fc38.noarch
> mock-5.2-1.fc38.noarch
>
> > I have cut everything but lines causing the problems
> >
> >
> > config_opts['root'] = 'c8s-x86_64'
> > config_opts['yum.conf'] = '
> >
> [main]\ncachedir=/var/cache/yum\ndebuglevel=1\nlogfile=/var/log/yum.log\nreposdir=/dev/null\nretries=20\nobsoletes=1\ngpgcheck=0\nassumeyes=1\nkeepcache=1\ninstall_weak_deps=0\nstrict=1\n\n#
> > repos\n\n
> > [build]\nname=build\nbaseurl=
> https://kojihub.stream.centos.org/kojifiles/repos/c8s-build/latest/x86_64\nmodule_hotfixes=1\n
> '
> >
> > config_opts['macros']['%dist'] =
> '%{!?distprefix0:%{?distprefix}}%{expand:%{lua:for i=0,9999
> > do print("%{?distprefix" .. i .."}")
> end}}.el8%{?with_bootstrap:%{__bootstrap}}'
> >
> > This looks like a config from either the CentOS Stream koji or for
> > EPEL-next-8.
>
> It's generated with this command and lightly edited (to keep refering to
> the latest buildroot):
>
> $ koji -p stream mock-config --target c8s-candidate --arch x86_64
>
> Thanks,
> Florian
>
>
--
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
c8s-x86_64.cfg
Description: Binary data
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
