Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Package Issue]: FireDaemon.OpenSSL #150085

Closed
2 tasks done
pjhavariotis opened this issue Apr 19, 2024 · 15 comments
Closed
2 tasks done

[Package Issue]: FireDaemon.OpenSSL #150085

pjhavariotis opened this issue Apr 19, 2024 · 15 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.
Milestone

Comments

@pjhavariotis
Copy link

Please confirm these before moving forward

  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

Different install technology.

Brief description of your issue

I'm trying to upgrade from 3.2.1 -> 3.3.0 and I'm getting the following error:
A newer version was found, but the install technology is different from the current version installed. Please uninstall the package and install the newer version.

Steps to reproduce

winget upgrade --id FireDaemon.OpenSSL

Actual behavior

PS C:\Users\p.chavariotis> winget upgrade --id FireDaemon.OpenSSL
A newer version was found, but the install technology is different from the current version installed. Please uninstall the package and install the newer version.

Expected behavior

Download and upgrade the package

Environment

Windows: Windows.Desktop v10.0.19045.4291
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10861.0

Screenshots and Logs

No response

@pjhavariotis pjhavariotis added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Apr 19, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label Apr 19, 2024
@vikingnope
Copy link
Contributor

Have you tried uninstalling 3.2.1 and installing version 3.3.0?

@pjhavariotis
Copy link
Author

Have you tried uninstalling 3.2.1 and installing version 3.3.0?

No

@vikingnope
Copy link
Contributor

Try that and see how it goes if possible

@pjhavariotis
Copy link
Author

The following 2 commands finished Successfully !

winget remove --id FireDaemon.OpenSSL
winget install --id FireDaemon.OpenSSL

@pjhavariotis
Copy link
Author

However, the upgrade function should work!

@vikingnope
Copy link
Contributor

It was probably some conflicting files from previous versions which caused the issue.

@stephengillie
Copy link
Collaborator

However, the upgrade function should work!

I believe that automating this currently manual process (finding and running the previous version uninstaller before running the current version installer) is planned, but might be lower priority than other work. This error isn't usually encountered when both the previous and current versions have manifests in the repo - the usual case is when performing upgrade for the first time. But here, it seems that the installer technology changed between versions.

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs-Triage This work item needs to be triaged by a member of the core team. label Apr 19, 2024
@pjhavariotis
Copy link
Author

This issue remains (from 3.3.0 -> 3.3.1)!
A newer version was found, but the install technology is different from the current version installed. Please uninstall the package and install the newer version.

@mdanish-kh
Copy link
Contributor

This is because the package is an MSI bundled inside of a EXE installer. If you run winget upgrade FireDaemon.OpenSSL --verbose-logs --open-logs and see the latest generated log file, you would be able to see the line at the end

2024-07-10 11:24:38.198 [CLI ] Installer [X64,exe,Machine,] not applicable: Installed package type 'msi' is not compatible with installer type exe

I think this'll get fixed if we add AppsAndFeatures > InstallerType: msi in its manifest to let WinGet know it's a nested MSI


In the meantime you can use winget upgrade FireDaemon.OpenSSL --force to ignore the installer type warning and continue with the upgrade

@pjhavariotis
Copy link
Author

Unfortunately, I'm getting the same error:
2024-07-11 13:53:34.040 [CLI ] Installer [X64,exe,Machine,] not applicable: Installed package type 'msi' is not compatible with installer type exe

@mdanish-kh
Copy link
Contributor

PR #162349 should hopefully fix the issue. You'll have to try again once that's merged and published. Did --force work for you though?

@pjhavariotis
Copy link
Author

No. The error I shared before is with the --force option.

@mdanish-kh
Copy link
Contributor

@pjhavariotis PR #162349 is now merged. Can you try again now?

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback This needs a response from the author. label Jul 11, 2024
@pjhavariotis
Copy link
Author

Issue resolved!

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention This work item needs to be reviewed by a member of the core team. and removed Needs-Author-Feedback This needs a response from the author. labels Jul 12, 2024
@mdanish-kh
Copy link
Contributor

Close with reason: Issue resolved;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants