-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Comments
Have you tried uninstalling 3.2.1 and installing version 3.3.0? |
No |
Try that and see how it goes if possible |
The following 2 commands finished Successfully !
|
However, the |
It was probably some conflicting files from previous versions which caused the issue. |
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 |
This issue remains (from 3.3.0 -> 3.3.1)! |
This is because the package is an
I think this'll get fixed if we add In the meantime you can use |
Unfortunately, I'm getting the same error: |
PR #162349 should hopefully fix the issue. You'll have to try again once that's merged and published. Did |
No. The error I shared before is with the |
@pjhavariotis PR #162349 is now merged. Can you try again now? |
Issue resolved! |
Close with reason: Issue resolved; |
Please confirm these before moving forward
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
Expected behavior
Download and upgrade the package
Environment
Screenshots and Logs
No response
The text was updated successfully, but these errors were encountered: