<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">On May 10, 2025, at 09:28, Gregorio Litenstein wrote:</div><div dir="ltr"><blockquote type="cite"><br></blockquote></div><blockquote type="cite"><div dir="ltr">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.<div name="messageBodySection">
<div> </div>
<div>In trying to install cmake, my CI failed looking for nghttp2-1.65.0_0+universal.darwin_23.arm64-x86_64.tbz2</div>
<div> </div>
<div>I was looking for what IS actually available on <a href="https://packages.macports.org">packages.macports.org</a> and just can't seem to determine whether it being missing is a bug or a feature...</div></div><div name="messageSignatureSection"><div dir="auto">
</div>
</div>
</div></blockquote><br><div>The buildbot builds ports with whatever variants they enable by default. Ports don't and generally shouldn't enable their universal variant by default. </div><div><br></div><div>In addition, buildbot will build ports with the universal variant if that is required while building a dependency. </div><div><br></div><div>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. </div><div><br></div><div>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. </div><div><br></div><div>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. </div><div><br></div><div><br></div><div><br></div></body></html>