Chocolatey version is not matching? Is it normal?

[ekozcifci]

As you see, versions are not same with chocolatey, is it a bug? i am newbie so im just confused.

[marticliment]

Chocolatey may sometimes take a while to update its package indexes, is the update recent?

[ekozcifci]

No, it is not. It is updated on 12 December. Also same bug happens on almost every package i searched on. Not package spesific issue.
FYI, i just miss-created this topic, i created same on on issue section too, sorry.

[marticliment]

I will investigate

[albino1]

I've just installed UniGetUI for the first time, and I'm also seeing this problem. Sometimes the chocolatey version shown in the GUI is an old version of the program, and not the current one. Here's an example using the program SABnzbd, which should be defaulting to 4.4.1 but for some reason UniGetUI shows 4.3.3 by default:

Searching for "sabnzbd" in Discover Packages

Verifying that it's set to Latest and that 4.4.1 is available in the options

Here's me checking on the command line with chocolatey and you can see that it automatically selects 4.4.1 and not 4.3.3 as the latest stable release:

> choco install sabnzbd
Chocolatey v2.4.2
Installing the following packages:
sabnzbd
By installing, you accept licenses for the packages.
Downloading package from source 'https://chocolatey.org/api/v2/'
Progress: Downloading SABnzbd 4.4.1... 100%

sabnzbd v4.4.1 [Approved]

Chocolatey URL for sabnzbd when searching the chocolatey website:

https://community.chocolatey.org/packages?q=sabnzbd

https://community.chocolatey.org/packages/SABnzbd/4.4.1

Checking the Version History we can see that 4.4.1 was added on December 20th so it shouldn't be affected by the package indexing.

This is using UniGetUI 3.1.6 installed from Github and not from the Microsoft Store. In case it's relevant, I already had chocolatey installed before installing UniGetUI.

[marticliment]

This issue will be fixed in next version

[albino1]

@marticliment I saw in the release notes what looked like a fix, but I just checked and it's still showing the wrong version for my previous example:

Just a heads up in case you thought it was solved.

[marticliment]

I have fixed something, because I was not able to reproduce the issue anymore. Nevertheless, I will look into the issue again