[Bug 1965960] Re: apt installs snap packages
1965960 at bugs.launchpad.net
Tue Mar 22 15:36:26 UTC 2022
Please, please, pretty please use apt for deb and snap for snap, and
don't pollute apt with snap packages.
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
apt installs snap packages
Status in apt package in Ubuntu:
$ lsb_release -rd
Description: Ubuntu Jammy Jellyfish (development branch)
$ apt-cache policy apt
*** 2.4.1 500
500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
3) I expected to dist-upgrade my system, running apt-get dist-upgrade
4) apt tried to install firefox from snap. I naturally aborted the upgrade, if I want a snap package I install it with snap, I use apt to install debian/apt packages.
Aborting the install essentially broke my system. Trying to repair it, and installing firefox using apt again, hence getting force-fed the snap of firefox, broke my install, too, as the snap cannot access my firefox configuration files (for good reasons).
It took me half a day to repair the system and switch to a PPA to keep the system (and Ubuntu with its intended processes - apt for deb, snap for snap, probably flatpaks and whatever for other stuff - for that matter) running.
In summary: We know you love snap. We use snap for certain purposes, and apt for others. Please don't force your love for snap on us, snaps constantly break long-running systems and require careful introduction.
The proper solution could have been to stop supporting firefox from apt, so we have to consciously deal with the situation - without getting our systems broken.
DistroRelease: Ubuntu 22.04
Package: apt 2.4.1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
Date: Tue Mar 22 16:26:47 2022
InstallationDate: Installed on 2022-03-07 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
RebootRequiredPkgs: Error: path contained symlinks.
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
More information about the foundations-bugs