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

(cmake) (cmake.install) Package fails to install: Exit code was '1603' #2591

Open
2 tasks done
LordOfDragons opened this issue Dec 8, 2024 · 6 comments
Open
2 tasks done

Comments

@LordOfDragons
Copy link

LordOfDragons commented Dec 8, 2024

Checklist

  • I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.
  • I have verified that this is happening in the latest available version of the package.

Chocolatey Version

2.4.0

Chocolatey License

None

Package Version

cmake.install 3.31.2

Current Behaviour

The install fails with this error message (logs unavailable since this happens on Github workflow):

cmake.install v3.31.2 [Approved]
cmake.install package files install completed. Performing other installation steps.
Installing 64-bit cmake.install...
WARNING: Generic MSI Error. This is a local environment error, not an issue with a package or the MSI itself - it could mean a pending reboot is necessary prior to install or something else (like the same version is already installed). Please see MSI log if available. If not, try again adding '--install-arguments="'/l*v c:\cmake.install_msi_install.log'"'. Then search the MSI Log for "Return Value 3" and look above that for the error.
ERROR: Running ["C:\Windows\System32\msiexec.exe" /i "C:\ProgramData\chocolatey\lib\cmake.install\tools\cmake-3.31.2-windows-x86_64.msi" /qn /norestart /l*v "C:\Users\runneradmin\AppData\Local\Temp\chocolatey\cmake.install.3.31.2.MsiInstall.log"] was not successful. Exit code was '1603'. Exit code indicates the following: Generic MSI Error. This is a local environment error, not an issue with a package or the MSI itself - it could mean a pending reboot is necessary prior to install or something else (like the same version is already installed). Please see MSI log if available. If not, try again adding '--install-arguments="'/l*v c:\cmake.install_msi_install.log'"'. Then search the MSI Log for "Return Value 3" and look above that for the error..
The install of cmake.install was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\cmake.install\tools\chocolateyInstall.ps1'.
 See log for details.
Failed to install cmake because a previous dependency failed.
Downloading package from source 'https://community.chocolatey.org/api/v2/'

NOTE: Chcolatey tries to install "cmake.install 3.31.2" which causes the failure. The install command is "choco install cmake ninja 7zip".

Expected Behaviour

Installation works. Last known working date is 5.12.2024 . Since then it's broken.

NOTE: Before Chocolatey correctly tried to install "cmake 3.31.1".

Steps To Reproduce

  1. Run command "choco install cmake ninja 7zip"
  2. Chocolatey tries to install "cmake.install 3.31.2" instead of "cmake 3.31.1" which fails.

Environment

- Operating System: Microsoft Windows Server 2022 [10.0.20348] (Github workflow builder)
- PowerShell Version: Unknown (no access to workflow builders)
- Shell: Unknown (no access to workflow builders)

Chocolatey Log

Log file is unavailable (Github workflow builder). Available is only the error message posted above.

Anything else?

Example build failure caused by this bug here: https://github.com/LordOfDragons/dragengine/actions/runs/12218416239/job/34083889618 .

Last working build is here: https://github.com/LordOfDragons/dragengine/actions/runs/12201105644/job/34038771603

Github workflow builder did not change (same operating system and same configuration). But for some reason Chocolatey does now try since two days to install "cmake.install 3.31.2" instead of "cmake 3.31.1" which causes the failure. The install command is "choco install cmake ninja 7zip".

Copy link

github-actions bot commented Dec 8, 2024

Thanks for raising this issue!

The packages within this repository are maintained by a small team of volunteer Community Maintainers, in their own time. Their time, like yours is important. Please help them by not wasting it.

This is a community repository where the expectation is that everybody will get involved by raising pull requests to fix problems they find. This will also allow that problem to be fixed more quickly as you don't have to wait for a member of the Community Maintainer Team to pick it up.

If you are unable to fix the issue yourself, the Community Maintainers Team will look at it when time allows. There are no service level agreements, nor should there be any expectation on when people can resolve issues in their own time.

A few dos and don'ts:

  • Do provide as much information as you can in any issue that you raise.
  • Don't complain that an issue has not yet been picked up or resolved. You are expected to help out in this community maintained repository. If you are unable to do so, don't complain when others don't adhere to your timelines. There is no SLA nor should you have any expectation of one.
  • Do read the CONTRIBUTING and COMMITTERS documentation before raising a pull request as it contains valuable information on what automation is used in this repository.
  • Do read the Code of Conduct.
  • Don't post your frustration in comments. The Community Maintainers Team are not a punching bag for your frustration. You will only end up banned from the repository.

Thank you.
(Automatically posted message)

@pauby
Copy link
Member

pauby commented Dec 8, 2024

The error message indicates this is a local environment issue for the installer, and not a package issue.

Chocolatey CLI will always install the latest version available to it, unless you tell it otherwise with the --version option. The latest version ofcmake.install is 3.31.2.

