AW: New 3.3.2 and 3.4.1 release candidates

AW: New 3.3.2 and 3.4.1 release candidates

[Carsten Schiers]

Keir,

could it be that there is something wrong with Config.mk's QEMU_TAG variable?

I get a:

> + git checkout -b dummy xen-3.4.1-rc7
> fatal: git checkout: updating paths is incompatible with switching branches/forcing
> Did you intend to checkout 'xen-3.4.1-rc7' which can not be resolved as commit?
> make[1]: *** [ioemu-dir-find] Fehler 128
> make[1]: Leaving directory `/usr/src/xen/xen-3.4.1-rc7/tools'
> make: *** [tools/ioemu-dir] Fehler 2

It's still working with tag xen-3.4.1-rc5, so I think it could be that the repo has no
-rc7 tag currently...

BR,
Carsten.

----- Originalnachricht -----
Von: Keir Fraser <keir.fraser@eu.citrix.com>
Gesendet: Mon, 13.7.2009 13:10
An: xen-devel@lists.xensource.com
Betreff: [Xen-devel] New 3.3.2 and 3.4.1 release candidates

Folks,

New RCs are tagged as follows:
http://xenbits.xensource.com/xen-3.3-testing.hg (3.3.2-rc5)
http://xenbits.xensource.com/xen-3.4-testing.hg (3.4.1-rc7)

Please test!

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: AW: New 3.3.2 and 3.4.1 release candidates

[Keir Fraser]

On 13/07/2009 13:27, "Carsten Schiers" <carsten@schiers.de> wrote:

>> + git checkout -b dummy xen-3.4.1-rc7
>> fatal: git checkout: updating paths is incompatible with switching
>> branches/forcing
>> Did you intend to checkout 'xen-3.4.1-rc7' which can not be resolved as
>> commit?
>> make[1]: *** [ioemu-dir-find] Fehler 128
>> make[1]: Leaving directory `/usr/src/xen/xen-3.4.1-rc7/tools'
>> make: *** [tools/ioemu-dir] Fehler 2
> 
> It's still working with tag xen-3.4.1-rc5, so I think it could be that the
> repo has no
> -rc7 tag currently...

I don't think Ian *ever* remembers to push his tree.

 -- Keir

Re: AW: New 3.3.2 and 3.4.1 release candidates

[Ian Jackson]

Keir Fraser writes ("Re: AW: [Xen-devel] New 3.3.2 and 3.4.1 release candidates"):
> On 13/07/2009 13:27, "Carsten Schiers" <carsten@schiers.de> wrote:
> > It's still working with tag xen-3.4.1-rc5, so I think it could be that the
> > repo has no
> > -rc7 tag currently...
> 
> I don't think Ian *ever* remembers to push his tree.

The tag file is there on xenbits, so I did push it.  I'm looking into
what's going wrong.

Ian.

Re: AW: New 3.3.2 and 3.4.1 release candidates

[Ian Jackson]

iwj writes ("Re: AW: [Xen-devel] New 3.3.2 and 3.4.1 release candidates"):
> The tag file is there on xenbits, so I did push it.  I'm looking into
> what's going wrong.

Ah.  The build system is fetching the tree via http rather than the
git protocol (which has been available on xenbits for some time now),
and I didn't run the magic `update the tree for http' rune.

I'm writing a checklist.

Ian.

AW: AW: New 3.3.2 and 3.4.1 release candidates

[Carsten Schiers]

Seems to be ok now...

Thanks,
Carsten

----- Originalnachricht -----
Von: Ian Jackson <Ian.Jackson@eu.citrix.com>
Gesendet: Mon, 13.7.2009 15:26
An: Keir Fraser <Keir.Fraser@eu.citrix.com> ; Carsten Schiers <carsten@schiers.de> ; xen-devel@lists.xensource.com
Betreff: Re: AW: [Xen-devel] New 3.3.2 and 3.4.1 release candidates

iwj writes ("Re: AW: [Xen-devel] New 3.3.2 and 3.4.1 release candidates"):
> The tag file is there on xenbits, so I did push it.  I'm looking into
> what's going wrong.

Ah.  The build system is fetching the tree via http rather than the
git protocol (which has been available on xenbits for some time now),
and I didn't run the magic `update the tree for http' rune.

I'm writing a checklist.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: AW: AW: New 3.3.2 and 3.4.1 release candidates

[Ian Jackson]

Carsten Schiers writes ("AW: AW: [Xen-devel] New 3.3.2 and 3.4.1 release candidates"):
> Seems to be ok now...

Yes, I fixed it.  Good to hear it worked.

Sorry,
Ian.

Re: AW: AW: New 3.3.2 and 3.4.1 release candidates

[Mark Johnson]

On Mon, Jul 13, 2009 at 9:45 AM, Ian Jackson<Ian.Jackson@eu.citrix.com> wrote:
> Carsten Schiers writes ("AW: AW: [Xen-devel] New 3.3.2 and 3.4.1 release candidates"):
>> Seems to be ok now...
>
> Yes, I fixed it.  Good to hear it worked.

Hmm, I seem to be missing something?  I haven't seen any pushes to
the qemu-3.3 repo on xen-changelog and I don't see an update in the
git repo?


: asus-a8n[1]; git pull -v
>From http://xenbits.xen.org/git-http/qemu-xen-3.3-testing
 = [up to date]      ide-write-cache -> origin/ide-write-cache
 = [up to date]      iwj.block-extendable-flag ->
origin/iwj.block-extendable-flag
 = [up to date]      iwj.block-rw-rangecheck -> origin/iwj.block-rw-rangecheck
 = [up to date]      iwj.t.phys_ram_size -> origin/iwj.t.phys_ram_size
 = [up to date]      master     -> origin/master
 = [up to date]      origin     -> origin/origin
 = [up to date]      qemu       -> origin/qemu
 = [up to date]      upstream   -> origin/upstream
 = [up to date]      vga-reverse-merge -> origin/vga-reverse-merge
 = [up to date]      xen.netscriptenv -> origin/xen.netscriptenv
Already up-to-date.
: asus-a8n[1]; git tag | tail -2
xen-3.3.1-rc4
xen-3.3.2-rc1
: asus-a8n[1];




MRJ

Re: AW: AW: New 3.3.2 and 3.4.1 release candidates

[Ian Jackson]

Mark Johnson writes ("Re: AW: AW: [Xen-devel] New 3.3.2 and 3.4.1 release candidates"):
> Hmm, I seem to be missing something?  I haven't seen any pushes to
> the qemu-3.3 repo on xen-changelog and I don't see an update in the
> git repo?

It looks like I pushed the tag but not the master ref, due to
misunderstanding what `git-push' does exactly.  I've updated the trees
and also fixed up the 3.3 trees (affected the same way) and amended my
new checklist.

Ian.