-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[install] Pacman segfaults with a single server in the mirrorlist #802
Comments
instead of 'wget' for the Pacman XferCommand. Resolves #802
instead of 'wget' for the Pacman XferCommand. Resolves #802
instead of 'wget' for the Pacman XferCommand. Resolves #802
It seems like the issue is with Pacman itself. There is a known bug that Pacman will result in a segfault when (1) there is only one server in a mirrorlist and (2) GPG key checking is enabled. This was fixed 1 week ago. The latest release of Pacman is 6.1.0 from 3 weeks ago. We will have to wait for a new release of Pacman. https://bbs.archlinux.org/viewtopic.php?id=293911 |
This issue only appears while using the new |
A bugfix Pacman 6.1.1 release with this fix is being planned. https://gitlab.archlinux.org/pacman/pacman/-/milestones/2#tab-issues |
from the live environment within the chroot. This makes downloads faster and avoids issues when a single or no mirror is configured. Related #802
I can confirm that (1) not using a single mirror and (2) commenting out the |
if pacman is not working we can use this command
|
I can verify that adding a duplicate Server line immediately beneath the existing one for only the So it is the same bug from upstream. |
@GuestSneezeOSDev Thanks for the suggestion! I gave it a try but the service checks to see if the Linux kernel version is 5.6 or older before starting. Newer Linux kernels appear to have patches that make the random entropy on-par with what @JerryWJackson Thanks for confirming! I'm holding out for Pacman 6.1.1 to be released instead of relying on the mentioned workaround of adding an extra Oddly, our GitHub Actions pipelines used to fail with this issue on the Chaotic AUR repository but that is no longer the case. I only notice it on local builds. We use container builds (with cache removed) so everything is supposed to be reproducible but apparently it is not. |
It has now been 3 months since the last Pacman release. I looked at their release history for comparison. Usually a new release comes every 1 month. At most, it takes 4 months. We're aiming to have another winesapOS stable release next month. If Pacman is still not updated by then, we'll apply the manual workaround of having duplicate |
to allow package downloads to work again. Related #802
to allow package downloads to work again. Related #802
to allow package downloads to work again. Related #802
Have you tried building it manually? or you could rebuild the repo |
Great idea, yes, building our own version of Pacman (probably |
Pacman 7.0.0 finally came out last week with the fix for this issue. The developers decided to just skip a 6.1.1 bug fix release and jump straight to 7.0.0. However, Pacman 7.0.0 is not available in Arch Linux yet. https://linuxiac.com/pacman-7-0-package-manager-released/ |
The Update should be in the AUR |
Yeah, it'll already be in The winesapOS 4.1.0 has partially been blocked by this issue but we've also been waiting for explicit sync support for NVIDIA to work on Wayland. That should finally be in all of our packages, including Related: #818 |
Pacman 7.0.0 has a major bug where |
Pacman will always report a
segmentation fault
when trying to download database files when theXferCommand
is configured to usewget
.The text was updated successfully, but these errors were encountered: