Re: stretch update overwrites nano file
On Wed 28 Nov 2018 at 08:19:39 +0100, Pascal Hambourg wrote:
> Le 27/11/2018 à 20:15, Brian a écrit :
> > On Tue 27 Nov 2018 at 11:07:33 +0000, Bonno Bloksma wrote:
> >
> > > Yup, I simply put my default.nanorc file back into the /usr/share/nano
> > > dir. I want it to be a system wide default as the current default is
> > > "a bit sparse" ;-)
> >
> > Then you used dpkg-divert to be able to sleep better at nights and not
> > have to worry about it being overwritten?
>
> This is a good advice for the future, but default.nanorc did not exist in
> Jessie's nano package, so there was nothing to divert before the upgrade.
> The OP was unlucky to choose a file name which will was used in the next
> version.
No - it is good advice for now, unless the OP wants to continually have
to manage the change manually after an upgrade. I surmise he is happy
to do that.
> > It would not have been better to have been given a warning. Any admin
> > who alters a system file should know what he is doing and be able to
> > deal with it.
>
> The OP did dot alter a system file, the file did not exist in Jessie's
> package.
But it exists now. Choices, choices.
--
Brian
Reply to: