Foreman 1.0.0 RC2 RPM's are available
at http://yum.theforeman.org/development/
The install documentation in both locations has been updated in these two
locations:
http://theforeman.org/projects/foreman/wiki/RPM's_distribution_based_installation
(authoritative)
http://yum.theforeman.org/development/instructions.txt (will probably go
away soon)
I think the issue where rake db:migrate was not running on upgrades is
finally fixed and would be very much interested to here if people are still
having issues.
Hi Jason,
I've been getting the following error after I run su - foreman -s /bin/bash
-c /usr/share/foreman/extras/dbmigrate
Libvirt binding are missing - hypervisor management is disabled
DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated. Please use
::Rails.logger. (called from /usr/share/foreman/config/application.rb:11)
rake aborted!
Wonder if you have seen this error?
Thanks
Robert
···
On Sat, Jun 30, 2012 at 7:44 AM, Jason Montleon wrote:
Foreman 1.0.0 RC2 RPM’s are available at
http://yum.theforeman.org/development/
The install documentation in both locations has been updated in these two
locations:
RPM’s distribution based installation - Foreman
(authoritative)
http://yum.theforeman.org/development/instructions.txt (will probably go
away soon)
I think the issue where rake db:migrate was not running on upgrades is
finally fixed and would be very much interested to here if people are still
having issues.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/PJciFsXOqiAJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
Nevermind I fixed it by upgrading rubygem has_many_polymorphs 3.beta.
···
On Sat, Jun 30, 2012 at 2:06 PM, Robert Tsai wrote:
Hi Jason,
I’ve been getting the following error after I run su - foreman -s
/bin/bash -c /usr/share/foreman/extras/dbmigrate
Libvirt binding are missing - hypervisor management is disabled
DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated. Please use
::Rails.logger. (called from /usr/share/foreman/config/application.rb:11)
rake aborted!
Wonder if you have seen this error?
Thanks
Robert
On Sat, Jun 30, 2012 at 7:44 AM, Jason Montleon jason@montleon.comwrote:
Foreman 1.0.0 RC2 RPM’s are available at
http://yum.theforeman.org/development/
The install documentation in both locations has been updated in these two
locations:
RPM’s distribution based installation - Foreman
(authoritative)
http://yum.theforeman.org/development/instructions.txt (will probably go
away soon)
I think the issue where rake db:migrate was not running on upgrades is
finally fixed and would be very much interested to here if people are still
having issues.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/PJciFsXOqiAJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
Hi Robert,
Did you upgrade to foreman 1.0.0-0.3 without rubygem-has_many_polymorphs
being updated to 3.0.0.beta1-3 as a dependency? If so I may have an issue
with the rpm dependency on this package, though looking at it, I think it
should have been updated automatically. Or did you mean you had to manually
update to an even newer version?
Just looking looking for clarification so I can fix any issues with the
rpm's
Thanks!
···
On Saturday, June 30, 2012 6:19:55 PM UTC-4, Robert Tsai wrote:
>
> Nevermind I fixed it by upgrading rubygem has_many_polymorphs 3.beta.
>
>
>
> On Sat, Jun 30, 2012 at 2:06 PM, Robert Tsai wrote:
>
>> Hi Jason,
>>
>> I've been getting the following error after I run su - foreman -s
>> /bin/bash -c /usr/share/foreman/extras/dbmigrate
>>
>> Libvirt binding are missing - hypervisor management is disabled
>> DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated. Please use
>> ::Rails.logger. (called from /usr/share/foreman/config/application.rb:11)
>> rake aborted!
>>
>> Wonder if you have seen this error?
>>
>> Thanks
>> Robert
>>
>> On Sat, Jun 30, 2012 at 7:44 AM, Jason Montleon wrote:
>>
>>> Foreman 1.0.0 RC2 RPM's are available at
>>> http://yum.theforeman.org/development/
>>>
>>> The install documentation in both locations has been updated in these
>>> two locations:
>>>
>>> http://theforeman.org/projects/foreman/wiki/RPM's_distribution_based_installation
>>> (authoritative)
>>> http://yum.theforeman.org/development/instructions.txt (will probably
>>> go away soon)
>>>
>>> I think the issue where rake db:migrate was not running on upgrades is
>>> finally fixed and would be very much interested to here if people are still
>>> having issues.
>>>
>>>
>
Hi Jason,
I upgraded to foreman1.0.0-0.3 and it installed rubygem-has_many_polymorphs
3.0.0.beta1-3. The problem was that there was still the older version of
rubygem-has_many_polymorphs 2.x. To solve that issue I just edited the
/usr/share/foreman/Gemfile with gem "has_many_polymorphs", '3.0.0.beta1'.
After that I stopped geting the "DEPRECATION WARNING: RAILS_DEFAULT_LOGGER
is deprecated" error. Hope that helped. I did, however, start up another
instance from scratch and had no problems installing foreman from your
guide. Hope that helps and Thanks for the easy installer guide!!
-Robert
···
On Sun, Jul 1, 2012 at 2:25 AM, Jason Montleon wrote:
Hi Robert,
Did you upgrade to foreman 1.0.0-0.3 without rubygem-has_many_polymorphs
being updated to 3.0.0.beta1-3 as a dependency? If so I may have an issue
with the rpm dependency on this package, though looking at it, I think it
should have been updated automatically. Or did you mean you had to manually
update to an even newer version?
Just looking looking for clarification so I can fix any issues with the
rpm’s
Thanks!
On Saturday, June 30, 2012 6:19:55 PM UTC-4, Robert Tsai wrote:
Nevermind I fixed it by upgrading rubygem has_many_polymorphs 3.beta.
On Sat, Jun 30, 2012 at 2:06 PM, Robert Tsai wrote:
Hi Jason,
I’ve been getting the following error after I run su - foreman -s
/bin/bash -c /usr/share/foreman/extras/**dbmigrate
Libvirt binding are missing - hypervisor management is disabled
DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated. Please use
::Rails.logger. (called from /usr/share/foreman/config/**
application.rb:11)
rake aborted!
Wonder if you have seen this error?
Thanks
Robert
On Sat, Jun 30, 2012 at 7:44 AM, Jason Montleon wrote:
Foreman 1.0.0 RC2 RPM’s are available at http://yum.theforeman.org/**
development/ http://yum.theforeman.org/development/
The install documentation in both locations has been updated in these
two locations:
http://theforeman.org/projects/foreman/wiki/RPM’s_
distribution_based_**installationhttp://theforeman.org/projects/foreman/wiki/RPM’s_distribution_based_installation
(authoritative)
http://yum.theforeman.org/**development/instructions.txthttp://yum.theforeman.org/development/instructions.txt
(**will probably go away soon)
I think the issue where rake db:migrate was not running on upgrades is
finally fixed and would be very much interested to here if people are still
having issues.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/kC3YPI5uYEQJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
> Hi Jason,
>
> I upgraded to foreman1.0.0-0.3 and it installed
> rubygem-has_many_polymorphs 3.0.0.beta1-3. The problem was that there was
> still the older version of rubygem-has_many_polymorphs 2.x. To solve that
> issue I just edited the /usr/share/foreman/Gemfile with gem
> "has_many_polymorphs", '3.0.0.beta1'. After that I stopped geting the
> "DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated" error. Hope that
> helped. I did, however, start up another instance from scratch and had no
> problems installing foreman from your guide. Hope that helps and Thanks
> for the easy installer guide!!
>
Oh, I wonder where you got that from… fur sure we need version 3.x, 2.x
wont work at all… any idea how it was installed first? was it via rpm
too?
Ohad
···
On Sun, Jul 1, 2012 at 6:42 PM, Robert Tsai wrote:
-Robert
On Sun, Jul 1, 2012 at 2:25 AM, Jason Montleon jason@montleon.com wrote:
Hi Robert,
Did you upgrade to foreman 1.0.0-0.3 without rubygem-has_many_polymorphs
being updated to 3.0.0.beta1-3 as a dependency? If so I may have an issue
with the rpm dependency on this package, though looking at it, I think it
should have been updated automatically. Or did you mean you had to manually
update to an even newer version?
Just looking looking for clarification so I can fix any issues with the
rpm’s
Thanks!
On Saturday, June 30, 2012 6:19:55 PM UTC-4, Robert Tsai wrote:
Nevermind I fixed it by upgrading rubygem has_many_polymorphs 3.beta.
On Sat, Jun 30, 2012 at 2:06 PM, Robert Tsai wrote:
Hi Jason,
I’ve been getting the following error after I run su - foreman -s
/bin/bash -c /usr/share/foreman/extras/**dbmigrate
Libvirt binding are missing - hypervisor management is disabled
DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated. Please use
::Rails.logger. (called from /usr/share/foreman/config/**
application.rb:11)
rake aborted!
Wonder if you have seen this error?
Thanks
Robert
On Sat, Jun 30, 2012 at 7:44 AM, Jason Montleon wrote:
Foreman 1.0.0 RC2 RPM’s are available at http://yum.theforeman.org/**
development/ http://yum.theforeman.org/development/
The install documentation in both locations has been updated in these
two locations:
http://theforeman.org/projects/foreman/wiki/RPM’s_
distribution_based_**installationhttp://theforeman.org/projects/foreman/wiki/RPM’s_distribution_based_installation
(authoritative)
http://yum.theforeman.org/**development/instructions.txthttp://yum.theforeman.org/development/instructions.txt
(**will probably go away soon)
I think the issue where rake db:migrate was not running on upgrades is
finally fixed and would be very much interested to here if people are still
having issues.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/kC3YPI5uYEQJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
Hi Ohad,
The first install was done a while back, must have been thru rpm install.
-Robert
···
On Sun, Jul 1, 2012 at 10:00 AM, Ohad Levy wrote:
On Sun, Jul 1, 2012 at 6:42 PM, Robert Tsai rtsai.mobile@gmail.comwrote:
Hi Jason,
I upgraded to foreman1.0.0-0.3 and it installed
rubygem-has_many_polymorphs 3.0.0.beta1-3. The problem was that there was
still the older version of rubygem-has_many_polymorphs 2.x. To solve that
issue I just edited the /usr/share/foreman/Gemfile with gem
"has_many_polymorphs", ‘3.0.0.beta1’. After that I stopped geting the
"DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated" error. Hope that
helped. I did, however, start up another instance from scratch and had no
problems installing foreman from your guide. Hope that helps and Thanks
for the easy installer guide!!
Oh, I wonder where you got that from… fur sure we need version 3.x, 2.x
wont work at all… any idea how it was installed first? was it via rpm
too?
Ohad
-Robert
On Sun, Jul 1, 2012 at 2:25 AM, Jason Montleon jason@montleon.comwrote:
Hi Robert,
Did you upgrade to foreman 1.0.0-0.3 without rubygem-has_many_polymorphs
being updated to 3.0.0.beta1-3 as a dependency? If so I may have an issue
with the rpm dependency on this package, though looking at it, I think it
should have been updated automatically. Or did you mean you had to manually
update to an even newer version?
Just looking looking for clarification so I can fix any issues with the
rpm’s
Thanks!
On Saturday, June 30, 2012 6:19:55 PM UTC-4, Robert Tsai wrote:
Nevermind I fixed it by upgrading rubygem has_many_polymorphs 3.beta.
On Sat, Jun 30, 2012 at 2:06 PM, Robert Tsai wrote:
Hi Jason,
I’ve been getting the following error after I run su - foreman -s
/bin/bash -c /usr/share/foreman/extras/**dbmigrate
Libvirt binding are missing - hypervisor management is disabled
DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated. Please use
::Rails.logger. (called from /usr/share/foreman/config/**
application.rb:11)
rake aborted!
Wonder if you have seen this error?
Thanks
Robert
On Sat, Jun 30, 2012 at 7:44 AM, Jason Montleon wrote:
Foreman 1.0.0 RC2 RPM’s are available at http://yum.theforeman.org/**
development/ http://yum.theforeman.org/development/
The install documentation in both locations has been updated in these
two locations:
http://theforeman.org/projects/foreman/wiki/RPM’s_
distribution_based_**installationhttp://theforeman.org/projects/foreman/wiki/RPM’s_distribution_based_installation
(authoritative)
http://yum.theforeman.org/**development/instructions.txthttp://yum.theforeman.org/development/instructions.txt
(**will probably go away soon)
I think the issue where rake db:migrate was not running on upgrades
is finally fixed and would be very much interested to here if people are
still having issues.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/kC3YPI5uYEQJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
I don't think there have ever been 2.x rpms. Not from me anyway 
···
On Sunday, July 1, 2012 4:39:39 PM UTC-4, Robert Tsai wrote:
>
> Hi Ohad,
>
> The first install was done a while back, must have been thru rpm install.
>
> -Robert
>
> On Sun, Jul 1, 2012 at 10:00 AM, Ohad Levy wrote:
>
>>
>>
>> On Sun, Jul 1, 2012 at 6:42 PM, Robert Tsai wrote:
>>
>>> Hi Jason,
>>>
>>> I upgraded to foreman1.0.0-0.3 and it installed
>>> rubygem-has_many_polymorphs 3.0.0.beta1-3. The problem was that there was
>>> still the older version of rubygem-has_many_polymorphs 2.x. To solve that
>>> issue I just edited the /usr/share/foreman/Gemfile with gem
>>> "has_many_polymorphs", '3.0.0.beta1'. After that I stopped geting the
>>> "DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated" error. Hope that
>>> helped. I did, however, start up another instance from scratch and had no
>>> problems installing foreman from your guide. Hope that helps and Thanks
>>> for the easy installer guide!!
>>>
>>
>> Oh, I wonder where you got that from.. fur sure we need version 3.x, 2.x
>> wont work at all.... any idea how it was installed first? was it via rpm
>> too?
>>
>> Ohad
>>
>>>
>>> -Robert
>>>
>>>
>>> On Sun, Jul 1, 2012 at 2:25 AM, Jason Montleon wrote:
>>>
>>>> Hi Robert,
>>>> Did you upgrade to foreman 1.0.0-0.3 without
>>>> rubygem-has_many_polymorphs being updated to 3.0.0.beta1-3 as a dependency?
>>>> If so I may have an issue with the rpm dependency on this package, though
>>>> looking at it, I think it should have been updated automatically. Or did
>>>> you mean you had to manually update to an even newer version?
>>>>
>>>> Just looking looking for clarification so I can fix any issues with the
>>>> rpm's
>>>>
>>>> Thanks!
>>>>
>>>> On Saturday, June 30, 2012 6:19:55 PM UTC-4, Robert Tsai wrote:
>>>>
>>>>> Nevermind I fixed it by upgrading rubygem has_many_polymorphs 3.beta.
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Jun 30, 2012 at 2:06 PM, Robert Tsai wrote:
>>>>>
>>>>>> Hi Jason,
>>>>>>
>>>>>> I've been getting the following error after I run su - foreman -s
>>>>>> /bin/bash -c /usr/share/foreman/extras/**dbmigrate
>>>>>>
>>>>>> Libvirt binding are missing - hypervisor management is disabled
>>>>>> DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated. Please use
>>>>>> ::Rails.logger. (called from /usr/share/foreman/config/**
>>>>>> application.rb:11)
>>>>>> rake aborted!
>>>>>>
>>>>>> Wonder if you have seen this error?
>>>>>>
>>>>>> Thanks
>>>>>> Robert
>>>>>>
>>>>>> On Sat, Jun 30, 2012 at 7:44 AM, Jason Montleon wrote:
>>>>>>
>>>>>> Foreman 1.0.0 RC2 RPM's are available at http://yum.theforeman.org/**
>>>>>>> development/
>>>>>>>
>>>>>>> The install documentation in both locations has been updated in
>>>>>>> these two locations:
>>>>>>> http://theforeman.org/**projects/foreman/wiki/RPM's_**
>>>>>>> distribution_based_**installation
>>>>>>> (authoritative)
>>>>>>> http://yum.theforeman.org/**development/instructions.txt
>>>>>>> (**will probably go away soon)
>>>>>>>
>>>>>>> I think the issue where rake db:migrate was not running on upgrades
>>>>>>> is finally fixed and would be very much interested to here if people are
>>>>>>> still having issues.
>>>>>>>
>>>>>>>
>>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Foreman users" group.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msg/foreman-users/-/kC3YPI5uYEQJ.
>>>>
>>>> To post to this group, send email to foreman-users@googlegroups.com.
>>>> To unsubscribe from this group, send email to
>>>> foreman-users+unsubscribe@googlegroups.com.
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/foreman-users?hl=en.
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Foreman users" group.
>>> To post to this group, send email to foreman-users@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> foreman-users+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/foreman-users?hl=en.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> foreman-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
>
> I don't think there have ever been 2.x rpms. Not from me anyway
>
> Robert, did you install using RPM's all along?
Anyone else had issues upgrading from 0.4 to 1.0RC rpms?
thanks
Ohad
···
On Mon, Jul 2, 2012 at 4:53 AM, Jason Montleon wrote:
On Sunday, July 1, 2012 4:39:39 PM UTC-4, Robert Tsai wrote:
Hi Ohad,
The first install was done a while back, must have been thru rpm install.
-Robert
On Sun, Jul 1, 2012 at 10:00 AM, Ohad Levy ohadlevy@gmail.com wrote:
On Sun, Jul 1, 2012 at 6:42 PM, Robert Tsai rtsai.mobile@gmail.comwrote:
Hi Jason,
I upgraded to foreman1.0.0-0.3 and it installed
rubygem-has_many_polymorphs 3.0.0.beta1-3. The problem was that there was
still the older version of rubygem-has_many_polymorphs 2.x. To solve that
issue I just edited the /usr/share/foreman/Gemfile with gem
"has_many_polymorphs", ‘3.0.0.beta1’. After that I stopped geting the
"DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated" error. Hope that
helped. I did, however, start up another instance from scratch and had no
problems installing foreman from your guide. Hope that helps and Thanks
for the easy installer guide!!
Oh, I wonder where you got that from… fur sure we need version 3.x, 2.x
wont work at all… any idea how it was installed first? was it via rpm
too?
Ohad
-Robert
On Sun, Jul 1, 2012 at 2:25 AM, Jason Montleon jason@montleon.comwrote:
Hi Robert,
Did you upgrade to foreman 1.0.0-0.3 without
rubygem-has_many_polymorphs being updated to 3.0.0.beta1-3 as a dependency?
If so I may have an issue with the rpm dependency on this package, though
looking at it, I think it should have been updated automatically. Or did
you mean you had to manually update to an even newer version?
Just looking looking for clarification so I can fix any issues with
the rpm’s
Thanks!
On Saturday, June 30, 2012 6:19:55 PM UTC-4, Robert Tsai wrote:
Nevermind I fixed it by upgrading rubygem has_many_polymorphs 3.beta.
On Sat, Jun 30, 2012 at 2:06 PM, Robert Tsai wrote:
Hi Jason,
I’ve been getting the following error after I run su - foreman -s
/bin/bash -c /usr/share/foreman/extras/dbmigrate
Libvirt binding are missing - hypervisor management is disabled
DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated. Please use
::Rails.logger. (called from /usr/share/foreman/config/appl
ication.rb:11)
rake aborted!
Wonder if you have seen this error?
Thanks
Robert
On Sat, Jun 30, 2012 at 7:44 AM, Jason Montleon wrote:
Foreman 1.0.0 RC2 RPM’s are available at http://yum.theforeman.org/*
*d**evelopment/ http://yum.theforeman.org/development/
The install documentation in both locations has been updated in
these two locations:
http://theforeman.org/projects/foreman/wiki/RPM’s_*distributi
*on_based_**installationhttp://theforeman.org/projects/foreman/wiki/RPM’s_distribution_based_installation
(**authoritative)
http://yum.theforeman.org/development/instructions.txthttp://yum.theforeman.org/development/instructions.txt
(**will probably go away soon)
I think the issue where rake db:migrate was not running on upgrades
is finally fixed and would be very much interested to here if people are
still having issues.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To view this discussion on the web visit https://groups.google.com/d/*
*msg/foreman-users/-/**kC3YPI5uYEQJhttps://groups.google.com/d/msg/foreman-users/-/kC3YPI5uYEQJ
.
To post to this group, send email to foreman-users@googlegroups.com**.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at http://groups.google.com/
group/foreman-users?hl=enhttp://groups.google.com/group/foreman-users?hl=en
.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com**.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at http://groups.google.com/
group/foreman-users?hl=enhttp://groups.google.com/group/foreman-users?hl=en
.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com**.
To unsubscribe from this group, send email to foreman-users+unsubscribe@
googlegroups.com foreman-users%2Bunsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/
group/foreman-users?hl=enhttp://groups.google.com/group/foreman-users?hl=en
.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/51dBiRKzCLAJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
Do you have a rubygem-rdoc rpm already installed? If so can you do rpm -qi
rubygem-rdoc? 3.12 is in the Foreman Development repo and it normally
installs automatically.
http://yum.theforeman.org/development/el6/x86_64/rubygem-rdoc-3.12-2.el6.x86_64.rpm
It is possible you have an older version with an Epoch set, but the errors
below don't look like that is the case, so I am not exactly sure why this
is happening.
Also, make sure you didn't grab the foreman-release package for Fedora 17
by accident, as that repo does not have rubygem-rdoc because it comes with
Fedora 17.
···
On Monday, July 2, 2012 9:21:09 AM UTC-4, Paradoxbound wrote:
>
> On 2 July 2012 14:14, James Bailey wrote:
> > On 2 July 2012 13:31, Ohad Levy wrote:
> >>
> >>
> >> On Mon, Jul 2, 2012 at 4:53 AM, Jason Montleon > wrote:
> >>>
> >>> I don't think there have ever been 2.x rpms. Not from me anyway :)
> >>>
> >> Robert, did you install using RPM's all along?
> >>
> >> Anyone else had issues upgrading from 0.4 to 1.0RC rpms?
> >
> > I am getting the following error
> >
> > Error: Package: rubygem-railties-3.0.15-1.el6.noarch (foreman)
> > Requires: rubygem-rdoc >= 3.4
> > Error: Package: rubygem-railties-3.0.15-1.el6.noarch (foreman)
> > Requires: rubygem-rdoc < 4
> > You could try using --skip-broken to work around the problem
> > You could try running: rpm -Va --nofiles --nodigest
>
> Sorry I forgot to add this is CentOS-6 with the development repo enabled.
>
> Jim
>
>
>
>>
>> I don't think there have ever been 2.x rpms. Not from me anyway
>>
> Robert, did you install using RPM's all along?
>
> Anyone else had issues upgrading from 0.4 to 1.0RC rpms?
I am getting the following error
Error: Package: rubygem-railties-3.0.15-1.el6.noarch (foreman)
Requires: rubygem-rdoc >= 3.4
Error: Package: rubygem-railties-3.0.15-1.el6.noarch (foreman)
Requires: rubygem-rdoc < 4
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Jim
···
On 2 July 2012 13:31, Ohad Levy wrote:
> On Mon, Jul 2, 2012 at 4:53 AM, Jason Montleon wrote:
thanks
Ohad
On Sunday, July 1, 2012 4:39:39 PM UTC-4, Robert Tsai wrote:
Hi Ohad,
The first install was done a while back, must have been thru rpm install.
-Robert
On Sun, Jul 1, 2012 at 10:00 AM, Ohad Levy ohadlevy@gmail.com wrote:
On Sun, Jul 1, 2012 at 6:42 PM, Robert Tsai rtsai.mobile@gmail.com >>>> wrote:
Hi Jason,
I upgraded to foreman1.0.0-0.3 and it installed
rubygem-has_many_polymorphs 3.0.0.beta1-3. The problem was that there was
still the older version of rubygem-has_many_polymorphs 2.x. To solve that
issue I just edited the /usr/share/foreman/Gemfile with gem
"has_many_polymorphs", ‘3.0.0.beta1’. After that I stopped geting the
"DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated" error. Hope that
helped. I did, however, start up another instance from scratch and had no
problems installing foreman from your guide. Hope that helps and Thanks for
the easy installer guide!!
Oh, I wonder where you got that from… fur sure we need version 3.x, 2.x
wont work at all… any idea how it was installed first? was it via rpm
too?
Ohad
-Robert
On Sun, Jul 1, 2012 at 2:25 AM, Jason Montleon jason@montleon.com >>>>> wrote:
Hi Robert,
Did you upgrade to foreman 1.0.0-0.3 without
rubygem-has_many_polymorphs being updated to 3.0.0.beta1-3 as a dependency?
If so I may have an issue with the rpm dependency on this package, though
looking at it, I think it should have been updated automatically. Or did you
mean you had to manually update to an even newer version?
Just looking looking for clarification so I can fix any issues with
the rpm’s
Thanks!
On Saturday, June 30, 2012 6:19:55 PM UTC-4, Robert Tsai wrote:
Nevermind I fixed it by upgrading rubygem has_many_polymorphs 3.beta.
On Sat, Jun 30, 2012 at 2:06 PM, Robert Tsai wrote:
Hi Jason,
I’ve been getting the following error after I run su - foreman -s
/bin/bash -c /usr/share/foreman/extras/dbmigrate
Libvirt binding are missing - hypervisor management is disabled
DEPRECATION WARNING: RAILS_DEFAULT_LOGGER is deprecated. Please use
::Rails.logger. (called from /usr/share/foreman/config/application.rb:11)
rake aborted!
Wonder if you have seen this error?
Thanks
Robert
On Sat, Jun 30, 2012 at 7:44 AM, Jason Montleon wrote:
Foreman 1.0.0 RC2 RPM’s are available
at http://yum.theforeman.org/development/
The install documentation in both locations has been updated in
these two locations:
RPM’s distribution based installation - Foreman (authoritative)
http://yum.theforeman.org/development/instructions.txt (will
probably go away soon)
I think the issue where rake db:migrate was not running on upgrades
is finally fixed and would be very much interested to here if people are
still having issues.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/kC3YPI5uYEQJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/51dBiRKzCLAJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
Sorry I forgot to add this is CentOS-6 with the development repo enabled.
Jim
···
On 2 July 2012 14:14, James Bailey wrote:
> On 2 July 2012 13:31, Ohad Levy wrote:
>>
>>
>> On Mon, Jul 2, 2012 at 4:53 AM, Jason Montleon wrote:
>>>
>>> I don't think there have ever been 2.x rpms. Not from me anyway :)
>>>
>> Robert, did you install using RPM's all along?
>>
>> Anyone else had issues upgrading from 0.4 to 1.0RC rpms?
>
> I am getting the following error
>
> Error: Package: rubygem-railties-3.0.15-1.el6.noarch (foreman)
> Requires: rubygem-rdoc >= 3.4
> Error: Package: rubygem-railties-3.0.15-1.el6.noarch (foreman)
> Requires: rubygem-rdoc < 4
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest
Are you using i386? I just built pacakges, though you'll have to fix the
foreman.repo file until next version:
http://yum.theforeman.org/development/el6/i386/
···
On Monday, July 2, 2012 9:21:09 AM UTC-4, Paradoxbound wrote:
>
> On 2 July 2012 14:14, James Bailey wrote:
> > On 2 July 2012 13:31, Ohad Levy wrote:
> >>
> >>
> >> On Mon, Jul 2, 2012 at 4:53 AM, Jason Montleon > wrote:
> >>>
> >>> I don't think there have ever been 2.x rpms. Not from me anyway :)
> >>>
> >> Robert, did you install using RPM's all along?
> >>
> >> Anyone else had issues upgrading from 0.4 to 1.0RC rpms?
> >
> > I am getting the following error
> >
> > Error: Package: rubygem-railties-3.0.15-1.el6.noarch (foreman)
> > Requires: rubygem-rdoc >= 3.4
> > Error: Package: rubygem-railties-3.0.15-1.el6.noarch (foreman)
> > Requires: rubygem-rdoc < 4
> > You could try using --skip-broken to work around the problem
> > You could try running: rpm -Va --nofiles --nodigest
>
> Sorry I forgot to add this is CentOS-6 with the development repo enabled.
>
> Jim
>
