search

microsoft / winget-cli

WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
https://learn.microsoft.com/windows/package-manager/
MIT License
23.4k stars 1.46k forks source link

Some package installed by winget are not marked by winget anymore #1704

Closed dnet890 closed 1 year ago

dnet890 commented 3 years ago

Brief description of your issue

I installed many packages via winget and then when I launched the winget list command I checked some packages source are not belong to winget anymore.

Steps to reproduce

the steps are simple:

  1. I installed some packages via winget install
  2. I typed winget list
  3. I checked some packages source with winget list command on the right side are not belonged to winget anymore.

Expected behavior

if Installed packages via winget. the source should be marked as a winget.

Actual behavior

multiples packages source are not belong to winget.

Environment

winget version v1.1.12653
denelon commented 3 years ago

Can you provide a couple of examples?

The output from list displays packages sources when an upgrade is available.

We have an enhancement on the backlog to improve this:

dnet890 commented 3 years ago

there are few packages like:

  1. winget install --id=Logitech.Options -e
  2. winget install --id=OBSProject.OBSStudio -e
  3. winget install --id=WinDirStat.WinDirStat -e
  4. winget install --id=BraveSoftware.BraveBrowser -e etc So, when I install these packages. I checked it on winget list especially source column. it is not part of winget anymore. Any thoughts about this?
denelon commented 3 years ago

I think it's an unclear UX related to the output from winget list. The "Available" and "Source" columns get populated when an upgrade is detected as available. We've recently added some additional logic to record which packages have been installed, but the display from "list" doesn't show when a package is available in a source if no available upgrade is detected.

keentext commented 3 years ago

yep, and windows 11 is shipping with a broken product by default.

the more time passes, the worst windows and microsoft software becomes.

vedantmgoyal9 commented 3 years ago

@keentext kindly learn to respect one's work.

keentext commented 3 years ago

@keentext kindly learn to respect one's work.

we wouldn't need respect if we had a great product

Trenly commented 3 years ago

https://github.com/microsoft/winget-cli/blob/73d35a20097f1c1efc243c2aa87ba377f65eaf2e/CODE_OF_CONDUCT.md

vedantmgoyal9 commented 3 years ago

More specifically: https://opensource.microsoft.com/codeofconduct/#:~:text=Trolling%2C%20insulting%20or%20derogatory%20comments%2C%20and%20personal%20or%20political%20attacks

Masamune3210 commented 3 years ago

Just stop feeding them, all it does it make it worse unfortunately. You can't reason with someone determined to not listen

ItzLevvie commented 3 years ago

Not to mention that these are all sock puppet accounts created several days ago or several weeks ago:

All of these accounts have similar biography and posts comments in the same thread as other accounts, so it's not worth engaging with them.

denelon commented 1 year ago

I'm closing this issue in favor of: