Jump to content

Photo

meld requires too new glib 2.50:2

- - - - -

Best Answer onli , 09 September 2017 - 11:58 AM

Hi jhan. I think there was an update to the ebuilds by now. I am not aware of having changed my system (and certainly not the USE flags), but meld compiles now.

 

The dbus USE flag is disabled on my system, but I had to enable it for some specific packages. But I don't see it activated for meld.

Go to the full post »


2 replies to this topic

#1
onli

onli

    Member

  • Members
  • PipPip
  • 16 posts

Emerge is failing to upgrade:

emerge: there are no ebuilds to satisfy ">=dev-libs/glib-2.50:2[dbus]".
(dependency required by "dev-util/meld-3.17.4::dev-kit" [ebuild])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

And indeed, the ebuild of meld, https://github.com/f...d-3.17.4.ebuild, got an update 6 hours ago that added a new ebuild for 3.17.4 that requires glib-2.50:2, but https://github.com/f...e/dev-libs/glib contains no ebuild for that version.

 

Should I report this in the bug tracker?



#2
jhan

jhan

    Member

  • Members
  • PipPip
  • 14 posts

As far as I can see glib is only needed when the dbus USE flag is set. Do you need that flag set? Can you compile meld with USE=-dbus?


  • onli likes this

#3
onli

onli

    Member

  • Members
  • PipPip
  • 16 posts
✓  Best Answer

Hi jhan. I think there was an update to the ebuilds by now. I am not aware of having changed my system (and certainly not the USE flags), but meld compiles now.

 

The dbus USE flag is disabled on my system, but I had to enable it for some specific packages. But I don't see it activated for meld.





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users