<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div><span>Sorry for the delay, it took me a while to understand this mail... :) your git tricks are awesome!<br></span></div><div><br>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!<br>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?<br>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?<br>Don't know, just guessing, having so many "debian" directories will be a little painful in updates, but not so much anyway ;)<br><br></div><div>Just my 0.02 $<br><br></div><div>Gianfranco<br><br>
<blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: arial, helvetica, sans-serif; font-size: 10pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">Da:</span></b> "pkg-boinc-commits-request@lists.alioth.debian.org" <pkg-boinc-commits-request@lists.alioth.debian.org><br> <b><span style="font-weight: bold;">A:</span></b> pkg-boinc-commits@lists.alioth.debian.org <br> <b><span style="font-weight: bold;">Inviato:</span></b> Domenica 30 Dicembre 2012 13:00<br> <b><span style="font-weight: bold;">Oggetto:</span></b> pkg-boinc-commits Digest, Vol 79, Issue 10<br> </font> </div> <br>Send pkg-boinc-commits mailing list submissions to<br> <a ymailto="mailto:pkg-boinc-commits@lists.alioth.debian.org"
href="mailto:pkg-boinc-commits@lists.alioth.debian.org">pkg-boinc-commits@lists.alioth.debian.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-commits" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-commits</a><br><br>or, via email, send a message with subject or body 'help' to<br> <a ymailto="mailto:pkg-boinc-commits-request@lists.alioth.debian.org" href="mailto:pkg-boinc-commits-request@lists.alioth.debian.org">pkg-boinc-commits-request@lists.alioth.debian.org</a><br><br>You can reach the person managing the list at<br> <a ymailto="mailto:pkg-boinc-commits-owner@lists.alioth.debian.org" href="mailto:pkg-boinc-commits-owner@lists.alioth.debian.org">pkg-boinc-commits-owner@lists.alioth.debian.org</a><br><br>When replying, please edit your Subject line so it is more
specific<br>than "Re: Contents of pkg-boinc-commits digest..."<br><br><br>Today's Topics:<br><br> 1. FW: 7.0.42-trunk and SETI (Steffen M?ller)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sat, 29 Dec 2012 18:15:34 +0100<br>From: "Steffen M?ller" <<a ymailto="mailto:steffen_moeller@gmx.de" href="mailto:steffen_moeller@gmx.de">steffen_moeller@gmx.de</a>><br>To: <a ymailto="mailto:pkg-boinc-commits@lists.alioth.debian.org" href="mailto:pkg-boinc-commits@lists.alioth.debian.org">pkg-boinc-commits@lists.alioth.debian.org</a><br>Subject: FW: 7.0.42-trunk and SETI<br>Message-ID: <<a ymailto="mailto:20121229171534.75070@gmx.net" href="mailto:20121229171534.75070@gmx.net">20121229171534.75070@gmx.net</a>><br>Content-Type: text/plain; charset="utf-8"<br><br>Dear all,<br><br> 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<br> * upstream's git repository as the "master" branch<br> * from there I branched into "upstream" - no further cleanups done on it, yet<br> * into an orphaned branch "debian" of it I copied the debian directory from our pkg-boinc/boinc.git repository<br> * a branch of(f) "master", named "working-with-debian" I merged with the "debian" branch into<br> * a series of changes were required to get our patches adjusted - some could be removed, which is nice<br> * worked on improved install instructions for the server side (which upstream today expects not to be installed anywhere beyond the checkout)<br> * 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"<br><br> For the curious:<br> * The boinc client of the trunk works nicely and does not show the issues of the 7.0.42 release in the boinc-manager.<br> * 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.<br> * I am now addressing (simplifying) the Debian side of the boinc-server-maker package<br><br> 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.<br><br> 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?<br><br> Kind regards,<br><br> Steffen<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.alioth.debian.org/pipermail/pkg-boinc-commits/attachments/20121229/b3ff17c4/attachment-0001.html"
target="_blank">http://lists.alioth.debian.org/pipermail/pkg-boinc-commits/attachments/20121229/b3ff17c4/attachment-0001.html</a>><br><br>------------------------------<br><br>_______________________________________________<br>pkg-boinc-commits mailing list<br><a ymailto="mailto:pkg-boinc-commits@lists.alioth.debian.org" href="mailto:pkg-boinc-commits@lists.alioth.debian.org">pkg-boinc-commits@lists.alioth.debian.org</a><br><a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-commits" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-commits</a><br><br>End of pkg-boinc-commits Digest, Vol 79, Issue 10<br>*************************************************<br><br><br> </div> </div> </blockquote> </div></div></body></html>