Hacker News Reader

Comment by lol768 | Hacker News Reader

For reasons currently unclear to me, installing this seems to cause apt to remove Discord.

    The following packages have unmet dependencies.


     libc++1-14 : Depends: libunwind-14 (>= 1:14.0.0) but it is not installable

     libc++abi1-14 : Depends: libunwind-14 (>= 1:14.0.0) but it is not installable

    E: Unable to correct problems, you have held broken packages.

View on HN

Context: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/19844...

it's always the same debian / ubuntu package mess. moving to Arch has made this specific headache entirely go away

Can you have several versions of the same package with pacman?

On an opposing note, updating my Arch system (pikaur -Syu) recently wanted to install Electron 20 and remove Electron 19, which the element-desktop package was still depending on. I wasn't using it so that's an easy uninstall. But there's nothing inherent about Arch that prevents these issues from popping up every now and then.

> On an opposing note, updating my Arch system (pikaur -Syu) recently wanted to install Electron 20 and remove Electron 19,

hm that's weird, with yay it only ever adds new electron versions, never removes the old ones. e.g. there's electron12 to 20 in the repos and they can be installed side by side

Or Gentoo with their"slot"s.

Ubuntu's .NET runtime relies on libunwind v13. Discord relies on libunwind v14. apt only allows one version of something to installed at once.

This is not generally the case: "apt only allows one version of something to installed at once" - apt and dpkg always supported having different major versions of a shared library installed concurrently.

See eg https://www.debian.org/doc//debian-policy/ch-sharedlibs.html which says

> The run-time shared library must be placed in a package whose name changes whenever the SONAME of the shared library changes. This allows several versions of the shared library to be installed at the same time, allowing installation of the new version of the shared library without immediately breaking binaries that depend on the old version.

In this libunwind case the situation is more complicated, the its different versions have conflicting subdependencies.

Every once in a while I consider switching to Linux and then I read things like this and then i remember why I keep sticking with Windows.

Reply on news.ycombinator.com