On Wed, Jul 03, 2013 at 10:26:39AM +0200, Paul Gevers wrote: > On 03-07-13 09:58, Marc Haber wrote: > > Did you on purpose decide not to bomb out if the new file does already > > exist? > > Yes. In my case it would mean that the admin already created a file with > the proposed new name, AND left the old name in place. As these files > are only in the "conf-available" folder, it doesn't hurt there. The > admin seems to know what he is doing. This doesn't mean that it works > for you though.
I will probably spew a warning and continue. > > The code you have written will probably ask the user a question about > > $newfile and then zap the file. Is this intended? Why not ucf > > --debconf-ok /dev/null $newfile? > > If I remember correctly, you don't get any question, because ucf > considers the file new and does not need to ask anything. I would expect > that this way (rm -f immediately afterwards) it does not matter what > source you use, and yours might just be clearer at the intension. Could > you test and let me know? I think you're right here. Thanks for explaining. Greetings Ma "need more coffee" rc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130703082924.gb26...@torres.zugschlus.de
