All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hajda, Andrzej" <andrzej.hajda@intel.com>
To: "Knop, Ryszard" <ryszard.knop@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "rk@dragonic.eu" <rk@dragonic.eu>,
	"adrinael@adrinael.net" <adrinael@adrinael.net>,
	"kamil.konieczny@linux.intel.com"
	<kamil.konieczny@linux.intel.com>
Subject: Re: [v2,3/5] Dockerfile: bump fedora version
Date: Thu, 12 Jun 2025 13:56:15 +0200	[thread overview]
Message-ID: <f6e3f845-2118-4a55-b4a9-9fde4e1da976@intel.com> (raw)
In-Reply-To: <1ffdb2f8ca93af11c528316ad331ef7adad718de.camel@intel.com>


W dniu 11.06.2025 o 14:30, Knop, Ryszard pisze:
> Hey Andrzej,
>
> On Wed, 2025-06-11 at 13:06 +0200, Andrzej Hajda wrote:
>> Fedora has not LTS versions so in this case we bump to version
>> close with release date of debian bullseye.
>>
>> v2: updated description
>>
>> Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
>> Reviewed-by: Petri Latvala <adrinael@adrinael.net> #irc
>> ---
>>   Dockerfile.build-fedora | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Dockerfile.build-fedora b/Dockerfile.build-fedora
>> index dc5d1b16b48880694167750cd3990bd7d7154d43..00f45857c20f82320500e7230e72c9522527e7a9 100644
>> --- a/Dockerfile.build-fedora
>> +++ b/Dockerfile.build-fedora
>> @@ -1,4 +1,4 @@
>> -FROM fedora:31
>> +FROM fedora:33
> As you've said, Fedora does not do LTS releases, and this one is 5
> years old. Realistically, nothing that uses a recent IGT checkout will
> be done on a Fedora version this old, and IMO there's little point in
> building this in parallel with the Debian toolchain.
>
> - If you want to support the lowest common denominator for LTSes (like
> RHELs, etc), you might want to target AlmaLinux instead. It's a RHEL
> rebuild, has a LTS release and has a chance of being actually used in
> the wild, unlike Fedora 33. Bonus points: Alma 8 (oldest, still
> supported release) comes with meson 0.58.2, so your Dockerfile gets
> simplified and closer to what end users have.
> - If you want to have one ancient and one modern distro, just target
> the latest Fedora 42 or Arch here.
> - Or do both if you want to have wider coverage on LTSes AND modern
> builds as well.


Good point, I was quite unsure which one to choose, especially as I am 
not familiar with Alma at all.

However the update to newer version/distro I will leave as TODO - 
current patchset is working/tested

and is enough to unblock some patches depending on new meson.

Playing with latest/another distro will require more time which I do not 
have atm.

Thanks for reviews and comments.


Regards

Andrzej


>
>>   RUN dnf install -y \
>>   	gcc flex bison libatomic meson ninja-build xdotool \
> Thanks, Ryszard

  reply	other threads:[~2025-06-12 11:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 11:06 [PATCH v2 0/5] CI/build: bump container images, OS and meson versions Andrzej Hajda
2025-06-11 11:06 ` [PATCH v2 1/5] CI: create own base buildah image instead of wayland's Andrzej Hajda
2025-06-11 12:33   ` [v2,1/5] " Knop, Ryszard
2025-06-11 11:06 ` [PATCH v2 2/5] Dockerfile: bump debian version Andrzej Hajda
2025-06-11 12:33   ` [v2,2/5] " Knop, Ryszard
2025-06-11 11:06 ` [PATCH v2 3/5] Dockerfile: bump fedora version Andrzej Hajda
2025-06-11 12:30   ` [v2,3/5] " Knop, Ryszard
2025-06-12 11:56     ` Hajda, Andrzej [this message]
2025-06-11 11:06 ` [PATCH v2 4/5] meson: bump required and tested version of meson Andrzej Hajda
2025-06-11 12:32   ` [v2,4/5] " Knop, Ryszard
2025-06-11 11:06 ` [PATCH v2 5/5] CI: remove podman login Andrzej Hajda
2025-06-11 12:34   ` [v2,5/5] " Knop, Ryszard
2025-06-11 20:27 ` ✓ i915.CI.BAT: success for CI/build: bump container images, OS and meson versions Patchwork
2025-06-11 20:50 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-12  0:29 ` ✓ i915.CI.Full: " Patchwork
2025-06-12  4:22 ` ✗ Xe.CI.Full: failure " Patchwork
2025-06-12 10:26   ` Kamil Konieczny

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=f6e3f845-2118-4a55-b4a9-9fde4e1da976@intel.com \
    --to=andrzej.hajda@intel.com \
    --cc=adrinael@adrinael.net \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=rk@dragonic.eu \
    --cc=ryszard.knop@intel.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 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.