how to do epel8 fedpkg mockbuild?

[Dave Love]

What do you need to do these days to run an epel-8 mock build?
fedpkg mockbuild fails for me with

Error: Error downloading packages:
  Status code: 403 for https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/... (IP: 38.145.60.16)

I configured a RHEL subscription key so that I can make a rhel-8 root
successfully.

[Dave Love]

I wrote:
> What do you need to do these days to run an epel-8 mock build?
> fedpkg mockbuild fails for me with
>
> Error: Error downloading packages:
>   Status code: 403 for
> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/...
> (IP: 38.145.60.16)

It turns out that it works if you link, say, the alma+epel mock config
into ~/.config/mock/epel-8-x86_64.cfg, per Richard Shaw's question at
around the same time.  I might have guessed that was the problem if it
reported an error about epel-8-x86_64.cfg rather than failing to
download RHEL rpms.  (I just had alma linked to default.cfg on the RHEL8
system I use, not to epel-8.)

[Pavel Raiskup]

On Monday, February 7, 2022 11:45:12 AM CET Dave Love wrote:
> > What do you need to do these days to run an epel-8 mock build?
> > fedpkg mockbuild fails for me with
> >
> > Error: Error downloading packages:
> >   Status code: 403 for
> > https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/...
> > (IP: 38.145.60.16)
>
> It turns out that it works if you link, say, the alma+epel mock config
> into ~/.config/mock/epel-8-x86_64.cfg, per Richard Shaw's question at
> around the same time.  I might have guessed that was the problem if it
> reported an error about epel-8-x86_64.cfg rather than failing to
> download RHEL rpms.  (I just had alma linked to default.cfg on the RHEL8
> system I use, not to epel-8.)

I'd encourage anyone to update to the latest fedpkg (v1.42):
https://bodhi.fedoraproject.org/updates/?packages=fedpkg

And Mock (configs v36.6):
https://bodhi.fedoraproject.org/updates/?packages=mock

Then mock should give a verbose hint about what to do.  For more info:
https://lists.fedoraproject.org/archives/list/[e-mail]/...

Pavel

[Dave Love]

Pavel Raiskup  writes:
> I'd encourage anyone to update to the latest fedpkg (v1.42):
> https://bodhi.fedoraproject.org/updates/?packages=fedpkg
>
> And Mock (configs v36.6):
> https://bodhi.fedoraproject.org/updates/?packages=mock

What I was using, in the hope it would help, is the latest in
epel-testing (fedpkg-1.41-2, mock-2.16-1, and mock-core-configs-37-1).
> Then mock should give a verbose hint about what to do.  For more info:
> https://lists.fedoraproject.org/archives/list/[e-mail]/...

So it will stay broken in EPEL7?

[Pavel Raiskup]

On Wednesday, February 9, 2022 10:46:44 AM CET Dave Love wrote:
> Pavel Raiskup  writes:
> > I'd encourage anyone to update to the latest fedpkg (v1.42):
> > https://bodhi.fedoraproject.org/updates/?packages=fedpkg
> >
> > And Mock (configs v36.6):
> > https://bodhi.fedoraproject.org/updates/?packages=mock
>
> What I was using, in the hope it would help, is the latest in
> epel-testing (fedpkg-1.41-2, mock-2.16-1, and mock-core-configs-37-1).

You need the fedpkg-1.42, and even updated rpkg (from the very same Bodhi
update) in case its update is not "enforced" by fedpkg's Requires:.
> > Then mock should give a verbose hint about what to do.  For more info:
> > https://lists.fedoraproject.org/archives/list/[e-mail]/...
>
> So it will stay broken in EPEL7?

Not sure whether you mean building for EPEL 7 (in epel-7 chroot), or
building on EPEL 7 host.... but both cases should OK.

Pavel
> epel-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]...
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure