[pkg-boost-devel] Upload of Boost 1.38

[Steve M. Robbins]

Hello again, Adeodato,

I'm interested in removing some older Boost packages from the
archive, specifically 1.34.1 (source package boost).


On Fri, Mar 20, 2009 at 09:13:34PM +0100, Adeodato Sim?? wrote:

> > Clearly, the strategies will depend on how much breakage is
> > encountered in a typical Boost relase.  As indicated, I don't have a
> > good handle on this.  I think that your proposal of boost-defaults --
> > especially the strategy of locally trying to build rdeps -- will help
> > to answer this question in the context of Debian packages.  So that
> > seems to me to be a good way forward.
> 
> Indeed, the ability to rebuild against a new Boost without source
> changes is the critical component of all this. This not only means
> API-wise, but (I guess) about packages using appropriate compiler/linker
> calls so that by that build-depending on unversioned package names,
> they???ll get linked against that version, without it being hard-coded in
> their build scripts.
> 
> I suggest that we get started by introducing boost1.38 in unstable, and
> once it has migrated to testing, start the migration work. This means:

OK, we have boost1.38 in unstable and in testing.


>   * an initial upload of boost-defaults providing versionless -dev
>     package names pointing at the 1.38 packages

Also done.

>   * a mass bug filing for packages build-depending on versioned packages
>     to build-depend on the un-versioned ones instead

Not yet done.

>   * an automatic rebuild of those packages already build-depending on
>     the un-versioned ones (from Boost 1.34), and file bugs for those
>     that fail

I used rebuildd locally to build all such packages (99 by my
reckoning) and found 69 succeed, while 30 fail to build.  I have just
started going through the log files and have filed bugs for two of
those.

Do you suggest we remove boost now or wait for the 30 failures to be
fixed?


> I???m foreseeing this won???t be a cup of tea, but it???s something that has
> to be done just once. With a bit of luck, we???ll get rid of at least
> boost 1.34 and 1.35, and ideally 1.37 as well.
> 
> Then, when Boost 1.39 comes along, please contact us again, and we???ll
> figure out how to proceed.

Boost 1.39 is already out ... :-)


Cheers,
-Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-boost-devel/attachments/20090522/bcd49ae8/attachment.pgp>