public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Eduardo Echeverria <echevemaster@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/goaccess] f43: Update to 1.11. Fixes rhbz#2502800
Date: Sat, 25 Jul 2026 18:18:52 GMT	[thread overview]
Message-ID: <178500353255.1.10797708381122561795.rpms-goaccess-a49eacc21347@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/goaccess
            Branch : f43
            Commit : a49eacc21347e7fc3a1eeb7d495c40a1eefad6fb
            Author : Eduardo Echeverria <echevemaster@gmail.com>
            Date   : 2026-07-25T15:18:42-03:00
            Stats  : +3/-2 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/goaccess/c/a49eacc21347e7fc3a1eeb7d495c40a1eefad6fb?branch=f43

            Log:
            Update to 1.11. Fixes rhbz#2502800

- Added automatic, crash-safe migration of persisted databases to
  storage format version 3
- Added configured zlib and AddressSanitizer options to the version
  output
- Added fullscreen expand and collapse controls to geolocation maps
  in the HTML report
- Added Traditional Chinese translation
- Expanded Debian package builds to Ubuntu 26.04 and additional
  architectures, and updated the packaging workflow actions
- Fixed a heap buffer overflow when parsing malformed Opera user
  agents
- Fixed an infinite loop while writing log parsing errors from
  multiple input files
- Fixed city lookups ignoring the City database when a Country
  database was listed first
- Fixed geolocation maps appearing grey after restoring persisted
  city data
- Fixed .gz file extensions being interpreted as macros in the man
  page
- Fixed iOS version parsing from user-agent strings
- Fixed unique visitor undercounting caused by collisions between
  reversed data and visitor key pairs
- Fixed WebSocket payload size checks for large and fragmented
  messages
- Grouped Lynx, Links, ELinks, w3m and Chawan under a new
  "Text-based" browser category
- Reduced storage memory usage by about 20% and parsing time by
  about 35%

---
diff --git a/.gitignore b/.gitignore
index 7d0f943..1dbf095 100644
--- a/.gitignore
+++ b/.gitignore
@@ -38,3 +38,4 @@
 /goaccess-1.9.4.tar.gz
 /goaccess-1.10.1.tar.gz
 /goaccess-1.10.2.tar.gz
+/goaccess-1.11.tar.gz

diff --git a/goaccess.spec b/goaccess.spec
index 69528a5..842ae56 100644
--- a/goaccess.spec
+++ b/goaccess.spec
@@ -7,7 +7,7 @@
 %endif
 
 Name:           goaccess
-Version:        1.10.2
+Version:        1.11
 Release:        %autorelease
 Summary:        Real-time web log analyzer and interactive viewer
 # Automatically converted from old format: GPLv2+ - review is highly recommended.

diff --git a/sources b/sources
index 36e5ef4..cb8457b 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (goaccess-1.10.2.tar.gz) = 9275ddb978d4d5c25ba0af9220bf10df8786b405f410b32e8c224374297fff10512de7158aeb77420f4e30c352c50f7a83cc3337076faccd9d1976418de0d9fb
+SHA512 (goaccess-1.11.tar.gz) = 14172061f8dbf4d6ab54c3c15019c4ea40278748f4bde05fce65a403a217a642302fd5649982a6d040bc1fbf5e1021826a18d660caf1ef6d1ccbdc61c95f03fe

                 reply	other threads:[~2026-07-25 18:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178500353255.1.10797708381122561795.rpms-goaccess-a49eacc21347@fedoraproject.org \
    --to=echevemaster@gmail.com \
    --cc=git-commits@fedoraproject.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