Uploaded image for project: 'Community Package Repository (Archived, moved to puppet.atlassian.net)'
  1. Community Package Repository (Archived, moved to puppet.atlassian.net)
  2. CPR-18

facter packages depend on dmidecode but it is unavailable on arm architecture

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Duplicate
    • None
    • 2017/08/02
    • None
    • None
    • Debian Wheezy 7.0 on Raspberry PI.

      uname -a -> Linux goldberry 3.6.11+ #408 PREEMPT Wed Apr 10 20:33:39 BST 2013 armv6l GNU/Linux

    Description

      facter debian packages from http://apt.puppetlabs.com/ cannot be installed on ARM architecture due to dependency on the dmidecode package.

      The dmidecode debian package is not available on the ARM architecture. In fact it is stated in the dmidecode home page that dmidecode is only available on i386, x86-64 and ia64 architectures.

      dmidecode dependency has been introduced with facter 1.6.4.

      Package: facter
      Version: 1.6.4-1puppetlabs1
      Architecture: all
      Maintainer: Puppet Labs <info@puppetlabs.com>
      Installed-Size: 416
      Depends: ruby1.8, libopenssl-ruby1.8, dmidecode
      Section: ruby
      

      facter packages from Debian repositories solve this by moving this to a Recommends dependency:

      Package: facter
      Version: 1.6.10-1
      Installed-Size: 214
      Maintainer: Puppet Package Maintainers <pkg-puppet-devel@lists.alioth.debian.org>
      Architecture: all
      Depends: ruby | ruby-interpreter, ruby-json, net-tools, bind9-host | host
      Recommends: pciutils, dmidecode
      

      By the way, why is there no facter 1.7.x on ARM architecture?

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              cbliard Christophe Bliard
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support