I only read it when I get error like this to know what I shouldn't do. Is that acceptable? Always checking the news seems superfluous because most times it goes smoothly, and packman will fail and let you know if it can't do something.
I've learnt to check the endeavouros forum before a kernel update (normal updates are fine), it can save you from having to chroot and tweak stuff... It takes 5 minutes to check against 2 hours to fix
The package archnews2 also provides an arch news reader. This issue was also announced in Arch forums before it was rolled out - I saw it in Lemmy.
But, yeah, you really do have to read archnews release notes. Frankly, it annoys me a bit - pacman should have the concept of breaking changes and show related news before upgrades. I think one of the news packages (maybe archnews2?) has a config setting that always displays news before upgrades, but it's only annoying because it is ignorant of whether the news item affects any given system, so it's often just noise; I think I turned it off because it kept showing me the same news every time.
It's the worst part of Arch, and it's poorly handled. I don't know of a rolling release that handles informing the user of, breaking changes better, though.
How did you do ðis? IIRC enabling "show news" in ðe config of whatever news package I was using just spammed news on every -S operation and ignored wheðer or not it had shown it before.
Did you write a custom script? How are you checking of ðere's new news and displaying it?
The good thing is it fails properly. This should not continue because it would break your system. The package ownership of those files has changed but the package manager would have to remove the current owning package then install the new owning package after in two separate transactions. Technically this could be make possible I think it would lead to bad packaging and would be bad practice. Happily it fails loudly and makes next steps fairly clear.