Please keyword activesupport-2.3.14-r1 stable. Changelog entry for the ebuild: 08 Dec 2011; Diego E. Pettenò <flameeyes@gentoo.org> +activesupport-2.3.14-r1.ebuild, +files/activesupport-2.3.14-unvendorize.patch, activesupport-3.0.11.ebuild: Fix specifications so that they can be used with bundler (required for radiant-1). Also add mocha to the list of test dependencies for 3.0, found while installing the wrong slot. My chiliproject ebuild (#374789) is another one depending on the use of bundler. Without the nice guys of chiliproject upstream I wouldn't even have known what the source of my problem is. For not having other people, which are trying to package ruby software, that is using bundler, running into this issue, I request to mark the fixed activesupport ebuild stable. In my case using a newer rails version isn't possible at the moment (looks like activesupport 3.0.3 no longer has any vendored code (#271147)). Upstream doesn't support it, yet. I assume this is the same with other ruby projects. Reproducible: Always Actual Results: rake aborted! builder is not part of the bundle. Add it to Gemfile. Expected Results: No error.
I'm fine with stabling this for now since it at least improves the current situation, but please be aware that Rails 2.3.x has known security issues, and the only reason it isn't masked yet is that we are still in the process of getting a Rails 3.x version stable.
(In reply to comment #1) > please be aware that Rails 2.3.x has known security issues, > and the only reason it isn't masked yet is that we are still in the process > of getting a Rails 3.x version stable. In the case of chiliproject the security fixes were backported. Of course I don't know it for other projects depending on Rails 2.3.x.
@graaff: * QA Notice: Your patch uses relative paths '../'. * In the future this will cause a failure.
amd64 stable
x86 stable
ppc stable
ppc64 done; closing as last arch