On Tue, 31 Jan 2017 at 18:27:46 +0100, Emilio Pozuelo Monfort wrote:
> soprano build-deps on libraptor1-dev but is actually using and linking against
> raptor2, so the build-dep can probably be changed to libraptor2-dev safely.
I have opened an 'important' bug with the obvious 1-character patch.
It builds successfully, although I don't know how to smoke-test the
resulting binaries. The bug should shortly appear as a blocker for this one.
> flickcurl seems to be using raptor2 as well (build-deps on libraptor2-dev,
> libflickcurl0 depends on libraptor2-0), but libflickcurl-dev still depends on
> libraptor1-dev, probably a mistake from the raptor1 -> raptor2 port. I assume
> that dependency can be safely changed to libraptor2-dev.
I have opened a 'serious' bug with the obvious 1-character patch
(severity justified by the dependencies being insufficient to link
a trivial executable to the library using pkg-config, which I have
verified is fixed by my change; probably also insufficient to link against
it statically by using flickcurl-config, but I didn't test that). The
bug should shortly appear as a blocker for this one.
If those patches are uploaded soon and the maintainer doesn't have any
particular objection, I am inclined to ask for src:raptor to be removed
from unstable rather than just testing, so we don't have to care about
it again in 2 years.
S
