[boinc_dev] Boinc 7.3.19 uploaded on debian experimental

[Gianfranco Costamagna]

Il Lunedì 26 Maggio 2014 23:45, Guo Yixuan <culu.gyx at gmail.com> ha scritto:


>
>
>On Sun, May 25, 2014 at 4:37 AM, costamagnagianfranco at yahoo.it <costamagnagianfranco at yahoo.it> wrote:
>>
>> Hi Guo, considering that 7.3 is out since few months and the freeze
>> is 6 months from today I think we can have an upload for jessie
>> without any problem.
>>
>> Moreover Olly is trying to get wx2.8 out of jessie release, so we
>> might be forced to switch to the new release, as for the gcc patch.
>>
>> So in my opinion we should switch as soon as possible to the new
>> release, I'm actively monitoring boinc-alpha mail list and I didn't see
>> any showstoppers on this new release.
>>
>> In 6 months however we should have time to fix bugs and I'm sure
>> they will release at least 10 new bug-fix builds
>>
>> (and I think if everything works as in the ubuntu way even after the
>> freeze we will be able to upload some more bug fix releases)
>>
>> BTW I'm planning to upload a 7.2.47-3 package on unstable, I spot
>> a problem in the rules file (we were building always the server
>> packages because of a typo in rules)
>>
>> This is preventing the corresponding wheezy-bpo to be built on armhf.
>>
>> I'll just push a tag, I don't think is worth creating a branch. For me
>> we should focus on 7.3 asap.
>
>However, for reference, there're actually branches for older backports.
>In addition, I think it's useful to have a branch, instead only a tag.
>(Because you can only get it by
>  $ git fetch alioth --tags
>but not pull/fetch without parameters.)
>
>
>$ git branch -a |grep remotes/alioth
>  remotes/alioth/HEAD -> alioth/master
>  remotes/alioth/SZTAKI
>  remotes/alioth/SZTAKI_templates
>  remotes/alioth/backports/squeeze
>  remotes/alioth/debian-folder-HEAD
>  remotes/alioth/debian-folder-release
>  remotes/alioth/debian/backports/etch
>  remotes/alioth/debian/backports/hardy
>  remotes/alioth/debian/backports/jaunty
>  remotes/alioth/debian/backports/sarge
>  remotes/alioth/master
>  remotes/alioth/pristine-tar
>  remotes/alioth/upstream
>  remotes/alioth/wheezy
>  remotes/alioth/wheezy-2
>
>The naming is a little confusing here, I suggest to follow
>"backports/squeeze" and rename "wheezy-2" branch 
>to "backports/wheezy". For the older "debian/backports"
>branches, we can rename too. (perhaps not too necessary.)
>
>
>(The "wheezy" branch was created, in hope to upload to 7.x
>updates of wheezy, not the backport. Therefore, I suppose 
>it can only contain some fixes on 7.0.27. I'm not sure if there's 
>still any motivation for it, though.)
>
>
>By the way, after I fetched with --tags, hundreds of 
>client_release_x.y.z tags come up, taking up more than
>20MB of space. I wonder if they are really useful. Also,
>you may notice that they come from the boinc.git repo,
>not the current upstream boinc-v2.git repo, although the
>files are the same, the commit hashes are totally different.
>

How do you suggest to move on for this?

The problem is that every backport is the testing version with a commit line on debian changelog.

the next backport (If I read correctly the documentation) shouldn't have the changelog line for the previous backport, but should again start from testing, this is why I just push tags instead of creating a new branch everytime.

Feel free to tell me the appropriate way, anyway with a git checkout debian/7.2.47+dfsg-3_bpo70 or whatever you have your history without any problem, and since backports doesn't live, but they are only "one shot" pushes I don't know how can we benefit from a branch creation (since everytime we start from master)

Anyway as usual comments are appreciated :)

Bests,

G.

>
>Cheers,
>
>
>Yixuan
>
>