What puzzled me was that I couldn't seem to figure out a pattern for what had universal and what didn't. On my actual machine I use `buildfromsource always`, but I was applying -b and `buildfromsource never" in here because I don't want to constantly be running 3-4 h CI workflows.
Anyway... I've decided that for this job I'll just make a function that does sudo port install -b || sudo port install Thanks for the replies! Gregorio Litenstein Goldzweig Médico Cirujano • Fono: +56 9 96343643 • E-Mail: [email protected] On 10 May 2025 14:59 -0400, Ryan Carsten Schmidt <[email protected]>, wrote: > On May 10, 2025, at 09:28, Gregorio Litenstein wrote: > > > > I understand that the binary archive is not meant to have every single > > combination of variants, arch and OS, but I just found one that seems like > > an odd combination to be missing, and I'm not sure if it's intentional or > > reflecting some current (or past) issue with the buildbot. > > > > In trying to install cmake, my CI failed looking for > > nghttp2-1.65.0_0+universal.darwin_23.arm64-x86_64.tbz2 > > > > I was looking for what IS actually available on packages.macports.org and > > just can't seem to determine whether it being missing is a bug or a > > feature... > > The buildbot builds ports with whatever variants they enable by default. > Ports don't and generally shouldn't enable their universal variant by default. > > In addition, buildbot will build ports with the universal variant if that is > required while building a dependency. > > On the packages server I see archives for some versions of nghttp2 with the > universal variant for some OS versions and architectures but not others. This > suggests that there does exist a port that requires nghttp2 to be universal > (it could be wine) but that when that other port was last updated, something > failed before getting around to building the universal nghttp2. > > There are many other reasons why an archive might not be available, including > server busy or server outage. We consider archives to be a convenience and > their absence not to be a bug. > > Your build should not have failed due to missing archive unless you requested > for that failure to occur by using the "-b" flag on the command line or > setting "buildfromsource always" in macports.conf. > > >
