[Katello 2.3] yum update triggers rubygem-bundler-1.0.15-3.el6.noarch dependency issue

Support
1

$ yum update
<snip>
–> Processing Dependency: rubygem(thor) = 0.14.6 for package:
rubygem-bundler-1.0.15-3.el6.noarch
—> Package rubygem-thor.noarch 0:0.18.1-3.el6 will be an update
–> Finished Dependency Resolution
Error: Package: rubygem-bundler-1.0.15-3.el6.noarch (@foreman)
Requires: rubygem(thor) = 0.14.6
Removing: rubygem-thor-0.14.6-2.el6.noarch (@foreman)
rubygem(thor) = 0.14.6
Updated By: rubygem-thor-0.18.1-3.el6.noarch (epel)
rubygem(thor) = 0.18.1

2

This will be resolved once the following newpkg is tested and pushed to
EPEL6 stable:
https://bodhi.fedoraproject.org/updates/rubygem-bundler-1.5.2-2.el6

Use --disablerepo=epel or -x rubygem-thor for now.

··· On 02/09/15 09:53, JC wrote: > $ yum update > > --> Processing Dependency: rubygem(thor) = 0.14.6 for package: > rubygem-bundler-1.0.15-3.el6.noarch > ---> Package rubygem-thor.noarch 0:0.18.1-3.el6 will be an update > --> Finished Dependency Resolution > Error: Package: rubygem-bundler-1.0.15-3.el6.noarch (@foreman) > Requires: rubygem(thor) = 0.14.6 > Removing: rubygem-thor-0.14.6-2.el6.noarch (@foreman) > rubygem(thor) = 0.14.6 > Updated By: rubygem-thor-0.18.1-3.el6.noarch (epel) > rubygem(thor) = 0.18.1

–
Dominic Cleal
dominic@cleal.org

3

Thanks Dominic.

··· On 2 September 2015 at 10:07, Dominic Cleal wrote:

On 02/09/15 09:53, JC wrote:

$ yum update

–> Processing Dependency: rubygem(thor) = 0.14.6 for package:
rubygem-bundler-1.0.15-3.el6.noarch
—> Package rubygem-thor.noarch 0:0.18.1-3.el6 will be an update
–> Finished Dependency Resolution
Error: Package: rubygem-bundler-1.0.15-3.el6.noarch (@foreman)
Requires: rubygem(thor) = 0.14.6
Removing: rubygem-thor-0.14.6-2.el6.noarch (@foreman)
rubygem(thor) = 0.14.6
Updated By: rubygem-thor-0.18.1-3.el6.noarch (epel)
rubygem(thor) = 0.18.1

This will be resolved once the following newpkg is tested and pushed to
EPEL6 stable:
https://bodhi.fedoraproject.org/updates/rubygem-bundler-1.5.2-2.el6

Use --disablerepo=epel or -x rubygem-thor for now.

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/7QzIWG_Lbrs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

4

Dominic,

This is still a problem, even though FEDORA-EPEL-2014-1024
<https://bodhi.fedoraproject.org/updates/rubygem-bundler-1.5.2-2.el6> and
FEDORA-EPEL-2015-7528
<https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7528> have both
been resolved as far as I can tell:

yum update --quiet

Error: Package: rubygem-bundler-1.0.15-3.el6.noarch (@foreman/6.5)
Requires: rubygem(thor) = 0.14.6
Removing: rubygem-thor-0.14.6-2.el6.noarch (@foreman/6.5)
rubygem(thor) = 0.14.6
Updated By: rubygem-thor-0.18.1-3.el6.noarch (epel)
rubygem(thor) = 0.18.1
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

··· #

-= Stefan

On Wednesday, September 2, 2015 at 2:22:35 AM UTC-7, JC wrote:

Thanks Dominic.

On 2 September 2015 at 10:07, Dominic Cleal <dom...@cleal.org > <javascript:>> wrote:

On 02/09/15 09:53, JC wrote:

$ yum update

–> Processing Dependency: rubygem(thor) = 0.14.6 for package:
rubygem-bundler-1.0.15-3.el6.noarch
—> Package rubygem-thor.noarch 0:0.18.1-3.el6 will be an update
–> Finished Dependency Resolution
Error: Package: rubygem-bundler-1.0.15-3.el6.noarch (@foreman)
Requires: rubygem(thor) = 0.14.6
Removing: rubygem-thor-0.14.6-2.el6.noarch (@foreman)
rubygem(thor) = 0.14.6
Updated By: rubygem-thor-0.18.1-3.el6.noarch (epel)
rubygem(thor) = 0.18.1

This will be resolved once the following newpkg is tested and pushed to
EPEL6 stable:
https://bodhi.fedoraproject.org/updates/rubygem-bundler-1.5.2-2.el6

Use --disablerepo=epel or -x rubygem-thor for now.

–
Dominic Cleal
dom...@cleal.org <javascript:>

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/7QzIWG_Lbrs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

5

The first (FEDORA-EPEL-2014-1024) has not yet been pushed to stable,
it's still waiting for somebody else to test it and provide karma, or
for the maintainer to decide it can be pushed.

··· On 14/09/15 22:33, Stefan Lasiewski wrote: > Dominic, > > This is still a problem, even though FEDORA-EPEL-2014-1024 > and FEDORA-EPEL-2015-7528 > have > both been resolved as far as I can tell:

–
Dominic Cleal
dominic@cleal.org

6

I see. I don't fully understand the Fedora bug process, so thanks for the
clarification.

– Stefan

··· On Sep 15, 2015 12:29 AM, "Dominic Cleal" wrote:

On 14/09/15 22:33, Stefan Lasiewski wrote:

Dominic,

This is still a problem, even though FEDORA-EPEL-2014-1024
https://bodhi.fedoraproject.org/updates/rubygem-bundler-1.5.2-2.el6
and FEDORA-EPEL-2015-7528
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7528 have
both been resolved as far as I can tell:

The first (FEDORA-EPEL-2014-1024) has not yet been pushed to stable,
it’s still waiting for somebody else to test it and provide karma, or
for the maintainer to decide it can be pushed.

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/7QzIWG_Lbrs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

7

A workaround is to ensure you have yum-plugin-priorities and add the
following to the [foreman] repo:

priority=1

John

··· On Tuesday, 15 September 2015 17:59:04 UTC+1, Stefan Lasiewski wrote: > > I see. I don't fully understand the Fedora bug process, so thanks for the > clarification. > > -- Stefan > On Sep 15, 2015 12:29 AM, "Dominic Cleal" <dom...@cleal.org > > wrote: > >> On 14/09/15 22:33, Stefan Lasiewski wrote: >> > Dominic, >> > >> > This is still a problem, even though FEDORA-EPEL-2014-1024 >> > >> and FEDORA-EPEL-2015-7528 >> > have >> > both been resolved as far as I can tell: >> >> The first (FEDORA-EPEL-2014-1024) has not yet been pushed to stable, >> it's still waiting for somebody else to test it and provide karma, or >> for the maintainer to decide it can be pushed. >> >> -- >> Dominic Cleal >> dom...@cleal.org >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Foreman users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/foreman-users/7QzIWG_Lbrs/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> >