Closed minergenon closed 1 month ago
Do you mean in the hud? It looks fine on my end
Hi @flightlessmango I just downloaded archive with submodules and trying compile it for my distrubution but discovered that this source archive https://github.com/flightlessmango/MangoHud/releases/download/v0.7.2/MangoHud-v0.7.2-Source.tar.xz is named as 0.7.2 but after unpacking it point to 0.7.1. But not a big deal, just needed to remove %{version} macro from packaging system.
It's probably because it takes the project version which still is 0.7.1, but everything else should point towards it being 0.7.2. Don't know if this is worth a hotfix
And https://github.com/flightlessmango/MangoHud/releases/download/v0.7.2/MangoHud-v0.7.2-Source.tar.xz dist tar ball has inside MangoHud-v0.7.1/
base directory.
I understand that it's labeled incorrectly, but is it causing any issues downstream or something? If I just rename these and reupload them, is that sufficient for now?
I've renamed it now, any other problem area?
This should be resolved
Looks like meson.build
in MangoHud-v0.7.2-Source.tar.xz
has version : 'v0.7.1'
.
https://github.com/flightlessmango/MangoHud/blob/v0.7.2/meson.build#L3
It does, but it should only be visible when running meson setup. Does it have any actual consequences downstream? I don't want to bump a hotfix for something that doesn't matter
The ArchLinux package in extra uses that, which results in v0.7.1
for mangohud --version
(and in the HUD I guess), but no other consequences than that.
The new version 0.7.2 displays version 0.7.1