[ Ken VanDine ]
* Multi-Arch: same libraries must not depend on run-time application,.
since this breaks cross-compilation. Furthermore, circular
dependencies are never needed: upstart-app-launch depends on
libupstart-app-launch2, which depends on upstart-app-launch. It's
the same reasoning why we do not make libgtk-3.0 depend on epiphany
webbrowser, even though gtk has functions to open URL in a
webbrowser. And in a multi-arch world libgtk-3.0 would never know
which architecture your web-browser is, it could be any. Libraries
should only ever depend on other linked shared libraries.
[ Ted Gould ]
* Make sure that 'package' sticks around until we setup the
environment. (LP: #1260079)
* Improve readability of the coverage report.
[ Didier Roche ]
* revert the archictecture specific list: britney doesn't use those
This bug was fixed in the package upstart-app-launch - 0.3+14. 04.20131218- 0ubuntu1
--------------- 04.20131218- 0ubuntu1) trusty; urgency=low
upstart-app-launch (0.3+14.
[ Ken VanDine ] app-launch2, which depends on upstart-app-launch. It's
* Multi-Arch: same libraries must not depend on run-time application,.
since this breaks cross-compilation. Furthermore, circular
dependencies are never needed: upstart-app-launch depends on
libupstart-
the same reasoning why we do not make libgtk-3.0 depend on epiphany
webbrowser, even though gtk has functions to open URL in a
webbrowser. And in a multi-arch world libgtk-3.0 would never know
which architecture your web-browser is, it could be any. Libraries
should only ever depend on other linked shared libraries.
[ Ted Gould ]
* Make sure that 'package' sticks around until we setup the
environment. (LP: #1260079)
* Improve readability of the coverage report.
[ Didier Roche ]
* revert the archictecture specific list: britney doesn't use those
[ Ubuntu daily release ]
* Automatic snapshot from revision 100
-- Ubuntu daily release <email address hidden> Wed, 18 Dec 2013 19:40:19 +0000