diff options
| author | user <user@clank> | 2026-09-02 16:10:48 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-09-02 16:10:48 +0200 |
| commit | 9cc6ff911ac794c5831407358fddb7b7c9c24ef6 (patch) | |
| tree | 3cbb4cd1f677a29094d77eb97ff487f9bd5cb4de /docs | |
| parent | ship: paperwork before the website, so the demo is not stamped -dirty (diff) | |
| download | slosh-9cc6ff911ac794c5831407358fddb7b7c9c24ef6.tar.gz slosh-9cc6ff911ac794c5831407358fddb7b7c9c24ef6.tar.xz slosh-9cc6ff911ac794c5831407358fddb7b7c9c24ef6.zip | |
version: never answer for somebody else's git; arch: 0.1.4-3
The v0.1.4 arch packages introduced themselves as 0.1.4-dirty: the
tag's tarball has no .git, makepkg builds it inside the release
box's repository, and git describe walked up and answered for the
outer tree -- mid-release, when the paperwork is honestly dirty.
Found at 0.1.2, diagnosed, and then left unfixed by yours truly.
Two fences now. contrib/version only trusts a .git whose toplevel is
its own root (helps every future tarball). The PKGBUILD exports
GIT_CEILING_DIRECTORIES for build and package (helps regardless of
which contrib/version the pinned tarball carries, which is why the
first rebuild still said -dirty: the fix was outside the tarball).
pkgrel=3; both architectures rebuilt, verified 'slosh 0.1.4', and
republished.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions