Bug#657314: [Pkg-samba-maint] Bug#657314: Bug#657314: Bug#657314: unstable: 2:3.6.1-3 fails to build due to incorrect python-ldb bindings

2012-05-09 Thread Christian PERRIER
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


Bug#657314: [Pkg-samba-maint] Bug#657314: Bug#657314: Bug#657314: unstable: 2:3.6.1-3 fails to build due to incorrect python-ldb bindings

2012-05-09 Thread Jelmer Vernooij
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


Bug#657314: [Pkg-samba-maint] Bug#657314: Bug#657314: Bug#657314: unstable: 2:3.6.1-3 fails to build due to incorrect python-ldb bindings

2012-05-09 Thread Christian PERRIER
Quoting Jelmer Vernooij (jel...@canonical.com):

 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).


I just committed such fix.




signature.asc
Description: Digital signature


Bug#657314: [Pkg-samba-maint] Bug#657314: Bug#657314: Bug#657314: unstable: 2:3.6.1-3 fails to build due to incorrect python-ldb bindings

2012-01-27 Thread Steve Langasek
On Fri, Jan 27, 2012 at 07:21:26PM +0100, Christian PERRIER wrote:
 Quoting John David Anglin (dave.ang...@bell.net):
  On 26-Jan-12, at 9:22 AM, Jelmer Vernooij wrote:

  ldb is also included in the Samba source tree, so a dependency isn't
  necessary. Can you reproduce this *without* any ldb libraries
  installed?

  I finally had a successful build.  In addition to removing the ldb
  libraries,
  I had to remove the python-talloc packages.  I think the problem is the

 I'm tempted to close this bug as this is not really related to the
 Debian package (that currently builds fine).

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.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature


Bug#657314: [Pkg-samba-maint] Bug#657314: Bug#657314: Bug#657314: unstable: 2:3.6.1-3 fails to build due to incorrect python-ldb bindings

2012-01-27 Thread John David Anglin

On 1/27/2012 1:54 PM, Steve Langasek wrote:

On Fri, Jan 27, 2012 at 07:21:26PM +0100, Christian PERRIER wrote:

Quoting John David Anglin (dave.ang...@bell.net):

On 26-Jan-12, at 9:22 AM, Jelmer Vernooij wrote:

ldb is also included in the Samba source tree, so a dependency isn't
necessary. Can you reproduce this *without* any ldb libraries
installed?

I finally had a successful build.  In addition to removing the ldb
libraries,
I had to remove the python-talloc packages.  I think the problem is the

I'm tempted to close this bug as this is not really related to the
Debian package (that currently builds fine).

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.

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.

It shouldn't be necessary to manually supply the missing rfc's.

Dave

--
John David Anglindave.ang...@bell.net




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org