Re: using older Lyx documents after upgrading

2016-07-20 Thread PhilipPirrip

On 07/19/2016 06:50 AM, Michael Berger wrote:

but trying to compile any of my classicthesis-LyX-v4.1 documents I get
either an endless loop or heaps of errors - there are so many different
errors that I eventually gave up trying to fix them


I can't confirm this, even classicthesis for LyX v. 3 compiles well - as 
it should, there's nothing in LyX that has changed that should make it 
impossible.
An endless loop of errors sometimes means you only need to change one 
thing... some packages are known to have updates that are not backwards 
compatible and can break things horribly.





Re: using older Lyx documents after upgrading

2016-07-19 Thread Scott Kostyshak
On Wed, Jul 20, 2016 at 06:55:25AM +0200, Michael Berger wrote:
> 
> To be frank, I am surprised that by now all but two my of old documents
> (Miede's classicthesis) do compile after changing/adapting just one or two
> details - most documents compiled off the cuff!
> And for these two last documents I found my way: a combination of copy
> and/or redoing other parts.

Great!

> Forgetting the frustration and thinking of the benefits and learning effects
> I have no regrets :-D.

This is a good attitude to have.

Scott


signature.asc
Description: PGP signature


Re: using older Lyx documents after upgrading

2016-07-19 Thread Michael Berger



On 07/20/2016 02:19 AM, Scott Kostyshak wrote:

On Tue, Jul 19, 2016 at 12:50:19PM +0200, Michael Berger wrote:

Hi all, this is to share my experience with other users and asking for help
from the developers. ;-)

I have quite a number of LyX documents made in Mageia5 using LyX 2.1;
TexLive 2013; classicthesis-LyX-v4.1, most of them with the module
'Linguistics' loaded and using different bibliography styles.

After upgrading to LyX 2.2.0; TexLive2016; classicthesis-LyX-v4.2 and
loading those older documents I found the following when trying to export to
PDF:

I don't know much about this stuff, but in general you do not want to
upgrade several critical components at once. Ideally you should upgrade
one system (e.g. LyX), test, if everything goes well, upgrade another
system (e.g. Koma-Script), test, etc. And whenever you upgrade, you
should always make sure you can easily downgrade. If you can't easily go
back to how you had it before, take a step back and ask yourself "do I
really need to upgrade"? You will learn through frustration that
upgrades break things. This will always be true. But since you are
learning more about Linux you will learn how to create a robust workflow
and how to easily go back to how you had things before.

Sounds like a frustrating issue. I hope you find a solution and don't
have to redo all of the documents!

Best of luck,

Scott

Thanks Scott,
good comment, very basic but nevertheless quite true: there is no such 
thing like a general recipe or one single reason if things don't work as 
expected after such radical upgrades.


To be frank, I am surprised that by now all but two my of old documents 
(Miede's classicthesis) do compile after changing/adapting just one or 
two details - most documents compiled off the cuff!
And for these two last documents I found my way: a combination of 
copy and/or redoing other parts.


And yes, I could always go back (there were situations when I thought to 
just forget about this whole dam.. idea) without loosing a bit because 
this exercise is done on a separate experimental computer while all my 
work is still there and save on another machine.


Forgetting the frustration and thinking of the benefits and learning 
effects I have no regrets :-D.


Cheers!
Michael




Re: using older Lyx documents after upgrading

2016-07-19 Thread Scott Kostyshak
On Tue, Jul 19, 2016 at 12:50:19PM +0200, Michael Berger wrote:
> Hi all, this is to share my experience with other users and asking for help
> from the developers. ;-)
> 
> I have quite a number of LyX documents made in Mageia5 using LyX 2.1;
> TexLive 2013; classicthesis-LyX-v4.1, most of them with the module
> 'Linguistics' loaded and using different bibliography styles.
> 
> After upgrading to LyX 2.2.0; TexLive2016; classicthesis-LyX-v4.2 and
> loading those older documents I found the following when trying to export to
> PDF:

I don't know much about this stuff, but in general you do not want to
upgrade several critical components at once. Ideally you should upgrade
one system (e.g. LyX), test, if everything goes well, upgrade another
system (e.g. Koma-Script), test, etc. And whenever you upgrade, you
should always make sure you can easily downgrade. If you can't easily go
back to how you had it before, take a step back and ask yourself "do I
really need to upgrade"? You will learn through frustration that
upgrades break things. This will always be true. But since you are
learning more about Linux you will learn how to create a robust workflow
and how to easily go back to how you had things before.

Sounds like a frustrating issue. I hope you find a solution and don't
have to redo all of the documents!

Best of luck,

Scott


signature.asc
Description: PGP signature


Re: using older Lyx documents after upgrading

2016-07-19 Thread Dr Eberhard Lisse
That seems to be a LaTeX issue,

export to LaTeX and look at the errors there.

el


On 2016-07-19 11:50, Michael Berger wrote:
> Hi all, this is to share my experience with other users and asking for
> help from the developers. ;-)
> 
> I have quite a number of LyX documents made in Mageia5 using LyX 2.1;
> TexLive 2013; classicthesis-LyX-v4.1, most of them with the module
> 'Linguistics' loaded and using different bibliography styles.
> 
> After upgrading to LyX 2.2.0; TexLive2016; classicthesis-LyX-v4.2 and
> loading those older documents I found the following when trying to
> export to PDF:
> 
>   * Beamer presentations > OK
>   * All types of Koma-Script documents >> basically OK with some minor
> adjustments, inter alia regarding the bibliography style, e.g. oscola
>   * classicthesis-LyX-v4.2_biblatex_biber and
> classicthesis-LyX-v4.2_biblatex_bibtex8 >> do compile all example
> files as well as their original 'ClassicThesis.lyx' template without
> any problem.
>   * but trying to compile any of my classicthesis-LyX-v4.1 documents I
> get either an endless loop or heaps of errors - there are so many
> different errors that I eventually gave up trying to fix them
> 
> I also started copying parts of my old documents into a new one but even
> text that I considered not very special produced errors.
> 
> Authoring everything entirely new seems to be the only way as far as I
> see now. Well is that it?
> 
> Any explanation, clue, advice etc. is highly appreciated.
> 
> Cheers and thanks,
> 
> Michael
> 




using older Lyx documents after upgrading

2016-07-19 Thread Michael Berger
Hi all, this is to share my experience with other users and asking for 
help from the developers. ;-)


I have quite a number of LyX documents made in Mageia5 using LyX 2.1; 
TexLive 2013; classicthesis-LyX-v4.1, most of them with the module 
'Linguistics' loaded and using different bibliography styles.


After upgrading to LyX 2.2.0; TexLive2016; classicthesis-LyX-v4.2 and 
loading those older documents I found the following when trying to 
export to PDF:


 * Beamer presentations > OK
 * All types of Koma-Script documents >> basically OK with some minor
   adjustments, inter alia regarding the bibliography style, e.g. oscola
 * classicthesis-LyX-v4.2_biblatex_biber and
   classicthesis-LyX-v4.2_biblatex_bibtex8 >> do compile all example
   files as well as their original 'ClassicThesis.lyx' template without
   any problem.
 * but trying to compile any of my classicthesis-LyX-v4.1 documents I
   get either an endless loop or heaps of errors - there are so many
   different errors that I eventually gave up trying to fix them

I also started copying parts of my old documents into a new one but even 
text that I considered not very special produced errors.


Authoring everything entirely new seems to be the only way as far as I 
see now. Well is that it?


Any explanation, clue, advice etc. is highly appreciated.

Cheers and thanks,

Michael