pipewire: apply qjackctl fix from master

[st3r4g]

General

• This is a new package and it conforms to the quality requirements

Have the results of the proposed changes been tested?

• I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
• I generally don't use the affected packages but briefly tested this PR

https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/696

[ericonr]

Can you add a link to the commit to the top of the file. It's hard to tell what this does.

[st3r4g]

Can you add a link to the commit to the top of the file. It's hard to tell what this does.

Well, the commit hash is already in the filename, I though it was descriptive enough. Also it will be removed on next release. Should we just wait for next release?

[ericonr]

Well, the commit hash is already in the filename, I though it was descriptive enough.

I somehow missed that, but the link is also easier to click and go directly to the explanation.

Re. Waiting for release, your choice. Pipewire is small enough IMO that either is ok. Unless a release is coming in the next few days, then I guess waiting is best.

[st3r4g]

Rerun CI because GitHub had problem earlier today.

Unless a release is coming in the next few days, then I guess waiting is best.

Releases are usually every 2 weeks.
But until the other PR (rpath removal) is merged qjackctl with pipewire is broken anyway.