I like to run Firefox in latest version and I’m just wondering how long usually takes between Mozilla releasing new Firefox version and it landing in official repository of Manjaro?
Usual cadence for Manjaro stable updates is about 2 weeks - Stable Updates - Manjaro Linux Forum
But Firefox will quite often be fast-tracked - Manjaro - Fresh & Stable
You can also switch to testing or unstable branches for quicker updates, or build the developer edition from AUR
That also applies to stuff like Firefox that’s essentially made and tested by someone else, they just need to include it into repo? I thought only stuff actually coded (or at least put together by Manjaro team itself) requires longer term testing.
Firefox usually gets fast tracked, so it should be available soon in the repo.
You can check the different branches as nicgnomic stated but I’m pretty when firefox has an update it is in the stable branch pretty fast as manjaro is a rolling release so it stays pretty much on the latest.
This is the link to the Manjaro - Branch Compare
If you want to have it right now switch your branch to Unstable, there 92.0-1 is already available.
Ok, I found a way to bypass that by downloading Firefox from Mozilla directly and it seems to update itself through built in updater. Only issue I have now is that I can’t seem to make a bloody shortcut in Application launcher so I could run Firefox from it easily. Never thought making a shortcut to executable is so complicated lol
This is not very smart @RejZoR, better not ask for help if you get in trouble.
You could have switched the branch or wait a couple of days and have the Manjaro repo version being installed.
You can also install firefox-nightly from AUR, version 94 is available since this afternoon.
What trouble? Why would there be trouble with Firefox downloaded straight from author opposed to one from repo? If they make builds stable enough for Windows, surely they can for Linux too.
Create a .desktop file.
You installed it outside the whole Manjaro package management. You need to make sure it’s upated independently from your system updates, make sure it stays compatible to other packages and don’t claim if it’s not fitting well with your selected DE themes a.s.o.
is a rule for rolling, manual install is to be prohibited
What is exactly your problem ? security/version ???
we have 2 versions (in stable):
- firefox 91.0.2-1
- firefox-developer-edition 92.0 (93 in 3…4 days ?)
and 94 exists in aur
my pacman logs (stable branch):
grep 'upgraded firefox ' /var/log/pacman.log [2021-02-09T14:00:16+0100] [ALPM] upgraded firefox (84.0-0.1 -> 85.0.1-1) [2021-02-19T17:02:23+0100] [ALPM] upgraded firefox (85.0.1-1 -> 85.0.2-1) [2021-03-01T01:57:35+0100] [ALPM] upgraded firefox (85.0.2-1 -> 86.0-1) [2021-03-08T17:33:40+0100] [ALPM] upgraded firefox (86.0-1 -> 86.0-2) [2021-03-19T12:06:03+0100] [ALPM] upgraded firefox (86.0-2 -> 86.0.1-1) [2021-04-09T19:38:06+0200] [ALPM] upgraded firefox (86.0.1-1 -> 87.0-1) [2021-04-16T09:47:38+0200] [ALPM] upgraded firefox (87.0-1 -> 87.0-2) [2021-04-28T17:12:05+0200] [ALPM] upgraded firefox (87.0-2 -> 88.0-1) [2021-05-19T15:39:30+0200] [ALPM] upgraded firefox (88.0-1 -> 88.0.1-1) [2021-06-07T19:13:38+0200] [ALPM] upgraded firefox (88.0.1-1 -> 89.0-1) [2021-06-19T06:22:40+0200] [ALPM] upgraded firefox (89.0-1 -> 89.0.1-1) [2021-07-08T16:24:10+0200] [ALPM] upgraded firefox (89.0.1-1 -> 89.0.2-0.1) [2021-07-13T13:24:15+0200] [ALPM] upgraded firefox (89.0.2-0.1 -> 89.0.2-1) [2021-07-19T13:02:30+0200] [ALPM] upgraded firefox (89.0.2-1 -> 90.0-1) [2021-07-20T23:54:43+0200] [ALPM] upgraded firefox (90.0-1 -> 90.0.1-0.1) [2021-07-23T12:56:47+0200] [ALPM] upgraded firefox (90.0.1-0.1 -> 90.0.1-1) [2021-07-28T18:48:50+0200] [ALPM] upgraded firefox (90.0.1-1 -> 90.0.2-1) [2021-08-17T12:06:28+0200] [ALPM] upgraded firefox (90.0.2-1 -> 91.0-1) [2021-08-27T16:53:04+0200] [ALPM] upgraded firefox (91.0-1 -> 91.0.2-1)
we have security updates, no reason to use another channel
and if i want beta version, i install
I do exactly that.
Here is my desktop, change the name of the guilty
The filename is in ~/Desktop called something.desktop
It does not need to be called firefox.desktop, call it anything you like.
I also have a sym link for that exec pathway to /usr/local/bin to reduce the size of my autostart config on icewm.
To esteemed members.
You may not know or may not like me for writing this…but my way saves the internet.
New integer release upgrade is a full download, similar to repo.
A point release upgrade is only a small file, which is the diff or acts like a patch.
it might only be a few kilobytes but often a couple of Mb
AFAIK it might be called a delta file
I will not dream of asking support here for my browser.
Prohibited? Srsly? I always thought Linux stands for the freedom to do whatever you wanna do (and live with the consequences of course).
And why would you install the Dev version if you want the Beta? Why not the Beta? I’m confused.
I don’t want the beta, but I want newest Firefox as soon as official final goes out. It’s taking days on official repo and that’s just too long to be honest.
Firefox v92.0-1 is now available in testing branch - Firefox - Manjaro Branch Compare
But if you want version parity with Arch for all packages you can switch to Unstable branch
I was just bored a little bit. Nah, not really. Just needed distraction. Anyway, here are all FF versions since 78 that I could find by searching the Stable Update-section of the forums:
(Format for dates is day.month.year)
Release Date Mozilla
Release Date on Manjaro Stable Branch
Longest here was 19 days (2x), quickest was 1 day.
Hi, I think that using the stable update section isn’t proper to defining when it was updated in the stable channel. Because usually the firefox packages updates aren’t related to the branch updates.
Anyway, I agree with you that they take a little too long to update the package in the stable channel.