From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [RFC kernel-meta] add proxmox-secure-boot-support package
Date: Thu, 11 Apr 2024 13:45:37 +0200 [thread overview]
Message-ID: <1712835911.h309v3pwpx.astroid@yuna.none> (raw)
In-Reply-To: <b92c93f7-6df9-4add-8ce2-50b13aea3317@proxmox.com>
On February 6, 2024 10:40 am, Thomas Lamprecht wrote:
> Am 05/02/2024 um 12:45 schrieb Fabian Grünbichler:
>> On February 2, 2024 7:23 pm, Thomas Lamprecht wrote:
>>> seems OK w.r.t. change, but do we want this to be either part of the shim,
>>> or a separate repo? So that we do not need to ship a new kernel meta package
>>> when the shim version pinning needs an update? As it feels a bit unrelated
>>> to the kernel meta package in general to me.
>>
>> well, it needs to be updated when either grub or shim have a security
>> update (or on major releases of course), so there's not really one place
>> to fit it. we could have a separate repo (or refactor this one to
>> contain two source packages, but that's fairly ugly as well) - that
>> would obviously work as well.
>>
>
> Then I'd prefer an extra repo, until now we basically pulled out any
> such only tangentially related package out from the source package it
> was added to, as there basically no time that a single change will
> affect both, and I really do not like that churn – while not a biggie
> it just is unnecessary churn, which I'm really not a fan of (and thus
> highly probably want to rip this out sooner or later anyway).
this is done now, see https://git.proxmox.com/?p=proxmox-secure-boot-support.git;a=summary
prev parent reply other threads:[~2024-04-11 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 12:05 Fabian Grünbichler
2024-02-02 18:23 ` Thomas Lamprecht
2024-02-05 11:45 ` Fabian Grünbichler
2024-02-06 9:40 ` Thomas Lamprecht
2024-04-11 11:45 ` Fabian Grünbichler [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=1712835911.h309v3pwpx.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.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.