Arve Barsnes wrote: > On Mon, 10 Jan 2022 at 08:50, Dale <rdalek1...@gmail.com> wrote: >> Howdy, >> >> I've been dealing with this for a while. When I do my updates, it >> either omits seamonkey because the rust version installed is to new or >> downgrades rust. I keyworded rust to see if emerge could sort it out >> itself but Seamonkey then complains about the newer version of rust. >> >> I've read some stories about rust and such but this is annoying. Is >> there not a way to make both packages happy? For once, I'd like to be >> able to update and get a clean outcome. Heck, at this point, I'm a bit >> confused. I've went around in circles so much, I feel like a >> professional drunk. :/ >> >> Thoughts? > I would try to remove this dependency in an overlay. I noticed the > release notes for seamonkey 2.53.10.2 mentions fixing something about > rust-1.57, and no mention of rust in any of the versions between the > latest in portage and that one, so I question if there is actually a > dependency on an older rust here. > > Regards, > Arve
I read in a bug report that this is fixed in a overlay. Makes me wonder why this has been going on for a month or so without a 'in tree' fix. I'd rather not add a overlay but if it is the only fix, may have too. I might add, Seamonkey and Firefox seem to work fine with both versions of rust. The biggest problem is when both Seamonkey and Firefox want to upgrade at the same time. That creates a major clash. Usually, I upgrade Seamonkey first, let it downgrade rust, then upgrade Firefox which pulls in the newer rust. Both seems happy until I do my weekly updates again. If no one else comes up with a better solution, I may try the overlay. I think it is poly.c or something. Thanks. Dale :-) :-)
