Skip to content

Different Chocolatey sources depending on task (Discover vs Update) #3036

@marticliment

Description

Discussed in #3034

Originally posted by Infinitay November 30, 2024
Before I continue, here is my current Package Manager settings for Chocolatey:

image

I'm not sure if this is particularly an issue or not so I'm opening up a discussion post for more information. I noticed just now that depending on what action I'm trying to do within WinGetUI, the chocolatey source changes. For example, when I go to Software Updates I only see Chocolatey: community packages. I should note that I haven't used WinGetUI to install any new chocolatey packages as I rely either on chocolatey CLI or chocolatey GUI for that. However, whenever I go to Discover Packages it lists packages only with the Chocolatey: chocolatey source.

For me, this is causing a minor issue to because the packages listed from Chocolatey: chocolatey seem to be outdated compared to packages found within Chocolatey: community - despite having the same package id/maintainer(?).

Discover Packages

image

Software Updates

image

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions