<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Here are the version number guidelines: <a href="https://www.python.org/dev/peps/pep-0440/">
https://www.python.org/dev/peps/pep-0440/</a></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
2.8.0.1 is allowed (otherwise I couldn't upload it to pypi anyway).</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
There is a 'post-release' 2.8.0post1 one can use.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
If a tag v2.8.0.post1 is less confusing, then I'm happy with that. We would also be happy with a</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
tag like 'pypi2.8.0.1' or we can setup a pypi/2.8.0.1 branch if the tag is somehow the issue.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
All we're asking is for a mechanism to provide upgrades to the pypi packages that allow us to tell users for are now working with a buggy package to simply run
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
pip install --upgrade <br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
to get a bugfix in the same way we would tell C++ users on the release branch to do git pull if we fixed a bug.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We would have preferred to have a well-defined state in the repositories to do that if possible.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Andreas<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Dune-devel <dune-devel-bounces@lists.dune-project.org> on behalf of Markus Blatt <markus@dr-blatt.de><br>
<b>Sent:</b> 26 November 2021 07:40<br>
<b>To:</b> dune-devel@lists.dune-project.org <dune-devel@lists.dune-project.org><br>
<b>Subject:</b> Re: [Dune-devel] vX.Y.Z.alpha tags</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi,<br>
<br>
On Thu, Nov 25, 2021 at 04:21:45PM +0000, Dedner, Andreas wrote:<br>
>Recently we discovered a bug in the 2.8.0 Python packages uploaded to pypi. During the installation of the packages from dune-istl/localfunctions the libs _istl.so/_localfunctions.so are not added to the venv - the install command was missing in the CMakeLists.txt
file. It's fixed now in the release branch.<br>
><br>
>It is not allowed to replace Python packages with new ones using the same version on pypi. So, we can only fix this by uploading a new version. We had the same issue already with dune-fem and just uploaded 2.8.0.1. We would like to do the same with the core
packages to fix this problem. On the other hand, we also only wanted to upload packages that correspond to tagged commits. Consequently, we would like to add a v2.8.0.1 tag to the core modules.<br>
<br>
I think these tags should correspond to releases and a fourth number seems quite uncommon.<br>
<br>
If I understand this correctly, then this tag is needed by pypi only. Have you asked how other projects handel this. Seem like there is<br>
something similar to the Debian packages: post releases <version>-1 or <version>-2 See
<a href="https://www.python.org/dev/peps/pep-0440/#post-releases">https://www.python.org/dev/peps/pep-0440/#post-releases</a><br>
in conjunction with a a tagging scheme different from the usual releases e.g. tag each pypi version like this:<br>
<br>
pypi/v2.8.0 # pypi based on official release<br>
pypi/v2.8.0-1 # pypi official relase with extra patches<br>
pypi/v2.8.0-2<br>
...<br>
<br>
I do not know anything about pypi, but would hope that something like this is possible. (After all there should be others that have the same problem)<br>
<br>
Markus<br>
<br>
<br>
_______________________________________________<br>
Dune-devel mailing list<br>
Dune-devel@lists.dune-project.org<br>
<a href="https://lists.dune-project.org/mailman/listinfo/dune-devel">https://lists.dune-project.org/mailman/listinfo/dune-devel</a><br>
</div>
</span></font></div>
</body>
</html>