Packaging: Issueshttps://projects.theforeman.org/https://projects.theforeman.org/favicon.ico?16970236342018-06-07T17:43:07ZForeman
Redmine Bug #23767 (Resolved): Update Katello spec enable SCL for Mongohttps://projects.theforeman.org/issues/23767#change-1067422018-06-07T17:43:07ZChris Robertschrobert@redhat.comBug #23767 (Ready For Testing): Update Katello spec enable SCL for Mongohttps://projects.theforeman.org/issues/23767#change-1065012018-06-04T13:39:00ZThe Foreman BotBug #23767 (Resolved): Update Katello spec enable SCL for Mongohttps://projects.theforeman.org/issues/237672018-06-01T08:57:15ZChris Robertschrobert@redhat.com
<p>/usr/sbin/foreman-debug: line 79: mongo: command not found</p>
<p>mongo does not work unless we run</p>
<p>scl enable rh-mongodb34 bash</p> Bug #20050 (Closed): ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/20050#change-1057422018-05-16T20:56:42ZAnonymous
<p>4a55d8c4d33b926dccb4ffb288d408a01a52d628 went in and got cherry-picked 1.17 and 1.16</p> Bug #22266 (Duplicate): Fresh installation of Foreman with Ansible plugin and proxy is broken aft...https://projects.theforeman.org/issues/22266#change-1056922018-05-16T15:26:18ZAnonymousBug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/20050#change-1056862018-05-16T15:15:00ZAnonymous
<p>Eric, your stuff is unrelated. Please open a new issue, preferrably under the Katello category/project.</p> Bug #20050 (Ready For Testing): ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/20050#change-1056852018-05-16T15:14:07ZAnonymousBug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/20050#change-1056392018-05-15T22:05:43ZEric Hansenehansen@catalogicsoftware.com
<p>removed unrelated issue</p> Bug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/20050#change-1056382018-05-15T22:00:15ZEric Hansenehansen@catalogicsoftware.com
<p>removed unrelated issue</p> Bug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/20050#change-1048182018-04-25T19:46:16ZMaximilian Stinskymaximilian@stinsky.com
<p>Great, I implemented the deletion of ruby-sequel-pg in my puppet class and everything works under 1.17.<br />Thank you.</p> Bug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/20050#change-1047542018-04-25T11:35:39ZAnonymous
<p>There's an ongoing discussion at <a class="external" href="https://community.theforeman.org/t/unmaintaned-incompatible-plugins-in-1-17-repos">https://community.theforeman.org/t/unmaintaned-incompatible-plugins-in-1-17-repos</a></p> Bug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/20050#change-1047532018-04-25T11:30:31ZJohannes Black
<p>Michael thanks for the information.</p>
<p>- Is there a documentation about which plugins won't work with Foreman 1.17 so the users don't have to try and error the plugins?<br />- Maybe it would be even more informative to hide options that won't work at the moment in foreman-installer so that there is no misunderstanding?</p> Bug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/20050#change-1047522018-04-25T11:26:05ZAnonymous
<p>Johannes, that problem with foreman_azure is unrelated. alias_method_chain was removed from Rails 5.x and Foreman 1.17 is using Rails 5.1, so foreman_zure is not compatible with 1.17+ at the moment.</p> Bug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/20050#change-1047502018-04-25T10:13:39ZJohannes Black
<p>[deleted. unrelated issue.]</p> Bug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/20050#change-1047382018-04-25T00:44:56ZTatsuya Hamamototatsuya@bhead.com
<p>Just wanted to report that the short-term solution worked for me. No errors what-so-ever.<br />Thank you very much!</p>