Bug#733977: boinc-app-milkyway: Please sync with upstream
costamagnagianfranco at yahoo.it
Mon Jan 13 11:19:10 UTC 2014
Hi Ken, I merged and pushed on debian git my local changes.
For separation I didn't succeed in making it work, so I disabled it (otherwise you won't get new work if you submit too many computation error units)
in order to make it work
clone the milkyway code
clone the debian directory
make a tarball of the source package
report here in case of troubles
> Il Domenica 12 Gennaio 2014 10:39, Gianfranco Costamagna <costamagnagianfranco at yahoo.it> ha scritto:
> > Hi Ken, I had more luck than you in my boinc-app-milkyway from github.
> I can run and validate successfully every milkyway_nbody task but I get a
> failure on milkybody_separation one.
> I don't have the nbody build now, I can give it to you tomorrow if you are
> Anyway for making it build:
> install boinc, boinc-app-dev, boinc-dev
> clone the repository
> git submodule init
> git submodule update
> delete the boinc folder (in this way we will use _our_ boinc libraries)
> apply the two pull requests
> https://github.com/Milkyway-at-home/milkywayathome_client/pulls (or just use the
> patches in debian directory)
> clone the debian directory from here
> dpkg-buildpackage should do the trick
> On monday I'll update the debian git repository, it won't work right now
> after you create the package (I'll change the debian/rules for building only
> the nbody) you will be able to run milkyway.
> As soon as I get more feedbacks, and if I don't figure out what is wrong
> with separation, I'll update milkyway using only nbody platform (and of
> course after I'm sure this is the right client to ship).
> EDIT: I see that maybe separation isn't just supported
>> Il Domenica 12 Gennaio 2014 9:27, Ken Sharp
> <imwellcushtymelike at googlemail.com> ha scritto:
>> > I'm not sure if the code you referenced is the correct code.
>> to the forums the original code didn't have a licence and the newer
>> hasn't been released yet, at least that's what I got from the
>> the threads. There really is nothing made clear on the subject.
>> I've asked for a little clarity but with no response so far:
>> I tried building the code from github but it can't find libraries, uses
>> old libraries.... a bit of a nightmare. Probably isn't much point in
>> using that code until someone officially tells us what is going on.
>> On 03/01/14 00:28, Gianfranco Costamagna wrote:
>>> Hi Ken
>>> thanks for your report.
>>> Unfortunately I tried some time ago to package again milkyway with the
>> code hosted here 
>>> Code that I think is the official client one.
>>> Anyway I'm just stuck with some errors when I run the package with
>> boinc, and I get only "computation errors" messages.
>>> I also asked two pull requests , to fix a build failure and a
>> security issue.
>>> Nobody replied so far.
>>> What can I do? Fix everything without upstream support?
>>> I can, but I don't have time and man power for making the package
>> stable without looking really deeply at the code.
>>> I'll try again with the last milkyway code, can you please try to
>> a better contact with upstream?
>>>  https://github.com/Milkyway-at-home/milkywayathome_client
>>>  https://github.com/Milkyway-at-home/milkywayathome_client/pulls
>>>> Il Giovedì 2 Gennaio 2014 20:48, Ken Sharp
>> <imwellcushtymelike at googlemail.com> ha scritto:
>>>>> Package: boinc-app-milkyway
>>>> Version: 0.18d-4
>>>> The current version supplied by boinc-app-milkyway appears to run
>>>> on armel but:
>>>> 1. The estimated runtime is always way off.
>>>> 2. The results are always invalid.
>>>> 3. It's a really old version: there will be many changes
>>>> and the current upstream 1.x branch which will fix a lot of bugs.
>>>> If there is anything further needed then please let me know.
>>>> pkg-boinc-devel mailing list
>>>> pkg-boinc-devel at lists.alioth.debian.org
> pkg-boinc-devel mailing list
> pkg-boinc-devel at lists.alioth.debian.org
More information about the pkg-boinc-devel