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

Skip 'strange' Erlang GitHub release #12

Closed
wants to merge 1 commit into from
Closed

Conversation

walro
Copy link
Contributor

@walro walro commented Sep 16, 2024

There's a weird release at: https://github.com/erlang/otp/releases/tag/patch-base-26 - it makes us barf when trying to parse as a Gem::Version, see https://github.com/cloudamqp/erlang-packages/actions/runs/10880399934/job/30187120021#step:4:10.

Refactor a bit to support all strangeness in one place.

There's a weird release at: https://github.com/erlang/otp/releases/tag/patch-base-26 - it makes us barf when trying to parse as a `Gem::Version`.

Refactor a bit to support all strangeness in one place.
@walro walro force-pushed the skip-strange-release branch from 3924f3f to 735d907 Compare September 16, 2024 14:58
@@ -7,6 +7,14 @@ PLATFORMS = %w[amd64 arm64].freeze
# 24.2 supports OpenSSL 3 and modern gcc/autoconf versions
FIRST_SANE_VERSION = Gem::Version.new("24.2")

def skip_release?(dist:, version:)
return true if version == "patch-base-26"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we have a comment about this? "unparseable version", "not a real release"
Or maybe it is obvious :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was contemplating to add the URL to the release page, but figured it would be in the commit message. I can add something if you'd like

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hehe, they have realized the mistake now and removed it from releases... Question what to do with this change then 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll close this, we can reopen and make adjustment the next time this happens (if it happens). Feels strange to add the indirection (method) for just one case and it will mess with git blame.

@walro
Copy link
Contributor Author

walro commented Sep 17, 2024

Erlang retracted the release, so it's no longer an issue.

@walro walro closed this Sep 17, 2024
@walro walro deleted the skip-strange-release branch September 17, 2024 05:30
@gomoripeti
Copy link
Contributor

FTR comment from the Erlang/OTP team

Any tag that does not have a OTP- prefix you can ignore.

(Such tags) are intentional, but only used to aid with development, so not an actual release. We will push such tags once a year, just as the new major release is done.
It was a mistake to create github releases from the tags though

@walro
Copy link
Contributor Author

walro commented Sep 17, 2024

Ah! Thanks, we should incorporate that then.

Edit: #13

walro added a commit that referenced this pull request Sep 17, 2024
From #12 (comment)

> Any tag that does not have a `OTP-` prefix you can ignore.

We had a problem with a release called "patch-base-26", see #12 for more information.
walro added a commit that referenced this pull request Sep 17, 2024
From #12 (comment)

> Any tag that does not have a `OTP-` prefix you can ignore.

We had a problem with a release called "patch-base-26", see #12 for more information.
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.

3 participants