On Tue, May 13, 2014 at 04:12:15PM -0300, Andre Felipe Machado wrote: > Hello, > I understand the reasoning, but the behaviour does not seem consistent / > coherent with expected behaviour of using preseed for clean installs. > > One expects preseed way to honor the preseed file, as the system is a fresh > install for automated deployment.
The reasoning is that the locales package is already installed and configured. It is therefore not a fresh install from the locales package point of view. > If applied over a manually installed, carefully configured system, this > behaviour is logic. But for a automated deployment using preseed, I guess not. > > When one fires an automated deployment using preseed, it is expected to honor > preseed file choices. If you use set the preseed values *before* the locales packages is installed, thus within debian-installer, this value will be honored. Alternatively I *think* that using debian-installer with the C "locale" will not install the locales package and thus that the preseeded values will be used later when the package is installed. > Is there a good way to detect the different procedures of installation? Maybe > using a predefined comment on the file registering the previously applied > procedure. If we change the behavior to trust the debconf value instead of the configuration file, users will complain that the changes in the configuration file are lost. The debconf-devel(7) manual is clear that debconf should not be used as a registery (there is even a lintian tag [1] for that), and that the configuration file should be read before running debconf and written after. Aurelien [1] http://lintian.debian.org/tags/debconf-is-not-a-registry.html -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
