Those instructions will work. Build 117 closes for SFW in a less than
45 minutes. If you have an approved RTI and you are comfortable that
there aren't any problems with your integration, you will need to do it
before 11PM PDT (40 minutes from now) to make build 117.
-Norm
Spoorthy H.S wrote:
> Norm,
>
> I thought to follow the steps described here..
> http://ostest.central.sun.com/wiki/index.php/Package_Delivery_Project#12._Integrate_Package
>
>
>
> If the process is changed now, Please let me know on which commands I
> can use to integrate.
>
> Also, Build 117 is 06/15/2009. When does the gate close ? Before what
> date should we integrate the package to the gate ?
>
> Thanks a lot
> Spoorthy
>
> Norm Jacobs wrote:
>>
>> A few things:
>>
>> 1. If you were planning on integrating into the SFW Nevada gate, your
>> parent workspace should be /ws/sfwnv-gate. You can use "-p
>> /ws/sfwnv-gate" to override the workspace parent during putback.
>> 2. You need to be logged into the gate machine (sfwnv) to putback
>> into the gate. (this is on purpose).
>> 3. Your workspace had a leftover lock that appears to be gone now.
>> (I just looked at it.)
>>
>>
>> -Norm
>>
>> Spoorthy H.S wrote:
>>> Hi,
>>>
>>> I am trying to do putback. If I do bringover of some updated file, I
>>> get the follwoing error.
>>>
>>> *Parent workspace: /ws/sfwnv-clone
>>> Child workspace: /builds1/ss22
>>> bringover: Cannot obtain a write lock in workspace "/builds1/ss22"
>>> because it has the following locks:
>>> User ss224839 has been running a bringover command (pid 8567)
>>> on mogo for 18 hours, 36 minutes
>>> (Error 2021)
>>> *
>>> If I do "$ps -aef | grep 8567", nothing will be displayed. And I'm
>>> unable to find that pid even if I do a grep. Can anybody help me how
>>> to address this asap ?
>>>
>>> Thanks
>>> Spoorthy
>>> _______________________________________________
>>> sfwnv-discuss mailing list
>>> sfwnv-discuss at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/sfwnv-discuss
>>
