You are correct. The patch is in Groovy.
Let's review how to confirm:
- You already did the hard part: You found the patch in Debian.
Information: One line in the patch header includes the Debian bug number (944509), which is very handy:
You found the lowest version of Portaudio19 that includes the patch from either the URL, the web page, or the changelog: 19.6.0-1.1
You checked Ubuntu for the releases that include that version or higher...
$ rmadison portaudio19
portaudio19 | 19+svn20111121-1 | precise | source
portaudio19 | 19+svn20140130-1 | trusty | source
portaudio19 | 19+svn20140130-1build1 | xenial | source
portaudio19 | 19.6.0-1 | bionic/universe | source
portaudio19 | 19.6.0-1build1 | focal/universe | source
portaudio19 | 19.6.0-1.1 | groovy/universe | source
...so Bionic definitely does NOT have the patch, Focal might (or might not), and Groovy definitely does have the patch.
Let's look more deeply into Focal. Here's the changelog on launchpad.net for the Focal package. The lack of a patch mention or a bug number in the changelog is a flare-lit tip-off that Focal does NOT have the patch:
portaudio19 (19.6.0-1build1) focal; urgency=medium
- No-change rebuild for libgcc-s1 package name change.
Finally, let's double-check that the patch is in Groovy. Here's the changelog. The mention of the patch, with the corresponding correct Debian bug number is conclusive proof that the patch in question was applied in this build.
portaudio19 (19.6.0-1.1) unstable; urgency=medium
- Non-maintainer upload.
- Apply crash fix patch (Closes: #944509)
BONUS: See how the Groovy version was a "Non-maintainer upload?" That often means that the volunteer Debian package maintainer welcomes help keeping the package up to date. It's not difficult or time-consuming, and it's a great way to contribute to Ubuntu. Debian (and Ubuntu) welcome new volunteers to learn the skills and contribute a bit of effort to keep everybody's favorite distro going strong.