Upgrade to firefox 135?

I’m guessing I’m stuck. I am running Manjaro on an ARM pinebook pro, and Firefox is telling me to upgrade to 135 by 14 March. However, packmanager says I’m on the current version of firefox.

Am I stuck?

1 Like

I’ve seen this message pop up in Floorp’s subreddit - because Floorp was using ESR… in that case the pop-up was an error, Floorp being a tad buggy.

Hi,

Are you on stable branch ? Firefox 123.0-1 is out of date, for sure, look below the branch compare tool

https://manjaristas.org/branch_compare?q=firefox&arm=on

You can install Firefox verion 134 from Unstable Branch.

How do I install the unstable branch of manjaro?

1 Like

Sometimes, I just install Firefox from Unstable Branch to Stable using

sudo pacman -U https://mirror.alpix.eu/manjaro/arm-unstable/extra/aarch64/firefox-134.0.2-1-aarch64.pkg.tar.xz

It usually works but at times it won’t install as there are unmet dependencies.

1 Like

Well poo. The command works, but firefox won’t launch. Tried 132 also, same story.

May be Manjaro-Arm Team might have a solution for you. Else you might have to switch to Unstable Branch for newer Firefox.

Have been on Unstable Branch for around 2 years now.

1 Like

The only branch being maintained right now is the unstable branch. I know of no plans to upgrade the testing or or stable branch in the foreseeable future.

Can you talk me through how to switch to unstable branch manjaro?

I am no expert follow here change “testing” to “unstable”.

Testers needed on arm-testing branch

We are in need of testers for our arm-testing and arm-unstable branches.
So if you are adventurous and want newer software quicker, we would love for you to help us test out the new packages in arm-testing branch.

All you have to do to switch to this branch is:

  • Run this command to switch branch: sudo pacman-mirrors -aS testing && sudo pacman -Syyu. This will generate a new mirrorlist for you, sync your databases with the new mirror and update your system using the arm-testing branch.

On receiving the News Item Update – error failed retrieving file community db I used the Kate option to remove the reference to ‘Community’ and save the file.

Then, trying to get Firefox upgraded before it turns into a pumpkin on 14th March, I searched further on the forum and found the suggestion of using

sudo pacman-mirrors -aS testing && sudo pacman -Syyu

This seemed to be working well and I left it running, but when I returned to check on progress, it had crashed, with the following error message:

error: failed retrieving file ‘kwin-6.2.3-1-aarch64.pkg.tar.xz.sig’ from ask4.mm.fcix.net : Resolving timed out after 10000 milliseconds
warning: failed to retrieve some files
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
[petern@Rpi ~]$

I noted from the Information icon that 155 package upgrades were available, so, perhaps naively, I tried to run an upgrade from there. However, Pacman responded with another error message:

could not satisfy dependencies:

  • removing gspell breaks dependency ‘gspell’ required by evince
    - installing icu (75.1-1) breaks dependency ‘libicuuc.so=74-64’ required by harfbuzz-icu
    - if possible, remove harfbuzz-icu and retry
    - removing libpamac breaks dependency ‘libpamac’ required by libpamac-snap-plugin
    - removing libpamac breaks dependency ‘libpamac>=11.6.3’ required by pamac-cli

I am not a systems person, and I would be very grateful for any assistance to help me find my way out of these problems, (a) to ensure I have a viable OS and (b) to help me find a useful version of Firefox. My set up is a Raspberry Pi 4B with 4GB RAM.

You were trying to switch to testing branch which is not being maintained either.

sudo pacman-mirrors -aS unstable && sudo pacman -Syyu

Your system is so outdated that it is going to require some manual intervention when updating. Take care of the errors one by one. Also looks like your mirrors are outdated also.

Thanks for the advice, Darksky; I’m now up and running, and the only problem I’ve encountered so far arose from my own mistake (a typo in an e-mail address which led to an obscure error message from my e-mail service provider’s mail server referring to an unspecified ‘syntax error’ - which led to a lot of head-scratching and detailed checking of the set-up of my e-mail account in Claws Mail before I found the guilty party!)

1 Like