From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Erik Skultety <eskultet@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Warner Losh" <imp@bsdimp.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Ed Maste" <emaste@freebsd.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Kyle Evans" <kevans@freebsd.org>,
"Li-Wen Hsu" <lwhsu@freebsd.org>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [PATCH v3 0/4] tests/vm/freebsd: Get up-to-date package list from lcitool
Date: Mon, 17 Jul 2023 14:17:09 +0100 [thread overview]
Message-ID: <ZLU/VS75+TEiB3+r@redhat.com> (raw)
In-Reply-To: <ZLU0Sz8nUUrlZlsY@ridgehead.tt.lan>
On Mon, Jul 17, 2023 at 02:30:03PM +0200, Erik Skultety wrote:
> On Mon, Jul 17, 2023 at 02:18:34PM +0200, Thomas Huth wrote:
> > On 11/07/2023 16.49, Philippe Mathieu-Daudé wrote:
> > > Inspired by this patch from Thomas:
> > > https://lore.kernel.org/qemu-devel/20230531090415.40421-1-thuth@redhat.com/
> > >
> > > Instead of updating the package list manually, use lcitool vars file.
> > >
> > > Since v2:
> > > - Commit generated json (Daniel)
> > >
> > > Since v1:
> > > - Addressed Erik & Daniel comments (generate in JSON)
> > >
> > > Philippe Mathieu-Daudé (4):
> > > tests/lcitool: Generate distribution packages list in JSON format
> > > tests/lcitool: Refresh generated files
> > > tests/vm: Introduce get_qemu_packages_from_lcitool_json() helper
> > > tests/vm/freebsd: Get up-to-date package list from lcitool vars file
> > >
> > > tests/docker/dockerfiles/debian-amd64.docker | 2 -
> > > tests/docker/dockerfiles/ubuntu2004.docker | 2 -
> > > tests/docker/dockerfiles/ubuntu2204.docker | 2 -
> >
> > Thanks, I'm queuing your patches for my next pull request - but I'm dropping
> > the hunks that change libpmem-dev and libxen-dev in the docker files -
> > otherwise this would just get reverted once somebody using a x86 host runs
> > the refresh step again. I hope this issue can be tackled by a future lcitool
> > update instead.
> >
> > Thomas
> >
>
> Can you guys please create an issue at
> https://gitlab.com/libvirt/libvirt-ci.git to have this officially tracked?
Done:
https://gitlab.com/libvirt/libvirt-ci/-/issues/26
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2023-07-17 13:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 14:49 [PATCH v3 0/4] tests/vm/freebsd: Get up-to-date package list from lcitool Philippe Mathieu-Daudé
2023-07-11 14:49 ` [PATCH v3 1/4] tests/lcitool: Generate distribution packages list in JSON format Philippe Mathieu-Daudé
2023-07-11 15:31 ` Daniel P. Berrangé
2023-07-11 19:39 ` Warner Losh
2023-07-12 11:07 ` Philippe Mathieu-Daudé
2023-07-12 17:57 ` Warner Losh
2023-07-11 14:49 ` [PATCH v3 2/4] tests/lcitool: Refresh generated files Philippe Mathieu-Daudé
2023-07-11 17:58 ` Daniel P. Berrangé
2023-07-12 11:00 ` Philippe Mathieu-Daudé
2023-07-12 11:12 ` Daniel P. Berrangé
2023-07-12 12:55 ` Philippe Mathieu-Daudé
2023-07-12 13:07 ` Daniel P. Berrangé
2024-01-02 18:19 ` Philippe Mathieu-Daudé
2024-01-02 18:36 ` Ilya Maximets
2024-01-03 9:07 ` Philippe Mathieu-Daudé
2023-07-11 14:49 ` [PATCH v3 3/4] tests/vm: Introduce get_qemu_packages_from_lcitool_json() helper Philippe Mathieu-Daudé
2023-07-11 17:59 ` Daniel P. Berrangé
2023-07-11 14:49 ` [PATCH v3 4/4] tests/vm/freebsd: Get up-to-date package list from lcitool vars file Philippe Mathieu-Daudé
2023-07-11 17:59 ` Daniel P. Berrangé
2023-07-17 12:18 ` [PATCH v3 0/4] tests/vm/freebsd: Get up-to-date package list from lcitool Thomas Huth
2023-07-17 12:30 ` Erik Skultety
2023-07-17 13:17 ` Daniel P. Berrangé [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZLU/VS75+TEiB3+r@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=emaste@freebsd.org \
--cc=eskultet@redhat.com \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=lwhsu@freebsd.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).