Re: Mock v2.16 release, mock-core-configs v36.4

[Pavel Raiskup]

On Sunday, December 19, 2021 4:55:28 PM CET Maxwell G via devel wrote:
>  On Thursday, December 16, 2021 12:25:12 PM CST Pavel Raiskup wrote:
>  > Hello!
>  > 
>  > I'm glad I can announce that we have a new release of Mock.  See the full
>  > release notes [1].  The major change that happened is the removal of
>  > 'epel-8' config files, as a follow-up for [2] discussion (and of course on
>  > *devel lists, big thanks to everyone for the discussion).
>  > 
>  > Note that this is is the last v2 release being shipped to all supported
>  > Fedora/EPEL versions.  From now on, we'll move to v3 with development (in
>  > 'main' branch) and EPEL 7 stays on v2 (in 'mock-2' branch, bugfix
> only).
>  > 
>  > [1] https://rpm-software-management.github.io/mock/Release-Notes-2.16
>  > [2] https://pagure.io/epel/issue/133
>  > [Fedora 35]: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a7d4aaa6fe
>  > [Fedora 34]: https://bodhi.fedoraproject.org/updates/FEDORA-2021-0947974f0a
>  > [EPEL 8]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-2d0f959e00
>  > [EPEL 7]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-82ccb8f2b7
>  > 
>  > Happy building!
>  > Pavel
>  
>  I have tested this update and found a couple problems. Please see my comment on the
> Fedora 35 update page (linked above) or see below:
>  
>  > Hi @praiskup et. al,
>  > 
>  > There are a couple problems:
>  > 
>  > - `fedpkg --release epel8 mockbuild ` does not work properly. It defaults to
>  > rhel8, which does not work by default and results in a 403 error when
>  > dnf/mock attempts to install packages. After running `ln -s
>  > /etc/mock/alma+epel-8-x86 
Mock doesn't default to RHEL, there must be some other problem.  I quickly tried
running that command, and fedpkg seems to create some temporary configuration
directory and defaults to building from Koji repos (aka `--enablerepo local`?).

Thank you for the report though, I will take a look.  ATM I'm curious if this is
a bug in Mock ...

>  _64.cfg ~/.config/mock/epel-8-x86_64.cfg`, it breaks entirely:
>  > 
>  > ```
>  > $ fedpkg --release epel8 mockbuild --no-cleanup-after
>  > Not downloading already downloaded ansible-core-2.12.1.tar.gz
>  > 
>  > setting SOURCE_DATE_EPOCH=1638921600
>  > Wrote:
> /home/gotmax/Sync/git-repos/packaging/fedora_rpms/forks.repos/ansible.repos/ansible-core/ansible-core-2.12.1-2.el8.src.rpm
>  > 
>  > mockbuild.exception.ConfigError: Could not find included config file:
> /tmp/epel-8-x86_64.v230b0w7mockconfig/templates/almalinux-8.tpl
>  > 
>  > ERROR: Error in configuration
>  > Could not execute mockbuild: Failed to execute command.
>  > ```
>  > 
>  > It is possible to override the buildroot with `--root alma+epel-8-x86_64`, but that
> is cumbersome and shouldn't be necessary.
>  > 
>  > - Using `alma+epel-8-x86_64` works with `mock` itself and with `fedpkg` after
> applying the aforementioned fix, but mock/dnf repeatedly prints out the following error
> when installing packages:  `Invalid configuration value: failoverm
>  ethod=priority in /var/lib/mock/alma+epel-8-x86_64/root/etc/dnf/dnf.conf; Configuration:
> OptionBinding with id "failovermethod" does not exist`. 
This is an innocent warning, new DNF will not pollute the stderr:
https://github.com/rpm-software-management/libdnf/pull/1276

