Skip to content

Versioned source tarball not available through github #111

@matthijskooijman

Description

@matthijskooijman

I just tried to update the Debian package, using the github-generated tarball, but I ran into problems there because there is no nml/__version__py inside (since the tarball is just a direct snapshot from the git repo).

It seems pypi does have the correct tarball (as generated by the release flow), so I could check for updates there, but I suspect people might be looking at the releases tab in github there. So maybe the same tarball should be published on Github?

If that sounds good, I guess the release flow should be updated.

For the Debian package, it would also be good if the existing tarball from pypi could be added to the 0.5.0 release, so I can update my watch file accordingly (the filename should remain consistent with what the release flow will use, but the nml-0.5.0.tar.gz filename sounds fine? Or would you want a more explicit nml-source-0.5.0.tar.gz maybe?).

If this could be settled in the coming two days, that would be awesome, then I can still include in the upload for 0.5.0.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions