Skip to content

Version string in release archives changes, which makes packaging harder #151

@grembo

Description

@grembo

(tagging @0mp, who is maintaining the FreeBSD port)

VERSION contains a version string that changes based on the state of the archive.

scli/VERSION

Line 1 in d9b38cf

$Format:%h %d$

This means, right after v0.6.5 was released, the file contained:

d2f437a (HEAD -> master, tag: v0.6.5, develop)

later this changed to

d2f437a (tag: v0.6.5).

This results in hashes of artifacts changing, which means package builders relying on those being correct end up not being able to fetch the package - one would think that official artifacts stay the same, but it appears that this might actually not be the case (comparing contents of v0.6.6 and v0.6.5 sources on the release page lead to this assumption).

There a discussion about this here: python-versioneer/python-versioneer#217

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions