[GitHub] [buildstream] gtristan opened a new issue, #1874: Cannot generate releases from the same commit as prereleases.

["gtristan (via GitHub)" <gi...@apache.org>]

gtristan opened a new issue, #1874:
URL: https://github.com/apache/buildstream/issues/1874

   Since we need to vote on releases, we create "(\d+).(\d+).(\d+).dev(\d+)" release candidates until a vote passes and then create the "(\d+).(\d+).(\d+)" release based on the release candidate with the passing vote.
   
   Having both tags present on the same commit causes issues when building the release tarballs in CI.
   
   As evidenced in this recent pipeline: https://github.com/apache/buildstream/actions/runs/6270069538, we can observe that while building wheels, we were getting `2.1.0.dev0` wheels when a `2.1.0` tag is present.
   
   I have filed an upstream issue as I currently suspect the problem to be either a bug in versioneer, or a misconfiguration of versioneer on our part: https://github.com/python-versioneer/python-versioneer/issues/380
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Cannot generate releases from the same commit as prereleases. [buildstream]

["gtristan (via GitHub)" <gi...@apache.org>]

gtristan commented on issue #1874:
URL: https://github.com/apache/buildstream/issues/1874#issuecomment-1743438298

   @Callek Really appreciate your attention to our project recently :)
   
   I'll see if I can find a way to produce the conditions to reproduce, I was also confused as to why it happens in CI and not on my local machine :-/
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Cannot generate releases from the same commit as prereleases. [buildstream]

["nanonyme (via GitHub)" <gi...@apache.org>]

nanonyme commented on issue #1874:
URL: https://github.com/apache/buildstream/issues/1874#issuecomment-1751803482

   Could this be something related light-weight tags vs annotated tags? I have seen before unexpected behaviour with git figuring out correct tag if tags aren't annotated.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [buildstream] Callek commented on issue #1874: Cannot generate releases from the same commit as prereleases.

["Callek (via GitHub)" <gi...@apache.org>]

Callek commented on issue #1874:
URL: https://github.com/apache/buildstream/issues/1874#issuecomment-1742188345

   Hi Versioneer maintainer here!
   
   I clearly see this in your CI - but I'm having trouble reproducing locally :( I'll have to look closer when I have more time.  Unless someone can try and help produce a simple STEPS TO REPRODUCE that is here or in a different repository. (even if its only able to be reproduced in a github action, having an example live would help - where the tags haven't moved since the issue appeared)
   
   Thanks!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org