From: Lukas Wagner <l.wagner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH debcargo-config/proxmox 0/6] package `mail-parser` for trixie; update proxmox-notify for newest mail-parser version
Date: Fri, 23 May 2025 14:26:09 +0200 [thread overview]
Message-ID: <20250523122615.251430-1-l.wagner@proxmox.com> (raw)
This series packages the newest version of the `mail-parser` crate along
with its new `hashify` dep for Debian Trixie.
The second part of the series adapts proxmox-notify to the changes in `mail-parser`'s
API.
debcargo-conf:
Lukas Wagner (3):
import mail-parser from bookworm
package hashify 0.2.6
update mail-parser to 0.11.0
src/hashify/debian/changelog | 6 ++
src/hashify/debian/copyright | 37 +++++++++
src/hashify/debian/copyright.debcargo.hint | 49 ++++++++++++
src/hashify/debian/debcargo.toml | 2 +
src/mail-parser/debian/changelog | 17 ++++
src/mail-parser/debian/copyright | 49 ++++++++++++
.../debian/copyright.debcargo.hint | 77 +++++++++++++++++++
src/mail-parser/debian/debcargo.toml | 2 +
8 files changed, 239 insertions(+)
create mode 100644 src/hashify/debian/changelog
create mode 100644 src/hashify/debian/copyright
create mode 100644 src/hashify/debian/copyright.debcargo.hint
create mode 100644 src/hashify/debian/debcargo.toml
create mode 100644 src/mail-parser/debian/changelog
create mode 100644 src/mail-parser/debian/copyright
create mode 100644 src/mail-parser/debian/copyright.debcargo.hint
create mode 100644 src/mail-parser/debian/debcargo.toml
proxmox:
Lukas Wagner (3):
notify: smtp: move building of forwarded mails to separate function
notify: smtp: add test for building forwarded messages
notify: update mail-parser dependency to 0.11
Cargo.toml | 2 +-
proxmox-notify/src/endpoints/smtp.rs | 221 ++++++++++--------
proxmox-notify/src/lib.rs | 3 +-
proxmox-notify/testdata/test1.msg | 104 +++++++++
.../test_forward_message_from_raw.ref | 95 ++++++++
5 files changed, 331 insertions(+), 94 deletions(-)
create mode 100644 proxmox-notify/testdata/test1.msg
create mode 100644 proxmox-notify/testdata/test_forward_message_from_raw.ref
Summary over all repositories:
13 files changed, 570 insertions(+), 94 deletions(-)
--
Generated by git-murpp 0.8.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-05-23 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 12:26 Lukas Wagner [this message]
2025-05-23 12:26 ` [pve-devel] [PATCH debcargo-config 1/3] import mail-parser from bookworm Lukas Wagner
2025-05-23 12:26 ` [pve-devel] [PATCH debcargo-config 2/3] package hashify 0.2.6 Lukas Wagner
2025-05-23 12:26 ` [pve-devel] [PATCH debcargo-config 3/3] update mail-parser to 0.11.0 Lukas Wagner
2025-05-23 12:26 ` [pve-devel] [PATCH proxmox 1/3] notify: smtp: move building of forwarded mails to separate function Lukas Wagner
2025-05-23 12:26 ` [pve-devel] [PATCH proxmox 2/3] notify: smtp: add test for building forwarded messages Lukas Wagner
2025-05-23 12:26 ` [pve-devel] [PATCH proxmox 3/3] notify: update mail-parser dependency to 0.11 Lukas Wagner
2025-05-26 14:01 ` [pve-devel] applied: [PATCH debcargo-config/proxmox 0/6] package `mail-parser` for trixie; update proxmox-notify for newest mail-parser version 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=20250523122615.251430-1-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 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.