Aren't these redundant?

[JoseHidalgo]

Hi guys. When updating stuff, I always get these packages, from both WinGet and Chocolatey. I guess they must be redundant, right?

Example 1:

Example 2:

What would be the solution? Just disabling the Chocolatey packages so they don't appear anymore?

Thanks for your advice.

[JoseHidalgo]

Hello? Somebody?... Guys, I'm asking a simple question here. Thank you.

[JoseHidalgo]

Martí Climent (@marticliment) sorry to bother you. Since nobody seems to be answering here, could you please answer this?
I find it odd that UniGetUI offers to DL identical packages from two different sources. Could you enlighten me on this?
Thank you.

[Gabriel Dufresne (GabrielDuf)]

JoseHidalgo,
Those are most likely the same applications being tracked by two different package managers (WinGet and Chocolatey), so seeing both entries is expected.

If you only use one source, you can disable or ignore the packages from the other source to avoid the duplicates. You can also use the Ignore updates feature if you don't want to see a specific package update anymore

[JoseHidalgo]

Thank you very much. The odd thing is that this only happens with .Net 8.0/10.0 and Visual C++.
For all other packages (and I have more than a hundred installed), there are never duplicates like these. And they are very common apps that arguably are present in both sources.
Why are these two different from all the others?

[Gabriel Dufresne (GabrielDuf)]

That's a good question. I'm not entirely sure why it only happens with those packages, but it does seem to be specific to .NET runtimes and the Visual C++ redistributables.

Since WinGet and Chocolatey both provide those packages, UnigetUI ends up showing updates from both sources.

For now, you can safely use Ignore updates on the entries you don't want to see. I'll also take a note of this and see if there's something we can improve on our side.