Re: [PATCH] gitlab: fall back to commit hash in qemu-setup filename

2022-01-28 Thread Alex Bennée
Stefan Hajnoczi writes: > Personal repos may not have release tags (v6.0.0, v6.1.0, etc) and this > causes cross_system_build_job to fail when pretty-printing a unique > qemu-setup-*.exe name: > > version="$(git describe --match v[0-9]*)"; > ^^ fails ^^^ > mv -v

Re: [PATCH] gitlab: fall back to commit hash in qemu-setup filename

2022-01-26 Thread Thomas Huth
On 25/01/2022 18.34, Stefan Hajnoczi wrote: Personal repos may not have release tags (v6.0.0, v6.1.0, etc) and this causes cross_system_build_job to fail when pretty-printing a unique qemu-setup-*.exe name: version="$(git describe --match v[0-9]*)"; ^^ fails ^^^

Re: [PATCH] gitlab: fall back to commit hash in qemu-setup filename

2022-01-25 Thread Philippe Mathieu-Daudé via
On 1/25/22 18:34, Stefan Hajnoczi wrote: > Personal repos may not have release tags (v6.0.0, v6.1.0, etc) and this > causes cross_system_build_job to fail when pretty-printing a unique > qemu-setup-*.exe name: > > version="$(git describe --match v[0-9]*)"; > ^^ fails ^^^

Re: [PATCH] gitlab: fall back to commit hash in qemu-setup filename

2022-01-25 Thread Greg Kurz
On Tue, 25 Jan 2022 17:34:54 + Stefan Hajnoczi wrote: > Personal repos may not have release tags (v6.0.0, v6.1.0, etc) and this > causes cross_system_build_job to fail when pretty-printing a unique > qemu-setup-*.exe name: > > version="$(git describe --match v[0-9]*)"; > ^

[PATCH] gitlab: fall back to commit hash in qemu-setup filename

2022-01-25 Thread Stefan Hajnoczi
Personal repos may not have release tags (v6.0.0, v6.1.0, etc) and this causes cross_system_build_job to fail when pretty-printing a unique qemu-setup-*.exe name: version="$(git describe --match v[0-9]*)"; ^^ fails ^^^ mv -v qemu-setup*.exe qemu-setup-${version}.ex