From: Lukas Wagner <l.wagner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 1/1] d/postinst: remove old pvemailforward migration logic
Date: Wed, 25 Jun 2025 14:20:11 +0200 [thread overview]
Message-ID: <20250625122012.226237-2-l.wagner@proxmox.com> (raw)
In-Reply-To: <20250625122012.226237-1-l.wagner@proxmox.com>
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.
This also means that proxmox-mail-forward is now fully in charge of the
contents of /root/.forward.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
debian/postinst | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/debian/postinst b/debian/postinst
index aba39904..6b706951 100755
--- a/debian/postinst
+++ b/debian/postinst
@@ -155,16 +155,6 @@ case "$1" in
pveam update || true
fi
- # Always try to clean old entry, even when proxmox-mail-forward entry is already present.
- # This ensures it will still be cleaned after an upgrade following a downgrade.
- if test -f /root/.forward; then
- sed -i '\!|/usr/bin/pvemailforward!d' /root/.forward
- fi
-
- if ! test -f /root/.forward || ! grep -q '|/usr/bin/proxmox-mail-forward' /root/.forward; then
- echo '|/usr/bin/proxmox-mail-forward' >>/root/.forward
- fi
-
systemctl --system daemon-reload >/dev/null || true
# same as dh_systemd_enable (code copied)
--
2.39.5
_______________________________________________
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-06-25 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 12:20 [pve-devel] [PATCH manager/proxmox-mail-forward 0/2] install proxmox-mail-forward at /usr/libexec Lukas Wagner
2025-06-25 12:20 ` Lukas Wagner [this message]
2025-06-25 12:20 ` [pve-devel] [PATCH proxmox-mail-forward 1/1] install to /usr/libexec instead of /usr/bin Lukas Wagner
2025-07-07 10:45 ` [pve-devel] [PATCH manager/proxmox-mail-forward 0/2] install proxmox-mail-forward at /usr/libexec Fabian Grünbichler
2025-07-16 7:41 ` [pve-devel] superseded: " Lukas Wagner
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=20250625122012.226237-2-l.wagner@proxmox.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox