Package: tuptime
Version: 5.2.4
Severity: important

Hi,

The installation process in Debian now uses StateDirectory= on SystemD unit to create and manage /var/lib/tuptime, instead of creating the directory in postinst. This change was intentional (See last comment on https://github.com/rfmoz/tuptime/issues/82).

In a clean installation from the official .deb package, the directory is correctly created and permissions are set. I just checked it on two new Debian severs, one with last stable and the other with last Sid:

Test done on Debian 13.2:

root@debian13:~# uname -a
Linux debian13 6.12.57+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.57-1 (2025-11-05) x86_64 GNU/Linux
root@debian13:~# apt install tuptime
Installing:
  tuptime

Summary:
  Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 0
  Download size: 27.7 kB
  Space needed: 98.3 kB / 17.7 GB available

Get:1 http://deb.debian.org/debian trixie/main amd64 tuptime all 5.2.4 [27.7 kB]
Fetched 27.7 kB in 0s (827 kB/s)
Selecting previously unselected package tuptime.
(Reading database ... 29500 files and directories currently installed.)
Preparing to unpack .../archives/tuptime_5.2.4_all.deb ...
Unpacking tuptime (5.2.4) ...
Setting up tuptime (5.2.4) ...
Creating group '_tuptime' with GID 988.
Creating user '_tuptime' (Tuptime execution user) with UID 988 and GID 988. Created symlink '/etc/systemd/system/timers.target.wants/tuptime-sync.timer' → '/usr/lib/systemd/system/tuptime-sync.timer'. Created symlink '/etc/systemd/system/multi-user.target.wants/tuptime.service' → '/usr/lib/systemd/system/tuptime.service'.
tuptime-sync.service is a disabled or a static unit, not starting it.
Processing triggers for man-db (2.13.1-1) ...
root@debian13:~# ls -al /var/lib/tuptime/
total 16
drwxr-xr-x  2 _tuptime _tuptime 4096 Dec 18 15:22 .
drwxr-xr-x 23 root     root     4096 Dec 18 15:22 ..
-rw-r--r--  1 _tuptime _tuptime 8192 Dec 18 15:22 tuptime.db


Test done on Debian Sid:

root@debian-sid:~# uname -a
Linux debian-sid 6.17.11+deb14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.17.11-1 (2025-12-07) x86_64 GNU/Linux
root@debian-sid:~# apt install tuptime
Installing:
  tuptime

Summary:
  Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 0
  Download size: 27.7 kB
  Space needed: 98.3 kB / 17.7 GB available

Get:1 http://deb.debian.org/debian forky/main amd64 tuptime all 5.2.4 [27.7 kB]
Fetched 27.7 kB in 0s (781 kB/s)
Selecting previously unselected package tuptime.
(Reading database ... 29743 files and directories currently installed.)
Preparing to unpack .../archives/tuptime_5.2.4_all.deb ...
Unpacking tuptime (5.2.4) ...
Setting up tuptime (5.2.4) ...
Creating group '_tuptime' with GID 987.
Creating user '_tuptime' (Tuptime execution user) with UID 987 and GID 987. Created symlink '/etc/systemd/system/timers.target.wants/tuptime-sync.timer' → '/usr/lib/systemd/system/tuptime-sync.timer'. Created symlink '/etc/systemd/system/multi-user.target.wants/tuptime.service' → '/usr/lib/systemd/system/tuptime.service'.
tuptime-sync.service is a disabled or a static unit, not starting it.
Processing triggers for man-db (2.13.1-1) ...
root@debian-sid:~# ls -al /var/lib/tuptime/
total 16
drwxr-xr-x  2 _tuptime _tuptime 4096 Dec 18 15:24 .
drwxr-xr-x 23 root     root     4096 Dec 18 15:24 ..
-rw-r--r--  1 _tuptime _tuptime 8192 Dec 18 15:24 tuptime.db


Could you provide details about your environment and the steps that led to the error? The Debian CI also pases without reporting any problem.

Thanks,
Ricardo F.

Reply via email to