New version of Hugo, new dependencies

I have some review requests for Go packages that are required for Hugo 0.140.1: https://bugzilla.redhat.com/show_bug.cgi?id=2334845 https://bugzilla.redhat.com/show_bug.cgi?id=2334847 https://bugzilla.redhat.com/show_bug.cgi?id=2334848 Additionally, I have a merge request pending for the gitmap p

Re: New version of Hugo, new dependencies

>> I have some review requests for Go packages that are required for Hugo >> 0.140.1: >> https://bugzilla.redhat.com/show_bug.cgi?id=2334845 > Needs some changes. Revision published to original bug report. Thank you for the quick work! The Hugo 0.140.2 package is ready, pending me completing th

Re: Heads-up: Go 1.24 causing widespread FTBFS in F42

Thank you for the heads up. I fixed the Hugo package, and I proposed a patch upstream: https://github.com/gohugoio/hugo/pull/13285 -- Mike :wq -- ___ golang mailing list -- golang@lists.fedoraproject.org To unsubscribe send an email to golang-le...@l

Re: New version of Hugo, new dependencies

> FYI, members of Go-SIG plan to propose vendoring dependencies as the > default method to package Golang packages. > > This is the draft of the document: > https://fedoraproject.org/wiki/Changes/GolangPackagesVendoredByDefault I would like to experiment with go2rpm's vendor profile. I am trying

New version of Hugo, new dependencies

I have some review requests for Go packages that are required for Hugo 0.147.3: https://bugzilla.redhat.com/show_bug.cgi?id=2366312 https://bugzilla.redhat.com/show_bug.cgi?id=2366320 I have COPR builds of all of this, including the new Hugo package and an update to the existing golang-github-bep

Re: New version of Hugo, new dependencies

> In this case, I think you should point to the LICENSE file at the top level > of the project -> > https://github.com/gohugoio/testmodBuilder/blob/master/LICENSE This file is not in the version of the repository pulled by go2rpm. However, I figured out that I can place it in the root of the packa

Re: Hugo go-vendor-tools package

> > Sorry for the late replies, I've been busier than expected last week. > > For that error I found that Brad already hit the same issue in > https://github.com/cri-o/cri-o/issues/8860#issuecomment-2558287657 and > fixed by applying "%global __golang_extldflags -Wl,-z,undefs" after > %build in

Hugo go-vendor-tools package

Mikel, I am still experimenting with building a Hugo package using go-vendor-tools. I have had some success, but the github.com/tetratelabs/wazero dependency is causing problems. Looking at the wazero .spec, the build has some special requirements, but I do not know how to apply these to wazero as