You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hifiasm has the following recent tags (release title in parens): 0.17.3 (0.17.3 r452), r458 (0.17.5 r458),... r460 (0.17.6 r460), ..., 0.18.2 (0.18.2 r467). That is to say, the authors seem to switch their tag names between semver-style version triples and a consecutive svn-style commit number. Unfortunately this breaks the autobump logic, as by version order (r460 > 0.18.2).
Is there a way for a recipe meta.yml to limit the allowable tag pattern for autobumping? e.g. one could give \d+\.\d+\.\d+ which would ignore r460 and solve the problem here, at least until the authors go back to using rXXX-style tags.
And does bioconda have an epoch or version prefix, like debian does? e.g. if upstream authors change versioning schemes, debian maintainers can prefix versions with numbers starting at 1 (like 1:0.18.2), which automatically makes them higher than any previous version (e.g. 460), as all unprefixed versions have an implicit 0: prefix, and 1:0.18.2 > 0:460.
Tagging @chhylp123 (hifiasm author) in case they have any comments
Best,
K
The text was updated successfully, but these errors were encountered:
Hello bioconda folks,
hifiasm has the following recent tags (release title in parens):
0.17.3 (0.17.3 r452)
,r458 (0.17.5 r458)
,...r460 (0.17.6 r460)
, ...,0.18.2 (0.18.2 r467)
. That is to say, the authors seem to switch their tag names between semver-style version triples and a consecutive svn-style commit number. Unfortunately this breaks the autobump logic, as by version order (r460
>0.18.2
).Is there a way for a recipe meta.yml to limit the allowable tag pattern for autobumping? e.g. one could give
\d+\.\d+\.\d+
which would ignorer460
and solve the problem here, at least until the authors go back to usingrXXX
-style tags.And does bioconda have an epoch or version prefix, like debian does? e.g. if upstream authors change versioning schemes, debian maintainers can prefix versions with numbers starting at 1 (like
1:0.18.2
), which automatically makes them higher than any previous version (e.g.460
), as all unprefixed versions have an implicit0:
prefix, and1:0.18.2 > 0:460
.Tagging @chhylp123 (hifiasm author) in case they have any comments
Best,
K
The text was updated successfully, but these errors were encountered: