-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
unable to run "pacman -Syu" #86
Comments
Alright, i sorta fixed this by manually installing the files in /var/cache/pacman/pkg with "pacman -U ./*" |
Same thing here. Manually installed the packages in the cache, but we'll have to see when the next updates come through if this is a real fix EDIT: tried to install some new packages and I still have the issue. Pacman was complaining that the key from builder@archlinuxarm.org is unknown trust. I trusted that but still get |
At least on my device it was just an uninitialized keyring.
and try again with pacman -Syu |
Thanks a lot, works now! |
That works |
And can an ADMIN close this? |
Why don't you close it yourself? |
Because i dont know how |
Thank you FreshMosh, I just installed and was running into the same issue. This resolved for me as well. |
@Zach-15803 next to the comment button, there is a close button |
It is not work for me |
@abicorios what exactly is not working for you? |
Now I understand. Working case in Termux is next:
My mistake was next:
And it was answer
So I run:
And it was next:
And I such
So I deleted all packages and TermuxArch was broken by my hands. Cool story. Yeah? |
Hopefully https://sdrausty.github.io/TermuxArch/docs/outputarmv720180722.txt shall be of use; Running |
Okay, okay. But you can run |
@abicorios this install Arch Linux, then cannot install Arch Linux in Termux PRoot because of keyrings is a recently acquired behavior of Arch Linux in Termux PRoot that was not present earlier. I am fairly sure that the keyring shouldn't be required for users. As far as being an option for users... |
Ok.
|
The fix is to add the SigLevel like this.
|
This 6c9c119 commit should resolve the keyring issue. |
|
Is it because I have aarch64? |
@abicorios Run |
@abicorios Running |
keys
|
@abicorios Please try sdrausty's solution and run in your Termux |
This snippet should be useful too: Updating -S to read -Syyuu in |
How'd your databases get messed up @abicorios?
|
"How'd your databases get messed up @abicorios?" |
It was better before fix commit. Last fix broke Arch for me. |
Which mirror is working for you? Maybe. I need nice mirror to exclude database error. |
@abicorios Or, if anything else fails, please completely delete the install directory of Arch in Termux and run the up-to-date setupTermuxArch.sh. Anyway: to anwser your question:
|
Yes, I already tried all provided solutions.
Updating -S to read -Syyuu in keys was not help.
And I have same result:
|
@abicorios what does It also appears that you misinterpreted what @FreshMosh said:
Use
There shouldn't be any reason to delete it. More information about working with git repositories at this link: Instructional GitHub and Git Foundations Videos Can Be Downloaded for Viewing at Your Leisure. When
Simply tap for yes. https://sdrausty.github.io/TermuxArch/docs/outputarmv720180729debugrefresh.txt https://sdrausty.github.io/TermuxArch/docs/outputarmv720180729installpc.txt |
No, I made |
I reinstall Termux, and it is not help me. |
I cant update or install, i have gereated a public keyring thingy, this is what happens when i try to run "pacman -Syu" after a fresh reinstall
https://pastebin.com/VbiBsteU
The text was updated successfully, but these errors were encountered: