Ubuntu CI Services

Build-dependency on libboost-all-dev is not allowed

Bug #1252860 reported by Dimitri John Ledkov on 2013-11-19

This bug affects 1 person

	Status	Importance	Assigned to
Ubuntu CI Services	Confirmed	Undecided	Unassigned
Unity System Compositor	Fix Released	Undecided	Robert Bruce Park
unity-system-compositor (Ubuntu)	Fix Released	High	Dimitri John Ledkov

Bug Description

boost package in ubuntu is split into two packages: one is in main and has most of the libraries, another one in universe of 4 components that depend on "mpi" parallel processing.

libboost-all-dev is build out of universe to provide compatibility for the rest of the package that we get from debian.

Because of the split, the mpi source package has tight dependency on the main package, such that the two are always kept in sync.

The net result is that all packages should depend on individual component -dev packages, instead of libboost-all-dev to:
1) avoid FTBFS if the two boosts are out of sync from each other
2) to be eligible for main inclusion
3) to enable cross-compilation (libboost-all-dev is not multiarch-all, due to mpi components)

Therefore "libboost-all-dev" build-dependency should be banned for our packages.

This is not the first time, where this is spotted.

Tags:

Related branches

lp://staging/~robru/unity-system-compositor/drop-libboost-all-dev

Merged into lp://staging/unity-system-compositor at revision 98

PS Jenkins bot (community): Approve (continuous-integration) on 2013-11-19

Ken VanDine: Approve on 2013-11-19

Michael Terry (community): Approve on 2013-11-19

Revision history for this message

Dimitri John Ledkov (xnox) wrote on 2013-11-19:

Also it's so much faster to install just the required boost components, instead of all 30 of them.

Changed in ubuntu-ci-services-itself:
status:	New → Confirmed
Changed in unity-system-compositor (Ubuntu):
status:	New → Confirmed
importance:	Undecided → High
assignee:	nobody → Dmitrijs Ledkovs (xnox)
Changed in unity-system-compositor:
status:	New → Confirmed
summary:	- Must fail any packages that build-depend on libboost-all-dev + Build-dependency on libboost-all-dev is not allowed

Robert Bruce Park (robru) on 2013-11-19

Changed in unity-system-compositor:
status:	Confirmed → Fix Committed
assignee:	nobody → Robert Bruce Park (robru)

Francis Ginther (fginther) on 2013-11-21

tags:

added: new-ci upstream-merger

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-11-21:

unity-system-compositor (0.0.2+14.04.20131120.1-0ubuntu1) trusty; urgency=low

  [ Michael Terry ]
  * Bump version to 0.0.2, so we can reference it in debian/control
  * Default to a public file socket, if one is used.
  * Clean some lintian warnings.
  * Add DBus interface for com.canonical.Unity.Screen to USC.

[ Alan Griffiths ]
* Use the Mir libraries detected by pkg_check_modules

  [ Timo Jyrinki ]
  * Clean the moved conffile when upgrading from previous version. (LP:
    #1253008). (LP: #1253008)

[ Kevin Gunn ]
* mir server abi and api broke, updating dependency to deb 0.1.1

[ Robert Bruce Park ]
* Stop depending on libboost-all-dev, it is verboten.

[ Ubuntu daily release ]
* Automatic snapshot from revision 101
-- Ubuntu daily release <email address hidden> Wed, 20 Nov 2013 11:17:20 +0000

Changed in unity-system-compositor (Ubuntu):
status:	Confirmed → Fix Released
Changed in unity-system-compositor:
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.