On 2019-01-17 11:14, Adam Bolte wrote:
> On Wed, Jan 16, 2019 at 11:43:57AM +0100, Aurelien Jarno wrote:
> > I don't think the patch is correct. Debconf is not a registry, the
> > canonical location for the configuration is the configuration files, not
> > the debconf database. Quoting debconf-deve
On Wed, Jan 16, 2019 at 11:43:57AM +0100, Aurelien Jarno wrote:
> I don't think the patch is correct. Debconf is not a registry, the
> canonical location for the configuration is the configuration files, not
> the debconf database. Quoting debconf-devel(7):
>
> "The issue to watch out for here is
On 2019-01-15 12:40, Adam Bolte wrote:
> Package: tzdata
> Version: 2018i-0+deb9u1
> Followup-For: Bug #704089
>
> Dear Maintainer,
>
> This is still a problem 4 years later, and I unexpectedly found myself
> spending time to track it down when doing configuration
> management. Can we please get
Package: tzdata
Version: 2018i-0+deb9u1
Followup-For: Bug #704089
Dear Maintainer,
This is still a problem 4 years later, and I unexpectedly found myself
spending time to track it down when doing configuration
management. Can we please get the above patch applied *before* the
Buster soft-freeze o
Control: found -1 2013i-0wheezy1
Control: tags -1 patch
Dear Sébastien and Debian folks,
Am Mittwoch, den 27.03.2013, 18:41 + schrieb Sébastien Bocahu:
> Package: tzdata
> Version: 2012j-1
>
> The configuration script of the tzdata package, wich uses debconf, prevents
> non-interactive (re
Package: tzdata
Version: 2012j-1
The configuration script of the tzdata package, wich uses debconf, prevents
non-interactive (re)configuration of the package.
To reproduce:
- feed debconf with new values for tzdata keys (ex. debconf-set-selections)
- run 'dpkg-reconfigure -fnoninteractive tzdata
6 matches
Mail list logo