public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Shannon Sterz <s.sterz@proxmox.com>
Subject: Re: [pve-devel] [PATCH proxmox-offline-mirror 3/8] wizard: switch to .pgp for Debian keyring files
Date: Tue, 09 Sep 2025 10:24:38 +0200	[thread overview]
Message-ID: <1757406203.jh05db11zs.astroid@yuna.none> (raw)
In-Reply-To: <DCNGWRX0QKTZ.12D7SUZM3YK9F@proxmox.com>

On September 8, 2025 3:53 pm, Shannon Sterz wrote:
> On Mon Sep 8, 2025 at 3:16 PM CEST, Fabian Grünbichler wrote:
>> .gpg is only used for backwards-compat via a symlink
>>
>> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>> ---
>>  src/bin/proxmox-offline-mirror.rs | 17 +++++++++--------
>>  1 file changed, 9 insertions(+), 8 deletions(-)
>>
>> diff --git a/src/bin/proxmox-offline-mirror.rs b/src/bin/proxmox-offline-mirror.rs
>> index 9b8a230..fb0f43e 100644
>> --- a/src/bin/proxmox-offline-mirror.rs
>> +++ b/src/bin/proxmox-offline-mirror.rs
>> @@ -162,26 +162,27 @@ fn derive_debian_repo(
>>      };
>>
>>      let url = format!("{url} {components}");
>> +
>>      let key = match (release, variant) {
>>          (Release::Trixie, DebianVariant::Security) => {
>> -            "/usr/share/keyrings/debian-archive-trixie-security-automatic.gpg"
>> +            "/usr/share/keyrings/debian-archive-trixie-security-automatic.pgp"
>>          }
>>          (Release::Trixie, DebianVariant::Updates) | (Release::Trixie, DebianVariant::Backports) => {
>> -            "/usr/share/keyrings/debian-archive-trixie-automatic.gpg"
>> +            "/usr/share/keyrings/debian-archive-trixie-automatic.pgp"
>>          }
>> -        (Release::Trixie, _) => "/usr/share/keyrings/debian-archive-trixie-stable.gpg",
>> +        (Release::Trixie, _) => "/usr/share/keyrings/debian-archive-trixie-stable.pgp",
>>          (Release::Bookworm, DebianVariant::Security) => {
>> -            "/usr/share/keyrings/debian-archive-bookworm-security-automatic.gpg"
>> +            "/usr/share/keyrings/debian-archive-bookworm-security-automatic.pgp"
>>          }
>>          (Release::Bookworm, DebianVariant::Updates)
>>          | (Release::Bookworm, DebianVariant::Backports) => {
>> -            "/usr/share/keyrings/debian-archive-bookworm-automatic.gpg"
>> +            "/usr/share/keyrings/debian-archive-bookworm-automatic.pgp"
>>          }
>> -        (Release::Bookworm, _) => "/usr/share/keyrings/debian-archive-bookworm-stable.gpg",
>> +        (Release::Bookworm, _) => "/usr/share/keyrings/debian-archive-bookworm-stable.pgp",
>>          (Release::Bullseye, DebianVariant::Security) => {
>> -            "/usr/share/keyrings/debian-archive-bullseye-security-automatic.gpg"
>> +            "/usr/share/keyrings/debian-archive-bullseye-security-automatic.pgp"
>>          }
>> -        (Release::Bullseye, _) => "/usr/share/keyrings/debian-archive-bullseye-automatic.gpg",
>> +        (Release::Bullseye, _) => "/usr/share/keyrings/debian-archive-bullseye-automatic.pgp",
>>          (Release::Buster, DebianVariant::Security) => {
>>              "/usr/share/keyrings/debian-archive-buster-security-automatic.gpg"
>>          }
> 
> couldn't we do something similar as before (patch 1 of this series)
> here too to simplify this match statement? for example:
> 
>     let key = match (release, variant) {
>         (_, DebianVariant::Security) => {
>             &format!("/usr/share/keyrings/debian-archive-{release}-security-automatic.pgp")
>         }
>         (Release::Bullseye, _) => "/usr/share/keyrings/debian-archive-bullseye-automatic.pgp",
>         (
>             Release::Trixie | Release::Bookworm,
>             DebianVariant::Updates | DebianVariant::Backports,
>         ) => &format!("/usr/share/keyrings/debian-archive-{release}-automatic.pgp)"),
>         _ => &format!("/usr/share/keyrings/debian-archive-{release}-stable.pgp"),
>     };
> 
> or do we want to keep it as-is for clarity? (note i already dropped the
> buster variant here)

I tried to limit myself to instances where the code got shorter without
losing much (or any ;)) readability, and this one didn't make that cut
for me..


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-09-09  8:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08 13:16 [pve-devel] [PATCH proxmox-offline-mirror 0/8] misc. wizard cleanup Fabian Grünbichler
2025-09-08 13:16 ` [pve-devel] [PATCH proxmox-offline-mirror 1/8] wizard: simplify repository url generation Fabian Grünbichler
2025-09-08 13:16 ` [pve-devel] [PATCH proxmox-offline-mirror 2/8] wizard: implement PartialOrd/Ord on Release Fabian Grünbichler
2025-09-08 13:16 ` [pve-devel] [PATCH proxmox-offline-mirror 3/8] wizard: switch to .pgp for Debian keyring files Fabian Grünbichler
2025-09-08 13:53   ` Shannon Sterz
2025-09-09  8:24     ` Fabian Grünbichler [this message]
2025-09-08 13:16 ` [pve-devel] [PATCH proxmox-offline-mirror 4/8] wizard: use /usr/share/keyring/proxmox-release-bookworm.gpg Fabian Grünbichler
2025-09-08 13:16 ` [pve-devel] [PATCH proxmox-offline-mirror 5/8] wizard: simplify Proxmox repository url generation Fabian Grünbichler
2025-09-08 15:20   ` Shannon Sterz
2025-09-09  8:35     ` Fabian Grünbichler
2025-09-08 13:16 ` [pve-devel] [PATCH proxmox-offline-mirror 6/8] wizard: drop Release::Buster and Ceph::Luminous/Nautilus Fabian Grünbichler
2025-09-08 13:16 ` [pve-devel] [PATCH proxmox-offline-mirror 7/8] wizard: simplify default Debian components Fabian Grünbichler
2025-09-08 13:16 ` [pve-devel] [PATCH proxmox-offline-mirror 8/8] wizard: deduplicate Proxmox key path mapping Fabian Grünbichler
2025-09-08 15:27 ` [pve-devel] [PATCH proxmox-offline-mirror 0/8] misc. wizard cleanup Shannon Sterz
2025-09-09  9:02 ` [pve-devel] applied-series: " Fabian Grünbichler

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=1757406203.jh05db11zs.astroid@yuna.none \
    --to=f.gruenbichler@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.sterz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal