On Thu, 29 Mar 2012, Matus UHLAR - fantomas wrote: > >What could be done is for dpkg to export its command line options > >in a new environment variable DPKG_CMDLINE_OPTS, and then ucf could > >inspect that new variable and verify if --force-confmiss is there. > > what if someone puts the option to dpkg config file?
Those should also be exported. They are command line options from dpkg's point of view. > >In the end, as long as ucf is external to dpkg, you can't really expect > >to have UCF-generated config files handled like dpkg conffiles. So I'm not > >convinced that finding a solution to this specific problem is important > >given the other differences that will continue to remain. > > what I want it to have single way to reenable package's config > file... not something (force-confmiss) that everyone describes and > documents, but someone other (ucf) simply ignores. This may be a UCF > problem, but in this case also dpkg should announce what user > requires. Solving this problem properly (most certainly) requires changes to ucf and to dpkg. So please file a bug against ucf and mark it blocked by this dpkg bug. Cheers, -- Raphaël Hertzog ◈ Debian Developer Pre-order a copy of the Debian Administrator's Handbook and help liberate it: http://debian-handbook.info/liberation/ -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
