Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Bug] When scoop is first installed, the main bucket possibly does not point to the best URI #6171

Closed
Gitoffthelawn opened this issue Oct 6, 2024 · 1 comment
Labels

Comments

@Gitoffthelawn
Copy link

Bug Report

Current Behavior

When scoop is first installed, the user can install applications from the main bucket before issuing a scoop bucket add main command (in fact, it seems they never need to issue that command). But without issue the scoop bucket add main command, the main bucket doesn't seem to point to the ideal URI. This can be seen when a scoop update command is issued; scoop will then change the URI for the main bucket.

Expected Behavior

I think it will be best if this little bit of confusion can be avoided, because it may leave the user wondering "were my apps installed from the right source"? (If the bucket has the wrong source, then all manifests in that bucket can be wrong.)

Additional context/output

Question: When the user never invokes a scoop bucket add main command, is the correct main bucket (and thus the correct main bucket manifests) always used?

Possible Solution

Perhaps always include the ideal URI for the main bucket in scoop by default. If this isn't possible, perhaps automatically issue scoop bucket add main when scoop is installed.

System details

Windows version: 11

OS architecture: 64bit

PowerShell version:

Major Minor Build Revision
5 1 22621 4111

Additional software: git

Scoop Configuration

{
    "last_update":  "2024-10-06T04:31:19.2938152-00:00",
    "virustotal_api_key":  "[redacted]",
    "scoop_repo":  "https://github.com/ScoopInstaller/Scoop",
    "scoop_branch":  "master"
}
@HUMORCE
Copy link
Member

HUMORCE commented Oct 11, 2024

#6172

@HUMORCE HUMORCE closed this as completed Oct 11, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants