This is a native package and we are not doing anything special,
just the data update from the upstream project.
Thereby the delta we apply is worthwhile, but none to retain
if there is a newer Debian upload as it would surely contain
the same or newer.
There also is a Debian PR [1] proposing the same and we have
intentionally chosen to not use the data of "today", but that
as proposed in Debian to increase the chance to order before
that potential upload.
Therefore I have intentionally chosen a versions which allows
subsequent Debian upload to auto-sync over this following the
discussion on [2].
The little extra twist in this cases is that, being a native
version matching the data files content, I need to pick a
version that starts with 2023112702. But need to stay ahead
in case Debian uploads just that version. So I need to use
a "~" before maysync1.
The special way this package is created with the native
version matching the data file content ensures that any
upload at or above this version will have the delta we
added in this upload.
This is the change as proposed to Debian right now [1].
Preferring that over the data of today allows us to auto-sync
a potential upload in Debian which would be fine as this is
just a data change following upstream, but not a delta to
be retained.