Re: [LyX/master] Cmake build: Ignore boost settings if we are using std-regex

[Kornel Benko]

Am Samstag, 29. Juli 2017 um 19:14:01, schrieb Scott Kostyshak 

> On Thu, Jul 27, 2017 at 11:32:06PM +0200, Kornel Benko wrote:
> > commit 2fe59adbc89f56e7e192b57c90eb5e2a8338721c
> > Author: Kornel Benko 
> > Date:   Thu Jul 27 23:29:29 2017 +0200
> > 
> > Cmake build: Ignore boost settings if we are using std-regex
> > 
> > External/included boost is only used for the component regex
> 
> With this commit, I get the following message:
> 
> Unable to determine the system directory having searched
>   /home/scott/lyxbuilds/master/CMakeBuild/share/lyx/
> Use the '-sysdir' command line parameter or set the environment variable
> LYX_DIR_23x to the LyX system directory containing the file 
> `chkconfig.ltx'.
> 
> Scott

Totally unexpected. What should boost have to do with system dir?
Could you please test with clean build?

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Options for resolving the minted + shell-escape issue

[Scott Kostyshak]

On Sat, Jul 29, 2017 at 07:51:08PM -0400, Scott Kostyshak wrote:
> On Sat, Jul 29, 2017 at 05:48:46PM -0400, Scott Kostyshak wrote:
> > On Fri, Jul 28, 2017 at 11:31:42PM +0200, Enrico Forestieri wrote:
> > > On Tue, Jul 25, 2017 at 09:16:15PM +0200, Enrico Forestieri wrote:
> > > 
> > > > I am also investigating the possibility of attaching a context menu to
> > > > the red icon in the status bar.
> > > 
> > > This is now done in the attached patch. Hovering with the mouse over the
> > > red icon a warning is shown, and right clicking shows a popup menu that
> > > allows to disable the shell escape option for the current document.
> > 
> > I'm trying to test the patch with respect to d3b2cb09, because I could
> > not compile current master for some reason.
> 
> I was able to apply the patch at 770ab9a8 and successfully compile it.
> The improvements look good. I've only noticed one issue so far:
> 
> If I remove the python-pygments module (and reconfigure) and test, I get
> the following error:
> 
> The driver command necessary to use the minted package
> (pygmentize) has not been found. Make sure you have
> the python-pygments module installed or, if the driver
> is named differently, to add the following line to the
> document preamble:
> 
> \AtBeginDocument{\renewcommand{\MintedPygmentize}{driver}}
> 
> where 'driver' is name of the driver command.
> 
> I expected to get the error, but what I was surprised by is that I get
> the error when going to Document > Settings. I expected to get an error
> immediately after compiling (before the LaTeX log errors). Is that
> expected? Note that I am using a compiled Qt 5.9.2dev so if you can't
> reproduce, it is probably a bug on my side.

I should clarify that the above comment has nothing to do with the
patch. It is about the previously implemented minted support.

Scott


signature.asc
Description: PGP signature

Re: Going into dangerous mode (Was: Can shell-escape take advantage of needauth framework?)

[Scott Kostyshak]

On Sun, Jul 30, 2017 at 12:12:08AM +0200, Enrico Forestieri wrote:
> On Sat, Jul 29, 2017 at 05:54:33PM -0400, Scott Kostyshak wrote:
> > 
> > More important to me is that we interpret "take responsibility" in a
> > different way. Enrico, if we decide to go forward with something like
> > the latest patch, will you be around in the next couple of months and
> > willing to make potential updates and fixes?
> 
> Yes, of course.

OK good to know. 

> By not endorsing it I meant I was not pushing for its
> approval.

That's what I understood. My question was more because I wasn't sure if
e.g. you were going on vacation.

Scott


signature.asc
Description: PGP signature

Re: Options for resolving the minted + shell-escape issue

[Scott Kostyshak]

On Sat, Jul 29, 2017 at 05:48:46PM -0400, Scott Kostyshak wrote:
> On Fri, Jul 28, 2017 at 11:31:42PM +0200, Enrico Forestieri wrote:
> > On Tue, Jul 25, 2017 at 09:16:15PM +0200, Enrico Forestieri wrote:
> > 
> > > I am also investigating the possibility of attaching a context menu to
> > > the red icon in the status bar.
> > 
> > This is now done in the attached patch. Hovering with the mouse over the
> > red icon a warning is shown, and right clicking shows a popup menu that
> > allows to disable the shell escape option for the current document.
> 
> I'm trying to test the patch with respect to d3b2cb09, because I could
> not compile current master for some reason.

I was able to apply the patch at 770ab9a8 and successfully compile it.
The improvements look good. I've only noticed one issue so far:

If I remove the python-pygments module (and reconfigure) and test, I get
the following error:

The driver command necessary to use the minted package
(pygmentize) has not been found. Make sure you have
the python-pygments module installed or, if the driver
is named differently, to add the following line to the
document preamble:

\AtBeginDocument{\renewcommand{\MintedPygmentize}{driver}}

where 'driver' is name of the driver command.

I expected to get the error, but what I was surprised by is that I get
the error when going to Document > Settings. I expected to get an error
immediately after compiling (before the LaTeX log errors). Is that
expected? Note that I am using a compiled Qt 5.9.2dev so if you can't
reproduce, it is probably a bug on my side.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Cmake build: Ignore boost settings if we are using std-regex

[Scott Kostyshak]

On Thu, Jul 27, 2017 at 11:32:06PM +0200, Kornel Benko wrote:
> commit 2fe59adbc89f56e7e192b57c90eb5e2a8338721c
> Author: Kornel Benko 
> Date:   Thu Jul 27 23:29:29 2017 +0200
> 
> Cmake build: Ignore boost settings if we are using std-regex
> 
> External/included boost is only used for the component regex

With this commit, I get the following message:

Unable to determine the system directory having searched
/home/scott/lyxbuilds/master/CMakeBuild/share/lyx/
Use the '-sysdir' command line parameter or set the environment variable
LYX_DIR_23x to the LyX system directory containing the file `chkconfig.ltx'.

