OBS may provide pulseaudio with newer dependencies (DLLs from dependent packages). I don't think it rebuilds it IIRC, just the download script downloads newer deps.
The pulseaudio-dependencies aggregate is unneeded and actually harmful nowadays. Instead of copying the dependencies into your own repository via an aggregate, you can build directly against the additional repositories. AFAIK, OBS will make sure that it's up-to-date, including rebuilds if dependencies change.
The download script looks weird... it just fetches the git repository and repackages it. Probably useful for testing manual builds, but it isn't used automatically anywhere.
Pulseaudio will never get a newer version build on OBS unless I myself work on it (or someone else does on their fork.) (If OBS supports collaborative development now on repos, I'd very much like to do that.)
I keep wondering about that... is X2Go really the only user of PulseAudio on Windows? Or do the other users just stay on the old 1.0 version (whatever it was) from 10 years ago?
But yeah, that's why I forked and updated it. OBS supports collaborative development in general though, so we could just use one repo. I didn't mean to do this privately. :)
I recommend backporting the patch.
Okay, will do so later and update the contrib repository. Luckily I won't have to also update the dependencies.
Mihai