Control: severity -1 normal
Control: tag -1 + moreinfo
20.04.2022 14:11, Vincent Lefevre wrote:
Package: unbound
Version: 1.15.0-3
Severity: important
In the upgrade to unbound 1.15.0-3, I chose to replace the script
to the default one (following the recent discussions, I intend to
revert to the default status):
Configuration file '/etc/resolvconf/update.d/unbound'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** unbound (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/resolvconf/update.d/unbound ...
Installing new version of config file /etc/unbound/unbound.conf ...
Setting up libunbound8:amd64 (1.15.0-3) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.33-7) ...
but contrary to what is said, the script is enabled by default:
-rwxr-xr-x 1 root root 1327 2022-04-19 12:54:02 /etc/resolvconf/update.d/unbound
The .deb file in debian has this file with permissions 0644. You can
see it in the build log file -- eg
https://buildd.debian.org/status/fetch.php?pkg=unbound&arch=amd64&ver=1.15.0-3&stamp=1650407026&raw=0
which has this when displaying contents of the files:
-rw-r--r-- root/root 1327 2022-04-19 10:54
./etc/resolvconf/update.d/unbound
so it comes exactly as it should, there's nothing do do there.
A possible cause might be that unbound is confused by the old status
of this script (i.e. if it was set to be executable in the past)
during the copy of the package maintainer's version.
That's a possibility, tho unbound here can not be confused, as
it does not handle conffiles. Dpkg does that.
What WAS the permissions of this file on your system before
the upgrade - was it executable (enabled) before or not?
Thanks,
/mjt
