from /var/tmp/portage/x11-misc/polybar-3.2.1/work/polybar-3.2.1/src/x11/window.cpp:4: /var/tmp/portage/x11-misc/polybar-3.2.1/work/polybar-3.2.1/include/x11/window.hpp: In copy constructor ‘polybar::v3_2_1::window::window(const polybar::v3_2_1::window&)’: /var/tmp/portage/x11-misc/polybar-3.2.1/work/polybar-3.2.1/include/x11/window.hpp:13:7: error: implicitly-declared ‘xpp::window<polybar::v3_2_1::connection&>::window(const xpp::window<polybar::v3_2_1::connection&>&)’ is deprecated [-Werror=deprecated-copy] 13 | class window : public xpp::window<connection&> { | ^~~~~~ In file included from /var/tmp/portage/x11-misc/polybar-3.2.1/work/polybar-3.2.1/lib/xpp/include/xpp/proto/../generic.hpp:8, ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-desktop_libressl_20190526-141358 ------------------------------------------------------------------- Please see the tracker bug for details. gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] 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 x11-misc/polybar !!! /etc/portage/package.env references non-existent file: /etc/portage/env/nousersandbox
Created attachment 578080 [details] emerge-info.txt
Created attachment 578082 [details] emerge-history.txt
Created attachment 578084 [details] environment
Created attachment 578086 [details] etc.portage.tbz2
Created attachment 578088 [details] logs.tbz2
Created attachment 578090 [details] temp.tbz2
Created attachment 578092 [details] x11-misc:polybar-3.2.1:20190530-012120.log
@Toral Since when we are posting the same error to two versions of the package? Imho duplicate of 686996
(In reply to Johannes Huber from comment #8) > @Toral Since when we are posting the same error to two versions of the > package? Imho duplicate of Bug #686994
*** This bug has been marked as a duplicate of bug 686994 ***