Re: [gentoo-user] python-updater constantly rebuilds one same package
On Thursday 14 August 2014 17:23:51 Mike Gilbert wrote: I have not run revdep-rebuild in over a year. If you have seen that preserve-libs is missing things, that's a a bug. Several people found that preserve-libs missed qtsql recently. The conversation's in the akonadi ... don't you just love it? thread. -- Regards Peter
Re: [gentoo-user] python-updater constantly rebuilds one same package
On 14/08/2014 13:38, Сергей wrote: http://pastebin.com/L3qxu460 Is it the way how python-updater should work? Seems a bit strange Please don't use pastebin. People here hate the bloody things. Just paste the relevant output into your mail. This list is archived so one week from now anyone can still help you. With pastebin, they can't. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] python-updater constantly rebuilds one same package
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.mckin...@gmail.com
Re: [gentoo-user] python-updater constantly rebuilds one same package
On 14/08/2014 16:35, Сергей wrote: kdelibs and glib depend on virtual/fam provided by gamin, so I don't think removing them all is a good idea. revdep-rebuild didn't help. Maaagic ~~ I see. OK, lets try identify why python-updater thinks libgamin needs updating: python--updater -p -v -v and search the output (it's long...) -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] python-updater constantly rebuilds one same package
On Thu, Aug 14, 2014 at 11:57 AM, Сергей protsero...@gmail.com wrote: I have looked at dev-libs/libgamin-0.1.10-r4 and dev-libs/libgamin-0.1.10-r5 ebuilds and compared them. dev-libs/libgamin-0.1.10-r5 has PYTHON_TARGETS=python2_7 (r4 had no PYTHON_TARGETS) and now python-updater doesn't rebuild libgamin. Seems like now everything is ok and it was only a portage bug. It is actually a bug with python-updater. However, we have no plans to fix it; instead, the problem will be resolved once all python-based ebuilds are migrated to python-r1.eclass and therefore utilize PYTHON_TARGETS. At that point, python-updater will become obsolete and you will no longer need to run it.
Re: [gentoo-user] python-updater constantly rebuilds one same package
On Thu 14 Aug 2014 11:57:53 AM EDT, Сергей wrote: I have looked at dev-libs/libgamin-0.1.10-r4 and dev-libs/libgamin-0.1.10-r5 ebuilds and compared them. dev-libs/libgamin-0.1.10-r5 has PYTHON_TARGETS=python2_7 (r4 had no PYTHON_TARGETS) and now python-updater doesn't rebuild libgamin. Seems like now everything is ok and it was only a portage bug. I've actually never run python-updater before; now running it twice it tries to rebuild dev-libs/stfl both times. I checked the ebuild; there's no PYTHON_TARGETS at all (and 0.22-r1 is the only ebuild in my local tree right now), but the error is * Checking dev-libs/stfl-0.22-r1:0 * Adding to list: dev-libs/stfl:0 * check: PYTHON_ABIS [ Previous Python ABIs: , new Python ABIs: 2.7 3.3 ] Not sure if this is a bug or not (and personally I don't really care, not gonna run python-updater until stuff breaks like crazy), but for any developers out there it might be important to take note? I can attach any relevant logs if necessary. Alec
Re: [gentoo-user] python-updater constantly rebuilds one same package
On 14/08/2014 18:09, Mike Gilbert wrote: On Thu, Aug 14, 2014 at 11:57 AM, Сергей protsero...@gmail.com wrote: I have looked at dev-libs/libgamin-0.1.10-r4 and dev-libs/libgamin-0.1.10-r5 ebuilds and compared them. dev-libs/libgamin-0.1.10-r5 has PYTHON_TARGETS=python2_7 (r4 had no PYTHON_TARGETS) and now python-updater doesn't rebuild libgamin. Seems like now everything is ok and it was only a portage bug. It is actually a bug with python-updater. However, we have no plans to fix it; instead, the problem will be resolved once all python-based ebuilds are migrated to python-r1.eclass and therefore utilize PYTHON_TARGETS. At that point, python-updater will become obsolete and you will no longer need to run it. Um, yeah. That's what they said about revdep-rebuild when @preserved-rebuild hit. And then again when sub-slots hit. But revdep-rebuild to this day still catches things both of those solutions missed. In Gentoo-land I have learned to be extremely wary of any statement like old xyz tool is no longer necessary :-) It seems like the 98%-2% rule is still very much in play -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] python-updater constantly rebuilds one same package
On Thu, Aug 14, 2014 at 2:26 PM, Alan McKinnon alan.mckin...@gmail.com wrote: On 14/08/2014 18:09, Mike Gilbert wrote: On Thu, Aug 14, 2014 at 11:57 AM, Сергей protsero...@gmail.com wrote: I have looked at dev-libs/libgamin-0.1.10-r4 and dev-libs/libgamin-0.1.10-r5 ebuilds and compared them. dev-libs/libgamin-0.1.10-r5 has PYTHON_TARGETS=python2_7 (r4 had no PYTHON_TARGETS) and now python-updater doesn't rebuild libgamin. Seems like now everything is ok and it was only a portage bug. It is actually a bug with python-updater. However, we have no plans to fix it; instead, the problem will be resolved once all python-based ebuilds are migrated to python-r1.eclass and therefore utilize PYTHON_TARGETS. At that point, python-updater will become obsolete and you will no longer need to run it. Um, yeah. That's what they said about revdep-rebuild when @preserved-rebuild hit. And then again when sub-slots hit. But revdep-rebuild to this day still catches things both of those solutions missed. In Gentoo-land I have learned to be extremely wary of any statement like old xyz tool is no longer necessary :-) It seems like the 98%-2% rule is still very much in play I have not run revdep-rebuild in over a year. If you have seen that preserve-libs is missing things, that's a a bug. Slot-operators are going to take a LONG time to get implemented tree-wide, and I agree that it may never happen. Packages which utilize PYTHON_TARGETS do not get rebuilt by python-updater anyway -- it explicitly skips them. At this point, the majority of packages that people actually use have been converted. Many users may not even need to run python-updater if they don't have USE=python enabled globally.
Re: [gentoo-user] python-updater constantly rebuilds one same package
On 14/08/2014 23:23, Mike Gilbert wrote: On Thu, Aug 14, 2014 at 2:26 PM, Alan McKinnon alan.mckin...@gmail.com wrote: On 14/08/2014 18:09, Mike Gilbert wrote: On Thu, Aug 14, 2014 at 11:57 AM, Сергей protsero...@gmail.com wrote: I have looked at dev-libs/libgamin-0.1.10-r4 and dev-libs/libgamin-0.1.10-r5 ebuilds and compared them. dev-libs/libgamin-0.1.10-r5 has PYTHON_TARGETS=python2_7 (r4 had no PYTHON_TARGETS) and now python-updater doesn't rebuild libgamin. Seems like now everything is ok and it was only a portage bug. It is actually a bug with python-updater. However, we have no plans to fix it; instead, the problem will be resolved once all python-based ebuilds are migrated to python-r1.eclass and therefore utilize PYTHON_TARGETS. At that point, python-updater will become obsolete and you will no longer need to run it. Um, yeah. That's what they said about revdep-rebuild when @preserved-rebuild hit. And then again when sub-slots hit. But revdep-rebuild to this day still catches things both of those solutions missed. In Gentoo-land I have learned to be extremely wary of any statement like old xyz tool is no longer necessary :-) It seems like the 98%-2% rule is still very much in play I have not run revdep-rebuild in over a year. If you have seen that preserve-libs is missing things, that's a a bug. Slot-operators are going to take a LONG time to get implemented tree-wide, and I agree that it may never happen. Packages which utilize PYTHON_TARGETS do not get rebuilt by python-updater anyway -- it explicitly skips them. At this point, the majority of packages that people actually use have been converted. Many users may not even need to run python-updater if they don't have USE=python enabled globally. That's good to know - I wasn't aware that python-updater did that. -- Alan McKinnon alan.mckin...@gmail.com
