Linuxmint and libstdc++6 ppa problem

[leolam]

Didn't mean to spread misinformation, but AFAIK you would have to add the PPA entry and pretend you're a trusty system (since the PPA only supports precise and trusty), which could work with Mint 17 which is based on Trusty. But it could also break or just not work (which is OP's case). While it's true that Mint is based on Ubuntu, uses dpkg as well and supports PPAs, not all PPAs were provided and packages in there were built with Mint in mind (same for Debian, you can use some Ubuntu PPAs with a Debian version that's not too old but it doesn't always work and it's not supported). But you're correct for gcc-4.9, that's probably why it wasn't working, maybe the packages got updated but the dependencies had versions that were too strict.

[sergio-br2]

(01-22-2016, 09:29 AM)leolam Wrote: Didn't mean to spread misinformation, but AFAIK you would have to add the PPA entry and pretend you're a trusty system (since the PPA only supports precise and trusty), which could work with Mint 17 which is based on Trusty. But it could also break or just not work (which is OP's case). While it's true that Mint is based on Ubuntu, uses dpkg as well and supports PPAs, not all PPAs were provided and packages in there were built with Mint in mind (same for Debian, you can use some Ubuntu PPAs with a Debian version that's not too old but it doesn't always work and it's not supported). But you're correct for gcc-4.9, that's probably why it wasn't working, maybe the packages got updated but the dependencies had versions that were too strict.

I don't know if I understood well what you are trying to explain/argue... what's the meaning of OP's ? sorry

The issue is not due the guy using Linux Mint, it's because Ubuntu repo got updated, and consequently Linux Mint, because they use the same repositories...

Take a look at your /etc/apt/sources.list.d/, you'll see the same Ubuntu repo. It doesn't make sense you say a PPA is not compatible with Linux Mint. It only has extra repositories for Cinnamon, Mate and whatever comes with Mint.

Also, you can't do comparison between Debian & Ubuntu and Ubuntu & Linux Mint. In the Ubuntu development they get packages from Debian testing/unstable and they freeze some months before the ubuntu release. This is why Debian [stable/testing] is incompatible with Ubuntu PPA, but for Linux Mint it's not the case, because they use the same "stable" stack from ubuntu release, so the PPAs must be compatible.

Edit: I didn't understand what you mean by "you're a trusty system (since the PPA only supports precise and trusty)", what do you want? gcc 4.9 ppa for vivid and wily too? It does not make sense, they have this gcc version or higher in the official repo... and you can trusty that ppa, if you read the description it comes from the ppa:ubuntu-toolchain-r/test, I just copied from there... you can see even who did the upload...

[leolam]

Ah, so Mint 17.3 uses "trusty" as the release name? As is, it will try to get packages for Trusty for PPAs automatically? That's something I didn't know and I stand corrected if I assumed the reverse. (I was referring to the trusty (14.04) release, not trusting the PPA or not.)

I compared the situation with Debian and Ubuntu because it most often works (when the versions are not too different, like trusty and jessie), except when there are subtle package name or version changes that break dependencies. The changes between Mint and Ubuntu are definitely much more minor than Debian and Ubuntu as you've said, but it's still not Ubuntu so it may have different packages or versions in the future.

And no, you definitely don't need the gcc 4.9 PPA for Vivid, since it has 4.9.2 in the official repos. Wily has 5.2 IIRC. And Trusty ships with 4.8.2, and I don't think the version (even the minor version) was updated.

[paulstelian97]

(01-23-2016, 03:01 AM)leolam Wrote: Ah, so Mint 17.3 uses "trusty" as the release name? As is, it will try to get packages for Trusty for PPAs automatically? That's something I didn't know and I stand corrected if I assumed the reverse. (I was referring to the trusty (14.04) release, not trusting the PPA or not.)

I compared the situation with Debian and Ubuntu because it most often works (when the versions are not too different, like trusty and jessie), except when there are subtle package name or version changes that break dependencies. The changes between Mint and Ubuntu are definitely much more minor than Debian and Ubuntu as you've said, but it's still not Ubuntu so it may have different packages or versions in the future.

And no, you definitely don't need the gcc 4.9 PPA for Vivid, since it has 4.9.2 in the official repos. Wily has 5.2 IIRC. And Trusty ships with 4.8.2, and I don't think the version (even the minor version) was updated.

I have a weird install of Linux Mint. I first debootstrapped Trusty to the destination, then added the Linux Mint sources, and finally fixed the policy complaints that Mint's update manager threw at me.

That is, Linux Mint 17.3 uses Trusty as package base. Packages from other Ubuntu distros won't work well on this version of Linux Mint but packages intended for Ubuntu Trusty will work perfectly on Linux Mint 17.x (although sometimes it might force some upgrades [breaking the apt policies for the purpose of fixing dependencies, in an automatic way, and installing not-so-recommended versions]).

You just should avoid packages of newer versions of Ubuntu (or even of older ones).