-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
32-bit vs 64-bit RPMs in different repos #11822
Comments
Thanks for the report. I know there was recently some changes with the way we handle arch suffixes on packages. @terminalmage can you look at this? |
@knine What are the values of the |
@knine Also, please run |
64 / 32 - bit respectively: osarch: x86_64 cpuarch: x86_64 |
64-bit:
|
32-bit:
|
Hmm, I guess the architecture isn't included in the |
Also, I've edited the output you posted so that it is enclosed in triple-backticks, which here on GitHub formats the output in fixed width. This helps make it easier to read. |
Thanks for the tip with the triple-backticks. Good to know. |
64-bit:
32-bit:
I wonder if there is a confusion between the i686 (cpuarch / osarch) vs i386 (rpms) |
Ahh, I found the issue. I'll have a fix for this by tomorrow. |
I have noticed a possible issue with installing the same yum package for 64
and 32 bit architectures. This came about when I went from the 0.17 line to 2014.1.1-1 on CentOS 6.5 using the EPEL RPMs.
I roll some custom RPMs for some file integrity software we run. I compile
them such that a specific central logging server (we have several) is built in
to the RPM. For example I call the RPM used on our office servers "samhain-
office". These are the two files I produce, each built on a VM for the specific
OS and arch:
Each server is pointed to the appropriate custom RPM repo (64 or 32 bit) where the files lives.
Then I use salt to install them:
This worked great before 2014.1. Now if I run a highstate on the 64-bit
CentOS 6.5 box, it works as before. But if I do it on the 32-bit CentOS 6.5
server:
Thanks.
The text was updated successfully, but these errors were encountered: