Andrei,
I found the answer in /tmp/logs. The AMI I was using (it's a Ubuntu
10.04), already included the latest cdh3 release in its sources (|deb
http://archive.cloudera.com/debian maverick-cdh3 contrib||)| and I think
that's the reason I see cdh3u3 installed.
Thanks for your quick help!
Sebastian
On 10.04.2012 14:12, Andrei Savu wrote:
It should work with a custom ami that's also running Ubuntu 10.04.
Anything interesting in /tmp/logs?
On Tue, Apr 10, 2012 at 3:05 PM, Sebastian Schoenherr
<[email protected]
<mailto:[email protected]>> wrote:
Hi Andrei,
I'm using ubuntu AMIs (tried it with ubuntu 10.4 and ubuntu 11.10)
cheers,
sebastian
On 10.04.2012 14:02, Andrei Savu wrote:
What OS is running your custom AMI?
On Tue, Apr 10, 2012 at 2:55 PM, Sebastian Schoenherr
<[email protected]
<mailto:[email protected]>> wrote:
Hi guys,
I've some problems using the whirr.env.repo with whirr 0.7.1.
When specifying a custom AMI the newest version of cdh3
(currently cdh3u3) is getting installed even if the variable
whirr.env.repo=cdh3u2 is set.
I tried the exact same configuration with a standard AMI
(ami-da0cf8b3) and everything works as expected.
Any suggestions what I might be missing?
Cheers,
Sebastian
--
Sebastian Schoenherr
PhD student in Bioinformatics
Institute of Computer Science
Division of Genetic Epidemiology
[email protected]
http://dbis-informatik.uibk.ac.at
http://www.i-med.ac.at/genepi/
