Minitube is built without a Google API key, thus rendering the entire application useless

Jakob Haufe sur5r at
Tue Jun 14 17:20:55 UTC 2016

On Tue, 14 Jun 2016 16:41:17 +0000
auspicious at wrote:

> Minitube is a native YouTube application. It has been broken in 14.04 
> due to Google deprecating an older API, and now it is broken in 16.04 
> due to whoever built the package not having filled in a Google API key.

Shipping an API key with the source package would render the whole point of
forcing users to use an API key in the first place moot (from Googles point
of view). I'm also pretty confident that such an action would result in
immediate blocking of that particular key (and maybe other consequences for
the associated Google account).

> This application has no function without an API key, as it will not work 
> at all. I would either suggest the removal of the application in the 
> repositories, or a rebuild with a Google API key filled in, for it to be 
> then pushed through as a mandatory update.

Please read [1]. Quoting:

minitube (2.5.1-1) unstable; urgency=medium

  Starting with 2.4, minitube supports the new YouTube API version 3.

  As this API version is the only one supprted by now, it is necessary to
  acquire an API key from Google.

  In order to do so, create a "Browser Key" at

  Minitube reads this key from the GOOGLE_API_KEY environment variable.

 -- Jakob Haufe <sur5r at>  Thu, 07 Jan 2016 23:13:57 +0100

It has also been documented by upstream in [2] and [3], respectively.

I would also strongly suggest installing and configuring apt-listchanges
which serves the purpose to display information like those above when updating.


[1] /usr/share/doc/minitube/NEWS.Debian.gz

ceterum censeo microsoftem esse delendam.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the Ubuntu-devel-discuss mailing list