On Wednesday, 6 September 2023 17:09:15 BST Grant Edwards wrote: > I just did my usual update > > sudo emerge --sync > sudo emerage -auvND world > > I noticed that it was downgrading sqlite from 3.43 to 3.42. OK, we'll > assume that portage and the devs know what they're doing... > > Now this happens: > > $ svn status > svn: E200029: Couldn't perform atomic initialization > svn: E200030: SQLite compiled for 3.43.0, but running with 3.42.0 > > Have I done something wrong? Is an ebuild broken? > > Manually re-merging svn didn't fix it. > > Now what do I do?
The message indicates subversion needs reinstalling with the downgraded sqlite - potentially @preserved-rebuild ought to catch this, or revdep-rebuild. You could have a go rebuilding sqlite with +static-libs, but I'm clutching at straws here. :-/
signature.asc
Description: This is a digitally signed message part.