Bug#1051822: installed chrony package post-installation script subprocess returned error exit status 1
On Thu, 2023-09-14 13:14:47 +0200, Vincent Blut wrote: > diff -Nru chrony-4.4/debian/changelog chrony-4.4/debian/changelog > --- chrony-4.4/debian/changelog 2023-08-09 17:50:42.0 +0200 > +++ chrony-4.4/debian/changelog 2023-09-14 12:02:21.0 +0200 > @@ -1,3 +1,10 @@ > +chrony (4.4-2) unstable; urgency=medium > + > + * debian/control: > +- Add version constraint on adduser. (Closes: #1051822) > + > + -- Vincent Blut Thu, 14 Sep 2023 12:02:21 +0200 > + > chrony (4.4-1) unstable; urgency=medium > >* Import upstream version 4.4: > diff -Nru chrony-4.4/debian/control chrony-4.4/debian/control > --- chrony-4.4/debian/control 2023-08-09 17:50:42.0 +0200 > +++ chrony-4.4/debian/control 2023-09-14 12:02:21.0 +0200 > @@ -25,7 +25,7 @@ > Package: chrony > Architecture: linux-any > Pre-Depends: ${misc:Pre-Depends} > -Depends: adduser, > +Depends: adduser (>= 3.130), > iproute2 [linux-any], > tzdata-legacy, > ucf, > diff -Nru chrony-4.4/debian/.gitlab-ci.yml chrony-4.4/debian/.gitlab-ci.yml > --- chrony-4.4/debian/.gitlab-ci.yml 2023-08-09 17:50:42.0 +0200 > +++ chrony-4.4/debian/.gitlab-ci.yml 2023-09-14 12:02:21.0 +0200 > @@ -4,8 +4,6 @@ > - > https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml > > variables: > -# chrony now depends on tzdata-legacy which is only available in > experimental > -RELEASE: 'experimental' > # Skip the reprotest job as long as it is run as root due to problems > with > # chrony system tests. > SALSA_CI_DISABLE_REPROTEST: 1 That fixed this bug for me. Thank you, Aníbal
Bug#1051822: installed chrony package post-installation script subprocess returned error exit status 1
On Wed, 2023-09-13 15:15:10 +0200, Vincent Blut wrote: > Control: tags -1 + moreinfo > > Hi Anibal, > > Le 2023-09-13 13:52, Anibal Monsalve Salazar a écrit : >> Package: chrony >> Version: 4.2-2 >> Severity: critical >> >> # dpkg -i /mnt/apt/archives/chrony_4.4-1_i386.deb >> (Reading database ... 34682 files and directories currently installed.) >> Preparing to unpack .../archives/chrony_4.4-1_i386.deb ... >> Failed to stop chronyd-restricted.service: Unit chronyd-restricted.service >> not loaded. >> Unpacking chrony (4.4-1) over (4.3-4) ... >> Setting up chrony (4.4-1) ... >> Unknown option: comment >> adduser [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID] >> [--firstuid ID] [--lastuid ID] [--gecos GECOS] [--ingroup GROUP | --gid ID] >> [--disabled-password] [--disabled-login] [--add_extra_groups] USER >>Add a normal user >> >> adduser --system [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID] >> [--gecos GECOS] [--group | --ingroup GROUP | --gid ID] [--disabled-password] >> [--disabled-login] [--add_extra_groups] USER >>Add a system user >> >> adduser --group [--gid ID] GROUP >> addgroup [--gid ID] GROUP >>Add a user group >> >> addgroup --system [--gid ID] GROUP >>Add a system group >> >> adduser USER GROUP >>Add an existing user to an existing group >> >> general options: >> --quiet | -q don't give process information to stdout >> --force-badname allow usernames which do not match the >> NAME_REGEX configuration variable >> --help | -h usage message >> --version | -vversion number and copyright >> --conf | -c FILE use FILE as configuration file >> >> dpkg: error processing package chrony (--install): >> installed chrony package post-installation script subprocess returned error >> exit status 1 >> Processing triggers for man-db (2.11.2-3) ... >> Errors were encountered while processing: >> chrony > > I don't seem to be able to reproduce this issue. Could you please give me more > information on the system on which you were upgrading chrony? It seems you > were > upgrading from chrony 4.3-4, so I guess this system is running > testing/unstable‽ > > Cheers, > Vincent Dear Vincent, I tried again to upgrade chrony on another machine and it failed. Setting up chrony (4.4-1) ... Unknown option: comment adduser [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID] [--firstuid ID] [--lastuid ID] [--gecos GECOS] [--ingroup GROUP | --gid ID] [--disabled-password] [--disabled-login] [--add_extra_groups] USER Add a normal user adduser --system [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID] [--gecos GECOS] [--group | --ingroup GROUP | --gid ID] [--disabled-password] [--disabled-login] [--add_extra_groups] USER Add a system user adduser --group [--gid ID] GROUP addgroup [--gid ID] GROUP Add a user group addgroup --system [--gid ID] GROUP Add a system group adduser USER GROUP Add an existing user to an existing group general options: --quiet | -q don't give process information to stdout --force-badname allow usernames which do not match the NAME_REGEX configuration variable --help | -h usage message --version | -vversion number and copyright --conf | -c FILE use FILE as configuration file dpkg: error processing package chrony (--configure): installed chrony package post-installation script subprocess returned error exit status 1 ... Errors were encountered while processing: chrony E: Sub-process /usr/bin/dpkg returned an error code (1) $ dpkg -l adduser chrony Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ri adduser3.118all add and remove users and groups iF chrony 4.4-1i386 Versatile implementation of the Network Time Protocol I know updating adduser from 3.118 to 3.137 will fix this bug. I tried dpkg -i chrony_4.4-1_i386.deb with the same messages above. I did not upgrade adduser this time. I suggest to replace line 28 in debian/control as follows: --- control 2023-09-14 13:52:34.323543535 +1000 +++ control 2023-09-14 13:55:18.960189965 +1000 @@ -25,7 +25,7 @@ Rules-Requires-Root: no Package: chrony Architecture: linux-any Pre-Depends: ${misc:Pre-Depends} -Depends: adduser, +Depends: adduser (>= 3.137), iproute2 [linux-any], tzdata-legacy, ucf, I will not touch the machine and will install any test package from you. Please let me know what would you like me to do. Thank you for your time and for helping me with this bug. Kind regards, Aníbal
Bug#1051822: installed chrony package post-installation script subprocess returned error exit status 1
Control: tags -1 + moreinfo Hi Anibal, Le 2023-09-13 13:52, Anibal Monsalve Salazar a écrit : > Package: chrony > Version: 4.2-2 > Severity: critical > > # dpkg -i /mnt/apt/archives/chrony_4.4-1_i386.deb > (Reading database ... 34682 files and directories currently installed.) > Preparing to unpack .../archives/chrony_4.4-1_i386.deb ... > Failed to stop chronyd-restricted.service: Unit chronyd-restricted.service > not loaded. > Unpacking chrony (4.4-1) over (4.3-4) ... > Setting up chrony (4.4-1) ... > Unknown option: comment > adduser [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID] > [--firstuid ID] [--lastuid ID] [--gecos GECOS] [--ingroup GROUP | --gid ID] > [--disabled-password] [--disabled-login] [--add_extra_groups] USER >Add a normal user > > adduser --system [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID] > [--gecos GECOS] [--group | --ingroup GROUP | --gid ID] [--disabled-password] > [--disabled-login] [--add_extra_groups] USER >Add a system user > > adduser --group [--gid ID] GROUP > addgroup [--gid ID] GROUP >Add a user group > > addgroup --system [--gid ID] GROUP >Add a system group > > adduser USER GROUP >Add an existing user to an existing group > > general options: > --quiet | -q don't give process information to stdout > --force-badname allow usernames which do not match the > NAME_REGEX configuration variable > --help | -h usage message > --version | -vversion number and copyright > --conf | -c FILE use FILE as configuration file > > dpkg: error processing package chrony (--install): > installed chrony package post-installation script subprocess returned error > exit status 1 > Processing triggers for man-db (2.11.2-3) ... > Errors were encountered while processing: > chrony I don't seem to be able to reproduce this issue. Could you please give me more information on the system on which you were upgrading chrony? It seems you were upgrading from chrony 4.3-4, so I guess this system is running testing/unstable‽ Cheers, Vincent signature.asc Description: PGP signature
Bug#1051822: installed chrony package post-installation script subprocess returned error exit status 1
Installing adduser (3.137) fixed this bug for me. Maybe there is a missing dependency on adduser (3.137).
Bug#1051822: installed chrony package post-installation script subprocess returned error exit status 1
Package: chrony Version: 4.2-2 Severity: critical # dpkg -i /mnt/apt/archives/chrony_4.4-1_i386.deb (Reading database ... 34682 files and directories currently installed.) Preparing to unpack .../archives/chrony_4.4-1_i386.deb ... Failed to stop chronyd-restricted.service: Unit chronyd-restricted.service not loaded. Unpacking chrony (4.4-1) over (4.3-4) ... Setting up chrony (4.4-1) ... Unknown option: comment adduser [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID] [--firstuid ID] [--lastuid ID] [--gecos GECOS] [--ingroup GROUP | --gid ID] [--disabled-password] [--disabled-login] [--add_extra_groups] USER Add a normal user adduser --system [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID] [--gecos GECOS] [--group | --ingroup GROUP | --gid ID] [--disabled-password] [--disabled-login] [--add_extra_groups] USER Add a system user adduser --group [--gid ID] GROUP addgroup [--gid ID] GROUP Add a user group addgroup --system [--gid ID] GROUP Add a system group adduser USER GROUP Add an existing user to an existing group general options: --quiet | -q don't give process information to stdout --force-badname allow usernames which do not match the NAME_REGEX configuration variable --help | -h usage message --version | -vversion number and copyright --conf | -c FILE use FILE as configuration file dpkg: error processing package chrony (--install): installed chrony package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.11.2-3) ... Errors were encountered while processing: chrony