On 2022-01-09 05:13, gevisz wrote:
Yes, masking some new package can work in this case.
However, it is not so easy as it may seem because it is not the new
version of tensorflow that I should mask in my case as on the day
when the tensorflow recompilation failed its version remained the same
and only some of its dependencies were supposed to be upgraded.
Of course, I may try this approach. However, tensorflow is not
considered stable in gentoo tree and it has a lot of dependencies
that are also not considered stable and should be unmasked.
All this leads to a large number of possible choices on
which packages to mask/unmask.
So, playing with this is like playing in a casino with about
4 hours of compilation for each bet.
So you know the date it last compiled and run successfully?
If it was me, I'd build a manual list of dependencies (like Dale
indicated), then install genlop and run `genlop -t` for each of the
dependencies and the main package. It will tell you the versions that
were built, and more importantly, the *date* they were built.
You should be able to deduce what package versions were working with
each other, but then the hard part: trying to figure out if those
versions are still available. `eshowkw <package>` will tell you what's
available in the tree, but if it isn't available, then it gets way
harder as you have to try to find the old ebuilds with sources and
possibly set up a local repo and pray those packages don't affect other
installed packages.
Dan
