Bug#473973: [pkg-boost-devel] Bug#473973: libboost-python-dev: rdeps?fails?to built - python packaging seems weird

2008-04-04 Thread Steve M. Robbins
On Wed, Apr 02, 2008 at 10:51:35PM +0200, Sune Vuorela wrote: > I think you *must* depend on at least one python -dev thingie. Do you need to > manually change stuff to support a new python version ? > But can't python-dev | python2.4-dev | python2.5-dev be appropriate ? Yes, I think you are rig

Bug#473973: [pkg-boost-devel] Bug#473973: libboost-python-dev: rdeps fails?to built - python packaging seems weird

2008-04-03 Thread Josselin Mouette
On mer, 2008-04-02 at 12:04 -0500, Steve M. Robbins wrote: > The sequence shown in the build log indicates that no python-dev > package is installed at all. This is due to another change made to > support multiple python runtimes. The libboost-python-dev package > used to depend on python-dev. N

Bug#473973: [pkg-boost-devel] Bug#473973: libboost-python-dev: rdeps fails to built - python packaging seems weird

2008-04-02 Thread Ben Burton
Hi Sune, > kdeedu build doesn't fail by itself if it isn't found as it is only optional, > but we test afterwards if it is actually build. As an aside, what I've done with regina-normal (which also uses boost.python) is make debian/rules check the config.log immediately after configure finishes

Bug#473973: [pkg-boost-devel] Bug#473973: libboost-python-dev: rdeps fails?to built - python packaging seems weird

2008-04-02 Thread Sune Vuorela
[My knowledge of python is nearly zero - and I don't plan to subscribe to -python] On Wednesday 02 April 2008, Steve M. Robbins wrote: > You might want to consider doing so; this allows you to be > clear as to which version of python you support. Or, indeed, > build support for both 2.4 and 2.

Bug#473973: [pkg-boost-devel] Bug#473973: libboost-python-dev: rdeps fails?to built - python packaging seems weird

2008-04-02 Thread Steve M. Robbins
For the debian-python readers just joining in: the recent modification of Boost to support multiple Python runtimes has some unintended consequences; see bug #473973. Below are some questions for your consideration. On Wed, Apr 02, 2008 at 06:11:34PM +0200, Sune Vuorela wrote: > If I ask specif

Bug#473973: [pkg-boost-devel] Bug#473973: libboost-python-dev: rdeps fails to built - python packaging seems weird

2008-04-02 Thread Sune Vuorela
On Wednesday 02 April 2008, Steve M. Robbins wrote: > On Wed, Apr 02, 2008 at 02:21:17PM +0200, Sune Vuorela wrote: > > Justification: packaging on crack > > That's a little harsh considering the limited analysis you presented. A little more analysis. If I ask specifically for -lboost_python-py24

Bug#473973: [pkg-boost-devel] Bug#473973: libboost-python-dev: rdeps fails to built - python packaging seems weird

2008-04-02 Thread Steve M. Robbins
On Wed, Apr 02, 2008 at 02:21:17PM +0200, Sune Vuorela wrote: > Justification: packaging on crack That's a little harsh considering the limited analysis you presented. > Looking at the newer boost-python-dev packages, I see tihs: > > $ dpkg -L libboost-python-dev | grep /usr/lib [ ... ] >

Bug#473973: libboost-python-dev: rdeps fails to built - python packaging seems weird

2008-04-02 Thread Sune Vuorela
Package: libboost-python-dev Version: 1.34.1-8 Severity: serious Justification: packaging on crack Hi! Looking at the newer boost-python-dev packages, I see tihs: $ dpkg -L libboost-python-dev | grep /usr/lib /usr/lib /usr/lib/libboost_python-gcc42-1_34_1-py24.a /usr/lib/libboost_python-gcc42-1_