How can I install ungoogled-chromium on my Debian Jessie? I think I have to build it manually, there's no simple way (yet)? I tried to build it with the instructions found in "Building" page, but I'm not really sure what I should do.
This is what I've tried:
We need Python 3 and Python 2 and Ninja to use buildlib, which is used to install ungoogled-chromium:
user@debian:~$ python3 --version
Python 3.4.2
user@debian:~$ python2 --version
Python 2.7.9
user@debian:~$ apt-get install ninja-build
Because we are using Debian Jessie, we need to do extra steps:
_"Note for Debian Jessie users: ungoogled-chromium is configured to build against the system's FFmpeg (available in Stretch and onwards); Libav (used in Jessie) will not work. However, FFmpeg is available in jessie-backports. To install it, add jessie-backports to the apt sources, and then install libavutil-dev, libavcodec-dev, and libavformat-dev from it. Note that this will replace Libav."_
Okay, let's add jessie-backports to our sources.list:
/etc/apt/sources.listdeb http://httpredir.debian.org/debian jessie-backports mainsudo apt-get update && sudo apt-get upgradelibavutil-dev, libavcodec-dev, and libavformat-dev packages:sudo apt-get install libavutil-dev libavcodec-dev libavformat-dev
Let's download the ungoogled-chromium:
wget https://github.com/Eloston/ungoogled-chromium/archive/master.zip
unzip master.zip
cd ungoogled-chromium-master
Okay, we have everything ready to go. Now we need to "invoke"(?) the build.py to install the ungoogled-chromium:
chmod +x build.py
./build.py
This is as far as I can go. build.py throws me an error and the building will fail.
What am I doing wrong?
Try to build a tag release instead of the master branch.
This looks like a feature introduced in Python 3.5. Python 3.5 is the default Python 3 version on Debian Stretch, so I hadn't realized I've broken Python 3.4 support. I'll make a quick fix.
Most helpful comment
This looks like a feature introduced in Python 3.5. Python 3.5 is the default Python 3 version on Debian Stretch, so I hadn't realized I've broken Python 3.4 support. I'll make a quick fix.