How to set priority for a PPA. I.e. using Firefox without SNAPD

[Snowhog]

What does apt policy firefox show after running an apt update?

paul@paul-virtualbox:~$ apt policy firefox
firefox:
  Installed: 1:1snap1-0ubuntu2
  Candidate: 1:1snap1-0ubuntu2
  Version table:
 *** 1:1snap1-0ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status
     105.0.1+build1-0ubuntu0.22.04.1~mt1 550
        500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 Packages
​

[claydoh]

So, you probably need to uninstall the firefox deb, then see what the policy changes to. I am guessing that it will magically look more like mine, except for the installed status:

$ apt policy firefox
firefox:
Installed: 105.0.1+build1-0ubuntu0.22.04.1~mt1
Candidate: 105.0.1+build1-0ubuntu0.22.04.1~mt1
Version table:
1:1snap1-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
*** 105.0.1+build1-0ubuntu0.22.04.1~mt1 550
500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status

Then installing FF again should install the PPA one, assuming the correct one is now the Candidate

While you can keep both the Snap and the deb installed at the same time, there is no real or logical reason to do so. Uninstalling the snap eliminated the minor default-browser confusions I was seeing while testing over a couple of days.

[Snowhog]

So I purged firefox then updated the package cache and installed firefox. Now we have:

paul@paul-virtualbox:~$ apt policy firefox
firefox:
  Installed: 105.0.1+build1-0ubuntu0.22.04.1~mt1
  Candidate: 105.0.1+build1-0ubuntu0.22.04.1~mt1
  Version table:
     1:1snap1-0ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
 *** 105.0.1+build1-0ubuntu0.22.04.1~mt1 550
        500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status
​

[claydoh]

That's what it needs to be.
Now you can ditch the FF Snap etc if you want.

[Snowhog]

Now you can ditch Snap etc if you want.

Nah. As I discovered on my laptop when I followed Oshunluvrs 'guide', if you completely remove snap from your system, it can result in system update failure (recoverable if you know what you are doing) when a snap dependency comes in and therefore, snapd is expected, but because it isn't present, well....

[claydoh]

lol, I mostly meant the FF snap.

I haven't seen this happen myself, or seen others with similar issues in my regular travels so far. But no one tests this sort of thing anyway.
Obviously neon won't have to worry about this for a couple of years.

[jlittle]

[B]You could always consider installing it manually.

I've found the mozilla team PPA too slow on occasion, to the point where I've had to stop the download during apt full-upgrade. So I'm trying the manual install approach; a bother setting up and moving the profile, but seems good. The download completes in less than a second, maybe coming from some cache somewhere, compared to tens of minutes from the PPA.

[claydoh]

compared to tens of minutes from the PPA

Yes, the PPA servers don't have mirrors like the regular repos have, so those on the other side of the globe, as well as the equator, might see more slowdowns than most.

I'd blame it on Kubuntu's PPAa taking up all the resourced building and packaging everything, but apparently it isn't the busiest one out there atm
Oops, it is again this week
https://launchpad.net/ubuntu/+ppas