>  > - Even if I wanted to use the `rhel+epel-8-*` configs, they
> don't work at
>  > all, as `subscription-manager` is broken (rhbz#1995465) and it is impossible
>  > to obtain an entitlement. 
This is unfortunate, I hope we can get an update soon.

>  > In my opinion, this update should not be pushed until these
> crucial issues are fixed. 
This all looks like the same issue.  There's no "RHEL default", same as no
"Alma default".  According to the previous discussion.

Thanks again,
Pavel

>  > Thanks,
>  > 
>  > Maxwell
>  
>  
>

Mock v2.16 release, mock-core-configs v36.4

[Pavel Raiskup]

On Sunday, December 19, 2021 9:56:20 PM CET Pavel Raiskup wrote:
>  On Sunday, December 19, 2021 4:55:28 PM CET Maxwell G via devel
> wrote:
>  > On Thursday, December 16, 2021 12:25:12 PM CST Pavel Raiskup wrote:
>  > > Hello!
>  > > 
>  > > I'm glad I can announce that we have a new release of Mock.  See the full
>  > > release notes [1].  The major change that happened is the removal of
>  > > 'epel-8' config files, as a follow-up for [2] discussion (and of course
> on
>  > > *devel lists, big thanks to everyone for the discussion).
>  > > 
>  > > Note that this is is the last v2 release being shipped to all supported
>  > > Fedora/EPEL versions.  From now on, we'll move to v3 with development (in
>  > > 'main' branch) and EPEL 7 stays on v2 (in 'mock-2' branch,
> bugfix only).
>  > > 
>  > > [1] https://rpm-software-management.github.io/mock/Release-Notes-2.16
>  > > [2] https://pagure.io/epel/issue/133
>  > > [Fedora 35]: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a7d4aaa6fe
>  > > [Fedora 34]: https://bodhi.fedoraproject.org/updates/FEDORA-2021-0947974f0a
>  > > [EPEL 8]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-2d0f959e00
>  > > [EPEL 7]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-82ccb8f2b7
>  > > 
>  > > Happy building!
>  > > Pavel
>  > 
>  > I have tested this update and found a couple problems. Please see my comment on the
> Fedora 35 update page (linked above) or see below:
>  > 
>  > > Hi @praiskup et. al,
>  > > 
>  > > There are a couple problems:
>  > > 
>  > > - `fedpkg --release epel8 mockbuild ` does not work properly. It defaults to
>  > > rhel8, which does not work by default and results in a 403 error when
>  > > dnf/mock attempts to install packages. After running `ln -s
>  > > /etc/mock/alma+epel-8-x86
>  
>  Mock doesn't default to RHEL, there must be some other problem.  I quickly tried
>  running that command, and fedpkg seems to create some temporary configuration
>  directory and defaults to building from Koji repos (aka `--enablerepo local`?).
>  
>  Thank you for the report though, I will take a look.  ATM I'm curious if this is
>  a bug in Mock ... 
Ok, I see it now:

  $ fedpkg -v mockbuild -N
  Creating repo object from /home/praiskup/rh/packages/mock
  Not downloading already downloaded mock-2.16.tar.gz
  Srpm found, rewriting it.
  Running: rpmbuild --define '_sourcedir /home/praiskup/rh/packages/mock' --define
'_specdir /home/praiskup/rh/packages/mock' --define '_builddir
/home/praiskup/rh/packages/mock' --define '_srcrpmdir
/home/praiskup/rh/packages/mock' --define '_rpmdir
/home/praiskup/rh/packages/mock' --define '_rpmfilename
%%{ARCH}/%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm' --define 'dist
%{?distprefix}.el8' --define 'rhel 8' --eval '%undefine fedora'
--define 'el8 1' --nodeps -bs /home/praiskup/rh/packages/mock/mock.spec

  setting SOURCE_DATE_EPOCH=1639612800
  Wrote: /home/praiskup/rh/packages/mock/mock-2.16-1.el8.src.rpm
  Mock config /etc/mock/epel-8-x86_64.cfg was not found. Going to request koji to create
new one.
  ...
  ^Z
  [1]+  Stopped                 fedpkg -v mockbuild -N
  $ cat /tmp/epel-8-x86_64.zbs7jxysmockconfig/epel-8-x86_64.cfg
  # Auto-generated by the Koji build system
  ....

So this is basically a config you also get by:

  $ koji mock-config --target epel8-candidate --arch x86_64

And this config can not work, since we don't have that repository locally
available.  But, doing this (or alike):

  sudo ln -s /etc/mock/rhel+epel-8-x86_64.cfg /etc/mock/epel-8-x86_64.cfg

... fixes the problem for me.  So it seems that fedpkg doesn't (yet) know
there's ~/.config/mock* at all.

Pavel

Mock v2.16 release, mock-core-configs v36.4

[Pavel Raiskup]

On Sunday, December 19, 2021 10:22:57 PM CET Pavel Raiskup wrote:
>  So it seems that fedpkg doesn't (yet) know there's
> ~/.config/mock* at all. 
Proposed fix: https://pagure.io/rpkg/pull-request/595

Pavel

Mock v2.16 release, mock-core-configs v36.4

[Miro Hrončok]

On 19. 12. 21 22:39, Pavel Raiskup wrote:
>  On Sunday, December 19, 2021 10:22:57 PM CET Pavel Raiskup wrote:
> > So it seems that fedpkg doesn't (yet) know there's ~/.config/mock* at all.
>  
>  Proposed fix: https://pagure.io/rpkg/pull-request/595 
It seems that this would only fix the issue if the symbolic link has already 
been created. But before that, `fedpkg --release epel8 mockbuild` would still 
fail, wouldn't it? Can we fix that as well, even if it's fixed in some 
documentation only?

-- 
Miro Hrončok
-- 
Phone: [phone]
IRC: mhroncok