ruby-rkerberos on debian could use an i386 package
ruby-rkerberos is required by foreman-proxy but can't be installed. This is because the apt repo only has an amd64 version. Looking at all the other packages, they're all architecture independent, but this one does have a compiled library in it so it needs to be built specifically for amd64 and i386.
Without this, the smart-proxy package can't be installed but the rest of foreman installs and runs on i386. It doesn't give very helpful errors either:
Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install foreman-proxy' returned 100: Reading package lists... /Stage[main]/Foreman_proxy::Install/Package[foreman-proxy]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install foreman-proxy' returned 100: The following packages have unmet dependencies: foreman-proxy : Depends: ruby-rkerberos (>= 0.1.1) but it is not installable Recommends: ruby-gssapi but it is not going to be installed Recommends: ruby-rubyipmi (>= 0.9.2) but it is not going to be installed E: Unable to correct problems, you have held broken packages.
Depending on your build environment, you could solve it in a few ways. One would be to do "Multi-Arch: same" in the control file (not sure if that's needed) then use an i386 vm to compile an i386 version. Another alternative is to use a chroot with the needed tools. Finally, you can install everything on your main build box and put together scripts which build it using something like this:
I looked into submitting a pull request based on this, but with the different choices and with not knowing your build system, I don't want to give you something that would be backwards.
Let me know if it's something that would be interesting.
#2 Updated by Dominic Cleal over 5 years ago
- Status changed from New to Closed
- Assignee set to Dominic Cleal
- % Done changed from 0 to 100
- Legacy Backlogs Release (now unused) set to 72
We're using pbuilder, but we weren't calling it again with the 32-bit chroot from our Jenkins job. I've fixed that, it should now work.
I'll rebuild rkerberos for our nightly repos and for 1.9.1.