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