In a later step we could discard unmodified config files based on a list of md5sum of what shipped in stable release.
So only users of default settings would get the new default settings.
I ve started updating debian/README.Debian
Greetings
Hi Nilesh, Alex,
Responding to the first point only, at the moment:
On Sat, 12 Apr 2025 at 07:39, Nilesh Patra <nilesh@debian.org> wrote:
> [ ... snip ... ]
> 1. matplotlib has historically shipped /etc/matploblibrc to force tkagg and patched the code
> to use this if there are no user defined rc files see [1]. However, this was not
> handled properly via maintscripts so that'd mean over-writing user-modified /etc/matplotlibrc.
Ah; what is the problem related to the maintscripts?
The /etc/matplotlibrc file is considered a config file by apt/dpkg (it
is not removed unless a purge is requested), so I was hoping that
shipping a default/unmodified matplotlibrc in an updated 3.10 upload
(as Alex suggests in his thread) would provide a useful additional
conflict-resolution step for anyone who has modified theirs.