Yes, it should be, as 13.2 will contain a newer libvpx1. (as mentioned already, it has 1.3.0 at the moment)
That said, a problem like this could maybe happen again in the future (libvpx1-1.3.0 vs. libvpx1-1.4.0 maybe?).
Actually libvpx1 should be compatible to libvpx1, so the bug is actually there IMHO.
But hopefully they will not make such a mistake again.