Go to content Go to menu

I don’t know why it’s taken me so long to realize this was happening, but today I needed to copy some files from one server to another, and I realized I was tab-completing paths on the remote server. Which shouldn’t be possible, and yet, there it was. MAGIC! Thanks, .bash_completion file.

In all my thrashing about trying to get Netflix installed on my Linux Mint 17 notebook, I finally figured out my problem: while Ubuntu PPAs do typically work just fine on Linux Mint, you’ll have to do more than just run sudo apt-add-repository to get them going.

So, here’s the trick: you have to set things up manually.

Copy an existing PPA in cd /etc/apt/sources.list.d/ (I used the one I set up for google chrome) and paste in the correct URL for deb lines.

What follows is more of a specific how-to for setting up Netflix, but I’ll include it as it might help someone, and it gives you a better idea of how to apply this approach to any other “non-Mint” PPA.

Here’s the contents of my hand-crafted pipelight.list file:

deb http://ppa.launchpad.net/pipelight/stable/ubuntu trusty main
deb-src http://ppa.launchpad.net/pipelight/stable/ubuntu trusty main

I found these URLs by going to this page:

and unhiding the “Technical details about this PPA” div (click the arrow).

Now, you have to also “trust the key” which was a bit trickier, here’s what I typed:

sudo gpg --ignore-time-conflict --no-options --no-default-keyring --keyring /etc/apt/trusted.gpg 
--keyserver keyserver.ubuntu.com --recv 37D519856DA17931CD1123FBFB5DF26925396B8E

FYI, that key hash is visible on the launchpad.net page:
and the gpg commands are copied from the second screenshot under “Signing key … what is this?”

Now all you have to do is (note below is what worked for me, there might be an easier way to do it):

sudo apt-get update
sudo apt-get install --install-recommends pipelight-multi
pipelight-plugin --update
sudo apt-get install pipelight