On 05/11/2018 11:44 PM, Joel Kulesza wrote:
> LyX Developers,
>
> As I'm writing my dissertation, I've been using LyX 2.2.3 but today
> decided to try migrating it to 2.3.0.  Upon doing so, I encountered
> what appears to be a regression (or else I've been doing something
> invalid all along that 2.2.3 accepts without complaint).
>
> I cannot make the document available but I have a not-quite-MWE
> available that I hope you could work with to see if you can reproduce
> what I'm seeing with LyX 2.2.3/2.3.0 on two separate computers (macOS
> 10.13.4 and OS X 10.11.6).  If this can be reproduced and someone can
> help me characterize this, I'm happy to file an item in the tracker.
>
> Steps to reproduce:
>
>  1. Clone https://github.com/jkulesza/UMich_Dissertation_LyX and
>     checkout the "lyx_mwe" branch.
>  2. Open dissertation.lyx in LyX 2.2.3.  Render.  This should succeed.
>  3. Right-click chapter_01.lyx -> Edit.  Render.  This should succeed.
>  4. Exit.
>  5. Open dissertation.lyx in LyX 2.3.0.  Render.  This should succeed.
>  6. Right-click chapter_01.lyx -> Edit.  Render.  This should fail
>     with the attached regarding being unable to find my .bst file.
>
> At this point, I'm unsure where the problem lies (if it is indeed a
> problem) so anything I'd file in the tracker is no more help that what
> I'm filing here.

Confirmed (in current master). For some reason, the bibtex file is being
copied to the temporary directory for the master buffer:

/tmp/lyx_tmpdir.RReWntipENIy/ > ls lyx_tmpbuf*
lyx_tmpbuf0:
0_home_rikiheck_cvs_lyx_test_UMich_Dissertation_LyX_include_footer_chapter.tex
2_home_rikiheck_cvs_lyx_test_UMich_Dissertation_LyX_include_frontmatter_frontispiece.jpg
3_home_rikiheck_cvs_lyx_test_UMich_Dissertation_LyX_include_bibliography.tex
chapter_01.aux
[...]
chapter_01.tex
chapter_01.tex.dep-pdf

lyx_tmpbuf1:
4_home_rikiheck_cvs_lyx_test_UMich_Dissertation_LyX_include_IEEEtranN_jak.bst

So LyX can't find it.

Jürgen will know what to do, I am sure.

By the way, I see a number of errors when loading the file. The problem
is the one branch that has a space in its name. There's a bug about
this, but you might want to rename that branch for now, if you have it
in your real document.

Riki

Reply via email to