[Software] How to install regular FireFox (not ESR) in such a way so it updates automatically (Debian 11)

[Diesel330]

I don't use apt to update, I have unattended updates enabled so it updates without bothering me. Ideally I wanted the regular Firefox to update that way.

I was hoping someone more knowledgeable than I would answer this but since no one has I'll try. Can I see the output of

Code: Select all

apt policy

please?

Code: Select all

100 /var/lib/dpkg/status
     release a=now
 500 https://dl.winehq.org/wine-builds/debian bullseye/main all Packages
     release o=dl.winehq.org,a=oldstable,n=bullseye,l=winehq,c=main,b=all
     origin dl.winehq.org
 500 https://dl.winehq.org/wine-builds/debian bullseye/main i386 Packages
     release o=dl.winehq.org,a=oldstable,n=bullseye,l=winehq,c=main,b=i386
     origin dl.winehq.org
 500 https://dl.winehq.org/wine-builds/debian bullseye/main amd64 Packages
     release o=dl.winehq.org,a=oldstable,n=bullseye,l=winehq,c=main,b=amd64
     origin dl.winehq.org
 500 https://repo.protonvpn.com/debian stable/main all Packages
     release o=proton-gitlab,n=stable,c=main,b=all
     origin repo.protonvpn.com
 500 https://repo.protonvpn.com/debian stable/main amd64 Packages
     release o=proton-gitlab,n=stable,c=main,b=amd64
     origin repo.protonvpn.com
1000 https://packages.mozilla.org/apt mozilla/main all Packages
     release o=namespaces/moz-fx-productdelivery-pr-38b5/repositories/mozilla,a=mozilla,n=mozilla,l=namespaces/moz-fx-productdelivery-pr-38b5/repositories/mozilla,c=main,b=all
     origin packages.mozilla.org
1000 https://packages.mozilla.org/apt mozilla/main amd64 Packages
     release o=namespaces/moz-fx-productdelivery-pr-38b5/repositories/mozilla,a=mozilla,n=mozilla,l=namespaces/moz-fx-productdelivery-pr-38b5/repositories/mozilla,c=main,b=amd64
     origin packages.mozilla.org
 500 https://brave-browser-apt-release.s3.brave.com stable/main amd64 Packages
     release o=Brave Software,a=stable,n=stable,l=Brave Browser,c=main,b=amd64
     origin brave-browser-apt-release.s3.brave.com
 500 http://security.debian.org/debian-security bullseye-security/non-free amd64 Packages
     release v=11,o=Debian,a=oldstable-security,n=bullseye-security,l=Debian-Security,c=non-free,b=amd64
     origin security.debian.org
 500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
     release v=11,o=Debian,a=oldstable-security,n=bullseye-security,l=Debian-Security,c=main,b=amd64
     origin security.debian.org
 100 http://deb.debian.org/debian bullseye-backports/non-free amd64 Packages
     release o=Debian Backports,a=bullseye-backports,n=bullseye-backports,l=Debian Backports,c=non-free,b=amd64
     origin deb.debian.org
 100 http://deb.debian.org/debian bullseye-backports/contrib amd64 Packages
     release o=Debian Backports,a=bullseye-backports,n=bullseye-backports,l=Debian Backports,c=contrib,b=amd64
     origin deb.debian.org
 100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
     release o=Debian Backports,a=bullseye-backports,n=bullseye-backports,l=Debian Backports,c=main,b=amd64
     origin deb.debian.org
 500 http://deb.debian.org/debian bullseye-updates/main amd64 Packages
     release v=11-updates,o=Debian,a=oldstable-updates,n=bullseye-updates,l=Debian,c=main,b=amd64
     origin deb.debian.org
 500 http://deb.debian.org/debian bullseye/non-free amd64 Packages
     release v=11.11,o=Debian,a=oldstable,n=bullseye,l=Debian,c=non-free,b=amd64
     origin deb.debian.org
 500 http://deb.debian.org/debian bullseye/contrib amd64 Packages
     release v=11.11,o=Debian,a=oldstable,n=bullseye,l=Debian,c=contrib,b=amd64
     origin deb.debian.org
 500 http://deb.debian.org/debian bullseye/main amd64 Packages
     release v=11.11,o=Debian,a=oldstable,n=bullseye,l=Debian,c=main,b=amd64
     origin deb.debian.org
Pinned packages:

[Shamak]

Here's the way that I have done. As root, edit the file /etc/apt/apt.conf.d/50unattended-upgrades and add the line

Code: Select all

"o=namespaces/moz-fx-productdelivery-pr-38b5/repositories/mozilla,n=mozilla";

as shown

Code: Select all

