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
Ubuntu Xenial: Repository does not support architecture i386 #1416
Comments
need to evaluate whether to support i386, put off to 2.13 |
@torkelsson Do you mean you'd like to install xCAT on an i386 server? |
@zet809 No, I'm installing xCAT on an amd64 server, which is multiarch enabled, i.e it looks for i386 packages too when running apt-get update. However as the repository does not provide the i386 archive (not even an empty one) I get the message from the initial report. Please, either provide a i386 archive (perhaps empty) or add to the documentation, how to set up apt-sources to only look for amd64 packages. See https://wiki.debian.org/Multiarch/HOWTO#Setting_up_apt_sources |
@torkelsson Thank you for point out this issue, we will modify our documentation like below: |
@zet809 Is this target to be changed on the xcat.org download page? or other places in our documentation? https://github.com/xcat2/xcat.org/blob/master/download.html |
@whowutwut I think both of them needed to be updated. I tried to modify the readthedoc within pull request #1705.
|
Created pull request: xcat2/xcat.org#25 Can you please double check the changes? |
@torkelsson We have updated the document, I think we can close the defect, right? |
I'm trying to install xcat on Ubuntu Xenial, however when following the documentation and adding:
deb http://xcat.org/files/xcat/repos/apt/devel/core-snap trusty main
to sources.list (or sources.list.d/xcat.list) I get the following message:
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://xcat.org/files/xcat/repos/apt/2.12/core-snap xenial InRelease' doesn't support architecture 'i386'
Can you please make the archive multi arch? And/or update the documentation?
The text was updated successfully, but these errors were encountered: