[pkg-boost-devel] Bug#426871: Bug#426871 closed by Domenico Andreoli <cavok at debian.org> (Bug#426871: fixed in boost 1.34.0-3)

[Domenico Andreoli]

On Tue, Jun 26, 2007 at 12:05:49PM +0200, Michal ??iha?? wrote:
> Hi

hi,

> On Tue, 26 Jun 2007 11:55:40 +0200
> Domenico Andreoli <cavok at debian.org> wrote:
> 
> > say that i changed my mind after the announce of the imminent transition
> > to python 2.5 as default :) anyway those -2 and -3 were already in
> > the queue...
> 
> The only question is how imminent it really it, based on experiences
> from previous transitions, it took always longer than expected ;-).

boost is not a light thing to turn from a compiler/python version to
another. it always passes from the NEW queue (ftp-masters are surely
starting to hate me) and a rebuild of all its reverse dependant packages.

so i try to foresee the Next Thing and prepare boost for it in
experimental. sometimes it takes weeks to pass throught the NEW queue,
sometimes (like yesterday) it takes hours.

> Well I'd really like to have a solution for this. Current tagpy is
> uninstallable because old boost libraries have been removed, it FTBFS
> because something changed in boost what needs minor change in sources.
> However if I upload this version to fix FTBFS, I will get version which
> will not work with default python, what is again bad as it is against
> Python policy and breaks applications using it.

i'd say to build it with pytohn 2.5. it will installable, it will build
from source and it will ok with the next default python version.

you fix 2 RC and you get 1 RC. not the best, but something better.. :}

moreover, the only rdepend of tagpy is yours and it is an application.
so it should not be that great tragedy to make it use python 2.5 in
advance respect the whole archive for some time.

ciao,
domenico

-----[ Domenico Andreoli, aka cavok
 --[ http://www.dandreoli.com/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50