GPT4All version inconsistency in winget upgrade on Windows about gpt4all HOT 8 CLOSED

I linked the two issues now. Let's see what the root cause and needed actions will be :)

from gpt4all.

Looking at it a bit more closely, I'd say it's simply the wrong approach.

The installer from this project is based on the Qt Installer Framework and configured to download the latest release files. So this is kind of making a mess when used as such in a separate package repository.

Technically, as long as the code which defines the installer logic doesn't change here, a new release in a separate package repository isn't necessary. Conversely, different releases there don't actually give you the exact release versions of GPT4All which are requested. The installer would still try to get the latest version of the release files.

from gpt4all.

Hm, can you tell me what the winget package source is anyway?

Maybe I'm missing something, but I don't think it's official and I don't know who maintains that. The official installers you can get from GitHub or the GPT4All website.

Edit:
Quick search led me to the following. I guess this is where the packages are defined? https://github.com/microsoft/winget-pkgs/pulls?q=is%3Apr+gpt4all

I don't immediately recognise any of the account names there, however.

from gpt4all.

The good (or bad) news is that I did not maintain any sources. I typically run winget to keep several apps updated - and was surprised that GPT4all was listed (as I installed it using the official installer from the website).

Find my sources that should be default sources only here:

What confuses me is:

• The current version is 2.8.0, which is also installed on my system (based on what the application tells me)
• Winget states: "currently installed version: 2.4.19" and "can be updated to 2.7.0"

from gpt4all.

If you click on the link I've posted above, it looks like the latest (but rejected) PR for winget is v2.7.1, so that'd explain why it isn't up-to-date there. And there were several different accounts in all the releases.

My impresssion is that it was previously done by a third party who lost interest at some point, not someone involved in the project here. I guess you might have more luck asking for clarification in one of the PRs there?

from gpt4all.

Thanks for your investigation and also for providing the link above. I will contact them and ask for clarification.

from gpt4all.

By the way, while I'm unfamiliar with how it works, looks like it directly depends on the GitHub release here. And I can see there's a difference between the latest accepted and rejected versions:

v2.7.0:
https://github.com/Trenly/winget-pkgs/blob/bb1a0304d399c24df95517450ba0a62abbe8658f/manifests/n/nomic/gpt4all/2.7.0/nomic.gpt4all.installer.yaml#L7-L8

InstallerSwitches:
  Silent: install --accept-licenses --confirm-command --am

v2.7.1:
https://github.com/headquarter8302/winget-pkgs/blob/656ed5f7abf48d079a831699081ea8ac74c1d168/manifests/n/nomic/gpt4all/2.7.1/nomic.gpt4all.installer.yaml#L9-L10

InstallerSwitches:
  Silent: --accept-licenses --confirm-command --am

Making a new release available there might just be a matter of making a working PR again.

from gpt4all.

Alright, I'm assuming there is nothing else to be done here for me and the conversation in the other issue done for now, too.

So for posteriority:

• To expand on/amend my previous comment: The installer which is released on GitHub already includes all files, i.e. it was built with the GPT4ALL_OFFLINE_INSTALLER flag and has been that way for quite some time[1][2]. I've checked, v2.5.0 should have had that already. So this is not a problem as long as another manager like WinGet uses the installer from GitHub releases and not the website (and unless changes are made to how that works).

• In the other issue it was mentioned that the probable cause is with the installer being able to self-update, but it doesn't update the version number as expected by WinGet. Full quote:

  My best guess is that the primary cause of this issue is that the QT Framework Installer (not from GitHub) has the ability to self-update within the app. I can't test currently since it's not possible to install an older version, but if this self-updater works the way many others do, then it doesn't change the version of the application written to Control Panel. If the version isn't updated in Control Panel, then WinGet has no way to know that the newer version is installed.

I have not tried to reproduce the issue, but I'd say for now, the take-away here would be to not mix different ways to update the application. Also, if this happens, uninstall and reinstall in one specific way, then stick to that.

from gpt4all.