All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 0/6] debian / libvirt / devconfig fixes
Date: Sat, 29 Mar 2025 16:01:35 -0700	[thread overview]
Message-ID: <20250329230141.3718282-1-mcgrof@kernel.org> (raw)

Changes on this v2:

I only modified this series with 1 small change and the commit log
on patch #5 "guestfs: replace ansible group permisison requirement on    
libvirt system uri" with the changes on here:

https://lore.kernel.org/all/Z-h3eTCpRC28eaCm@bombadil.infradead.org/T/#mcdb789863b84ed219ed19eeccac3eb8dcfcca17b

That's it.

Lemme know if this looks good, I just tested this on a bringup on a shared
system.

Luis Chamberlain (6):
  scripts/bringup_guestfs.sh: uninstall unattended-upgrades on debian
    guests
  devconfig: ensure unattended-upgrades is not installed on debian
  libvirt: use consistent pool path variables and use optional yaml
    output
  Kconfig: adopt output yaml for KDEVOPS_FIRST_RUN
  guestfs: replace ansible group permisison requirement on libvirt
    system uri
  gen_nodes: ensure kdevops prefix has no dashes

 Kconfig                                       |  1 +
 kconfigs/Kconfig.guestfs                      | 15 ++++
 kconfigs/Kconfig.libvirt                      | 11 ++-
 .../roles/bringup_guestfs/tasks/main.yml      | 76 +++++++++++++++++++
 .../tasks/install-deps/debian/main.yml        | 22 ++++++
 playbooks/roles/gen_nodes/tasks/main.yml      |  5 ++
 scripts/bringup_guestfs.sh                    |  6 +-
 scripts/bringup_vagrant.sh                    |  2 +-
 scripts/destroy_guestfs.sh                    |  2 +-
 scripts/destroy_vagrant.sh                    |  2 +-
 scripts/gen-nodes.Makefile                    |  6 --
 scripts/guestfs.Makefile                      |  9 +--
 scripts/prune_stale_vagrant.sh                |  2 +-
 scripts/vagrant.Makefile                      |  5 --
 14 files changed, 137 insertions(+), 27 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-03-29 23:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-29 23:01 Luis Chamberlain [this message]
2025-03-29 23:01 ` [PATCH 1/6] scripts/bringup_guestfs.sh: uninstall unattended-upgrades on debian guests Luis Chamberlain
2025-03-29 23:01 ` [PATCH 2/6] devconfig: ensure unattended-upgrades is not installed on debian Luis Chamberlain
2025-03-29 23:01 ` [PATCH 3/6] libvirt: use consistent pool path variables and use optional yaml output Luis Chamberlain
2025-03-29 23:01 ` [PATCH 4/6] Kconfig: adopt output yaml for KDEVOPS_FIRST_RUN Luis Chamberlain
2025-03-29 23:01 ` [PATCH 5/6] guestfs: replace ansible group permisison requirement on libvirt system uri Luis Chamberlain
2025-03-29 23:01 ` [PATCH 6/6] gen_nodes: ensure kdevops prefix has no dashes Luis Chamberlain
2025-03-31 17:35   ` Scott Mayhew
2025-03-31 18:33     ` Luis Chamberlain
2025-03-31 19:14       ` Scott Mayhew
2025-03-31 19:36         ` Luis Chamberlain
2025-03-31 20:49           ` Scott Mayhew
2025-04-01 21:11             ` Luis Chamberlain
  -- strict thread matches above, loose matches on Subject: below --
2025-03-23 11:50 [PATCH 0/6] debian / libvirt / devconfig fixes Luis Chamberlain

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=20250329230141.3718282-1-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=kdevops@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.