Error with libxml2 after upgrade

Maybe try updating libxml2 first, skipping the version dependency check:

./pacman-static -Syd libxml2

You might even have to skip all checks:

./pacman-static -Sydd libxml2

If that installs the correct version of libxml2 (2.14.3-1) successfully, then you should (hopefully) have pacman working and be able to do the rest of the update:

sudo pacman -Syu

Yeah, we ignored libxml2, so that was foreseeable. Anything else is updated right now? Usually the database should be refreshed by force (since double yy) and the packages electron31,electron32,libarchive,openconnect,sane need now the the newer libxml2 version. Therefore the update should run.

./pacman-static -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
warning: shortwave: local (1:3.2.0-1) is newer than extra (5.0.0-1)
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing libxml2 (2.14.3-1) breaks dependency 'libxml2.so=2-64' required by electron32

Great… now remove electron32 for now. And possibly code? Then do an update and install code again…

1 Like

Phew - yes - that did it - muchĆ­simas gracias

One question… Is -Syd safe? Can some apps stop working asking for the prior version after updating? Thanks.

I really don’t know. I’ve never had any need to use the -d or -dd options when installing or upgrading a package with pacman. I might have used it when removing a package though.

At the time of writing my reply, it looked like the topic was getting stuck on the dependency issues, so I thought that it might move along if the correct version of libxml2 could be installed without any dependency checks.

Running sudo pacman -Syu immediately afterwards should have then gotten everything else up-to-date.

I’m not brave enough to remove or downgrade libxml2 on my own system to test out my suggestion though.

3 Likes

Probably not, but it would depend on various factors. In this case libxml2 is required by one or more of pacman’s dependencies, based on recent threads it seems likely pacman would break.

However the proposed command already used pacman-static so it shouldn’t have been a problem, just finish the update with pacman-static.


Typically the proper way to deal with version conflicts during an update is to uninstall the conflicting packages and if necessary reinstall them after updating.

4 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.