From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lukas Wagner <l.wagner@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager v2 1/1] d/postinst: remove old pvemailforward migration logic
Date: Wed, 16 Jul 2025 16:36:01 +0200 [thread overview]
Message-ID: <175267655946.3186576.15023236658830859690.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250716073759.40752-2-l.wagner@proxmox.com>
On Wed, 16 Jul 2025 09:37:58 +0200, Lukas Wagner wrote:
> Before the separate proxmox-mail-forward helper was split out into its
> own package, pve-manager shipped its own pvemailforward script. Arguably
> this is the reason why the code for migrating the path to the helper in
> /root/.forward is part of pve-manager's d/postinst script, not
> proxmox-mail-forward's.
>
> The pvemailforward -> proxmox-mail-forward migration happened in
> pve-manager 7.2-12. Since we don't support skipping major versions (e.g.
> 7 -> 9), we should be able to drop the migration code for PVE 9.
>
> [...]
Applied, thanks!
[1/1] d/postinst: remove old pvemailforward migration logic
(no commit info)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-16 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 7:37 [pve-devel] [PATCH manager/proxmox-mail-forward v2 0/2] install proxmox-mail-forward at /usr/libexec Lukas Wagner
2025-07-16 7:37 ` [pve-devel] [PATCH manager v2 1/1] d/postinst: remove old pvemailforward migration logic Lukas Wagner
2025-07-16 14:36 ` Thomas Lamprecht [this message]
2025-07-16 7:37 ` [pve-devel] [PATCH proxmox-mail-forward v2 1/1] install to /usr/libexec instead of /usr/bin Lukas Wagner
2025-07-16 14:36 ` [pve-devel] applied: " Thomas Lamprecht
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=175267655946.3186576.15023236658830859690.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pve-devel@lists.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.