Ebuild of libproxy-0.4.18 depends on spidermonkey:68 wich is no longer available in the tree: =============== %< ============== $ equery d spidermonkey * These packages depend on spidermonkey: net-libs/libproxy-0.4.18 (spidermonkey ? dev-lang/spidermonkey:68) [...] $ eix spidermonkey [U?] dev-lang/spidermonkey Verfügbare Versionen: (78) 78.15.0^t (91) 91.13.0-r1^t (102) 102.6.0^t {clang debug +jit lto test CPU_FLAGS_ARM="neon"} Installierte Versionen: 68.12.0-r1(68)^t(06:14:49 PM 06/15/2022)(jit -debug -test CPU_FLAGS_ARM="-neon") Startseite: https://spidermonkey.dev https://firefox-source-docs.mozilla.org/js/index.html Beschreibung: SpiderMonkey is Mozilla's JavaScript engine written in C and C++ =============== %< ============== Therefore I cannot get rid of preserved libraries: =============== %< ============== $ sudo emerge @preserved-rebuild Passwort: Calculating dependencies... done! emerge: there are no ebuilds to satisfy "dev-lang/spidermonkey:68". (dependency required by "@preserved-rebuild" [argument]) =============== %< ============== Reproducible: Always Steps to Reproduce: Unsure how to setup a system for a similar state, but the missing referenced version in the ebuild is ovbious. Actual Results: preserved rebuild cannot resolve the deps Expected Results: preserved rebuild should be successful Actually I have spidermonkey in a different system in the world file. Anything works fine with latest version 102.
You should always do: 1. world upgrade 2. depclean 3. *then* preserved-rebuild if required (you should never need to). libproxy's USE=spidermonkey is masked because that version of SM was vulnerable and old.
Thanks, actually I was never aware that depclean should be run before a repdev rebuild. And I have a 20 year history with Gentoo... repdev rebuild was once quite common ;-)
