Arch Linux User Repository

Thanks for the report @GiugAles. It seems upstream has pulled the v0.7.0 release (and likely re-tagged v0.7.0 as a different git commit), so I have reverted the package to v0.6.7 until this is clarified.

Since the latest update, I get

==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha256sums...
    sysbox ... FAILED
    dockerfiles ... Passed
    sysbox-fs ... Passed
    fuse ... Passed
    sysbox-ipc ... Passed
    sysbox-libs ... Passed
    sysbox-mgr ... Passed
    sysbox-pkgr ... Passed
    sysbox-runc ... Passed
    Honor-SOURCE_DATE_EPOCH-for-reproducible-builds.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
 -> error downloading sources: /home/user/.cache/yay/sysbox-ce 
         context: exit status 1 

I have tried a clean build and to clear the cache. The package is freshly cloned during build.

On bleeding edge kernels (Linux 6.13-rc) there is an issue starting Sysbox containers:

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: container_linux.go:439: starting container process caused: process_linux.go:608: container init caused: write sysctl key net.ipv4.ip_unprivileged_port_start: write /proc/sys/net/ipv4/ip_unprivileged_port_start: invalid argument: unknown.

This is a kernel issue due to commit 3b97c3652d91 "fuse: convert direct io to use folios" and should be fixed once "fuse: fix direct io folio offset and length calculation" lands in 6.13 (https://lore.kernel.org/all/CAJfpegu7o_X=SBWk_C47dUVUQ1mJZDEGe1MfD0N3wVJoUBWdmg@mail.gmail.com/).

EDIT: This has been fixed before the 6.13 release.

@bidskii No worries! This seems to be a problem with how the protoc-gen-go-grpc AUR package declares its version.

My apologies, yay kept installing an old cached version of protoc-gen-go-grpc so I was wildly out of date

@bidskii I probably shouldn't be using that flag, but that's a bit puzzling since as far as I can tell, it should be there in protoc-gen-go-grpc 1.5.1, and I can build this package in a clean container.

Can you confirm that the output of protoc-gen-go-grpc --version is indeed "protoc-gen-go-grpc 1.5.1"? That would discard possibilities such as e.g. having an older version of protoc-gen-go-grpc somewhere in your PATH.

EDIT: Though you mention that you have protoc-gen-go-grpc 1.5.1-1, is it possible that you have been affected by this problem and still have an older version?

Got this error today protoc-gen-go-grpc: no such flag -use_generic_streams_experimental trying to build sysbox-ce 0.6.4-3 with go 2:1.22.5-1 and protoc-gen-go-grpc 1.5.1-1

make: Entering directory '~/.cache/yay/sysbox-ce/src/sysbox'
find: ‘/usr/src/linux-headers-6.10.2-arch1-2’: No such file or directory
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
make[1]: Entering directory '~/.cache/yay/sysbox-ce/src/sysbox/sysbox-ipc'
make -C sysboxFsGrpc/sysboxFsProtobuf
make -C sysboxMgrGrpc/sysboxMgrProtobuf
make[2]: Entering directory '~/.cache/yay/sysbox-ce/src/sysbox/sysbox- 
ipc/sysboxFsGrpc/sysboxFsProtobuf'
GOFLAGS='-buildvcs=false' protoc -I . -I /usr/local/include/ sysboxFsProtobuf.proto -- 
go_out=. --go-grpc_out=. --go-grpc_opt=use_generic_streams_experimental=false --go- 
grpc_opt=require_unimplemented_servers=false
make[2]: Entering directory '~/.cache/yay/sysbox-ce/src/sysbox/sysbox- 
ipc/sysboxMgrGrpc/sysboxMgrProtobuf'
GOFLAGS='-buildvcs=false' protoc -I . -I /usr/local/include/ sysboxMgrProtobuf.proto - 
-go_out=. --go-grpc_out=. --go-grpc_opt=use_generic_streams_experimental=false --go- 
grpc_opt=require_unimplemented_servers=false
protoc-gen-go-grpc: no such flag -use_generic_streams_experimental
protoc-gen-go-grpc: no such flag -use_generic_streams_experimental
--go-grpc_out: protoc-gen-go-grpc: Plugin failed with status code 1.
--go-grpc_out: protoc-gen-go-grpc: Plugin failed with status code 1.

Hi AlexTalker, indeed the problem you are experiencing is related to this package's PKGBUILD using the checksum support for Git repositories introduced in Pacman 6.1.0.

However, Pacman 6.1.0 is currently in the stable (i.e. non-testing) Arch Linux repositories (https://archlinux.org/packages/core/x86_64/pacman/). The problem is that you are not using Arch but Manjaro, which holds back packages for some time so they still haven't released that version of Pacman (see also https://forum.endeavouros.com/t/video-be-careful-with-the-aur-on-manjaro-linux/24809).

I don't maintain compatibility with Manjaro. That said, it will most likely work if you replace the checksums in sha256sums with SKIP, or use the sysbox-ce-bin package instead.

I think the issue might be that my pacman is

$ pacman -Qi pacman
Name            : pacman
Version         : 6.0.2-18
Description     : A library-based package manager with dependency support
Architecture    : x86_64
URL             : https://www.archlinux.org/pacman/
Licenses        : GPL-2.0-or-later
Groups          : None
Provides        : libalpm.so=13-64
Depends On      : bash  glibc  libarchive  curl  gpgme  pacman-mirrorlist  gettext  gawk  coreutils  gnupg  grep
Optional Deps   : perl-locale-gettext: translation support in makepkg-template
Required By     : appstream-glib  archlinux-keyring  base  libpamac  manjaro-keyring  mhwd  packagekit  pkgfile
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 4.73 MiB
Packager        : Mark Wagie <mark@manjaro.org>
Build Date      : Sat 10 Feb 2024 06:51:23 PM MSK
Install Date    : Tue 30 Apr 2024 01:06:47 AM MSK
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

due to the distro, and your PKGBUILD is written according to the future where they figure out how to compute check sum for directories or something

I used pamac to fetch stuff from AUR, gonna try to do it manually now.