Am 26.05.2016 um 16:07 schrieb Uwe Stöhr:
everything is now ready. Please put the new installer for LyX 2.1.4 to
the ftp server:
http://ftp.lyx.de/LyX%202.1.4/
I uploaded there version a new version 7 of the installer for 2.1.4 to
avoid confusions the the version 6 that I released more than
Am 27.05.2016 um 01:03 schrieb Scott Kostyshak:
I will try to release a new version withing 2 hours or so.
It was more tricky than I thought. However, I solved the problems and
uploaded a new version:
http://ftp.lyx.de/LyX%202.2.0/
sorry and regards
Uwe
On Thu, May 26, 2016 at 11:30:03PM +0200, Uwe Stöhr wrote:
> Am 26.05.2016 um 16:05 schrieb Uwe Stöhr:
>
> > Here it is:
> > http://ftp.lyx.de/LyX%202.2.0/
>
> As always a release without testing is very bad. I only had an hour but
> fortunately have now time to test it and there are some errors
Am 26.05.2016 um 16:05 schrieb Uwe Stöhr:
Here it is:
http://ftp.lyx.de/LyX%202.2.0/
As always a release without testing is very bad. I only had an hour but
fortunately have now time to test it and there are some errors and
mistakes if Lyx is installed the first time and without admin
On Thu, May 26, 2016 at 06:44:39PM +0200, Kornel Benko wrote:
> Am Mittwoch, 25. Mai 2016 um 16:48:58, schrieb Kornel Benko
> > Am Montag, 23. Mai 2016 um 18:03:27, schrieb Scott Kostyshak
> >
> > > On Mon, May 23, 2016 at 03:55:59PM +, Guenter Milde wrote:
On Thu, May 26, 2016 at 02:17:11PM +0100, José Abílio Matos wrote:
> On Wednesday, May 25, 2016 1:39:56 PM WEST Scott Kostyshak wrote:
> > I'm still curious someone has thoughts on the above idea. The main
> > question I have is do we usually know when we are not producing
> > equivalent documents
Am Donnerstag, 26. Mai 2016 um 16:30:28, schrieb Scott Kostyshak
> On Thu, May 26, 2016 at 07:00:37PM +0200, Kornel Benko wrote:
> >
> > Subject says it all.
> > Commit?
>
> Yes, to 2.3-staging I think. It is actually in a LyX note along with
> another example file. I'm not
On Thu, May 26, 2016 at 07:00:37PM +0200, Kornel Benko wrote:
>
> Subject says it all.
> Commit?
Yes, to 2.3-staging I think. It is actually in a LyX note along with
another example file. I'm not sure why they are in MergedManuals.lyx.
Scott
>
> Kornel
> diff --git
On Thu, May 26, 2016 at 04:05:24PM +0200, Uwe Stöhr wrote:
> Am 25.05.2016 um 00:29 schrieb Uwe Stöhr:
>
> > Despite of the warning the compilation run fine and I have an installer
> > ready.
>
> Here it is:
> http://ftp.lyx.de/LyX%202.2.0/
Thanks they are uploaded.
> It contains the fresh
Subject says it all.
Commit?
Kornel
signature.asc
Description: This is a digitally signed message part.
diff --git a/lib/doc/MergedManuals.lyx b/lib/doc/MergedManuals.lyx
index 44cbae8..cf72312 100644
--- a/lib/doc/MergedManuals.lyx
+++ b/lib/doc/MergedManuals.lyx
@@ -233,7 +233,7 @@
Am Mittwoch, 25. Mai 2016 um 16:48:58, schrieb Kornel Benko
> Am Montag, 23. Mai 2016 um 18:03:27, schrieb Scott Kostyshak
>
> > On Mon, May 23, 2016 at 03:55:59PM +, Guenter Milde wrote:
> > > On 2016-05-23, Kornel Benko wrote:
> > > > Am Montag, 23. Mai
Uwe Stöhr wrote:
> Am 25.05.2016 um 00:37 schrieb Richard Heck:
>
>> We have lots of warnings like this. They are usually fixed by doing the
>> conversion explicitly, so probably nothing really needs to be done for
>> the release.
>
> This is suspicious to me because usually MSVC has good
Le 26/05/2016 15:12, Uwe Stöhr a écrit :
Am 25.05.2016 um 00:37 schrieb Richard Heck:
We have lots of warnings like this. They are usually fixed by doing the
conversion explicitly, so probably nothing really needs to be done for
the release.
This is suspicious to me because usually MSVC has
Am 25.05.2016 um 00:37 schrieb Richard Heck:
We have lots of warnings like this. They are usually fixed by doing the
conversion explicitly, so probably nothing really needs to be done for
the release.
This is suspicious to me because usually MSVC has good reasons for
issuing a dataloss
Am 17.05.2016 um 23:13 schrieb Uwe Stöhr:
The MiKTeX developer said me that...
he will release this week a new installer that fixes several MiKTeX
issues affecting new installations. So I will include this and then
release version 6 of the installer for LyX 2.1.4.
Hi Richard,
everything is
Am 25.05.2016 um 00:29 schrieb Uwe Stöhr:
Despite of the warning the compilation run fine and I have an installer
ready.
Here it is:
http://ftp.lyx.de/LyX%202.2.0/
It contains the fresh MiKTeX release from yesterday. However, I did not
yet have the time to test new installation of
On Wednesday, May 25, 2016 1:39:56 PM WEST Scott Kostyshak wrote:
> I'm still curious someone has thoughts on the above idea. The main
> question I have is do we usually know when we are not producing
> equivalent documents (and thus it is easy to issue a warning)? I assumed
> so but I don't have
On Wednesday, May 25, 2016 7:11:14 PM WEST Jürgen Spitzmüller wrote:
> Congratulations. And thanks for the excellent management job, Scott.
>
> Jürgen
I agree. :-)
Well done.
--
José Abílio
Le 24/05/2016 23:37, Pavel Sanda a écrit :
I only tried 2.2, so I did not really compare. I do not have 2.0 here. I
can try to have a look at 2.1 vs 2.2 later.
Please try, we should see whether the problem is reproducible at all...
Since you were asking in different thread, ping :)
When I
Le 24/05/2016 23:41, Enrico Forestieri a écrit :
We already check for the presence of the QtSvg (or Qt5Svg) library.
Other than that, I don't know how to check whether the gui libraries
actually have support for loading svg images compiled in.
OK, thanks.
JMarc
Le 25/05/2016 19:11, Jürgen Spitzmüller a écrit :
Thanks to everyone for all the help with the final steps in the
release
process.
Congratulations. And thanks for the excellent management job, Scott.
Indeed. You did it much more thoroughly than I would have been able to.
Time to think about
On Tue, May 24, 2016 at 08:50:14PM -0400, Scott Kostyshak wrote:
> On Wed, May 25, 2016 at 12:29:04AM +0200, Uwe Stöhr wrote:
> > Am 24.05.2016 um 04:32 schrieb Scott Kostyshak:
> >
> > > As usual I'll wait before announcing the release until after uploading
> > > the binaries and providing some
22 matches
Mail list logo