Again(!) a dependency consistency error within the Artix repositories:
lib32/lib32-expat is at version 2.6.0-1 and depends on
expat=2.6.0.
But
system/expat is at version 2.6.1-1.
Thus,
lib32-expat's dependency cannot be fulfilled consistently within the Artix repositories.
From
yay -Syu:
error: failed to prepare transaction (could not satisfy dependencies)
:: installing expat (2.6.1-1) breaks dependency 'expat=2.6.0' required by lib32-expat
Rergards!
I ran an update now and it passed.
You sound frustrated ?
If you took the time to look you'd have seen the lib32-expat package was updated at least a couple of hours before you made your post.
Then ,I imagine, it has to enter a build queue. Then It has to be picked up by the mirror you use.
If you update less frequently you'll encounter far fewer such issues.
If you want to update very frequently just expect the, generally short-lived, dependency problems more often.
It's pretty simple.
Yes I am, because such errors in the past I encountered quite frequently, and sometimes they persistet for days until they were eventually reported and someone manually fixed them, and I thought it was that case again, because partial sync of repositories/ mirror does not came into my mind at all (can easily be avoided), and because:
What frustrates me that in principle this could be avoided algorithmically, this case by doing the updates and syncs atomically (switch to the new packages only after all are in the backend store, e.g. by rotating a symlink).
Actually we are trained on Arch and Artix to update before installing any new package to not have "partial updates". This is what I read.
So "updating less frequently" means "not installing a single package if I want/ need, but only when the less-frequent update is due". (And I updated a bit more than a week ago last time.)
Hm.
Regards and thanks that it works now!
It's only a partial update if you do pacman -Sy $package.
You can quite safely use pacman -S $package until such time as $package (and / or non installed dependencies) 404's because the package listed in your database has been updated. You do not need to do a full system update every time you install a package.
You can if you want though. But it's simple logic that the more often you update the more often you'll encounter situations where $package has just had an update but lib32-$package is lagging behind or vice verse.
Comes across to me as entitled and ungrateful. But maybe that's just me?
I have the odd issue myself but wouldn't dream of moaning about any of them without at least going on gitea to see if the package had been updated and was just waiting to hit the mirrors.
Bug reports good (after a check that's it's even needed). Behaviour which could be discouraging to people who give up a portion of their free time for my benefit bad. imho.
OK, thanks, my fault of shortcut-thinking. Thanks for cutting through my shortcut-thinking!
And I am on the complete opposite side, that I think I express gratefulness much too less. I take purpose of communication solely to be "peer review" too often.
And yes, you are right, some thing within myself assumes that "they"/ "you" (the Artix peopke) are doing things right and perfect, and that increases my frustration if not.
I take this as settled for me now.
And thanks for you maintainers
what you actually make possible!
ignore
What should I or someone else ignore?
I solved this with "--ignore=*expat", as usual, when something like this happend.