eclipseo merged a pull-request against the project: `go-rpm-macros` that you
are following.
Merged pull-request:
``
Disable Markdown files installation
``
https://pagure.io/go-rpm-macros/pull-request/58
___
golang mailing list --
eclipseo opened a new pull-request against the project: `go-rpm-macros` that
you are following:
``
Disable Markdown files installation
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/58
___
eclipseo added a new comment to an issue you are following:
``
This is fixed in latest golist
https://pagure.io/golist/c/4a2511bb0089458eef3b78acc0f1dbc264c9c15a?branch=master
Also update to go2rpm 1.10.0 for your templates.
``
To reply, visit the link below or just reply to this email
eclipseo merged a pull-request against the project: `golist` that you are
following.
Merged pull-request:
``
Exclude .md files by default
``
https://pagure.io/golist/pull-request/33
___
golang mailing list -- golang@lists.fedoraproject.org
To
eclipseo opened a new pull-request against the project: `golist` that you are
following:
``
Exclude .md files by default
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/pull-request/33
___
golang mailing list --
eclipseo reported a new issue against the project: `golist` that you are
following:
``
We shouldn't install md files by default.
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/32
___
golang mailing list --
eclipseo merged a pull-request against the project: `go-rpm-macros` that you
are following.
Merged pull-request:
``
Fix goname generation to match versioning guildelines
``
https://pagure.io/go-rpm-macros/pull-request/56
___
golang mailing list --
eclipseo commented on the pull-request: `Fix goname generation to match
versioning guildelines` that you are following:
``
Could you add the comment on teh go2rpm MR? I'd like to do both at once
``
To reply, visit the link below or just reply to this email
eclipseo commented on the pull-request: `Fix goname generation to match
versioning guildelines` that you are following:
``
@gotmax23 @alexsaezm
Could you check again the current situation:
- we got the -L flag that enable go_use_new_versioning
- go_use_new_versioning allow to add more
eclipseo commented on the pull-request: `Fix goname generation to match
versioning guildelines` that you are following:
``
Also this was tested in COPR with no changes in the packages names. We can ask
for a mass rebuilt in a side tag if necessary.
``
To reply, visit the link below or just
eclipseo commented on the pull-request: `Fix goname generation to match
versioning guildelines` that you are following:
``
> I made it so it always uses a _ to separate a version from the import path
> when go_use_new_versioning is set and otherwise use a -. Did I not understand
> what the FPC
eclipseo commented on the pull-request: `Fix goname generation to match
versioning guildelines` that you are following:
``
> This is likely to cause confusing behavior across branches and other issues
Unlikely, we know the list of packages that will be affected and we just need
update theses
eclipseo commented on the pull-request: `Fix goname generation to match
versioning guildelines` that you are following:
``
I disagree, the default behavior should be the ones which respect the
guidelines, and the flag should be added to the incorrect packages.
The exception should be the
eclipseo commented on the pull-request: `Fix goname generation to match
versioning guildelines` that you are following:
``
@gotmax23 Can I have you feedback as soon as possible on these changes?
``
To reply, visit the link below or just reply to this email
Hello folks,
So, following the ticket to the packaging-commitee:
https://pagure.io/packaging-committee/issue/1307
The summary of the meeting is the following:
We discussed this during today's meeting, and there was consensus for two
things:
we don't like that package Name is controlled
eclipseo opened a new pull-request against the project: `go-rpm-macros` that
you are following:
``
Fix goname generation to match versioning guildelines
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/56
eclipseo closed without merging a pull-request against the project:
`go-rpm-macros` that you
are following.
Closed pull-request:
``
Fix goname generation to match versioning guildelines
``
https://pagure.io/go-rpm-macros/pull-request/55
___
golang
eclipseo commented on the pull-request: `Fix goname generation to match
versioning guildelines` that you are following:
``
https://pagure.io/packaging-committee/issue/1307
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/55
eclipseo commented on the pull-request: `Fix goname generation to match
versioning guildelines` that you are following:
``
> We cannot change this without breaking many packages
Package won't be broken because they will be superseeded by the replacement
with Provides/Obsoletes.
Packages will
eclipseo commented on the pull-request: `Fix goname generation to match
versioning guildelines` that you are following:
``
Problem is:
- I need to request new compat package on fedora-scm-requests
- @tibbs won't approve package with -version anymore
- thus if i want the package approved, i
eclipseo commented on the pull-request: `Fix goname generation to match
versioning guildelines` that you are following:
``
Testing is in progress.
The goal would be to recreate new repos and retire the older ones.
``
To reply, visit the link below or just reply to this email
eclipseo opened a new pull-request against the project: `go-rpm-macros` that
you are following:
``
Fix goname generation to match versioning guildelines
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/55
On 8/26/23 12:11, Mark E. Fuller wrote:
Dear Go-list (and broader Fedora dev list),
I've been dragging on getting an update to go-task done - I need to request a (re)review of
golang-github-google-renameio-2 (https://bugzilla.redhat.com/show_bug.cgi?id=2231733) as a
dependency of
eclipseo opened a new pull-request against the project: `go-rpm-macros` that
you are following:
``
Add option to ignore directories in go_generate_buildrequires
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/54
eclipseo reported a new issue against the project: `go-rpm-macros` that you are
following:
``
Very occasionally I need to bypass some BR to vendor some stuff. It would be
neat to be able to pass -t / - d / -r to %go_generate_buildrequires for it to
be passed to the golist call:
```
Hello,
I need help to review the ORAS stack needed for Ariga and others:
https://bugzilla.redhat.com/show_bug.cgi?id=2140707 Review Request:
golang-github-need-being-tree - Pretty print trees in Go
https://bugzilla.redhat.com/show_bug.cgi?id=2140708 Review Request: golang-oras - Work with
OCI
On 9/22/22 01:10, Maxwell G wrote:
On Fri Sep 2, 2022, Maxwell G via devel wrote:
Sep 2, 2022 5:36:41 AM Fabio Valentini :
Does anybody know whether olem still wants to maintain their Fedora
packages?
I'm fairly sure that they no longer wish to maintain Fedora packages. I
reached out to
Hello,
Go2rpm 1.7.0 has been published, featuring:
- Use of SPDX licenses
- Automatic Generation of RPM Release Fields and Changelogs are now the
default. (-r flag)
- By default, the cache for chosen Go import path is now cleaned. (-C flag)
Best regards,
Robert-André
eclipseo commented on the pull-request: `Introduce %golang_arches_future and
stop using %go_arches` that you are following:
``
lgtm, although, won't we need to go back to all the -f created once we are out
of ix86 completely?
``
To reply, visit the link below or just reply to this email
Hi,
I'd like to recommend you to switch to SPDX for your license fields.
Please intervene on any spec you create or edit.
The license conversion should be disabled in go2rpm and then the rust2rpm dependencies
should be dropped at a later date.
Thank you.
Robert-André
On 6/27/22 19:38, Robert-André Mauchin wrote:
Thread to send your Golang package reviews which are waiting... reply to this thread so we
can sync up our efforts.
Best regards
Robert-André
I have a new baby https://bugzilla.redhat.com/show_bug.cgi?id=2103460
Pretty please, will take yours
eclipseo commented on the pull-request: `Use Fedora's build flags for cgo.`
that you are following:
``
Thanks so much for your hard work!
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/47
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 this by dropping %ix86 from our supported
arches?
Most Go dev don't
eclipseo commented on the pull-request: `Use Fedora's build flags for cgo.`
that you are following:
``
I agree, if you have a copr with more packages it would help. I can look into
it at one point too.
``
To reply, visit the link below or just reply to this email
Thread to send your Golang package reviews which are waiting... reply to this thread so we
can sync up our efforts.
Best regards
Robert-André
___
golang mailing list -- golang@lists.fedoraproject.org
To unsubscribe send an email to
eclipseo merged a pull-request against the project: `golist` that you are
following.
Merged pull-request:
``
Don't skip testdata
``
https://pagure.io/golist/pull-request/30
___
golang mailing list -- golang@lists.fedoraproject.org
To unsubscribe
eclipseo commented on the pull-request: `Don't skip testdata` that you are
following:
``
Hmmm, in general I add them manually but ok.
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/pull-request/30
___
golang
eclipseo merged a pull-request against the project: `go-rpm-macros` that you
are following.
Merged pull-request:
``
srpm/go.lua meta: Set `%gourl` after `forge.meta` call
``
https://pagure.io/go-rpm-macros/pull-request/45
___
golang mailing list --
eclipseo added a new comment to an issue you are following:
``
I've rebased the PR.
Not sure which packages will need fixing after that.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/36
___
golang
eclipseo commented on the pull-request: `Stop using deprecated
%__global_ldflags macro.` that you are following:
``
LGTM.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/44
___
golang mailing
eclipseo commented on the pull-request: `Stop using deprecated
%__global_ldflags macro.` that you are following:
``
Isn't there an extra } here and below?
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/44
eclipseo commented on the pull-request: `Stop using deprecated
%__global_ldflags macro.` that you are following:
``
LGTM.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/44
___
golang mailing
eclipseo commented on the pull-request: `Undefine _auto_set_build_flags in
%gocheck definition` that you are following:
``
LGTM :thumbsup:
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/42
eclipseo commented on the pull-request: `Undefine _auto_set_build_flags in
%gocheck definition` that you are following:
``
Thanks for adding the expand.
Will be testing soon.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/42
eclipseo opened a new pull-request against the project: `go-rpm-macros` that
you are following:
``
Convert LDFLAGS to GOLDFLAGS and BUILTAGS to GOBUILDTAGS
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/41
eclipseo commented on the pull-request: `Try again to fix failures with
https://fedoraproject.org/wiki/Changes/SetBuildFlagsBuildCheck` that you are
following:
``
Yes I have version 3.0.14-1.fc36 from the f36 repo:
https_kojipkgs_fedoraproject_org_repos_f36_build_latest_basearch
``
To reply,
eclipseo commented on the pull-request: `Try again to fix failures with
https://fedoraproject.org/wiki/Changes/SetBuildFlagsBuildCheck` that you are
following:
``
@gotmax23 @tstellar This is not working for me in %check:
https://copr.fedorainfracloud.org/coprs/eclipseo/gotests2/build/3259438/
eclipseo commented on the pull-request: `Fix build failures due to
https://fedoraproject.org/wiki/Changes/SetBuildFlagsBuildCheck` that you are
following:
``
> > It looks like this change did not work as expected.
> > `%{golang_filter_ldflags}` seems to expand to an empty string.
>
> Rpm
eclipseo merged a pull-request against the project: `go-rpm-macros` that you
are following.
Merged pull-request:
``
Fix gotest ldflags invocation
``
https://pagure.io/go-rpm-macros/pull-request/39
___
golang mailing list --
eclipseo opened a new pull-request against the project: `go-rpm-macros` that
you are following:
``
Fix gotest ldflags invocation
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/39
___
golang
eclipseo added a new comment to an issue you are following:
``
Ok, I am partisan of solution 1.
The state of the current macros regarding this provoked the mass failures with
have seen due to the introduction of relro which is not recognized by the
Golang compiler.
What is the scope of this
eclipseo merged a pull-request against the project: `go-rpm-macros` that you
are following.
Merged pull-request:
``
Fix build failures due to
https://fedoraproject.org/wiki/Changes/SetBuildFlagsBuildCheck
``
https://pagure.io/go-rpm-macros/pull-request/38
eclipseo commented on the pull-request: `Fix build failures due to
https://fedoraproject.org/wiki/Changes/SetBuildFlagsBuildCheck` that you are
following:
``
There is no problem with your patch. I will push it.
I'll try fixing our LDFLAGS problem later,
``
To reply, visit the link below or
eclipseo commented on the pull-request: `Fix build failures due to
https://fedoraproject.org/wiki/Changes/SetBuildFlagsBuildCheck` that you are
following:
``
We may have a problem on some packages. For some of them we redefine LDFLAGS:
eclipseo commented on the pull-request: `Fix build failures due to
https://fedoraproject.org/wiki/Changes/SetBuildFlagsBuildCheck` that you are
following:
``
Thank you kindly!
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/38
eclipseo commented on the pull-request: `Fix build failures due to
https://fedoraproject.org/wiki/Changes/SetBuildFlagsBuildCheck` that you are
following:
``
This is hackish.
Please also modify the gotest line
```
-%gotest() %{?gomodulesmode} go test %{gotestflags} -ldflags "${LDFLAGS:-}
On 1/10/22 07:04, Maxwell G wrote:
Hi everyone,
I recently became a co-maintainer of gh, and I noticed that the package's
`%goipath` is incorrectly set to `github.com/cli/cli` when, according to the
go.mod, it should be `github.com/cli/cli/v2`. How should I go about correcting
this? We have
eclipseo merged a pull-request against the project: `go-rpm-macros` that you
are following.
Merged pull-request:
``
srpm/go.lua: fix handling of version numbers with multiple digits
``
https://pagure.io/go-rpm-macros/pull-request/37
___
golang
On 12/6/21 12:42, Mikel Olasagasti wrote:
Hi all,
I was updating some golang specs I've and switching them to use
go_generate_buildrequires.
I realized that some specs that are using it fail to build if `%global
debug_package %{nil}` is not set. Same spec with all BuildRequires
defined works
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
Jakub or Alex, do you know whose prerogative is this?
Best regards,
Robert-André
On 6/25/21 8:32 PM, Link Dupont wrote:
to support the git.sr.ht forge.
See
https://src.fedoraproject.org/rpms/golang-sr-sircmpwn-getopt/blob/rawhide/f/golang-sr-sircmpwn-getopt.spec
for example on how to support it.
It should go like this:
# https://git.sr.ht/~spc/mqttcli
%global goipath
On 5/24/21 2:37 PM, Jakub Čajka wrote:
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.
eclipseo added a new comment to an issue you are following:
``
> The `v` prefix depends on if upstream decided to add it, but it's not
> necessarily a thing that must happen. @nim decided to default to adding it,
> but that can be overridden by setting `tag`. Are you setting `%global tag
>
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
eclipseo commented on the pull-request: `Add -trimpath` that you are following:
``
I've tested some builds in a COPR:
https://copr.fedorainfracloud.org/coprs/eclipseo/trimpath/builds/
They all fail, apparently no debuginfo are generated.
``
To reply, visit the link below or just reply to this
eclipseo commented on the pull-request: `Add -trimpath` that you are following:
``
You should probably edit %gobuildflags() too?
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/31
___
golang
eclipseo commented on the pull-request: `Add -trimpath` that you are following:
``
This seems okay to me as is, but I don't know if it could affect the builds. A
beta test in COPR might be useful.
``
To reply, visit the link below or just reply to this email
eclipseo added a new comment to an issue you are following:
``
Ping @alexsaezm Could you cut a new release once you fix this. I've merged the
change regarding the tilde handling, it is needed by people packaging from
SourceHut.
``
To reply, visit the link below or just reply to this email
The status of the issue: `LDFlags Macro Typos` of project: `go-rpm-macros` has
been updated to: Closed by eclipseo.
https://pagure.io/go-rpm-macros/issue/19
___
golang mailing list -- golang@lists.fedoraproject.org
To unsubscribe send an email to
eclipseo merged a pull-request against the project: `go-rpm-macros` that you
are following.
Merged pull-request:
``
srpm/go.lua: avoid remove char 'v' from project name
``
https://pagure.io/go-rpm-macros/pull-request/29
___
golang mailing list --
eclipseo commented on the pull-request: `srpm/go.lua: avoid remove char 'v'
from project name` that you are following:
``
This change will need to be matched in go2rpm.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/29
eclipseo merged a pull-request against the project: `go-rpm-macros` that you
are following.
Merged pull-request:
``
fix: missing space to separate args
``
https://pagure.io/go-rpm-macros/pull-request/30
___
golang mailing list --
eclipseo merged a pull-request against the project: `go-rpm-macros` that you
are following.
Merged pull-request:
``
Remove tildes from goname
``
https://pagure.io/go-rpm-macros/pull-request/26
___
golang mailing list --
On 2/24/21 9:24 PM, Ben Cotton wrote:
Hi Robert-André and Go SIG,
There has been no progress on the Patches in Forge macros change[1],
so FESCo deferred it to Fedora 35. Since nim hasn't been seen in a
while and you were interested in getting this implemented, would you
be willing to take this
Hi,
To my knowledge, in the future Go modules macros (which will hopefully
be available at some point in the future), we won't be able to pass -d
or -t to %gocheck to disable some test directory. In order to tackle the
problem of failing tests, I devised an alternative method to disable
On 12/22/20 2:52 PM, Jakub Cajka wrote:
- Original Message -
From: "Robert-André Mauchin"
To: golang@lists.fedoraproject.org
Cc: "Jakub Čajka"
Sent: Tuesday, December 22, 2020 3:53:12 AM
Subject: Golang 1.16
Hello Jakub,
I wanted to ask you at the meetin
Hello Jakub,
I wanted to ask you at the meeting, how is the update to Golang 1.16
shaping up? Have you tested it on a small batch of packages? Should we
expect breaking changes from upstream again?
Best regards,
Robert-André
___
golang mailing
Hi,
Following the discussion we had at the meeting, it would be great if we
had the new tooling in F34. As you may know, RHEL9 will be based off
F34; we already missed the mark for RHEL8 which still doesn't support
our current macros, so we have to bundle everything.
I don't expect we will
See:
https://utcc.utoronto.ca/~cks/space/blog/programming/GoModulesOnlyFuture
I guess we'll need to switch too! I don't know if we're readyk
Best regards,
Robert-André
___
golang mailing list -- golang@lists.fedoraproject.org
To unsubscribe send an
eclipseo added a new comment to an issue you are following:
``
Have you tried redefining gomodulesmode in your SPEC:
%global gomodulesmode GO111MODULE=on
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/28
On Monday, 2 November 2020 22:45:09 CET Olivier Lemasle wrote:
> Hi all,
>
> I have two questions related to the packaging of Go modules.
>
> 1. When a new major version of a Go module is released, breaking backwards
> compatibility, the module path should be changed [1].
> According to the
On Friday, 2 October 2020 20:55:42 CEST Neal Gompa wrote:
>
> This is cool! Would you mind creating a repo under pagure.io/GoSIG
> namespace to put this script and keep track of it? That way we have it
> and can easily contribute to it too. :)
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one
Hi,
I wrote a quick and dirty Python 3 script to track upstream package version
including last GIT commit and commit date, so you can compare Hedora's version
with upstream. This is slightly better than Anitya as it supports commit.
It takes as input a file containing one Fedora package per
On Thursday, 24 September 2020 02:26:11 CEST Edd Salkield wrote:
> Hi all,
>
> I'm currently working on packaging github.com/writeas/writefreely, a
> platform for building writing spaces. Some of its dependencies are
> currently not packaged for Fedora, so I'm seeking some advice on the
>
On Tuesday, 1 September 2020 01:03:57 CEST Germano Massullo wrote:
> Good day everybody. As some from #fedora-golang channel may know, Fabian
> Affolter and I, we are releasing for the first time Bettercap to Fedora
> repository. By the way we are getting this build error and we have no
> idea
Hi,
dep is FTBFS, and I wonder if this is still useful to package it? It's not
maintained upstream and I think it has been obsoleted by Go modules.
Do we still have customers for it?
Please give me your opinions.
Best regards,
Robert-André
___
Hello,
So I have checked 1657 golang- packages (around 1343 "active"), with a rate of
35-40 of updated package per 100 packages.
A few new bugs for updating already cropped up though.
However to update the remaining packages, I have 78 new packages to import.
The TODO list:
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
___
golang
eclipseo commented on the pull-request: `Handle tests outside packages
correctly.` that you are following:
``
Yeah I'm slowly working my way through the FTBFS, will probably need some help
with reviews for new dep.
``
To reply, visit the link below or just reply to this email
Hello,
I have 2 new dependencies for Rclone in needs of a review:
Review Request: golang-github-jzelinskie-whirlpool - Whirlpool cryptographic
hashing library
https://bugzilla.redhat.com/show_bug.cgi?id=1755566
Review Request: golang-github-putdotio-putio - Put.io Go API client
Hello,
Feel free to help review these packages needed to update Hugo:
* 1742352 • hugo-0.57.2 is available[1]
* 1743048 • Review Request: golang-github-niklasfasching-org - Org
mode parser
with html & pretty printed org rendering[2]
* 1744238 • Review Request:
Hello,
I need your help to review these Go packages:
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED=Fedora=Package%20Review=zebob.m%40gmail.com=1=substring_id=10401033=Fedora_format=advanced
They are needed to update others or fix FTBFS. I'd love to be able to get
Hello,
I need your help to review these packages:
https://bugzilla.redhat.com/buglist.cgi?
bug_status=NEW_status=ASSIGNED=Fedora=Package%20Review=zebob.m%40gmail.com=1=substring_id=10378477=Fedora_format=advanced
They are needed to update others or fix FTBFS.
On Wednesday, 10 July 2019 02:45:42 CEST you wrote:
> Hello,
>
> I finished building the last package tonight and will be busy with life for
> the upcoming months. So here's a TODO for the remaining stuff that needs
> work.
>
> I've assigned go-sig to all the new packages in dist-git, added them
Hello,
I finished building the last package tonight and will be busy with life for the
upcoming months. So here's a TODO for the remaining stuff that needs work.
I've assigned go-sig to all the new packages in dist-git, added them to
Koschei and added most of them to Anitya.
Some package
eclipseo commented on the pull-request: `Always install SFiles whatever the
arch` that you are following:
``
Used:
```
Value: {".proto", ".md", ".s"},
```
We're still using the v1 of urfave/cli. v2 never caught up and the whole
project seems abandoned since 2016.
eclipseo commented on the pull-request: `Always install SFiles whatever the
arch` that you are following:
``
It seems the "other files" are not included by default but need to be specified
with --include-extension.
``
To reply, visit the link below or just reply to this email
eclipseo commented on the pull-request: `Always install SFiles whatever the
arch` that you are following:
``
Tested and it doesn't work.
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/pull-request/25
___
golang
eclipseo commented on the pull-request: `Always install SFiles whatever the
arch` that you are following:
``
> I assume you checked it builds and works
I haven't. But I assume it would work.
``
To reply, visit the link below or just reply to this email
https://pagure.io/golist/pull-request/25
eclipseo added a new comment to an issue you are following:
``
https://pagure.io/golist/pull-request/25
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/17
___
golang mailing list --
1 - 100 of 137 matches
Mail list logo
