micro release exception for bzr

[Martin Pitt]

Hello Martin,

Martin Pool [2010-11-29 19:47 +1100]:
> The good news, with regard to our SRU MRE conditions, is that the test
> suite now passes cleanly when run both during a build, and when run
> from an installed package.  We've checked this for the specific source
> packaged in 2.2.2.

Thanks a bunch for this!

> However, the bad news is that we can't really meet this MRE condition
> for Maverick.  To run its test suite, bzr needs the "python-testtools"
> package[1], which is packaged in Universe while bzr itself is in
> main[2].  This hasn't been a problem before because every other
> command works without it, and attempting to run the tests just asks
> you to install testtools.  I personally can't see any way to unlock
> this: I presume we can't promote python-testtools into main in an SRU.

Right, and I think we shouldn't. For SRU testing, I think it's
sufficient (and actually the more interesting case) to run the tests
on an installed system, since only that will provide a proper
integration test.

>  * grandfather the 2.2 series SRUs by running their tests in a
> separate build, and manually after installation of the package
>  * for Natty, pursue a main inclusion request
> <https://wiki.ubuntu.com/MainInclusionProcess> for python-testtools

+1 from me on this.

Thanks,

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/technical-board/attachments/20101130/babf120a/attachment.pgp