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

Fix packagecloud repo- and packagename #558

Merged
merged 3 commits into from
Jun 19, 2023
Merged

Conversation

sjaeckel
Copy link
Member

@sjaeckel sjaeckel commented Jun 15, 2023

No description provided.

@sjaeckel
Copy link
Member Author

I'll leave this open for comments on #557

@sjaeckel
Copy link
Member Author

The versioning should be done compliant to https://linux.die.net/man/5/deb-version

@czurnieden
Copy link
Contributor

That could be helpful for MoarVM (I think it's @MasterDuke17 who "represesents" them here?).

https://linux.die.net/man/5/deb-version

For those who have trouble parsing a natural language (e.g.: me ;-) ) it is formally (ABNF)

DECDIGIT     = %x30-39                            ; 0-9
ALNUM        = DECDIGIT / (%x41–5A / %x61–7A)     ; A-Za-z0-9
EXTRA        = %x2e / %x2b / %x7e                 ; '.' period, '+' plus, '~' tilde
COLON        = %x3a                               ; ':' colon
MINUS        = %x2d                               ; '-' minus

EPOCH        = 1*DECDIGIT COLON
DEBREVISION  = MINUS 1*(ALNUM / EXTRA)

UPSTRVER     = DECDIGIT / ALNUM / EXTRA           ; Upstream version number (original version number)

UPVERSION    = 1*DECDIGIT *UPSTRVER                   ; No extras
UPVERSIONEP  = 1*DECDIGIT *(UPSTRVER / COLON)         ; Epoch exists
UPVERSIONDEB = 1*DECDIGIT *(UPSTRVER / MINUS)         ; Debian revision number exists
UPVERSIONALL = 1*DECDIGIT *(UPSTRVER / COLON / MINUS) ; Both, an epoch and a Debian revision number exists

DEBVERSION  =  (EPOCH UPVERSIONALL DEBREVISION)
            =/ (EPOCH UPVERSIONEP             )
            =/ (      UPVERSIONDEB DEBREVISION)
            =/ (      UPVERSION               )

(Please correct me if I made an error)

@sjaeckel sjaeckel changed the title Fix packagecloud reponame Fix packagecloud repo- and packagename Jun 16, 2023
Signed-off-by: Steffen Jaeckel <s@jaeckel.eu>
@sjaeckel sjaeckel force-pushed the deploy-via-gh-actions branch 3 times, most recently from 25f1ea7 to 075091a Compare June 16, 2023 16:32
Those are only used in case we're building on develop.

Signed-off-by: Steffen Jaeckel <s@jaeckel.eu>
@sjaeckel
Copy link
Member Author

For those who have trouble parsing a natural language (e.g.: me ;-) ) it is formally (ABNF)

thx, that's exactly what I needed :D

I've renamed the packages now to libtommath-git resp. libtommath-git-dev if they originate from a non-tagged commit. This also allows us to publish an "official" libtommath resp. libtommath-dev package once we made a new release.

Signed-off-by: Steffen Jaeckel <s@jaeckel.eu>
@sjaeckel sjaeckel merged commit c6a00c2 into develop Jun 19, 2023
79 checks passed
@sjaeckel sjaeckel deleted the deploy-via-gh-actions branch June 19, 2023 18:52
@czurnieden
Copy link
Contributor

thx, that's exactly what I needed :D

So you think that was bold, coming from me of all people? ;-)

…once we made a new release.

Do you want to wait for the projects meant for 2.0 to get ready or do you want an intermediate version? I mean: there are a lot of bugfixes accumulated in develop. I think it is enough for an 1.3.0 although I said otherwise a couple of weeksmonths ago.

And if we do a proper Debian package we need a man-page.

@sjaeckel sjaeckel added this to the v2.0.0 milestone Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants