this post was submitted on 27 Oct 2024
354 points (97.8% liked)
Technology
59708 readers
2383 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's just very unfortunate timing. Google removed some library Firefox depended on in NDK and it meant developers need to make significant changes to their packaging system. At the same time critical vulnerably was discovered in Firefox. On top of that, everything happened when main developer of Fennec was away from home and short on time. But from what I've seen on Fennec gitlab most of the work is done so you should expect update soon.
Yep, it's this. Annoying change, but from what I was reading, perfectly solvable with a little time. Unfortunately the dev was moving house, so they fell a version behind at the worst possible moment, but they're aware of the issue. I'm not too concerned.
Had it not been for FDroid's warning, I wouldn't have even realized Fennec was a version behind (now 2). Normally it's not that big a deal.
Firefox 130 was released on the 3th of September, almost 2 months ago. This didn't just happen in a short time frame.
Fennec being a version behind for over a month because the dev was absent wouldn't normally be that big a deal if not for the vulnerability being discovered.