Scott


signature.asc
Description: PGP signature

Re: Options for resolving the minted + shell-escape issue

[Kornel Benko]

Am Samstag, 29. Juli 2017 um 17:57:52, schrieb Scott Kostyshak 

> On Thu, Jul 20, 2017 at 03:30:14PM -0400, Richard Heck wrote:
> > On 07/20/2017 01:21 AM, Jürgen Spitzmüller wrote:
> > > Am Mittwoch, den 19.07.2017, 16:37 +0200 schrieb Enrico Forestieri:
> > >> The attached patch takes into account all of these ideas. As a
> > >> disclaimer,
> > >> note that I am providing it only because I am now familiar with this
> > >> part
> > >> of the code and can quickly come up with a patch. But I am not
> > >> endorsing it.
> > > I propose to apply this patch and return to productivity.
> > 
> > I would agree with that.
> 
> I'm concerned that since this issue has left us all exhausted, there is
> a feeling of "let's just get this over so we can move on". I encourage
> all of us to give one more cognitive spurt and give a vote.
> 
> From what I understand, the three options are still what I proposed
> three weeks ago [1]:
> 
> 1. Revert the recently added minted support.
> 
> 2. Keep the current state of master.
> 
> 3. Apply the patch at [2]. Don't forget to copy emblem-shellescape.svgz
> to lib/images. (Note that I get linker errors when I try to apply the
> latest patch, but it might be something specific to my setup.)

I opt for this one. There is work to be done for tests, but this looks doable.

> So I ask explicitly to everyone (even if you think you have already
> voted, please give your vote again): who has given the latest patch a
> good test, has looked at the code (the patch is not so long), and votes
> in favor of one of the three options?
> 
> Please also feel free to say that you have tested the patch but choose
> to abstain from voting. This way I will know that even if the vote is
> only 2 to 1, at least the rest of the developers are indifferent, rather
> than not having tested. But I ask that everyone tests the patch and says
> something. If you are lost because you had the fortune of not following
> the debate, let us know so we can tell you what to test, and can point
> you to some advantages/disadvantages of each option.
> 
> Scott
> 
> 
> [1]
> https://www.mail-archive.com/search?l=mid=20170705045915.h4uyrsc27g54da3m%40steph
> [2]
> https://www.mail-archive.com/search?l=mid=20170728213142.GA7880%40GIOVE

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Options for resolving the minted + shell-escape issue

[Kornel Benko]

Am Samstag, 29. Juli 2017 um 17:48:46, schrieb Scott Kostyshak 

> On Fri, Jul 28, 2017 at 11:31:42PM +0200, Enrico Forestieri wrote:
> > On Tue, Jul 25, 2017 at 09:16:15PM +0200, Enrico Forestieri wrote:
> > 
> > > I am also investigating the possibility of attaching a context menu to
> > > the red icon in the status bar.
> > 
> > This is now done in the attached patch. Hovering with the mouse over the
> > red icon a warning is shown, and right clicking shows a popup menu that
> > allows to disable the shell escape option for the current document.
> 
> I'm trying to test the patch with respect to d3b2cb09, because I could
> not compile current master for some reason.
> 
> I get linker errors. I attach the errors from both CMake and autotools.
> If you think my problems are due to using an older commit or something
> else specific to my system, please don't spend time on it. I'll figure
> out soon why I cannot compile current master on CMake. Maybe that will
> somehow fix the issue.
> 
> Scott

I had no errors, neither compile nor link with cmake build.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Going into dangerous mode (Was: Can shell-escape take advantage of needauth framework?)

[Enrico Forestieri]

On Sat, Jul 29, 2017 at 05:54:33PM -0400, Scott Kostyshak wrote:
> 
> More important to me is that we interpret "take responsibility" in a
> different way. Enrico, if we decide to go forward with something like
> the latest patch, will you be around in the next couple of months and
> willing to make potential updates and fixes?

Yes, of course. By not endorsing it I meant I was not pushing for its
approval.

-- 
Enrico

Re: Options for resolving the minted + shell-escape issue

[Scott Kostyshak]

On Thu, Jul 20, 2017 at 03:30:14PM -0400, Richard Heck wrote:
> On 07/20/2017 01:21 AM, Jürgen Spitzmüller wrote:
> > Am Mittwoch, den 19.07.2017, 16:37 +0200 schrieb Enrico Forestieri:
> >> The attached patch takes into account all of these ideas. As a
> >> disclaimer,
> >> note that I am providing it only because I am now familiar with this
> >> part
> >> of the code and can quickly come up with a patch. But I am not
> >> endorsing it.
> > I propose to apply this patch and return to productivity.
> 
> I would agree with that.

I'm concerned that since this issue has left us all exhausted, there is
a feeling of "let's just get this over so we can move on". I encourage
all of us to give one more cognitive spurt and give a vote.

From what I understand, the three options are still what I proposed
three weeks ago [1]:

1. Revert the recently added minted support.

2. Keep the current state of master.

3. Apply the patch at [2]. Don't forget to copy emblem-shellescape.svgz
to lib/images. (Note that I get linker errors when I try to apply the
latest patch, but it might be something specific to my setup.)

So I ask explicitly to everyone (even if you think you have already
voted, please give your vote again): who has given the latest patch a
good test, has looked at the code (the patch is not so long), and votes
in favor of one of the three options?

Please also feel free to say that you have tested the patch but choose
to abstain from voting. This way I will know that even if the vote is
only 2 to 1, at least the rest of the developers are indifferent, rather
than not having tested. But I ask that everyone tests the patch and says
something. If you are lost because you had the fortune of not following
the debate, let us know so we can tell you what to test, and can point
you to some advantages/disadvantages of each option.

Scott


[1]
https://www.mail-archive.com/search?l=mid=20170705045915.h4uyrsc27g54da3m%40steph
[2]
https://www.mail-archive.com/search?l=mid=20170728213142.GA7880%40GIOVE


signature.asc
Description: PGP signature

Re: Going into dangerous mode (Was: Can shell-escape take advantage of needauth framework?)

[Scott Kostyshak]

On Thu, Jul 27, 2017 at 04:09:56PM +0200, Guillaume MM wrote:

> * One has to decide which suggestions are needed for 2.3 and which ones
> can be implemented later.

Agreed. And the more immediate issue is which suggestions are needed
before beta1. Conditional on LyX devs supporting something like the
current patch, I'm fine with moving with the current state for beta.
However, I would like to see a stronger vote of support before I
conclude that LyX devs are indeed in favor of the approach (more on this
in a separate email).

> * Having to use -shell-escape for running Pygments.

Yes, and if we go the way of the patch, I don't think any other
improvements (e.g. post-beta1) will be made to address this, until
perhaps 2.4.0 if the Github issues is addressed.

> I would also be more comfortable if somebody takes responsibility for
> any patch that is to be committed, given that the author has said that
> they do not endorse it.

Fair point. My goal with the vote was to collectively take
responsibility, since this is an important patch and involves security.
But I feel that most people are just tired of the debate and are hoping
too much to move forward that they have not taken a deep look.

As for my personal opinion, I keep coming back to "I think this improves
security" (as I perceive the word, explained at [1]). I'm not *sure*
that it improves security, but all I can do is go with my best guess
(taking into account of course, that we are almost at beta stage). If I
am wrong and we end up shipping a LyX version that it turns out is less
secure, I will certainly blame myself.

More important to me is that we interpret "take responsibility" in a
different way. Enrico, if we decide to go forward with something like
the latest patch, will you be around in the next couple of months and
willing to make potential updates and fixes? If not, we will need to see
if anyone else can task responsibility for making potential fixes
post-beta pre-final.

Thanks to everyone for all of their time on this issue.

Scott


[1]
https://www.mail-archive.com/search?l=mid=20170721201254.hvh6jrbc3yrjxqr7%40steph


signature.asc
Description: PGP signature

Re: Options for resolving the minted + shell-escape issue

[Scott Kostyshak]

On Sat, Jul 29, 2017 at 02:03:52AM +0200, Tommaso Cucinotta wrote:

