Re: WARNING: updating LaTeX or LyX under Windows will currently break LaTeX installation
On 29/08/2018 1:30 p.m., Uwe Stöhr wrote: Dear LyX Windows users, yesterday I noticed a severe bug in the LaTeX system "MiKTeX" that LyX is usually using under Windows. The problem is that if you - upgrade MiKTeX or LyX or - install a new LaTeX package or - refresh the MiKTeX package database you will end up in a broken LaTeX with error messages like "unknown procedure entry point". I experimented around for more than 2 hours but could not find a workaround once LaTeX is broken. Even a reinstallation of LyX or MiKTeX doesn't help since the result are always broken DLLs and I could not find a way to prevent this. Therefore I strongly recommend not to change anything in your LaTeX setup nor to compile LyX documents that might use special LaTeX packages hat are not yet installed on your PC. Also don't install another version of LyX or reinstall LyX. I hope this issue will be fixed soon and report back. regards Uwe I met this problem too, but after waiting a day and then updating MiKTeX again it has vanished and I am once more able to compile documents (and use instant preview, which the problem also interfered with). Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
WARNING: updating LaTeX or LyX under Windows will currently break LaTeX installation
Dear LyX Windows users, yesterday I noticed a severe bug in the LaTeX system "MiKTeX" that LyX is usually using under Windows. The problem is that if you - upgrade MiKTeX or LyX or - install a new LaTeX package or - refresh the MiKTeX package database you will end up in a broken LaTeX with error messages like "unknown procedure entry point". I experimented around for more than 2 hours but could not find a workaround once LaTeX is broken. Even a reinstallation of LyX or MiKTeX doesn't help since the result are always broken DLLs and I could not find a way to prevent this. Therefore I strongly recommend not to change anything in your LaTeX setup nor to compile LyX documents that might use special LaTeX packages hat are not yet installed on your PC. Also don't install another version of LyX or reinstall LyX. I hope this issue will be fixed soon and report back. regards Uwe
New Tarballs: Please Build Binaries
Slightly updated tarballs are now at http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/. The only changes are to the ANNOUNCE, RELEASE-NOTES, and README files. Please go ahead and build binaries. Riki
Re: 2.3.1 Binaries
On Monday, 27 August 2018 19.41.26 WEST Richard Kimberly Heck wrote: > Are available for testing at http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/. > I suppose we should wait to prepare binaries until we have some feedback. > > Riki Compiled successfully on Fedora 27 to 30 (rawhide), as well as EL7, for all the supported architectures on copr: epel-7-ppc64le epel-7-x86_64 fedora-27-i386 fedora-27-ppc64le fedora-27-x86_64 fedora-28-i386 fedora-28-ppc64le fedora-28-x86_64 fedora-29-i386 fedora-29-ppc64le fedora-29-x86_64 fedora-rawhide-i386 fedora-rawhide-ppc64le fedora-rawhide-x86_64 For further details see: https://copr.fedorainfracloud.org/coprs/jamatos/lyx-next/ -- José Abílio
SIGHUP signal
Hello I happened to close a command window from which I called lyx-2.3.1 and I got a popup about the SIGHUP crashing LyX. Excellent! Is it a new feature or has it been there for a long time ? -- Jean-Pierre
Re: 2.3.1 Binaries
On Tue, Aug 28, 2018 at 05:20:38PM +0200, Jean-Pierre Chrétien wrote: > Le 27/08/2018 à 20:41, Richard Kimberly Heck a écrit : > > Are available for testing at http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/. > > I suppose we should wait to prepare binaries until we have some feedback. Compiles and works well in brief testing. Ubuntu 18.04.1 here, with TeX Live 2018. Configuration Host type: x86_64-pc-linux-gnu Special build flags: build=release std-regex use-hunspell use-enchant Bundled libraries:boost C++ Compiler:g++ (7) C++ Compiler flags: -O2 -std=c++14 C++ Compiler user flags: Linker flags: Linker user flags: Qt Frontend: Qt version: 4.8.7 Packaging: posix LyX binary dir: /usr/local/bin LyX files dir: /usr/local/share/lyx I did get the following message: $ ./src/lyx Gtk-Message: 11:49:35.330: Failed to load module "canberra-gtk-module" After installing the packages libcanberra-gtk-module and libcanberra-gtk0, I no longer get that message. Scott signature.asc Description: PGP signature
Re: 2.3.1 Binaries
Le 27/08/2018 à 20:41, Richard Kimberly Heck a écrit : Are available for testing at http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/. I suppose we should wait to prepare binaries until we have some feedback. On Debian Stretch, with: Configuration Host type: x86_64-pc-linux-gnu Special build flags: build=release std-regex use-hunspell Bundled libraries:boost mythes C++ Compiler:g++ (6.3.0) C++ Compiler flags: -fPIC -O2 -std=c++14 C++ Compiler user flags: Linker flags: Linker user flags: Qt Frontend: Qt version: 5.7.1 Packaging: posix LyX binary dir: /usr/local/bin LyX files dir: /usr/local/share/lyx-2.3.1 compilation runs flawlessly, With TL18, Advanced, Customization and EmbeddeOnjects pdfcompile all right. UserGuide compilation is successful, with two warnings from the indexer: WARNING: Found no :close-range matching an already opened one! Location-reference is 20 in keyword (Environnements de paragraphe). Maybe I lost some of the regular location-references. WARNING: Found a :close-range in the index that wasn't opened before! Location-reference is 37 in keyword (Environnements de Paragraphe) I'll continue and ignore this. The index processor is texindy. -- Jean-Pierre
rpmlint report for lyx on opensuse
LyX 2.3.1 builds fine on openSUSE. Maybe you are interested in warnings and errors that the buildsystem used by openSUSE report: [ 1130s] RPMLINT report: [ 1130s] === [ 1139s] lyx.x86_64: W: empty-%post [ 1139s] lyx.x86_64: W: empty-%postun [ 1139s] lyx.x86_64: W: non-executable-script /usr/share/lyx/lyx2lyx/profiling.py 644 /usr/bin/env python [ 1139s] lyx.x86_64: W: non-executable-script /usr/share/lyx/scripts/prefTest.pl.in 644 /usr/bin/env perl [ 1139s] This text file contains a shebang or is located in a path dedicated for [ 1139s] executables, but lacks the executable bits and cannot thus be executed. If [ 1139s] the file is meant to be an executable script, add the executable bits, [ 1139s] otherwise remove the shebang or move the file elsewhere. [ 1139s] [ 1139s] lyx.x86_64: W: position-independent-executable-suggested /usr/bin/lyx [ 1139s] lyx.x86_64: W: position-independent-executable-suggested /usr/bin/lyxclient [ 1139s] lyx.x86_64: W: position-independent-executable-suggested /usr/bin/tex2lyx [ 1139s] This executable should be position independent (all binaries should). Check [ 1139s] that it is built with -fPIE/-fpie in compiler flags and -pie in linker flags. [ 1139s] [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/TeXFiles.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/clean_dvi.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/convertDefault.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/convert_pdf.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/csv2lyx.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/ext_copy.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/fen2ascii.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/fig2pdftex.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/fig2pstex.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/fig_copy.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/html2latexwrapper.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/include_bib.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/layout2layout.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/legacy_lyxpreview2ppm.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/lyxpak.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/lyxpreview2bitmap.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/lyxpreview_tools.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/prefs2prefs.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/prefs2prefs_lfuns.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/prefs2prefs_prefs.py [ 1139s] lyx.x86_64: W: script-without-shebang /usr/share/lyx/scripts/tex_copy.py [ 1139s] This text file has executable bits set or is located in a path dedicated for [ 1139s] executables, but lacks a shebang and cannot thus be executed. If the file is [ 1140s] meant to be an executable script, add the shebang, otherwise remove the [ 1140s] executable bits or move the file elsewhere. [ 1140s] [ 1140s] lyx.x86_64: W: suse-filelist-forbidden-bashcomp-userdirs /etc/bash_completion.d/lyx is not allowed in SUSE [ 1140s] This directory is for user files, use /usr/share/bash- [ 1140s] completion/completions/ [ 1140s] [ 1140s] lyx.x86_64: E: env-script-interpreter (Badness: 9) /usr/share/lyx/configure.py /usr/bin/env python [ 1140s] lyx.x86_64: E: env-script-interpreter (Badness: 9) /usr/share/lyx/lyx2lyx/lyx2lyx /usr/bin/env python [ 1140s] lyx.x86_64: E: env-script-interpreter (Badness: 9) /usr/share/lyx/scripts/listerrors /usr/bin/env python [ 1140s] lyx.x86_64: E: env-script-interpreter (Badness: 9) /usr/share/lyx/scripts/svg2pdftex.py /usr/bin/env python [ 1140s] lyx.x86_64: E: env-script-interpreter (Badness: 9) /usr/share/lyx/scripts/svg2pstex.py /usr/bin/env python [ 1140s] This script uses 'env' as an interpreter. For the rpm runtime dependency [ 1140s] detection to work, the shebang #!/usr/bin/env python needs to be patched into [ 1140s] #!/usr/bin/python otherwise the package dependency generator merely adds a [ 1140s] dependency on /usr/bin/env rather than the actual interpreter /usr/bin/python. [ 1140s] Alternatively, if the file should not be executed, then ensure that it is not [ 1140s] marked as executable or don't install it in a path that is reserved for [ 1140s] executables.
