Summary: | webkit-gtk blocking each other | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joseph <gentoo_bugzilla> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | mattst88 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
output of emerge -udNpv @world (emerge --sync run shortly before)
emerge -pv --depclean net-libs/webkit-gtk yelp shotwell gnucash > /tmp/emerge-depclean.tx |
Description
Joseph
2022-12-08 15:08:21 UTC
Created attachment 840993 [details]
output of emerge -udNpv @world (emerge --sync run shortly before)
Created attachment 840995 [details]
emerge -pv --depclean net-libs/webkit-gtk yelp shotwell gnucash > /tmp/emerge-depclean.tx
This is some kind of local misconfiguration. The problem is
> [ebuild UD ] net-libs/webkit-gtk-2.36.7:4/37::gentoo [2.38.1:4/37::gentoo] USE="X egl gnome-keyring gstreamer introspection jpeg2k jumbo-build lcms libnotify%* (seccomp) spell systemd wayland (-aqua) -avif -examples -gamepad -gles2-only -gtk-doc% -test (-pdf%*)" 25.972 KiB
> ...
> [blocks B ] <net-libs/webkit-gtk-2.38:4 ("<net-libs/webkit-gtk-2.38:4" is soft blocking net-libs/webkit-gtk-2.38.2-r500, net-libs/webkit-gtk-2.38.2-r410)
You need 2.38.2:4 to satisfy the blocker. For some reason you're not getting the 3 slots of webkit-gtk updated in sync.
I suspect this is because you had 2.38.1 in your package.accept_keywords, which is now gone from the tree. You have to update package.accept_keywords. I recommend app-portage/portpeek for finding outdated package.* entries.
Ah, I found the issue. It was indeed on my end, sorry. I had the following in my package.mask from some time ago: =net-libs/webkit-gtk-2.38.2 Removing it (and its compatriots) and everything was fine again. I don't recall when I put it in, but I put entries in there when there's a compilation issue in a package, and I expect the next version bump will fix it. |