Sorry, spoke too soon. I noted the missing dependencies there. Once installed, it gets further and then fails at compile with [javac] phyutility/src/jebl/gui/trees/treeviewer_dev/TreePane.java:495: error: reference to Painter is ambiguous, both interface javax.swing.Painter in javax.swing and interface jebl.gui.trees.treeviewer_dev.painters.Painter in jebl.gui.trees.treeviewer_dev.painters match
BUNCH OF STUFF AND THEN.... BUILD FAILED phyutility/build.xml:7: Compile failed; see the compiler error output for details. Total time: 8 seconds make[1]: *** [override_dh_auto_build] Error 1 make[1]: Leaving directory `phyutility' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 debuild: fatal error at line 1364: dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed gbp:error: Couldn't run 'debuild -i -I': debuild -i -I returned 29 Does that look more like it? If so, seems like the solution is me fixing the phyutility code and then bringing it back in, correct? (At least since I am the developer of phyutility this seems like the easiest thing). Take care, Stephen On Tue, Mar 4, 2014 at 7:42 PM, Stephen Smith <black...@gmail.com> wrote: > Hi Andreas > > OK. When I do git-buildpackage (no arguments) in the directory I have been > working in, I get > dpkg-buildpackage -rfakeroot -D -us -uc -i -I > dpkg-buildpackage: source package phyutility > dpkg-buildpackage: source version 2.6-1 > dpkg-buildpackage: source distribution UNRELEASED > dpkg-buildpackage: source changed by Andreas Tille <ti...@debian.org> > dpkg-source -i -I --before-build phyutility > dpkg-buildpackage: host architecture amd64 > dpkg-checkbuilddeps: Unmet build dependencies: javahelper default-jdk > libjebl2-java > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; > aborting > dpkg-buildpackage: warning: (Use -d flag to override.) > debuild: fatal error at line 1364: > dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed > gbp:error: Couldn't run 'debuild -i -I': debuild -i -I returned 29 > > Is this the error you were getting? I am looking at the git-buildpackage > documentation but am having a little difficulty determining when the > arguments are necessary (despite the fact that I understand arguments). > > Take care, > Stephen > > > On Tue, Mar 4, 2014 at 1:57 PM, Andreas Tille <andr...@an3as.eu> wrote: > >> Hi Stephen, >> >> On Tue, Mar 04, 2014 at 01:17:17PM -0500, Stephen Smith wrote: >> > All sounds good. OK, I have done an initial commit so you can check out >> > where I am at. >> >> I was really curious where you are at and thus I took the freedom to do >> two commits: >> >> 1. Adapt changelog version to the injected upstream version >> (otherwise git-buildpackage would not have worked). >> 2. Use default-jdk (instead of an outdated JDK) >> >> So the build at least starts but runs into an error you most probably >> will be able to reproduce (hopefully). >> >> Please confirm thyt you can run git-buildpackage and the build problem >> can be reproduced at your side. >> >> Kind regards >> >> Andreas. >> >> -- >> http://fam-tille.de >> >> >> -- >> To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org >> with a subject of "unsubscribe". Trouble? Contact >> listmas...@lists.debian.org >> Archive: https://lists.debian.org/20140304185716.gc16...@an3as.eu >> >> >
