Bug#411585: pinging bug
On Tue, 13 Dec 2011 22:24:05 +, Nicholas Bamber wrote: Regis, Thanks for responding. Yes I had cdebconf installed for a while and I was trying to use it. I was motivated to try it out after having issues during the recent perl transition. If cdebconf could make perl transitions smoother I think that would be a big plus in its favour. If cdebconf actually fully worked on an installed system, it would be an even better point in its favour, but I'm working on it. I would appreciate it if you would make sure that there was a bug report called something like cdebconf not ready for general use and all the issues with using cdebconf in a general way, such as this one, were marked as blocking that bug. Or perhaps all those bug reports could be tagged in some way. Well, to be fair there is one (#328498), and this bug wasn't considered a blocker. I'll probably update the description of the .deb package to make it clear that it is not production material yet. Thanks, Regis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#411585: pinging bug
Hi, On Tue, 2011-12-13 at 06:30 +, Nicholas Bamber wrote: severity 411585 important tag 411585 +confirmed thanks I am marking this bug as important and confirmed for various reasons. I am finding it with purge rather than unregister. However it seems likely that that purge is defined in terms of unregister, or at least that they share code. Unregister is realtively obscure whilst purge is always used. The debconf-devel(7) man page is fairly clear: It [purge] removes all of your package's questions from the debconf's database. I have found that this works under debconf but not cdebconf. Note however that if you restrict yourself to debconf-show it appears to work. You have to either view the cache file or reinstall a purged package to see if it failed or worked. This difference in behaviour from the documentation and the debconf implementation, is enough for me to think that this bug eport should actually be severe, but may be oters woud disagree. Should I assume that you're actually using cdebconf on a system, and not only as part of the installer ? It's only been possible to do so for a very short time, and it's not the only feature missing to make it a full replacement for debconf, yet. I'm adding it to my todo list, though. Thanks again, Regis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#411585: pinging bug
Regis, Thanks for responding. Yes I had cdebconf installed for a while and I was trying to use it. I was motivated to try it out after having issues during the recent perl transition. If cdebconf could make perl transitions smoother I think that would be a big plus in its favour. I would appreciate it if you would make sure that there was a bug report called something like cdebconf not ready for general use and all the issues with using cdebconf in a general way, such as this one, were marked as blocking that bug. Or perhaps all those bug reports could be tagged in some way. On 13/12/11 14:02, Regis Boudin wrote: Should I assume that you're actually using cdebconf on a system, and not only as part of the installer ? It's only been possible to do so for a very short time, and it's not the only feature missing to make it a full replacement for debconf, yet. I'm adding it to my todo list, though. Thanks again, Regis -- Nicholas Bamber | http://www.periapt.co.uk/ PGP key 3BFFE73C from pgp.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#411585: pinging bug
severity 411585 important tag 411585 +confirmed thanks I am marking this bug as important and confirmed for various reasons. I am finding it with purge rather than unregister. However it seems likely that that purge is defined in terms of unregister, or at least that they share code. Unregister is realtively obscure whilst purge is always used. The debconf-devel(7) man page is fairly clear: It [purge] removes all of your package's questions from the debconf's database. I have found that this works under debconf but not cdebconf. Note however that if you restrict yourself to debconf-show it appears to work. You have to either view the cache file or reinstall a purged package to see if it failed or worked. This difference in behaviour from the documentation and the debconf implementation, is enough for me to think that this bug eport should actually be severe, but may be oters woud disagree. -- Nicholas Bamber | http://www.periapt.co.uk/ PGP key 3BFFE73C from pgp.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
