In file included from /var/tmp/portage/net-im/toxic-0.7.2/work/toxic-0.7.2/src/windows.h:37:0, from /var/tmp/portage/net-im/toxic-0.7.2/work/toxic-0.7.2/src/autocomplete.c:34: /var/tmp/portage/net-im/toxic-0.7.2/work/toxic-0.7.2/src/toxic.h:119:52: error: unknown type name ‘TOX_CONFERENCE_TYPE’ void on_groupinvite(Tox *m, uint32_t friendnumber, TOX_CONFERENCE_TYPE type, co ^ ----------------------------------------------------------------- This is an unstable amd64 chroot image (named plasma-systemd_20170215-191016) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * llvm-config: 3.9.1 Available Python interpreters, in order of preference: [1] python2.7 [2] python3.5 (fallback) [3] python3.4 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 7.2.6.8 [icedtea-bin-7] 2) IcedTea JDK 3.3.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-7 system-vm [2] icedtea-bin-8
Created attachment 464712 [details] emerge-info.txt
Created attachment 464714 [details] emerge-history.txt
Created attachment 464716 [details] environment
Created attachment 464718 [details] etc.portage.tbz2
Created attachment 464720 [details] net-im:toxic-0.7.2:20170222-150749.log
It appears upstream switched to TokTok/toxcore. I didn't run into this when I first wrote this, so a rebuild of net-libs/tox can fix it. Does DEPEND="net-libs/tox:0=[av?]" correct this? It appears to work fine on my system.
(In reply to Daniel Campbell from comment #6) not here, used this diff : tinderbox@mr-fox ~/tb/data/portage/net-im/toxic $ diff /usr/portage/net-im/toxic/toxic-0.7.2.ebuild toxic-0.7.2.ebuild 17d16 < net-libs/tox:0/0.0[av?] 25c24,25 < DEPEND="${RDEPEND}" --- > DEPEND="net-libs/tox:0=[av?] > ${RDEPEND}"
The tinderbox pulled in the 0/0.0 slot, which is what the ebuild is at now. Maybe switching to the 0/0.1 subslot will get things to cooperate. Try this out: --- a/toxic-0.7.2.ebuild 2017-02-23 05:00:37.749931270 -0800 +++ b/toxic-0.7.2.ebuild 2017-02-23 05:00:47.968812991 -0800 @@ -14,7 +14,7 @@ IUSE="+X +av notifications" RDEPEND=" - net-libs/tox:0/0.0[av?] + net-libs/tox:0/0.1[av?] dev-libs/libconfig media-gfx/qrencode net-misc/curl That should require net-libs/tox to be at 0.1.6 (currently), and get this corrected.
(In reply to Daniel Campbell from comment #8) indeed, this made it here : tinderbox@mr-fox ~/tb/data/portage/net-im/toxic $ diff /usr/portage/net-im/toxic/toxic-0.7.2.ebuild toxic-0.7.2.ebuild 17c17 < net-libs/tox:0/0.0[av?] --- > net-libs/tox:0/0.1[av?]
(In reply to Toralf Förster from comment #9) > indeed, this made it here : Great! commit fb2addc500dcfa1c7f7125aaaf63145a47a69a19 Author: Daniel Campbell <zlg@gentoo.org> Date: Thu Feb 23 17:05:58 2017 -0800 net-im/toxic: correct dependency wrt bug 610570 Gentoo-Bug: 610570 Gentoo-Bug-URL: https://bugs.gentoo.org/610570 Package-Manager: Portage-2.3.3, Repoman-2.3.1
