Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Normal
-
Resolution: Done
-
Labels:None
-
Template:customfield_10700 true
Description
As can be seen in:
http://apt.puppetlabs.com/dists/wheezy/main/binary-armhf/Packages
facter is again depending on dmidecode on all architectures, instead of just x86 and ia64 where it actually makes sense. This is actually the same issue reocurring:
https://projects.puppetlabs.com/issues/19678
This makes puppet uninstallable on a raspberrypi. The solution is to do the dmidecode requirement conditional on architecture. This pull request was used to fix this but apparently only on facter 1.7, which isn't out yet?
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Explorer
FWIW I repackaged facter 1.7.5 as 'Architecture: all' and was able to install / run it on my arm-based systems. I had previously built a stubbed out dmidecode for this same bug on an earlier release of facter.
Appears to be collecting relevant info and not throwing any obvious errors.
jon yeargers
added a comment - FWIW I repackaged facter 1.7.5 as 'Architecture: all' and was able to install / run it on my arm-based systems. I had previously built a stubbed out dmidecode for this same bug on an earlier release of facter.
Appears to be collecting relevant info and not throwing any obvious errors. Apparently dpkg isn't able to do architecture specific dependencies in arch:all packages. Building it arch-all is a dead end if dmidecode is to remain a Depends and not a Recommends. So the solutions could be:
1. Making dmidecode a Recommends and building arch all could be a good solution. dmidecode will be installed in most systems where it is available, and yet work on arm as well
2. Failing that it may make sense to build i386 and amd64 packages depending on dmidecode and an arch-all package for everything else. Maybe there's a way to make that work in the repo.
3. Failing that then building for all arch's is needed.
I think making dmidecode a Recommends is the best option
Pedro Côrte-Real
added a comment - Apparently dpkg isn't able to do architecture specific dependencies in arch:all packages. Building it arch-all is a dead end if dmidecode is to remain a Depends and not a Recommends. So the solutions could be:
1. Making dmidecode a Recommends and building arch all could be a good solution. dmidecode will be installed in most systems where it is available, and yet work on arm as well
2. Failing that it may make sense to build i386 and amd64 packages depending on dmidecode and an arch-all package for everything else. Maybe there's a way to make that work in the repo.
3. Failing that then building for all arch's is needed.
I think making dmidecode a Recommends is the best option
Michael Stahnke
added a comment - PR filed https://github.com/puppetlabs/facter/pull/763 PR #763 was resolved by updating the commit title and merging https://github.com/puppetlabs/facter/pull/768.
Michael Smith
added a comment - PR #763 was resolved by updating the commit title and merging https://github.com/puppetlabs/facter/pull/768 . The fix has been merged to facter, so look for this to be released in facter 2.2.0.
Matthaus Owens
added a comment - The fix has been merged to facter, so look for this to be released in facter 2.2.0. 
Pedro Côrte-Real That isn't exactly correct, as is noted in http://www.debian.org/doc/debian-policy/ch-relationships.html, conditional dependencies like those in facter result in separate packages with different dependencies. The i386 and amd64 facter packages correctly depend on dmidecode, and if we were to build arm specific facter packages they would not have that dependency.
The Packages file you link shows facter with all architectures from the 1.6 series, which is where I would expect to see them. The pull you link was merged and released in the Facter 1.7 series, and those packages are no longer architecture all, so they aren't advertised in the armhf Packages list, as is expected.