#52327: Buildbot fails incorrectly if calculated dependency tree becomes invalid during installation ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: contrib | Version: 2.3.4 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by ryandesign@…): Replying to [comment:1 cal@…]:
Build 5623 of `gnss-sdr-devel` should not have failed, because at the point where `gnuradio` was required by `gr-osmosdr`, `gnuradio-devel` was already installed and would have satisfied the dependency of `gr-osmosdr`. The problem is that at this point, we no longer know that `gr-osmosdr` would accept the already-installed `gnuradio-devel`, because we run dependency calculation first and then just stupidly iterate over the list.
A solution for this problem might be complicated… basically, while iterating over the dependency tree and before installing a specific dependency, we'd have to check whether the port(s) that require(s) the current dependency still need it or the requirement has been satisfied using other means (e.g., a path:, lib:, or bin: dependency) meanwhile. This problem occurs more or less because we don't compute a closed form solution of the dependency tree before actually installing.
I figured it was something tricky like this.
To reset the incorrect state for now, you can just trigger a build of gnuradio directly, which will ignore the failcache but update it on success.
Oh good, I didn't know that would work. I ran builds of gnuradio on all the builders, which succeeded on the recent OS versions at least. -- Ticket URL: <https://trac.macports.org/ticket/52327#comment:2> MacPorts <https://www.macports.org/> Ports system for macOS