My install is Foreman 1.10.1 on Fedora 19 installed using the repositories,
and the same goes for all of the plugins that I have installed.
I'm trying to add the plugin for remote execution but when I try to install
using yum I get:
Error: Package: rubygem-smart_proxy_dynflow-0.0.4-1.fc19.noarch
(foreman-plugins)
Requires: rubygem(sequel)
Available: rubygem-sequel-3.47.0-1.fc19.noarch (fedora)
rubygem(sequel) = 3.47.0
Installed: rubygem-sequel-4.16.0-1.fc19.noarch (@updates)
Not found
The documentation for plugins suggests using foreman-installer now, but for
whatever reason when I run that I don't have access to the
–[no-]enable-<plugin> options, hence the use of yum. I also don't seem to
have access to the tfm-* packages that the documentation suggests but my
repo file is verbatim to the docs. I've been upgrading Foreman in place
since I think version 1.5 and it's very possible I've mangled the installer
yaml at some point, but I don't think that matters in this case because the
plugin seems to want to install some specific dependency and isn't happy
with a newer version.
I'm fine reverting from using yum to install the plugins from gems (section
2.3), but the first thing it says is "Not recommended" so I'd rather fix it
than change if that's possible.
Couple of questions:
Would fixing my foreman-installer config bring back the --enable commands?
Should I be seeing the tfm-* packages in yum assuming that I've got the
correct 1.10 repo file?
Why does ruby hate me?
Thanks
> >
>
> >
> My install is Foreman 1.10.1 on Fedora 19 installed using the
> repositories, and the same goes for all of the plugins that I have
> installed.
>
> I'm trying to add the plugin for remote execution but when I try to
> install using yum I get:
>
> Error: Package: rubygem-smart_proxy_dynflow-0.0.4-1.fc19.noarch
> (foreman-plugins)
> Requires: rubygem(sequel)
> Available: rubygem-sequel-3.47.0-1.fc19.noarch (fedora)
> rubygem(sequel) = 3.47.0
> Installed: rubygem-sequel-4.16.0-1.fc19.noarch (@updates)
> Not found
This was a bug in the rubygem-sequel package that was pushed to F19
updates ages ago (https://bugzilla.redhat.com/show_bug.cgi?id=1174138),
but never fixed. Our dependency should have been on "rubygem-sequel" to
workaround the missing provides.
I think our tests passed because an older version of the package (3.47.0
in your output) satisified the dep. You could try running "yum
downgrade rubygem-sequel-3.47.0-1.fc19.noarch" to switch to the older
version, or you could force installation of the package with rpm -i
–nodeps. (In this instance, it's safe to do so.)
> Would fixing my foreman-installer config bring back the --enable commands?
Yes, it's probably just that the installer config doesn't get updated on
upgrades. Adding the installer and answers entries for plugins to your
configs under /etc/foreman should bring them back - see
https://github.com/theforeman/foreman-installer/tree/1.10-stable/config.
> Should I be seeing the tfm-* packages in yum assuming that I've got the
> correct 1.10 repo file?
The tfm-* prefixes are only for EL6/7. Fedora RPMs have no tfm- or
ruby193- prefix, so just ignore any references you see to them.
···
On 28/01/16 00:07, Geoff Johnson wrote:
–
Dominic Cleal
dominic@cleal.org
I'd rather --nodeps than downgrade because there's other packages that have
sequel as a dependency but I'm not able to find an rpm anywhere for that
version. Any chance you know where I can get one from? I tried yum install
–downloadonly but it doesn't download the file anywhere that I can find,
not sure why.
Thanks
···
On Thursday, 28 January 2016 00:36:32 UTC-8, Dominic Cleal wrote:
>
> On 28/01/16 00:07, Geoff Johnson wrote:
> > >
> >
> > >
> > My install is Foreman 1.10.1 on Fedora 19 installed using the
> > repositories, and the same goes for all of the plugins that I have
> > installed.
> >
> > I'm trying to add the plugin for remote execution but when I try to
> > install using yum I get:
> >
> > Error: Package: rubygem-smart_proxy_dynflow-0.0.4-1.fc19.noarch
> > (foreman-plugins)
> > Requires: rubygem(sequel)
> > Available: rubygem-sequel-3.47.0-1.fc19.noarch (fedora)
> > rubygem(sequel) = 3.47.0
> > Installed: rubygem-sequel-4.16.0-1.fc19.noarch (@updates)
> > Not found
>
> This was a bug in the rubygem-sequel package that was pushed to F19
> updates ages ago (https://bugzilla.redhat.com/show_bug.cgi?id=1174138),
> but never fixed. Our dependency should have been on "rubygem-sequel" to
> workaround the missing provides.
>
> I think our tests passed because an older version of the package (3.47.0
> in your output) satisified the dep. You could try running "yum
> downgrade rubygem-sequel-3.47.0-1.fc19.noarch" to switch to the older
> version, or you could force installation of the package with rpm -i
> --nodeps. (In this instance, it's safe to do so.)
>
> > Would fixing my foreman-installer config bring back the --enable
> commands?
>
> Yes, it's probably just that the installer config doesn't get updated on
> upgrades. Adding the installer and answers entries for plugins to your
> configs under /etc/foreman should bring them back - see
> https://github.com/theforeman/foreman-installer/tree/1.10-stable/config.
>
> > Should I be seeing the tfm-* packages in yum assuming that I've got the
> > correct 1.10 repo file?
>
> The tfm-* prefixes are only for EL6/7. Fedora RPMs have no tfm- or
> ruby193- prefix, so just ignore any references you see to them.
>
> --
> Dominic Cleal
> dom...@cleal.org
>
Sorry, I'm not quite sure which package you're talking about.
I think you want the smart_proxy_dynflow package as that's the one which
would need installing with nodeps. This is available from:
http://yum.theforeman.org/plugins/1.10/fc19/x86_64/ at
http://yum.theforeman.org/plugins/1.10/fc19/x86_64/rubygem-smart_proxy_dynflow-0.0.4-1.fc19.noarch.rpm.
Cheers,
···
--
Dominic Cleal
dominic@cleal.org
On 30/01/16 04:28, Geoff Johnson wrote:
I’d rather --nodeps than downgrade because there’s other packages that
have sequel as a dependency but I’m not able to find an rpm anywhere for
that version. Any chance you know where I can get one from? I tried yum
install --downloadonly but it doesn’t download the file anywhere that I
can find, not sure why.
Thanks
On Thursday, 28 January 2016 00:36:32 UTC-8, Dominic Cleal wrote:
On 28/01/16 00:07, Geoff Johnson wrote:
> >
>
> >
> My install is Foreman 1.10.1 on Fedora 19 installed using the
> repositories, and the same goes for all of the plugins that I have
> installed.
>
> I'm trying to add the plugin for remote execution but when I try to
> install using yum I get:
>
> Error: Package: rubygem-smart_proxy_dynflow-0.0.4-1.fc19.noarch
> (foreman-plugins)
> Requires: rubygem(sequel)
> Available: rubygem-sequel-3.47.0-1.fc19.noarch (fedora)
> rubygem(sequel) = 3.47.0
> Installed: rubygem-sequel-4.16.0-1.fc19.noarch (@updates)
> Not found
This was a bug in the rubygem-sequel package that was pushed to F19
updates ages ago
(https://bugzilla.redhat.com/show_bug.cgi?id=1174138
<https://bugzilla.redhat.com/show_bug.cgi?id=1174138>),
but never fixed. Our dependency should have been on
"rubygem-sequel" to
workaround the missing provides.
I think our tests passed because an older version of the package
(3.47.0
in your output) satisified the dep. You could try running "yum
downgrade rubygem-sequel-3.47.0-1.fc19.noarch" to switch to the older
version, or you could force installation of the package with rpm -i
--nodeps. (In this instance, it's safe to do so.)
> Would fixing my foreman-installer config bring back the --enable
commands?
Yes, it's probably just that the installer config doesn't get
updated on
upgrades. Adding the installer and answers entries for plugins to your
configs under /etc/foreman should bring them back - see
https://github.com/theforeman/foreman-installer/tree/1.10-stable/config
<https://github.com/theforeman/foreman-installer/tree/1.10-stable/config>.
> Should I be seeing the tfm-* packages in yum assuming that I've
got the
> correct 1.10 repo file?
The tfm-* prefixes are only for EL6/7. Fedora RPMs have no tfm- or
ruby193- prefix, so just ignore any references you see to them.
--
Dominic Cleal
dom...@cleal.org <javascript:>
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
My brain skipped a cog and I was trying to find the rubygem-sequal rpm for
some reason. Thanks for the link, I should be good to go now from the looks
of it.
···
On Saturday, 30 January 2016 04:17:00 UTC-8, Dominic Cleal wrote:
>
> Sorry, I'm not quite sure which package you're talking about.
>
> I think you want the smart_proxy_dynflow package as that's the one which
> would need installing with nodeps. This is available from:
> http://yum.theforeman.org/plugins/1.10/fc19/x86_64/ at
>
> http://yum.theforeman.org/plugins/1.10/fc19/x86_64/rubygem-smart_proxy_dynflow-0.0.4-1.fc19.noarch.rpm.
>
>
> Cheers,
>
> --
> Dominic Cleal
> dom...@cleal.org
>
> On 30/01/16 04:28, Geoff Johnson wrote:
> > I'd rather --nodeps than downgrade because there's other packages that
> > have sequel as a dependency but I'm not able to find an rpm anywhere for
> > that version. Any chance you know where I can get one from? I tried yum
> > install --downloadonly but it doesn't download the file anywhere that I
> > can find, not sure why.
> >
> > Thanks
> >
> > On Thursday, 28 January 2016 00:36:32 UTC-8, Dominic Cleal wrote:
> >
> > On 28/01/16 00:07, Geoff Johnson wrote:
> > > >
> > >
> > > >
> > > My install is Foreman 1.10.1 on Fedora 19 installed using the
> > > repositories, and the same goes for all of the plugins that I have
> > > installed.
> > >
> > > I'm trying to add the plugin for remote execution but when I try
> to
> > > install using yum I get:
> > >
> > > Error: Package: rubygem-smart_proxy_dynflow-0.0.4-1.fc19.noarch
> > > (foreman-plugins)
> > > Requires: rubygem(sequel)
> > > Available: rubygem-sequel-3.47.0-1.fc19.noarch (fedora)
> > > rubygem(sequel) = 3.47.0
> > > Installed: rubygem-sequel-4.16.0-1.fc19.noarch
> (@updates)
> > > Not found
> >
> > This was a bug in the rubygem-sequel package that was pushed to F19
> > updates ages ago
> > (https://bugzilla.redhat.com/show_bug.cgi?id=1174138
> > ),
> > but never fixed. Our dependency should have been on
> > "rubygem-sequel" to
> > workaround the missing provides.
> >
> > I think our tests passed because an older version of the package
> > (3.47.0
> > in your output) satisified the dep. You could try running "yum
> > downgrade rubygem-sequel-3.47.0-1.fc19.noarch" to switch to the
> older
> > version, or you could force installation of the package with rpm -i
> > --nodeps. (In this instance, it's safe to do so.)
> >
> > > Would fixing my foreman-installer config bring back the --enable
> > commands?
> >
> > Yes, it's probably just that the installer config doesn't get
> > updated on
> > upgrades. Adding the installer and answers entries for plugins to
> your
> > configs under /etc/foreman should bring them back - see
> >
> https://github.com/theforeman/foreman-installer/tree/1.10-stable/config
> > <
> https://github.com/theforeman/foreman-installer/tree/1.10-stable/config>.
> >
> >
> > > Should I be seeing the tfm-* packages in yum assuming that I've
> > got the
> > > correct 1.10 repo file?
> >
> > The tfm-* prefixes are only for EL6/7. Fedora RPMs have no tfm- or
> > ruby193- prefix, so just ignore any references you see to them.
> >
> > --
> > Dominic Cleal
> > dom...@cleal.org
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Foreman users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to foreman-user...@googlegroups.com
> > <mailto:foreman-users+unsubscribe@googlegroups.com >.
> > To post to this group, send email to forema...@googlegroups.com
>
> > <mailto:forema...@googlegroups.com >.
> > Visit this group at https://groups.google.com/group/foreman-users.
> > For more options, visit https://groups.google.com/d/optout.
>
>
