Arch Linux User Repository

@petris Fair enough, I removed the conflicts() field for this package. Thanks!

The conflicts field should really be removed altogether for this package. This is derived from a couple different places in the wiki. First, for the PKGBUILD wiki (https://wiki.archlinux.org/title/PKGBUILD#conflicts), it says:

Note that conflicts are checked against pkgname as well as names specified in the provides array. Hence, if your package provides a foo feature, specifying foo in the conflicts array will cause a conflict between your package and all other packages that contain foo in their provides array (i.e., you do not need to specify all those conflicting package names in your conflicts array).

It then goes on to provide and example for netbeans packages.

Then, from the VCS package guidelines (https://wiki.archlinux.org/title/VCS_package_guidelines):

2.3 Conflicts and dependencies

Include what the package conflicts with and provides (e.g. for fluxbox-git: conflicts=('fluxbox') and provides=("fluxbox=${pkgver}")).

i.e., -whatever packages are supposed to have a conflicts/provides for the package that they can be used in place of (i.e. dnsproxy-git should have dnsproxy for its provides/conflicts), and the regular package without -whatever shouldn't have any.

@kemelzaidan fixed

please, add dnsproxy-git to conflicts.

The current release (0.53.1) requires go<1.21 to build.

EDIT: fixed now