[Neurodebian-devel] OpenSesame 0.27

[Sebastiaan Mathot]

Hi guys,

Well, here I am again! OpenSesame 0.27 is about to see daylight, and I was 
hoping to get this update into NeuroDebian quickly. So here's where 	I am now:

- The current debian branch of OpenSesame builds fine on the NeuroDebian build 
farm, which I have installed per the instructions on your blog.
- mentors.debian.net does not give any red flags: 
http://mentors.debian.net/package/opensesame
- I checked debian/copying, and I believe it is accurate and complete.

Please let me know where we go from here, and whether there is something more 
that I should do.

Cheers!
Sebastiaan

On Monday, August 13, 2012 05:26:36 PM Yaroslav Halchenko wrote:
> Hi Sebastiaan,
> 
> Great to hear/see the progress!
> 
> On Sat, 11 Aug 2012, Sebastiaan Mathot wrote:
> >    <[3]https://github.com/smathot/OpenSesame/tree/playground/debian>. I
> >    also
> 
> why not just debian branch?
> 
> btw do not forget a Vcs-Browser field for debian/control
> 
> >    uploaded the packaging to [4]mentors.debian.net
> >    <[5]http://mentors.debian.net/package/opensesame>.
> 
> good!
> 
> >    In general, it works encouragingly well and it was not nearly as
> >    difficult
> >    as I imagined.
> 
> ;-)
> 
> >    opensesame_0.27~pre2-1~nd60+1_amd64.build       FAILED  0:00.02 real,
> >    0.00
> >    user, 0.01 sys, 0 out
> >    opensesame_0.27~pre2-1~nd70+1_amd64.build       OK      2:43.49 real,
> >    25.47 user, 9.24 sys, 873744 out
> >    opensesame_0.27~pre2-1~nd+1_amd64.build         OK      2:49.33 real,
> >    25.01 user, 9.34 sys, 881024 out
> >    opensesame_0.27~pre2-1~nd10.04+1_amd64.build    OK      2:30.26 real,
> >    31.98 user, 113.39 sys, 469768 out
> >    opensesame_0.27~pre2-1~nd10.10+1_amd64.build    OK      4:03.16 real,
> >    18.50 user, 17.33 sys, 565504 out
> >    opensesame_0.27~pre2-1~nd11.04+1_amd64.build    FAILED  4:35.01 real,
> >    25.46 user, 14.37 sys, 619256 out
> >    opensesame_0.27~pre2-1~nd11.10+1_amd64.build    OK      2:48.55 real,
> >    25.24 user, 15.69 sys, 801536 out
> >    opensesame_0.27~pre2-1~nd12.04+1_amd64.build    OK      2:44.52 real,
> >    23.71 user, 14.83 sys, 734120 out
> >    For nd60, it is difficult to say what goes wrong, because there is
> >    no .build file to check for errors (it's apparently not generated).
> 
> yeah -- difficult to say what was wrong especially since it built just
> 
> fine for me ;):
> > cat summary.build
> 
> opensesame_0.27~pre2-1_amd64.build      OK      3:53.10 real, 173.15 user,
> 130.78 sys, 947704 out opensesame_0.27~pre2-1~nd60+1_amd64.build       OK  
>    3:12.35 real, 157.32 user, 110.93 sys, 624728 out
> opensesame_0.27~pre2-1~nd70+1_amd64.build       OK      3:31.60 real,
> 175.39 user, 125.69 sys, 903576 out opensesame_0.27~pre2-1~nd+1_amd64.build
> OK      3:30.07 real, 170.64 user, 130.54 sys, 918912 out
> opensesame_0.27~pre2-1~nd10.10+1_amd64.build    OK      6:58.22 real,
> 164.17 user, 249.91 sys, 650784 out
> opensesame_0.27~pre2-1~nd10.04+1_amd64.build    OK      5:12.10 real,
> 190.08 user, 354.11 sys, 529792 out
> opensesame_0.27~pre2-1~nd11.04+1_amd64.build    FAILED  2:58.96 real,
> 149.66 user, 98.73 sys, 642896 out
> opensesame_0.27~pre2-1~nd11.10+1_amd64.build    OK      3:30.40 real,
> 181.91 user, 122.58 sys, 828824 out
> opensesame_0.27~pre2-1~nd12.04+1_amd64.build    OK      3:20.90 real,
> 175.87 user, 117.57 sys, 769576 out
> > For
> > 
> >    nd11.04, there is a .build file, and it indicates that the build fails,
> >    because PyQt4.Qsci isn't available (from python-qscintilla2). This is
> >    strange, because it is.
> > 
> > ...
> > 
> >    Do you guys have any clue what the problem(s) might be? Thanks for all
> >    your help!
> 
> 2 possible resolutions: ignore and stay without 11.04 pkg (people have
> jumped over to the next release probably by now), or fix it by
> troubleshooting WTF... so you would need smth like:
> 
> sudo nd_build nd+ubuntu natty amd64 *~nd11.04*.dsc
> --hookdir=/home/neurodebian/neurodebian/tools/hooks
> 
> where you should adjust trailing path to the location where you checked out
> neurodebian repository (I do not think we shipped this "get into shell upon
> failure" pbuilder hook).  So, when you run it this way you end up in that
> minimalistic chroot where build has failed so you could figure it all out (I
> would be interested to know too).
-- 
http://www.cogsci.nl/smathot