Le 11/03/2015 04:15, Scott Kostyshak a écrit :
I tried the user directory on my computer with 2.1.3 and with master,
and it worked fine for me.

Does anyone have any ideas why this happened? I've seen similar topics
come up from
time to time so I'm wondering if there's a bug lurking somewhere.

The full bug report (along with the user's configure output) is here:
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/1430059

After asking the reporter, it turns out that it is because his lyxrc.default was newer than the configure.py. The configure.py last modification date is not the date of installation, but the date when the package got built.

One solution could be to create a new file VERSION in the user directory that contains the version of LyX that uses it.

It is not fool-proof, but would help in many cases (and can probably be used in other ways).

The problem however is that configure.py itself does not know LyX version number. We could let LyX itself create this file (and maybe let configure.py delete it first, so that there is no wrong VERSION file laying around).

JMarc

Reply via email to