scoop update * not updating local bucket git repos
#5330
Replies: 7 comments 4 replies
-
|
see also: |
Beta Was this translation helpful? Give feedback.
-
|
I also can't just re-install: |
Beta Was this translation helpful? Give feedback.
-
|
I had to manually remove |
Beta Was this translation helpful? Give feedback.
-
|
Unable to reproduce on powershell.exe, Windows 11
|
Beta Was this translation helpful? Give feedback.
-
|
yeah, this is why I'm trying to transition to 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. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @fluffynuts I appreciate you're trying to make things better, but I don't think the attitude of calling out specific individuals is helping. If some open source tool doesn't solve your problems, it's fine to say that. But unless people are getting paid to maintain scoop I don't think we're entitled to a fix. |
Beta Was this translation helpful? Give feedback.
-
|
Hi yourself I suggested a solution (scoop should do what every user has to do - use PowerShell to update pwsh - or scoop should simply not manage pwsh, as it's now something which can be installed by Winget and kept up to date by windows update; or there's a third option where cleverness with an extra process could update pwsh without pwsh running). I would have been happy to participate in the implementation, but it was clear that a specific person wasn't onboard. I've raised PRs before (on other projects, to be clear) that languish and eventually rot. What a waste of time and effort! If there's no buy-in from the people who maintain the project, there's a good chance that I'd do that work for nothing. Hence my statements and my abandonment of scoop. You may have just come in to see the tail end of the conversation, and it's easy to assume I'm just another entitled user, when the opposite is true: I used to heartily recommend scoop to people, I got involved who I could, reporting bugs, trying to find ways around them, feeling out if I could positively contribute. I've given up on that - too many other things to get done and Winget is working "ok" for me, though nothing is ever perfect. I wish the project and its users well. I hope that some day, users can just update pwsh easily via scoop and never even have to see this issue again. Since the workaround is relatively simple (but arcane knowledge, let's be honest - it's not obvious that pwsh must be updated differently from other software), that could have been implemented in the year since this discussion - but it wasn't, so read into that what you will. |
Beta Was this translation helpful? Give feedback.
-
|
I'm definitely more on the outside of this than you! I just opened a new issue linked from that thread for another footgun around I'm particularly irked that I have come back to this issue thread multiple times trying to get the workaround to work. I haven't looked into using |
Beta Was this translation helpful? Give feedback.
-
|
The only downside is how long it takes for a new pwsh version to end up in winget - if you have the update reminder enabled in pwsh (it defaults on), you'll have a few days or a week when pwsh moans at you every time it starts up. So what I've done now is:
|
Beta Was this translation helpful? Give feedback.
-
Would you mind showing me one more instance where I did this?
What logs? Scoop does not log anything
What scripts? I ran the all the exact commands you gave me, and showed you
That's precisely what I did. Do you want me to spell out "plz help"? |
Beta Was this translation helpful? Give feedback.
-
in the included link about pwsh: ScoopInstaller/Main#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"
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?
the scripts that are scoop. Since a hard reinstall fixed it, there must have been something wrong, no?
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": |
Beta Was this translation helpful? Give feedback.
-
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 ScoopInstaller/Main#3572, I crack open powershell.exe,
pskill pwshandscoop update *and nothing happens. Scoop claims it's all up to date.So I deleted
~/.config/scoop/config.jsonand try again - I get the message that the last update time isn't set and scoop proceeds to update nothingSo I had to head manually off into each of the bucket repos under
~/scoopandgit pull --rebase, after whichscoop 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" }Beta Was this translation helpful? Give feedback.
All reactions