Followup-For: Bug #905177
Hi,
the situation is a bit tricky for upgrades that had bind9 from squeeze
or older installed: there /etc/bind/named.conf.options was a conffile.
Which is something dpkg remembers (with an outdated md5sum). The content
of the file have been updated over time s.t. we don'
Control: tags -1 help
Am 01.08.2018 um 18:56 schrieb Andreas Beckmann:
Hi,
> Suggestion: In the preinst check whether you are upgrading from <<
> 9.11.2+dfsg-6 and whether the file matches the version installed in
> stretch (md5sum/...) and move it aside (maybe there were more possible
> files i
On 2018-08-01 18:05, Bernhard Schmidt wrote:
> So the file is there and not marked as conffile, because it has been
> created in postinst. Now in Buster the file is properly shipped as
> conffile (since commit 9ddbb41a71236815d246180b454850ec4ef7862d,
> included in 9.11.2+dfsg-6.
>
> It is only ap
Am 01.08.2018 um 12:00 schrieb Andreas Beckmann:
Hi,
I can reproduce this in a container upgrading Stretch to Buster.
Configuration file '/etc/bind/named.conf.options'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you li
Package: bind9
Version: 1:9.11.4+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As the
5 matches
Mail list logo
