Please stabilize, thanks!
sparc done
We cannot mark this version stable without further investigation of already pending bundler issues. Not sure why you didn't follow normal process on this?
Keywords are not fully specified and arches are not CC-ed for the following packages: - =dev-ruby/bundler-2.2.18
(In reply to Hans de Graaff from comment #2) > We cannot mark this version stable without further investigation of already > pending bundler issues. What bugs, so we can depend on them here? > Not sure why you didn't follow normal process on this? I asked for stabilization in June, and got zero response. I don't see any obvious bugs open for bundler-2.2.18, so I went ahead with stabilization since we have a pending security bug.
(In reply to John Helmert III from comment #4) > (In reply to Hans de Graaff from comment #2) > > We cannot mark this version stable without further investigation of already > > pending bundler issues. > > What bugs, so we can depend on them here? > > > Not sure why you didn't follow normal process on this? > > I asked for stabilization in June, and got zero response. I don't see any > obvious bugs open for bundler-2.2.18, so I went ahead with stabilization > since we have a pending security bug. I'll try to sort this out this weekend.
(In reply to Hans de Graaff from comment #5) > I'll try to sort this out this weekend. Thanks!
Need 2.2.33 for newer bug.
It appears there is a 2.3.25 version, but portage only has 2.3.8-r1. Is there any point in targeting a newer version?
(In reply to Jack from comment #8) > It appears there is a 2.3.25 version, but portage only has 2.3.8-r1. Is > there any point in targeting a newer version? Yes, we need a fixed stable version. Ping ruby@.
(In reply to Jack from comment #8) > It appears there is a 2.3.25 version, but portage only has 2.3.8-r1. Is > there any point in targeting a newer version? Normally rubygems versions (to which bundler is now linked) match up with dev-lang/ruby versions, so I'd rather not just pick a newer version. Unfortunately I haven't made a lot of head-way with the issues mentioned earlier and I won't be able to work on this until next week.
Does this need a subject change or closing? 2.2.33-r1 is marked stable and there are 2.3 and 2.4 versions marked testing.
*** This bug has been marked as a duplicate of bug 890915 ***