Fix macOs Actions

[4ydan]

#4973

Basics

• Short descriptions of your changes are in the release notes
  (added as entry in doc/news/_preparation_next_release.md which contains _(my name)_)
  Please always add them to the release notes.
• Details of what you changed are in commit messages
  (first line should have module: short statement syntax)
• References to issues, e.g. close #X, are in the commit messages.
• The buildservers are happy. If not, fix in this order:
  • add a line in doc/news/_preparation_next_release.md
  • reformat the code with scripts/dev/reformat-all
  • make all unit tests pass
  • fix all memleaks
  • fix the CI itself (or rebase if already fixed)
• The PR is rebased with current master.

Checklist

• I added unit tests for my code
• I fully described what my PR does in the documentation
  (not in the PR description)
• I fixed all affected documentation (see Documentation Guidelines)
• I fixed all affected decisions (see Decision Process)
• I added code comments, logging, and assertions as appropriate (see Coding Guidelines)
• I updated all meta data (e.g. README.md of plugins and METADATA.ini)
• I mentioned every code not directly written by me in reuse syntax

Review

• Documentation is introductory, concise, good to read and describes everything what the PR does
• Examples are well chosen and understandable
• Code is conforming to our Coding Guidelines
• APIs are conforming to our Design Guidelines
• Code is consistent to our Design Decisions

Labels

• Add the "work in progress" label if you do not want the PR to be reviewed yet.
• Add the "ready to merge" label if everything is done and no further pushes are planned by you.

[atmaxinger]

Have you tried brew install [email protected] and brew pin [email protected] ?

[4ydan]

Have you tried brew install [email protected] and brew pin [email protected] ?

Brew install didnt work because a higher version is installed, brew pin I didnt try.

[atmaxinger]

Well, it wouldn't work either way, just tried it. Seems like this solution here is the only way to do it.

[markus2330]

Thx, when it solves the problem, please merge.

[4ydan]

Yea, the best would be probably to port libelektra to 2.5.6 and avoid dark magic in the yml file.

[atmaxinger]

Does libelektra actually directly depend upon libassuan? Or is this a transitive dependency?

[markus2330]

It is only a development dependency, for ASAN builds. I don't think anyone would use it for production builds.

[4ydan]

Will try some stuff on the macos github actions on my fork, will close this to not start the other pipelines.

[4ydan]

These tests behave very weird, I removed all my changes, and the macos/cirrus tests pass now.
I doubt that its just because of macos12 or brew cleanup. Also the jenkins pipeline fails randomly for no reason :s

[atmaxinger]

jenkins build libelektra please

[atmaxinger]

It seems like time itself fixed this issue. So there's probably been a package update in homebrew, this PR is no longer needed. Thanks for working on it anyways!

[4ydan]

Nice!