On Sat, Mar 28, 2009 at 10:14:38AM +0100, Gerfried Fuchs wrote:
> * Gerfried Fuchs <rho...@deb.at> [2009-03-27 10:59:29 CET]:
> > * Steve M. Robbins <st...@sumost.ca> [2009-03-23 20:57:49 CET]:
> > > The script is used to create undecorated symlinks to libraries built
> > > with the "default" python version.  Right now the package builds
> > > libraries for Python 2.4 and Python 2.5.  I don't have libraries for
> > > any other python version.  One way I can handle "any python version"
> > > is to simply not provide symlinks if Boost.Python doesn't have
> > > libararies for the default version of python doesn't have.
> > > 
> > > Once Python 2.6 is in sid, I'll update boost to build libraries for
> > > it.
> > 
> >  ... so for the time being the boost (and all its dependencies) are
> > blocked from transitioning to squeeze because of these bug reports. Is
> > that really the intended behavior, how long is it expected to take to
> > get solved for the good?
> 
>  Looked into it again - it only seems to affect boost1.37 badly. The
> version it was reported for boost1.35 is only in experimental, and the
> version it was reported for boost is already in testing.
> 
>  My suggestion is to reduce the severity for the bugreport against
> boost1.37 for the time being so that it can transition to testing and
> won't hold up other packages along that way until a proper solution has
> been worked out.

Since you raised this, Rhonda, I have fixed the problem in all three
versions and am in the process of building and uploading new packages.

I should be done in a few hours.

-Steve

Attachment: signature.asc
Description: Digital signature

Reply via email to