On 10.11.2023 03:10, Wookey wrote: Hi Wookey,
I think your options are 1) add an epoch (which exists to deal with this sort of problem)
Well, would like to avoid it, if possible.
2) wait till the next (numerical) release 1.3.9 and upload that.
Do releases happen often? This approach only really makes sense
if you/your users can put up with the old version until a
higher-versioned one appears
About every two years, so not uploading is not really in option.
3) upload a 'nobbled' version number, which is often done to deal
with this sort of temporary issue: 1.3.8a+really1.3.8+dfsg-1
dpkg --compare-versions 1.3.8a+dfsg lt 1.3.8a+really1.3.8+dfsg; echo $?
I'd probably go with option 3 in this case. Ugly but temporary.
Sounds like an option for now. Thanks! Hilmar -- sigfault
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature