Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #794

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/794/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace

Re: Planning to announce 2.3.0 around 17h00 UTC

On 02/28/2018 01:11 AM, Scott Kostyshak wrote: > I'm planning to announce 2.3.0 around 17h00 UTC unless someone reports a > major issue and suggests delaying. > > The biggest pending issue is that the 2.3.0 Windows binary is not > working for racoon, but perhaps this is because of having tested >

Re: Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #794

On 02/28/2018 01:25 PM, ci-...@inria.fr wrote: > https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/794/-- > Started by an SCM change > Building remotely on lyx-linux1 (linux) in workspace >

Re: Tar balls and binaries have been uploaded

On Wed, Feb 28, 2018 at 07:20:38PM +, racoon wrote: > > Uwe and racoon, do you recommend going forward with the release? Why was > > the above not a problem for rc2? > > My guess is that I did not have the virus scanner activated when installing > rc2 but can't say for sure. We've decided

Re: Tar balls and binaries have been uploaded

Yes, I can do it. But the earliest is tomorrow morning (so in about 10 hours). Just to be sure: The virus scanner did not detect anything. And I left the scanner activated during the second, successful installation process. It is just that the scanner did not do a deep scan the second time

Re: Planning to announce 2.3.0 around 17h00 UTC

On Wed, Feb 28, 2018 at 07:27:15PM +, Richard Heck wrote: > On 02/28/2018 01:11 AM, Scott Kostyshak wrote: > > I'm planning to announce 2.3.0 around 17h00 UTC unless someone reports a > > major issue and suggests delaying. > > > > The biggest pending issue is that the 2.3.0 Windows binary is

Re: Tar balls and binaries have been uploaded

On 2018-02-28 17:50, Scott Kostyshak wrote: On Wed, Feb 28, 2018 at 11:36:33AM +, racoon wrote: On 28.02.2018 12:04, Uwe Stöhr wrote: Strange. I just ran the installer again and now it works. The installer checks the Windows registry to locate LaTeX program. If you have MiKTeX or

Re: Tar balls and binaries have been uploaded

On 2018-02-28 17:58, Scott Kostyshak wrote: On Wed, Feb 28, 2018 at 09:25:47AM +, racoon wrote: Strange. I just ran the installer again and now it works. To be clear, the installer works and after the installation you can successfully compile e.g. the user guide? That is correct.

Re: Planning to announce 2.3.0 around 17h00 UTC

On 1/03/2018 8:27 a.m., Richard Heck wrote: On 02/28/2018 01:11 AM, Scott Kostyshak wrote: I'm planning to announce 2.3.0 around 17h00 UTC unless someone reports a major issue and suggests delaying. The biggest pending issue is that the 2.3.0 Windows binary is not working for racoon, but

Re: Tar balls and binaries have been uploaded

On Wed, Feb 28, 2018 at 08:41:43PM +, racoon wrote: > Yes, I can do it. But the earliest is tomorrow morning (so in about 10 > hours). > > Just to be sure: The virus scanner did not detect anything. And I left the > scanner activated during the second, successful installation process. It is >

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #708

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/708/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools #709

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/709/

Build failed in Jenkins: Support and maintenance jobs » Check-author-email-in-commit-log #50

https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/50/Changes: [spitz] tex2lyx: do not force default bibliography style if none is set [spitz] Add literal param to InsetInclude [spitz] Add LyX 2.3 format [uwestoehr] ar.po: correct year [sanda] * cs.po [rgheck] Fix bug

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools-extended #796

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/796/

Re: CI job: Check author email in commit log

Hi, Just FYI, the CI job that checks authors' email has triggered. https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/ Here's the difference: Latest log: cca365f26c 2018-02-15 11:28:34 -0800 name=Alexander Dunlap email=alexander.dun...@gmail.com c070c2f1f8 2018-01-10

Re: Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #794

On Wed, 28 Feb 2018 at 20:27, Richard Heck wrote: > On 02/28/2018 01:25 PM, ci-...@inria.fr wrote: > > > https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/794/-- > > Started by an SCM change > > Building

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #795

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/795/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace

Re: Tar balls and binaries have been uploaded

Or it might be even enough to just download a fresh file... I'll try in a bit. Daniel On 2018-02-28 23:31, Scott Kostyshak wrote: On Wed, Feb 28, 2018 at 08:41:43PM +, racoon wrote: Yes, I can do it. But the earliest is tomorrow morning (so in about 10 hours). Just to be sure: The virus

Re: Tar balls and binaries have been uploaded

On 28.02.2018 07:03, Scott Kostyshak wrote: On Tue, Feb 27, 2018 at 09:38:47PM +, Scott Kostyshak wrote: On Tue, Feb 27, 2018 at 08:24:43PM +, racoon wrote: Yes. What is the exact error message that is given and when is it given? Can you provide a screenshot? Screenshot attached.

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #706

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/706/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace

Re: Tar balls and binaries have been uploaded

On 28.02.2018 07:03, Scott Kostyshak wrote: On Tue, Feb 27, 2018 at 09:38:47PM +, Scott Kostyshak wrote: On Tue, Feb 27, 2018 at 08:24:43PM +, racoon wrote: Yes. What is the exact error message that is given and when is it given? Can you provide a screenshot? Also, have you

Re: Tar balls and binaries have been uploaded

On 28.02.2018 12:04, Uwe Stöhr wrote: Strange. I just ran the installer again and now it works. The installer checks the Windows registry to locate LaTeX program. If you have MiKTeX or TeXLive  installed but the installer cannot find it, your virus scanner blocks that the installer have

Re: Tar balls and binaries have been uploaded

On Wed, Feb 28, 2018 at 11:36:33AM +, racoon wrote: > On 28.02.2018 12:04, Uwe Stöhr wrote: > > > > > Strange. I just ran the installer again and now it works. > > > > The installer checks the Windows registry to locate LaTeX program. If you > > have MiKTeX or TeXLive  installed but the

Re: Tar balls and binaries have been uploaded

On Wed, Feb 28, 2018 at 09:25:47AM +, racoon wrote: > Strange. I just ran the installer again and now it works. To be clear, the installer works and after the installation you can successfully compile e.g. the user guide? Scott signature.asc Description: PGP signature

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #707

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/707/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #793

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/793/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace

Re: Tar balls and binaries have been uploaded

> Strange. I just ran the installer again and now it works. The installer checks the Windows registry to locate LaTeX program. If you have MiKTeX or TeXLive  installed but the installer cannot find it, your virus scanner blocks that the installer have read access to the registry. This should