Closed forquare closed 2 years ago
I've been using this method for a few www/gohugo releases and have found it to work well. I haven't tried this on any other Go based ports, so it hasn't been truly battle-tested!
Looks like an issue with the M2T_GITHUB
secret is causing CI to fail 😞
Hi,
Thanks for the PR. Unfortunately, it breaks tests e.g.
--- FAIL: TestGithubLookupTag (0.84s)
github_test.go:46: expected tag v1.3.4, got /v1.3.4 (example 0)
github_test.go:46: expected tag v1.1.7, got /v1.1.7 (example 3)
also there are some e2e test failures later that I haven't looked at yet.
🤦 I am very sorry! I completely forgot to run the tests!. I'll look myself and I'll try to find some time to sort them out
Hi Ben,
I looked at what modules2tuple generates for www/gohugo and how it is different from the actual GH_TUPLE, and it seems that there's a fair amount of manual work involved with each gohugo update.
Why not just switch to the GO_MODULE? Here's my take on it, it's shorter and needs only DISTVERSION bump for the update.
Edit: vendor/github.com/bep/golibsass/internal/libsass/a__cgo.go
also needs hardcoded cgo flags patched out, I can submit the complete diff to Bugzilla if you'd like.
Hey Dmitri,
I had tried using GO_MODULE but hit upon the libsass issue and wasn't sure how to solve it. If you would be able to submit a diff to Bugzilla that would be awesome - it will certainly reduce the effort of bumping this port!
Sure, will do that shortly.
Closing this PR as we've solved my particular issue by moving to GO_MODULE.
If a repo (like https://github.com/aws/aws-sdk-go-v2) has too many tags, doing a lookup of all tags results in a 502.
In a number of cases I found that the path is actually part of the tag, so we can try that to see if we can find the tag and reduce the number of times we might try getting all tags.