Is it normal, that after every upgrade I have to give http user and/or group access to /etc/webapps/matomo/config.ini.php as the owner is root:root with permissions 770? If I don't do that, nginx can't read the config and when I visit the login page, it starts the installation wizard.
Search Criteria
Package Details: matomo 5.0.3-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/matomo.git (read-only, click to copy) |
|---|---|
| Package Base: | matomo |
| Description: | A real-time web analytics platform |
| Upstream URL: | https://matomo.org/ |
| Licenses: | GPL-3.0-or-later |
| Replaces: | piwik |
| Submitter: | freaknils |
| Maintainer: | C0rn3j |
| Last Packager: | C0rn3j |
| Votes: | 35 |
| Popularity: | 0.000000 |
| First Submitted: | 2018-04-01 09:31 (UTC) |
| Last Updated: | 2024-03-24 15:42 (UTC) |
Dependencies (5)
Required by (0)
Sources (2)
Tha-Fox commented on 2019-02-08 07:43 (UTC)
ChrisMorgan commented on 2018-11-20 22:21 (UTC)
@C0rn3j: thanks, fixed in 3.7.0-1, just released.
C0rn3j commented on 2018-11-20 10:11 (UTC)
The PKGBUILD has the following line - GeoLite2-City.mmdb is provided by geoip2-datbase, which is optdepends.
The geoip2-datbase is a typo, it's missing an 'a'. Caught me off guard when I was copypasting it.
ChrisMorgan commented on 2018-09-02 09:24 (UTC)
@G4Zz0L1: the situation has now been clarified, and I’ve released 3.6.0-2 with the checksums for the updated matomo-3.6.0.tar.gz{,.asc}.
ChrisMorgan commented on 2018-09-02 08:48 (UTC)
@G4Zz0L1: they changed matomo-3.6.0.tar.gz yesterday; I’ve filed https://github.com/matomo-org/matomo/issues/13380 to follow up what happened. While that happens, feel free to modify the sha256sums in the PKGBUILD yourself.
G4Zz0L1 commented on 2018-09-01 23:36 (UTC)
The sha512sum for matomo-3.6.0.tar.gz is wrong
ChrisMorgan commented on 2018-09-01 01:48 (UTC) (edited on 2018-09-01 01:48 (UTC) by ChrisMorgan)
I apologise for the delay. I’ve now updated it to 3.6.0 which was just released. Note that when you do the database upgrade, you’ll get complaints about file integrity checks having failed; that’s an upstream bug, see https://github.com/matomo-org/matomo/issues/13364.
If you’re upgrading from 3.4.0, I recommend caution: it’s a major release of the packaging. There are certain changes in the structure of the packaging, and the build script has been substantially rewritten. One of the important changes is restricting write access where convenient, to harden things up, and making it easy to perform further hardening after that.
I believe I’ve got it all right so that new installations and upgrades alike should work properly, but I don’t have a genuine 3.4.0 installation to upgrade from and am disinclined to do the extra work to get one going, so you lot are all guinea-pigs! Consider something like tar caf matomo-backup.tar.xz /usr/share/webapps/matomo /etc/webapps/matomo for safety.
For more notes on what has changed in the packaging since 3.4.0, see the commit message on ff3f2bdccdeb.
ChrisMorgan commented on 2018-07-12 00:45 (UTC)
I’ve made various changes to this locally, to update it and improve various things about the packaging and functionality.
Could I please be made a maintainer so I can update the package?
coderobe commented on 2018-04-01 19:05 (UTC)
should probably use <https://builds.matomo.org/> instead of <https://builds.piwik.org/> for future-proofing ;)
Pinned Comments
C0rn3j commented on 2020-06-09 06:52 (UTC) (edited on 2022-03-11 12:01 (UTC) by C0rn3j)
GPG key changed with 4.8.0 release!
You need to import the public key before installing:
gpg --recv-keys F529A27008477483777FC23D63BB30D0E5D2C749For versions before 4.8.0 you need the old key:
gpg --recv-keys 814E346FA01A20DBB04B6807B5DBD5925590A237