Hi Yair,
I managed to install the two missing dependencies from the web and now the
build seem to run ok but apparently 8gb of RAM are not sufficient to build
ovirt-engine so I'll have to give it a pass for now and wait for binary
releases.
Regards,
Dennis
On 10/30/2011 01:46 PM, Yair Zaslavsky wrote:
> Hi Dennis,
> Do you still need assistance with this?
>
> Kind regards,
> Yair
>
>
> On 10/30/2011 02:24 PM, Dennis Jacobfeuerborn wrote:
>> On 10/30/2011 06:09 AM, Livnat Peer wrote:
>>> On 10/30/2011 01:36 AM, Dennis Jacobfeuerborn wrote:
>>>> On 10/29/2011 10:39 PM, Livnat Peer wrote:
>>>>> On 10/29/2011 10:08 PM, Dennis Jacobfeuerborn wrote:
>>>>>> On 10/29/2011 07:15 PM, Livnat Peer wrote:
>>>>>>> On 10/29/2011 05:48 PM, Dennis Jacobfeuerborn wrote:
>>>>>>>> On 10/28/2011 02:09 AM, Livnat Peer wrote:
>>>>>>>>> On 10/27/2011 11:51 PM, Itamar Heim wrote:
>>>>>>>>>> Here we go...
>>>>>>>>>>
>>>>>>>>>> - gerrit is up.
>>>>>>>>>> - ovirt-engine git repo is there.
>>>>>>>>>> - will upload the other repositories soon.
>>>>>>>>>>
>>>>>>>>>> below you can find the steps on how to get the code (yes,
>>>>>>>>>> coming to
>>>>>>>>>> you
>>>>>>>>>> in wiki soon).
>>>>>>>>>> a link to the wiki on how to build oVirt will be sent soon by
>>>>>>>>>> Livnat.
>>>>>>>>>>
>>>>>>>>>> It's exciting to see everyone coming together to build a
>>>>>>>>>> community,
>>>>>>>>>> and
>>>>>>>>>> I'm looking forward to working together on oVirt.
>>>>>>>>>>
>>>>>>>>>> Welcome everyone,
>>>>>>>>>> Itamar
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Welcome indeed,
>>>>>>>>>
>>>>>>>>> A link to a wiki with info for setting development environment -
>>>>>>>>> http://www.ovirt.org/wiki/Building_Ovirt_Engine
>>>>>>>>
>>>>>>>> I tried building with these instructions but get "9 required
>>>>>>>> artifacts
>>>>>>>> are missing." Also I get a *lot* of "unable to fine resource"
>>>>>>>> info/warning messages. I've attached the output of the maven run.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Dennis
>>>>>>>>
>>>>>>>
>>>>>>> Hi Dennis,
>>>>>>> Maven tries to download dependencies that are required by your
>>>>>>> project,
>>>>>>> in this case oVirt.
>>>>>>> For each dependency maven iterates over all the repositories
>>>>>>> defined in
>>>>>>> the pom.xml and stops when it finds the required dependency, if it
>>>>>>> does
>>>>>>> not find the Jar in a repository it issues info message and looks in
>>>>>>> the
>>>>>>> next repsitory. The info message looks like "[INFO] Unable to find
>>>>>>> resource XXX in repository YYY" and does not indicate on a problem.
>>>>>>>
>>>>>>> For the errors you get -
>>>>>>>
>>>>>>> I looked into the first missing jar commons-httpclient-2.0.2, it
>>>>>>> can be
>>>>>>> found in -
>>>>>>> http://repository.jboss.org/maven2/apache-httpclient/commons-httpclient/2.0…
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> but it looks like you get -
>>>>>>>
>>>>>>> Authorization failed: Access denied to:
>>>>>>> http://repository.jboss.org/maven2/apache-httpclient/commons-httpclient/2.0…
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Any idea why you got authorization error? I can access it locally.
>>>>>>> Can you try again? maybe a temporary problem.
>>>>>>
>>>>>> When I access that URL in a browser I still get a 403 Forbidden
>>>>>> response.
>>>>>> I can access http://repository.jboss.org/ but not
>>>>>> http://repository.jboss.org/maven2/.
>>>>>>
>>>>>> In fact the maven2 directory doesn't show up in the directory listing
>>>>>> when requesting http://repository.jboss.org/ which could
>>>>>> potentially be
>>>>>> an SELinux issue on the server. Has this directory perhaps been
>>>>>> manually
>>>>>> copied to the server without the correct SELinux labels?
>>>>>>
>>>>>> Regards,
>>>>>> Dennis
>>>>>
>>>>> Can you access this -
>>>>> https://repository.jboss.org/nexus/content/repositories/central/commons-htt…
>>>>>
>>>>>
>>>>
>>>> Yes, this URL works fine.
>>>>
>>>> Regards,
>>>> Dennis
>>>>
>>>
>>> Hi Dennis,
>>> It looks like repo - http://repository.jboss.org/maven2/ is deprecated
>>> and can only be accessed within RedHat Network, probably for JBoss
>>> engineers.
>>>
>>> I have attached a temporary patch with another URL for this repo.
>>> The new URL is accessible from outside of RedHat but we should replace
>>> it with the new repositories in Nexus.
>>>
>>> As i have to catch a flight in a few hours i have no time to test it so
>>> i hope it will do the work.
>>
>> This improved the situation but there are still two missing artifacts:
>>
>> 1) sun-jaxb:jaxb-api:jar:2.1.9
>> 2) oswego-concurrent:concurrent:jar:1.3.4
>>
>> jaxb-api seems to be present in the new repository but only version
>> 2.0.5 and concurrent seems to be missing completely.
>>
>> Regards,
>> Dennis
>>
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
Here we go...
- gerrit is up.
- ovirt-engine git repo is there.
- will upload the other repositories soon.
below you can find the steps on how to get the code (yes, coming to you
in wiki soon).
a link to the wiki on how to build oVirt will be sent soon by Livnat.
It's exciting to see everyone coming together to build a community, and
I'm looking forward to working together on oVirt.
Welcome everyone,
Itamar
How to use:
1. registering as a user:
- you can use any OpenID provider for now[1]
- login page shows google and yahoo
- any fedora FAS account can login as well via
https://admin.fedoraproject.org/accounts/openid/id/<username>
2. set ssh keys in gerrit settings
- on your local machine, create a set of ssh keys if you don't have one
via 'ssh-keygen -t rsa'
- update via gerrit settings the ssh public key to allow ssh to gerrit
3. define gerrit in ~/.ssh/config
Host gerrit.ovirt.org
HostName gerrit.ovirt.org
Port 29418
User <username>
4. check ssh works correctly, verify and ack the host fingerprint:
ssh gerrit.ovirt.org
if you get this, it is fine:
*** Welcome to Gerrit Code Review ****
5. cloning the repo
git clone gerrit.ovirt.org:ovirt-engine
this can be done without registering to gerrit using:
git clone git://gerrit.ovirt.org/ovirt-engine
6. install the change-Id hook - you must do this before you commit anything:
scp -p gerrit.ovirt.org:hooks/commit-msg .git/hooks/
7. do some work/commit/etc.
wiki link on how to build/run ovirt will be sent by Livnat soon.
8. rebase:
git fetch gerrit.ovirt.org:ovirt-engine master
9. push your patch for review:
git push gerrit.ovirt.org:ovirt-engine HEAD:refs/for/master
10. track patch review process
the review process is comprised of:
- anyone can send a patch
- anyone can code review and comment on the patch and +1/-1. This helps
maintainers in reviewing the patches.
- a maintainer can code review it with +2 it, which is required to
commit (submit) it.
- someone (anyone) needs to confirm they checked the patch works and
flag it as verified +1
- a maintainer can submit (commit) the patch when it has:
Code Review: +2
Verified: +1
- nacked (-1) patches should not be submitted
- a submitted patch is merged to the git
TODOs:
- emails to mailing list on patches/commits[2]
- upload repos of more projects
- have gerrit add acked-by/verified-by based on the gerrit reviewes?
- mirror to github
[1] if anyone provides a reason to limit to specific OpenID providers
that's an option as well.
[2] basic emails until we merge the gerrit patches sending them inline -
we are working on sending them to upstream gerrit.
