public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] vnstat: Update to 2.11
Date: Mon, 04 Sep 2023 15:15:16 +0200	[thread overview]
Message-ID: <cc9aa55d-790f-478a-9df6-6a5f814788b4@ipfire.org> (raw)
In-Reply-To: <20230820171523.113000-1-matthias.fischer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 4285 bytes --]

Reviewed-by: Adolf Belka <adolf.belka(a)ipfire.org>

On 20/08/2023 19:15, Matthias Fischer wrote:
> For details see:
> https://humdi.net/vnstat/CHANGES
>
> "2.11 / 19-Aug-2023
>
>   - Fixed
>     - Database queries worked only if SQLite double-quoted string (DQS)
>       feature (https://www.sqlite.org/quirks.html#dblquote) was enabled
>     - Disabling data resolutions in data retention configuration didn't result
>       in possibly existing database entries getting removed from the database
>     - Disabling data resolutions in data retention configuration didn't result
>       in the data resolution getting disabled but instead storing data forever
>     - "expr: syntax error" during configure in BSD (pull request by namtsui)
>     - Image output summary would show only "no data available" text in case of
>       zero total traffic even when the historical data of no traffic could have
>       been shown instead
>     - Image output "-o -" content could get corrupted due to info, warning and
>       error messages also using stdout, configuration file warnings being the
>       most likely source, now uses stderr in image output
>     - Configuration validation was too heavily limiting and enforcing image
>       output 5 minute graph related configuration options for combinations that
>       would have resulted in usable images
>   - New
>     - Database cleanup has been changed to interpret data retention
>       configuration as number of entries to be kept instead of calendar time,
>       this restores the behaviour to similar as it was up to version 1.18, the
>       difference is visible only on systems that aren't powered all the time
>     - Database is vacuumed during daemon startup and reload, behaviour is
>       configurable using VacuumOnStartup and VacuumOnHUPSignal configuration
>       options
>     - Add configuration option InterfaceOrder for controlling the interface
>       order in outputs with multiple interfaces
>     - Used data retention configuration is made visible during daemon startup
>       and after configuration reloads
>     - Daemon will no longer start if all data resolutions have been disabled
>       in the configuration file
>     - SQLite version is visible in --version outputs
>   - Notes
>     - "Not enough data available yet." message has been replaced with
>       "No data. Timestamp of last update is same YYYY-MM-DD HH:MM:SS as of
>       database creation." to better explain the reason why there's nothing to
>       show, this message is expected to disappear within configured
>       SaveInterval if the interface is active"
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
>   lfs/vnstat | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lfs/vnstat b/lfs/vnstat
> index c854ea090..ca61562c0 100644
> --- a/lfs/vnstat
> +++ b/lfs/vnstat
> @@ -1,7 +1,7 @@
>   ###############################################################################
>   #                                                                             #
>   # IPFire.org - A linux based firewall                                         #
> -# Copyright (C) 2007-2022  IPFire Team  <info(a)ipfire.org>                     #
> +# Copyright (C) 2007-2023  IPFire Team  <info(a)ipfire.org>                     #
>   #                                                                             #
>   # This program is free software: you can redistribute it and/or modify        #
>   # it under the terms of the GNU General Public License as published by        #
> @@ -24,7 +24,7 @@
>   
>   include Config
>   
> -VER        = 2.10
> +VER        = 2.11
>   
>   THISAPP    = vnstat-$(VER)
>   DL_FILE    = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>   
>   $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>   
> -$(DL_FILE)_BLAKE2 = 82fcb54cf00a8122f31dc27f41f830ef68b92452bf7ae22bf2f1be13a1526bd12e8365002edef7766156f2df15472b189b3f219074532cb00a81156775b08997
> +$(DL_FILE)_BLAKE2 = 6eeed45d628641c9d88cf33ae1fc14871109b1e9fd0ac4a46fe8e2c194bb4600878b69408ed177bcde38ca859d0a3165d0095cab9b0bb6c036f7788fbfcb47e6
>   
>   install : $(TARGET)
>   

-- 
Sent from my laptop


      reply	other threads:[~2023-09-04 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20 17:15 Matthias Fischer
2023-09-04 13:15 ` Adolf Belka [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=cc9aa55d-790f-478a-9df6-6a5f814788b4@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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