checking for GMODULE... yes checking for PANEL... no configure: error: Package requirements (gmodule-2.0 gdk-pixbuf-2.0 >= 2.25.2 pango >= 1.15.4 gtk+-3.0 >= 3.22.0 glib-2.0 >= 2.50.0 gio-unix-2.0 >= 2.50.0 mate-desktop-2.0 >= 1.17.0 gio-2.0 >= 2.50.0 libmate-menu >= 1.21.0) were not met: Package dependency requirement 'libmate-menu >= 1.21.0' could not be satisfied. Package 'libmate-menu' has version '1.18.1', required version is '>= 1.21.0' ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-desktop-gnome-systemd_libressl_20190313-132619 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.3.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) [3] ruby26 (with Rubygems) Available Rust versions: [1] rust-bin-1.32.0 [2] rust-1.32.0 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.10.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpvO mate-base/mate-panel [ebuild N ] mate-base/mate-panel-1.22.0 USE="X introspection"
Created attachment 569508 [details] emerge-info.txt
Created attachment 569510 [details] emerge-history.txt
Created attachment 569512 [details] environment
Created attachment 569514 [details] etc.portage.tbz2
Created attachment 569516 [details] logs.tbz2
Created attachment 569518 [details] mate-base:mate-panel-1.22.0:20190317-133217.log
Created attachment 569520 [details] temp.tbz2
libmate-menu provided by mate-menus which appropriate version is in the tree and being installed alongside with the panel
The dependency is wrong. Minimum deps need to be updated to be at least as high as upstream needs. ebuild has >=1.10.0, upstream needs >=1.21.0 as seen in the error output.
(In reply to Mart Raudsepp from comment #9) > The dependency is wrong. Minimum deps need to be updated to be at least as > high as upstream needs. > ebuild has >=1.10.0, upstream needs >=1.21.0 as seen in the error output. according to the emerge info output the initial report still can be considered invalid as from output this is seen that ~amd64 is commonly used so this is supposed to take the latest one (although I doubt any testing being performed against unstable, and that is why)
Reflecting upstream minimum deps properly and not relying on "latest available" in packages is ebuild maintenance 1-0-1. I'm not really sure what else to say. The original report is correct.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4a2354be4f225a40670a059ac8e086edffc24d49 commit 4a2354be4f225a40670a059ac8e086edffc24d49 Author: Mikle Kolyada <zlogene@gentoo.org> AuthorDate: 2019-04-07 11:25:46 +0000 Commit: Mikle Kolyada <zlogene@gentoo.org> CommitDate: 2019-04-07 11:26:16 +0000 mate-base/mate-panel: Bump minimal mate-menus version Closes: https://bugs.gentoo.org/680766 Signed-off-by: Mikle Kolyada <zlogene@gentoo.org> Package-Manager: Portage-2.3.62, Repoman-2.3.11 mate-base/mate-panel/mate-panel-1.22.0.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
