Re: DEP8 tests using the built package source

2014-03-24 Thread Martin Pitt
Hello Stephen, Stephen Kitt [2014-03-25 0:45 +0100]: > > Recent versions of autopkgtest now ship the new > > /usr/share/doc/autopkgtest/README.running-tests.gz which I hope > > explains the use cases and how to run them. > > It does explain the various use cases, but I found auto-package-testing

Re: DEP8 tests using the built package source

2014-03-24 Thread Stephen Kitt
Hi, On Thu, 20 Mar 2014 15:10:23 +, Ian Jackson wrote: > Stephen Kitt writes ("Re: DEP8 tests using the built package source"): > > (Hi Ian, I'm adding you to the discussion since I'm talking about changes > > to DEP8. I've snipped the exchanges but I hope you can get the gist of it > > witho

Re: DEP8 tests using the built package source

2014-03-24 Thread Stephen Kitt
Hi Andreas, On Thu, 20 Mar 2014 08:35:33 +0100, Andreas Tille wrote: > On Wed, Mar 19, 2014 at 11:54:03PM +0100, Stephen Kitt wrote: > > > Moreover I observed another issue with autopkgtest which is quite > > > astonishing to me: In bug #741274 it was reported that the autopkgtest > > > would fa

Re: DEP8 tests using the built package source

2014-03-24 Thread Stephen Kitt
On Thu, 20 Mar 2014 08:24:15 +0100, Martin Pitt wrote: > Stephen Kitt [2014-03-19 23:54 +0100]: > Well, it depends what you want to do. In CI we *always* want to test > the packages from the actual archive of course. But as a package > maintainer you may want to (and should) run your autopkgtest f

Re: RFS: cl-launch (updated package)

2014-03-24 Thread Christoph Egger
Hi! Faré writes: > - dget > http://mentors.debian.net/debian/pool/main/c/cl-launch/cl-launch_4.0.3-1.dsc On the way Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.deb

Re: library linking, missing libB.so

2014-03-24 Thread Mathieu Malaterre
On Mon, Mar 24, 2014 at 11:18 AM, Nico Schlömer wrote: > Thanks for the hints! > >> If you have access to upstream source, simply set the target properties with: >> set_properties(target LINK_INTERFACE_LIBRARIES "") > > I might. The culprit right now are CMake property settings of the kind > ``` >

Re: library linking, missing libB.so

2014-03-24 Thread Nico Schlömer
Thanks for the hints! > If you have access to upstream source, simply set the target properties with: > set_properties(target LINK_INTERFACE_LIBRARIES "") I might. The culprit right now are CMake property settings of the kind ``` set_target_properties(teuchosnumerics PROPERTIES IMPORTED_LINK_IN

Re: library linking, missing libB.so

2014-03-24 Thread Mathieu Malaterre
On Sat, Mar 22, 2014 at 1:31 PM, Nico Schlömer wrote: >> No, the 'linker' does not complain. > > You're right, it is the CMake dependency checker. The linking is all > right, but there's something amiss with the CMake export files. I'll > investigate. I think you should find online reference with