Hi On 14 July 2012 21:59, Julien Puydt <julien.pu...@laposte.net> wrote:
> Le 14/07/2012 21:47, Jan Groenewald a écrit : > >> On 14 July 2012 21:26, Julien Puydt <julien.pu...@laposte.net >> <mailto:julien.puydt@laposte.**net <julien.pu...@laposte.net>>> wrote: >> >> Le 14/07/2012 21:22, Jan Groenewald a écrit : >> > (many things) >> >> I downloaded a buildlog and had a look, but there was nothing >> interesting to see :-/ >> >> I can do two things when time allows. >> 1. debuild -b locally, and >> > > Uh... you mean you haven't even tested if your package built locally > before sending it afar!? > I generally do. For this, I wanted to see the exact launchpad behaviour. This package takes 4.5 hours to build, so the turnaround time of doing it twice each time is limiting. >From the package directory, just "dpkg-buildpackage -us -uc" should be > enough. It only assumes that (1) you are in package-3.14/ (2) upstream's > sources are in ../package_3.14.orig.tar.gz. Or even in /debian. Perhaps even anywhere in the tree. > 2. learn to use pbuilder and I've heard there is a launchpad-like > >> pbuilder mode. >> > > I don't know if there's a launchpad-like pbuilder mode, but using it is > trivial: > - first, run "pbuilder --create" to initialize it ; > - then any time you have a package you'd like to test : "pbuilder --build > <name of the dsc>" > Bot those require sudo here. Why? Regards, Jan -- .~. /V\ Jan Groenewald /( )\ www.aims.ac.za ^^-^^ -- -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
