Pine as a Pi-hole ... Does that make it a PineHole?

[DanSchaper]

Code:

Err:9 http://ppa.launchpad.net/marutter/rdev/ubuntu xenial Release                
 404  Not Found
Err:10 http://ppa.launchpad.net/relan/exfat/ubuntu xenial Release                  
 404  Not Found
Reading package lists... Done                                                                
E: The repository 'http://ppa.launchpad.net/marutter/rdev/ubuntu xenial Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/relan/exfat/ubuntu xenial Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'http://repo.ajenti.org/debian main InRelease' doesn't support architecture 'arm64'
N: Skipping acquire of configured file 'ubuntu/binary-arm64/Packages' as repository 'http://repo.ajenti.org/debian main InRelease' doesn't support architecture 'arm64'
W: GPG error: https://cran.cnr.berkeley.edu//bin/linux/debian jessie-cran3/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 06F90DE5381BA480
E: The repository 'https://cran.cnr.berkeley.edu//bin/linux/debian jessie-cran3/ Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://dev2day.de/pms jessie InRelease' doesn't support architecture 'arm64'

Looks like a bunch of CRAN and Ajenti repositories that aren't compatible? Would those errors be enough to drop out of the update? Can I have it run to it ignores those?

Thanks!

Those errors are at the operating system level with Ubuntu. We can't bypass those errors as you need to have an updated system in order to install the latest versions of the packages. We don't use any PPA's or other repositories besides the official source repositories so the ones that are generating errors are from another packages installation. You may want to check the PPA and CRAN for updated repository locations.