Package Details: authelia-git 4.38.17.r0.g592ab519b-1

Git Clone URL: https://aur.archlinux.org/authelia-git.git (read-only, click to copy)
Package Base: authelia-git
Description: The Cloud ready multi-factor authentication portal for your Apps.
Upstream URL: https://github.com/authelia/authelia
Licenses: Apache-2.0
Conflicts: authelia, authelia-bin
Provides: authelia
Submitter: nightah
Maintainer: nightah (clems4ever)
Last Packager: nightah
Votes: 1
Popularity: 0.000000
First Submitted: 2020-01-24 03:53 (UTC)
Last Updated: 2024-10-30 22:51 (UTC)

Required by (0)

Sources (1)

Latest Comments

Xoepe commented on 2022-02-03 21:56 (UTC)

When installing using yay there are directory permissions. It seems the cache is being built as read-only and I was able to resolve this issue with the -modecacherw flag before -ldflags.

nightah commented on 2021-11-18 02:55 (UTC)

Thanks for providing the additional information/context. I'll fix this as part of our 4.33.0 release.

micwoj92 commented on 2021-11-18 02:09 (UTC)

I couldn't find any official documentation, but I found this https://wiki.archlinux.org/title/Talk:VCS_package_guidelines#Warn_against_trivial_pkgver_bumps.

Also here is real world example where people are against it https://github.com/Chatterino/chatterino2/discussions/2736

If you are doing this with CI then you can set it to bump on each release which I could more or less understand.

nightah commented on 2021-11-17 00:25 (UTC)

https://wiki.archlinux.org/title/VCS_package_guidelines#Guidelines stipulates it's not mandatory but does not specify that you should not. The whole build and publishing process is automated by our CI/CD.

Can you point me to any source/documentation that suggests we should not be bumping the pkgver for each commit?

micwoj92 commented on 2021-11-13 12:47 (UTC)

You are not supposed to bump pkgver each time.