So am I SOL on this? Is ARM considered an 'unsupported architecture' until I can create a 'dmidecode' for this platform?
On Wednesday, December 11, 2013 10:55:11 AM UTC-8, Jon Yeargers wrote: > > I can wget and install facter but the issues continue: > > root@plugpc-005:/tmp# apt-get install puppet > Reading package lists... Done > Building dependency tree > Reading state information... Done > You might want to run 'apt-get -f install' to correct these: > The following packages have unmet dependencies: > facter : Depends: dmidecode but it is not installable > puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but it is not > going to be installed > E: Unmet dependencies. Try 'apt-get -f install' with no packages (or > specify a solution). > > > root@plugpc-005:/tmp# apt-get install puppet-common > Reading package lists... Done > Building dependency tree > Reading state information... Done > You might want to run 'apt-get -f install' to correct these: > The following packages have unmet dependencies: > facter : Depends: dmidecode but it is not installable > puppet-common : Depends: ruby-shadow but it is not installable or > libshadow-ruby1.8 but it is not going to be > installed > Depends: libaugeas-ruby but it is not going to be > installed or > libaugeas-ruby1.9.1 but it is not going to be > installed or > libaugeas-ruby1.8 but it is not going to be > installed > Depends: hiera (>= 1.0.0) but it is not going to be > installed > Depends: ruby-rgen (>= 0.6.5) but it is not going to be > installed > Recommends: lsb-release but it is not going to be > installed > Recommends: debconf-utils but it is not going to be > installed > E: Unmet dependencies. Try 'apt-get -f install' with no packages (or > specify a solution). > > > Attempts to install any of these packages gives me similar errors. > > On Wednesday, December 11, 2013 9:50:07 AM UTC-8, Jeff Bachtel wrote: >> >> You can fetch it directly (wget, curl, whatever) from >> >> >> http://apt.puppetlabs.com/pool/squeeze/main/f/facter/facter_1.6.18-1puppetlabs1_all.deb >> >> Jeff >> >> On 12/11/2013 12:39 PM, Jon Yeargers wrote: >> >> root@plugpc-005:~# apt-get install ruby libopenssl-ruby pciutils >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> Note, selecting 'libruby' instead of 'libopenssl-ruby' >> pciutils is already the newest version. >> libruby is already the newest version. >> ruby is already the newest version. >> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >> >> There isn't a 'download' option for apt-get on this system so I tried >> '--download-only': >> >> root@plugpc-005:~# apt-get --download-only install facter >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> Some packages could not be installed. This may mean that you have >> requested an impossible situation or if you are using the unstable >> distribution that some required packages have not yet been created >> or been moved out of Incoming. >> The following information may help to resolve the situation: >> >> The following packages have unmet dependencies: >> facter : Depends: dmidecode but it is not installable >> E: Broken packages >> >> I added '--ignore-missing' but the result was the same. >> >> On Wednesday, December 11, 2013 7:47:02 AM UTC-8, Jeff Bachtel wrote: >>> >>> demidecode (which is a hard dependency for facter) is not available for >>> armel in Debian's repository. I have confirmed that facter will not fail >>> outright when dmidecode is missing. >>> >>> The following facter variables will not be created, however: >>> bios_release_date >>> bios_vendor >>> bios_version >>> boardmanufacturer >>> boardproductname >>> boardserialnumber >>> manufacturer >>> productname >>> serialnumber >>> type >>> uuid >>> >>> If that's acceptable for you, you can try >>> >>> apt-get install ruby libopenssl-ruby pciutils >>> apt-get download facter >>> dpkg -i --force-depends facter*.deb >>> apt-get install puppet >>> >>> This will manually install the other facter dependencies (which should >>> exist for armel), download the facter .deb file, then do an install of it >>> without checking depends. The puppet install should succeed after that. >>> >>> I think facter's dmidecode dependency should be a Suggests vice a >>> Depends, and it might be worth filing a bugrep to get it changed. >>> >>> Jeff >>> >>> >>> On 12/11/2013 10:31 AM, Jon Yeargers wrote: >>> >>> I also tried 'apt-get dist-upgrade'. This brought down 'hiera' (along >>> with a few other things). >>> >>> Then tried 'apt-get install puppet-common' - this failed as 'facter' >>> needed a higher version. >>> >>> .. so tried 'facter' but this failed with: >>> >>> facter : Depends : dmidecode but it is not installable >>> >>> >>> >>> If I do 'apt-cache search dmidecode' it isn't available. >>> >>> On Wednesday, December 11, 2013 7:26:02 AM UTC-8, Jon Yeargers wrote: >>>> >>>> 'apt-get update' ran fine this time. >>>> >>>> 'apt-get install puppet': >>>> >>>> Some packages could not be installed. This may mean that you have >>>> requested an impossible situation or if you are using the unstable >>>> distribution that some required packages have not yet been created >>>> or been moved out of Incoming. >>>> The following information may help to resolve the situation: >>>> >>>> The following packages have unmet dependencies: >>>> puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but >>>> 2.6.2-5+squeeze8 is to be installed >>>> E: Broken packages >>>> >>>> >>>> I also tried uninstalling puppet and then doing the install. Same >>>> result. >>>> >>>> >>>> >>>> On Tuesday, December 10, 2013 3:11:27 PM UTC-8, Moses Mendoza wrote: >>>>> >>>>> Hi all, apt.puppetlabs.com has been updated with additional >>>>> architectures so the 'all' packages should install. Can you check if >>>>> you still have the same issues? >>>>> >>>>> On Tue, Dec 10, 2013 at 12:01 PM, Moses Mendoza <[email protected]> >>>>> wrote: >>>>> > On Tue, Dec 10, 2013 at 10:52 AM, Jon Yeargers <[email protected]> >>>>> wrote: >>>>> >> I updated the repository file using the official puppet-recommended >>>>> version. >>>>> >> The corrected line is: >>>>> >> >>>>> >> deb http://apt.puppetlabs.com squeeze main (i mistakenly entered >>>>> 'wheezy' >>>>> >> above). >>>>> >> >>>>> >> When I do 'apt-get update' I'm told: >>>>> >> >>>>> >> W: Filed to fetch >>>>> >> http://apt.puppetlabs.com/dists/squeeze/ReleaseUnable to >>>>> >> find expected entry main/binary-armel/Packages in Meta-index file >>>>> (malformed >>>>> >> Release file?) >>>>> >> >>>>> >> >>>>> >> On Tuesday, December 10, 2013 9:11:44 AM UTC-8, Felix.Frank wrote: >>>>> >>> >>>>> >>> That's not the issue at all I think. >>>>> >>> >>>>> >>> Is that source.list entry from a howto? >>>>> >>> >>>>> >>> Have you tried the instructions here: >>>>> >>> >>>>> >>> >>>>> http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu >>>>> >>>>> >>> >>>>> >>> Because what apt is making of your configuration is plain wrong. >>>>> >>> >>>>> >>> On 12/10/2013 05:50 PM, Jon Yeargers wrote: >>>>> >>> > If I create a '/etc/apt/sources.list.d/puppet.list' with: >>>>> >>> > >>>>> >>> > deb http://apt.puppetlabs.com/pool wheezy stable >>>>> >>> > >>>>> >>> > I get: >>>>> >>> > >>>>> >>> > Failed to fetch >>>>> >>> > >>>>> >>> > >>>>> http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz >>>>> >>>>> >>> > 404 Not Found >>>>> >>> > >>>>> >>> > I'm thinking that I might need to set this up on an x86 machine >>>>> and then >>>>> >>> > rebuild the package file myself in a private repository. >>>>> > >>>>> > My apologies - this is a problem with our apt repository >>>>> configuration >>>>> > - we did not set it up to include architectures other than i386 and >>>>> > amd64. We will be remedying this soon, so that while we may not yet >>>>> > have arm-specific packages, at least our all-arch packages will >>>>> work. >>>>> > >>>>> >> >>>>> >> -- >>>>> >> You received this message because you are subscribed to the Google >>>>> Groups >>>>> >> "Puppet Users" group. >>>>> >> To unsubscribe from this group and stop receiving emails from it, >>>>> send an >>>>> >> email to [email protected]. >>>>> >> To view this discussion on the web visit >>>>> >> >>>>> https://groups.google.com/d/msgid/puppet-users/0e4f7484-682f-44c9-b370-5a977d4085ee%40googlegroups.com. >>>>> >>>>> >>>>> >> >>>>> >> For more options, visit https://groups.google.com/groups/opt_out. >>>>> > >>>>> > >>>>> > >>>>> > -- >>>>> > Moses Mendoza >>>>> > Puppet Labs >>>>> > >>>>> > Join us at PuppetConf 2014, September 23-24 in San Francisco >>>>> >>>>> >>>>> >>>>> -- >>>>> Moses Mendoza >>>>> Puppet Labs >>>>> >>>>> Join us at PuppetConf 2014, September 23-24 in San Francisco >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/puppet-users/96382244-64e6-458e-a33a-81f24a4befbf%40googlegroups.com >>> . >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/bcfc669e-ff80-4c81-933b-fbdf5b1bc440%40googlegroups.com >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ddb21baa-0971-4b5a-b1cd-ba35cae60bc5%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
