Skip to content
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 Error #1

Closed
Lokilittle opened this issue Apr 8, 2023 · 13 comments
Closed

Install Error #1

Lokilittle opened this issue Apr 8, 2023 · 13 comments
Assignees

Comments

@Lokilittle
Copy link

Hello, thank you for making this, unfortunately I get this in my terminal and nothing installs.

==> Appending keys from archlinux.gpg...
==> Updating trust database...
gpg: next trustdb check due at 2023-04-21
:: Synchronizing package databases...
jupiter-rel 87.4 KiB 243 KiB/s 00:00 [###########################################################################] 100%
holo-rel 41.9 KiB 117 KiB/s 00:00 [###########################################################################] 100%
core-rel 157.3 KiB 414 KiB/s 00:00 [###########################################################################] 100%
extra-rel 1721.5 KiB 3.82 MiB/s 00:00 [###########################################################################] 100%
community-rel 7.1 MiB 10.2 MiB/s 00:01 [###########################################################################] 100%
multilib-rel 168.7 KiB 405 KiB/s 00:00 [###########################################################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) lib32-libxcrypt-compat-4.4.28-2

Total Download Size: 0.07 MiB
Total Installed Size: 0.18 MiB

:: Proceed with installation? [Y/n]
:: Retrieving packages...
lib32-libxcrypt-compat-4.4.28-2-x86_64 70.7 KiB 384 KiB/s 00:00 [###########################################################################] 100%
(1/1) checking keys in keyring [###########################################################################] 100%
(1/1) checking package integrity [###########################################################################] 100%
error: lib32-libxcrypt-compat: signature from "Alexander Epaneshnikov [email protected]" is unknown trust
:: File /var/cache/pacman/pkg/lib32-libxcrypt-compat-4.4.28-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

@Tritschla
Copy link
Owner

Hi,

I've updated the script to use a different command in regards to setup the needed keyring.
I hope this resolves the issue.

Please launch the "InstallResilio4SteamDeck.desktop" (downloaded in step 1) again to see, if the installation is now working.

@Lokilittle
Copy link
Author

I downloaded the new script and still no install. I tried running the install.sh line by line in terminal and I get error here.
47: sudo -S pacman -Syyu --noconfirm lib32-libxcrypt-compat

The error message is:

error: lib32-libxcrypt-compat: signature from "Alexander Epaneshnikov [email protected]" is unknown trust
:: File /var/cache/pacman/pkg/lib32-libxcrypt-compat-4.4.28-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

@Tritschla
Copy link
Owner

And I renewed the script to use "echo "$PASSWORD" | sudo pacman -Syy --noconfirm" before trying to install the package. Please may you test this?

@Lokilittle
Copy link
Author

I get the same error with the updated package. I'm sorry, I'm new to linux.

@Tritschla
Copy link
Owner

The script is asking you to delete the corrupted file, did you do that?
If not, please do that and rerun the whole script

@Lokilittle
Copy link
Author

I've tried to delete the file but I can't find it either in terminal or through the dolphin file browser.

@Tritschla
Copy link
Owner

when you use the command "sudo -S pacman -Syyu --noconfirm lib32-libxcrypt-compat" it is giving you the error message following with "Do you want to delete it? [Y/n]". Please press Y and hit enter to delete the file

@Lokilittle
Copy link
Author

Terminal displays the message "Do you want to delete it? [Y/n]" but it never gives me the chance to enter a key. It runs through the rest of the text. Same with the "proceed with installation [Y/n]" I'm never given the chance to enter a response.

@Tritschla
Copy link
Owner

My bad :-)
sudo -S pacman -Syyu lib32-libxcrypt-compat makes it, so you can go on.

@Lokilittle
Copy link
Author

For some reason this wouldn't update the package. After messing around I got it working by replacing the problematic line with:
sudo cp -r -t "/usr" "/home/deck/ResilioSync/usr/lib32"

After following these steps from the SteamDeck resilio sync thread:
1-Go to the AUR page for lib32-libxcrypt-compat and click "Download from Mirror"
2-Extract the "/usr" folder from this package and place it somewhere safe; I have it in my "/home/Deck/Resilio Sync" folder.
3-Paste the below code into a text editor, swapping out "home/deck/Resilio Sync" to the folder you saved the /usr folder to.

I re-ran your script with the changed line and now all my files are synced. Perhaps my SteamDeck is cursed.

@Tritschla
Copy link
Owner

Tritschla commented Apr 13, 2023

ok, thank you for the feedback. I hope that the tool now will run fine for you. I will try to get the situation rebuilt on my side to have a deeper look how the script could get this problem solved for you automatically if you want to use it in the fututre.

If you like, you may run the following command in konsole and give me the output: pacman-key --list-sigs Master

@Tritschla Tritschla self-assigned this Apr 13, 2023
@Tritschla
Copy link
Owner

Did you had the opportiunity to test this or should we leave this for now, since it is working for you, the way you got it working?

@Tritschla
Copy link
Owner

Please note, this issue is set to solve, since it is based on the same problem as the more frequent issue #2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants