facter-1.5.7 is the latest stable release upstream, in portage since 01/2010 with some fixes in -r1 and portage-specific fixes in -r2. It is working on my systems (amd64 and hppa) and correctly reports information about these environment: - amd64 physical - amd64 xen domU - hppa linux-vserver host - hppa linux-vserver guest please stable it if there isn't any problem
dev-ruby/facter-1.5.7-r2 cannot be stabilized yet because it has not yet been in portage long enough and because it depends on ruby implementations that are masked or only available as testing. We could change the bug to request stabilization of -r1 now, or we could wait until -r2 is ready.
As far as I'm concerned, -r1 would be perfectly ok. I just recently started to deploy puppet (depends on facter) on my systems and I'd like to bring Gentoo Portage on par with upstream stable releases.
I switched all of my systems (amd64 and hppa) to facter-1.5.7-r1 in July, it is working perfectly for me. facter-1.5.7 was released by upstream as stable version in Sep 2009, the -r1 ebuild is in portage since 21 Mar 2010. I changed this bug as suggested by Hans, please stable it if there isn't any showstopper I'm not aware of. (side note: 1.5.8 has been released two days ago, I'll open another BR to ask for version bump)
(In reply to comment #3) > (side note: 1.5.8 has been released two days ago, I'll open another BR to ask > for version bump) Added to CVS this weekend. Note that in general bugs are not needed for this: http://www.gentoo.org/proj/en/prog_lang/ruby/index.xml (bottom)
@Matsuu: any reason not to stable a newer version? The currently stable versions still depend on deprecated ruby.eclass and I would like to get rid of those versions.
facter 1.6.0 is now stable.