Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#40276 - [pygobject] build fails
Attached to Project:
Arch Linux
Opened by Joel Teichroeb (klusark) - Friday, 09 May 2014, 00:31 GMT
Last edited by Jan de Groot (JGC) - Thursday, 29 May 2014, 09:55 GMT
Opened by Joel Teichroeb (klusark) - Friday, 09 May 2014, 00:31 GMT
Last edited by Jan de Groot (JGC) - Thursday, 29 May 2014, 09:55 GMT
|
DetailsDescription:
==> Retrieving sources... -> Found pygobject-3.12.1.tar.xz ==> Validating source files with sha256sums... pygobject-3.12.1.tar.xz ... Passed ==> Extracting sources... -> Extracting pygobject-3.12.1.tar.xz with bsdtar ==> Starting prepare()... ==> Starting build()... lcov not installed, not enabling code coverage /usr/bin/gnome-autogen.sh ==> ERROR: A failure occurred in build(). Aborting... Steps to reproduce: sudo extra-x86_64-build |
This task depends upon
Comment by Doug Newgard (Scimmia) -
Friday, 09 May 2014, 04:10 GMT
Can't reproduce, builds fine here. I get the same two lines after "Starting build()", but it doesn't fail.
Comment by Joel Teichroeb (klusark) -
Friday, 09 May 2014, 16:52 GMT
It's consistently failing on one of my machines, but not on my others. I'll see if I can figure out why...
Comment by Doug Newgard (Scimmia) -
Thursday, 29 May 2014, 02:20 GMT
Anything on this? It's been sitting for a few weeks now, I'd like to either assign it or close it.
Comment by Joel Teichroeb (klusark) -
Thursday, 29 May 2014, 02:23 GMT
It has been consistently failing on one of my machines, but not on the rest of them and I can't seem to figure out why. I think it might be best to just close it for now until I can figure out what is happening as it seems to be machine centric, and is probably just an issue of my configuration or hardware.