3 ms·

On 25.10, removing snap gets rid of firefox, chromium, cups and many more packages.

by kuschku 6mo ago

throw0101a 6mo ago
> On 25.10, removing snap gets rid of firefox, chromium, cups and many more packages. For servers, this may not be a problem for us. Currently on 24.04, so will have to see how things are ≥25.10.
- bravetraveler 6mo ago
  Some server stuff is hit too! I learned about this pattern through the BGP daemon 'frr'. No idea how many server packages are/may be captured by Snap, but it's worth being aware of. Imagine my surprise. Remove it and bam, no networking.
  - throw0101a 6mo ago
    Seems to also be available as a Debian package: * https://packages.ubuntu.com/search?keywords=frr https://packages.ubuntu.com/search?keywords=frr in addition to a Snap: * https://snapcraft.io/install/frr/ubuntu https://snapcraft.io/install/frr/ubuntu Doing a quick test on 24.04: on a system without snapd installed, `apt install frr` installs packages and not any Snap stuff. Will have to see about 26.04 when I get a moment.
    - bravetraveler 6mo ago
      Thanks for digging in, as I mentioned earlier in this thread/another [lost track], I haven't messed with this in at least two LTS releases. Good to see it's aware at install time; this wasn't always the case. How about the inverse, purging? At one point, removing Snap would lose BGP announcements [through the loss of the 'frr' software/service it was managing]. Anyway, I'm willing to believe most of my install/dependency-resolution pain was inspired by [and limited to] 18.04 or whatever was immediately after. We had a fleet of systems inadvertently moved to Snap, only learned through a loss of announcements on removal. edit: Tested on a 24.04 box I had laying around; removing Snap does indeed still rip out things one might want: $ sudo apt purge snapd [...] Stopping snap.frr.ripngd.service Stopping unit snap.frr.ripngd.service [...] Stopping snap.frr.zebra.service Likely fine in your case, where if memory serves, you're removing Snap in the image/provisioning stage. Cooks in busy kitchens may still be surprised, however. The real problem appears solved: 'you' get the software 'you' asked for.

On 25.10, removing snap gets rid of firefox, chromium, cups and many more packages.

by kuschku 6mo ago

On 25.10, removing snap gets rid of firefox, chromium, cups and many more packages.

> On 25.10, removing snap gets rid of firefox, chromium, cups and many more packages. For servers, this may not be a problem for us. Currently on 24.04, so will have to see how things are ≥25.10.

bravetraveler 6mo ago
Some server stuff is hit too! I learned about this pattern through the BGP daemon 'frr'. No idea how many server packages are/may be captured by Snap, but it's worth being aware of. Imagine my surprise. Remove it and bam, no networking.
- throw0101a 6mo ago
  Seems to also be available as a Debian package: * https://packages.ubuntu.com/search?keywords=frr https://packages.ubuntu.com/search?keywords=frr in addition to a Snap: * https://snapcraft.io/install/frr/ubuntu https://snapcraft.io/install/frr/ubuntu Doing a quick test on 24.04: on a system without snapd installed, `apt install frr` installs packages and not any Snap stuff. Will have to see about 26.04 when I get a moment.
  - bravetraveler 6mo ago
    Thanks for digging in, as I mentioned earlier in this thread/another [lost track], I haven't messed with this in at least two LTS releases. Good to see it's aware at install time; this wasn't always the case. How about the inverse, purging? At one point, removing Snap would lose BGP announcements [through the loss of the 'frr' software/service it was managing]. Anyway, I'm willing to believe most of my install/dependency-resolution pain was inspired by [and limited to] 18.04 or whatever was immediately after. We had a fleet of systems inadvertently moved to Snap, only learned through a loss of announcements on removal. edit: Tested on a 24.04 box I had laying around; removing Snap does indeed still rip out things one might want: $ sudo apt purge snapd [...] Stopping snap.frr.ripngd.service Stopping unit snap.frr.ripngd.service [...] Stopping snap.frr.zebra.service Likely fine in your case, where if memory serves, you're removing Snap in the image/provisioning stage. Cooks in busy kitchens may still be surprised, however. The real problem appears solved: 'you' get the software 'you' asked for.