[vcpkg baseline] Retrigger failed port apr-util

[Septarius]

Describe the pull request

Attempts to reproduce #11923 from master on the CI since I can't reproduce this locally (lack of an appropriate local OSX configuration).

• What does your PR fix?

• Which triplets are supported/not supported? Have you updated the CI baseline?

• Does your PR follow the maintainer guide?

[Septarius]

Failed OSX Check Run

[Septarius]

Successful OSX Check Run
It is successful if apr and apr-util are built at the same time at least.

[JackBoosY]

Thanks for this PR!

[BillyONeal]

This just retriggers a build so I'd prefer to see it resolved by deleting the tombstone(s) for these ports. We should endeavor to make the port work consistently; if there's a consistent pattern of such failures we may need to skip these ports in CI.

[Septarius]

@BillyONeal I was just attempting a repro case for the attached issue so let me know if you need anything from me.

[JackBoosY]

Apr-util failure logs:

./../src/apr-util-1-a62665826e/configure: line 4089: cd: /Volumes/data/work/2/s/installed/x64-osx/build-1: No such file or directory

codes:

APR_BUILD_DIR="`cd $APR_BUILD_DIR && pwd`"

files:

vcpkg@VCPKG% ls packages/apr_x64-osx/build-1
apr_rules.mk            libtool                 make_exports.awk        make_var_export.awk     mkdir.sh

[BillyONeal]

I can't believe we have multiple ports trying to provide this "build-1" dir :(

[BillyONeal]

Can you add an assertion that the directory in question build-1 doesn't exist before building the 'apr' port in addition to bumping the number?

Bumping the apr-util number is unnecessary: it's in the "cone of destruction" of apr so it will get rebuild automatically.

[JackBoosY]

This issue occurs because apr-1.pc is not fixed. And I fixed it in #12067.

[BillyONeal]

+1 @JackBoosY found the correct reason for the failure rather than Bill's supposition :)

[BillyONeal]

I believe #12067 will fix this

[Septarius]

Sounds good to me, thanks for all the work on this! I will go ahead and close this PR. If you want you could add a fix tag for #11923 to #12067 since it should unblock the PRs mentioned in that issue as well.