-
Notifications
You must be signed in to change notification settings - Fork 384
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
(cygwin) mbox Target CPU mismatch: You're trying to install a 32 bit version of Cygwin into a directory containing a 64 bit version of Cygwin. #757
Comments
That certainly is odd, it should pick the correct architecture as long as you're running choco v 0.10.4+ (and since the package have a dependency on choco v 0.10.5 you should, unless you are installing with the argument @ferventcoder any idea on this one? |
@tek0011 What version of Puppet are you running? It should do the right thing, but for some reason it could be picking up the right architecture regardless. Unless there is something in the cygwin packaging or its installer that is messed up. |
I should have said, are you running a 64x version of Puppet as well? |
You may also want to ensure that you are not having choco.exe get virtualized (where it is ignoring the app.manifest file) - the best way to ensure this is to run |
Puppet (old) 3.7.3 - Open Source ill take a look at that issue. I am away from the machine for the weekend.. |
More logs from the user:
|
still looking into that other ticket. will update when can. |
The easy thing to do is touch choco.exe (after ensuring there is a choco.exe.manifest next to it) - the choco is |
touching choco.exe did not work. I did finally get all the logs though:
|
dang, git should include a [spoiler] tag for things like that. sorry for massive wall of logs. |
I uninstalled cygwin and cyg-get, re-ran and it worked fine. Thanks. |
Here is the problem it seems.
Followed by:
It looks like there is something you're trying to install that needs to downgrade chocolatey, or maybe the artifactory source you're using have the chocolatey software (but only up to version 0.10.3)? Not entirely sure how that works. This gives a conflict with cygwin, as the package requires a minimum of chocolatey 0.10.5. So when something tries to downgrade it, everything pretty much fails. |
Thanks @AdmiringWorm - You are correct. We downgrade all servers to choco 10.3 (for now). Looks like cygwin had an update, and I bet that update doesnt work with 10.3 Thanks for the explanation. |
@tek0011 yep, you're correct. The latest version of the cygwin package do not work with 0.10.3. |
BTW, this is probably why your original issue occurred as well. |
I agree. I think that is exactly why the original issue occurred. Thanks @AdmiringWorm - glad we got it figured out and it wasnt an underlying choco issue. |
Installing latest version. Some reason it picks up this as a 32bit OS, when it is actually a x64 2016 Server.
Did not have this issue on builds before June 7th release. Any ideas?
The text was updated successfully, but these errors were encountered: