Bug#527641: Package installation overwrites /etc/default/console-setup without warning
On Wed, May 20, 2009 at 12:45:55PM +0200, Raphael Hertzog wrote: > > Well, when I reported #528033, something had lost my "bepo" setting > on upgrade without me doing dpkg-reconfigure console-setup. I assumed > it was already reported since 527641 said "Package installation overwrites > /etc/default/console-setup without warning" in its title. Thas was > consistent with what I saw: /etc/default/console-setup had been > modified/overwritten without my consent to something that did not match my > manual configuration. I didn't see how you adressed that by supporting > empty values... so I reopened the bug. You are right. #528033 was completely different problem and it was fixed by this: * Escape commas in Debconf questions. Thanks to Raphaël Hertzog, closes: #528033. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#527641: Package installation overwrites /etc/default/console-setup without warning
notfound 527641 1.35 notfound 527641 1.36 retitle 527641 doesn't support/keep undefined FONT* parameters close 527641 1.35 On Wed, 20 May 2009, Anton Zinoviev wrote: > If you have found the bug in versions 1.35 and 1.36, please provide more > information: is this reproduced behaviour, how did it occur, what was > the contents of the configuration file before and after it was > overwriten, etc. I did this only to reopen the bug. > > This is the real problem this bug is about... so closing it with this > > explanation: > > >* Support unset font in Debconf configurator. Thanks Dave Witbrodt, > > > closes: #527641. > > This documents how I fixed the problem discovered by Dave Witbrodt. You > must have found a completely different problem and thats why I am asking > for more information. Well, when I reported #528033, something had lost my "bepo" setting on upgrade without me doing dpkg-reconfigure console-setup. I assumed it was already reported since 527641 said "Package installation overwrites /etc/default/console-setup without warning" in its title. Thas was consistent with what I saw: /etc/default/console-setup had been modified/overwritten without my consent to something that did not match my manual configuration. I didn't see how you adressed that by supporting empty values... so I reopened the bug. Now looking closer, it looks like console-setup's config script feed the values of the config file in debconf and then reuse those to update only the corresponding lines. So it's not as bad as I thought it was. I tried to reproduce the problem but did not manage to do it. I'll close the bug again. Cheers, -- Raphaël Hertzog Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny : http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed (with 5 errors): Re: Bug#527641: Package installation overwrites /etc/default/console-setup without warning
Processing commands for cont...@bugs.debian.org: > notfound 527641 1.35 Bug#527641: Package installation overwrites /etc/default/console-setup without warning Bug no longer marked as found in version 1.35. > notfound 527641 1.36 Bug#527641: Package installation overwrites /etc/default/console-setup without warning Bug no longer marked as found in version 1.36. > retitle 527641 doesn't support/keep undefined FONT* parameters Bug#527641: Package installation overwrites /etc/default/console-setup without warning Changed Bug title to `doesn't support/keep undefined FONT* parameters' from `Package installation overwrites /etc/default/console-setup without warning'. > close 527641 1.35 Bug#527641: doesn't support/keep undefined FONT* parameters 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.35, send any further explanations to Dave Witbrodt > On Wed, 20 May 2009, Anton Zinoviev wrote: Unknown command or malformed arguments to command. > > If you have found the bug in versions 1.35 and 1.36, please provide more Unknown command or malformed arguments to command. > > information: is this reproduced behaviour, how did it occur, what was Unknown command or malformed arguments to command. > > the contents of the configuration file before and after it was Unknown command or malformed arguments to command. > > overwriten, etc. Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#527641: Package installation overwrites /etc/default/console-setup without warning
On Wed, May 20, 2009 at 10:21:10AM +0200, Raphael Hertzog wrote: > found 527641 1.35 > found 527641 1.36 > thanks If you have found the bug in versions 1.35 and 1.36, please provide more information: is this reproduced behaviour, how did it occur, what was the contents of the configuration file before and after it was overwriten, etc. > This is the real problem this bug is about... so closing it with this > explanation: > >* Support unset font in Debconf configurator. Thanks Dave Witbrodt, > > closes: #527641. This documents how I fixed the problem discovered by Dave Witbrodt. You must have found a completely different problem and thats why I am asking for more information. > To fix it, you have to: > 1/ document in the file that it's auto-updated based on the debconf infos >and that dpkg-reconfigure console-setup is recommended to update it The use of dpkg-reconfigure is optional. Console-setup is not supposed to overwrite its configuration file. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#527641: Package installation overwrites /etc/default/console-setup without warning
On Wednesday 20 May 2009, Raphael Hertzog wrote: > To fix it, you have to: > 1/ document in the file that it's auto-updated based on the debconf > infos and that dpkg-reconfigure console-setup is recommended to update > it 2/ use ucf or something similar to detect if the file has been > edited by the user since last generation and avoid overwriting the file > in that case (ucf like dpkg let the user choose what to do in that > case) It sounds like c-s is using debconf as a registry. If that is the case, it is just plain wrong. Configuration scripts should read the current settings from the configuration file(s) and set the defaults for debconf questions based on that, and not just display the current value in the debconf database. From debconf-devel(7): [...] The issue to watch out for here is that debconf is not intended to be, and must not be used as a registry. This is unix after all, and programs are configured by files in /etc, not by some nebulous debconf database (that is only a cache anyway and might get blown away). [...] See also the example under "Config file handling" in the same man page. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#527641: Package installation overwrites /etc/default/console-setup without warning
found 527641 1.35 found 527641 1.36 thanks On Fri, 08 May 2009, Dave Witbrodt wrote: > I have set the severity of this bug report to "serious" because, > technically, it is a policy violation to overwrite user changes to file > in /etc; This is the real problem this bug is about... so closing it with this explanation: >* Support unset font in Debconf configurator. Thanks Dave Witbrodt, > closes: #527641. is not correct. To fix it, you have to: 1/ document in the file that it's auto-updated based on the debconf infos and that dpkg-reconfigure console-setup is recommended to update it 2/ use ucf or something similar to detect if the file has been edited by the user since last generation and avoid overwriting the file in that case (ucf like dpkg let the user choose what to do in that case) Cheers, -- Raphaël Hertzog Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny : http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#527641: Package installation overwrites /etc/default/console-setup without warning
Processing commands for cont...@bugs.debian.org: > found 527641 1.35 Bug#527641: Package installation overwrites /etc/default/console-setup without warning Bug marked as found in version 1.35 and reopened. > found 527641 1.36 Bug#527641: Package installation overwrites /etc/default/console-setup without warning Bug marked as found in version 1.36. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#527641: Package installation overwrites /etc/default/console-setup without warning
Package: console-setup Version: 1.34 Severity: serious Justification: Policy 10.7.3 My last upgrade of 'console-setup' caused /etc/default/console-setup to be overwritten without warning. The contents of the file before being overwritten were : # A configuration file for setupcon # Change to "yes" and setupcon will explain what is being doing VERBOSE_OUTPUT=no # Setup these consoles. Most people do not need to change this. ACTIVE_CONSOLES="/dev/tty[1-6]" # Put here your encoding. Valid charmaps are: UTF-8 ARMSCII-8 CP1251 # CP1255 CP1256 GEORGIAN-ACADEMY GEORGIAN-PS IBM1133 ISIRI-3342 # ISO-8859-1 ISO-8859-2 ISO-8859-3 ISO-8859-4 ISO-8859-5 ISO-8859-6 # ISO-8859-7 ISO-8859-8 ISO-8859-9 ISO-8859-10 ISO-8859-11 ISO-8859-13 # ISO-8859-14 ISO-8859-15 ISO-8859-16 KOI8-R KOI8-U TIS-620 VISCII CHARMAP="UTF-8" # The codeset determines which symbols are supported by the font. # Valid codesets are: Arabic Armenian CyrAsia CyrKoi CyrSlav Ethiopian # Georgian Greek Hebrew Lao Lat15 Lat2 Lat38 Lat7 Thai Uni1 Uni2 Uni3 # Vietnamese. Read README.fonts for explanation. CODESET="Lat15" # Valid font faces are: VGA (sizes 8, 14 and 16), Terminus (sizes # 12x6, 14, 16, 20x10, 24x12, 28x14 and 32x16), TerminusBold (sizes # 14, 16, 20x10, 24x12, 28x14 and 32x16), TerminusBoldVGA (sizes 14 # and 16), Fixed (sizes 13, 14, 15, 16 and 18), Goha (sizes 12, 14 and # 16), GohaClassic (sizes 12, 14 and 16). FONTFACE= FONTSIZE= # You can also directly specify nonstandard font and ACM to load. # Use space as separator if you want to load more than one font. # FONT='lat9w-08.psf.gz /usr/local/share/brailefonts/brl-08.psf' # ACM=/usr/local/share/consoletrans/my_special_encoding.acm # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL="pc104" XKBLAYOUT="us" XKBVARIANT="" XKBOPTIONS="" After installing the update, my edited version of the file was lost and the default file from the package had been written in its place. I have since manually restored my preferred settings, but a 'diff' between the package's default file and my preferred settings looks like this: 27,28c27,28 < FONTFACE="Fixed" < FONTSIZE="16" --- > FONTFACE= > FONTSIZE= Also please note that recent changes to 'console-setup' were made on my behalf, and the current bug may well be related to loose strings regarding those changes. I carried out experimentation last year with many things, two of which were: building custom kernels, and configuring my virtual terminals to my own liking. In the course of those experiments, I discovered that the kernel font called "10x18" provided a balance of readability with maximizing the amount of information that could be fit on one screen. At that time, I discovered that another package, 'console-tools', was replacing the kernel font with software fonts once the Debian boot scripts were run. However, the 'console-tools' configuration allowed for settings which would prevent the software font from being loaded -- allowing me to use the desired kernel font. The recent changes to 'xserver-xorg' brought in the 'console-setup' package as a new dependency. I found that 'console-setup' was loading software fonts at boot time, and found no mechanism for allowing the kernel font to be left in place. I assumed that this was not a bug, and posted a question to debian-b...@lists.debian.org asking whether 'console-setup' had a mechanism that would allow me to continue using the kernel font on my virtual terminals. Colin Watson responded by creating a patch for me to test which would allow the behavior seen with 'console-tools': leaving FONTFACE and FONTSIZE undefined in /etc/default/console-setup would prevent a software font from being loaded by 'setupcon', and the kernel font would be left in place. I was running with the patched 'setupcon' on my system when the update of 'console-setup' appeared. At the next reboot, I found that my changes to /etc/default/console-setup were gone. I have set the severity of this bug report to "serious" because, technically, it is a policy violation to overwrite user changes to file in /etc; feel free to lower the severity if you folks want to put this bug on the back burner -- since it's not exactly a pressing matter. My concern, in setting this bug to "serious," is that other folks might also have their changes overwritten (if they make any). Please note that some of the debconf output displayed below is misleading. For example, these particular settings, console-setup/fontsize-text: 16 [...] console-setup/fontsize: 16 [...] console-setup/fontsize-fb: 16 make no sense given that my virtual terminal font is actually 10x18, instead of something typical like 8x16. Clearly these values are not fr
