non-semver version numbers #36
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…without semver compatible version numbers. If we encounter such a version number, try to pad it with '.0' so that it becomes compatible. One example is: https://ftp-master.debian.org/new/rust-curve25519-dalek_4+20231122+dfsg-2.html That has version number: 4+20231122+dfsg-2
kpcyrd
reviewed
Jan 14, 2024
kpcyrd
approved these changes
Jan 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems like Jonas Smedegaard have started to upload source package without semver compatible version numbers. If we encounter such a version number, try to pad it with '.0' so that it becomes compatible.
One example is: https://ftp-master.debian.org/new/rust-curve25519-dalek_4+20231122+dfsg-2.html
That has version number: 4+20231122+dfsg-2
Fixes #35