Arch Linux User Repository

@riskartstuck Hi, I've also had issues with adguard-cli on arch & fedora. But I don't think that this is the installation directory issue. Might be wrong on that tho, so at some point maybe I should migrate the package to different path...

My issues with certificates were all connected to the adguard-cli CA cert not installing in firefox-based browsers such as Zen Browser. I had to install these certificates manually there, but had no issues with chromium based browsers (Chrome, Helium, Vivaldi etc.).

What's your browsers, maybe this is the underlying issue here?

I've encountered some issues, based on this recent Github discussion for adguard-cli:

• https://github.com/AdguardTeam/AdGuardCLI/issues/74

• Certificates are not being installed properly

• The AdGuard team expects the binary to be installed at /opt/adguard-cli

@thebrownmamba Seems now no need to add sig file when update to v1.2.32

Hi, currently with this PKGBUILD, the "auto" proxy_mode does not work because adguard-cli.sig could not be found by the binary.

https://github.com/AdguardTeam/AdGuardCLI/issues/58

I've attempted to make an alternative PKGBUILD so that it can actually run successfully:

_scriptname="${pkgname}-${pkgver}-install.sh"

source=("${_scriptname}::https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/release/install.sh")
sha256sums=('182ea8c80423644ec49b656db82ac71d9142a72a5652b38b2266459e9b6a94ef')  

_file1="adguard-cli"
_file2="adguard-cli.sig"
_file3="adguard_root_helper"
_file4="adguard_root_helper.sig"
_file5="bash-completion.sh"
_file6="certutil"
_file7="certutil.sig"
_file8="defaults.zip"

package() {
  sed -i '/read -r response < \/dev\/tty/ i response="y"' "${_scriptname}"
  sed -i '/read -r response < \/dev\/tty/ d' "${_scriptname}"

  chmod +x "${_scriptname}"
  echo N | ./"${_scriptname}" -o "."

  cd ${srcdir}/${_file1}

  install -D "${_file1}" "${pkgdir}/usr/share/${_file1}/${_file1}"
  install -D "${_file2}" "${pkgdir}/usr/share/${_file1}/${_file2}"
  install -D "${_file3}" "${pkgdir}/usr/share/${_file1}/${_file3}"
  install -D "${_file4}" "${pkgdir}/usr/share/${_file1}/${_file4}"
  install -D "${_file5}" "${pkgdir}/usr/share/${_file1}/${_file5}"
  install -D "${_file6}" "${pkgdir}/usr/share/${_file1}/${_file6}"
  install -D "${_file7}" "${pkgdir}/usr/share/${_file1}/${_file7}"
  install -D "${_file8}" "${pkgdir}/usr/share/${_file1}/${_file8}"

}

What I did differently is that I used the original install script instead, changed the output directory of the script to the current temporary build directory, and then modified the install script so that the symlink prompt by the script is automatically accepted.

But this PKGBUILD probably contains a lot of bad practices since this is literally my first attempt at a PKGBUILD. auto proxy_mode works though, so if you have the time can you update the package so that auto proxy_mode works? Thank you!