Hacker News Reader

Comment by emersion | Hacker News Reader

It seems like on recent Ubuntu installations some packages are provided by snaps (ie. "apt install XXX" will install a snap). I'd be interested in disabling this behaviour, if anyone knows.

View on HN

Cies posted a link to https://github.com/cies/kubuntu-setup#remove-snap

They give the suggestion to remove via

   sudo rm -rf /var/cache/snapd/ && sudo apt autoremove --purge snapd && rm -fr ~/snap

And make sure it never installs again:

   sudo bash -c "cat > /etc/apt/preferences.d/no-snapd.pref" << EOL
   Package: snapd
   Pin: origin ""
   Pin-Priority: -1
   EOL

Hmm, but then "apt install" would just fail because of an unresolved dependency right?

That would be really bad. I used Ubuntu for the past 15 years or so, but that would make me switch to a different distro.

So shortly after the Mir fiasco, why does Canonical feel it necessary to come up with the next dumb idea?

Unfortunately, it seems like I remembered correctly, at least for Chromium: https://news.ycombinator.com/item?id=22972856

What is or was the Mir fiasco?

https://en.wikipedia.org/wiki/Mir_(software)#Controversy

I think that this is just the case with LXD. LXD used to be distributed as a DEB package in Ubuntu 18.04. Therefore, to make it to upgrade from DEB to snap in newer versions of Ubuntu, there is this dummy 'lxd' DEB package in the repositories that in fact installs the snap package of LXD.

Other than that, I do not think other packages are affected.

Reply on news.ycombinator.com