Current version of libmrproject is 0.9.1 but current mrproject asks for libmrproject = 0.6 on emerge. So, emerge mrproject fails if libmrproject is already installed: checking for pkg-config... /usr/bin/pkg-config checking for libmrproject = 0.6 glib-2.0 >= 2.0.4 gobject-2.0 gmodule-2.0 gtk+-2.0 >= 2.0.3 libgnomecanvas-2.0 >= 2.0.1 libgnomeui-2.0 >= 2.0.1 libglade-2.0 >= 2.0.0 libbonoboui-2.0 >= 2.0.0 ... Requested 'libmrproject = 0.6' but version of libmrproject is 0.9.1 configure: error: Library requirements ( libmrproject = 0.6 glib-2.0 >= 2.0.4 gobject-2.0 gmodule-2.0 gtk+-2.0 >= 2.0.3 libgnomecanvas-2.0 >= 2.0.1 libgnomeui-2.0 >= 2.0.1 libglade-2.0 >= 2.0.0 libbonoboui-2.0 >= 2.0.0 ) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. !!! ERROR: app-office/mrproject-0.6 failed. !!! Function econf, Line 320, Exitcode 1 !!! econf failed
This looks like a masking error, ie, libmrproject 0.9.1 is unmasked, whereas mrproject 0.9.1 is still masked. This causes "emerge mrproject" to install the newest stable lib (0.9.1) and then it tries to install mrproject 0.6, causing the mrproject ebuild to barf. You can easily do 'ACCEPT_KEYWORDS="~x86" emerge mrproject' which installs the 0.9.1 version of mrproject just fine (however, portage will attempt to downgrade without the -U switch, etc). I think the fix is to either mask or unmask version 0.9.1 of *both* mrproject and libmrproject. Any dissent?
Why is mrproject still masked? Is there a list of current problems anywhere?
i think this is more gnome related. to be honest i'm not sure what the deal is with libmrproject (spider?)
Checking right now.
okay, Not sure what happened to libmrproject, but since this is the first bug I've seen about mrproject I just bump it to stable.
afaik mrproject and its split up lib are directly related, so the version numbers should ideally be the same. Currently mrproject depends '>=' on libmrp , which can better be altered to '='.
