microsoft / microsoft/winget-pkgs
[Package Issue]: JohnMacFarlane.pandoc
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Please confirm these before moving forward
- I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue
Other
Brief description of your issue
Kinda related to https://github.com/microsoft/winget-pkgs/issues/118528? The user-scope installer works fine, but when trying to upgrade the package, the upgrade only shows as available for the system scope, not the user scope.
Steps to reproduce
- Install an older version of pandoc
winget source updatewinget list --scope user --upgrade-availablewinget upgrade --scope user JohnMacFarlane.pandoc
Actual behavior
The application doesnt show up as upgradable in the user-scope upgradable list, and can't be upgraded as a user.
winget.exe upgrade --scope user JohnMacFarlane.pandoc
<#
No installed package found matching input criteria.
#>
Expected behavior
The package should have the update installed
Environment
Windows Package Manager v1.8.1911
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.22631.4169
System Architecture: x64
Package: Microsoft.DesktopAppInstaller v1.23.1911.0
Screenshots and Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported commands for JohnMacFarlane.pandoc, especially winget list --scope user --upgrade-available and winget upgrade --scope user JohnMacFarlane.pandoc. Compare how the package is represented for user and system scopes; done when the user-scoped update appears and installs successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100