Created attachment 428748 [details] /var/tmp/portage/app-emulation/spice-0.13.0/temp/build.log emerge -1 app-emulation/spice-0.13.0 fails to compile.
today ebuilds app-emulation/spice-protocol && app-emulation/spice are unusable. This packages is needed for enable spice in qemu. Historical - this is one package, which was divided into 2 different. Current problem is explained to move header generation script from app-emulation/spice to app-emulation/spice-protocol. Next, developers was make revert this move. As result - 2 packages(tar.bz2) is in inconsistent state. Temporary solution: $ cat /etc/portage/package.keywords =app-emulation/spice-protocol-9999 ** =app-emulation/spice-9999 ** ------------------------------------------- This allow build from git directly. After that we are able compile qemu with spice protocol support. With best wishes:)
*** Bug 578440 has been marked as a duplicate of this bug. ***
This is an issue with parallel make. Building with MAKEOPTS="" solves this. This ebuild doesn't seem to install /usr/include/spice-server for some reason though.
Nope, I am wrong. It still fails with MAKEOPTS="". MAKEOPTS="-pipe" makes it build, but this error still pops up somewhere down the line. Weird. The same happens with spice-0.12.6-r2, by the way.
Created attachment 429700 [details, diff] Set upper bound for spice-protocol in spice ebuilds Okay, I see the problem now. Spice 0.13.0 (and 0.12.6 apparently) assumes that spice-protocol ships code generation utilities and .proto files, and spice-protocol-0.12.10 does this indeed. However, those common files are not shipped with spice-protocol-0.12.11. This has been fixed in spice-9999 (commit 1cd26b8 in spice-common) I would suggest setting upper bound on spice-protocol in both spice-0.12.6 and spice-0.13.0 ebuilds. A pretty straightforward patch attached.
(In reply to Livid from comment #5) > Created attachment 429700 [details, diff] [details, diff] > Set upper bound for spice-protocol in spice ebuilds > > Okay, I see the problem now. Spice 0.13.0 (and 0.12.6 apparently) assumes > that spice-protocol ships code generation utilities and .proto files, and > spice-protocol-0.12.10 does this indeed. However, those common files are not > shipped with spice-protocol-0.12.11. > > This has been fixed in spice-9999 (commit 1cd26b8 in spice-common) > > I would suggest setting upper bound on spice-protocol in both spice-0.12.6 > and spice-0.13.0 ebuilds. > > A pretty straightforward patch attached. Hi guys, I just received this same error when attempting to install gnome-boxes. I'll give the patch a shot, but I'd be interested to know if this will be fixed upstream any time soon. Also, I'm using ACCEPT_KEYWORDS="~amd64" and have attached the information recommended by ebuild after the failure.
Created attachment 430480 [details] Spice info Info for the spice ebuild
Created attachment 430482 [details] Results of emerge -pqv spice Results of emerge -pqv spice
Tried uploading the rest of the logs as attachments, but no go: 8< This site can’t be reached The webpage at https://bugs.gentoo.org/attachment.cgi might be temporarily down or it may have moved permanently to a new web address. >8 So, I've thrown them up on pastebin for reference. Build log: http://pastebin.com/TvLPHQAA Build env: http://pastebin.com/rMhSgXzK
To fix the problem, downgrade to =app-emulation/spice-protocol-0.12.10 and compile fine spice-0.12.7 and spice-0.13.1 support spice-protocol-0.12.11 --- spice-0.12.6-r2.ebuild.old 2015-11-18 21:37:03.000000000 +0100 +++ spice-0.12.6-r2.ebuild 2016-04-28 11:52:55.028511255 +0200 @@ -30,7 +30,7 @@ sasl? ( dev-libs/cyrus-sasl[static-libs(+)?] )" DEPEND=" - >=app-emulation/spice-protocol-0.12.10 + =app-emulation/spice-protocol-0.12.10 virtual/pkgconfig $(python_gen_any_dep ' >=dev-python/pyparsing-1.5.6-r2[${PYTHON_USEDEP}]
*** This bug has been marked as a duplicate of bug 580084 ***
