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

Packages installed using --x86 don't stay x86 when updated #636

Closed
blackwind opened this issue Feb 15, 2016 · 6 comments
Closed

Packages installed using --x86 don't stay x86 when updated #636

blackwind opened this issue Feb 15, 2016 · 6 comments

Comments

@blackwind
Copy link

When a package is installed using --x86, the next update will install the x64 version (unless, I assume, --x86 is specified again during the update). Certain packages have explicit x86 versions that can be installed (like python-x86_32), but for those that don't (like php), this means you can no longer use cup all, which is highly counterintuitive.

Either there needs to be a separate x86 package for all packages with x86 versions, or Chocolatey needs to remember when --x86 is specified. I would lean towards the latter.

@ferventcoder
Copy link
Member

Remember is already planned #358

@ferventcoder
Copy link
Member

This is coming for the next version of choco.

As a workaround for now you can still use cup all, if you pin those particular ones and upgrade them separately. With a pin, they won't be upgraded in the upgrade all (or at all until you remove the pin).

As an alternative, you can try install the beta and take advantage of the --except feature #293 (if the list is small enough).

@ferventcoder
Copy link
Member

I'm going to close this as a duplicate of #358 for now. Please subscribe to that one for updates.

@Arnavion
Copy link

#358 appears to be marked as fixed in 0.9.10, but as of 0.10.3 this issue doesn't seem to be fixed. I have notepadplusplus.install installed with --forceX86, and cup all is trying to install the x64 variant of the new version.

@ferventcoder
Copy link
Member

#797 is what the issue is

@ferventcoder
Copy link
Member

ferventcoder commented Nov 19, 2016

It was a dupe when I closed it, but we split #358 to two tickets, one to handle remembering the args and another to use them during upgrades

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

3 participants