These are two incredibly persistent pieces of misinformation…
Canonical provides snaps for Ubuntu. This is no more “forcing” you to use snaps than they force you to use debs, or than Fedora forces you to use flatpaks/rpms.
Apt doesn’t “prefer snaps” by any means. Canonical provides transitional packages for certain packages that got migrated from debs to snaps, but the steps for using another apt repository to replace one of these transitional packages are the same as the steps for replacing any other package provided in your base repos with one from a different repository: You add the other repository, and you tell apt to prefer that repository for the specific packages.
If you were running a previous version of Ubuntu, where you had deb packages which worked, over the course of a few updates, they replaced half of your programs with snaps (without telling you), which were unable to see additional hard drives, USB pens, printers, scanners or cameras, couldn’t use plug-ins, couldn’t use 3rd party templates or presets, and didn’t respect any system settings for fonts/text size, icon placement and so on.
Snaps were fine for “aisleriot solitaire” or “calculator” (assuming you didn’t mind a 5 minute loading time) or other things which didn’t need to interact with any file or system or device, but for actual programs for people trying to do work? Bag of shite.
Now, I imagine some years later they must have fixed some of this rubbish, and I read recently they might have finally done something about permissions, but no, they didn’t ask anyone before they swapped working programs for completely broken snaps. They forced it on their existing users, and some of us bear grudges.
Sorry, I might have misremembered the exact process (this was probably three or four years ago), though no need for the nasty aggressive attitude (though my apologies if I offended you somehow).
Maybe it was version upgrades (e.g 18.04 to 20.04) instead of updates, or clean installs/new installs/reinstalls? I expect it was some of one and some of another.
At the time I used to (casually) maintain a bunch of Ubuntu computers for a few community projects, small organisations and older people who live nearby. I don’t remember the specifics, I just remember the phone calls of “the printer isn’t working” “Linux has broken my USB pen” etc, and the fix being “remove the snap version and install the deb version”. It caused a lot of problems.
Canonical provides transitional packages for packages that they’ve decided to provide as snaps. They’re not forcing anyone to use snaps, they’re saying “if you want the default we provide you, we’re providing you with a snap.” KDE Neon (my current distro, which is downstream of Ubuntu) has decided that they want to use the deb packages from packages.mozilla.org, so they provide an override. If you want to use the deb from packages.mozilla.org, you could grab KDE Neon’s repository deb and install that, or just set up the mozilla repository and use the same pin file they already have.
This is like saying “Debian FORCES you to use libav” Debian moved from ffmpeg to libav for a while. No, they provided libav and made transitional packages for this drop-in replacement. Some people didn’t like that and made their own ffmpeg repos, and the process for using their separate ffmpeg rather than Debian’s transitional packages was the same as the process for using Firefox from a different repository. (I was one of the people used some third-party ffmpeg repositories, and I was glad when they switched back to ffmpeg and provided libav to ffmpeg transitional packages.)
Does the fact that the Ubuntu repositories don’t contain Keysmith mean “Ubuntu PROHIBITS you from using Keysmith?”
Canonical provides transitional packages for packages that they’ve decided to provide as snaps. They’re not forcing anyone to use snaps, they’re saying “if you want the default we provide you, we’re providing you with a snap.”
Uhm… and why does the user have to transition to snaps? Why does Canonical provide those transitional packages while there are perfectly valid debs for the same thing? Certainly not because they have a vested interest in forcing it right?
Uhm… and why does the user have to transition to snaps?
They don’t. But Canonical will no longer be providing debs in primary Ubuntu repositories, so those transitional packages exist so that users don’t wind up with an abandoned, old version of Firefox.
Why does Canonical provide those transitional packages while there are perfectly valid debs for the same thing?
For the same reason neither Ubuntu nor Debian provide debs for Google Chrome, despite Google having an official apt repository? Those debs exist in somebody else’s apt repository. If you want to add that apt repository, you’re welcome to. But those external packages aren’t part of the system they provide.
you instantly refute yourself, kudos!
Your unwillingness to accept what I’m saying doesn’t make what I’m saying contradictory.
If I were giving you €50/month, and then one day I decided to give you USD$55 instead, am I “forcing” you to accept US currency? No, I’m choosing to give you something I don’t have to give you in the first place in a different form. You can always reject my offer. You can ask someone else to give you €50/month.
They’re choosing how they want to provide Firefox. If anyone else wants to provide Firefox differently, Canonical isn’t stopping them. In fact, Canonical literally hosts and does the builds for an unofficial Firefox repo with their free Launchpad service.
Distributions decide what they want to package and how to package it all the time. Pretty much every time, someone is upset. But that upset is generally based on an unreasonable sense of entitlement.
Fuckin preach it friend!
That’s the joy of Linux, the “have it your way” approach to an OS
yeah well, you can’t have it your way on Ubuntu when Canonical FORCES you to use snaps (heck they even hacked apt to prefer snaps instead of debs)
These are two incredibly persistent pieces of misinformation…
If you were running a previous version of Ubuntu, where you had deb packages which worked, over the course of a few updates, they replaced half of your programs with snaps (without telling you), which were unable to see additional hard drives, USB pens, printers, scanners or cameras, couldn’t use plug-ins, couldn’t use 3rd party templates or presets, and didn’t respect any system settings for fonts/text size, icon placement and so on.
Snaps were fine for “aisleriot solitaire” or “calculator” (assuming you didn’t mind a 5 minute loading time) or other things which didn’t need to interact with any file or system or device, but for actual programs for people trying to do work? Bag of shite.
Now, I imagine some years later they must have fixed some of this rubbish, and I read recently they might have finally done something about permissions, but no, they didn’t ask anyone before they swapped working programs for completely broken snaps. They forced it on their existing users, and some of us bear grudges.
You don’t need to lie. A full list of debs that have been transitioned to snaps is:
Sorry, I might have misremembered the exact process (this was probably three or four years ago), though no need for the nasty aggressive attitude (though my apologies if I offended you somehow).
Maybe it was version upgrades (e.g 18.04 to 20.04) instead of updates, or clean installs/new installs/reinstalls? I expect it was some of one and some of another.
At the time I used to (casually) maintain a bunch of Ubuntu computers for a few community projects, small organisations and older people who live nearby. I don’t remember the specifics, I just remember the phone calls of “the printer isn’t working” “Linux has broken my USB pen” etc, and the fix being “remove the snap version and install the deb version”. It caused a lot of problems.
If that is true, then why are deb packages provided by Canonical for Ubuntu dummied out?
Canonical FORCES you to use snaps, there is no other way to look at this.
Canonical provides transitional packages for packages that they’ve decided to provide as snaps. They’re not forcing anyone to use snaps, they’re saying “if you want the default we provide you, we’re providing you with a snap.” KDE Neon (my current distro, which is downstream of Ubuntu) has decided that they want to use the deb packages from packages.mozilla.org, so they provide an override. If you want to use the deb from packages.mozilla.org, you could grab KDE Neon’s repository deb and install that, or just set up the mozilla repository and use the same pin file they already have.
This is like saying “Debian FORCES you to use libav” Debian moved from ffmpeg to libav for a while. No, they provided libav and made transitional packages for this drop-in replacement. Some people didn’t like that and made their own ffmpeg repos, and the process for using their separate ffmpeg rather than Debian’s transitional packages was the same as the process for using Firefox from a different repository. (I was one of the people used some third-party ffmpeg repositories, and I was glad when they switched back to ffmpeg and provided libav to ffmpeg transitional packages.)
Does the fact that the Ubuntu repositories don’t contain Keysmith mean “Ubuntu PROHIBITS you from using Keysmith?”
Uhm… and why does the user have to transition to snaps? Why does Canonical provide those transitional packages while there are perfectly valid debs for the same thing? Certainly not because they have a vested interest in forcing it right?
you instantly refute yourself, kudos!
They don’t. But Canonical will no longer be providing debs in primary Ubuntu repositories, so those transitional packages exist so that users don’t wind up with an abandoned, old version of Firefox.
For the same reason neither Ubuntu nor Debian provide debs for Google Chrome, despite Google having an official apt repository? Those debs exist in somebody else’s apt repository. If you want to add that apt repository, you’re welcome to. But those external packages aren’t part of the system they provide.
Your unwillingness to accept what I’m saying doesn’t make what I’m saying contradictory.
so they are forcing the users to adopt snaps.
If I were giving you €50/month, and then one day I decided to give you USD$55 instead, am I “forcing” you to accept US currency? No, I’m choosing to give you something I don’t have to give you in the first place in a different form. You can always reject my offer. You can ask someone else to give you €50/month.
They’re choosing how they want to provide Firefox. If anyone else wants to provide Firefox differently, Canonical isn’t stopping them. In fact, Canonical literally hosts and does the builds for an unofficial Firefox repo with their free Launchpad service.
Distributions decide what they want to package and how to package it all the time. Pretty much every time, someone is upset. But that upset is generally based on an unreasonable sense of entitlement.
You’re still missing the point.
and what point would that be? That you can’t have it your way, actually?
No, that some people’s way involves using snap, and that’s fine.