You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by mojorising <mo...@aim.com> on 2013/04/25 08:13:08 UTC
The requested profile "deps" could not be activated
Hello! I've been following the documentation at:
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/sect-source-buildrpm.html
..and when I run 'mvn -P deps', I get an error:
[WARNING] The requested profile "deps" could not be activated because it
does not exist.
Might anyone here be able to tell me why this error appears? Do I need to
create the 'deps' profile or move it from somewhere?
I tried to continue with the installation steps but when I try './waf rpm',
I get:
'-bash: ./waf: No such file or directory', which, of course, is not present
if I check. I presume this waf file is missing because the previous step
failed, though I'm not sure.
I didn't see any other reference to this in the documentation. I also
checked Google and this list archive but didn't find anything about this
problem (I could have missed it).
Thanks a lot for your help!
Mike
Re: The requested profile "deps" could not be activated
Posted by mojorising <mo...@aim.com>.
Sweet! I'll definitely give that a go.
Best,
Mike
On 25 April 2013 00:47, Sebastien Goasguen <ru...@gmail.com> wrote:
>
> On Apr 25, 2013, at 3:41 AM, mojorising <mo...@aim.com> wrote:
>
> > Hi, Sebastien,
> >
> > Thanks so much for the reply! I just checked and tried again to be sure
> --
> > I am running this from the root of the cloudstack source. I did get the
> > same result when I tried again as well. :/
> >
> > I saw a 'deps' sub-directory in the source directory. It
> > contains install-non-oss.sh and XenServerJava. I don't see anything else
> > in the source directory with that name.
> >
> > [root@manage1 cloudstack]# ls
> > agent awsapi-setup cloud-cli deps framework
> > NOTICE pom.xml scripts target usage
> > agent-simulator build configure-info.in developer INSTALL.md
> > packaging python server test utils
> > api CHANGES core docs LICENSE
> > patches README.md services tools version-info.in
> > awsapi client debian engine
> > m2-settings.xml plugins README.tools.md setup ui
> vmware-base
> >
> > [root@manage1 cloudstack]# pwd
> > /root/cloudstack
> >
> >
> > Also, just remembered that I forgot some details: The OS is CentOS 6.4
> and
> > I have checked out the latest code as of today (4.0.2) from
> > https://git-wip-us.apache.org/repos/asf/cloudstack.git.
> >
> > *** Okay. Just before clicking send on this I decided to try downloading
> > the bzipped copy of the code and running the Maven task from that
> directory
> > ..and it worked. Looks like the same directory on my checked out copy was
> > missing the file, 'pom.xml'. ***
> >
> > Thanks again! Hopefully it's smooth sailing from here.
> >
> >
>
> Great, you might want to check out my screencast:
> http://www.youtube.com/watch?v=vvgIkF1e1QE
>
> Where I follow the testing procedure for 4.0.2
>
>
> > Mike
> >
> >
> >
> > On 24 April 2013 23:56, Sebastien Goasguen <ru...@gmail.com> wrote:
> >
> >>
> >> On Apr 25, 2013, at 2:13 AM, mojorising <mo...@aim.com> wrote:
> >>
> >>> Hello! I've been following the documentation at:
> >>>
> >>>
> >>
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/sect-source-buildrpm.html
> >>>
> >>> ..and when I run 'mvn -P deps', I get an error:
> >>>
> >>> [WARNING] The requested profile "deps" could not be activated because
> it
> >>> does not exist.
> >>>
> >>
> >> Can you make sure to run this when in the root of the CloudStack source.
> >> Do not do it in any of the subdirectories.
> >>
> >>> Might anyone here be able to tell me why this error appears? Do I need
> to
> >>> create the 'deps' profile or move it from somewhere?
> >>>
> >>> I tried to continue with the installation steps but when I try './waf
> >> rpm',
> >>> I get:
> >>> '-bash: ./waf: No such file or directory', which, of course, is not
> >> present
> >>> if I check. I presume this waf file is missing because the previous
> step
> >>> failed, though I'm not sure.
> >>>
> >>> I didn't see any other reference to this in the documentation. I also
> >>> checked Google and this list archive but didn't find anything about
> this
> >>> problem (I could have missed it).
> >>>
> >>>
> >>> Thanks a lot for your help!
> >>> Mike
> >>
> >>
>
>
Re: The requested profile "deps" could not be activated
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 25, 2013, at 3:41 AM, mojorising <mo...@aim.com> wrote:
> Hi, Sebastien,
>
> Thanks so much for the reply! I just checked and tried again to be sure --
> I am running this from the root of the cloudstack source. I did get the
> same result when I tried again as well. :/
>
> I saw a 'deps' sub-directory in the source directory. It
> contains install-non-oss.sh and XenServerJava. I don't see anything else
> in the source directory with that name.
>
> [root@manage1 cloudstack]# ls
> agent awsapi-setup cloud-cli deps framework
> NOTICE pom.xml scripts target usage
> agent-simulator build configure-info.in developer INSTALL.md
> packaging python server test utils
> api CHANGES core docs LICENSE
> patches README.md services tools version-info.in
> awsapi client debian engine
> m2-settings.xml plugins README.tools.md setup ui vmware-base
>
> [root@manage1 cloudstack]# pwd
> /root/cloudstack
>
>
> Also, just remembered that I forgot some details: The OS is CentOS 6.4 and
> I have checked out the latest code as of today (4.0.2) from
> https://git-wip-us.apache.org/repos/asf/cloudstack.git.
>
> *** Okay. Just before clicking send on this I decided to try downloading
> the bzipped copy of the code and running the Maven task from that directory
> ..and it worked. Looks like the same directory on my checked out copy was
> missing the file, 'pom.xml'. ***
>
> Thanks again! Hopefully it's smooth sailing from here.
>
>
Great, you might want to check out my screencast:
http://www.youtube.com/watch?v=vvgIkF1e1QE
Where I follow the testing procedure for 4.0.2
> Mike
>
>
>
> On 24 April 2013 23:56, Sebastien Goasguen <ru...@gmail.com> wrote:
>
>>
>> On Apr 25, 2013, at 2:13 AM, mojorising <mo...@aim.com> wrote:
>>
>>> Hello! I've been following the documentation at:
>>>
>>>
>> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/sect-source-buildrpm.html
>>>
>>> ..and when I run 'mvn -P deps', I get an error:
>>>
>>> [WARNING] The requested profile "deps" could not be activated because it
>>> does not exist.
>>>
>>
>> Can you make sure to run this when in the root of the CloudStack source.
>> Do not do it in any of the subdirectories.
>>
>>> Might anyone here be able to tell me why this error appears? Do I need to
>>> create the 'deps' profile or move it from somewhere?
>>>
>>> I tried to continue with the installation steps but when I try './waf
>> rpm',
>>> I get:
>>> '-bash: ./waf: No such file or directory', which, of course, is not
>> present
>>> if I check. I presume this waf file is missing because the previous step
>>> failed, though I'm not sure.
>>>
>>> I didn't see any other reference to this in the documentation. I also
>>> checked Google and this list archive but didn't find anything about this
>>> problem (I could have missed it).
>>>
>>>
>>> Thanks a lot for your help!
>>> Mike
>>
>>
Re: The requested profile "deps" could not be activated
Posted by mojorising <mo...@aim.com>.
Hi, Sebastien,
Thanks so much for the reply! I just checked and tried again to be sure --
I am running this from the root of the cloudstack source. I did get the
same result when I tried again as well. :/
I saw a 'deps' sub-directory in the source directory. It
contains install-non-oss.sh and XenServerJava. I don't see anything else
in the source directory with that name.
[root@manage1 cloudstack]# ls
agent awsapi-setup cloud-cli deps framework
NOTICE pom.xml scripts target usage
agent-simulator build configure-info.in developer INSTALL.md
packaging python server test utils
api CHANGES core docs LICENSE
patches README.md services tools version-info.in
awsapi client debian engine
m2-settings.xml plugins README.tools.md setup ui vmware-base
[root@manage1 cloudstack]# pwd
/root/cloudstack
Also, just remembered that I forgot some details: The OS is CentOS 6.4 and
I have checked out the latest code as of today (4.0.2) from
https://git-wip-us.apache.org/repos/asf/cloudstack.git.
*** Okay. Just before clicking send on this I decided to try downloading
the bzipped copy of the code and running the Maven task from that directory
..and it worked. Looks like the same directory on my checked out copy was
missing the file, 'pom.xml'. ***
Thanks again! Hopefully it's smooth sailing from here.
Mike
On 24 April 2013 23:56, Sebastien Goasguen <ru...@gmail.com> wrote:
>
> On Apr 25, 2013, at 2:13 AM, mojorising <mo...@aim.com> wrote:
>
> > Hello! I've been following the documentation at:
> >
> >
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/sect-source-buildrpm.html
> >
> > ..and when I run 'mvn -P deps', I get an error:
> >
> > [WARNING] The requested profile "deps" could not be activated because it
> > does not exist.
> >
>
> Can you make sure to run this when in the root of the CloudStack source.
> Do not do it in any of the subdirectories.
>
> > Might anyone here be able to tell me why this error appears? Do I need to
> > create the 'deps' profile or move it from somewhere?
> >
> > I tried to continue with the installation steps but when I try './waf
> rpm',
> > I get:
> > '-bash: ./waf: No such file or directory', which, of course, is not
> present
> > if I check. I presume this waf file is missing because the previous step
> > failed, though I'm not sure.
> >
> > I didn't see any other reference to this in the documentation. I also
> > checked Google and this list archive but didn't find anything about this
> > problem (I could have missed it).
> >
> >
> > Thanks a lot for your help!
> > Mike
>
>
Re: The requested profile "deps" could not be activated
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 25, 2013, at 2:13 AM, mojorising <mo...@aim.com> wrote:
> Hello! I've been following the documentation at:
>
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/sect-source-buildrpm.html
>
> ..and when I run 'mvn -P deps', I get an error:
>
> [WARNING] The requested profile "deps" could not be activated because it
> does not exist.
>
Can you make sure to run this when in the root of the CloudStack source. Do not do it in any of the subdirectories.
> Might anyone here be able to tell me why this error appears? Do I need to
> create the 'deps' profile or move it from somewhere?
>
> I tried to continue with the installation steps but when I try './waf rpm',
> I get:
> '-bash: ./waf: No such file or directory', which, of course, is not present
> if I check. I presume this waf file is missing because the previous step
> failed, though I'm not sure.
>
> I didn't see any other reference to this in the documentation. I also
> checked Google and this list archive but didn't find anything about this
> problem (I could have missed it).
>
>
> Thanks a lot for your help!
> Mike