Hi,
While rsyslog doesn't ship its init script anymore, ucf is still having
a reference to that script after the rsyslog upgrade.
,----
| # ls -l /var/lib/ucf/cache/*rsyslog*
| -rwxr-xr-x 1 root root 2864 5. Nov 01:24
/var/lib/ucf/cache/:etc:init.d:rsyslog
`----
For ucf, the case is clear. The configuration file is under its control
and the file was changed (deleted) and per policy, all changes to
configuration files must be preserved. So, orphan-sysvinit-scripts isn't
allowed to "overwrite" this change by creating a new file.
As a workaround, the environment variable UCF_FORCE_CONFFMISS=1 can be set
and then the upgrade will run through.
I guess, rsyslog eventually needs to de-register that file from ucf
correctly when removing the init script.
Cheers,
Dirk
Am Di, 09. Nov 2021 um 17:05:07 +0000 schrieb Matthew Vernon:
On 09/11/2021 15:45, gregor herrmann wrote:
On Tue, 09 Nov 2021 16:17:31 +0100, Adam Borowski wrote:
On two different setups, I get:
Not replacing deleted config file /etc/init.d/rsyslog
update-rc.d: error: initscript does not exist: /etc/init.d/rsyslog
dpkg: error processing package orphan-sysvinit-scripts (--configure):
installed orphan-sysvinit-scripts package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
orphan-sysvinit-scripts
Hm, I wonder if this is because rsyslog is more vigorous than it
should be about removing the init script?
[we've not seen this with any other package to date]
Matthew
