Re: [gentoo-user] python-updater constantly rebuilds one same package

[Alan McKinnon]

On 14/08/2014 14:58, Сергей wrote:
> Sorry. Here is what I wanted to paste:
> sudo python-updater
>  * Starting Python Updater...
>  * Main active version of Python:    3.3
>  * Active version of Python 2:       2.7
>  * Active version of Python 3:       3.3
>  * Globally supported Python ABIs in installed repositories:
>  *   gentoo:                         2.4 2.5 2.6 2.7 3.1 3.2 3.3
> 2.5-jython 2.7-jython 2.7-pypy-1.7 2.7-pypy-1.8 2.7-pypy-1.9
> 2.7-pypy-2.0
>  *   kde:                            2.4 2.5 2.6 2.7 3.1 3.2 3.3
> 2.5-jython 2.7-jython 2.7-pypy-1.7 2.7-pypy-1.8 2.7-pypy-1.9
> 2.7-pypy-2.0
>  *   Adding to list: dev-libs/libgamin:0
>  * emerge -Dv1 --keep-going dev-libs/libgamin:0
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R    ] dev-libs/libgamin-0.1.10-r4  USE="-debug -python
> -static-libs" ABI_X86="(64) (-32) (-x32)" 0 kB
>
> Total: 1 package (1 reinstall), Size of downloads: 0 kB
>
>>>> Verifying ebuild manifests
>>>> Emerging (1 of 1) dev-libs/libgamin-0.1.10-r4
>>>> Installing (1 of 1) dev-libs/libgamin-0.1.10-r4
>>>> Jobs: 1 of 1 complete                           Load avg: 1.15, 0.72, 0.46
>>>> Auto-cleaning packages...
>
>>>> No outdated packages were found on your system.
>
>  * GNU info directory index is up-to-date.
> sergey@sergey-pc ~ % sudo python-updater
>  * Starting Python Updater...
>  * Main active version of Python:    3.3
>  * Active version of Python 2:       2.7
>  * Active version of Python 3:       3.3
>  * Globally supported Python ABIs in installed repositories:
>  *   gentoo:                         2.4 2.5 2.6 2.7 3.1 3.2 3.3
> 2.5-jython 2.7-jython 2.7-pypy-1.7 2.7-pypy-1.8 2.7-pypy-1.9
> 2.7-pypy-2.0
>  *   kde:                            2.4 2.5 2.6 2.7 3.1 3.2 3.3
> 2.5-jython 2.7-jython 2.7-pypy-1.7 2.7-pypy-1.8 2.7-pypy-1.9
> 2.7-pypy-2.0
>  *   Adding to list: dev-libs/libgamin:0
>  * emerge -Dv1 --keep-going dev-libs/libgamin:0
>
> As you can see, though libgamin was rebuilt, if I run python-updater
> once more it wants to rebuild it again.


These kinds of things are hard to fix, and even harder to figure out
what is going on. Behind the scenes, there's a lot of portage magic
involved to determine what depends on what, and what changed ABI so now
it's dependants must be rebuilt. But the tools often don't give enough
info (or too much!), so we have to resort to blunt weapons.

I find that this often works out:

revdep-rebuild, the python-updater again. If that doesn't fix it:

equery depends libgamin

then unmerge libgamin andthe packages that depend on it. Then emerge
them back with the -1 option (not an update world just in case there are
missing deps in ebuild)

Yes, it's a blunt weapon and probably overkill (sorta like rebooting
windows to fix every little thing), but without more info your choices
are limited





-- 
Alan McKinnon
alan.mckinnon@×××××.com