Bug 953025

Summary:	/: go ebuilds fail if bcachefs is used for PORTAGE_TMPDIR because "go mod verify" fails, e.g., github.com/docker/distribution v2.8.3+incompatible: dir has been modified
Product:	Gentoo Linux	Reporter:	lekto
Component:	Current packages	Assignee:	William Hubbs <williamh>
Status:	CONFIRMED ---
Severity:	normal	CC:	flow, lekto, stijn+gentoo
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://github.com/golang/go/issues/73938
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	build.log emerge --info dmesg build.log (dev-lang/go)

Description lekto 2025-04-01 18:44:30 UTC

Created attachment 923473 [details]
build.log

> >>> Unpacking docker-compose-2.32.3-deps.tar.xz to /var/tmp/portage/app-containers/docker-compose-2.32.3/work
> go mod verify
> github.com/docker/distribution v2.8.3+incompatible: dir has been modified (/var/tmp/portage/app-containers/docker-compose-2.32.3/work/go-mod/github.com/docker/distribution@v2.8.3+incompatible)
> google.golang.org/protobuf v1.35.1: dir has been modified (/var/tmp/portage/app-containers/docker-compose-2.32.3/work/go-mod/google.golang.org/protobuf@v1.35.1)

Comment 1 lekto 2025-04-01 18:44:50 UTC

Created attachment 923474 [details]
emerge --info

Comment 2 Florian Schmaus gentoo-dev

2025-04-02 05:44:03 UTC

Which kind of filesystem is holding /var/tmp/portage (cause I am seeing similar failures when using bcachefs)?

Comment 3 lekto 2025-04-02 13:40:13 UTC

Yes, I have bcachefs, I tried to build it on tmpfs and it worked.

Comment 4 Florian Schmaus gentoo-dev

2025-04-03 09:26:53 UTC

Which kernel version do you use?

Comment 5 lekto 2025-04-03 13:00:59 UTC

>6.12.16-gentoo-dist #1 SMP PREEMPT_DYNAMIC Fri Feb 21 16:00:51 -00 2025

Also, there is a WARNING every boot in dmesg related to bcachefs.

Comment 6 lekto 2025-04-03 13:01:14 UTC

Created attachment 923543 [details]
dmesg

Comment 7 Florian Schmaus gentoo-dev

2025-04-08 07:21:13 UTC

I am making this a tracker bug for "go mod verify" failing on bcachefs volumes. I am seeing this for various other go ebuilds as well (e.g., dev-lang/go or dev-util/gitlab-runner).

This is very likely an upstream (bcachefs) issue regarding filesystem operation consistency and visibility.

Comment 8 Florian Schmaus gentoo-dev

2025-04-08 07:25:22 UTC

Created attachment 923915 [details]
build.log (dev-lang/go)

Attaching a build.log from dev-lang/go failing. Here, it does not seem to be "go mod verify" that is failing, but "go tool dist".

Comment 9 Stijn Tintel 2025-05-31 21:39:19 UTC

FYI: https://github.com/golang/go/issues/73938