Reproducing the bug with jammy packages, and no syslog user
ubuntu@j-frr-packaging-regression:~$ id syslog
id: ‘syslog’: no such user
ubuntu@j-frr-packaging-regression:~$ sudo apt install frr -y
(...)
Setting up frr (8.1-1ubuntu1.2) ...
Adding group `frrvty' (GID 111) ...
Done.
Adding group `frr' (GID 116) ...
Done.
Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory
Adding system user `frr' (UID 104) ...
Adding new user `frr' (UID 104) with group `frr' ...
Not creating home directory `/nonexistent'.
chown: invalid user: ‘syslog:adm’
dpkg: error processing package frr (--configure):
installed frr package post-installation script subprocess returned error exit status 1
Updating to the proposed package fixes the installation:
(...)
Preparing to unpack .../frr_8.1-1ubuntu1.3_amd64.deb ...
Unpacking frr (8.1-1ubuntu1.3) over (8.1-1ubuntu1.2) ...
Setting up frr (8.1-1ubuntu1.3) ...
addgroup: The group `frrvty' already exists as a system group. Exiting.
addgroup: The group `frr' already exists as a system group. Exiting.
Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory
The system user `frr' already exists. Exiting.
Created symlink /etc/systemd/system/multi-user.target.wants/frr.service → /lib/systemd/system/frr.service.
Setting up frr-pythontools (8.1-1ubuntu1.2) ...
Processing triggers for man-db (2.10.2-1) ...
Fresh install of the proposed package on a system without the syslog user also works:
ubuntu@j-frr-packaging-regression:~$ id syslog
id: ‘syslog’: no such user
ubuntu@j-frr-packaging-regression:~$ sudo apt install frr -y
(...)
Setting up frr (8.1-1ubuntu1.3) ...
Adding group `frrvty' (GID 111) ...
Done.
Adding group `frr' (GID 116) ...
Done.
Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory
Adding system user `frr' (UID 104) ...
Adding new user `frr' (UID 104) with group `frr' ...
Not creating home directory `/nonexistent'.
Created symlink /etc/systemd/system/multi-user.target.wants/frr.service → /lib/systemd/system/frr.service.
Setting up frr-pythontools (8.1-1ubuntu1.3) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Jammy verification
a) Specific test for this bug
Reproducing the bug with jammy packages, and no syslog user
ubuntu@ j-frr-packaging -regression: ~$ id syslog
id: ‘syslog’: no such user
ubuntu@ j-frr-packaging -regression: ~$ sudo apt install frr -y
(...)
Setting up frr (8.1-1ubuntu1.2) ...
Adding group `frrvty' (GID 111) ...
Done.
Adding group `frr' (GID 116) ...
Done.
Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory
Adding system user `frr' (UID 104) ...
Adding new user `frr' (UID 104) with group `frr' ...
Not creating home directory `/nonexistent'.
chown: invalid user: ‘syslog:adm’
dpkg: error processing package frr (--configure):
installed frr package post-installation script subprocess returned error exit status 1
ubuntu@ j-frr-packaging -regression: ~$ apt-cache policy frr br.archive. ubuntu. com/ubuntu jammy-updates/main amd64 Packages br.archive. ubuntu. com/ubuntu jammy-security/main amd64 Packages dpkg/status br.archive. ubuntu. com/ubuntu jammy/main amd64 Packages
frr:
Installed: 8.1-1ubuntu1.2
Candidate: 8.1-1ubuntu1.2
Version table:
*** 8.1-1ubuntu1.2 500
500 http://
500 http://
100 /var/lib/
8.1-1ubuntu1 500
500 http://
Updating to the proposed package fixes the installation: 8.1-1ubuntu1. 3_amd64. deb ... system/ multi-user. target. wants/frr. service → /lib/systemd/ system/ frr.service.
(...)
Preparing to unpack .../frr_
Unpacking frr (8.1-1ubuntu1.3) over (8.1-1ubuntu1.2) ...
Setting up frr (8.1-1ubuntu1.3) ...
addgroup: The group `frrvty' already exists as a system group. Exiting.
addgroup: The group `frr' already exists as a system group. Exiting.
Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory
The system user `frr' already exists. Exiting.
Created symlink /etc/systemd/
Setting up frr-pythontools (8.1-1ubuntu1.2) ...
Processing triggers for man-db (2.10.2-1) ...
ubuntu@ j-frr-packaging -regression: ~$ apt-cache policy frr br.archive. ubuntu. com/ubuntu jammy-proposed/main amd64 Packages dpkg/status br.archive. ubuntu. com/ubuntu jammy-updates/main amd64 Packages br.archive. ubuntu. com/ubuntu jammy-security/main amd64 Packages br.archive. ubuntu. com/ubuntu jammy/main amd64 Packages
frr:
Installed: 8.1-1ubuntu1.3
Candidate: 8.1-1ubuntu1.3
Version table:
*** 8.1-1ubuntu1.3 500
500 http://
100 /var/lib/
8.1-1ubuntu1.2 500
500 http://
500 http://
8.1-1ubuntu1 500
500 http://
Fresh install of the proposed package on a system without the syslog user also works: j-frr-packaging -regression: ~$ id syslog j-frr-packaging -regression: ~$ sudo apt install frr -y system/ multi-user. target. wants/frr. service → /lib/systemd/ system/ frr.service.
ubuntu@
id: ‘syslog’: no such user
ubuntu@
(...)
Setting up frr (8.1-1ubuntu1.3) ...
Adding group `frrvty' (GID 111) ...
Done.
Adding group `frr' (GID 116) ...
Done.
Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory
Adding system user `frr' (UID 104) ...
Adding new user `frr' (UID 104) with group `frr' ...
Not creating home directory `/nonexistent'.
Created symlink /etc/systemd/
Setting up frr-pythontools (8.1-1ubuntu1.3) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
ubuntu@ j-frr-packaging -regression: ~$ apt-cache policy frr br.archive. ubuntu. com/ubuntu jammy-proposed/main amd64 Packages dpkg/status br.archive. ubuntu. com/ubuntu jammy-updates/main amd64 Packages br.archive. ubuntu. com/ubuntu jammy-security/main amd64 Packages br.archive. ubuntu. com/ubuntu jammy/main amd64 Packages
frr:
Installed: 8.1-1ubuntu1.3
Candidate: 8.1-1ubuntu1.3
Version table:
*** 8.1-1ubuntu1.3 500
500 http://
100 /var/lib/
8.1-1ubuntu1.2 500
500 http://
500 http://
8.1-1ubuntu1 500
500 http://