From: Efraim Flashner <efraim@flashner.co.il>
To: Xavier Montillet <xavierm02@guix.xavierm02.fr>
Cc: 37013@debbugs.gnu.org
Subject: bug#37013: LyX can not find refstyle.sty
Date: Thu, 11 Jun 2020 10:00:43 +0300 [thread overview]
Message-ID: <20200611070043.GI963@E5400> (raw)
In-Reply-To: <b0ca5670-99d7-4991-be93-6b6401d36bdc@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 2127 bytes --]
I just made some changes to the Lyx package. Can you test it out now to
see if it works as expected?
On Thu, Aug 22, 2019 at 04:23:18PM +0000, Xavier Montillet wrote:
> Hi Ricardo,
>
> LyX seems to build and run fine without this texlive-union. The texlive stuff is only required when one wants to compile a lyx document to a pdf. I'd therefore expect it to not be a dependency (but maybe a recommended package).
>
> And removing this texlive-union fixes my problem: Now, if texlive is installed in the profile, it finds it and all its components.
>
> (Note: I use "./pre-inst-env guix environment --pure --container --share=$XAUTHORITY --share=/tmp/.X11-unix --ad-hoc lyx bash coreutils evince -- env XAUTHORITY=$XAUTHORITY DISPLAY=$DISPLAY lyx2.3" to run lyx so that it reconfigures at startup)
>
> Xavier
>
> On Mon, Aug 12, 2019, at 9:30 PM, Ricardo Wurmus wrote:
> >
> > Hi Xavier,
> >
> > thanks for the report!
> >
> > > Since it loaded inputenc, the package just before refstyle, from
> > > /gnu/store/wy5865kh09qak63rpq3v47wnxv2gj1y0-texlive-union-49435/share/texmf-dist/tex/latex/base/inputenc.sty,
> > > and /gnu/store/wy5865kh09qak63rpq3v47wnxv2gj1y0-texlive-union-49435/ does not contain refstyle, I
> > > think that the problem is that LyX uses the pdflatex from this
> > > textlive-union instead of the one from the full texlive.
> >
> > The problem is that Lyx is configured to use the texlive-union that was
> > provided during the build. It should prefer an optional TeX Live
> > installation that the user provides. Perhaps we can make it
> > (optionally?) look up the TeX Live tools on PATH before falling back to
> > its texlive-union.
> >
> > > LyX has a reconfigure option (Tools -> Reconfigure) but it does not
> > > seem to help.
> >
> > Investigating this might be a good starting point.
> >
> > --
> > Ricardo
> >
> >
>
>
>
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-11 7:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 20:51 bug#37013: LyX can not find refstyle.sty Xavier Montillet
2019-08-12 21:29 ` Ricardo Wurmus
2019-08-22 16:23 ` Xavier Montillet
2020-06-11 7:00 ` Efraim Flashner [this message]
2020-06-17 0:11 ` sirgazil via Bug reports for GNU Guix
2020-08-05 2:20 ` Jakub Kądziołka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200611070043.GI963@E5400 \
--to=efraim@flashner.co.il \
--cc=37013@debbugs.gnu.org \
--cc=xavierm02@guix.xavierm02.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).