Am 09/05/12 16:42, schrieb Christian PERRIER:Am 09/05/12 15:21, schrieb "L. Alberto Giménez": > Hi, > > Regarding http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652848 > I'm thinking about buying a Line6 POD device, and I was wondering if I > could make it work in Linux. > > Do you know if your package will work with newer POD devices? I mean, > are they compatible? If true, I might help you maintaining the package > since I could use it to interface my computer with the POD. > > > Best regards! >
> Quoting John David Anglin (dave.ang...@bell.net): > >>> If the package fails to build due to other unrelated packages being >>> installed in the build environment, that's still a bug, just a >>> lower-priority one. > Well, the original message was showing a build that's different from > the build we're really using when building the package > Waf: Entering directory `/home/dave/debian/samba/samba-3.6.1/bin' > 'reconfigure' finished successfully (13.520s) > cd .. && WAF_MAKE=1 buildtools/bin/waf --targets=smbtorture > Waf: Entering directory `/home/dave/debian/samba/samba-3.6.1/bin' > > >> I would guess that there is a problem with include paths. The build >> should be picking >> up its header files, and not the system headers. From what I could >> see on the net, >> there have been incompatible changes in the python bindings for both >> the ldb and talloc >> source packages in recent versions. >> >> Possibly the simplest solution is to just add the conflicts. > Certainly, it probably doesn't hurt to BUild-Conflicts with > python-talloc and python-ldb (that are, from my understanding, the > packages that create the problem). It should just be python-ldb and python-ldb-dev. The helper library for the python ldb module didn't have a stable API until recently (1.1.4 I think). Cheers, Jelmer
signature.asc
Description: OpenPGP digital signature
