Bug#1102086: game-data-packager: Not NMU-safe

[Santiago Vila]

El 5/4/25 a las 12:03, Simon McVittie escribió:
> This package is NMU-safe if you follow the NMU convention that is documented in devref. `dch --nmu` automates this.

Ok, thanks a lot for the explanation. Yes, I noticed that some NMUs were following the +nmuX convention, never got to the point of figuring out why, but now I know, and of course it makes sense.
  
> (It seems that it actually fails to build from source right now because we're having trouble running inkscape non-interactively to generate icons from their "source code", but that's orthogonal to the version numbering.)

See the next bug I sent. It actually builds ok when the dbus thing is removed from debian/rules.
  
> If you were genuinely preparing a NMU to fix a RC issue after a lack of maintainer response, it should be based on the version that is actually in the archive, currently 84 (so it would be 84+nmu1), rather than the version in git. Or, if you're merely suggesting a patch that you have no intention of uploading to Debian yourself (effectively an upstream merge request, but possibly in diff|patch format), there's no need to change the changelog or version number - and, indeed, it's better if you don't, because if every MR or patch updates the changelog, that guarantees that every parallel contribution will have merge conflicts.

Ok, for completeness and clarification: I was preparing a modified package which I could
feed to my autobuilders to test, as they need a real source package in a private repo
with a version that has to be different than the one in unstable. The reason I used 85.1 is
that I did a git clone from salsa and did not bother to remove the existing dummy
changelog entry.

While we are at it, using those dummy entries has its drawbacks, they trigger a warning
in tracker.debian.org, as you can see here:

https://qa.debian.org/cgi-bin/vcswatch?package=game-data-packager

Thanks.