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

error code inconsistent with vso output #159

Open
jardon opened this issue Dec 6, 2024 · 1 comment
Open

error code inconsistent with vso output #159

jardon opened this issue Dec 6, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@jardon
Copy link
Member

jardon commented Dec 6, 2024

As you can see in the output below, vso reports an error code of 100 but the process exits with 0

vso sideload -- ../vanilla-installer_2.4.0_amd64.deb
Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease
Get:3 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  InRelease [1,581 B]
Err:3 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A4B469963BF863CC
Hit:2 https://repo2.vanillaos.org sid InRelease
492 packages can be upgraded. Run 'apt list --upgradable' to see them.
Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A4B469963BF863CC
Warning: Failed to fetch https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A4B469963BF863CC
Warning: Some index files failed to download. They have been ignored, or old ones used instead.
Note, selecting 'vanilla-installer' instead of '../vanilla-installer_2.4.0_amd64.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 vanilla-installer : Depends: albius but it is not installable
Error: Unable to correct problems, you have held broken packages.
Error: exit status 100
Usage:
  vso sideload [flags]

Flags:
  -h, --help   help for sideload

  ERROR   exit status 100
echo $?
0
@jardon jardon changed the title error code inconsistent with vso outpute error code inconsistent with vso output Dec 6, 2024
@jardon
Copy link
Member Author

jardon commented Dec 6, 2024

this may also be relevant to apx as the pico components are dependent on apx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants