On 12/19/19 6:05 PM, Allan McRae via arch-dev-public wrote:
There's no package replacing libdmx and libxxf86dga so manual intervention will be needed. So here's a small news draft:
"Xorg cleanup requires manual intervention
"In the process of Xorg cleanup [1] the update requires manual intervention when you hit this message:
:: installing xorgproto (2019.2-2) breaks dependency 'inputproto' required by lib32-libxi :: installing xorgproto (2019.2-2) breaks dependency 'dmxproto' required by libdmx :: installing xorgproto (2019.2-2) breaks dependency 'xf86dgaproto' required by libxxf86dga
when updating, use: `pacman -Rdd libdmx libxxf86dga && pacman -Syu`
to perform the upgrade. After the update it will be safe to also remove the "xorgproto" package.
This why does xorgproto not provides=('inputproto' .... )? Then all we need to do is announce, update and remove.
Allan
Well, this is our new fancy all-the-everything-in-one package, but the inputproto headers / inputproto.pc won't be provided anymore... I think conflicts would be better fitted here, but the bigger question I have is why do we need to be so quick to remove things which apparently work, even if they're legacy/dead, *before* we fix the downstream users? It's hardly difficult to deprecate packages before pulling the plug on them, in cases like this. -- Eli Schwartz Bug Wrangler and Trusted User