On Thu, May 15, 2025 at 12:51 AM W. Michael Petullo via golang <
golang@lists.fedoraproject.org> wrote:
> > 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/w
On Thu, Mar 20, 2025 at 4:22 PM Zdenek Dohnal via golang <
golang@lists.fedoraproject.org> wrote:
> Hi all,
>
> I maintain two components written in Go, so time to time the components
> get CVE reports where vulnerable code comes from another component via
> static linking during build.
>
> I was
Hi everyone.
TL;DR: Remove a patch we ship in Go that disables GOPROXY and GOSUMDB and
follow upstream defaults, or keep it?
Recently, I had a short conversation in a public forum about two Go
features that we modified in Fedora. GOPROXY and GOSUMDB. As I prepare the
Fedora 40 and Go 1.22 proposa
Hi everyone.
The IRC bridge is down and looks like there is no ETA.
Some of us are on Matrix, and others on IRC, making the group splitted.
(For some reason, libera.chat banned the IP my ISP assigned to me :') )
I was wondering what we should do for the next meetings until the bridge is
back.
Use
Thanks for the notification. That's not good news :(
I guess at that point we should deprecate them. Maybe other repositories
like RPMFusion can take them.
On Fri, Aug 11, 2023 at 7:07 AM Bob Mauchin wrote:
> Hello,
>
> Hashicorp just moved all their products to a non-free license:
> https://ww
Hi everyone!
Currently, golang ships the golang-race package, but this process is
going to get trickier with Go 1.20 due to this change:
The directory $GOROOT/pkg no longer stores pre-compiled package
archives for the standard library: go install no longer writes them,
the go build no longer chec
On Fri, Jan 13, 2023 at 8:55 PM M Hickford
wrote:
>
> `go version -m` prints "Go version and module versions used to build a
> specific executable"
>
> Example from the Go docs https://go.dev/ref/mod#go-version-m
>
> > The -m flag causes go version to print each executable’s embedded module
> >
odle or if my timeslot is really between 3AM-3PM? If so that's a big gap
> in which I really would be available between ~6AM-5PM (America/New_York)
> but I didn't see an option to input my open times.
>
> Is this expected?
>
> Thanks,
> Anthony (anthr76)
> On 8/10/22 1
Hi everyone. As requested multiple times during the Go SIG meetings that we
do at the IRC room, we should try to search for a new time slot.
So we have two things to discuss, the cadence of the meetings and the
schedule.
Cadence poll: https://framadate.org/JsnSXSfqAvwNNMyz
Schedule poll: https:/
Not quite sure but there are a bunch of bugs open and it is marked as FTBFS.
https://bugzilla.redhat.com/show_bug.cgi?id=2097975
https://bugzilla.redhat.com/show_bug.cgi?id=2067435
https://bugzilla.redhat.com/show_bug.cgi?id=2045644
https://bugzilla.redhat.com/show_bug.cgi?id=1977738
https://bugzi
On Wed, Jun 29, 2022 at 11:10 PM Robert-André Mauchin wrote:
>
> Hi,
>
> So the change deadline is very soon, so I'd like a quick answer on this.
>
> So Fedora is dropping i686 in the near future, only plsnning to support Wine
> related thingie
> as far as I know. Could we too make a move toward
Damn! I just found out that you already have liner! My bad. I don't
know why I didn't see it when I was testing delve today...
I'll stop the review, and make a pull request to your repo.
On Wed, Jun 29, 2022 at 10:29 PM Alejandro Saez Morollon
wrote:
>
> Instead of goin
. Fuller, Ph.D.
> ful...@fedoraproject.org
> ful...@mefuller.dev
> @fuller:fedora.im
> @fuller:one.ems.host
> https://www.stossrohr.net
> PGP Fingerprint: 73F1 A30C BDF4 DB4B C75F FD0F D599 E76C FFCA BF60
>
> On 29/06/2022 18:33, Alejandro Saez Morollon wrote:
>
> For ref
you
don't mind, we can co-maintain it if you want.
On Wed, Jun 29, 2022 at 5:33 PM Alejandro Saez Morollon wrote:
>
> For reference:
> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/623JJ43MD6YLLQ737A4K623XIWAYKQTO/
>
> On Wed, Jun 29, 2022
For reference:
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/623JJ43MD6YLLQ737A4K623XIWAYKQTO/
On Wed, Jun 29, 2022 at 5:14 PM Alejandro Saez Morollon wrote:
>
> Hi, I've been working on it because I make theRHEL package and made a
> few co
Hi, I've been working on it because I make theRHEL package and made a
few contributions to the upstream project so I said why not.
But I didn't have enough time. I added two of the dependencies and I
have a working specfile somewhere in my computer but never finished
the process :(
I'll check it o
On Fri, Jun 17, 2022 at 7:03 AM Miroslav Suchý wrote:
>
> I have been asked to add support for Go external dependencies to Mock
>
>https://github.com/rpm-software-management/mock/issues/919
>
> I tried to get the information from
>
> https://developer.fedoraproject.org/tech/languages/go/go-pac
For the record, there's an ongoing conversation in this bug about this
topic:
https://bugzilla.redhat.com/show_bug.cgi?id=2013628
On Tue, Dec 21, 2021 at 10:01 AM Alejandro Saez Morollon
wrote:
>
>
> On Mon, Dec 20, 2021 at 12:36 AM Robert-André Mauchin
> wrote:
>
>&
On Mon, Dec 20, 2021 at 12:36 AM Robert-André Mauchin
wrote:
> On 12/1/21 20:11, Dave Dykstra wrote:
> > What will it take to get golang updated on epel7 from the no longer
> > supported version 1.15? RHEL8.5 reports a long list of security
> > problems that are fixed in 1.16.
> >
> > Dave
>
> J
On Tue, Dec 14, 2021 at 5:01 AM Matthew Miller
wrote:
> On Mon, Dec 13, 2021 at 02:22:24PM +0100, Alejandro Saez Morollon wrote:
> > A hypothetical new release cycle would look like this:
> >
> >- Fedora N release follows Go upstream as close as we can.
> >-
I've been thinking a little about how Go is updated in Fedora. I would like
to hear other opinions about the current state of the releases and improve
it.
This is not related to the Fedora proposal that I'm planning to submit
today regarding the update of Go. I do not pretend to change anything f
On Wed, Dec 1, 2021 at 5:40 PM Matthew Miller
wrote:
> > https://github.com/sourcegraph/src-cli
>
> Okay, so, Jan Kuparinen (copperi) is working on this. I'm happy to sponsor
> him, but I am not up on the state of Go packaging, like, even a little bit.
> Can someone help by reviewing his packages
alexsaezm closed without merging a pull-request against the project:
`go-rpm-macros` that you
are following.
Closed pull-request:
``
Add -trimpath
``
https://pagure.io/go-rpm-macros/pull-request/31
___
golang mailing list -- golang@lists.fedoraprojec
alexsaezm added a new comment to an issue you are following:
``
In that case, I think we can drop this issue and my PR.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/25
___
golang mailing list -- gol
The status of the issue: `Consider using -trimpath` of project: `go-rpm-macros`
has been updated to: Closed by alexsaezm.
https://pagure.io/go-rpm-macros/issue/25
___
golang mailing list -- golang@lists.fedoraproject.org
To unsubscribe send an email to
alexsaezm added a new comment to an issue you are following:
``
After considering it and talking with coworkers about why this flag was not
included before, I think it doesn't make any sense, mainly because Koji builds
in a sanitized build root, so nothing to leak. The same thing goes for
repro
alexsaezm commented on the pull-request: `Add -trimpath` that you are following:
``
After considering it and talking with coworkers about why this flag was not
included before, I think it doesn't make any sense, mainly because Koji builds
in a sanitized build root, so nothing to leak. The same t
alexsaezm added a new comment to an issue you are following:
``
I created a PR with the change in case anyone has suggestions:
https://pagure.io/go-rpm-macros/pull-request/31
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/25
__
alexsaezm commented on the pull-request: `Add -trimpath` that you are following:
``
Any suggestions @eclipseo ? I'm not quite sure about including it in the
`%{?gocompilerflags}` because it is used in `go test` and `-trimpath` is just
for `go build` but I see duplicated flags so not really sure.
alexsaezm opened a new pull-request against the project: `go-rpm-macros` that
you are following:
``
Add -trimpath
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/31
___
golang mailing list -- g
The issue: `Consider using -trimpath` of project: `go-rpm-macros` has been
assigned to `alexsaezm` by alexsaezm.
https://pagure.io/go-rpm-macros/issue/25
___
golang mailing list -- golang@lists.fedoraproject.org
To unsubscribe send an email to golang-l
Hi Denis.
Which package gave you issues? Just to try to build it by myself.
Thanks!
On Wed, Aug 12, 2020 at 10:17 PM Denis Fateyev wrote:
>
> Hello all,
>
> Originally posted to go-sig@, but haven't got any answer, maybe here will be
> better luck.
>
> I have recently tried to rebuild some Gol
Hi, a few days ago, I requested a repository[0] for a new Fedora package[1].
However, it seems the reviewer is not a packager, and therefore, the
repository request is not valid.
Can someone take a look at it? Thanks!
Kind regards.
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1803223
[1] http
33 matches
Mail list logo
