Your message dated Thu, 25 Dec 2025 09:33:54 +0000
with message-id <[email protected]>
and subject line Bug#1123962: fixed in dhcpcd 1:10.3.0-3
has caused the Debian Bug report #1123962,
regarding dhcpcd-base: NTP is disabled by default, leading to unsynchronized
Debian installations
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1123962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123962
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dhcpcd-base
Version: 1:10.1.0-11+deb13u1
Severity: serious
Justification: time is important
Control: affects -1 + systemd-timesyncd
Hi,
Spotted on a local CI: my bookworm hosts are NTP-synced, while my
trixie hosts are not. The installation procedure is the very same
though: netinst images and almost-all-default answers all the way.
This means having:
- ifupdown/isc-dhcp-client (dhclient) on bookworm;
- ifupdown/dhcpcd-base on trixie.
On bookworm hosts, lease information stored by dhclient include the
ntp-servers option, which trickles down to systemd-timesyncd via
/run/systemd/timesyncd.conf.d/01-dhclient.conf
On trixie hosts, that's not happening, /run/systemd/timesyncd.conf.d/
is not even present.
There's /usr/lib/dhcpcd/dhcpcd-hooks/50-timesyncd.conf though, which
would be doing the trick except… the default setting in dhcpcd-base is
the following:
| # Most distributions have NTP support.
| #option ntp_servers
This dates back to commit aa1a876387301cbfe636a3f737fde1baf7d00493 in
2017. I'm not sure what “Most distributions have NTP support.” means
in the first place, or why the default was changed, as there were no
explanations whatsoever…
See:
https://github.com/NetworkConfiguration/dhcpcd/commit/aa1a876387301cbfe636a3f737fde1baf7d00493
What I can say for sure though is that default installations that
wouldn't be able to access the default NTP servers (as in the ones
embedded in systemd-timesyncd, see also FallbackNTP=), e.g. because of
network-level restrictions, end up without NTP synchronization with the
default dhcpcd-base configuration, which is a HUGE functional regression
from bookworm.
Uncommenting the `option ntp_servers` line in /etc/dhcpcd.conf is
sufficient to fix the issue:
- /run/systemd/timesyncd.conf.d/ gets created;
- /run/systemd/timesyncd.conf.d/dhcpcd-ens18.dhcp.conf gets populated
with an NTP= entry matching what's provided by the DHCP server.
- `timedatectl` reports `System clock synchronized: yes` as well as
`NTP service: active` (as opposed to `no` and `active` resp.).
- `timedatectl show-timesync --all` now reports a non-empty
`SystemNTPServers=`.
- And of course the system isn't running anymore with one full minute
worth of offset (after 2 days of uptime)…
I strongly suggest adjusting the configuration to enable this option,
first in unstable, and then in trixie, making sure to coordinate with
the release team.
(I think that's orthogonal to #1087113 which I first glance could have
been related to this issue, except that (currently-disabled) test was
actively setting the option via the command line, so that's another
story I suppose.)
Cheers,
--
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
--- End Message ---
--- Begin Message ---
Source: dhcpcd
Source-Version: 1:10.3.0-3
Done: Martin-Éric Racine <[email protected]>
We believe that the bug you reported is fixed in the latest version of
dhcpcd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin-Éric Racine <[email protected]> (supplier of updated dhcpcd
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 25 Dec 2025 11:16:42 +0200
Source: dhcpcd
Architecture: source
Version: 1:10.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Martin-Éric Racine <[email protected]>
Changed-By: Martin-Éric Racine <[email protected]>
Closes: 1121452 1123962
Changes:
dhcpcd (1:10.3.0-3) unstable; urgency=medium
.
* [control]
= Simplify bin:dhcpcd's long description (Closes: #1121452).
* [patches]
+ Uncomment 'ntp_servers' in dhcpcd.conf (Closes: #1123962).
Checksums-Sha1:
23160ad15cc207f9af7642d06a2d61db7861818c 2401 dhcpcd_10.3.0-3.dsc
f97dacea4bf8a4a5c1578ef532c0dddbff49c494 19852 dhcpcd_10.3.0-3.debian.tar.xz
3ad6746d9a43eb7c4a7cba971e68d6133e160454 5526 dhcpcd_10.3.0-3_source.buildinfo
Checksums-Sha256:
26e34930524faccb97b07f1688fb063bab3feaabdef1ba6a8bfef0ac4284fbbc 2401
dhcpcd_10.3.0-3.dsc
888977bb7eae842472dbd8724e05d47cc352a8f0f3ab4bfbe432e09b783d3384 19852
dhcpcd_10.3.0-3.debian.tar.xz
4dd8507dec8db20d4fa5ae212b9c36dde50cbfd7fba46a2d6e6e03a5b38a72ea 5526
dhcpcd_10.3.0-3_source.buildinfo
Files:
6c0da966f2920d937cfb71b38a878378 2401 net optional dhcpcd_10.3.0-3.dsc
c6c171c86df235f0a42a3fd2dbd005aa 19852 net optional
dhcpcd_10.3.0-3.debian.tar.xz
aee6cf6c0882c1fcfa905ba7c7d9ef16 5526 net optional
dhcpcd_10.3.0-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmlNAZMACgkQrh+Cd8S0
17ZJEw/+LexcYYgtbrl3+WwFfkTBWzKgjEQAT/jFxFNvk4/l1ALE7hrudrdfWKWo
YLmvfiZx1ajqDzFWi4ZQH/EY8CMOEHh//5prdCTjOv2axIukxyiRCus+KZXNfvxE
aNFwxKW9CZwKdmf1KJ2cWj4fp/2VT2x0H4sPf6xY9/2SkI+Trq449S17XIAQTg8n
ijPO96PNoPj0YFIvvT63V3Owp1fmug6n8xHK8+nk1P2RhG+K2R0JMxA7qA5oChpq
JgIEEpy317C3AmXqNpy2C6Lil42WeXLEuK/7zit6EHVC9pyMteqYv0Ia+qpW1QRn
XyrWbJv0PFbO9MoY+nPoSjj7Mqsf1VKU0HZSR/JjHHgd64PTgrV/2fBVRtbdl2ET
cHNHiginVeLQefUGFKFwm8fsxw6KmvWfMup3S01P/ueOXje1T1MpuQHbM7SOtMRD
c/bdRwTsX+JE3fNz3OUpDVRCOHD9lICvdMoAp4XTFR1jAxgpA9w8gVhLeusMVcqw
BjNTtHQzNL4aHu91xY9h12tBw6JHMKlONYOwrXJCFdnzoVxc+IZTGjxezbAAmUGm
ePF2+IfgYnFnk5kNZILFk+v/J180Jw+vctCDtMQ9AGZ1TEG6spkEZcJZj5kuQWqM
sUjPHJvQqIBMN2S/JGzfnizjo1qBaIdlh0eI82HrFgN9Zd0HbTQ=
=BRwK
-----END PGP SIGNATURE-----
pgpuirVFiAPa2.pgp
Description: PGP signature
--- End Message ---
