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