On Fri, May 31, 2024 at 06:50:43PM +0100, Kirill A. Korinsky wrote: > On Fri, 31 May 2024 17:18:40 +0100, > Theo Buehler <t...@theobuehler.org> wrote: > > > > On Fri, May 24, 2024 at 06:37:26PM +0100, Kirill A. Korinsky wrote: > > > ports@, > > > > > > Here an update for docker-compose to the last version which was released a > > > few hours ago. > > > > > > The good news that this release includes our patches that allows to drop > > > it > > > from ports tree. > > > > > > The only patch that left was also merged to upstream of buildkit and the > > > next release of buildkit will include that. > > > > > > After that this port can be rewritten to usual go port and vendor artifact > > > can be avoided. > > > > > > Thus, it is future, but todays diff which was tested on -current/amd64 > > > here: > > > > > > This doesn't build here: > > > > # github.com/docker/compose/v2/vendor/github.com/tonistiigi/fsutil > > vendor/github.com/tonistiigi/fsutil/hardlinks.go:83:67: undefined: > > syscall.EBADMSG > > > > Did the commit miss a patch or did you build this with the related > > patches for lang/go that you sent to the list recently? > > Indeed I do have updated lang/go with patches which I sent recently to > remove patches which enforce value of syscall.EBADMSG. > > Well, I've reinstalled lang/go to have reproduce the failure, and here the > diff which should fix the build. I've re-checked docker-cli, docker-buildx > and docker-compose.
Thanks. Committed the diff. > So, this diff required until lang/go is updated. I think that move with > patch for lang/go is the rigth move, but anyway, here the fix: Maybe, but until jsing has decided to land that one, we need to patch the ports.
