On Mon, Apr 11, 2016 at 01:36:28PM +0200, Jean-Marc Lasgouttes wrote:
> Le 11/04/2016 07:27, Andrew Parsloe a écrit :
> >Suppose a module defines flex insets moo and baa (the locale-dependent
> >version of foo and bah in New Zealand), and these are used in a document
> >to which the module has been added. If the module is now deleted from
> >the document, the flex insets become undefined. If the document is saved
> >then closed with undefined insets, the saved file will contain lines like
> >
> >\begin_inset Flex undefined
> 
> Please open a new ticket.

Yes and mark it with milestone 2.2.0.

I can confirm that I do not see the problem in 2.1.4 and I do see it
with 2.2.0dev.

I suppose this is a dataloss bug, and that there is a rule of not going
to an RC with a known dataloss bug that is a regression. Although the
bug only shows in a specific case and has gone unnoticed for more than a
year in 2.2.0dev, it is pretty easy to trigger and it would not be
surprising at all that a user comes across it. I would like to hear from
Jürgen to see if a quick fix can be made before proceeding with rc1.

> I think it is a consequence of
> 
> commit cfeddb9293bb1e3b45fe2f118a6ce35e37bbebf3
> Author: Juergen Spitzmueller <[email protected]>
> Date:   Mon Dec 8 09:06:41 2014 +0100
> 
>     Add ObsoletedBy tag to InsetLayout
> 
>     Fixes: #9000.

Jürgen are you able to take a look?

Scott

Attachment: signature.asc
Description: PGP signature

Reply via email to