Disregard, my bad.

This was a server that didn't have the Ubuntu universe repo enabled, which 
is why it could find the virt-what (facter) or libjson-ruby and ruby-json 
(hiera) packages.

On Friday, June 14, 2013 10:35:10 PM UTC-4, Justin wrote:
>
> Forgot to paste my apt-get update output (which I ran immediately after 
> installing the repo).
>
> ~# apt-get update 
> Hit http://apt.puppetlabs.com quantal Release.gpg
> Hit http://us.archive.ubuntu.com quantal Release.gpg
> Hit http://apt.puppetlabs.com quantal Release
> Hit http://us.archive.ubuntu.com quantal-security Release.gpg
> Hit http://apt.puppetlabs.com quantal/main Sources
> Hit http://us.archive.ubuntu.com quantal-updates Release.gpg
> Hit http://apt.puppetlabs.com quantal/dependencies Sources
> Hit http://us.archive.ubuntu.com quantal Release
> Hit http://apt.puppetlabs.com quantal/main amd64 Packages             
> Hit http://us.archive.ubuntu.com quantal-security Release
> Hit http://apt.puppetlabs.com quantal/dependencies amd64 Packages     
> Hit http://apt.puppetlabs.com quantal/main i386 Packages              
> Hit http://us.archive.ubuntu.com quantal-updates Release
> Hit http://apt.puppetlabs.com quantal/dependencies i386 Packages      
> Hit http://us.archive.ubuntu.com quantal/main Sources
> Hit http://us.archive.ubuntu.com quantal/main amd64 Packages
> Hit http://us.archive.ubuntu.com quantal/main i386 Packages
> Hit http://us.archive.ubuntu.com quantal/main Translation-en
> Hit http://us.archive.ubuntu.com quantal-security/main Sources
> Hit http://us.archive.ubuntu.com quantal-security/main amd64 Packages
> Hit http://us.archive.ubuntu.com quantal-security/main i386 Packages
> Hit http://us.archive.ubuntu.com quantal-security/main Translation-en
> Hit http://us.archive.ubuntu.com quantal-updates/main Sources
> Hit http://us.archive.ubuntu.com quantal-updates/main amd64 Packages
> Hit http://us.archive.ubuntu.com quantal-updates/main i386 Packages
> Ign http://apt.puppetlabs.com quantal/dependencies Translation-en_US
> Hit http://us.archive.ubuntu.com quantal-updates/main Translation-en
> Ign http://apt.puppetlabs.com quantal/dependencies Translation-en
> Ign http://apt.puppetlabs.com quantal/main Translation-en_US
> Ign http://apt.puppetlabs.com quantal/main Translation-en
> Ign http://us.archive.ubuntu.com quantal/main Translation-en_US
> Ign http://us.archive.ubuntu.com quantal-security/main Translation-en_US
> Ign http://us.archive.ubuntu.com quantal-updates/main Translation-en_US
> Reading package lists... Done
>
>
> On Friday, June 14, 2013 10:30:38 PM UTC-4, Justin wrote:
>>
>> Read through the thread and didn't see a fix. I'm running into this issue 
>> with a new Ubuntu server. Any help?
>>
>> Here's how I installed the repo.
>>
>> ~# lsb_release -a
>> No LSB modules are available.
>> Distributor ID: Ubuntu
>> Description:    Ubuntu 12.10
>> Release:        12.10
>> Codename:       quantal
>>
>> ~# wget -q https://apt.puppetlabs.com/puppetlabs-release-quantal.deb
>>
>> ~# dpkg -i puppetlabs-release-quantal.deb 
>> (Reading database ... 60865 files and directories currently installed.)
>> Preparing to replace puppetlabs-release 1.0-7 (using 
>> puppetlabs-release-quantal.deb) ...
>> Unpacking replacement puppetlabs-release ...
>> Setting up puppetlabs-release (1.0-7) ...
>>
>> ~# grep '^deb' /etc/apt/sources.list.d/puppetlabs.list
>> deb http://apt.puppetlabs.com quantal main
>> deb-src http://apt.puppetlabs.com quantal main
>> deb http://apt.puppetlabs.com quantal dependencies
>> deb-src http://apt.puppetlabs.com quantal dependencies
>>
>> # apt-get install puppet
>> 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:
>>  puppet : Depends: puppet-common (= 3.2.1-1puppetlabs1) but it is not 
>> going to be installed
>> E: Unable to correct problems, you have held broken packages.
>>
>>
>> On Thursday, May 23, 2013 5:25:52 PM UTC-4, Eric Sorenson wrote:
>>>
>>> Quick question for those of you affected by this -- what did you to do 
>>> to add the puppetlabs apt repo? 
>>>
>>> Did you do it through the method described here: 
>>> http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu
>>>
>>> .. or some other way? I'm trying to suss out whether the docs / packages 
>>> are messing people up.
>>>
>>> thx
>>> eric0
>>>
>>>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to