[arch-general] Fwd: glibc flagged out-of-date
Hi.... Why is Arch Linux core repository still using glibc version 2.33? Why not upgrade the core repository to version 2.34, since it was flagged out-of-date on 2021-08-02? Thanks.
I'm pretty sure libc updates are very difficult to do and require recompiling a lot of packages. On 13 November 2021 21:56:35 GMT, Fabiano Furtado Pessoa Coelho via arch-general <arch-general@lists.archlinux.org> wrote:
Hi....
Why is Arch Linux core repository still using glibc version 2.33? Why not upgrade the core repository to version 2.34, since it was flagged out-of-date on 2021-08-02?
Thanks.
Le 14 novembre 2021 02:52:40 GMT+04:00, KSP Atlas via arch-general <arch-general@lists.archlinux.org> a écrit :
I'm pretty sure libc updates are very difficult to do and require recompiling a lot of packages.
On 13 November 2021 21:56:35 GMT, Fabiano Furtado Pessoa Coelho via arch-general <arch-general@lists.archlinux.org> wrote:
Hi....
Why is Arch Linux core repository still using glibc version 2.33? Why not upgrade the core repository to version 2.34, since it was flagged out-of-date on 2021-08-02?
Thanks.
This has been partly discussed recently already, but regarding what is generally called as “tooling” (libc, gcc, etc.) upgrades can be very complex indeed, especially while trying to make package reproducibles, which is one of the somewhat recent Arch goals. So this update is in the pipeline, actually they have been several peoples working on this lately, so it will happen at some point. But as I said in a recent thread, updating a package is not just about using your editor of choice to change the pkgver line. Regards, Bruno/Archange
Em novembro 13, 2021 18:56 Fabiano Furtado Pessoa Coelho via arch-general escreveu:
Hi....
Why is Arch Linux core repository still using glibc version 2.33? Why not upgrade the core repository to version 2.34, since it was flagged out-of-date on 2021-08-02?
Thanks.
Mostly time. Toolchain updates are very time consuming, even using the build server Arch has. I got some help recently and I'm working to finish the update soon, as well as I'm trying to lay a better foundation for future updates. Updating the toolchain is sometimes a trial and error process, with the added issue that it takes hours between your error and you noticing that error. I got some emails regarding this and I wish to thank everyone that asked me directly regarding this. Regards, Giancarlo Razzolini
On Mon, 2021-11-15 at 17:46 -0300, Giancarlo Razzolini via arch-general wrote:
Em novembro 13, 2021 18:56 Fabiano Furtado Pessoa Coelho via arch- general escreveu:
Hi....
Why is Arch Linux core repository still using glibc version 2.33? Why not upgrade the core repository to version 2.34, since it was flagged out-of-date on 2021-08-02?
Thanks.
Mostly time. Toolchain updates are very time consuming, even using the build server Arch has. I got some help recently and I'm working to finish the update soon, as well as I'm trying to lay a better foundation for future updates.
Updating the toolchain is sometimes a trial and error process, with the added issue that it takes hours between your error and you noticing that error. I got some emails regarding this and I wish to thank everyone that asked me directly regarding this.
Regards, Giancarlo Razzolini
You are going to be a pro soon. I feel the pain. I once wanted to build recent gcc/glibc libs for a CentOS7 box and those packages PKGBUILD files were my guidelines to succeed in doing it. Pierre, the previous maintainer, left notes about bootstrapping 3 packages (gcc -> binutils -> glibc) then, according to the notes, you need perform a second pass... I'm not even sure if all this is neccessary or not... but the whole thing is very tedious.. This is why despite getting my hands on the latest versions of those packages is burning me, I refrain from building them myselves and I just wait the official release... On the bright side, once you have done it, this becomes a mecanical process and a second nature... Hopefully, once you get the process smooth, you are going to stay the maintainer for a long time! Greetings,
Em novembro 18, 2021 4:36 Olivier Langlois via arch-general escreveu:
You are going to be a pro soon. I feel the pain. I once wanted to build recent gcc/glibc libs for a CentOS7 box and those packages PKGBUILD files were my guidelines to succeed in doing it.
Pierre, the previous maintainer, left notes about bootstrapping 3 packages (gcc -> binutils -> glibc) then, according to the notes, you need perform a second pass...
I'm not even sure if all this is neccessary or not... but the whole thing is very tedious.. This is why despite getting my hands on the latest versions of those packages is burning me, I refrain from building them myselves and I just wait the official release...
On the bright side, once you have done it, this becomes a mecanical process and a second nature...
Hopefully, once you get the process smooth, you are going to stay the maintainer for a long time!
Greetings,
We have documentation on [0]. The process is lenghty, because it takes a good amount of time to build. I do builds mostly on my own machine. If some patch fails, or tests fail, you have to start over the build in most cases (in some situations you can continue from second pass only). I'm also trying to improve the scripts I use to make the process smoother for future upgrades, too. [0] https://wiki.archlinux.org/title/DeveloperWiki:Toolchain_maintenance
participants (5)
-
Archange
-
Fabiano Furtado Pessoa Coelho
-
Giancarlo Razzolini
-
KSP Atlas
-
Olivier Langlois