Hot answers tagged

4

This can be achieved with an altered version of the script which can be found here. #! /bin/sh find /etc/apt/ -name '*.list' | while read -r apt do grep -o "^deb http://ppa.launchpad.net/[a-z0-9\-]\+/[a-z0-9\-]\+" "$apt" | while read entry ; do user=$(echo "$entry" | cut -d/ -f4) ppa=$(echo "$entry" | cut -d/ -f5) ...


3

Option 3 -- Automatically add the new PPA This is like 2, but php5-common would automatically add the new PPA, so the new packages would be available after next apt-get update run. Optionally there could be a Debconf question whether the users wants the PPA added automatically or they will do so themselves. Pros: One single repository to handle No ...


2

Option 2 -- Make a deprecation plan and inform the users prominently Pros: One single repository to handle No automatic transition Users can prepare their transition plan Cons: Some users will miss the announcement no matter how hard you try There will be people how will say: "Please, don't do that" No automatic transition


2

To compile from source you need to install first the following packages as dependencies (be carefull to select the whole box and paste it into terminal): sudo apt-get install git build-essential automake autoconf libtool \ intltool libgtk2.0-dev libspeexdsp-dev libavcodec-dev libswscale-dev \ libx11-dev libxv-dev libgl1-mesa-dev libreadline-dev ...


2

As of 29 April 2016, the accepted answer is no longer the correct procedure. It is now self-service: you can change an option in the PPA settings to get it to build for any of the following architectures automatically (documentation link): AMD x86-64 (amd64) ARM ARMv8 (arm64) ARM ARMv7 Soft Float (armel) ARM ARMv7 Hard Float (armhf) Intel x86 (i386) ...


2

They changed the GPG key they use to sign packages. Try running this in a terminal: gpg --recv-keys DD969F10A7E2BCD2 EDIT: You need to add it to apt so the correct answer is: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys DD969F10A7E2BCD2


1

Install PPA Purge using sudo apt install ppa-purge. Then use ppa-purge to purge the offending PPA (padoka PPA) and restore the files that are found in the Ubuntu repositories by using sudo ppa-purge ppa:paulo-miguel-dias/mesa.


1

These PPAs have been not updated to 16.04 yet. You can wait or disable them via Updates.


1

The old php5-* packages are coinstallable with the new phpX.Y-* scheme, so the first thing you need to do is to install and enable new packages: Apache 2.4 You need to install new libapache2-mod-phpX.Y packages and then disable the old php5, and enable new versioned module, f.e. for PHP 5.6: sudo apt-get install libapache2-mod-php5.6 sudo phpdismod php5 ...


1

The discussed ppa does not support 16.04 so far. Last supported version right now is Wily - aka 15.10 according to the Launchpad side listing. Therefor contact the ppa maintainer and ask for updates or wait until he does it by himself.


1

Option 4 -- Fully automated transition This is like Option 3, but adds dummy packages that will replace the old php5* and pull the new php5.6* Pros (includes Pros from Option 3): If everything works like expected, it might be the best option, as the users will have the new packages without any work at their side Cons (includes Cons from Option 3): ...


1

Option 1 -- Do nothing Pros: Users are happy Cons: Every duplicate source package has to have two versions of the build script Overloaded and unhappy PPA maintainer


1

The rabbitvcs package is within the official repositories so remove the ppa's again and make sure your /etc/apt/sources.list looks like this. Then do: sudo apt-get install rabbitvcs* If you run into following error: IOError: [Errno 13] Permission denied: '/home/username/.config/rabbitvcs/settings.conf simply correct the permissions by : chmod with ...


1

It could be an error relative to some broken updates. You can try to fix this error updating package list: sudo apt-get update sudo apt-get upgrade Note: before run the above commands check that your computer is connected to internet. I hope this could help you.


1

I had this issue - it was because Anaconda2 didn't have the GLIBCXX_3.4.20 version of whatever that thing is. Only up to .19, the same as yours. However, Ubuntu's library did have it. So I just created a softlink/shortcut in the Anaconda library to the actual Linux library containing that GLIBCXX_3.4.20, replacing the previous one, and it worked fine after ...



Only top voted, non community-wiki answers of a minimum length are eligible