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
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
berrange opened a new pull-request against the project: `go-rpm-macros` that you are following:
``
Expose Go build flags directly to spec files as a macro
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/21
eclipseo opened a new pull-request against the project: `go-rpm-macros` that you are following:
``
Fix LDFLAGS macros typos
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/24
The `reg` package [1] is a Golang project needed by fedora-infra team. To prevent it from being retired due to FTB I've taken it [2], but I've found it's a real nightmare trying to fix it (I've got no experience at all with golang).
Is there someone from Go SIG that can help with this? I think it will also need to be renamed to follow current packaging policies... it also seems to have a lot of bundled stuff.
Mattia
[1] https://src.fedoraproject.org/rpms/reg
[2] https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr…
Hello,
we have been talking about the fitness of current meeting slot in the recent past, especially in context of DTS shifts. I would like to start new poll to see if current slot, TZ peg and cadence is still working for us.
Please fill this survey with your availability through out the week so we can select best slot. Please fellow up in this thread about on TZ(DTS) peg, cadence, if you want them to be changed.
https://xoyondo.com/dp/Y9j5f0YpiF0a6fl
For me I think that it would best to not have meeting based on UTC, but CEST TZ(and follow the DTS changes), cadence I think works fine.
Looking forward to the results and feedback,
JC