EPEL7 repo error for distribution-gpg-keys?

[Nick Howitt]

On a server I don't use very often, I am trying to update 
mock-core-configs with yum and I am seeing:

>  Resolving Dependencies
>  --> Running transaction check
>  ---> Package mock-core-configs.noarch 0:36.9-1.el7 will be updated
>  ---> Package mock-core-configs.noarch 0:36.13-1.el7 will be an update
>  --> Processing Dependency: distribution-gpg-keys >= 1.77 for package: 
>  mock-core-configs-36.13-1.el7.noarch
>  --> Finished Dependency Resolution
>  Error: Package: mock-core-configs-36.13-1.el7.noarch (epel-unverified)
>             Requires: distribution-gpg-keys >= 1.77
>             Installed: distribution-gpg-keys-1.75-1.el7.noarch 
>  (@epel-unverified)
>                 distribution-gpg-keys = 1.75-1.el7
>   You could try using --skip-broken to work around the problem
>   You could try running: rpm -Va --nofiles --nodigest 
On another server I regularly use and update I have 
distribution-gpg-keys-1.77-1.el7.noarch which I updated to a while back, 
so it appears that the updated package has been removed? Obviously this 
then breaks updating mock-core-configs. If 
distribution-gpg-keys-1.77-1.el7.noarch was a bad release, perhaps 1.75 
should be bumped to a later version so it gets installed over 1.77 
rather than just removing the package?

Regards,

Nick

[Troy Dawson]

On Wed, Oct 19, 2022 at 2:44 AM Nick Howitt via epel-devel <
epel-devel(a)lists.fedoraproject.org&gt; wrote:

>  On a server I don't use very often, I am trying to update
>  mock-core-configs with yum and I am seeing:
>
>  Resolving Dependencies
>  --> Running transaction check
>  ---> Package mock-core-configs.noarch 0:36.9-1.el7 will be updated
>  ---> Package mock-core-configs.noarch 0:36.13-1.el7 will be an update
>  --> Processing Dependency: distribution-gpg-keys >= 1.77 for package:
>  mock-core-configs-36.13-1.el7.noarch
>  --> Finished Dependency Resolution
>  Error: Package: mock-core-configs-36.13-1.el7.noarch (epel-unverified)
>             Requires: distribution-gpg-keys >= 1.77
>             Installed: distribution-gpg-keys-1.75-1.el7.noarch
>  (@epel-unverified)
>                 distribution-gpg-keys = 1.75-1.el7
>   You could try using --skip-broken to work around the problem
>   You could try running: rpm -Va --nofiles --nodigest
>
>
>  On another server I regularly use and update I have
>  distribution-gpg-keys-1.77-1.el7.noarch which I updated to a while back, so
>  it appears that the updated package has been removed? Obviously this then
>  breaks updating mock-core-configs. If
>  distribution-gpg-keys-1.77-1.el7.noarch was a bad release, perhaps 1.75
>  should be bumped to a later version so it gets installed over 1.77 rather
>  than just removing the package?
>  
Hi Nick,
Looking at the koji history, 1.77 never was untagged, but 1.75 was tagged
in on Oct. 10th.  Koji and the repo's only show what was the last tagged in.
I'm not sure why 1.75 was tagged in.

distribution-gpg-keys-1.78-1.el7 is currently in testing.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-318362b0c0

You can get things moving my using the epel-testing repo
  yum --enablerepo=epel-testing update mock-core-configs
If it works for you (it works for me) give the update some karma so it will
go out quicker.

Troy

[manuel wolfshant]

