[Bug] Execution policy error with scoop

[dragonmkww]

I installed this with scoop, and set the alias "pacman" for "pacaptr". When I run "pacman -Syu" which should run "scoop update" it instead runs "powershell scoop update". This gives me an Execution Policy error and says that the file "C:\Users<user>\scoop\shims\scoop.ps1" is not digitally signed. My Execution Policy is set to "Bypass" so this error should never happen, right? Can you please help me fix this, because this looks really cool and I would love to try it out!

[rami3l]

@dragonmkww
Thanks for your feedback!

IIRC powershell scoop update is actually the right command, since scoop is not a launch-able subprocess.

Unfortunately, I don't have enough info to determine the root of the problem you have encountered...

There are a few things you can try though:
- Run Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser to ensure you have the good execution policy.
- Run powershell scoop update manually to ensure pacaptr is doing what it claims to do.
- If powershell scoop update doesn't work, maybe the problem is with your scoop installation. Does scoop update work instead?

---

The problem turns out to be the difference between pwsh and powershell, as discussed below.

[rami3l]

@dragonmkww
Thanks for your reply.

I'm not actively using Windows for the moment, but pacaptr does its job just using a thin wrapper layer around subprocesses, and on Windows IIRC it seems not possible to me to start a subprocess call with scoop. That's why I added powershell at the beginning: it's a valid subprocess that can launch scoop properly.

For the implementation details, all is in scoop.rs, and I do encourage you to experiment as you wish.

The subprocess call is represented simply with a slice of strings:

pacaptr/src/pm/scoop.rs

Line 180 in 2804f72

Cmd::new(&["powershell", "scoop", "update"])

Interestingly, the first time I tried to add support for scoop I did begin the call with scoop but it didn't work:

pacaptr/src/package_manager/scoop.rs

Line 154 in 2e2b797

Cmd::new(&["scoop", "update"]).kws(kws).flags(flags),

Please also notice that our CI tests are working alright, and I did make sure that pacaptr works on my Windows 10 VM during my initial development period, and that's why I'm very curious about your actual situation:

pacaptr/.github/workflows/test.yml

Lines 32 to 60 in 2804f72

	scoop-test:
	runs-on: windows-latest
	steps:
	- uses: actions/checkout@v2
	- uses: actions-rs/toolchain@v1
	with:
	profile: minimal
	toolchain: stable
	override: true
	- uses: Swatinem/rust-cache@v1
	- name: Install scoop
	shell: pwsh
	run: |
	Set-ExecutionPolicy RemoteSigned -Scope CurrentUser -Force
	iwr -useb 'https://raw.githubusercontent.com/scoopinstaller/install/master/install.ps1' -outfile 'install.ps1'
	.\install.ps1 -RunAsAdmin
	(Resolve-Path ~\scoop\shims).Path >> $Env:GITHUB_PATH
	- name: Verity scoop installation
	run: |
	powershell scoop help
	Get-Command scoop
	- name: Build
	run: cargo build --verbose
	- name: Run unit tests
	run: cargo test tests --verbose
	- name: Run smoke tests
	run: cargo test scoop --verbose
	- name: Run heavy tests
	run: cargo test scoop --verbose -- --ignored

[rami3l]

@dragonmkww
Please indicate your Windows version, the powershell version (32/64 bit and version number, both the one in which you set the policy and the one pointed to by the command powershell), so that we can rule out the situation in which the powershell you ran and the powershell I launched weren't the same thing.

You can also do Get-ExecutionPolicy -List with and without powershell at the beginning to see the differences.

Thanks in advance :)

---

Possibly related:
https://stackoverflow.com/a/44247390 shows that launching powershell with extra args might be required.

[dragonmkww]

Ok, I'll try to experiment on that! My windows version is: Microsoft Windows 11 Home, Version 10.0.22000 Build 22000 My system type is: x64 My powershell version is: PowerShell v7.2.2 Do you think you could change the call to begin with scoop, just to try it out? Thank you, I really want to get this fixed because it looks so cool!