Unattended-Upgrade::Origins-Pattern {
        // Codename based matching:
        // This will follow the migration of a release through different
        // archives (e.g. from testing to stable and later oldstable).
        // Software will be the latest available for the named release,
        // but the Debian release itself will not be automatically upgraded.
//      "origin=Debian,codename=${distro_codename}-updates";
//      "origin=Debian,codename=${distro_codename}-proposed-updates";
        "origin=Debian,codename=${distro_codename},label=Debian";
        "origin=Debian,codename=${distro_codename},label=Debian-Security";
        "origin=Debian,codename=${distro_codename}-security,label=Debian-Security";
        "o=namespaces/moz-fx-productdelivery-pr-38b5/repositories/mozilla,n=mozilla";

        // Archive or Suite based matching:
        // Note that this will silently match a different release after
        // migration to the specified archive (e.g. testing becomes the
        // new stable).
//      "o=Debian,a=stable";
//      "o=Debian,a=stable-updates";
//      "o=Debian,a=proposed-updates";
//      "o=Debian Backports,a=${distro_codename}-backports,l=Debian Backports";
};

This has always worked for me although it was on Ubuntu with the Mozillateam PPA. But it should be the same. EDIT: I also used it with the Google Chrome repository on Debian.

By the way you can see in the output of "apt policy" where this line came from.

[Shamak]

I'm a little unsure if this will work with @bbbhltz's pinning. I'm wondering if the pinning should be Package: firefox-esr instead of Package: *. I'm wondering it the Package: * would keep unattended-upgrades from updating Mozilla's Firefox. But maybe they or someone else can speak to that as I can muddle through pinning but am no expert.

I see blackbird has a similar concern.

I also notice the origin in bbbhltz's post is different than the origin in "apt policy". Is that important? Wiser minds than mine will have to work this out.

[fabien]

(probably in /etc/apt/preferences.d/)?

You'd think, but synaptic has its own settings that may be ignored by apt.

/var/lib/synaptic/preferences

Thanks. Indeed, I wouldn't have imagined such an awful solution, good to know. Something to remember to test in a VM.
Think about what happens if you set such a "preference" and then use apt or aptitude or some other apt front-end or unattended-upgrades.
I'm still interested in the contents of this /var/lib/synaptic/preferences

With priority 1 he won't get any updates of firefox (without esr) from Mozilla.

With priority 1, firefox will be updated if no other source offers it. Set priority to -1 to disable a source completely.
edit: I think you're right. According to the manual:

0 < P < 100
causes a version to be installed only if there is no installed version of the package

Pinning requires good testing of its effects.

I'm a little unsure if this will work with @bbbhltz's pinning. I'm wondering if the pinning should be Package: firefox-esr instead of Package: *. I'm wondering it the Package: * would keep unattended-upgrades from updating Mozilla's Firefox.

This will work, including with unattended-upgrades. But I agree, it's better to pin packages individually. This means pinning mozilla repo to -1 and pinning firefox from the mozilla repo to say 100 (so firefox-esr is updated from the debian repo).

[Shamak]

@Diesel330 , please note that I made a mistake in my post. I put /etc/apt/apt.conf.d/50-unattended-upgrades when it should have been /etc/apt/apt.conf.d/50unattended-upgrades. It's now been corrected.

[CwF]

I'm still interested in the contents of this /var/lib/synaptic/preferences

Code: Select all

$   cat /var/lib/synaptic/preferences
Package: dvb-apps
Pin: version 1.1.1+rev1500-1.2
Pin-Priority: 1001

I've typed about that a few times. It's all synaptic, or only for reference only and not management. Another issue is a unified package history. If we take the time to build a local repo with dpkg.dev for all foreign packages, and add the entry to sources.list, then all is coherent within synaptic. Foreign packages show as 0 download size installed by foreign means or no longer in the repo, locally available shows as 1. Truth be told synaptic has done all my package management from deb10 to current, so a perfect history with some gaps in the deb8 to 10 time frame.

Synaptic is not a great tool for mix-n-match methods. It is a fantastic tool for total management.

[sunrat]

But I'm not sure if this is needed, having firefox-esr and firefox from Mozilla should be fine. They are both updated from the Mozilla repos.

Agreed. I accidentally upgraded to Mozilla FF-ESR a few days ago and have been using it as default browser since. It is performing excellently and, although not empirically tested, feels more responsive than the old Debian FF-ESR. Will likely stick with it and remove the non-esr Firefox; one doesn't need 4 browsers!

[Shamak]

I also notice the origin in bbbhltz's post is different than the origin in "apt policy". Is that important?

I get my confusion now. You can do it by origin url or repository name.

https://wiki.debian.org/AptConfiguratio ... repository

[blackbird]

With priority 1 he won't get any updates of firefox (without esr) from Mozilla.

