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

+- PINE64 (https://forum.pine64.org)
+-- Forum: PINE A64(+) (https://forum.pine64.org/forumdisplay.php?fid=4)
+--- Forum: Linux on Pine A64(+) (https://forum.pine64.org/forumdisplay.php?fid=6)
+---- Forum: Ubuntu (https://forum.pine64.org/forumdisplay.php?fid=27)
+---- Thread: Pine as a Pi-hole ... Does that make it a PineHole? (/showthread.php?tid=829)

Pages: 1 2

RE: Pine as a Pi-hole ... Does that make it a PineHole? - DanSchaper - 01-23-2017

(01-22-2017, 06:38 PM)auger Wrote: Thanks. It does indeed look like it's failing at the update. 

Code:
::: Updating local cache of available packages...+ apt-get update

Try running the `apt` update and that should give you any errors that are occurring and I'll see about adding some more information when the script fails to give you the error that was generated instead of just dropping back to the shell prompt.

RE: Pine as a Pi-hole ... Does that make it a PineHole? - auger - 01-23-2017

(01-23-2017, 12:50 PM)DanSchaper Wrote:
(01-22-2017, 06:38 PM)auger Wrote: Thanks. It does indeed look like it's failing at the update. 

Code:
::: Updating local cache of available packages...+ apt-get update

Try running the `apt` update and that should give you any errors that are occurring and I'll see about adding some more information when the script fails to give you the error that was generated instead of just dropping back to the shell prompt.

Code:
s@pine64:~$ sudo apt update
[sudo] password for s:
Hit:1 http://ppa.launchpad.net/longsleep/ubuntu-pine64-flavour-makers/ubuntu xenial InRelease
Hit:2 http://ports.ubuntu.com xenial InRelease                                                          
Hit:3 http://repo.ajenti.org/debian main InRelease                                                      
Ign:4 http://ppa.launchpad.net/marutter/rdev/ubuntu xenial InRelease              
Get:5 http://ports.ubuntu.com xenial-updates InRelease [102 kB]          
Hit:6 http://ppa.launchpad.net/marutter/rrutter/ubuntu xenial InRelease            
Ign:7 http://ppa.launchpad.net/relan/exfat/ubuntu xenial InRelease                  
Get:8 https://downloads.plex.tv/repo/deb public InRelease [3,408 B]                
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
Get:11 http://ports.ubuntu.com xenial-security InRelease [102 kB]      
Hit:12 http://ports.ubuntu.com xenial-backports InRelease      
Get:13 http://ports.ubuntu.com/ubuntu-ports xenial-proposed InRelease [253 kB]
Ign:14 https://cran.cnr.berkeley.edu//bin/linux/debian jessie-cran3/ InRelease
Hit:15 https://cran.cnr.berkeley.edu//bin/linux/debian jessie-cran3/ Release
Get:16 https://cran.cnr.berkeley.edu//bin/linux/debian jessie-cran3/ Release.gpg [181 B]
Get:17 http://ports.ubuntu.com xenial-updates/main Sources [217 kB]
Get:18 http://ports.ubuntu.com xenial-updates/main arm64 Packages [410 kB]
Get:19 http://ports.ubuntu.com xenial-updates/main armhf Packages [422 kB]          
Get:20 http://ports.ubuntu.com xenial-updates/main Translation-en [180 kB]          
Get:21 http://ports.ubuntu.com xenial-updates/universe arm64 Packages [350 kB]            
Get:22 http://ports.ubuntu.com xenial-updates/universe armhf Packages [346 kB]      
Hit:23 https://dev2day.de/pms jessie InRelease                                      
Get:24 http://ports.ubuntu.com xenial-updates/universe Translation-en [141 kB]        
Get:25 http://ports.ubuntu.com xenial-security/main Sources [54.9 kB]                      
Get:26 http://ports.ubuntu.com xenial-security/main arm64 Packages [167 kB]                
Get:27 http://ports.ubuntu.com xenial-security/main armhf Packages [176 kB]      
Get:28 http://ports.ubuntu.com xenial-security/main Translation-en [84.6 kB]                  
Get:29 http://ports.ubuntu.com xenial-security/universe arm64 Packages [72.8 kB]                      
Get:30 http://ports.ubuntu.com xenial-security/universe armhf Packages [70.9 kB]                
Get:31 http://ports.ubuntu.com xenial-security/universe Translation-en [38.2 kB]          
Get:32 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main arm64 Packages [91.1 kB]        
Ign:16 https://cran.cnr.berkeley.edu//bin/linux/debian jessie-cran3/ Release.gpg          
Get:33 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main armhf Packages [93.6 kB]
Get:34 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main Translation-en [39.1 kB]
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!

RE: Pine as a Pi-hole ... Does that make it a PineHole? - DanSchaper - 01-25-2017

(01-23-2017, 02:37 PM)auger Wrote:
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.

RE: Pine as a Pi-hole ... Does that make it a PineHole? - auger - 01-26-2017

(01-25-2017, 12:55 PM)DanSchaper Wrote:
(01-23-2017, 02:37 PM)auger Wrote:
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.

Thanks for the help. I cleaned up my apt and now we're up and running. So long, ads!