dev-python/telepathy-python-0.15.18 is consistently failing to build on this system. Please see attached build log.
Created attachment 256863 [details] Build log
Same on my system, it fails on install after succesfully compiling. This happened after upgrading to python 2.7. On Python 2.6 it compiles fine.
Makefile.am is trying to install twice the same file (errors.py) this is a problem with newer autotools. Attached is a patch that solves the issue for me at least. Filed a bug upstream. R.
Created attachment 257618 [details, diff] remove double entry of erros.py from Makefile.am
Can we get this patch in the tree?
Please retry with 0.15.19
Still fails with it: /usr/bin/install: will not overwrite just-created `/var/tmp/portage/dev-python/telepathy-python-0.15.19/image//usr/lib64/python2.7/site-packages/telepathy/_generated/errors.py' with `_generated/errors.py'
(In reply to comment #3) > Makefile.am is trying to install twice the same file (errors.py) this is a > problem with newer autotools. Attached is a patch that solves the issue for me > at least. Filed a bug upstream. > > R. > What autotools version start to fail on this cases?
+ 08 Feb 2011; Pacho Ramos <pacho@gentoo.org> telepathy-python-0.15.19.ebuild, + +files/telepathy-python-0.15.19-install-twice.patch: + Don't install errors.py twice as it fails (bug #348386 by Jonathan Callen and + patch by Reimundo Heluani). +
The patch has been applied to git master upstream ( https://bugs.freedesktop.org//show_bug.cgi?id=32526 ) don't know in which version it got released... R.
(In reply to comment #10) > The patch has been applied to git master upstream ( > https://bugs.freedesktop.org//show_bug.cgi?id=32526 ) don't know in which > version it got released... > > R. > The patch hasn't been included upstream yet. The latest package (0.15.19) is dated December 3rd. This said, it shouldn't make a difference as long as we apply the patch through portage, but - although the patch applies correctly - install still fails because of the same problem.
Not sure which autotools update did the damage on my system, but I'm running sys-devel/automake-1.11.1 and sys-devel/autoconf-2.68 and the patch allows me to install the package dev-python/telepathy-python-0.15.18 without trouble. Haven't tried yet with 0.15.19.
Just checked with 0.15.19 and it installs fine on my system.
(In reply to comment #12) > Not sure which autotools update did the damage on my system, but I'm running > sys-devel/automake-1.11.1 and sys-devel/autoconf-2.68 and the patch allows me > to install the package dev-python/telepathy-python-0.15.18 without trouble. > Haven't tried yet with 0.15.19. > Same automake and autoconf as you, 0.15.18 installs fine *without* the patch (it's not in the ebuild and I didn't apply it manually). Like I said, 0.15.19 fails to install *despite* the patch.
(In reply to comment #14) > (In reply to comment #12) > > Not sure which autotools update did the damage on my system, but I'm running > > sys-devel/automake-1.11.1 and sys-devel/autoconf-2.68 and the patch allows me > > to install the package dev-python/telepathy-python-0.15.18 without trouble. > > Haven't tried yet with 0.15.19. > > > > Same automake and autoconf as you, 0.15.18 installs fine *without* the patch > (it's not in the ebuild and I didn't apply it manually). Like I said, 0.15.19 > fails to install *despite* the patch. > I have only those versions in portage, and neither installs for me =[
