1 |
Jörg Schaible: |
2 |
> Alexandre Rostovtsev wrote: |
3 |
> |
4 |
>> On Mon, 2014-06-23 at 22:15 +0200, Jörg Schaible wrote: |
5 |
>>> So, why the heck, was the dependency to dev-libs/glib changed for an |
6 |
>>> existing ebuild without increasing its version (e.g. |
7 |
>>> dbus-glib-0.100.2-r2)? |
8 |
>> |
9 |
>> Please see http://article.gmane.org/gmane.linux.gentoo.devel/91615 |
10 |
> |
11 |
> These blocks had nothing to do with the multilibs ABI. It has been just the |
12 |
> updated versions for the dependencies. |
13 |
> |
14 |
|
15 |
I'm not sure if you understood the bug. It was breaking dependency |
16 |
calculation of portage, so the fallout you see is minor to what was |
17 |
going on. |
18 |
|
19 |
Revbumping and restabilizing all of these packages (a LOT) would have |
20 |
been unrealistic. |
21 |
|
22 |
Another possibility would have been to revbump the ebuild and make it |
23 |
instantly stable without arch teams involvement. That would actually be |
24 |
the cleaner way, but afair some people don't agree with that, so it |
25 |
isn't standard practice. |
26 |
|
27 |
However, you can still overwrite tree ebuilds in your local overlay and |
28 |
revert dependencies. I once did that with pypy, because it triggered too |
29 |
many rebuilds for me. |