Ubuntu – How to install VLC 3.0 on Ubuntu Zesty 17.04

I'm having a difficulty installing VLC 3.0 in Ubuntu Zesty. Using the official PPA. I added it using

sudo add-apt-repository ppa:videolan/master-daily
sudo apt-get update

And apt-cache show has it listed,

apt-cache show vlc | grep Version
Version: 3.0.0~~git20160813+r65787+62~ubuntu16.04.1
Version: 2.2.4-14ubuntu2

but when I try to install 3.0.0 with sudo apt-get install vlc=3.* I get,

sudo apt-get install vlc=3.*
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Selected version '3.0.0~~git20160813+r65787+62~ubuntu16.04.1' ( [amd64]) for 'vlc'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 vlc : Depends: vlc-nox (= 3.0.0~~git20160813+r65787+62~ubuntu16.04.1) but it is not going to be installed
       Depends: libavcodec-ffmpeg56 (>= 7:2.6) but it is not installable or
                libavcodec-ffmpeg-extra56 (>= 7:2.6) but it is not installable
       Depends: libgles1-mesa (>= 7.8.1) or
                libgles1
       Recommends: vlc-plugin-notify (= 3.0.0~~git20160813+r65787+62~ubuntu16.04.1) but it is not going to be installed
       Recommends: vlc-plugin-samba (= 3.0.0~~git20160813+r65787+62~ubuntu16.04.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Is there another PPA that provides VLC 3.0 in Ubuntu Zesty? It seems that libavcodec-ffmpeg56 was renamed,

$ apt-cache search libavcodec ffmpeg
libavcodec-extra57 - FFmpeg library with additional de/encoders for audio/video codecs

And that now vlc-3.* needs to be built against the new library (libavcodec-extra57) and have its manifest updated from old name (libavcodec-ffmpeg-extra56)

I can't file a bug on this either because Launchpad doesn't support that. All I can do is write the maintainer using the Launchpad contact forum, which I did. No response back.