gnome-cmd-tags-exiv2.cc: In function ‘void gcmd_tags_exiv2_load_metadata(GnomeCmdFile*)’: gnome-cmd-tags-exiv2.cc:410:12: error: ‘AnyError’ does not name a type 410 | catch (AnyError &e) | ^~~~~~~~ make[3]: *** [Makefile:527: gnome-cmd-tags-exiv2.o] Error 1 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-desktop-gnome_20190618-212647 ------------------------------------------------------------------- Please see the tracker bug for details. gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * Available Rust versions: [1] rust-1.35.0 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.12.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpvO gnome-extra/gnome-commander [ebuild N ] gnome-extra/gnome-commander-1.10.0 USE="exif pdf unique -chm -gsf -samba -taglib -test"
Created attachment 580320 [details] emerge-info.txt
Created attachment 580322 [details] emerge-history.txt
Created attachment 580324 [details] environment
Created attachment 580326 [details] etc.portage.tbz2
Created attachment 580328 [details] gnome-extra:gnome-commander-1.10.0:20190621-181016.log
Created attachment 580330 [details] logs.tbz2
Created attachment 580332 [details] temp.tbz2
No gcc-9 issue, just a regular build issue against exiv2-0.27.1 where it is missing a header.
Thanks for reporting. I am thinking of adding a patch instead for version 1.10.0 and 1.10.1. The issue is solved in Gnome Commander 1.10.2, but I did not find the time to having a look how this is done. A workaround for the moment is removing the exif capability: echo "gnome-extra/gnome-commander -exif" Here is the commit for the actual patch: https://github.com/gcmd/gnome-commander/commit/1f98b4a87df3d68b8dd6a2eef24521db7a4d5c75
I meant echo "gnome-extra/gnome-commander -exif" >> /etc/portage/package.use
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eefb5b9bd1af103688a7dee4c0db9a7fcee35a3a commit eefb5b9bd1af103688a7dee4c0db9a7fcee35a3a Author: Uwe Scholz <uwescholz@src.gnome.org> AuthorDate: 2019-07-07 10:10:30 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2019-07-07 21:36:40 +0000 gnome-extra/gnome-commander: patch for compiling with exiv2-0.27.1 Closes: https://bugs.gentoo.org/688452 Signed-off-by: Uwe Scholz <uwescholz@src.gnome.org> Closes: https://github.com/gentoo/gentoo/pull/12400 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> ...mander-1.10.0-exiv2-0.27.1-missing-header.patch | 25 ++++++++++++++++++++++ .../gnome-commander/gnome-commander-1.10.0.ebuild | 3 +++ 2 files changed, 28 insertions(+)
Actually, let's use this bug for upcoming stabilisation as well, as it conveniently blocks exiv2 already.
You mean stabilization of gnome-commander-1.10.0? Yes, I'm fine with it. With the committed patch we can go ahead. I would then open a stabilization request in the next days.
(In reply to Uwe Scholz from comment #13) > I would then open a stabilization request in the next days. No need to, this bug already is prepared for it, has the necessary blocker on exiv2-0.27.1-r1 stable set and just needs arches added.
Arches, please stabilise.
amd64 stable
x86 stable. Closing.