Hi,

There's something strange going on regarding the version of the source you're
building as 2.1.0.

I noticed this when doing a local backport, and then seeing 1.7.1 in the running
program, and wondering if I'd actually managed to install my newly built copy or
not.

oscar/VERSION in the upstream/2.1.0 tag from salsa contains 1.7.1, which seems wrong.

This seems not to be an upstream bug, since the repo pointed to by debian/watch
has a v2.1.0 tag, and the version of oscar/VERSION in that tagged commit has
2.1.0 in it, as seen here:

https://gitlab.com/CrimsonNape/oscar-sql/-/blob/82ec7db2ca90f83cf3490d20051e547cf9df4f28/oscar/VERSION

I had a quick look to see if I could find the version of the upstream source
you're actually using, but failed to find a match, so something strange is going
on here -- are you using another repo as upstream?

Meanwhile, https://gitlab.com/CrimsonNape/oscar-sql has recently released v2.1.1
(with that correctly reflected in the oscar/VERSION) so the trivial fix for this
is probably simply to upgrade to that.

BTW the backport to trixie was completely trivial, so if you're already a
backport uploader it would be great if you would add oscar to trixie-backports,
as that would allow stable users to upgrade.

If you're not already a backports uploader, and don't feel the urge to become
one, I'd be happy to handle uploads to trixie-backports if you'd like me to.

Cheers, Phil.