fix: allow service-owned data directory during uninstall

2026-09-02 06:54:36 +08:00
parent bac10b6fdf
commit 3cedcb901b
5 changed files with 41 additions and 20 deletions
@@ -98,6 +98,20 @@ run_uninstall "$fixture" --purge-data --yes --purge-config
 [[ ! -e "$fixture/var/lib/tallynote" && ! -e "$fixture/var/lib/tallynote-backups" ]]
 [[ ! -e "$fixture/etc/tallynote" ]]

+# In production the service user owns the data directory. The target itself
+# must be accepted while its parent directories remain root-owned. This test
+# is meaningful only when the suite runs as root on a host with that account;
+# ordinary developer runs continue with the portable fixture coverage above.
+tallynote_uid=$(id -u tallynote 2>/dev/null || true)
+if [[ "$EUID" == 0 && -n "$tallynote_uid" && "$tallynote_uid" != "$(id -u)" ]]; then
+  fixture="$tmp/service-user-data"
+  make_fixture "$fixture"
+  make_systemctl "$fixture"
+  chown -R "$tallynote_uid" "$fixture/var/lib/tallynote"
+  TALLYNOTE_UNINSTALL_TEST_DATA_OWNER_UID="$tallynote_uid" run_uninstall "$fixture" --purge-data --yes
+  [[ ! -e "$fixture/var/lib/tallynote" ]]
+fi
+
 # A custom data path must not overlap the release prefix; otherwise removing
 # releases could destroy data that the default uninstall promises to keep.
 fixture="$tmp/overlap"