gotmax23 opened a new pull-request against the project: `go-rpm-macros` that you are following:
Introduce %golang_arches_future and stop using %go_arches
To reply, visit the link below or just reply to this email
I've started to see very strange build failures of syncthing since the
update from go 1.18 to 1.19:
I've looked at build logs, but there's no obvious source of a problem
that I can see in the usual "megabyte-sized wall of inscrutable build
commands / output". Grepping for "error" does not help, the build
just appears to "fail" at some point.
Could somebody please take a look? I don't know what's going wrong.
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.
Hi Fedorians and Gophers,
golang 1.18.4 was released a couple days ago. This release has fixes for
9 medium (rated by Red Hat Product Security) CVEs, so I will preform a
rebuild in `rawhide` and `f36` to mitigate them[^0]. See
more information about the specific vulnerabilities.
[^0]: The golang version is Fedora 35 is EOL upstream, and the
maintainers have not yet had a chance to backport the changes.
Only packages that provide binaries need to be rebuilt, which will make
this rebuild less disruptive. These packages were determined by querying
for source packages that BuildRequire `golang` or `go-rpm-macros` and
then checking if they provide any binary RPMS that install files in
`/usr/bin`, `/usr/sbin`, or `/usr/libexec`.
No action will be required from you, unless you'd like your package to
receive special treatment regarding merging `rawhide` into `f36`. I plan
to handle this rebuild later this week (the week of the 17th).
In light of the recent discussion about large updates, I will most
likely split this into 4 Bodhi updates per branch (a total of 8; each
containing ~100 packages).
Here is a list of the affected packages on `rawhide`.
Here is a list of all of the affected packages on `f36`. However, I
have further split this list down into two subgroups.
### Mergable from Rawhide
For these packages, `rawhide` was determined to be mergable back to
`f36`, as `f36` is up to date with `rawhide`.
### Not mergable
These packages were determined to not be mergable, as `rawhide` is
ahead of (or has otherwise diverged from) `f36`. Therefore, I will
create a new rebuild commit and bump the release on `f36`. This will
likely cause merge conflicts if you try to merge `rawhide` back into
`f36` after this change. Assuming the update would be compatible and
comply with the Updates Policy, I can move your package into the other
list and merge `rawhide` into `f36`. Please leave a comment on
https://pagure.io/GoSIG/go-sig/issue/44 if you would like me to do so.
Conversely, if you believe your package is incorrectly in the mergable
list, also let me know in the aforementioned ticket.
Maxwell G (@gotmax23)
Jul 19, 2022 9:56:02 AM Davide Cavalca <dcavalca(a)fb.com>:
> The latest version of helm picked up a dependency
> on oras.land/oras-go. That library isn't currently packaged, and fails
> in %check on a docker-related test due to a conflict between
> docker/distribution and distribution/v3.
Does it work if you add
# Use new docker/distribution import path
-e 's|github.com/docker/distribution|github.com/distribution/distribution/v3|' \
-i $(find . -name '*.go')
in %prep and use dynamic buildrequires?
Maxwell G (@gotmax23)
On 22/07/19 02:37PM, Ali Yousefi Sabzevar wrote:
> I saw that those bugs were related to golang-helm-3 package, so maybe not
> directly related to the helm3 rpm package.
helm is a subpackage of the golang-helm-3 source package. These bugs are
very much related to helm.
> I checked on
> https://packages.fedoraproject.org/pkgs/golang-helm-3/helm/ that the
> maintainer is *dcavalca*, but an email to dcavalca(a)redhat.com failed
> to deliver.
That is not the correct way to reach out to a maintainer. Not everyone
who works on Fedora is a Red Hat employee. USERNAME(a)fedoraproject.org
is an alias to whatever the user's actual email is. You can look in the
package %changelog or on accounts.fedoraproject.org for a user's email,
as well. This email also should've reached Davide directly.
> Anyway, if you see the helm3 package is orphaned and has no active
> maintainer, I will pick it up as a maintainer and make an up to date rpm
> package out of it.
The package is not orphaned. The maintainer just hasn't updated it in a
little while. I'm sure they would appreciate a PR.
Maxwell G (@gotmax23)
There is a lot of work needed to keep golang libraries working in Fedora,
and in order to cut down extra items that are taking time and debugging,
the golang SIG would like to remove x86_32 from i686 starting in Fedora 38.
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren