Package: debmake-doc Version: 1.17-7 Severity: minor 1) Section 3.6 of the debmake doc says to run `adduser <your_user_name> sbuild` but there should be `sudo` at the beginning of that command.
2) It also says "Logout and login to check you are a member of sbuild group using id command." I don't know how universal this is, but if a user has done `loginctl enable-linger` or has a user-level systemd daemon configured, logging out logging back in won't work; they still won't be in the group. They would need to either reboot or run `kill -TERM -1` (NOT as root) to make all of their processes die and thereby get the user-level systemd to restart. I know you're trying to keep the guide simple so you you may not want to get into the nitty-gritty details, but perhaps it is worth mentioning that if logging out and logging back in doesn't work the user should try restarting their computer. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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) LSM: AppArmor: enabled debmake-doc depends on no packages. Versions of packages debmake-doc recommends: ii debmake 4.4.0-1 Versions of packages debmake-doc suggests: pn debian-policy <none> pn developers-reference <none> -- no debconf information
