From: Lukas Sichert <l.sichert@proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Lukas Sichert <l.sichert@proxmox.com>
Subject: [PATCH perl-rs v2 1/3] common: remove deprecated PVE::RS::CalendarEvent compat module
Date: Thu, 5 Nov 2026 10:41:02 +0100 [thread overview]
Message-ID: <20261105094124.42373-2-l.sichert@proxmox.com> (raw)
In-Reply-To: <20261105094124.42373-1-l.sichert@proxmox.com>
PVE::RS::CalendarEvent only provided Proxmox::RS::CalendarEvent under
its old name by using it as base and has been deprecated since the
package was renamed. Nothing in the pve and perl-rs repositories
references it any more, so drop it.
Signed-off-by: Lukas Sichert <l.sichert@proxmox.com>
---
Notes:
Changes v1 -> v2:
- new patch, delete the CalendarEvent file instead of enabling strict
and warnings in it
common/pkg/PVE/RS/CalendarEvent.pm | 3 ---
1 file changed, 3 deletions(-)
delete mode 100644 common/pkg/PVE/RS/CalendarEvent.pm
diff --git a/common/pkg/PVE/RS/CalendarEvent.pm b/common/pkg/PVE/RS/CalendarEvent.pm
deleted file mode 100644
index 3a5f66e..0000000
--- a/common/pkg/PVE/RS/CalendarEvent.pm
+++ /dev/null
@@ -1,3 +0,0 @@
-use base 'Proxmox::RS::CalendarEvent';
-# Compat, Deprecated!
-1
--
2.47.3
next prev parent reply other threads:[~2026-11-05 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 9:41 [PATCH perl-rs/proxmox v2 0/3] perl: enable strict and warnings in modules that lack them Lukas Sichert
2026-11-05 9:41 ` Lukas Sichert [this message]
2026-11-05 9:41 ` [PATCH perl-rs v2 2/3] common: enable v5.36 in Proxmox::Lib::Common Lukas Sichert
2026-11-05 9:41 ` [PATCH proxmox v2 3/3] pve-api-types: enable v5.36 in Bool Lukas Sichert
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=20261105094124.42373-2-l.sichert@proxmox.com \
--to=l.sichert@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