@LordOfDragons
Copy link
Author

LordOfDragons commented Dec 8, 2024

But why does it change package? Before it installed "cmake". Now it tries to install "cmake.install". The "cmake" one is smaller while the "cmake.install" seems to be a huge package. Why install a different package than requested? It looks as if this change causes all the problems.

@pauby
Copy link
Member

pauby commented Dec 8, 2024

But why does it change package?

It didn't change package. cmake installed cmake.install for the previous version too.

Before it installed "cmake"

It still does.

Now it tries to install "cmake.install"

It always did.

Why install a different package than requested?

It didn't. You asked it to install cmake. cmake.install is a dependency of the cmake package. This has always been the case. Dependencies are a fundamental of package management. If you are going to use them, I would suggest you understand that part. That is said with respect and not sarcasm as it may come across in text.

It looks as if this change causes all the problems.

There has not been a "change". The previous version was the same.

Going back to what I said earlier, the error message indicates this is a local environment issue for the installer, and not a package issue.

Have you tried to install cmake outside of the pipeline? It works:

image

@LordOfDragons
Copy link
Author

LordOfDragons commented Dec 8, 2024

I disagree with "There has not been a "change".". Obviously there has been a change. According to version history of the cmake package (both the "cmake" and "cmake.install" one) there has been a version upgrade 2 days ago. Since then the build fails. So no, there has been a change and it directly caused the breaking. The question is now "why" did it break the build. The only thing I could notice is that a different package is installed. The run log of the working build shows "cmake" being installed and the download is rather small. The run log of the broken build shows "cmake.install" being installed and the download is very large (takes very long to download). So something is inherently different but I don't know the chocolatey system to figure out what causes all these problems.

To make it a bit clearer this is what I see in the working build before the upgrade:

Downloading package from source 'https://community.chocolatey.org/api/v2/'

Progress: Downloading cmake 3.31.1... 17%
Progress: Downloading cmake 3.31.1... 51%
Progress: Downloading cmake 3.31.1... 86%
Progress: Downloading cmake 3.31.1... 100%

cmake v3.31.1 [Approved]

4 lines and the download is done. This means a small package size.

Now the broken build run:

Downloading package from source 'https://community.chocolatey.org/api/v2/'

Progress: Downloading cmake.install 3.31.2... %
Progress: Downloading cmake.install 3.31.2... %
Progress: Downloading cmake.install 3.31.2... % (line number 12)
...
Progress: Downloading cmake.install 3.31.2... 100% (line number 7582)
Progress: Downloading cmake.install 3.31.2... 100%
Progress: Downloading cmake.install 3.31.2... 100%

cmake.install v3.31.2 [Approved]

Over 7500 lines instead of 4. That means the package is huge.

Personally I would conclude from this that something is wrong with the package. It's massively larger than the previous one and fails. Maybe somebody can compare the two revisions and check what went wrong there?

@pauby
Copy link
Member

pauby commented Dec 8, 2024

We're going around in circles.

I disagree with "There has not been a "change".

There has been no change to the package. The software has obviously changed.

Obviously there has been a change.

As I have said, the package has not changed. But if it is obvious, please let me know what the change is.

To make it a bit clearer this is what I see in the working build before the upgrade:

cmake v3.31.1 [Approved]

Now the broken build run:

cmake.install v3.31.2 [Approved]

They are not the same package. cmake.install package for version 3.31.1 is 58.7MB (I just downloaded it) and for version 3.31.2 it is 58.7MB (I just downloaded that too).

Personally I would conclude from this that something is wrong with the package.

Again, respectfully, you've already said you "don't know the chocolatey system". I have also installed the package and provided a screenshot as proof that it works

As I mentioned previously, the error message indicates this is a local environment issue for the installer, and not a package issue:

WARNING: Generic MSI Error. This is a local environment error, not an issue with a package or the MSI itself - it could mean a pending reboot is necessary prior to install or something else (like the same version is already installed). Please see MSI log if available. If not, try again adding '--install-arguments="'/l*v c:\cmake.install_msi_install.log'"'. Then search the MSI Log for "Return Value 3" and look above that for the error.

I want to highlight a section from that error message: This is a local environment error, not an issue with a package or the MSI itself. Have a look at what the MSI 1603 error is

To prove the package is fine, I just installed it:

image

I have:

  • Provided screenshot confirmation that the cmake package and its dependencies work for both 3.31.1 and 3.31.2.
  • Highlighted that the error you have clearly states it is not a package issue, but a local environment one.
  • I have given you the sizes of the packages that are part of the cmake dependency chain.

I appreciate you are unhappy with what I've told you, but there is nothing more I can do.

Before responding again, please:

@pauby pauby changed the title (cmake 3.31.1 -> cmake.install 3.31.2) fails to install: Exit code was '1603' (cmake) (cmake.install) Package fails to install: Exit code was '1603' Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants