Hi Paul, On Mon, Jan 26, 2015 at 10:19:55AM -0500, Paul Novotny wrote: > On Fri, 2015-01-23 at 16:24 +0100, Andreas Tille wrote: > > > > I have not yet tested this approach and your mileage may vary but you > > might like to send the patches in a wishlist bug report to the Debian > > package. On one hand it might solve your current build problem very > > easily and on the other hand it might convince upstream if a major > > distribution has the patches. > > Upstream yaml-cpp just merged the patches, and it sounds like they will > release a new version in the next week or so. So, fingers crossed, I can > remove yaml-cpp from OpenSurgSim source and add it as a build-depends as > you requested.
Cool! > Should I get in touch with the maintainer of Debian > yaml-cpp to see if I can help getting the new version packaged? This sounds sensible. Considering the old debhelper and Standards-Version $ apt-cache showsrc yaml-cpp Package: yaml-cpp Binary: libyaml-cpp0.5, libyaml-cpp-dev Version: 0.5.1-1 Maintainer: Lifeng Sun <[email protected]> Build-Depends: debhelper (>= 7.0.50~), cmake, libboost-dev Architecture: any Standards-Version: 3.9.4 it was not maintained for some time. Offering help (perhaps inside collab-maint VCS) would probably enhance chances to get things happening more quickly. > Also, there are a couple of more packaging questions: > > - The policy mentions adding "Testsuite" field to the debian/control > file. OpenSurgSim uses CTest to run our Google Test unit tests. The > tests seems to be running correctly during the build. But, what do I > need to put in this field? The testsuite field can stay empty but it would be great to run also autopkgtest (in debian/tests). There is a difference between tests run at build time and testing ready built binaries fetched from Debian mirror. We should provide both if possible. > - README.test and README.source, I am a little confused as to what goes > here. Is there an example I can look at? We have several examples in Debian Med repository. You might also try codesearch - here is a quite naive example that probably could be enhanced: http://codesearch.debian.net/results/debian%2Ftests%2Fcontrol/page_0 > - debian/upstream (or debian/upstream/metadata). I would like to add > this as well. Again, do you know of a good example I can follow? I created a package template (see Debian Med team policy) which also contains a boilerplate: http://anonscm.debian.org/viewvc/debian-med/trunk/package_template/upstream/metadata?view=markup Hope this helps Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
