Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arch User Repository: 'tizonia-all' builds sometimes break during upgrades #485

tizonia opened this issue May 4, 2018 · 1 comment


None yet
2 participants
Copy link

commented May 4, 2018


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

  1. Install release a
  2. upgrade to release a + b (where new APIs have been added)
  3. [and so on...]

Expected behavior:
Build proceeds reliably, as in a first install.

Actual behaviour:
Sometimes, the build breaks when using the old tizonia headers in the system (since no knowledge of the new APIs exist in those headers).

Reproduces how often:
E.g. between versions 12 -> 14.


versions 12 -> 14.

Installation Method Used


@tizonia tizonia added the bug label May 4, 2018

@tizonia tizonia added this to the v0.15.0 milestone May 4, 2018

@tizonia tizonia modified the milestones: v0.15.0, v0.16.0 Jun 15, 2018

@tizonia tizonia modified the milestones: v0.16.0, v0.17.0 Dec 20, 2018

@tizonia tizonia removed this from the v0.17.0 milestone Jan 31, 2019


This comment has been minimized.

Copy link
Owner Author

commented Jan 31, 2019

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.

See 1ad0fec

This will make users aware of this limitation and should hopefully prevent dissapointments.

Also, a note has been added in about the need to remove the old package before an upgrade.

@tizonia tizonia closed this Jan 31, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.