Hello Christopher,
Am 23.03.25 um 22:52 schrieb Christopher Obbard:
I guess eventually upstream will release 1.0.1 but I don't think it
will be for a long while.
They had a few issues with their github release pipeline last year,
but all seems to be OK now.
if you don't have statement from upstream about there future release
plannings it's just pure guessing what can happen.
Looking at the releases over time I don't have the impression it will
soon come to a release 1.x.
...
I am happy to do that rather than add an epoch; does anyone else have
any opinions ?
> I thought an epoch would be cleaner here personally, but I don't
have any actual upstream Debian packaging experience with epochs.
When developing custom distros with custom (not suitable for Debian)
packages we added them fairly frequently when bootstrapping things
and upstream changing things. But it seems like adding epochs in
Debian is a much more conservative decision? It'd be interesting to
hear more about this, I possibly need some history lesson for real-
world case where adding epoch is dangerous ;-).
Yeah, epochs are for ever, and they confuse the "normal" users often as
they don't understand why they are in the version string.
So maybe another option is to introduce a new src and binary package
that can replace the existing package over time.
Looking at PyPi and into the pyproject.toml file the package seems to
have the real name 'fluster-conformance'.
https://pypi.org/project/fluster-conformance/
https://github.com/fluendo/fluster/blob/master/pyproject.toml#L6
So you could create a new src package with the name
'fluster-conformance' that is providing 'python3-fluster' and uses
Breaks/Replace and optional Provides for fluster.
Once you want to keep the binary name this all will not work because the
version issue plus package name is still the same then!
There is a wiki page existing about how to do some transitions of packages.
https://wiki.debian.org/PackageTransition
I haven't looked at all details so maybe my suggestion is also not
sufficient in the end and using an epoch is still the best solution.
--
Regards
Carsten
