bzr-2.3.2, SRU and conflicting tags

vila v.ladeuil+lp at free.fr
Fri May 13 06:25:21 UTC 2011


>>>>> John Arbash Meinel <john at arbash-meinel.com> writes:

    > On 5/12/2011 11:12 PM, vila wrote:
    >> Hi guys,
    >> 
    >> I was cutting the 2.3.2 release and encountered an issue:
    >> 
    >> * I created the bzr-2.3.2 tag and submitted to pqm (lp:bzr/2.3) (yeah,
    >> for once I didn't run the test suite locally, shame on me !)
    >> 
    >> * I ran make check-dist-tarball | subunit2pyunit and got > 1000
    >> failures... Hello http://pad.lv/760435 ! Of course, pqm running py2.6
    >> happily ignored the problem (and of course this patch landed while I
    >> was in vacations and babune wasn't running so I never witnessed the
    >> bug nor realized the implications).
    >> 
    >> * I thought that the SRU won't be possible without a passing test suite
    >> (oops ?)
    >> 

    > Why is the SRU running python 2.7?

Natty is running 2.7.

$ rmadison python
    python | 2.4.2-0ubuntu3 |        dapper | all
    python | 2.5.2-0ubuntu1 |         hardy | all
    python | 2.6.4~rc1-0ubuntu1 |        karmic | all
    python | 2.6.4-0ubuntu1 | karmic-updates | all
    python | 2.6.5-0ubuntu1 |         lucid | all
    python | 2.6.6-2ubuntu1 |      maverick | all
    python | 2.6.6-2ubuntu2 | maverick-updates | all
    python | 2.7.1-0ubuntu5 |         natty | all
    python | 2.7.1-0ubuntu5 |       oneiric | all

    > If we are backporting to Natty, I thought that still had a default
    > of python 2.6. (I certainly could be wrong.)

    > I would personally say, if python2.7 is the target, and Natty can't pass
    > the test suite, then we fix it for bzr-2.3.3 and don't try to SRU
    > 2.3.2.

Lacking feedback, That's what I wanted to do.

    > The release *is cut*,

-ish. The issue is that the tag is already on lp:bzr/2.3.

    > the tarballs are in the wild.

No. The problem occurred while testing the tarball *before* uploading
it.

    > Now is *not* the time to override the version.

Right, I thought I could change the tag *before* uploading the tarball :-/

    > We can cut bzr-2.3.3 *today* if you want, but the ship has long since
    > sailed for us to release something new called bzr-2.3.2.

There is no 2.3.2 tarball yet, hence my request.

      Vincent

P.S.: I'll wait a couple of hours more and will go the 2.3.3 route if no
further feedback is provided.



More information about the bazaar mailing list