GNU bug report logs - #73093
Shouldn't Icecat should be moving to the 128.x.x branch?

Previous Next

Full log

View this message in rfc822 format

From: Nin Gen <0xningen <at> gmail.com>
To: 73093 <at> debbugs.gnu.org
Subject: bug#73093: Shouldn't Icecat should be moving to the 128.x.x branch?
Date: Sat, 7 Sep 2024 01:13:22 +0000

[Message part 1 (text/plain, inline)]

Hi all,

I am just wondering shouldn't icecat be moving to 128.x.x now? There are
already esr release builds for this branch
https://ftp.mozilla.org/pub/firefox/releases/128.2.0esr/ and the 115.x.x
branch will be moving to deprication.

The main reason why I bring this up is because on rolling release distros
like ArchLinux, we are unable to compile Icecat 'cleanly as is' due to
clang17/llvm17 being required to build Icecat since 115.13.0 onwards, and
since the current version of clang/llvm is 18 which seems not backwards
compatible we cannot compile Icecat without compiling an older
clang17/llvm17 independently which is very troublesome and problematic.

Thank you,

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.