[✓] Update local cache of available packages
[i] Existing PHP installation detected : PHP version 7.4.30
[✓] Checking for git
[✓] Checking for iproute2
[✓] Checking for whiptail
[✓] Checking for ca-certificates
[i] Checking for updates...
error: git-remote-https died of signal 4
[i] Pi-hole Core: up to date
[i] FTL: up to date
[✓] Everything is up to date!
Manually updating via GitHub does not work either. FTL was updated correctly though.
Other than this, pi-hole is running as expected.
Any idea?
Debug Token:
[Replace this text with the debug token provided from running pihole -d (or running the debug script through the web interface]
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
I just learned that git internally uses this command when fetching/pulling from remote https repos. (What we do during installation/upgrade).
There is another report here about the issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010340
(TL;DR:
So this is not really a bug in git, but a bug in GnuTLS when running QEMU with Windows as host (with Hyper-V acceleration hax or whpx).)
No, I do not use QEMU at all. Plain Debian Linux, and is has worked before without any issues.
I saw the thread compiling GIT to use OpenSSL instead of GnuTLS. But this was all related to QEMU.
I tried various things like comiling git with openSSL, using a higher version like 2.34, trying to nailing down the issue. But matter of fact, this issue needs to be solved either with git or pihole.
No way for us to do that really. We call apt-get and act on what it reports. There may be a way for apt to use the locally installed version but you would have to create a local apt package with the compiled version and dpkg -i it in.
Seems you have manually compiled some software? We use apt to install the packages that we need. If apt doesn't see your manually compiled package then there's nothing we can do to prevent apt from overwriting your manual changes.
I used the standard version provide with Debian Bullseye initially,
git version 2.30.2
That is giving the issues.
Searching through various forums, I found a hint point to a GnuTLS and that might can be circumvented by a fresh compile version of git which results in
git version 2.37.1
It does not change anything at all. And I reverted back to the standard version anyway.
