Multiarch and architecture specific headers

another solution to deal with this bug? Thanks, -- Thomas Moulard（ムラー　トマ） CNRS-AIST JRL (Joint Robotics Laboratory), UMI3218/CRT, Tsukuba, Japan http://thomas.moulard.net | GPG Key Id: 516FC68F31496D58 Add me on LinkedIn: http://www.linkedin.com/in/moulard -- To UNSUBSCRIBE, email to debian-mentors

Re: Multiarch and architecture specific headers

On Tue, May 14, 2013 at 9:56 AM, Russ Allbery wrote: > Thomas Moulard writes: > >> A package I maintain contains a configuration header (vpConfig.h) which >> differ depending on the architecture we are (here the dependencies are >> not the same on i386 and powerpc

How to handle a package triggering ice or segv during build?

=2.7.0-4&stamp=1371023299 [3] https://buildd.debian.org/status/fetch.php?pkg=visp&arch=sparc&ver=2.7.0-2&stamp=1367014144 [4] https://buildd.debian.org/status/fetch.php?pkg=visp&arch=armel&ver=2.7.0-4&stamp=1371101186 Best, -- Thomas Moulard（ムラー　トマ） -- To UNSUB

Re: How to handle a package triggering ice or segv during build?

On Mon, Jun 17, 2013 at 2:31 AM, Jakub Wilk wrote: > * Thomas Moulard , 2013-06-14, 15:50: > >> the ViSP[1] software I maintain is causing GCC[2,3] and Doxygen[4] to >> crash on some platforms. > > > Why does it build documentation on the buildds? You put documentati

Re: How to handle a package triggering ice or segv during build?

On Mon, Jun 17, 2013 at 1:34 PM, Paul Wise wrote: > On Mon, Jun 17, 2013 at 8:53 AM, Thomas Moulard wrote: > >> Actually I think so too but I am a bit reluctant to process the >> Doxygen documentation locally >> then copy it into the package (mainly because it will easy t

How to handle a package requiring external test data for its test suite?

requiring this dataset. Note: the dataset is mainly composed of video sequences stored as pgm images. [1] http://packages.qa.debian.org/v/visp.html [2] http://lists.debian.org/debian-mentors/2013/06/msg00140.html Thanks, -- Thomas Moulard -- To UNSUBSCRIBE, email to debian-mentors-requ

Re: How to handle a package requiring external test data for its test suite?

into a new page (visp-image-data) - I added the dependency and now the test suite is running fine - I added a autopkgtest to check that a simple program can be compiled after installing the packages. However I am not aware of a way to run a CMake test suite against installed software so I let

What is the correct fix for this piuparts related issue?

and libvisp2.9 provides the same file which is obviously an issue if one tries to install the two packages side by side. In this particular case, should libvisp2.9 declare a break+replace on libvisp2.8 or is there another better solution to solve this issue? Thanks, -- Thomas Moulard -- To UNSUBS