Well, that's frustrating. Now I'm sort of stuck... the build fails to compile on my machine, but there's no way to force the buildbot to attempt a build, because it already knows that it successfully completed a build previously.
-- Jason Liu On Tue, Dec 23, 2025 at 4:37 PM Joshua Root <[email protected]> wrote: > "qt64-qtquick3d" is not distributable because its license "gpl" > conflicts with license "APSL-2" of dependency "legacy-support" > > On 24/12/2025 07:41, Jason Liu wrote: > > Wait, why is it being flagged as non-distributable? Packages for the > > other macOS versions have been uploaded to packages.macports.org > > <http://packages.macports.org> and are being distributed. Or is this > > just a generic message, and the 10.14 package needs to be copied from > > the private server to the public one? > > > > -- > > Jason Liu > > > > > > On Tue, Dec 23, 2025 at 3:20 PM Joshua Root <[email protected] > > <mailto:[email protected]>> wrote: > > > > On 24/12/2025 06:15, Jason Liu wrote: > > > According to the port health for the qt64-qtquick3d port <https:// > > > ports.macports.org/port/qt64-qtquick3d/details/ <http:// > > ports.macports.org/port/qt64-qtquick3d/details/>>, it has been built > > > successfully for Mojave. However, a package for 10.14 doesn't > > seem to > > > exist on packages.macports.org <http://packages.macports.org> > > <http://packages.macports.org/qt64- <http://packages.macports.org/ > > qt64-> > > > qtquick3d>, so my machine attempts to build the port from source > > > locally, and the build fails. Can someone try triggering a build > > on the > > > 10.14 buildbot to verify that the build does indeed complete, and > > > possibly put a pre-compiled binary up onto the packages server? > > <https://build.macports.org/builders/ports-10.14_x86_64-watcher/ > > builds/84756/steps/subports/logs/stdio <https://build.macports.org/ > > builders/ports-10.14_x86_64-watcher/builds/84756/steps/subports/ > > logs/stdio>> > > > > - Josh > > > >
