-
Notifications
You must be signed in to change notification settings - Fork 25
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
Arch Linux: error: could not open file /var/lib/pacman/sync/selinux.db: Unrecognized archive format #124
Comments
Same error for me,
But i manule download all release packges and manule install it, in short time is ok, but is not a good idea for it |
Hello, For information, the command which created the SELinux repository are selinux/.github/workflows/main.yml Lines 187 to 202 in d6b4793
These commands download all built packages, run ... And searching about similar issues, I found out this appears to be a GitHub issue in I've just triggered the build&release workflow again (https://github.com/archlinuxhardened/selinux/actions/runs/10334164646). Let's see if this un-breaks things. |
Thanks, is look like need take some time to build packges, later I will test it and give you feed back. |
The workflow succeeded and my test environment was able to download and use |
Is work now thanks for you help.
|
Hello. Yes it works for me now. Thanks for the quick fix! |
Since a few days ago, I have been facing an issue where running
sudo pacman -Syu
andsudo pacman -Syyu
outputs the following error, then the command will end. It does look like this started with the release that was done 4 days ago.When inspecting
/var/lib/pacman/sync/selinux.db
it seems that all that files contains is the text "selinux.db.tar.xz". I have tried deleting the file, but it regenerates with the same contents. If i comment out the selinux lines from /etc/pacman.conf, it at least lets pacman upgrade the core and extra packages, but selinux will no longer update.Does anyone have any ideas on how to fix this?
The text was updated successfully, but these errors were encountered: