From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Stoiko Ivanov <s.ivanov@proxmox.com>
Cc: pmg-devel@lists.proxmox.com
Subject: Re: [PATCH pve-installer/pmg-api 0/2] ensure clamav-daemon is enabled
Date: Tue, 9 Jun 2026 13:15:52 +0200 [thread overview]
Message-ID: <bd371ffb-30fc-4fc8-8ab1-7311b1c8684d@proxmox.com> (raw)
In-Reply-To: <20260609130949.44a52611@rosa.proxmox.com>
On 09/06/2026 13:09, Stoiko Ivanov wrote:
> On Tue, 9 Jun 2026 12:49:20 +0200
> Thomas Lamprecht <t.lamprecht@proxmox.com> wrote:
>
>> On 09/06/2026 12:07, Stoiko Ivanov wrote:
>>> debian upstream's clamav packaging had some changes recently as to which
>>> services are enabled by default.
>>> This seems somewhat in active flux currently - so for the time being
>>> enable the 2 services PMG needs unconditionally.
>>
>> Doesn't catches the on-top of plain Debian installation though? Why not
>> address this in our clamav packages?
> Would also be an option - but tbh - the current intermediate version we
> ship should get replaced by the next update to clamav with (one of) the
> next trixie point releases - and I'd want to avoid tracking clamav
> ourselves, if the only diff is the service enablement.
Why? I'd always want to track such core packages for a product to reduce
reliance on external dependencies and avoid a few surprise like here, and
it's not like it would be _that_ much work?
> I sent a MR upstream last time (PMG 9.0):
> https://salsa.debian.org/clamav-team/clamav/-/merge_requests/7
> while this was not merged as is - there have been 3-4 different variants
> of how and which services are enabled and started in different branches
> and tags on salsa. - I don't mean to complain - but to say that I think
> this will take a while until the dust settles.
Supports my point above.
prev parent reply other threads:[~2026-06-09 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 10:07 [PATCH pve-installer/pmg-api 0/2] ensure clamav-daemon is enabled Stoiko Ivanov
2026-06-09 10:07 ` [PATCH pmg-api 1/2] d/postinst: ensure that " Stoiko Ivanov
2026-06-09 10:07 ` [PATCH installer 2/2] pmg: ensure " Stoiko Ivanov
2026-06-09 10:18 ` Christoph Heiss
2026-06-09 10:49 ` [PATCH pve-installer/pmg-api 0/2] " Thomas Lamprecht
2026-06-09 10:53 ` Thomas Lamprecht
2026-06-09 11:09 ` Stoiko Ivanov
2026-06-09 11:15 ` Thomas Lamprecht [this message]
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=bd371ffb-30fc-4fc8-8ab1-7311b1c8684d@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=s.ivanov@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