Package: mount
Version: 2.42.2-1
Severity: minor
* What led up to the situation?
Nothing I did. It's been this way quite some time, perhaps since last year or
longer.
Tumbleweed was doing it too, but it stopped there recently.
Fedora at least was doing same. I don't remember if it stopped or not.
* What exactly did you do (or not do) that was effective (or
ineffective)?
NA
* What was the outcome of this action?
NA
* What outcome did you expect instead?
NA
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (610, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 7.0.13+deb14-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mount depends on:
ii libblkid1 2.42.2-1
ii libc6 2.42-17
ii libmount1 2.42.2-1
ii libselinux1 3.10-1
ii libsmartcols1 2.42.2-1
mount recommends no packages.
Versions of packages mount suggests:
ii nfs-common 1:2.9.1-1
-- no debconf information
To reproduce:
1-edit fstab
2-reboot
3-use mount command, e.g.
# ls -gGh /etc/fstab
-rw-r--r-- 1 13K Jul 10 09:46 /etc/fstab
# uptime
13:43:23 up 59 min, 2 users, load average: 0.02, 0.06, 0.03
# date
Fri Jul 10 01:44:22 PM EDT 2026
# mount /disks/deb13
Actual Behavior:
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
# date
Fri Jul 10 01:44:22 PM EDT 2026
#
Expected behavior:
#
