FIrefox disappears from v3 repositories when there is an update, causing pacman to “upgrade” to the standard arch version. It happened with 133 > 134 and is now happening with 134.1 > 134.2. The package is just not there. I think that even if the package is not planned to be updated soon, the older version should stay in the repo so pacman doesnt install the unoptimized version. From what i’ve seen this doesn’t happen in v4.
I wouldn’t be surprised if that’s during the build process (but I don’t know). Err, that’s probably what you’re saying…
That is pretty normal when new version is pushed to arch repos. It will take some time that the optimised build process runs through, and then it will come available in the cachy-repos
I know that packages are slightly delayed, but that’s not what i’m saying
1.I don’t think it is supposed to be delayed for a week, usually it is like 3 hours to a day
2.Even if the package is getting delayed or built, the old version should still be available to download. That’s not the case (firefox 134.0.2 is not yet ready and 134.0.1 was deleted from the v3 repos)
I believe this is caused by both v3 and v4 repos sharing the same builder. It is likely that they run in parallel (can’t confirm) so for these heavy PGO builds (firefox, electron), one build from either repo will inevitably fail. Unfortunately, I don’t think there’s been a fix yet from our side.