With priority 1, firefox will be updated if no other source offers it. Set priority to -1 to disable a source completely.
edit: I think you're right. According to the manual:

0 < P < 100
causes a version to be installed only if there is no installed version of the package

I can confirm this from own experience. Some time ago I tried the Mozilla repos since firefox from Debian is old and the Flatpak version is too slow. Since it wanted to overwrite the Debian firefox-esr I first wanted to reason about what I want and set the priority of the repo to 1. And recently I went on with this topic and saw that firefox form Mozilla is still in version 128 and not updated. I think the warnings in the debian wiki about pinning should be taken serious, it's something for experts.

[fabien]

Code: Select all

$   cat /var/lib/synaptic/preferences
Package: dvb-apps
Pin: version 1.1.1+rev1500-1.2
Pin-Priority: 1001

Thanks, that's what I assumed, the Synaptic procedure pins the package to a fixed version and it never gets upgraded (this is the same as putting a package on hold with apt-mark).

I can confirm this from own experience. Some time ago I tried the Mozilla repos since firefox from Debian is old and the Flatpak version is too slow. Since it wanted to overwrite the Debian firefox-esr I first wanted to reason about what I want and set the priority of the repo to 1. And recently I went on with this topic and saw that firefox form Mozilla is still in version 128 and not updated. I think the warnings in the debian wiki about pinning should be taken serious, it's something for experts.

Thank you for your confirmation. Maybe not expertise, but experience as you just demonstrated. I don't use pinning because I'm on stable and since my sources.list is as simple as possible, I just use it for experimental purposes. Nothing replaces real experience. But first read the documentation:
Debian Wiki - AptConfiguration - apt_preferences (APT pinning)
Debian Reference - Chapter 2. Debian package management - 2.7.7. Tweaking candidate version with apt-pinning

Warning

Use of apt-pinning by a novice user is sure call for major troubles. You must avoid using apt-pinning except when you absolutely need it.

Without the "/etc/apt/preferences" file, APT system choses the latest available version as the candidate version using the version string. This is the normal state and most recommended usage of APT system. All officially supported combinations of archives do not require the "/etc/apt/preferences" file since some archives which should not be used as the automatic source of upgrades are marked as NotAutomatic and dealt properly.

[Shamak]

This has always worked for me although it was on Ubuntu with the Mozillateam PPA. But it should be the same.

I forgot that I used this method on Debian with the Google Chrome repository as well.

[Shamak]

There's also the slick way which I haven't tried because I didn't know about it when I was doing this. If you have sudo installed just run this command.

Code: Select all

echo 'Unattended-Upgrade::Allowed-Origins:: "o=namespaces/moz-fx-productdelivery-pr-38b5/repositories/mozilla,n=mozilla";' | sudo tee /etc/apt/apt.conf.d/51unattended-upgrades-mozillarepository

This was slightly adapted for Debian from the following AskUbuntu page.

https://askubuntu.com/questions/1492981 ... r-priority

[Diesel330]

Thanks for the guidance @Shamak , I want to see what's gonna happen with the next updates of those browsers before I try anything else, I will report back

[friendlysalmon88]

I found this discussion quite helpful as matter of fact I've already bookmarked both the post and the page on the mozilla wiki in addition.

[Lesha]

I decided that I don't trust Brave any more, there's something wrong with it, but I need a second browser along with FF ESR which is preinstalled and updates automatically. I want the same situation with the regular FF, is it possible?

I read the question and answers. Mark the solution, please, what saved you?

[Diesel330]

I decided that I don't trust Brave any more, there's something wrong with it, but I need a second browser along with FF ESR which is preinstalled and updates automatically. I want the same situation with the regular FF, is it possible?

I read the question and answers. Mark the solution, please, what saved you?

This is an old thread, I don't remember if I tried everything the guys suggest but my current situation is that I have 2 FireFoxes, ESR and regular and both maintained by Mozilla which means no updates on the fly, When notification comes I must go to the software manager and click ''download and update'' and restart the computer, Nothing like the Debian maintained FF which updated while you were using it. So basically nothing saved me, I just used to the new situation

[Lesha]

I decided that I don't trust Brave any more, there's something wrong with it, but I need a second browser along with FF ESR which is preinstalled and updates automatically. I want the same situation with the regular FF, is it possible?

I read the question and answers. Mark the solution, please, what saved you?

This is an old thread, I don't remember if I tried everything the guys suggest but my current situation is that I have 2 FireFoxes, ESR and regular and both maintained by Mozilla which means no updates on the fly, When notification comes I must go to the software manager and click ''download and update'' and restart the computer, Nothing like the Debian maintained FF which updated while you were using it. So basically nothing saved me, I just used to the new situation

Thanks to Diesel330. At least we can guess how it behaves, and what to do next ...