[gentoo-dev] Re: Re: Changes in installed ebuilds

["Jörg Schaible" <joerg.schaible@gmx.de>]

hasufell wrote:

> 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.


The dependency calculation worked perfectly, it just could not resolve them 
anymore, because those suddenly required newer packages are hard masked on  
my system to keep the software *I* need for my daily work running.


> Revbumping and restabilizing all of these packages (a LOT) would have
> been unrealistic.


And the question was, why was the version for these deps upgraded in those 
ebuild at all. The official tree did not contain anything older anyway.

 
> 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.


That's what I did in the end for all "bumped" ebuilds, but the effort would 
not have been necessary at all.

- Jörg