Package: gbsplay
Version: 0.0.99-1
Severity: minor

Dear Maintainer,

`gbsplay -V` displays the gbsplay version number as `0.0.99ish`
instead of `0.0.99`.

This seems to be the case because the `gbsplay_0.0.99.orig.tar.gz`
used for the package build is not the original upstream tarball, but
most likely the manual export from some git repository (either the one
on salsa or the `Source Code.tar.gz` offered on the gbsplay GitHub
release page).

The current correct upstream release tarball is the asset named `gbsplay-0.0.99.tar.gz` on the GitHub release page:

- https://github.com/mmitch/gbsplay/releases/tag/0.0.99
- https://github.com/mmitch/gbsplay/releases/download/0.0.99/gbsplay-0.0.99.tar.gz

Using this autogenerated file instead will create the wrong version number:

- https://github.com/mmitch/gbsplay/archive/refs/tags/0.0.99.tar.gz


Because this is not very intuitive I've added a new file called
PACKAGING.md to the gbsplay repo with information regarding the
version number handling of the gbsplay build system:

https://github.com/mmitch/gbsplay/blob/master/PACKAGING.md

Feel free to have a look at that file and tell me if something is
unclear or it does not help at all. It's brand new and untested :)



To fix the version number in the Debian package, please use the
original tarball as .orig.tar.gz.

I don't know if it is possible or advisable to switch the tarball
between versions 0.0.99-1 and 0.0.99-2. upstream 0.0.100 should not
be too far in the future, so perhaps it's better to just wait for the
next release and incorporate the tarball switch into it.


Kind regards,
Christian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)