…

On Mon, Apr 18, 2022 at 6:02 PM Gen Li ***@***.***> wrote: @dragonmkww <https://github.com/dragonmkww> Also, please indicate your Windows version, the powershell version (32/64 bit and version number), so that we can rule out the situation in which the powershell you ran and the powershell I launched weren't the same thing. — Reply to this email directly, view it on GitHub <#357 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW37P6XT3QEJL2QOFYUQC5DVFXLXJANCNFSM5TULM35A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[rami3l]

@dragonmkww
Sorry for saying so, but since I cannot reproduce your environment easily (it works on my Windows 10 VM, I don't know what could be the difference, and I cannot get a Windows 11 environment easily), I refuse to fix this bug in the blind.

It will be nice however if you can fork this repository and clone it, see what will work for you, and make a Pull Request back.

Of course, I'll be continuing my investigation on my side, but don't expect it to happen very soon.

Have a nice day, and good luck with the fix :D

[rami3l]

@dragonmkww
BTW, could you please paste the output with the commands below?

• Get-ExecutionPolicy -List
• powershell Get-ExecutionPolicy -List
• powershell scoop update, containing the execution policy error

Thanks in advance.

[lynzrand]

Rough guess: since you're using PowerShell Core 7.x.x, its executable is named pwsh instead of powershell (which corresponds to the system-installed .NET Framework version).

I suggest @rami3l try using pwsh instead of powershell and see if it works.

[rami3l]

@dragonmkww
If @lynzrand got it right, I assume you'll get different outputs for

Get-ExecutionPolicy -List

and

powershell Get-ExecutionPolicy -List

. If that is the case, please make sure that you indeed ran

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

in powershell, and not in pwsh. After that, the issue should be resolved.

---

Many thanks to both of you! If this indeed closes this issue, I'll include an update in the README describing this pwsh thing.

[rami3l]

Closing as it's not a bug.

[dragonmkww]

Thanks!

…

On Tue, Apr 19, 2022 at 3:54 PM Gen Li ***@***.***> wrote: Closing as it's not a bug. — Reply to this email directly, view it on GitHub <#357 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW37P6WR2Z5TYE6J2YYP4GDVF4FO5ANCNFSM5TULM35A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[dragonmkww]

And, I am in powershell not pwsh

…

On Tue, Apr 19, 2022 at 3:42 PM Frostbite209 ***@***.***> wrote: Literally just take powershell out of the call and it should be fine, pwsh doesn't work either. My execution policy error is: pacman -Syu Running `powershell scoop update` scoop : File C:\Users\ctayl\scoop\shims\scoop.ps1 cannot be loaded. The file C:\Users\ctayl\scoop\shims\scoop.ps1 is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at https:/ go.microsoft.com/fwlink/?LinkID=135170. At line:1 char:1 + scoop update + ~~~~~ + CategoryInfo : SecurityError: (:) [], PSSecurityException + FullyQualifiedErrorId : UnauthorizedAccess Error Subprocess exited with code 1 I you take powershell out of the call it works fine! Scoop is an executable process, for example: powershell scoop update = Execution policy error. scoop update = Works perfectly! I promise you that if you remove powershell from the call, it would work fine. It doesn't matter the version or the .NET framework, it's just the fact that powershell scoop update is not the right command. The correct command is scoop update. Please just try removing powershell from the call! On Tue, Apr 19, 2022 at 3:51 AM Gen Li ***@***.***> wrote: > @dragonmkww <https://github.com/dragonmkww> > If @lynzrand <https://github.com/lynzrand> got it right, I assume you'll > get different outputs for Get-ExecutionPolicy -List and powershell > Get-ExecutionPolicy -List, and if that is the case, please ensure that > you indeed ran Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope > CurrentUser *in powershell and not pwsh*. > > — > Reply to this email directly, view it on GitHub > <#357 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AW37P6QCSBGCXO6BRCNI5DTVFZQWTANCNFSM5TULM35A> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >