On Mon, Nov 12, 2018 at 03:09:13PM +0100, Pavel Sanda wrote:
> The security problems of ghostscript which caused the policy restrictions
> were
> fixed with the release of ghostscript 9.25 (released 2018-09-13).
> I quickly looked at ubuntu packages and 18.04 already ships 9.25, so
> it would be
On Sat, Nov 10, 2018 at 02:32:19PM -0500, Scott Kostyshak wrote:
> On Sat, Nov 10, 2018 at 02:14:58PM -0500, Paul A. Rubin wrote:
> > On 11/5/18 2:32 PM, Jeff Defoe wrote:
> > > I realized I was using the Lyx from the Ubuntu repository. When I
> > > removed it, added the PPA, and installed LyX from
On Sat, Nov 10, 2018 at 02:14:58PM -0500, Paul A. Rubin wrote:
> On 11/5/18 2:32 PM, Jeff Defoe wrote:
> > I realized I was using the Lyx from the Ubuntu repository. When I
> > removed it, added the PPA, and installed LyX from that -- it now seems
> > to work.
> >
> > I do, however, have an odd pr
On 11/5/18 2:32 PM, Jeff Defoe wrote:
I realized I was using the Lyx from the Ubuntu repository. When I
removed it, added the PPA, and installed LyX from that -- it now seems
to work.
I do, however, have an odd problem where graphics often don't display
in LyX, giving errors such as "error lo
I realized I was using the Lyx from the Ubuntu repository. When I removed
it, added the PPA, and installed LyX from that -- it now seems to work.
I do, however, have an odd problem where graphics often don't display in
LyX, giving errors such as "error loading file into memory" or "error
convertin
On 11/2/18, Richard Kimberly Heck wrote:
> Unfortunately, without debug symbols, the backtrace is unreadable. I
> don't know if there is an Ubuntu package that would allow you to install
> them.
If the OP is using the LyX PPA, try to install the lyx-dbg package,
which should give the debugging sy
Can you describe better what triggers this bug?
Unfortunately, without debug symbols, the backtrace is unreadable. I
don't know if there is an Ubuntu package that would allow you to install
them. But you could also try compiling from source with --enable-debug.
Riki
On 11/1/18 9:20 PM, Jeff De
On 9/29/18 7:50 AM, Stephan Witt wrote:
> Am 29.09.2018 um 11:09 schrieb Jürgen Spitzmüller :
>> Am Freitag, den 28.09.2018, 20:51 -0400 schrieb Richard Kimberly Heck:
I think for the sake of clarity we should do that, yes.
>>> OK. I personally do not know how to do this, so I will wait
>>
Am 29.09.2018 um 11:09 schrieb Jürgen Spitzmüller :
>
> Am Freitag, den 28.09.2018, 20:51 -0400 schrieb Richard Kimberly Heck:
>>> I think for the sake of clarity we should do that, yes.
>>
>> OK. I personally do not know how to do this, so I will wait
>
> update version and date in configur
Am Freitag, den 28.09.2018, 20:51 -0400 schrieb Richard Kimberly Heck:
> > I think for the sake of clarity we should do that, yes.
>
> OK. I personally do not know how to do this, so I will wait
update version and date in configure.ac
(this should have been done also for the windows updates,
On 28/09/2018 16:13, Daniel wrote:
Hi,
I am pretty sure that 2) is a bug. Maybe there is a reason for 1) but
then the installer should tell the user to uninstall the old version
first not only under the conditions mentioned in the initial dialog (see
attached screen capture).
"reinstall" in
On 29/09/2018 1:53 p.m., Richard Kimberly Heck wrote:
On 09/28/2018 12:04 PM, Richard Kimberly Heck wrote:
On 9/28/18 10:31 AM, Jürgen Spitzmüller wrote:
Am Freitag, den 28.09.2018, 16:13 +0200 schrieb Daniel:
Maybe there is a reason for 1) but
then the installer should tell the user to uninst
On 09/28/2018 10:52 PM, Andrew Parsloe wrote:
> On 29/09/2018 1:53 p.m., Richard Kimberly Heck wrote:
>> On 09/28/2018 12:04 PM, Richard Kimberly Heck wrote:
>>> On 9/28/18 10:31 AM, Jürgen Spitzmüller wrote:
Am Freitag, den 28.09.2018, 16:13 +0200 schrieb Daniel:
> Maybe there is a reason
On 29/09/2018 1:53 p.m., Richard Kimberly Heck wrote:
On 09/28/2018 12:04 PM, Richard Kimberly Heck wrote:
On 9/28/18 10:31 AM, Jürgen Spitzmüller wrote:
Am Freitag, den 28.09.2018, 16:13 +0200 schrieb Daniel:
Maybe there is a reason for 1) but
then the installer should tell the user to uninst
On 09/28/2018 12:04 PM, Richard Kimberly Heck wrote:
> On 9/28/18 10:31 AM, Jürgen Spitzmüller wrote:
>> Am Freitag, den 28.09.2018, 16:13 +0200 schrieb Daniel:
>>> Maybe there is a reason for 1) but
>>> then the installer should tell the user to uninstall the old version
>>> first not only under
On 09/28/2018 12:04 PM, Richard Kimberly Heck wrote:
> On 9/28/18 10:31 AM, Jürgen Spitzmüller wrote:
>> Am Freitag, den 28.09.2018, 16:13 +0200 schrieb Daniel:
>>> Hi,
>>>
>>> I just checked the new installer. The crashing on closing the PDF
>>> reader seems fixed. However,
>>>
>>> 1) if one insta
On 09/28/2018 12:36 PM, Jürgen Spitzmüller wrote:
> Am Freitag, den 28.09.2018, 12:00 -0400 schrieb Richard Kimberly Heck:
>>> Don’t we need a new version tag to get the 2.3.1.1 in the About
>>> LyX?
>>> I should have ask earlier, I know - sorry.
>>
>> I'm kind of ignorant of that sort of thing. An
Am Freitag, den 28.09.2018, 12:00 -0400 schrieb Richard Kimberly Heck:
> > Don’t we need a new version tag to get the 2.3.1.1 in the About
> > LyX?
> > I should have ask earlier, I know - sorry.
>
>
> I'm kind of ignorant of that sort of thing. Anyone?
I think for the sake of clarity we should
On 9/28/18 10:31 AM, Jürgen Spitzmüller wrote:
> Am Freitag, den 28.09.2018, 16:13 +0200 schrieb Daniel:
>> Hi,
>>
>> I just checked the new installer. The crashing on closing the PDF
>> reader
>> seems fixed. However,
>>
>> 1) if one installs it over the existing version, it will create a
>> seco
On 9/28/18 1:12 AM, Stephan Witt wrote:
> Am 27.09.2018 um 19:56 schrieb Richard Kimberly Heck :
>> On 09/23/2018 02:57 AM, Jürgen Spitzmüller wrote:
>>> Am Samstag, den 22.09.2018, 20:42 +0200 schrieb Stephan Witt:
>> What can be done with it? The error is serious and makes the
>> tex2lyx
Am Freitag, den 28.09.2018, 16:13 +0200 schrieb Daniel:
> Hi,
>
> I just checked the new installer. The crashing on closing the PDF
> reader
> seems fixed. However,
>
> 1) if one installs it over the existing version, it will create a
> second
> LyX version rather than replace the current one.
Am 27.09.2018 um 19:56 schrieb Richard Kimberly Heck :
>
> On 09/23/2018 02:57 AM, Jürgen Spitzmüller wrote:
>> Am Samstag, den 22.09.2018, 20:42 +0200 schrieb Stephan Witt:
> What can be done with it? The error is serious and makes the
> tex2lyx in the original package useless. I propose
On 09/23/2018 02:57 AM, Jürgen Spitzmüller wrote:
> Am Samstag, den 22.09.2018, 20:42 +0200 schrieb Stephan Witt:
What can be done with it? The error is serious and makes the
tex2lyx in the original package useless. I propose to replace the
wrong package with the new one. But is this
Am Samstag, den 22.09.2018, 20:42 +0200 schrieb Stephan Witt:
> > > What can be done with it? The error is serious and makes the
> > > tex2lyx in the original package useless. I propose to replace the
> > > wrong package with the new one. But is this an option? There is
> > > no visible difference
Am 22.09.2018 um 19:33 schrieb Richard Kimberly Heck :
>
> On 09/22/2018 11:25 AM, Stephan Witt wrote:
>> Hi Riki,
>>
>> did you notice the problem report from Paola Manzini? It’s in mail archive
>> here:
>> https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg206434.html
>>
>> We never had
Richard Kimberly Heck wrote:
> >> Any disagreement?
> > That sounds reasonable, but I don't recall many reports from users who
> > have installed the 2.2.3 bundle and reported problems. I guess the
> > problem comes if they try to update MiKTeX after installing the 2.2.3
> > bundle?
>
> The answer
On 05/15/2018 01:14 PM, Scott Kostyshak wrote:
> On Tue, May 15, 2018 at 09:30:09AM +, Pavel Sanda wrote:
>> Richard Kimberly Heck wrote:
>>> I am working on this. I've managed to compile for Windows using mingw on
>>> Linux (amazingly easy, actually) but have not dealt with the packaging
>>> i
On Tue, May 15, 2018 at 09:30:09AM +, Pavel Sanda wrote:
> Richard Kimberly Heck wrote:
> > I am working on this. I've managed to compile for Windows using mingw on
> > Linux (amazingly easy, actually) but have not dealt with the packaging
> > issues yet. Fortunately, someone who reported a bug
Richard Kimberly Heck wrote:
> I am working on this. I've managed to compile for Windows using mingw on
> Linux (amazingly easy, actually) but have not dealt with the packaging
> issues yet. Fortunately, someone who reported a bug to us seems as if
> they may have done so and is giving me some help
On 05/10/2018 02:37 PM, Richard Kimberly Heck wrote:
> On 05/10/2018 11:41 AM, Kornel Benko wrote:
>> Am Mittwoch, 9. Mai 2018 11:59:01 CEST schrieb Richard Kimberly Heck
>> :
>>> On 05/09/2018 11:18 AM, Pavel Sanda wrote:
Jürgen Spitzmüller wrote:
> 2018-05-06 19:50 GMT+02:00 Richard Kim
On 05/10/2018 11:41 AM, Kornel Benko wrote:
> Am Mittwoch, 9. Mai 2018 11:59:01 CEST schrieb Richard Kimberly Heck
> :
>> On 05/09/2018 11:18 AM, Pavel Sanda wrote:
>>> Jürgen Spitzmüller wrote:
2018-05-06 19:50 GMT+02:00 Richard Kimberly Heck:
> I'm intending to close stable to stri
Am Mittwoch, 9. Mai 2018 11:59:01 CEST schrieb Richard Kimberly Heck
:
> On 05/09/2018 11:18 AM, Pavel Sanda wrote:
> > Jürgen Spitzmüller wrote:
> >> 2018-05-06 19:50 GMT+02:00 Richard Kimberly Heck:
> >>
> >>> I'm intending to close stable to string changes shortly, so we can move
> >>> toward 2
Le 09/05/2018 à 03:45, Richard Kimberly Heck a écrit :
6df8c42e59f7d 7bcb78a77875ec 90cfe4ec3b4ff2
Those would be fine with me.
Thanks, they are in now.
JMarc
On 05/09/2018 11:18 AM, Pavel Sanda wrote:
> Jürgen Spitzmüller wrote:
>> 2018-05-06 19:50 GMT+02:00 Richard Kimberly Heck:
>>
>>> I'm intending to close stable to string changes shortly, so we can move
>>> toward 2.3.1. We have a LOT of bug fixes already. Anything that needs
>>> doing before we no
Jürgen Spitzmüller wrote:
> 2018-05-06 19:50 GMT+02:00 Richard Kimberly Heck:
>
> > I'm intending to close stable to string changes shortly, so we can move
> > toward 2.3.1. We have a LOT of bug fixes already. Anything that needs
> > doing before we notify the translators?
> >
>
> Any plans how t
2018-05-06 19:50 GMT+02:00 Richard Kimberly Heck:
> I'm intending to close stable to string changes shortly, so we can move
> toward 2.3.1. We have a LOT of bug fixes already. Anything that needs
> doing before we notify the translators?
>
Any plans how to proceed with the Windows binaries?
Jürg
Le 09/05/2018 à 09:36, Pavel Sanda a écrit :
Those would be fine with me.
JMarc? P
Yes, I am here :) I am busy today, but may manage to do that on Thursday
or Friday.
JMarc
Richard Kimberly Heck wrote:
> On 05/08/2018 06:47 PM, Pavel Sanda wrote:
> > Richard Kimberly Heck wrote:
> >> On 05/08/2018 05:30 AM, Pavel Sanda wrote:
> >>> Richard Kimberly Heck wrote:
> I'm intending to close stable to string changes shortly, so we can move
> toward 2.3.1. We have a
On 05/08/2018 06:47 PM, Pavel Sanda wrote:
> Richard Kimberly Heck wrote:
>> On 05/08/2018 05:30 AM, Pavel Sanda wrote:
>>> Richard Kimberly Heck wrote:
I'm intending to close stable to string changes shortly, so we can move
toward 2.3.1. We have a LOT of bug fixes already. Anything that
Richard Kimberly Heck wrote:
> On 05/08/2018 05:30 AM, Pavel Sanda wrote:
> > Richard Kimberly Heck wrote:
> >> I'm intending to close stable to string changes shortly, so we can move
> >> toward 2.3.1. We have a LOT of bug fixes already. Anything that needs
> >> doing before we notify the translat
On 05/08/2018 05:30 AM, Pavel Sanda wrote:
> Richard Kimberly Heck wrote:
>> I'm intending to close stable to string changes shortly, so we can move
>> toward 2.3.1. We have a LOT of bug fixes already. Anything that needs
>> doing before we notify the translators?
> Not related to translations, but
Richard Kimberly Heck wrote:
> I'm intending to close stable to string changes shortly, so we can move
> toward 2.3.1. We have a LOT of bug fixes already. Anything that needs
> doing before we notify the translators?
Not related to translations, but given mathed still needs some testing
after last
42 matches
Mail list logo
