7.0.42-trunk and SETI (Steffen M?ller)

Wed Jan 2 00:48:21 UTC 2013

Sorry for the delay, it took me a while to understand this mail... :) your git tricks are awesome!

The auto-builders in my ppa I am almost sure they can only build the "master" branch, I didn't manage to build another one, I tried so many times, but they fetch only master!
So this could be an issue while building both packages, I mean, how can I in the same building process build both server and client? should we have two different sources and building processes?
What about ask upstream to backport the server parts into the 7.0.x branch since we can provide them they are stable and safe for use?
Don't know, just guessing, having so many "debian" directories will be a little painful in updates, but not so much anyway ;)

Just my 0.02 $

Gianfranco

>________________________________
> Da: "pkg-boinc-commits-request at lists.alioth.debian.org" <pkg-boinc-commits-request at lists.alioth.debian.org>
>A: pkg-boinc-commits at lists.alioth.debian.org 
>Inviato: Domenica 30 Dicembre 2012 13:00
>Oggetto: pkg-boinc-commits Digest, Vol 79, Issue 10
> 
>Send pkg-boinc-commits mailing list submissions to
>    pkg-boinc-commits at lists.alioth.debian.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>    http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-commits
>
>or, via email, send a message with subject or body 'help' to
>    pkg-boinc-commits-request at lists.alioth.debian.org
>
>You can reach the person managing the list at
>    pkg-boinc-commits-owner at lists.alioth.debian.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of pkg-boinc-commits digest..."
>
>
>Today's Topics:
>
>   1. FW: 7.0.42-trunk and SETI (Steffen M?ller)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Sat, 29 Dec 2012 18:15:34 +0100
>From: "Steffen M?ller" <steffen_moeller at gmx.de>
>To: pkg-boinc-commits at lists.alioth.debian.org
>Subject: FW: 7.0.42-trunk and SETI
>Message-ID: <20121229171534.75070 at gmx.net>
>Content-Type: text/plain; charset="utf-8"
>
>Dear all,
>
>I took the time "between the years" to address the boinc server side a bit more. That server side however for the more recent versions of boinc only compiles for the "trunk" or the version of the repository that is not tagged with a client release. And we were kindly asked to work from that max-current codebase for that server packages. Now, before I push anything to our alioth git repository, I thought I better get your comments on this setup. I took
>* upstream's git repository as the "master" branch
>* from there I branched into "upstream" - no further cleanups done on it, yet
>* into an orphaned branch "debian" of it I copied the debian directory from our pkg-boinc/boinc.git repository
>* a branch of(f) "master", named "working-with-debian" I merged with the "debian" branch into
>* a series of changes were required to get our patches adjusted - some could be removed, which is nice
>* worked on improved install instructions for the server side (which upstream today expects not to be installed anywhere beyond the checkout)
>* all changes were _not_ committed to "working-with-debian" but stashed and committed to a new branch of(f) the "debian" branch, named "debian-for-trunk"
>
>For the curious:
>* The boinc client of the trunk works nicely and does not show the issues of the 7.0.42 release in the boinc-manager.
>* boinc-app-seti crashes with the librararies it provides, and it needs a bit of a tweak to compile with it - Gianfranco has just kindly cleaned up my changes - many thanks! This strongly supports the need of static binaries for the scientific apps, I admit it.
>* I am now addressing (simplifying) the Debian side of the boinc-server-maker package
>
>Now, how should this work be fed back to our git repository? I would like to avoid too much of a redundancy with boinc-upstream's repository on our servers, even though this might be somewhat unavoidable with my limited understanding of the PPA auto-build instructions - Gianfranco? The only novelty is the "debian-for-trunk" branch and it could just sit as an orphan branch in our pkg-boinc/boinc.git repository as it is now. We would also need the "debian" branch to keep the differences between the two for future updates. But in a pure git repository for packaging we would have that pure debian branch already, anyway.
>
>We are bitten a bit by our heritage of the subversion exports that make our upstream folders, so we cannot just migrate quickly between the trunk /head and the tags of a particular release for the upstream code. Are there ideas on your side about it all?
>
>Kind regards,
>
>Steffen
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: <http://lists.alioth.debian.org/pipermail/pkg-boinc-commits/attachments/20121229/b3ff17c4/attachment-0001.html>
>
>------------------------------
>
>_______________________________________________
>pkg-boinc-commits mailing list
>pkg-boinc-commits at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-commits
>
>End of pkg-boinc-commits Digest, Vol 79, Issue 10
>*************************************************
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-boinc-commits/attachments/20130102/76d1f15e/attachment-0001.html>