nim reported a new issue against the project: `go-rpm-macros` that you are following:
``
The macro code needs massaging to also work on EPEL.
Most of the work is spec side since some of the macros are going to collide with the ones provided by previous iterations of Go macro packages
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/2
nim reported a new issue against the project: `go-rpm-macros` that you are following:
``
`%goprep` should apply patches automatically, so there is no convenience gap with `%autosetup`.
This is generic work that should be done *redhat-rpm-config* side in forge macros and then reused in`%goprep`. Basically:
1. define a `patch_flags<suffix>` rpm variable holding the parameters that should be passed to `%patch<suffix>`
2. define a `default_flags<suffix>` fallback
3. define a `source_patches<suffix>` holding an ordered space separated list of patch suffixes associated with a particular forge/go source.
And then write the usual lua loops to apply it all at the right moment in the spec.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/3
eclipseo reported a new issue against the project: `go-rpm-macros` that you are following:
``
When packaging: `code.gitea.io/tea`
The goname is reduced to `golang-codeea-tea`
Also the download link is wrong: it is resolved to
`https://gitea.com/gitea/tea/archive/0.7.0.tar.gz`
whereas it should be
`https://gitea.com/gitea/tea/archive/v0.7.0.tar.gz`
Can someone with knowledge of Lua regex fix this?
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/32
qulogic opened a new pull-request against the project: `go-rpm-macros` that you are following:
``
Use --with-tests when running checks also.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/20
atodorov opened a new pull-request against the project: `go-rpm-macros` that you are following:
``
macros: Accept options for %gotest
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/23
Hello,
I haveforgotten to send this out earlier. It happened that the currentmeeting slot doesn't fit us all any more. Under following link issurvey to find slot that would work for us on representativeweek. https://omnipointment.com/qZXRskVES1lGmEi8qCrT
Otherquestion is if the cadence is right. Meeting every two weeks? And thelast question is the location of the meeting. With the Freenode dramathere seems to be push to move off of it. Do we still want to meetover IRC where ever the Fedora will move? Do we want to move to thematrix? Or my shill, start maybe even informally, meet on some Jitsiinstance once a certain period?
Sorry forsending this out late. I think we can skip today meeting as there areno new issues, updates available, but I will be around if more of uswill turn up or there are some pressing issues to discuss.
Please fillthe servey and if you would like some changes to the place or cadencespeak up here. Looking forward to the feedback and responses,
Jakub Čajka