Matthew Miller writes:
> See:
> https://lists.freedesktop.org/archives/systemd-devel/2022-October/048519.html
>
>Systemd will set the taint flag 'support-ended' if it detects that
>the OS image is past its end-of-support date. This date is declared
>in a new /etc/os-release field
Fabio Valentini writes:
> On Wed, Sep 7, 2022 at 10:53 PM Stewart Smith via devel
> wrote:
>>
>> For Amazon Linux, we take a different approach to Fedora (but similar to
>> RHEL) for software written in Rust and Go, and instead bundle
>> dependencies rather than hav
"Richard W.M. Jones" writes:
> On Wed, Sep 07, 2022 at 10:05:55AM +0100, Richard W.M. Jones wrote:
>>
>> https://gitlab.com/libblkio/libblkio
>>
>> This is a library that offers a C API. It happens to be implemented
>> in Rust, but it's not a "Crate" or anything like that.
>>
>> I wrote a spec
Lukas Javorsky writes:
> Hi,
>
> As from the pcre-8.45, the upstream stopped supporting this
> library. The recommended procedure is to switch onto the new pcre2
> library that has full upstream support. [1]
I was looking into doing this as much as possible for AL2022 and managed
to dig a bit on
Ben Beasley writes:
> I support deprecating openssl1.1. We definitely shouldn’t be adding any
> new packages that depend on it.
>
> However, dropping the -devel package is almost as drastic as simply
> retiring the OpenSSL 1.1 package altogether. Grepping spec files for
>
Adam Williamson writes:
> On Thu, 2022-07-07 at 10:49 -0700, Stewart Smith via devel wrote:
>> We actually have a skeleton design for such a thing (it says what
>> updates and upgrades are available), but we've lagged on
>> both posting to devel@ that it's something we've b
Josh Boyer writes:
> I really don't think encoding lifecycle information in the
> installation itself is the right approach, but it's perhaps the most
> tenable one for Fedora. However, until Fedora definitively moves to
> using independent lifecycles for their releases, this is a game of
>
Kevin Kofler via devel writes:
> Zbigniew Jędrzejewski-Szmek wrote:
>> In https://pagure.io/fesco/issue/2803 Artem asked for a user-visible
>> notification when a Fedora stops being supported. Various proposals
>> for online checks were discussed in the bug, but I think we might make
>> do with
Zbigniew Jędrzejewski-Szmek writes:
> In https://pagure.io/fesco/issue/2803 Artem asked for a user-visible
> notification when a Fedora stops being supported. Various proposals
> for online checks were discussed in the bug, but I think we might make
> do with something much simpler.
We've been
Maxwell G via devel writes:
> Hi everyone,
>
> I have been de-facto maintaining containerd in Fedora as a member of the go-
> sig for a little while now, as the previous maintainer no longer has time to
> do. In addition to the Fedora branches, this package also exists on EPEL 7.
> That branch
Chris Adams writes:
> Once upon a time, Jared Dominguez said:
>> Looks like they are using vSphere, which supports UEFI VMs. The same is
>> true for KVM, Xen and bhyve, so it's more about what feature set cloud
>> providers using these hypervisors are choosing to turn on.
>
> In a way, this is
Ben Cotton writes:
> https://fedoraproject.org/wiki/Changes/DeprecateLegacyBIOS
>
> == Summary ==
> Make UEFI a hardware requirement for new Fedora installations on
> platforms that support it (x86_64). Legacy BIOS support is not
> removed, but new non-UEFI installation is not supported on those
Gary Buhrmaster writes:
> On Thu, Nov 18, 2021 at 2:32 AM Josh Stone wrote:
>>
>> On 11/16/21 7:05 PM, Kevin Kofler via devel wrote:
>> > Realistically, they will just stick to Fedora 36 forever and just stop
>> > updating the devices (or try updating them anyway and get no updates from
>> > the
Hi there, I’m Stewart, a Principal Engineer at AWS working on Amazon
Linux, and thanks to our new direction in basing Amazon Linux on Fedora,
also Fedora.
I have a (decently) long time Linux history, remembering Slackware 3.5
on floppies, RedHat (not RHEL) 5 from CD-ROM, MkLinux, and YellowDog
Björn Persson writes:
> I believe Yum has a feature to verify signed repository metadata. I
> don't know why it's not used. If that verification would be turned on,
> are there any attacks that would still be possible then, that Rekor
> could prevent?
There's still the classic downgrade attack:
15 matches
Mail list logo
