Search Criteria
Package Details: coredns 1.12.1-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/coredns.git (read-only, click to copy) |
---|---|
Package Base: | coredns |
Description: | A DNS server that chains plugins |
Upstream URL: | https://github.com/coredns/coredns |
Keywords: | coredns dns |
Licenses: | Apache |
Conflicts: | coredns-bin |
Provides: | coredns |
Submitter: | arshlinux |
Maintainer: | miki (SilverRainZ, hexchain) |
Last Packager: | miki |
Votes: | 6 |
Popularity: | 0.000548 |
First Submitted: | 2017-05-23 16:16 (UTC) |
Last Updated: | 2025-04-03 06:28 (UTC) |
Dependencies (2)
- go (go-gitAUR, gcc-go-gitAUR, gcc-go-snapshotAUR, gcc-go) (make)
- make (make-gitAUR) (make)
Latest Comments
1 2 Next › Last »
miki commented on 2025-04-03 06:29 (UTC)
Should be fixed, sorry.
LiteracyFanatic commented on 2025-04-03 04:52 (UTC)
The build is failing because the manpages are actually under
src/coredns-1.12.1/man/
miki commented on 2025-04-02 11:15 (UTC)
man pages are now included.
nl6720 commented on 2025-04-02 07:00 (UTC)
None of the man pages are packaged in the built package.
miki commented on 2022-05-31 07:19 (UTC)
pkgrel reset to 1.
endre commented on 2022-05-31 06:48 (UTC)
you forgot to reset pkgrel to 1.
pkgrel
The release number. This is usually a positive integer number that allows to differentiate between consecutive builds of the same version of a package. As fixes and additional features are added to the PKGBUILD that influence the resulting package, the pkgrel should be incremented by 1. When a new version of the software is released, this value must be reset to 1.
xuanwo commented on 2021-12-06 07:01 (UTC)
@kauron, sorry for the late, I have updated the arch to
any
.xuanwo commented on 2021-12-06 07:00 (UTC)
@ddelnano I have cleanup the go build logic, please give it another try!
ddelnano commented on 2021-11-29 18:23 (UTC) (edited on 2021-11-29 18:23 (UTC) by ddelnano)
Every time I update this package with yay I run into a permission error. It seems that that the files created only have read permissions set so they fail to be removed on update.
Could this be an issue with how the package is built or related to something I'm doing?
1 2 Next › Last »