bug#81499: 30.2; Truncation of custom settings when custom-safe-themes changes

Brad Howes via "Bug reports for GNU Emacs, the Swiss army knife of text editors" [26/Jul 12:21pm +02] wrote:
> I updated the packages I use, and this included an update to 'modus-vivendi’ theme.  When loading the updated theme, Emacs cautioned that
>
>   Loading a theme can run Lisp code. Really load? (y or n)
>
> After responding ‘y’, Emacs asks:
>
>   Treat this theme as safe in future sessions? (y or n)
>
> If I respond ’n’, Emacs loads fine and all of my configuration settings are honored. My init.el file defines a `custom-file` setting, and the content of this file is unchanged. However, if I respond ‘y’, then the custom file contains a change to the `custom-safe-themes` value as one would expect, but any settings *after* in the file no long exist, including any `custom-set-faces` value.

So Emacs isn't completely overriding the file, just losing one part of
it?

-- 
Sean Whitton