The following packages have been kept back: dhcpd5

Creating a bug report/issue

X I have searched the existing open and closed issues

Required Information

  • DietPi version | G_DIETPI_VERSION_CORE=9

G_DIETPI_VERSION_SUB=4

G_DIETPI_VERSION_RC=2

G_GITBRANCH=‘beta’

G_GITOWNER=‘MichaIng’

  • Distro version | bookworm 0
  • Kernel version | Linux DietPi 6.6.31-v8-16k+ #1766 SMP PREEMPT Fri May 24 12:15:34 BST 2024 aarch64 GNU/Linux
  • Architecture | arm64
  • SBC model | RPi 5 Model B (aarch64)
  • Power supply used | USB C power supply for RPi 5 by Raspberry
  • SD card used | 128GB SanDisk Extreme Pro

Additional Information (if applicable)

  • Software title | dhcpd5
  • Was the software title installed freshly or updated/migrated? No
  • Can this issue be replicated on a fresh installation of DietPi? I don’t know
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID

Steps to reproduce

sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade

Expected behaviour

Update software and packages

Actual behaviour

The following packages have been kept back: dhcpd5

Extra details

Trying to manually update the dhcpd5 package results in:

The following packages have unmet dependencies:

dhcpd5 : Depends: dhcpcd (>= 1:10.0.6-4~bpo12+1) but 1:9.4.1-24~deb12u3

What should I do? Should I just delete the package dhcpd5?

Two things:

  1. Do you actually use dhcpcd as DHCP client? DietPi by default uses isc-dhcp-client/dhclient. Check the network logs: journalctl -u ifup@eth0 or if you use WiFi: journalctl -u ifup@wlan0
  2. You tried to install the dhcpcd5 package from Bookworm “backports”. Was this intentional?

If you did not intentionally install dhcpcd and either no DHCP client is used (static IP), or the ISC one dhclient, purge dhcpcd:

apt autopurge dhcpcd5 dhcpcd

If you intentionally use dhcpcd, first of all purge the transitional dummy package dhcpcd5. The real package is called dhcpcd since Bookworm:

apt-mark manual dhcpcd
apt autopurge dhcpcd5

If you intentionally tried to install the backports version, do this for the real package now:

apt install -t bookworm-backports dhcpcd
1 Like

Thank you, Michal, for your input. I did not intentionally install dhcpd5; I believe this issue stems from a previous PiHole installation.

I don’t use DHCP locally, as I have a fixed IP address for the RPI5 (both IPv4 and IPv6).

I assume the dhcpd5 package is from a legacy installation.

Can I safely remove the dhcpd5 package without interrupting PiHole?

Then this seems to be a very old instance, isn’t it? Pi-hole removed its dhcpcd dependency several years ago :slightly_smiling_face:. But makes sense, then you can safely purge both packages. Yes, it won’t interrupt or tangent Pi-hole in any way.

1 Like

Thank you, Michal!
This fixed my problem.

How can I set a static ipv6 address now as /etc/dhcpcd.conf is empty now?

should be working similar to IPv4 using /etc/network/interfaces??

To be true, I never faced a use case where it was necessary to set a static IPv6 address at the host itself:

  • Every network adapter has a static MAC address based LLA (Link-Local Address).
  • For Internet access, every adapter gets a GUA (Global Unicast Address). But this must match the global prefix of the router, which is done automatically via SLAAC.
  • There are ULA’s (Unique Local Address), but it is generally recommended to not enable them, unless really required. Similarly it makes sense to let the router assign these, to assure a shared prefix is used, no conflicts etc. This is also done automatically via SLAAC, if the router has ULA’s enabled.
  • Basically IPv6 is all about very light/fast SLAAC auto-configuration, and any manual IPv6 address assignment as well as DHCPv6 are needed for edge cases only.
  • And of course, for access within your LAN, I see no reason to (explicitly) use IPv6 at all. If your router does not promote local hostnames, you can use the anyway assigned static IPv4 addresses instead.
1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.