Closed q3cpma closed 2 years ago
Hi @q3cpma
Currently, I'm a little busy with IRL and low on energy when I'm finished with it, so I don't know how much time it will take to look at these issues. Also, I was in the middle of making all the changes for the new Vapoursynth API so because of that, a solution may take even a little bit longer.
I will make you know if I need more info on those.
I updated the deps for the live ebuild, but you will not be able to use it as the new API is not ready in the overlay yet.
As for the problems with broken dependencies, the only thing I can think of if revdep-rebuild
fails you is to use something like
#!/bin/bash
echo "List of dependencies to rebuild:"
printf "%s\n" $(equery -C g --depth=1 -MUl "$1" | awk '{if (!x[$NF]++ && $NF ~ /[^[:space:]]+/) print "=" $NF}' | tail -n +2)
emerge -a1v $(equery -C g --depth=1 -MUl "$1" | awk '{if (!x[$NF]++ && $NF ~ /[^[:space:]]+/) print "=" $NF}' | tail -n +2)
to update its deps. Note that this script needs a full ebuild name and will pull all deps not respecting your use flags.
Feel free to reopen this issue if you think your problem has not been solved.
With 33, I get:
and with 9999, I get:
Both of these with vapoursynth 55 and 9999.
EDIT: fixed the second one by installing vapoursynth-temporalsoften2 and the first one by rebuilding (with
--usepkg=n
) and reinstalling vapoursynth-mvtools. I then got:which I solved the same way as mvtools. Is there some python or vapoursynth cache to invalidate or something?