Scoop
Scoop copied to clipboard
`scoop update *` not updating local bucket git repos
Bug Report
I noticed today pwsh telling me there was an update (from my 7.2.3 to 7.2.4). So naturally, being aware of https://github.com/ScoopInstaller/Main/issues/3572, I crack open powershell.exe, pskill pwsh and scoop update * and nothing happens. Scoop claims it's all up to date.
So I deleted ~/.config/scoop/config.json and try again - I get the message that the last update time isn't set and scoop proceeds to update nothing
So I had to head manually off into each of the bucket repos under ~/scoop and git pull --rebase, after which scoop update * had heaps of updates to do.
(I did also try from within pwsh 7.2.3 before getting brute-force on it, and again, no updates applied)
Current Behavior
Doesn't pull git changes to buckets, so updates don't happen.
Expected Behavior
Should pull the git changes & perform updates
Possible Solution
I dunno, this used to work.
System details
Windows version: win11
OS architecture: 64bit
PowerShell version: 5.1.22000.653
Additional software: [(optional) e.g. ConEmu, Git]
Scoop Configuration
{
"SCOOP_BRANCH": "master",
"lastupdate": "2022-05-18T09:46:04.1056781+02:00",
"SCOOP_REPO": "https://github.com/ScoopInstaller/Scoop"
}
see also:

I also can't just re-install:

I had to manually remove ~/scoop/shims/scoop* and then run Invoke-WebRequest get.scoop.sh | Invoke-Expression; now scoop update * works 😕
Unable to reproduce on powershell.exe, Windows 11

yeah, this is why I'm trying to transition to winget - "unable to repro, glhf" (and let's be honest, winget has it's own set of issues :| )
this is far from the first issue I've raised and it's always @rashil2000 responding with "sucks to be you"
no "gimme logs, I want to understand", no "do you have the scoop scripts that were failing", just "works on my machine". Not even a "can't repro, plz help".
A package manager is all about empowering the user. You should read some gentoo bug reports to see how to opensource.
this is far from the first issue I've raised and it's always @rashil2000 responding with "sucks to be you"
Would you mind showing me one more instance where I did this?
no "gimme logs, I want to understand",
What logs? Scoop does not log anything
no "do you have the scoop scripts that were failing", just "works on my machine".
What scripts? I ran the all the exact commands you gave me, and showed you
Not even a "can't repro, plz help".
That's precisely what I did. Do you want me to spell out "plz help"?
this is far from the first issue I've raised and it's always @rashil2000 responding with "sucks to be you"
Would you mind showing me one more instance where I did this?
in the included link about pwsh: https://github.com/ScoopInstaller/Main/issues/3572 where I, and other users, have expressed that the current situation should be remedied: having a package manager which can install a package once but not update it is totally unexpected. Your responses there are basically "nope"
no "gimme logs, I want to understand",
What logs? Scoop does not log anything
if your scoop works and mine does not, then one avenue I would take if I were you would be to ask for copies of my scoop scripts. Perhaps something got broken in an update?
no "do you have the scoop scripts that were failing", just "works on my machine".
What scripts? I ran the all the exact commands you gave me, and showed you
the scripts that are scoop. Since a hard reinstall fixed it, there must have been something wrong, no?
Not even a "can't repro, plz help".
That's precisely what I did. Do you want me to spell out "plz help"?
incorrect: you literally just said "unable to reproduce on powershell.exe, Windows 11". Which anyone would tell you does not include any attempt to gather more information or fix the problem. It just says "works for me":
