Package Details: protobuf-go 1.5.2-2

Git Clone URL: (read-only, click to copy)
Package Base: protobuf-go
Description: Go support for Google's protocol buffers
Upstream URL:
Keywords: golang protouf
Licenses: BSD
Submitter: fzerorubigd
Maintainer: None
Last Packager: fzerorubigd
Votes: 6
Popularity: 0.000000
First Submitted: 2016-05-18 07:38 (UTC)
Last Updated: 2022-02-27 12:35 (UTC)

Latest Comments

1 2 Next › Last »

gamezelda commented on 2023-02-19 21:33 (UTC)

I have been able to migrate my AUR packages to protoc-gen-go-grpc so this package no longer has any dependents.

samuellittley commented on 2022-08-13 19:42 (UTC)

Note: has been superseded by, and users of this package should probably use the protoc-gen-go package instead. Not sure if this package should be deleted?

sauyon commented on 2022-07-27 19:39 (UTC)

This package still appears to be broken due to the bug mentioned below by gamezelda.

gamezelda commented on 2022-03-22 18:52 (UTC)

Build fails on the recently released go 2:1.18-1.

The problem appears to be --> "go get no longer builds or installs packages in module-aware mode."

It appears go get needs to be replaced with go install.

gamezelda commented on 2021-07-17 14:15 (UTC)

Any change to add GOFLAGS="-modcacherw"? Building creates read-only files which are mildly annoying to remove.


fzerorubigd commented on 2019-11-08 14:32 (UTC) (edited on 2019-11-08 14:32 (UTC) by fzerorubigd)

I can confirm the issue, if you set the GOBIN in your shell, it fails. fixed in the new version

fzerorubigd commented on 2019-11-08 14:26 (UTC)

I tried the build with makepkg and also with yay (I guess that bsed on the path in your log) and there was no problem. do you set GOBIN env in your shell? can you unset GOBIN and try again?

chibby0ne commented on 2019-11-08 11:39 (UTC) (edited on 2019-11-08 12:06 (UTC) by chibby0ne)

I'm getting this error at install time:

==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat '/home/user1/.cache/yay/protobuf-go/src/bin/protoc-gen-go': No such file or directory
==> ERROR: A failure occurred in package().

even though it actually downloaded it to the $GOBIN.

freswa commented on 2019-10-24 13:20 (UTC) (edited on 2019-10-24 13:20 (UTC) by freswa)

Thank you for the changes. Looks better now. The packaging guidlines state, that a PKGBUILD using the latest commit is a -git package. Using a git tag or a tarball it's a normal release without any suffix. If you'd use a prebuild binary the pkgname should have the -bin suffix. You can make building easier if you change the url to${pkgver}.tar.gz

which points to the corresponding tarball of the release. It's the same code as the tag, but it's easier to download than a git clone. :)

fzerorubigd commented on 2019-10-24 11:28 (UTC)

@freswa Yes, you are right. but since there is no pre-built binary release, now it builds on tags. technically it's a git version, but on the latest tag.