Bug#220469: xserver-xfree86: dpkg-reconfigure should create the config file if it doesn't exist
On Fri, Nov 14, 2003 at 02:59:08AM +0100, Uwe Storbeck wrote: Hi Branden But if the config file doesn't exist dpkg-reconfigure should create a new one instead of refusing to write it: Why? dpkg works the same way. If you delete a conffile it will respect your (apparent) wishes. Ooops, that's new to me. If I change a config file I would expect dpkg to protect it, ok. But removing a config file and reconfiguring the package means give me a new one for me. I am not sure there is universal agreement on that, however it is true that we (as a Project) need to be defining some semantics for it. I just have checked a few packages, which I remember asking for configuration during installation. Selection is probably not representative. I have moved away the config file and have reconfigured each package after this: [...] Opinions seem to vary, even between Debian maintainers ;-). That's usually what happens when there are no defined semantics. If you are playing around with different options or even different graphic cards and want to start from scratch with a new config file, save the pre-created one in a safe location, and move it back when you're done. Yes, of course I can do this. But first it doesn't make much sense to save a configuration which is already stored by debconf Debconf doesn't store a config file, it stores settings. If you change those settings, how are you going to get the old ones back? and second I mostly forget to save the file before changing it :-). There's not much help for this except better habits. :) It only was an idea to make life easier. Treat it as a wish as you already have done. There are much more important things to do like porting version 4.4 of XFree86 ;-). Actually I think an overhaul of the xserver-xfree86 debconfage is pretty important. But it's not a goal for 4.3.0-1. -- G. Branden Robinson|The errors of great men are Debian GNU/Linux |venerable because they are more [EMAIL PROTECTED] |fruitful than the truths of little http://people.debian.org/~branden/ |men. -- Friedrich Nietzsche signature.asc Description: Digital signature
Bug#220469: xserver-xfree86: dpkg-reconfigure should create the config file if it doesn't exist
severity 220469 wishlist thanks On Wed, Nov 12, 2003 at 11:05:07PM +0100, Uwe Storbeck wrote: Package: xserver-xfree86 Version: 4.2.1-12.1 Severity: minor Hi, I like the idea protecting changes in the XF86Config-4 config file by a md5-sum. But if the config file doesn't exist dpkg-reconfigure should create a new one instead of refusing to write it: Why? dpkg works the same way. If you delete a conffile it will respect your (apparent) wishes. # dpkg-reconfigure xserver-xfree86 Note: not updating /etc/X11/XF86Config-4; file does not exist. If you are playing around with different options or even different graphic cards and want to start from scratch with a new config file you have to remove and reinstall the xserver-package (or at least with knowledge of package internals to recreate the md5-file). Removing the config file would be the much easier way. If you are playing around with different options or even different graphic cards and want to start from scratch with a new config file, save the pre-created one in a safe location, and move it back when you're done. BTW: Getting the warning about a changed config file BEFORE going through all the config questions would be nice. But maybe the config mechanism doesn't have the ability to distinguish between the package installation and a run of dpkg-reconfigure? I plan to revisit the xserver-xfree86 debconfage after 4.3.0-1 is released to unstable. -- G. Branden Robinson| It just seems to me that you are Debian GNU/Linux | willfully entering an arse-kicking [EMAIL PROTECTED] | contest with a monstrous entity http://people.debian.org/~branden/ | that has sixteen legs and no arse. signature.asc Description: Digital signature
Processed: Re: Bug#220469: xserver-xfree86: dpkg-reconfigure should create the config file if it doesn't exist
Processing commands for [EMAIL PROTECTED]: severity 220469 wishlist Bug#220469: xserver-xfree86: dpkg-reconfigure should create the config file if it doesn't exist Severity set to `wishlist'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#220469: xserver-xfree86: dpkg-reconfigure should create the config file if it doesn't exist
Hi Branden But if the config file doesn't exist dpkg-reconfigure should create a new one instead of refusing to write it: Why? dpkg works the same way. If you delete a conffile it will respect your (apparent) wishes. Ooops, that's new to me. If I change a config file I would expect dpkg to protect it, ok. But removing a config file and reconfiguring the package means give me a new one for me. I just have checked a few packages, which I remember asking for configuration during installation. Selection is probably not representative. I have moved away the config file and have reconfigured each package after this: ntpdate: config file will be recreated, previous configured values appears as defaults for config questions gpm: config file will be recreated, but old configuration values get lost (probably not handled by debconf?) exim:config file will be recreated, old configuration values also get lost Opinions seem to vary, even between Debian maintainers ;-). If you are playing around with different options or even different graphic cards and want to start from scratch with a new config file, save the pre-created one in a safe location, and move it back when you're done. Yes, of course I can do this. But first it doesn't make much sense to save a configuration which is already stored by debconf and second I mostly forget to save the file before changing it :-). It only was an idea to make life easier. Treat it as a wish as you already have done. There are much more important things to do like porting version 4.4 of XFree86 ;-). Cheers, Uwe
Bug#220469: xserver-xfree86: dpkg-reconfigure should create the config file if it doesn't exist
Package: xserver-xfree86 Version: 4.2.1-12.1 Severity: minor Hi, I like the idea protecting changes in the XF86Config-4 config file by a md5-sum. But if the config file doesn't exist dpkg-reconfigure should create a new one instead of refusing to write it: # dpkg-reconfigure xserver-xfree86 Note: not updating /etc/X11/XF86Config-4; file does not exist. If you are playing around with different options or even different graphic cards and want to start from scratch with a new config file you have to remove and reinstall the xserver-package (or at least with knowledge of package internals to recreate the md5-file). Removing the config file would be the much easier way. Uwe BTW: Getting the warning about a changed config file BEFORE going through all the config questions would be nice. But maybe the config mechanism doesn't have the ability to distinguish between the package installation and a run of dpkg-reconfigure? -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux coruba 2.4.21 #1 Sun Jun 15 03:15:21 CEST 2003 i686 Versions of packages xserver-xfree86 depends on: ii debconf 1.3.15 Debian configuration management sy ii libc6 2.3.2-9GNU C Library: Shared libraries an ii xserver-common4.2.1-12.1 files and utilities common to all ii zlib1g1:1.1.4-16 compression library - runtime
