Merge branch 'master' of ssh://git-annex.branchable.com

This commit is contained in:
Joey Hess 2021-08-09 15:20:19 -04:00
commit a331321d2a
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 26 additions and 0 deletions

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="standalone build version vs standard release version"
date="2021-08-09T17:28:31Z"
content="""
Sorry if I'm being dense here, but the version mismatch issue also [[affects|forum/standalone_tarballs_for_specific_versions]] the [[conda build|install/conda]], so I want to better understand the underlying issue. What makes it necessary for the standalone version to be built from a different git commit than the standard version? If \"The two commits are whitespace changes and the commit that increased the version number\", could these commits be made before the official release is tagged?
"""]]

View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="yarikoptic"
avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
subject="comment 4"
date="2021-08-09T17:34:39Z"
content="""
> ... you can build against the release tag if you wish.
well, FWIW we do that AFAIK in https://github.com/datalad/git-annex , but those are non-official builds. And echoing Ilya, this issue was about an official distribution repository which is used for conda-forge \"no proper build, just grab a standalone\" version of a package.
"""]]

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="yarikoptic"
avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
subject="comment 2"
date="2021-08-09T17:58:55Z"
content="""
damn, sorry for the noise and thanks for the link -- something was nagging in the back of my head, but I didn't listen ;)
"""]]