On Tue, 11 Apr 2017 04:17:31 +0700 "Vadim A. Misbakh-Soloviov" <gen...@mva.name> wrote:
> Also, > > > Its an update issue. You set a target to say Ruby 24. But something > > wants Ruby23. It could be it only builds with ruby23. Or more than > > likely no one has gotten around to adding it to the package. Since > > for every new version. EVERY ebuild must be touched. > > As I said above, this only happens if package manintainer is a > slacker and a package wasn't touched for years. > > Chances that it will work with new ruby is... about 0%. Why should > you auto- add modern ruby targets for it then? See my other post where I talk about recent breakage that did not exist a month ago. When I was updating jruby for spring-context. Which a month later ends up preventing nightly builds on my build server. In fact I spent several hours yesterday trying to deal with the recent Ruby situation. After days if it not building or being fixed in tree. Git commit shows ruby24 being added. Something must have been a dep that was ruby 23 thus it wanting to come back onto my systems, Despite having been gone for a month. I ended up masking < Ruby 24. That was a PITA. It kept dropping. Masked 23 it went down to 22, masked 22, it dropped to 21. Not to mention all the other headaches before I went to hard mask the package. -- William L. Thomson Jr.
