Joshua Root

> I thought mpbb was only running MacPorts built-in tests, not the ones defined in the Portfile. But I see this is coming from a `post-test` block in the Portfile....

> If it were the port's problem, though, how would it do it? Obviously in this specific case it could check in the `post-test` block whether `test-z3` exists before running...

I'm pretty sure the z3-fstar build failure isn't a CI bug.

> It has probably been broken by a global switch to a pep517 without testing if it actually works for all ports. No, it would have been broken by 4c09b10.

I'm not seeking to assign blame here, but you seem to want CI to pass, and fixing that build failure is how that will happen.

https://docs.python.org/3/whatsnew/3.12.html > Remove the distutils package. See [the migration guide](https://peps.python.org/pep-0632/#migration-advice) for advice replacing the APIs it provided. The third-party [Setuptools](https://setuptools.pypa.io/en/latest/deprecated/distutils-legacy.html) package continues to provide distutils, if you still require it...

> It seems like on the face of it, `openrsync` is just referencing a bunch of OpenBSD-native functions that aren't being declared in macOS. There does seem to be a...

> > _resources/port1.0/checks/implicit_function_declaration > > So, if I understood you correctly, basically to every file in: > > https://github.com/macports/macports-ports/tree/master/_resources/port1.0/checks/implicit_function_declaration > > append something like: > > `crypt_newhash crypt_checkpass explicit_bzero getexecname...

> I'm quite curious to know when the Apple team will post the source code of their fork and how they solved the problem with these implicit declarations (or broke...

Please rebase against master in order to pick up c83c328.