> 3) I liked to propose addition of support for running Gnuplot scripts as 
> well, with the corresponding converter tagged as a 'needauth' one
> [ this last feature cannot be tagged as a security enhancement,

(clarifying, in case anyone was wondering why Tommaso said the above):
because we did not previously ship Gnuplot.

Scott


signature.asc
Description: PGP signature

Re: Options for resolving the minted + shell-escape issue

[Scott Kostyshak]

On Fri, Jul 28, 2017 at 11:31:42PM +0200, Enrico Forestieri wrote:
> On Tue, Jul 25, 2017 at 09:16:15PM +0200, Enrico Forestieri wrote:
> 
> > I am also investigating the possibility of attaching a context menu to
> > the red icon in the status bar.
> 
> This is now done in the attached patch. Hovering with the mouse over the
> red icon a warning is shown, and right clicking shows a popup menu that
> allows to disable the shell escape option for the current document.

I'm trying to test the patch with respect to d3b2cb09, because I could
not compile current master for some reason.

I get linker errors. I attach the errors from both CMake and autotools.
If you think my problems are due to using an older commit or something
else specific to my system, please don't spend time on it. I'll figure
out soon why I cannot compile current master on CMake. Maybe that will
somehow fix the issue.

Scott
/home/scott/lyxbuilds/master/repo/src/Buffer.cpp:984: undefined reference to 
`lyx::ShellEscapeSection::find(std::__cxx11::basic_string const&) const'
liblyxcore.a(Converter.o): In function 
`lyx::Converters::checkAuth(lyx::Converter const&, 
std::__cxx11::basic_string 
const&, bool)':
/home/scott/lyxbuilds/master/repo/src/Converter.cpp:360: undefined reference to 
`lyx::ShellEscapeSection::findAuth(std::__cxx11::basic_string const&) const'
/home/scott/lyxbuilds/master/repo/src/Converter.cpp:360: undefined reference to 
`lyx::AuthFilesSection::find(std::__cxx11::basic_string const&) const'
/home/scott/lyxbuilds/master/repo/src/Converter.cpp:367: undefined reference to 
`lyx::ShellEscapeSection::insert(std::__cxx11::basic_string const&, bool)'
/home/scott/lyxbuilds/master/repo/src/Converter.cpp:369: undefined reference to 
`lyx::AuthFilesSection::insert(std::__cxx11::basic_string const&)'
liblyxcore.a(LyX.o): In function 
`lyx::ShellEscapeSection::~ShellEscapeSection()':
/home/scott/lyxbuilds/master/repo/src/Session.h:347: undefined reference to 
`vtable for lyx::ShellEscapeSection'
/home/scott/lyxbuilds/master/repo/src/Session.h:347: undefined reference to 
`vtable for lyx::ShellEscapeSection'
/home/scott/lyxbuilds/master/repo/src/Session.h:347: undefined reference to 
`vtable for lyx::ShellEscapeSection'
liblyxcore.a(Session.o): In function 
`lyx::ShellEscapeSection::ShellEscapeSection()':
/home/scott/lyxbuilds/master/repo/src/Session.h:351: undefined reference to 
`vtable for lyx::ShellEscapeSection'
liblyxcore.a(Session.o): In function 
`lyx::ShellEscapeSection::~ShellEscapeSection()':
/home/scott/lyxbuilds/master/repo/src/Session.h:347: undefined reference to 
`vtable for lyx::ShellEscapeSection'
frontends/qt4/liblyxqt4.a(GuiView.o): In function 
`lyx::frontend::GuiView::disableShellEscape()':
/home/scott/lyxbuilds/master/repo/src/frontends/qt4/GuiView.cpp:661: undefined 
reference to `lyx::ShellEscapeSection::remove(std::__cxx11::basic_string const&)'
frontends/qt4/liblyxqt4.a(GuiDocument.o): In function 
`lyx::frontend::GuiDocument::shellescapeChanged()':
/home/scott/lyxbuilds/master/repo/src/frontends/qt4/GuiDocument.cpp:1550: 
undefined reference to 
`lyx::ShellEscapeSection::remove(std::__cxx11::basic_string const&)'
/home/scott/lyxbuilds/master/repo/src/frontends/qt4/GuiDocument.cpp:1551: 
undefined reference to 
`lyx::ShellEscapeSection::find(std::__cxx11::basic_string const&) const'
/home/scott/lyxbuilds/master/repo/src/frontends/qt4/GuiDocument.cpp:1552: 
undefined reference to 
`lyx::ShellEscapeSection::insert(std::__cxx11::basic_string const&, bool)'
collect2: error: ld returned 1 exit status
Makefile:2125: recipe for target 'lyx' failed
make[4]: *** [lyx] Error 1
make[4]: Leaving directory '/home/scott/lyxbuilds/master/repo/src'
Makefile:2467: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/home/scott/lyxbuilds/master/repo/src'
Makefile:1703: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/home/scott/lyxbuilds/master/repo/src'
Makefile:575: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/scott/lyxbuilds/master/repo'
Makefile:470: recipe for target 'all' failed
make: *** [all] Error 2

CMakeFiles/lyx.dir/Session.cpp.o: In function 
`lyx::ShellEscapeSection::ShellEscapeSection()':
/home/scott/lyxbuilds/master/repo/src/Session.h:351: undefined reference to 
`vtable for lyx::ShellEscapeSection'
CMakeFiles/lyx.dir/Session.cpp.o: In function 
`lyx::ShellEscapeSection::~ShellEscapeSection()':

Re: #10735: needauth - ask again authorization if file (or script snippet) changes

[Scott Kostyshak]

On Sat, Jul 29, 2017 at 07:33:23PM +0200, Christian Ridderström wrote:
> Hoping/testing if a simple reply works and is added to the ticket.

I wish. That would be nice. I've wondered in the past whether simply
disabling the reply-to to lyx-devel would be a "second-best". There are
many fragmented conversations because of this.

I pasted your response into the trac ticket.

Scott


signature.asc
Description: PGP signature

Re: #10735: needauth - ask again authorization if file (or script snippet) changes

[Christian Ridderström]

Hoping/testing if a simple reply works and is added to the ticket.

I think this is an excellent improvement.
However, I'd like to suggest that instad of storing a timestamp, we should
store a hash of the document's contents.

I'm not sure if it's necessary to include the file name in what's hashed.
For instance, let's say we approve running (the content of) doc1.lyx.
Would we automatically be ok with running (the content of) an identical
document named doc_with_a_different_name.lyx?

Perhaps it'd be nice if the hash could be done only on the "code" parts.
OTOH, perhaps we can't be sure that the code parts don't depend on the
content of the non-code parts.  Similarly, in theory the code parts could
perhaps depend on the name of the document, or it's absolute path.

/C

On 29 July 2017 at 02:03, LyX Ticket Tracker  wrote:

> #10735: needauth - ask again authorization if file (or script snippet)
> changes
> -+--
>  Reporter:  t.cucinotta  |  Owner:  rgheck
>  Type:  enhancement  | Status:  new
>  Priority:  normal   |  Milestone:
> Component:  converters   |Version:  2.3.0dev
>  Severity:  normal   |   Keywords:
> -+--
>  Related to #10481.
>
>  If I authorize conversion on a file, its absolute filepath is remembered
>  by LyX, in a section of $HOME/.lyx/session. If the document is updated
>  later, e.g., saved from an e-mail, updated from git/svn/cvs, then said
>  authorization should be automatically revoked.
>  Namely, we need to store in the session also the timestamp of the last
>  authorized file, so that, when it changes, we ask authorization again.
>
> --
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor
>

Re: Obsoleted, inaccessible or wrong urls in some documents

[Jean-Pierre Chrétien]

Le 29/07/2017 à 13:14, mn a écrit :



On 29.07.17 12:20, Kornel Benko wrote:

Hi,
the url

"ftp://ftp.dante.de/tex-archive/info/math/voss/mathmode/Mathmode.pdf;

is no longer accessible. The new one is available under
"https://www.tug.org/~hvoss/PDF/mathmode.pdf;
Affected documents are "lib/doc/(.|de|es|fr|ja)/Math.lyx"

Other inaccessible urls (maybe temporary)


http://download.gna.org/lettre_observatoire/release/20151201_v2.354/lettre.zip

in lib/templates/lettre.lyx


This one in wrong forever, the Gna! service closed recently.
I'm trying to find a replacement.

--
Jean-Pierre

Re: Obsoleted, inaccessible or wrong urls in some documents

[mn]

On 29.07.17 12:20, Kornel Benko wrote:

> Urls blocked because of security
> http://www.edpsciences.fr/aa/
>   in lib/doc/(.|de|es|fr|ja)/Additional.lyx


That whole section in Additional.lyx needs to be checked.

> 
> 6.1.1 Introduction
> 
> This section describes how LyX can be used […] 
> using Version _5.01_ of the document class aa.cls. 

Current version of the package in question:
\def\filedate{2016/09/01}
\let\aafiledate\filedate
\def\fileversion{9.1}


greetings
Mike

Re: Obsoleted, inaccessible or wrong urls in some documents

[mn]

On 29.07.17 12:20, Kornel Benko wrote:

> Urls blocked because of security
> http://www.edpsciences.fr/aa/
>   in lib/doc/(.|de|es|fr|ja)/Additional.lyx

The given link just uses an invalid security cert.
The site is accessible – and empty.

The journal in question seems to reside now under:
https://www.aanda.org
The ftp link seems to be active.

greetings
Mike

Re: Obsoleted, inaccessible or wrong urls in some documents

[mn]

On 29.07.17 12:20, Kornel Benko wrote:
> Hi,
> the url
"ftp://ftp.dante.de/tex-archive/info/math/voss/mathmode/Mathmode.pdf;
> is no longer accessible. The new one is available under
>   "https://www.tug.org/~hvoss/PDF/mathmode.pdf;
> Affected documents are "lib/doc/(.|de|es|fr|ja)/Math.lyx"
>
> Other inaccessible urls (maybe temporary)
>
http://download.gna.org/lettre_observatoire/release/20151201_v2.354/lettre.zip
>   in lib/templates/lettre.lyx
>
> Urls not found:
> http://publish.aps.org/revtex4/
>   in lib/doc/(.|de|es|fr|ja)/Additional.lyx
>  lib/doc/(.|ja)/LaTeXConfig.lyx
> http://www.aeaweb.org/aer/authref.php
>   in lib/doc/(.|ja)/LaTeXConfig.lyx
> http://www.cs.haifa.ac.il/~dekelts/lyx/
>   in lib/doc/he/Tutorial.lyx
> http://www.cs.virginia.edu/~nr/noweb
>   in lib/doc/de/Additional.lyx
> http://www.cs.virginia.edu/~nr/noweb/
>   in lib/doc/(.|es|fr|ja)/Additional.lyx
> http://www.eecs.harvard.edu/~nr/noweb
>   in lib/examples/listerrors.lyx
>
http://www.physik.uni-augsburg.de/theo3/Comp/hp750c/computing_hp750c_A0.de.shtml
>   in lib/templates/poster-a0poster-simple.lyx
> http://www.stat.uni-muenchen.de/~leisch/Sweave/
>   in lib/examples/(.|ja)/sweave.lyx
> http://www.tug.org/applications/hyperref/ftp/doc/manual.pdf
>   in lib/doc/(.|de|es|fr|ja)/Math.lyx
>
> Urls blocked because of security
> http://www.edpsciences.fr/aa/
>   in lib/doc/(.|de|es|fr|ja)/Additional.lyx
>
> What should be done here?



# Check if they are still relevant.

http://www.cs.haifa.ac.il/~dekelts/lyx/
Seems outdated according to
https://web.archive.org/web/20150919234057/http://cs.haifa.ac.il/~dekelts/lyx/instructions2.html

> http://www.aeaweb.org/aer/authref.php
seems also irrelevant now, according to:
https://web.archive.org/web/20130518073654/http://www.aeaweb.org/aer/authref.php


# Update the links if they have just moved.

> http://publish.aps.org/revtex4/
Is probably now:
https://journals.aps.org/revtex

> http://www.tug.org/applications/hyperref/ftp/doc/manual.pdf
https://www.tug.org/applications/hyperref/manual.html
http://mirrors.ctan.org/macros/latex/contrib/hyperref/doc/manual.pdf



Relevance has to be judged by someone with more expertise.

greetings
Mike

Obsoleted, inaccessible or wrong urls in some documents

[Kornel Benko]

Hi,
the url "ftp://ftp.dante.de/tex-archive/info/math/voss/mathmode/Mathmode.pdf;
is no longer accessible. The new one is available under
"https://www.tug.org/~hvoss/PDF/mathmode.pdf;
Affected documents are "lib/doc/(.|de|es|fr|ja)/Math.lyx"

Other inaccessible urls (maybe temporary)
http://download.gna.org/lettre_observatoire/release/20151201_v2.354/lettre.zip
in lib/templates/lettre.lyx

Urls not found:
http://publish.aps.org/revtex4/
in lib/doc/(.|de|es|fr|ja)/Additional.lyx
   lib/doc/(.|ja)/LaTeXConfig.lyx
http://www.aeaweb.org/aer/authref.php
in lib/doc/(.|ja)/LaTeXConfig.lyx
http://www.cs.haifa.ac.il/~dekelts/lyx/
in lib/doc/he/Tutorial.lyx
http://www.cs.virginia.edu/~nr/noweb
in lib/doc/de/Additional.lyx
http://www.cs.virginia.edu/~nr/noweb/
in lib/doc/(.|es|fr|ja)/Additional.lyx   
http://www.eecs.harvard.edu/~nr/noweb
in lib/examples/listerrors.lyx
http://www.physik.uni-augsburg.de/theo3/Comp/hp750c/computing_hp750c_A0.de.shtml
in lib/templates/poster-a0poster-simple.lyx
http://www.stat.uni-muenchen.de/~leisch/Sweave/
in lib/examples/(.|ja)/sweave.lyx
http://www.tug.org/applications/hyperref/ftp/doc/manual.pdf
in lib/doc/(.|de|es|fr|ja)/Math.lyx

Urls blocked because of security
http://www.edpsciences.fr/aa/
in lib/doc/(.|de|es|fr|ja)/Additional.lyx

What should be done here?

Kornel

signature.asc
Description: This is a digitally signed message part.