Here:
http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
The only change is the date in configure.ac.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel
On Thu, 2023-06-22 at 11:27 -0400, Richard Kimberly Heck wrote:
> I have gotten access to the ftp site again, so beta 3 has been
> uploaded
> there:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please prepare binaries for release next week.
>
> Riki
Coming lat
On Tue, 4 Jul 2023 at 00:02, Pavel Sanda wrote:
> On Mon, Jul 03, 2023 at 10:53:52PM +0200, Pavel Sanda wrote:
> > please can you have a look on few 2.4 related bugs:
> > https://www.lyx.org/trac/ticket/12786
> > https://www.lyx.org/trac/ticket/12803
> > https://www.lyx.org/trac/ticket/10364
>
>
On Mon, Jul 03, 2023 at 10:53:52PM +0200, Pavel Sanda wrote:
> please can you have a look on few 2.4 related bugs:
> https://www.lyx.org/trac/ticket/12786
> https://www.lyx.org/trac/ticket/12803
> https://www.lyx.org/trac/ticket/10364
And there was also bug report on users list:
"in the last windo
On Mon, Jun 26, 2023 at 09:14:12AM +0200, Yu Jin wrote:
> Am Do., 22. Juni 2023 um 17:28 Uhr schrieb Richard Kimberly Heck:
>
> > I have gotten access to the ftp site again, so beta 3 has been uploaded
> > there:
> >
> > http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
&
Am Do., 22. Juni 2023 um 17:28 Uhr schrieb Richard Kimberly Heck:
> I have gotten access to the ftp site again, so beta 3 has been uploaded
> there:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please prepare binaries for release next week.
I have built and uploaded
I have gotten access to the ftp site again, so beta 3 has been uploaded
there:
http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
Please prepare binaries for release next week.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Mon, Sep 27, 2021 at 03:39:33PM +0200, Thibaut Cuvelier wrote:
> > > Recently, the major browsers stopped supporting FTP links. I don't like
> > > the change, but there's nothing I can do about it???
> > >
> > > The problem is that the Ly
On Mon, 27 Sept 2021 at 15:15, Jean-Marc Lasgouttes
wrote:
> Le 27/09/2021 à 13:10, Thibaut Cuvelier a écrit :
> > Dear list,
> >
> > Recently, the major browsers stopped supporting FTP links. I don't like
> > the change, but there's nothing I can do about it
Le 27/09/2021 à 13:10, Thibaut Cuvelier a écrit :
Dear list,
Recently, the major browsers stopped supporting FTP links. I don't like
the change, but there's nothing I can do about it…
The problem is that the LyX website still has one FTP link that could be
replaced with the equiv
Dear list,
Recently, the major browsers stopped supporting FTP links. I don't like the
change, but there's nothing I can do about it…
The problem is that the LyX website still has one FTP link that could be
replaced with the equivalent HTTP link, on https://www.lyx.org/Download.
Secti
pty archive to the official ftp
> you might be very thankful to have one mirror wihout the delete feature :)
Ah that is a good point!
Scott
signature.asc
Description: PGP signature
Scott Kostyshak wrote:
> Should this be reported to the server maintainer of that mirror?
I would not worry about that, one of our former .de mirrors did the
same and if one day you incidentally sync empty archive to the official ftp
you might be very thankful to have one mirror wihout the del
The other mirrors remove files when we remove a file in the upstream
FTP, but UCSD seems to keep files around.
If you go to:
ftp://ftp.ucsd.edu/LyX/devel/lyx-2.3/lyx-2.3.0rc1/
You can still see the old Windows and Mac installers.
Should this be reported to the server maintainer of that
Uwe Stöhr writes:
>> With our release frequency, it shouldn't be a problem to manually [*]
>> update PDFs and upload the official manuals.
>
> I only used ft.lyx.de because I could not upload files anymore to
> wiki.lyx.org. Is this now again possible?
Hi Uwe,
Yes,
icm.edu.pl/packages/lyx
> > >
> > > Is it normal to have http://ftp ? On the other hand, if I change it to
> > > ftp://ftp, although it loads fine in the browser, I get:
> > >
> > > $ curl 'ftp://ftp.icm.edu.pl/packages/lyx'
> > > cur
On Fri, May 05, 2017 at 01:17:23PM +0200, Kornel Benko wrote:
> Am Freitag, 5. Mai 2017 um 05:49:10, schrieb Scott Kostyshak
>
> > One of our mirrors is:
> >
> > http://ftp.icm.edu.pl/packages/lyx
> >
> > Is it normal to have http://ftp ? On the other h
On Fri, May 05, 2017 at 08:18:55AM -0700, Pavel Sanda wrote:
> Scott Kostyshak wrote:
> > One of our mirrors is:
> >
> > http://ftp.icm.edu.pl/packages/lyx
> >
> > Is it normal to have http://ftp ? On the other hand, if I change it to
>
> Both ftp &
Scott Kostyshak wrote:
> One of our mirrors is:
>
> http://ftp.icm.edu.pl/packages/lyx
>
> Is it normal to have http://ftp ? On the other hand, if I change it to
Both ftp & http(s) work for some of our mirrors and I mixed ftp/http
protocols in mirrors section beca
Am Freitag, 5. Mai 2017 um 05:49:10, schrieb Scott Kostyshak
> One of our mirrors is:
>
> http://ftp.icm.edu.pl/packages/lyx
>
> Is it normal to have http://ftp ? On the other hand, if I change it to
> ftp://ftp, although it loads fine in the browser, I get:
Le 05/05/17 à 11:49, Scott Kostyshak a écrit :
One of our mirrors is:
http://ftp.icm.edu.pl/packages/lyx
Is it normal to have http://ftp ? On the other hand, if I change it to
ftp://ftp, although it loads fine in the browser, I get:
Well, we can do that with ftp.lyx.org too.
JMarc
One of our mirrors is:
http://ftp.icm.edu.pl/packages/lyx
Is it normal to have http://ftp ? On the other hand, if I change it to
ftp://ftp, although it loads fine in the browser, I get:
$ curl 'ftp://ftp.icm.edu.pl/packages/lyx'
curl: (78) RETR response: 550
Scott
sig
Christian Ridderström wrote:
> On 27 January 2017 at 20:11, Pavel Sanda wrote:
> > as an additional safety meaure I would like to track our .sig files stored
> > on ftp via git. Is there any opposition to put them into
> > master/development?
>
> Sounds like a good ide
On 27 January 2017 at 20:11, Pavel Sanda wrote:
>
> as an additional safety meaure I would like to track our .sig files stored
> on
> ftp via git. Is there any opposition to put them into master/development?
Sounds like a good idea to me.
Could you give an example of where
Hi,
as an additional safety meaure I would like to track our .sig files stored on
ftp via git. Is there any opposition to put them into master/development?
Pavel
Le 09/06/2016 à 04:03, Richard Heck a écrit :
On 06/08/2016 03:57 PM, Georg Baum wrote:
Guillaume Munch wrote:
Le 07/06/2016 00:00, Richard Heck a écrit :
Our use of git would make it very easy for us to have a branch in which
new features not requiring format changes could also be put.
Thi
Le 15/06/2016 00:51, Enrico Forestieri a écrit :
On Fri, Jun 10, 2016 at 10:20:32PM +0100, Guillaume Munch wrote:
As for lyx2lyx, I gave one example of a commit which explicitly said
that it would not be made round-trip, and another example where it had
to be fixed afterwards because a special c
On Fri, Jun 10, 2016 at 10:20:32PM +0100, Guillaume Munch wrote:
> As for lyx2lyx, I gave one example of a commit which explicitly said
> that it would not be made round-trip, and another example where it had
> to be fixed afterwards because a special case was not taken into
> accountn because it i
Le 08/06/2016 22:36, Liviu Andronic a écrit :
On Wed, Jun 8, 2016 at 10:14 PM, Guillaume Munch wrote:
Le 08/06/2016 20:48, Pavel Sanda a écrit :
Guillaume Munch wrote:
Here's what I suggest. Let's do, on a trial basis for the
duration of 2.3dev, a branch that mirrors master but inserts
pat
On 06/08/2016 03:57 PM, Georg Baum wrote:
> Guillaume Munch wrote:
>
>> Le 07/06/2016 00:00, Richard Heck a écrit :
>>> Our use of git would make it very easy for us to have a branch in which
>>> new features not requiring format changes could also be put.
>>>
>> This solution would be fine by me t
On Wed, Jun 8, 2016 at 10:14 PM, Guillaume Munch wrote:
>
> Le 08/06/2016 20:48, Pavel Sanda a écrit :
>>
>> Guillaume Munch wrote:
>>>
>>> Here's what I suggest. Let's do, on a trial basis for the duration of
>>> 2.3dev, a branch that mirrors master but inserts patches to disable the
>>> input an
Le 08/06/16 à 22:14, Guillaume Munch a écrit :
As long as I am allowed to ignore the third branch completely I am
fine with that.
I think this is the idea.
So why not, indeed.
JMarc
Le 08/06/2016 20:57, Georg Baum a écrit :
Guillaume Munch wrote:
Le 07/06/2016 00:00, Richard Heck a écrit :
Our use of git would make it very easy for us to have a branch in which
new features not requiring format changes could also be put.
This solution would be fine by me too, if people
Le 08/06/2016 20:48, Pavel Sanda a écrit :
Guillaume Munch wrote:
Here's what I suggest. Let's do, on a trial basis for the duration of
2.3dev, a branch that mirrors master but inserts patches to disable the
input and output of new file-format features (as well as layout changes,
etc.) after eac
Guillaume Munch wrote:
> Le 07/06/2016 00:00, Richard Heck a écrit :
>>
>> Our use of git would make it very easy for us to have a branch in which
>> new features not requiring format changes could also be put.
>>
>
> This solution would be fine by me too, if people agree to have three
> branches
Guillaume Munch wrote:
> Here's what I suggest. Let's do, on a trial basis for the duration of
> 2.3dev, a branch that mirrors master but inserts patches to disable the
> input and output of new file-format features (as well as layout changes,
> etc.) after each file-format change. We would see if
Le 07/06/2016 00:35, Guillaume Munch a écrit :
Le 07/06/2016 00:00, Richard Heck a écrit :
On 06/06/2016 06:40 PM, Guillaume Munch wrote:
The point of the proposal is to enabling the early testing and release
of *non-file-format* changes. Then for a proper master release only
file-format chang
On Tue, Jun 7, 2016 at 12:10 AM, Andrew Parsloe wrote:
> On 7/06/2016 9:50 a.m., Richard Heck wrote:
>>
>> On 06/06/2016 03:33 PM, Georg Baum wrote:
>>>
>>> Jean-Marc Lasgouttes wrote:
>>>
Le 05/06/2016 à 21:05, Guillaume Munch a écrit :
>
> Yet, most of the file format changes are ve
Le 07/06/2016 00:00, Richard Heck a écrit :
On 06/06/2016 06:40 PM, Guillaume Munch wrote:
The point of the proposal is to enabling the early testing and release
of *non-file-format* changes. Then for a proper master release only
file-format changes remain to be fully tested.
This assumes the
On 06/06/2016 06:40 PM, Guillaume Munch wrote:
>
> The point of the proposal is to enabling the early testing and release
> of *non-file-format* changes. Then for a proper master release only
> file-format changes remain to be fully tested.
This assumes these aspects do not interact. Oftentimes, t
On 06/06/2016 06:10 PM, Andrew Parsloe wrote:
> On 7/06/2016 9:50 a.m., Richard Heck wrote:
>> On 06/06/2016 03:33 PM, Georg Baum wrote:
>>> Jean-Marc Lasgouttes wrote:
>>>
Le 05/06/2016 à 21:05, Guillaume Munch a écrit :
> Yet, most of the file format changes are very simple. I wonder
>>>
Le 06/06/2016 22:47, Richard Heck a écrit :
On 06/06/2016 04:27 PM, Guillaume Munch wrote:
Le 06/06/2016 20:33, Georg Baum a écrit :
Jean-Marc Lasgouttes wrote:
Le 05/06/2016 à 21:05, Guillaume Munch a écrit :
Yet, most of the file format changes are very simple. I wonder
whether one could i
On 7/06/2016 9:50 a.m., Richard Heck wrote:
On 06/06/2016 03:33 PM, Georg Baum wrote:
Jean-Marc Lasgouttes wrote:
Le 05/06/2016 à 21:05, Guillaume Munch a écrit :
Yet, most of the file format changes are very simple. I wonder whether
one could introduce a single compilation variable to disabl
On 06/06/2016 03:33 PM, Georg Baum wrote:
> Jean-Marc Lasgouttes wrote:
>
>> Le 05/06/2016 à 21:05, Guillaume Munch a écrit :
>>> Yet, most of the file format changes are very simple. I wonder whether
>>> one could introduce a single compilation variable to disable them,
>>> and ask developers to e
On 06/06/2016 04:27 PM, Guillaume Munch wrote:
> Le 06/06/2016 20:33, Georg Baum a écrit :
>> Jean-Marc Lasgouttes wrote:
>>
>>> Le 05/06/2016 à 21:05, Guillaume Munch a écrit :
Yet, most of the file format changes are very simple. I wonder
whether one could introduce a single compilation
Le 06/06/2016 20:33, Georg Baum a écrit :
Jean-Marc Lasgouttes wrote:
Le 05/06/2016 à 21:05, Guillaume Munch a écrit :
Yet, most of the file format changes are very simple. I wonder
whether one could introduce a single compilation variable to
disable them, and ask developers to enclose file-fo
Jean-Marc Lasgouttes wrote:
> Le 05/06/2016 à 21:05, Guillaume Munch a écrit :
>> Yet, most of the file format changes are very simple. I wonder whether
>> one could introduce a single compilation variable to disable them,
>> and ask developers to enclose file-format-specific code between the
>> c
Liviu Andronic wrote:
> We already have nightly builds for Ubuntu Linux:
> https://launchpad.net/~lyx-devel/+archive/ubuntu/daily
>
> It's been running for couple of years (probably all through the 2.2
> development cycle), though I'm not sure it's made much of an impact in
> terms of testing and
Sorry for the late reply, I somehow missed this message.
Jean-Marc Lasgouttes wrote:
> Le 31/05/2016 à 22:26, Georg Baum a écrit :
>> We need to decide: Either have a fixed schedule, and an unknown feature
>> set of the next release, or a fixed feature set, and an unknown schedule.
>> We do not
Le 05/06/2016 à 21:05, Guillaume Munch a écrit :
Yet, most of the file format changes are very simple. I wonder whether
one could introduce a single compilation variable to disable them,
and ask developers to enclose file-format-specific code between the
corresponding #ifdefs. (For instance in my
Le 03/06/2016 13:02, Jean-Marc Lasgouttes a écrit :
Le 31/05/2016 à 22:26, Georg Baum a écrit :
In addition I would suggest the following: (Officially) allow new
features that do not require a file format change into minor
releases.
The main reason is again that this allows testing more
regular
On Friday, June 3, 2016 2:02:15 PM WEST Jean-Marc Lasgouttes wrote:
> I prefer the fixed schedule. We never know exactly when starting a
> release cycle what features will happen or not. But we can enforce when
> the release will happen.
+1
--
José Abílio
Le 03/06/2016 à 15:03, Liviu Andronic a écrit :
We already have nightly builds for Ubuntu Linux:
https://launchpad.net/~lyx-devel/+archive/ubuntu/daily
It's been running for couple of years (probably all through the 2.2
development cycle), though I'm not sure it's made much of an impact in
terms
On Fri, Jun 3, 2016 at 2:02 PM, Jean-Marc Lasgouttes wrote:
> Le 31/05/2016 à 22:26, Georg Baum a écrit :
>>
>> We need to decide: Either have a fixed schedule, and an unknown feature
>> set
>> of the next release, or a fixed feature set, and an unknown schedule. We
>> do
>> not have enough man po
Le 31/05/2016 à 22:26, Georg Baum a écrit :
We need to decide: Either have a fixed schedule, and an unknown feature set
of the next release, or a fixed feature set, and an unknown schedule. We do
not have enough man power for defining both a fixed feature set and a fixed
release schedule.
I pre
On Tue, May 31, 2016 at 10:26:57PM +0200, Georg Baum wrote:
> Guillaume Munch wrote:
> - Have a build server that does automatic builds on a regular basis for all
> three platforms (Linux, OS X, windows) and makes binary packages and build
> logs available.
This would be a great way to get feed
On Thu, Jun 02, 2016 at 02:00:20AM +0200, Uwe Stöhr wrote:
> There are 2 large security holes in ImageMagick (and also GraphicsMagick)
> that have been fixed:
> (article in German:
> http://www.heise.de/newsticker/meldung/Luecke-in-ImageMagick-und-GraphicsMagick-ermoeglicht-erneute-Angriffe-322381
There are 2 large security holes in ImageMagick (and also
GraphicsMagick) that have been fixed:
(article in German:
http://www.heise.de/newsticker/meldung/Luecke-in-ImageMagick-und-GraphicsMagick-ermoeglicht-erneute-Angriffe-3223811.html)
I therefore decided to release a new installer for LyX 2
On Tue, May 31, 2016 at 10:26:57PM +0200, Georg Baum wrote:
> Guillaume Munch wrote:
>
> > Le 26/05/2016 07:45, Jean-Marc Lasgouttes a écrit :
> >
> >> Time to think about the release date of 2.3.0 now ;)
> >>
> >
> > Yes, let's have this discussion :)
> >
> > I find the interval between featur
Guillaume Munch wrote:
> Le 26/05/2016 07:45, Jean-Marc Lasgouttes a écrit :
>
>> Time to think about the release date of 2.3.0 now ;)
>>
>
> Yes, let's have this discussion :)
>
> I find the interval between feature releases too high. Having an
> interval longer than one year (more than two fo
Guillaume Munch wrote:
> The schedule could be decided in advance, and be on the website for
> clarity.
This is more or less decision of release manager and his style. Some
releases had that and some did not.
> In addition I would suggest the following: (Officially) allow new
> features that do
Le 26/05/2016 07:45, Jean-Marc Lasgouttes a écrit :
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
On Sat, May 28, 2016 at 03:36:28AM +0200, Uwe Stöhr wrote:
> Am 27.05.2016 um 09:20 schrieb Scott Kostyshak:
>
> > > 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/
>
> Just for information: Today I te
Am 27.05.2016 um 09:20 schrieb Scott Kostyshak:
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/
Just for information: Today I tested a lot more and despite minir issues
(e.g. 2 residues after uninstalling LyX) they
Scott Kostyshak wrote:
> The tarballs for LyX 2.2.0 can be found at
>
> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/lyx-2.2.0/
>
quickly tested on ubuntu 12.04 & gentoo x86 and seemed ok. p
On Fri, May 27, 2016 at 03:09:59AM +0200, Uwe Stöhr wrote:
> 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.d
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
privi
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 MiKT
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 reason
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 g
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 warnin
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 LyX/MiKTeX
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 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 t
Am Montag, den 23.05.2016, 22:32 -0400 schrieb Scott Kostyshak:
> Hi all,
>
> The tarballs for LyX 2.2.0 can be found at
>
> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/lyx-2.2.0/
>
> As usual I'll wait before announcing the release until after
> uploading
> the bina
Am Dienstag, 24. Mai 2016 um 21:16:33, schrieb Georg Baum
> Scott Kostyshak wrote:
>
> > Hi all,
> >
> > The tarballs for LyX 2.2.0 can be found at
> >
> > ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/lyx-2.2.0/
>
> Builds and runs fine on debian
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 time for the mirrors.
>
> Great job Scott! Many thanks for all your patient
On 05/24/2016 06:29 PM, 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 time for the mirrors.
>
> Great job Scott! Many thanks for all your patient work.
>
> I built it
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 time for the mirrors.
Great job Scott! Many thanks for all your patient work.
I built it now and noticed 2 things:
- There is a dataloss warn
Scott Kostyshak wrote:
> Hi all,
>
> The tarballs for LyX 2.2.0 can be found at
>
> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/lyx-2.2.0/
Builds and runs fine on debian 8.1, except when configuring with version
suffix: http://www.lyx.org/trac/ticket/10159. Since this also happens
Hi all,
The tarballs for LyX 2.2.0 can be found at
ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/lyx-2.2.0/
As usual I'll wait before announcing the release until after uploading
the binaries and providing some time for the mirrors.
Thanks to everyone for all the help with the final steps i
On 10/13/2015 07:05 PM, Uwe Stöhr wrote:
Hi Richard,
due to bug http://www.lyx.org/trac/ticket/9733 I released a new
installer:
http://ftp.lyx.de/LyX%202.1.4/
Could you please put it on ftp.lyx.org?
The bug is not our fault but the users of course expect that a basic
thing like the spell c
Hi Richard,
due to bug http://www.lyx.org/trac/ticket/9733 I released a new installer:
http://ftp.lyx.de/LyX%202.1.4/
Could you please put it on ftp.lyx.org?
The bug is not our fault but the users of course expect that a basic
thing like the spell checker works.
thanks and regards
Uwe
Christian Ridderström gmail.com> writes:
>
>
> Hi,
>
>
> A long time ago (2012) I tried setting up an FTP server but couldn't get
it to work in a fashion I felt was secure enough. But now during my vacation
I've had time to try again in peace and quiet. A
Hi,
A long time ago (2012) I tried setting up an FTP server but couldn't get it
to work in a fashion I felt was secure enough. But now during my vacation
I've had time to try again in peace and quiet. And it seems I've got it
working.
The FTP server is VSFTP (https://secur
24/04/2014 14:41, Alessandro Di Federico:
On Mon, 14 Apr 2014 19:47:13 +0200
Vincent van Ravesteijn wrote:
As usual I'll wait for the packagers to provide the binaries before
announcing the release.
Hi! When are you going to announce the release? In a few weeks we're
going to have the fourth
On Mon, 14 Apr 2014 19:47:13 +0200
Vincent van Ravesteijn wrote:
> As usual I'll wait for the packagers to provide the binaries before
> announcing the release.
Hi! When are you going to announce the release? In a few weeks we're
going to have the fourth LyX Workshop here at POuL and we are wil
On Mon, Apr 14, 2014 at 7:47 PM, Vincent van Ravesteijn wrote:
> Hi all,
>
> The tarballs for LyX 2.1.0 can be found at
>
Ubuntu packages are now available on the PPA:
https://launchpad.net/~lyx-devel/+archive/release
Liviu
> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.1/lyx-2.1.0/
&g
Am 16.04.2014 17:46, schrieb Vincent van Ravesteijn:
you can find the installers for LyX 2.1.0 here:
https://sourceforge.net/projects/lyxwininstaller/files/TestVersions/
(I'll add the installer improvements we discussed the next days as soon as I
find the time.)
Hello Vincent,
I found now
Stephan Witt schreef op 17-4-2014 8:17:
Am 14.04.2014 um 19:47 schrieb Vincent van Ravesteijn :
Hi all,
The tarballs for LyX 2.1.0 can be found at
ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.1/lyx-2.1.0/
As usual I'll wait for the packagers to provide the binaries before announcing
the re
s. We have paragraph about this in download section of our web.
>
> It helps to ensure that the file's contents has not been changed by someone
> else than
> by the one owing private key. You might know about the cases when attackers
> get into
> ftp infrastructure of some pr
27;s contents has not been changed by someone
else than
by the one owing private key. You might know about the cases when attackers get
into
ftp infrastructure of some projects and added backdoors to the code released.
This
helps until they also succesfully hack into computers of the people who do the
releases ;)
Pavel
On Apr 16, 2014, at 11:17 PM, Stephan Witt wrote:
> Am 14.04.2014 um 19:47 schrieb Vincent van Ravesteijn :
>
>> Hi all,
>>
>> The tarballs for LyX 2.1.0 can be found at
>>
>> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.1/lyx-2.1.0/
>>
>> As
Am 14.04.2014 um 19:47 schrieb Vincent van Ravesteijn :
> Hi all,
>
> The tarballs for LyX 2.1.0 can be found at
>
> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.1/lyx-2.1.0/
>
> As usual I'll wait for the packagers to provide the binaries before
> announcing the rel
Am 14.04.2014 um 20:00 schrieb Richard Heck :
>
> The tarballs for LyX 2.0.8 can be found at:
>
> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.0/2.0.8/
>
> Please prepare binaries. I aim to release when 2.1.0 goes out.
The package for mac is here:
https://dl.dropboxusercontent.
Uwe Stöhr schreef op 16-4-2014 0:58:
Am 14.04.2014 19:47, schrieb Vincent van Ravesteijn:
Hi all,
The tarballs for LyX 2.1.0 can be found at
ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.1/lyx-2.1.0/
As usual I'll wait for the packagers to provide the binaries before
announcing the release.
On Monday 14 April 2014 19:47:13 Vincent van Ravesteijn wrote:
> Hi all,
>
> The tarballs for LyX 2.1.0 can be found at
>
> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.1/lyx-2.1.0/
>
> As usual I'll wait for the packagers to provide the binaries before
> announc
1 - 100 of 301 matches
Mail list logo
