Sync bzr 2.3.0-1 (main) from Debian unstable (main)

bzr 2.3.0-1 builds on amd64. Sync request ACK'd.

[Updating] bzr (2.3.0~beta5-1 [Ubuntu] < 2.3.0-2 [Debian])
 * Trying to add bzr...
2011-02-08 16:11:15 INFO - <bzr_2.3.0.orig.tar.gz: downloading from http://ftp.debian.org/debian/>
2011-02-08 16:11:18 INFO - <bzr_2.3.0-2.dsc: downloading from http://ftp.debian.org/debian/>
2011-02-08 16:11:18 INFO - <bzr_2.3.0-2.debian.tar.gz: downloading from http://ftp.debian.org/debian/>
I: bzr [main] -> bzr_2.3.0~beta5-1 [main].
I: bzr [main] -> bzr-doc_2.3.0~beta5-1 [main].

please check component-mismatches before sync requests and syncs

 o subunit: libcppunit-subunit-dev libcppunit-subunit0 libsubunit-dev libsubunit0 python-subunit
   [Reverse-Depends: Rescued from subunit, libcppunit-subunit-dev, libsubunit-dev]
   [Reverse-Build-Depends: bzr]

Assigning to Jelmer as original requestor of the sync, to help with the MIR review of subunit (or revert the need for it, but I guess we should rather have it in main for proper test suite integration).

At the moment subunit is really only required for running the testsuite in parallel, so for the moment I think we should just disable that and drop subunit as build dependency.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/25/2011 03:39 PM, Jelmer Vernooij wrote:
> At the moment subunit is really only required for running the testsuite
> in parallel, so for the moment I think we should just disable that and
> drop subunit as build dependency.
>

Is there such a thing as a "build recommends" or "build suggests"?

I know we use subunit as part of PQM, so it isn't required but it does
seem recommended to have around.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2MriAACgkQJdeBCYSNAAM/2QCfZzajuncCxTmL/jYPRfb8KPmp
njEAoK4O+qK8Vt10/iST8EtXjnhafQRU
=YDYd
-----END PGP SIGNATURE-----

On Fri, 2011-03-25 at 15:00 +0000, John A Meinel wrote:
> On 03/25/2011 03:39 PM, Jelmer Vernooij wrote:
> > At the moment subunit is really only required for running the testsuite
> > in parallel, so for the moment I think we should just disable that and
> > drop subunit as build dependency.
> Is there such a thing as a "build recommends" or "build suggests"?
No, there isn't anything like that as far as I know. Build-Depends are
only required when building the binary packages from the source
package so generally we're pretty liberal with what we add there.

> I know we use subunit as part of PQM, so it isn't required but it does
> seem recommended to have around.
We only added the subunit dependency recently so we could run the
testsuite in parallel. The package built fine before that, so I think
just reverting that change in the Ubuntu package would work.

Cheers,

Jelmer

bzr (2.3.1-1ubuntu1) natty; urgency=low

  * Drop build dependency on python-subunit (universe). LP: #713038.
  * Disable parallel tests.

 -- Matthias Klose <email address hidden> Sat, 26 Mar 2011 01:50:11 +0100

This makes the subunit task no longer relevant for beta-1. I'm leaving it open in case you still want to get it reviewed for promotion to main.

The subunit task isn't release critical.

Unsubscribing archive admins. Please resubscribe if a sync etc. is necessary.

Removing the subunit task for now; we'll have to look at what to do about bzr in Ubuntu vs Debian as the Debian package has more build dependencies that are not in main these days.