public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Daniel Gomez <da.gomez@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>
Cc: kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH 1/2] devconfig: drop locales-all leftovers
Date: Thu, 9 Oct 2025 23:33:04 +0200	[thread overview]
Message-ID: <4be96c4d-c86f-469a-861c-1fc381a9f385@kernel.org> (raw)
In-Reply-To: <20250929-locales-all-removal-v1-1-4177411d3e44@samsung.com>



On 29/09/2025 21.04, Daniel Gomez wrote:
> From: Daniel Gomez <da.gomez@samsung.com>
> 
> When locales-all support was added in commit 2514a694 ("guestfs: fix
> locale warnings in VM deployment"), it was added for all distros in the
> virt-builder.j2 template as well as Ansible tasks to ensure idempotency
> on previous base images.
> 
> But we just need to ensure en_US.UTF-8 is available on the guests
> image, so keep just this config in both template and tasks but remove
> locales-all.
> 
> While we are at it, also move the locale configuration after all deps
> are installed and to the distro agnostic task section. We do it anyways
> for all distros in virt-builder.j2, this ensures idempotency in all
> of them.
> 
> Fixes: 6bb3bfb2 ("base_image: Skip "locales-all" package installation")
> Signed-off-by: Daniel Gomez <da.gomez@samsung.com>
> ---
>  playbooks/roles/devconfig/tasks/main.yml | 50 +++++++++++---------------------
>  1 file changed, 17 insertions(+), 33 deletions(-)
> 
> diff --git a/playbooks/roles/devconfig/tasks/main.yml b/playbooks/roles/devconfig/tasks/main.yml
> index ae16a698..1acca6b4 100644
> --- a/playbooks/roles/devconfig/tasks/main.yml
> +++ b/playbooks/roles/devconfig/tasks/main.yml
...
> @@ -80,8 +88,6 @@
>      - { path: "/etc/default/locale", line: "LANG=en_US.UTF-8" }
>      - { path: "/etc/default/locale", line: "LANGUAGE=en_US:en" }
>      - { path: "/etc/locale.gen", line: "en_US.UTF-8 UTF-8" }
> -  when:
> -    - ansible_facts['os_family']|lower == 'debian'

FYI, I plan to merge this tomorrow as this patchset solves the current
linux-ci issue [1]. Please note that this change affects all distributions.
I believe this is the correct approach and will proceed with it to restore CI
functionality. Please, let me know if you find it breaks something on non-Debian
distros.

Link: https://github.com/linux-kdevops/kdevops/actions/runs/18347971703/job/52259752236 [1]

  reply	other threads:[~2025-10-09 21:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 19:04 [PATCH 0/2] Locales fixes Daniel Gomez
2025-09-29 19:04 ` [PATCH 1/2] devconfig: drop locales-all leftovers Daniel Gomez
2025-10-09 21:33   ` Daniel Gomez [this message]
2025-09-29 19:04 ` [PATCH 2/2] base_image: ensure base image permissions are set Daniel Gomez
2025-10-14 18:02 ` [PATCH 0/2] Locales fixes Daniel Gomez
2025-10-14 21:35   ` Chuck Lever
2025-10-15 18:21     ` Daniel Gomez
2025-10-15 21:17       ` Chuck Lever
2025-10-16 18:56         ` Chuck Lever
2025-10-17 21:59           ` Chuck Lever
2025-10-17 22:21             ` Daniel Gomez
2025-10-17 22:53             ` Daniel Gomez
2025-10-17 23:06               ` Daniel Gomez

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=4be96c4d-c86f-469a-861c-1fc381a9f385@kernel.org \
    --to=da.gomez@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=da.gomez@samsung.com \
    --cc=kdevops@lists.linux.dev \
    --cc=mcgrof@kernel.org \
    /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