summarylogtreecommitdiffstats
path: root/PKGBUILD
AgeCommit message (Collapse)Author
2024-03-10Fix build with GCC 14Joan Bruguera Micó
2024-01-01Fix build (when specifying SOURCE_DATE_EPOCH?).Joan Bruguera Micó
2024-01-01Honor SOURCE_DATE_EPOCH for reproducible builds.Joan Bruguera Micó
2023-03-06Remove i686 arch (due to being untested)Joan Bruguera
2021-03-11Remove GCC 10 patch since problem appears to be solved upstream - my ↵Joan Bruguera
previous pkgrel was botched.
2021-03-11Update to 5.4.2.20210310.Joan Bruguera
2021-03-09Update to 5.4.2.20210309.Joan Bruguera
2020-11-20Revert last update since it was reverted from BSC FTP - this is the same as ↵Joan Bruguera
5.4.2.20200414, but with a higher version to force the rollback.
2020-11-20Revert "Update to 5.4.2.20201116 - silent update, no changelog entry, some ↵Joan Bruguera
OpenMP stuff? Who knows..." This reverts commit 57e68e31ddf4651478a4fde58ac35fa68c7fa0e9.
2020-11-16Update to 5.4.2.20201116 - silent update, no changelog entry, some OpenMP ↵Joan Bruguera
stuff? Who knows...
2020-05-12Fix build for GCC 10+Joan Bruguera
2020-04-15Update to 5.4.2.20200414.Joan Bruguera
2019-12-10Upgrade tracking to the latest version. Additionally, change BSC package ↵Joan Bruguera
versioning numbers, in order to include the year in the pkgver. This is to deal with the fact that multiple, different tallbars are routinely released for the same version number. Up until now, this was handled by bumping pkgrel, but this is not the correct way to handle this, since it's not just a rebuild, but just the upstream code changed.
2019-08-02Update pkgrel sha512sum due to upstream change with no version change (this ↵Joan Bruguera
is getting annoying, should start tracking changes...).
2019-07-06Upstream checksum changed, doesn't seem to have relevant changes wrt. ↵Joan Bruguera
github's past release.
2019-03-22Fix package licenses.Joan Bruguera
2019-03-22Update to 5.4.1, lint and uniformize BSC package files.Joan Bruguera
2019-02-28Initial version.Joan Bruguera