What's the right repo to use for ubuntu 12.04?

Ron,

Sorry been away … but yeah, that certainly does work.

Thanks for sharing the info …

best rgds

··· On Friday, 1 February 2013 19:57:52 UTC, Ronald Wolf wrote: > > Chux, > > I'm also installing on Ubuntu 12.04, and the foreman-installer method > configures the following into /etc/apt/sources: > > deb http://deb.theforeman.org/ precise rc > > > This worked fine for me moments ago. > > Ron > > > On Thursday, January 31, 2013 12:29:09 PM UTC-6, Chux wrote: >> >> >> Hi, >> >> It's good to know there are several ways to install foreman on ubuntu .. >> I went the package route because there are multi admins looking after the >> host in question, and pkgs would be easier to manage without writing up too >> much docs for other sysadmins. >> >> However, the paths to the suggested ubuntu repo seems wrong, and the >> packages are not installing .. >> >> The following is my sources.list entry .. >> > deb http://deb.theforeman.org/ precise stable >> >> with this, an 'apt-get update' throws up errors like: >> > Failed to fetch >> http://deb.theforeman.org/dists/stable/main/binary-amd64/Packages 404 >> Not Found >> >> Looking at the foreman repo, I can see that there is no 'main' >> subdirectory of 'stable' .. eg., the correct path is >> http://deb.theforeman.org/dists/stable/binary-amd64/Packages .. so, >> this could be the problem .. >> >> I went ahead regardless and an 'apt-cache' surprisingly finds the puppet >> packages .. but an attempt to install (just foreman main package) throws up: >> ======================= >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> The following extra packages will be installed: >> foreman-proxy libjson-ruby libnet-ping-ruby libnet-ping-ruby1.8 >> libsinatra-ruby ruby-bundler ruby-json ruby-sinatra ruby-tilt >> The following NEW packages will be installed >> foreman foreman-proxy libjson-ruby libnet-ping-ruby libnet-ping-ruby1.8 >> libsinatra-ruby ruby-bundler ruby-json ruby-sinatra ruby-tilt >> 0 upgraded, 10 newly installed, 0 to remove and 90 not upgraded. >> Need to get 64.7 kB/1,446 kB of archives. >> After this operation, 5,546 kB of additional disk space will be used. >> Do you want to continue [Y/n]? Y >> WARNING: The following packages cannot be authenticated! >> ruby-json >> Install these packages without verification [y/N]? y >> Err http://deb.theforeman.org/ stable/main ruby-json amd64 1.7.3-1 >> 404 Not Found >> Failed to fetch >> http://deb.theforeman.org/pool/main/r/ruby-json/ruby-json_1.7.3-1_amd64.deb >> 404 Not Found >> ======================= >> >> So, it seems like a new 'main' path element needs to be created .. >> perhaps via a symlink .. >> >> Just seeking confirmation primarily .. >> >> Thanks in advance for responses .. >> >> rgds >> >

1.1 stable is out so you should use that repo instead of the RC one:

deb http://deb.theforeman.org/ precise stable

-Sam

··· On Fri, Feb 15, 2013 at 9:45 AM, Chux wrote:

Ron,

Sorry been away … but yeah, that certainly does work.

Thanks for sharing the info …

best rgds

On Friday, 1 February 2013 19:57:52 UTC, Ronald Wolf wrote:

Chux,

I’m also installing on Ubuntu 12.04, and the foreman-installer method
configures the following into /etc/apt/sources:

deb http://deb.theforeman.org/ precise rc

This worked fine for me moments ago.

Ron

On Thursday, January 31, 2013 12:29:09 PM UTC-6, Chux wrote:

Hi,

It’s good to know there are several ways to install foreman on ubuntu …
I went the package route because there are multi admins looking after the
host in question, and pkgs would be easier to manage without writing up too
much docs for other sysadmins.

However, the paths to the suggested ubuntu repo seems wrong, and the
packages are not installing …

The following is my sources.list entry …

deb http://deb.theforeman.org/ precise stable

with this, an ‘apt-get update’ throws up errors like:

Failed to fetch http://deb.theforeman.org/*dists/stable/main/binary-
*amd64/Packageshttp://deb.theforeman.org/dists/stable/main/binary-amd64/Packages
404 Not Found

Looking at the foreman repo, I can see that there is no 'main’
subdirectory of ‘stable’ … eg., the correct path is
http://deb.theforeman.org/**dists/stable/binary-amd64/**Packageshttp://deb.theforeman.org/dists/stable/binary-amd64/Packages
… so, this could be the problem …

I went ahead regardless and an ‘apt-cache’ surprisingly finds the puppet
packages … but an attempt to install (just foreman main package) throws up:

Reading package lists… Done
Building dependency tree
Reading state information… Done
The following extra packages will be installed:
foreman-proxy libjson-ruby libnet-ping-ruby libnet-ping-ruby1.8
libsinatra-ruby ruby-bundler ruby-json ruby-sinatra ruby-tilt
The following NEW packages will be installed
foreman foreman-proxy libjson-ruby libnet-ping-ruby libnet-ping-ruby1.8
libsinatra-ruby ruby-bundler ruby-json ruby-sinatra ruby-tilt
0 upgraded, 10 newly installed, 0 to remove and 90 not upgraded.
Need to get 64.7 kB/1,446 kB of archives.
After this operation, 5,546 kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
WARNING: The following packages cannot be authenticated!
ruby-json
Install these packages without verification [y/N]? y
Err http://deb.theforeman.org/ stable/main ruby-json amd64 1.7.3-1
404 Not Found
Failed to fetch http://deb.theforeman.org/*pool/main/r/ruby-json/ruby-
*json_1.7.3-1_amd64.debhttp://deb.theforeman.org/pool/main/r/ruby-json/ruby-json_1.7.3-1_amd64.deb
404 Not Found

So, it seems like a new ‘main’ path element needs to be created …
perhaps via a symlink …

Just seeking confirmation primarily …

Thanks in advance for responses …

rgds


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.