You are not logged in.
Hi,
I update my main working system on a daily base, and today I noticed that a unusual big number of packages got an update without having a new upstream version, for example avahi went from 1:0.8+r194+g3f79789-1 to 1:0.8+r194+g3f79789-2. I wonder what’s going on and where to find further information as I did not see related information in Arch General nor in Arch Public Dev mailing list or on the website.
Can someone point out a place where to find such information, please?
regards
english is not my first language. If you find a mistake in this post, please mention it in your reply – this way I can learn. TIA
Offline
Offline
You could also subscribe to the arch-dev-public ML to be aware there was a python rebuild getting ready to be moved out of testing repos.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I am subscribed to that mailing list but I‘m skimming it most of the time, Lone_Wolf. I have read about a python rebuild but I did not expect this to have an impact on so many packages, especially on packages that do not even depend on python.
I thought about something fundamental that that would demand such a comprehensive rebuild of packages and I did wonder whether there is some central place where informations about such things can be found. Looks like this is not the case.
thanks
Last edited by nichts (2024-04-28 12:36:53)
english is not my first language. If you find a mistake in this post, please mention it in your reply – this way I can learn. TIA
Offline
Most rebuilds are listed in https://archlinux.org/todo/.
Offline
but I did not expect this to have an impact on so many packages, especially on packages that do not even depend on python.
gcc needed to be rebuilt for python 3.12 , that probably triggered a rebuilt of the whole toolchain and everything that depends on the toolchain .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
nichts wrote:but I did not expect this to have an impact on so many packages, especially on packages that do not even depend on python.
gcc needed to be rebuilt for python 3.12 , that probably triggered a rebuilt of the whole toolchain and everything that depends on the toolchain .
No rebuilds were triggered due to this gcc rebuild.
Offline