On 10/22/22 00:22, Troy Dawson wrote:
>  On Wed, Oct 19, 2022 at 2:44 AM Nick Howitt via epel-devel 
>  <epel-devel(a)lists.fedoraproject.org&gt; wrote:
>
>      On a server I don't use very often, I am trying to update
>      mock-core-configs with yum and I am seeing:
>
> >     Resolving Dependencies
> >     --> Running transaction check
> >     ---> Package mock-core-configs.noarch 0:36.9-1.el7 will be updated
> >     ---> Package mock-core-configs.noarch 0:36.13-1.el7 will be an update
> >     --> Processing Dependency: distribution-gpg-keys >= 1.77 for
> >     package: mock-core-configs-36.13-1.el7.noarch
> >     --> Finished Dependency Resolution
> >     Error: Package: mock-core-configs-36.13-1.el7.noarch
> >     (epel-unverified)
> >                Requires: distribution-gpg-keys >= 1.77
> >                Installed: distribution-gpg-keys-1.75-1.el7.noarch
> >     (@epel-unverified)
> >                    distribution-gpg-keys = 1.75-1.el7
> >      You could try using --skip-broken to work around the problem
> >      You could try running: rpm -Va --nofiles --nodigest
>
>      On another server I regularly use and update I have
>      distribution-gpg-keys-1.77-1.el7.noarch which I updated to a while
>      back, so it appears that the updated package has been removed?
>      Obviously this then breaks updating mock-core-configs. If
>      distribution-gpg-keys-1.77-1.el7.noarch was a bad release, perhaps
>      1.75 should be bumped to a later version so it gets installed over
>      1.77 rather than just removing the package?
>
>
>  Hi Nick,
>  Looking at the koji history, 1.77 never was untagged, but 1.75 was 
>  tagged in on Oct. 10th.  Koji and the repo's only show what was the 
>  last tagged in.
>  I'm not sure why 1.75 was tagged in.
>
>  distribution-gpg-keys-1.78-1.el7 is currently in testing.
>  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-318362b0c0
>
>  You can get things moving my using the epel-testing repo
>    yum --enablerepo=epel-testing update mock-core-configs
>  
s/distribution-gpg-keys/distribution-gpg-keys :)


>  If it works for you (it works for me) give the update some karma so
> it 
>  will go out quicker.
>
>  
wfm too

[Todd Zullinger]

manuel wolfshant wrote:
>  On 10/22/22 00:22, Troy Dawson wrote:
> > 
> > distribution-gpg-keys-1.78-1.el7 is currently in testing.
> > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-318362b0c0
> > 
> > You can get things moving my using the epel-testing repo
> >   yum --enablerepo=epel-testing update mock-core-configs
>  
>  s/distribution-gpg-keys/distribution-gpg-keys :) 
I presume s/mock-core-configs/distribution-gpg-keys/ is what
you meant? ;)

But since the OP was trying to install mock-core-configs and
hitting the issue, installing that package with the
epel-testing repo enabled would seem to be the quicker way
to the end goal.

Thanks to the karma you each left, the update is on the way
to the stable repo now.  (I added another, but only because
I had done the testing before I noticed that it only needed
2 positive karma points.)

-- 
Todd

[Nick Howitt]

On 21/10/2022 23:53, Todd Zullinger wrote:
>  manuel wolfshant wrote:
> > On 10/22/22 00:22, Troy Dawson wrote:
> >> distribution-gpg-keys-1.78-1.el7 is currently in testing.
> >> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-318362b0c0
> >>
> >> You can get things moving my using the epel-testing repo
> >>    yum --enablerepo=epel-testing update mock-core-configs
> > s/distribution-gpg-keys/distribution-gpg-keys :)
>  I presume s/mock-core-configs/distribution-gpg-keys/ is what
>  you meant? ;)
>
>  But since the OP was trying to install mock-core-configs and
>  hitting the issue, installing that package with the
>  epel-testing repo enabled would seem to be the quicker way
>  to the end goal.
>
>  Thanks to the karma you each left, the update is on the way
>  to the stable repo now.  (I added another, but only because
>  I had done the testing before I noticed that it only needed
>  2 positive karma points.)
>  
9 hours too late, but updating mock-core-configs works now if I enable 
the epel-testing repo for distribution-gpg-keys where it installs 
1.78-1.el7. FWIW, distribution-gpg-keys-1.78-1.el7 has not yet made its 
way to the epel repo.

Thanks,

Nick