Re: configure.py regression in RC1 compared to beta

2017-10-31 Thread Scott Kostyshak
On Tue, Oct 31, 2017 at 09:19:49AM +, Stephan Witt wrote: > Am 30.10.2017 um 08:31 schrieb Scott Kostyshak : > > > > On Sun, Oct 29, 2017 at 09:10:23PM +, Uwe Stöhr wrote: > >> El 29.10.2017 a las 16:52, Jürgen Spitzmüller escribió: > >> > >>> Note that I am traveling. So if it works on t

Re: configure.py regression in RC1 compared to beta

2017-10-31 Thread Stephan Witt
Am 30.10.2017 um 08:31 schrieb Scott Kostyshak : > > On Sun, Oct 29, 2017 at 09:10:23PM +, Uwe Stöhr wrote: >> El 29.10.2017 a las 16:52, Jürgen Spitzmüller escribió: >> >>> Note that I am traveling. So if it works on the Mac, someone will have >>> to cherry-pick it. >> >> I might also not b

Re: configure.py regression in RC1 compared to beta

2017-10-30 Thread Uwe Stöhr
El 30.10.2017 a las 08:31, Scott Kostyshak escribió: I'll cherry-pick Jürgen's change regarding WMF -> EPS converter. I don't want the commit that stores text editors in a variable in RC1 (even though I requested that improvement) since it is more of a long-run benefit fix. OK, then only also

Re: configure.py regression in RC1 compared to beta

2017-10-30 Thread Scott Kostyshak
On Sun, Oct 29, 2017 at 09:10:23PM +, Uwe Stöhr wrote: > El 29.10.2017 a las 16:52, Jürgen Spitzmüller escribió: > > > Note that I am traveling. So if it works on the Mac, someone will have > > to cherry-pick it. > > I might also not be able to commit soon. So Scott, could you please do this

Re: configure.py regression in RC1 compared to beta

2017-10-29 Thread Uwe Stöhr
El 29.10.2017 a las 16:52, Jürgen Spitzmüller escribió: Note that I am traveling. So if it works on the Mac, someone will have to cherry-pick it. I might also not be able to commit soon. So Scott, could you please do this if Stephan gave his OK? Moreover, I propose to commit configure.py as

Re: configure.py regression in RC1 compared to beta

2017-10-29 Thread Jürgen Spitzmüller
Am Sonntag, den 29.10.2017, 15:17 +0100 schrieb Uwe Stöhr: > El 29.10.2017 a las 08:54, Jürgen Spitzmüller escribió: > > > > Any thoughts on whether this should be an rc1 blocker? > > > > Yes, it should, if only since we need the rc to test all OSes. > > +1 > > > Anyway, I have pushed a fix to

Re: configure.py regression in RC1 compared to beta

2017-10-29 Thread Uwe Stöhr
El 29.10.2017 a las 08:54, Jürgen Spitzmüller escribió: Any thoughts on whether this should be an rc1 blocker? Yes, it should, if only since we need the rc to test all OSes. +1 Anyway, I have pushed a fix to master. It works on Linux. Great! This works here. best regards Uwe

Re: configure.py regression in RC1 compared to beta

2017-10-29 Thread Uwe Stöhr
El 28.10.2017 a las 19:25, Jürgen Spitzmüller escribió: It should be quoted. You can check via the messages pane. Hi Jürgen, sorry I did not have time to look closer up to now. Nevertheless I cannot see the complete path behind $$p, all I get is this:

Re: configure.py regression in RC1 compared to beta

2017-10-29 Thread Stephan Witt
Am 29.10.2017 um 08:54 schrieb Jürgen Spitzmüller : > > Am Samstag, den 28.10.2017, 15:59 -0400 schrieb Scott Kostyshak: >> I think that this is the type of issue that would not necessarily be >> a >> beta-blocker but that should be an rc-blocker. Indeed, we prioritized >> fixing SVG conversion on

Re: configure.py regression in RC1 compared to beta

2017-10-29 Thread Jürgen Spitzmüller
Am Samstag, den 28.10.2017, 15:59 -0400 schrieb Scott Kostyshak: > I think that this is the type of issue that would not necessarily be > a > beta-blocker but that should be an rc-blocker. Indeed, we prioritized > fixing SVG conversion on Mac before rc1, which we did; so I suppose > we > should con

Re: configure.py regression in RC1 compared to beta

2017-10-28 Thread Scott Kostyshak
On Sat, Oct 28, 2017 at 05:25:46PM +, Jürgen Spitzmüller wrote: > Am Samstag, den 28.10.2017, 18:49 +0200 schrieb Uwe Stöhr: > > El 28.10.2017 a las 14:05, Jürgen Spitzmüller escribió: > > > > > > How can we fix this? > > > > > > If it turns out that Inkscape on Windows cannot deal with paths

Re: configure.py regression in RC1 compared to beta

2017-10-28 Thread Jürgen Spitzmüller
Am Samstag, den 28.10.2017, 18:49 +0200 schrieb Uwe Stöhr: > El 28.10.2017 a las 14:05, Jürgen Spitzmüller escribió: > > > > How can we fix this? > > > > If it turns out that Inkscape on Windows cannot deal with paths we > > need > > to introduce a function for configure.py that returns full path

Re: configure.py regression in RC1 compared to beta

2017-10-28 Thread Uwe Stöhr
El 28.10.2017 a las 14:05, Jürgen Spitzmüller escribió: How can we fix this? If it turns out that Inkscape on Windows cannot deal with paths we need to introduce a function for configure.py that returns full path or only file name depending on the OS. I think this is the problem as far as I

Re: configure.py regression in RC1 compared to beta

2017-10-28 Thread Jürgen Spitzmüller
Am Samstag, den 28.10.2017, 13:08 +0200 schrieb Uwe Stöhr: > Hi Stephan, > > With LyX 2.3.0beta1 I can convert EMF images in LyX file while this > fails in RC1. Can you please elaborate what exactly fails? > The reason is commit > http://www.lyx.org/trac/changeset/350ef993/lyxgit > > The bug i

configure.py regression in RC1 compared to beta

2017-10-28 Thread Uwe Stöhr
Hi Stephan, With LyX 2.3.0beta1 I can convert EMF images in LyX file while this fails in RC1. The reason is commit http://www.lyx.org/trac/changeset/350ef993/lyxgit The bug is that the path must not be output for inkscape on Win and apparently also not on Linux. As this seems to be a special