PyBOMBS (Python Build Overlay Managed Bundle System) is the GNU Radio install management system for resolving dependencies and pulling in out-of-tree projects.
Installed something with its default recipe. The recipe indicated that it pulls from branch A.
Install failed due to a mismatch with another recipe.
I went into the recipe and changed the branch to branch B, which is compatible with the other recipe.
Subsequent pybombs install still uses branch A despite recipe file saying branch B (local change only).
To me, this feels like a bug. If I need to update my local config I should be able to do so, and I would expect the recipe files to be the single point of truth for installation definitions. There seems to be a cache somewhere else though, at least in the case of a previously attempted installation (step 2.)?
My workaround was to go into the checked out repo in my prefix src folder and do a git checkout B, and then run pybombs install again; this time B was used.
Expected behavior to me would be that pybombs install always checks out the branch that is defined in the recipe file before performing any further installation-relevant operations on the source files.
I just encountered this weird issue:
pybombs installstill uses branch A despite recipe file saying branch B (local change only).To me, this feels like a bug. If I need to update my local config I should be able to do so, and I would expect the recipe files to be the single point of truth for installation definitions. There seems to be a cache somewhere else though, at least in the case of a previously attempted installation (step 2.)?
My workaround was to go into the checked out repo in my prefix
srcfolder and do agit checkout B, and then runpybombs installagain; this time B was used.Expected behavior to me would be that
pybombs installalways checks out the branch that is defined in the recipe file before performing any further installation-relevant operations on the source files.