"doesn't support current architecture" error occurs in local manifest #6420
|
Here is my custom manifest file, placed in {
"version": "1.0.0",
"description": "mytool is a utility to run commands with administrator privileges on Windows.",
"homepage": "",
"license": "Unknown",
"bin": "MyTool.exe",
"installer": {
"script": [
"Write-Host \"Installing mytool locally...\"",
"Copy-Item -Path 'C:\\Users\\me\\scoop\\buckets\\local\\Sources\\mytool\\*' -Destination \"$dir\" -Recurse -Force",
"Write-Host \"mytool and all related files have been copied to the Scoop-managed directory.\""
]
},
"uninstaller": {
"script": [
"Write-Host \"Uninstalling mytool locally...\"",
"Remove-Item \"$dir\\*\" -Recurse -Force",
"Write-Host \"mytool and all related files have been removed from the Scoop-managed directory.\""
]
}
}Then I ran: And received this error: This is very strange because I'm running Windows 11 x64, and At first, I suspected the issue was due to the missing "architecture": {
"64bit": {
"bin": "MyTool.exe",
"installer": {
"script": [
"Write-Host \"Installing mytool locally...\"",
"Copy-Item -Path 'C:\\Users\\me\\scoop\\buckets\\local\\Sources\\mytool\\*' -Destination \"$dir\" -Recurse -Force",
"Write-Host \"mytool and all related files have been copied to the Scoop-managed directory.\""
]
},
"uninstaller": {
"script": [
"Write-Host \"Uninstalling mytool locally...\"",
"Remove-Item \"$dir\\*\" -Recurse -Force",
"Write-Host \"mytool and all related files have been removed from the Scoop-managed directory.\""
]
}
}
}However, I still got the same error: I even tried explicitly specifying the architecture via: But again received the same result. Furthermore, according to the [Scoop manifest documentation](https://github.com/ScoopInstaller/Scoop/wiki/App-Manifests), the For all these reasons, I believe this might be a bug in Scoop itself. How to solve the problem? |
Replies: 1 comment
|
I used local zip as url and it works. |
I used local zip as url and it works.