Kein Update auf 4.3.2 möglich?

Hallo,
ich habe versucht das Update von V 4.3.1 auf V 4.3.2 zu installieren.
Per SSH verbunden und mit “pihole -up” den Vorgang gestartet.
Dann kommt auch Update verfügbar, usw. und wenn der Raspberry mit PI-Hole dann neu gestartet wird habe ich wieder V 4.3.1


Update Complete!
Current Pi-hole version is v4.3.1-40-ge41c4b5
Current AdminLTE version is v4.3
Current FTL version is v4.3.1


Was mache ich falsch??
grafik

Thank you for your support

cd /etc/.pihole
sudo git tag -d v4.3.2
sudo git pull

Clear browser cache and reload page.

Da ich nicht so fit bin in Linux meine Frage.
Was bewirken diese Befehle?

sudo git pull

remote: Enumerating objects: 1, done.
remote: Counting objects: 100% (1/1), done.
remote: Total 1 (delta 0), reused 1 (delta 0), pack-reused 0
Unpacking objects: 100% (1/1), done.
From https://github.com/pi-hole/pi-hole
 * [new tag]         v4.3.2     -> v4.3.2
**Already up-to-date.**
pi@raspberrypi:/etc/.pihole $ pihole -up
  [i] Checking for updates...
  [i] Pi-hole Core:	up to date
  [i] Web Interface:	up to date
  [i] FTL:		up to date

  [✓] **Everything is up to date!**

grafik
Thanks Dan !

@ Werner_Weich
Git richtig erklären kann ich nicht aber im Prinzip wurden der alte Tag gelöscht und dann die Änderungen noch einmal eingepflegt.
Aber das können dir die Linux-Spezialisten bestimmt besser erklären.

My current status and it seems I have also to use the extra commands:

# sudo pihole -up --check-only
  [i] Checking for updates...
  [i] Pi-hole Core:     update available
  [i] Web Interface:    up to date
  [i] FTL:              up to date

nobody@raspberrypi:~# sudo pihole -v
  Pi-hole version is v4.3.1 (Latest: v4.3.2)
  AdminLTE version is v4.3 (Latest: v4.3)
  FTL version is v4.3.1 (Latest: v4.3.1)

It might be the case that others wanting to update gets halfs an update.

And after the two commands:

nobody@raspberrypi:/etc/.pihole# sudo git tag -d v4.3.2
Deleted tag 'v4.3.2' (was eed1cc5)

nobody@raspberrypi:/etc/.pihole#sudo git pull
From https://github.com/pi-hole/pi-hole
 * [new tag]         v4.3.2     -> v4.3.2
Updating 1a741f6..e41c4b5
Fast-forward
 .github/FUNDING.yml                   |  4 +++
 advanced/01-pihole.conf               |  5 ----
 advanced/Scripts/query.sh             | 30 +++++++++++-----------
 advanced/Scripts/webpage.sh           | 11 +++++++-
 advanced/Templates/pihole-FTL.service |  9 ++++++-
 advanced/lighttpd.conf.debian         |  2 +-
 advanced/lighttpd.conf.fedora         |  2 +-
 automated install/basic-install.sh    | 48 +++++++++++++++++++++--------------
 automated install/uninstall.sh        | 17 ++++++++-----
 gravity.sh                            | 43 ++-----------------------------
 manpages/pihole.8                     |  2 +-
 pihole                                | 27 +++++++++-----------
 test/fedora.Dockerfile                |  2 +-
 test/test_automated_install.py        | 21 +++++++++++++++
 14 files changed, 115 insertions(+), 108 deletions(-)
 create mode 100644 .github/FUNDING.yml

nobody@raspberrypi:/etc/.pihole# sudo pihole -up --check-only
  [i] Checking for updates...
  [i] Pi-hole Core:     up to date
  [i] Web Interface:    up to date
  [i] FTL:              up to date

  [â] Everything is up to date!
nobody@raspberrypi:/etc/.pihole# sudo pihole -v
  Pi-hole version is v4.3.2 (Latest: v4.3.2)
  AdminLTE version is v4.3 (Latest: v4.3)
  FTL version is v4.3.1 (Latest: v4.3.1)

I have not yet made the update and probably could not even do an update.

The .pihole directory was duplicated before I started to poke in it,so I can return to the 4.31 version.

I don’t see why you would need to do anything with /etc/.pihole actually. You never pulled the tag with the different commit. It was an issue for about 20 minutes when the merge was completed but is not needed or advised anymore.

My fault. I thought Pi-hole FTL was also on 4.32. Did now the update and Pi-hole is now on 4.32.

AdminLTE and Pi-hole FTL are not updated, what is correct.

1 Like

Git ist für die Versionierung zuständig und wird am häufigsten für die Entwicklung von Software verwendet. Das bedeutet, dass man sich die aktuelle Version vom Repo runterladen kann.