[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#610653: ITP: dmtcp -- Checkpoint/Restart functionality for Linux processes



That's pretty cool. Thank you Yaroslav!
I will give it a try soon.

--Kapil

On Wed, Feb 2, 2011 at 7:44 PM, Yaroslav Halchenko
<debian@onerussian.com> wrote:
>
> On Wed, 02 Feb 2011, Kapil Arya wrote:
>> Okay, so I have fixed this one as well. Here is the link to the latest
>> .dsc file:
>> http://mentors.debian.net/debian/pool/main/d/dmtcp/dmtcp_1.2.0+svn873-1.dsc
> ok -- I will have a look
>
>>    Can you tell me how to setup this environment having 32-build
>> system over 32/64 bit capable kernel so that I can do some testing in
>> that environment without wasting your time :-)?
> quite easy actually.
>
> look at the call to cowbuilder (at the end of the script) in the scripts
> we are using for managing our builds for NeuroDebian:
>
> http://git.debian.org/?p=pkg-exppsy/neurodebian.git;a=blob;hb=HEAD;f=tools/nd_adddist
>
> you might call it manually or actually simply use our nd_ scripts to
> manage and build across any number of distributions.  May be you would
> not want to deal with nd+ family of distributions which would include
> also our neuro.debian.net repository into apt sources
>
> so it should be as easy as
>
>  nd_adddist  debian sid
>
> if you are to use our scripts (you might want to adjust
> /etc/neurodebian/cmdsettings.sh to point to the location you like to have cow
> chroots).
>
> having created all cows for all "interesting" ones listed in allnddist,
> building backports for ALL "interesting" debian and ubuntu releases as easy as
>
> sudo nd_build4allnd blah-xyz.dsc
>
> ;-)
>
> alternatively you could simply call cowbuilder --build ... for every distribution
>
> http://wiki.debian.org/cowbuilder  could provide more information
>
> --
> =------------------------------------------------------------------=
> Keep in touch                                     www.onerussian.com
> Yaroslav Halchenko                 www.ohloh.net/accounts/yarikoptic
>



Reply to: