Re: Build proceeds on arm64 despite BROKEN_aarch64 being in the port
- In reply to: Ronald Klop : "Re: Build proceeds on arm64 despite BROKEN_aarch64 being in the port"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 11 Dec 2024 21:36:26 UTC
It appears this way. When I tried to cherry-pick this commit today the command failed saying that there is a conflict, which left me thinking that it was pushed earlier. Thanks, Yuri On 12/11/24 13:26, Ronald Klop wrote: > You pushed the change today, didn’t you? > > https://cgit.freebsd.org/ports/commit/?h=2024Q4&id=0ca0be4ae9db2a693ceae90519cc722d93090b8e > <https://cgit.freebsd.org/ports/commit/?h=2024Q4&id=0ca0be4ae9db2a693ceae90519cc722d93090b8e> > > Regards, > Ronald > > *Van:* Yuri <yuri@FreeBSD.org> > *Datum:* 11 december 2024 22:11 > *Aan:* "ports@freebsd.org" <ports@freebsd.org> > *Onderwerp:* Build proceeds on arm64 despite BROKEN_aarch64 being in > the port > > The port graphics/oculante has the BROKEN_aarch64 line in the > 2024Q4 branch since October. > > Despite this it is still being built now, in December: > https://pkg-status.freebsd.org/ampere1/data/141arm64-quarterly/e17ba537c699/logs/oculante-0.9.1.log > > > What is wrong? > > > > Thanks, > > Yuri > > > > >