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).
signature.asc
Description: Digital signature
