Jack wrote: > On 2019.05.06 19:19, Dale wrote: > [snip....] >> I use Konsole when I do updates and it has this nifty search function >> that I use. I use it to look for "error 1" since sometimes it can be >> buried deep and hard to find without it. On this one, I got two >> hits, the one I posted plus one further down where emerge was giving >> up or something. I usually post the first one since that is usually >> the problem. ;-) > You need the first "error" not just "error 1". Unfortunately, you do > need to week out everything where "error" is a substring of some > parameter or variable name. > >> I'm attaching the whole thing since it appears what I posted isn't >> enough in this case. Generally it is but there is always that >> exception. >> >> Meantime, I'm going to try some other ideas from other replies. I >> think I tried them before but I don't trust that memory. Last I >> worked on this was when my Mom was so sick. Memory is a bit fuzzy. :/ >> >> Thanks for the help. > It does look like it's the bug someone just posted to this thread - so > downgrading guile might be your current best solution. > > Jack >
This is what I ended up doing to fix this. It took some trial and error tho. emerge =dev-scheme/guile-2.0.14-r3 Then I ran emerge @preserved-rebuild. It seems to be happy at the moment. Doing a world update came back clean also. I also had to remove the package from the keyword file. I'm not sure what caused it to be added as it had no notes attached to it. I also tried: emerge =dev-scheme/guile-2.0.13-r2 It failed with a different error, to old of a version basically. Since I run a mix of stable and unstable, it is likely just a mismatch of versions that caused this. I just wish I knew why I added it to the keyword file to begin with. There was likely a good reason and it did work for a while but caused a problem later on as newer packages become available. It's solved for now tho. Thanks much to all for the help. :-D Dale :-) :-)
