Arch User Repository: 'tizonia-all' builds sometimes break during upgrades #485
During AUR's tizonia packages upgrades, the old package artifacts are already in the system directories when the build starts. This sometimes upsets the compilation of the new source code (e.g. when new APIs have been added in the new release, the old headers have no knowledge of them).
Steps to Reproduce
Reproduces how often:
versions 12 -> 14.
Installation Method Used
The text was updated successfully, but these errors were encountered:
I'm closing this issue now.
Note that the root problem has not actually been fixed, but both Tizonia AUR packages now refuse to install if the 'tizonia' command is detected on the system.
This will make users aware of this limitation and should hopefully prevent dissapointments.
Also, a note has been added in README.md about the need to remove the old package before an upgrade.