/var/tmp/portage/dev-libs/sink-0.7.0/work/sink-0.7.0/examples/imapresource/imapserverproxy.cpp: In function ‘int translateImapError(KJob*)’: /var/tmp/portage/dev-libs/sink-0.7.0/work/sink-0.7.0/examples/imapresource/imapserverproxy.cpp:72:32: error: ‘KIMAP2::LoginJob::ErrorCode’ has not been declared 72 | case KIMAP2::LoginJob::ErrorCode::ERR_HOST_NOT_FOUND: | ^~~~~~~~~ /var/tmp/portage/dev-libs/sink-0.7.0/work/sink-0.7.0/examples/imapresource/imapserverproxy.cpp:74:32: error: ‘KIMAP2::LoginJob::ErrorCode’ has not been declared ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma_systemd-libressl-20190908-101602 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.13.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm repository timestamp: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Tue, 10 Sep 2019 09:06:00 +0000 emerge -qpvO dev-libs/sink [ebuild N ] dev-libs/sink-0.7.0 USE="-debug"
Created attachment 589634 [details] emerge-info.txt
Created attachment 589636 [details] dev-libs:sink-0.7.0:20190910-100008.log
Created attachment 589638 [details] emerge-history.txt
Created attachment 589640 [details] environment
Created attachment 589642 [details] etc.portage.tbz2
Created attachment 589644 [details] logs.tbz2
Created attachment 589646 [details] temp.tbz2
Same here. It looks like it fails with kimap2-0.3.0 and kdav2-0.3.0. Downgrading them to 0.2.0 solves the issue for me. Probably would be best to depend on =0.2* version in dev-libs/sink.
In somewhat connected issue: Kube-0.7.0 needs kasync-0.2*
0.8.0 was just tagged so I guess a new release is imminent.
(In reply to Andreas Sturmlechner from comment #10) > 0.8.0 was just tagged so I guess a new release is imminent. It seems Gentoo builds directly from Git tags. Can the package please be version bumped?
Gentoo builds from release tarballs.
(In reply to Andreas Sturmlechner from comment #12) > Gentoo builds from release tarballs. I doubt that: https://github.com/gentoo/gentoo/blob/master/dev-libs/sink/sink-0.7.0.ebuild#L10
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cb03fa2ffb85e396b804edcd716f9191fd00cc70 commit cb03fa2ffb85e396b804edcd716f9191fd00cc70 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2019-09-29 19:01:36 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2019-09-29 20:07:06 +0000 dev-libs/sink: 0.8.0 version bump Sigh... if upstream will not bless us with a release... Closes: https://bugs.gentoo.org/693988 Package-Manager: Portage-2.3.76, Repoman-2.3.17 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> dev-libs/sink/Manifest | 1 + dev-libs/sink/sink-0.8.0.ebuild | 59 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 60 insertions(+)
