From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Stoiko Ivanov <s.ivanov@proxmox.com>, pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [PATCH pmg-api v2 2/4] api: spamassassin: read local channels
Date: Fri, 15 Jan 2021 11:02:42 +0100 [thread overview]
Message-ID: <5c086b1d-86f6-77e2-1f44-302656162535@proxmox.com> (raw)
In-Reply-To: <20201230171539.7644-3-s.ivanov@proxmox.com>
On 30.12.20 18:15, Stoiko Ivanov wrote:
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> v1->v2:
> * changed the transliteration (tr///) to an equivalent more common s///
>
> src/PMG/API2/SpamAssassin.pm | 83 +++++++++++++++++++++---------------
> 1 file changed, 49 insertions(+), 34 deletions(-)
>
> diff --git a/src/PMG/API2/SpamAssassin.pm b/src/PMG/API2/SpamAssassin.pm
> index eab02d9..6b9f8f9 100644
> --- a/src/PMG/API2/SpamAssassin.pm
> +++ b/src/PMG/API2/SpamAssassin.pm
> @@ -80,50 +80,65 @@ __PACKAGE__->register_method({
> my ($param) = @_;
>
> my $saversion = $Mail::SpamAssassin::VERSION;
> - my $channelfile = "/var/lib/spamassassin/$saversion/updates_spamassassin_org.cf";
> + my $sa_update_dir = "/var/lib/spamassassin/$saversion/";
> +
> + my $check_channel = sub {
> + my ($channel) = @_;
> +
> + # see sa-update source:
> + my $channel_file_base = $channel;
> + $channel_file_base =~ s/[^A-Za-z0-9-]+/_/g;
> + my $channelfile = "${sa_update_dir}${channel_file_base}.cf";
> +
> + my $mtime = -1;
> + my $version = -1;
> + my $newversion = -1;
> +
> + if (-f $channelfile) {
> + # stat metadata cf file
> + $mtime = (stat($channelfile))[9]; # 9 is mtime
> +
> + # parse version from metadata cf file
> + my $metadata = PVE::Tools::file_read_firstline($channelfile);
> + if ($metadata =~ m/\s([0-9]+)$/) {
> + $version = $1;
> + } else {
> + warn "invalid metadata in '$channelfile'\n";
I know it was already there, but this mayresults in a undef comparison
when checking `if ($newversion > $version) {` below.
I'd do a separate followup with that being fixed, e.g., by either prepending the
if check with a `!defined($version) || ...` check or setting it to -1000 or so.
> + }
> + }
> + # call sa-update to see if updates are available
>
> - my $mtime = -1;
> - my $version = -1;
> - my $newversion = -1;
> + my $cmd = "$SAUPDATE -v --checkonly --channel $channel";
> + PVE::Tools::run_command($cmd, noerr => 1, logfunc => sub {
> + my ($line) = @_;
>
> - if (-f $channelfile) {
> - # stat metadata cf file
> - $mtime = (stat($channelfile))[9]; # 9 is mtime
> + if ($line =~ m/Update available for channel \S+: -?[0-9]+ -> ([0-9]+)/) {
> + $newversion = $1;
> + }
> + });
>
> - # parse version from metadata cf file
> - my $metadata = PVE::Tools::file_read_firstline($channelfile);
> - if ($metadata =~ m/\s([0-9]+)$/) {
> - $version = $1;
> - } else {
> - warn "invalid metadata in '$channelfile'\n";
> - }
> - }
> - # call sa-update to see if updates are available
> + my $result = {
> + channel => $channel,
> + };
>
> - my $cmd = "$SAUPDATE -v --checkonly";
> - PVE::Tools::run_command($cmd, noerr => 1, logfunc => sub {
> - my ($line) = @_;
> + $result->{version} = $version if $version > -1;
> + $result->{update_version} = $newversion if $newversion > -1;
> + $result->{last_updated} = $mtime if $mtime > -1;
>
> - if ($line =~ m/Update available for channel \S+: -?[0-9]+ -> ([0-9]+)/) {
> - $newversion = $1;
> + if ($newversion > $version) {
> + $result->{update_avail} = 1;
> + } else {
> + $result->{update_avail} = 0;
> }
> - });
> -
> - my $result = {
> - channel => 'updates.spamassassin.org',
> + return $result;
> };
>
> - $result->{version} = $version if $version > -1;
> - $result->{update_version} = $newversion if $newversion > -1;
> - $result->{last_updated} = $mtime if $mtime > -1;
> + my @channels = ('updates.spamassassin.org');
>
> - if ($newversion > $version) {
> - $result->{update_avail} = 1;
> - } else {
> - $result->{update_avail} = 0;
> - }
> + my $localchannels = PMG::Utils::local_spamassassin_channels();
> + push(@channels, map { $_->{channelurl} } @$localchannels);
>
> - return [$result];
> + return [ map { $check_channel->($_) } @channels];
this reads a bit weird, but can be OK as $check_channel does seem to catch
all actual possible errors.
> }});
>
> __PACKAGE__->register_method({
>
next prev parent reply other threads:[~2021-01-15 10:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 17:15 [pmg-devel] [PATCH pmg-api v2 0/4] add support for locally configured SA channels Stoiko Ivanov
2020-12-30 17:15 ` [pmg-devel] [PATCH pmg-api v2 1/4] add helper for parsing SA channel.d files Stoiko Ivanov
2021-01-15 8:21 ` Thomas Lamprecht
2020-12-30 17:15 ` [pmg-devel] [PATCH pmg-api v2 2/4] api: spamassassin: read local channels Stoiko Ivanov
2021-01-15 10:02 ` Thomas Lamprecht [this message]
2021-01-18 19:47 ` Stoiko Ivanov
2021-01-19 9:10 ` Thomas Lamprecht
2020-12-30 17:15 ` [pmg-devel] [PATCH pmg-api v2 3/4] api: spamassassin: update " Stoiko Ivanov
2021-01-15 9:58 ` Thomas Lamprecht
2020-12-30 17:15 ` [pmg-devel] [PATCH pmg-api v2 4/4] pmg-daily: run sa-update for " Stoiko Ivanov
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=5c086b1d-86f6-77e2-1f44-302656162535@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