Il 01/06/25 16:21, Dr Rainer Woitok ha scritto:
Greetings,since quite some time I have installed both packages, "dev-cpp/abseil- cpp" and "dev-libs/protobuf" from the binhost. Now there is an upgrade for "dev-cpp/abseil-cpp" which causes a rebuild for "dev-libs/protobuf" that stubbornly requests rebuilding the latter from source: $ emerge --pretend --oneshot --getbinpkg dev-libs/protobuf Local copy of remote index is up-to-date and will be used. [binary r U ] dev-cpp/abseil-cpp-20250127.1-1 [20240722.0-r1] [binary rR ] media-libs/webrtc-audio-processing-1.3-r3-5 [ebuild R ] dev-libs/protobuf-28.0 [ebuild rR ] dev-util/android-tools-34.0.5 The following packages are causing rebuilds: (dev-cpp/abseil-cpp-20250127.1-1:0/2501.1.0::gentoo, binary scheduled for merge) causes rebuilds for: (media-libs/webrtc-audio-processing-1.3-r3-5:1/1::gentoo, binary scheduled for merge) (dev-util/android-tools-34.0.5:0/0::gentoo, ebuild scheduled for merge) (dev-libs/protobuf-28.0:0/28.0.0::gentoo, ebuild scheduled for merge) $ However, when I exclude package "dev-cpp/abseil-cpp", package "dev-libs/ protobuf" would be rebuild from the binhost as expected: $ emerge --pretend --oneshot --getbinpkg --exclude=dev-cpp/abseil-cpp dev-libs/protobuf Local copy of remote index is up-to-date and will be used. [binary R ] dev-libs/protobuf-28.0-1 $ Can anybody shed some light on this behaviour? Since my last ebuild of package "dev-libs/protobuf" took 12 minutes to complete, I'm hesitating to just let this pass ... :-/
Maybe abseil-cpp requires dev-libs/protobuf with USE flags different from the ones the bin package was built with? But normally emerge tells me if this is the case, I don't see that in your output. Maybe re-run emerge with -v?
raf
