Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing PyPI packages for v2.0.58 #8537

Closed
dbaio opened this issue Feb 14, 2019 · 5 comments
Closed

Missing PyPI packages for v2.0.58 #8537

dbaio opened this issue Feb 14, 2019 · 5 comments
Assignees
Labels
Packaging/Pip question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@dbaio
Copy link

dbaio commented Feb 14, 2019

Hi.

There aren't available PyPI packages for version 2.0.58.

I packaged azure-cli for FreeBSD and I noticed that our track system (portscout) didn't find this new version.

We fetch packages from PyPI like this way:

https://files.pythonhosted.org/packages/source/a/azure-cli/azure-cli-2.0.57.tar.gz

And that's the way we track for upstream updates (guessing new versions).

Thank you for your time.

Regards.

@tjprescott tjprescott added Packaging/Pip question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Feb 14, 2019
@tjprescott
Copy link
Member

When I run pip install azure-cli I get version 2.0.58 with all the appropriate modules. All of the packages do appear at PyPI.org.

@tjprescott
Copy link
Member

@marstr did we change anything about what we publish with twine?

@dbaio
Copy link
Author

dbaio commented Feb 14, 2019

Well, there is something strange, in the download page there aren't a .tar.gz file.

See this:

https://pypi.org/project/azure-cli-core/2.0.57/#files

https://pypi.org/project/azure-cli-core/2.0.58/#files

@marstr
Copy link
Member

marstr commented Feb 15, 2019

Hmmm, I handled the PyPI release process for both 2.0.57 and 2.0.58. I don't believe that there was any difference in procedure. Let me investigate.

@marstr
Copy link
Member

marstr commented Feb 15, 2019

I've mitigated this issue by downloading the PyPI artifacts from the 2.0.58 build and using twine to upload all non-existing assets from my local machine.

I verified that the previous build 2.0.57 seems like it has the same artifact structure.

I did check the most recent PyPI release logs. Like with 2.0.57, there were some gremlins in our new release system that had meant I had to execute this step manually from my machine. My guess is that when I executed twine I used a wildcard like *.whl instead of just * when I executed locally.

However, the gremlins from the release were tracked in issue #8507, and we should not have to resort to manual execution next time.

@marstr marstr closed this as completed Feb 15, 2019
@haroldrandom haroldrandom added Packaging/Pip question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Oct 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Packaging/Pip question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

4 participants