Re: miktex update has no effect

2018-01-31 Thread Scott Kostyshak
On Wed, Jan 31, 2018 at 11:08:23PM +, Uwe Stöhr wrote:
> Am 31.01.2018 um 21:22 schrieb Scott Kostyshak:
> 
> > Why "force"? When there is a MiKTeX update the repositories refuse to
> > work with older MiKTeX installations? Why isn't the MiKTeX installation
> > itself just updated without LyX needing to do anything?
> 
> Because I triggered a redevelopment of the way how packages are installed.
> Therefore the command line parameters to do this will be changed.

Ah I see. So this is just a one-time issue and it's not that any update
of MiKTeX would force us to release a new installer. That's good to
know.

> However, I see that no MiKTeX installer with these changes has been
> published yet. I will act when this is the case.

OK.

Thanks for your help on this,

Scott


signature.asc
Description: PGP signature


Re: miktex update has no effect

2018-01-31 Thread Uwe Stöhr

Am 31.01.2018 um 21:22 schrieb Scott Kostyshak:


Why "force"? When there is a MiKTeX update the repositories refuse to
work with older MiKTeX installations? Why isn't the MiKTeX installation
itself just updated without LyX needing to do anything?


Because I triggered a redevelopment of the way how packages are 
installed. Therefore the command line parameters to do this will be changed.
However, I see that no MiKTeX installer with these changes has been 
published yet. I will act when this is the case.


regards Uwe


Re: miktex update has no effect

2018-01-31 Thread Scott Kostyshak
On Wed, Jan 31, 2018 at 04:25:19PM +, Uwe Stöhr wrote:
> Am 31.01.2018 um 08:01 schrieb Ian Worthington:
> 
> > Going to the update wizard via the package manager, rather than directly
> > (even as admin) seems to fix the problem.
> 
> I see that MiKTeX released a new major version yesterday. Therefore some
> package repositories were not yet synced.

> @ Scott: The MiKTeX update will probably force me to release another
> installer for RC2. I'll have a look as soon as I find time.

Why "force"? When there is a MiKTeX update the repositories refuse to
work with older MiKTeX installations? Why isn't the MiKTeX installation
itself just updated without LyX needing to do anything?

Would the bundle be the only binary affected or would the installer
binary also change?

Thanks,

Scott


signature.asc
Description: PGP signature


Re: miktex update has no effect

2018-01-31 Thread Uwe Stöhr

Am 31.01.2018 um 08:01 schrieb Ian Worthington:

Going to the update wizard via the package manager, rather than directly 
(even as admin) seems to fix the problem.


I see that MiKTeX released a new major version yesterday. Therefore some 
package repositories were not yet synced.


@ Scott: The MiKTeX update will probably force me to release another 
installer for RC2. I'll have a look as soon as I find time.


regards Uwe


Re: miktex update has no effect

2018-01-30 Thread Ian Worthington
 Danke Uwe.
Going to the update wizard via the package manager, rather than directly (even 
as admin) seems to fix the problem.
thanks,
Ian
On Tuesday, January 30, 2018, 11:59:39 PM GMT-5, Uwe Stöhr 
 wrote:  
 
 Am 30.01.2018 um 07:31 schrieb Ian Worthington:

 > 1. When I do a miktex update and select packages to update, there is 
activity, and no errors recorded in the log, but when I return to the 
update package list nothing has changed.

This sounds like a problem with the package repository.
An unfinished update explains your second problem.

Therefore please start MiKTeX's update program (the Admin version) via 
the Windows start menu. At first try to run the update normally. If this 
succeeds, please run the update again because for older installations 2 
runs could be necessary.
If the update is still not successful, restart the MiKTeX update and 
select in the welcome page to select another package repository. Then it 
should work. If so, please also run the update a second time until there 
are no more updates found.

regards Uwe
  

Re: miktex update has no effect

2018-01-30 Thread Uwe Stöhr

Am 30.01.2018 um 07:31 schrieb Ian Worthington:

> 1. When I do a miktex update and select packages to update, there is 
activity, and no errors recorded in the log, but when I return to the 
update package list nothing has changed.


This sounds like a problem with the package repository.
An unfinished update explains your second problem.

Therefore please start MiKTeX's update program (the Admin version) via 
the Windows start menu. At first try to run the update normally. If this 
succeeds, please run the update again because for older installations 2 
runs could be necessary.
If the update is still not successful, restart the MiKTeX update and 
select in the welcome page to select another package repository. Then it 
should work. If so, please also run the update a second time until there 
are no more updates found.


regards Uwe


Re: miktex update has no effect

2018-01-30 Thread Uwe Stöhr

Am 30.01.2018 um 07:31 schrieb Ian Worthington:


I've just installed the lyx 2.3 rc on my windows 10 system.

I have two problems so far:

1. When I do a miktex update and select packages to update, there is 
activity, and no errors recorded in the log, but when I return to the 
update package list nothing has changed.


This sounds like a problem with the package repository.
An unfinished update explains your second problem.

Therefore please start MiKTeX's update program (the Admin version) via 
the Windows start menu. At first try to run the update normally. If this 
succeeds, please run the update again because for older installations 2 
runs could be necessary.
If the update is still not successful, restart the MiKTeX update and 
select in the welcome page to select another package repository. Then it 
should work. If so, please also run the update a second time until there 
are no more updates found.


regards Uwe


Re: miktex update has no effect

2018-01-30 Thread Ian Worthington
 This is the bundle.
Maybe it's still in the log?  Where do I find that?
Ian
On Tuesday, January 30, 2018, 1:09:29 PM GMT-5, Scott Kostyshak 
 wrote:  
 
 On Tue, Jan 30, 2018 at 06:31:12AM +, Ian Worthington wrote:
> I've just installed the lyx 2.3 rc on my windows 10 system.

Thanks for testing, Ian!

Did you test the bundle or the non-bundle?

> I have two problems so far:
> 1. When I do a miktex update and select packages to update, there is 
> activity, and no errors recorded in the log, but when I return to the update 
> package list nothing has changed.
> 2. The very first time I clicked VIEW on the sample document it gave an error 
> message, which I regret I neglected to make a note of.  It works fine 
> subsequently, but something to be aware of for new users maybe?

That is indeed good to know. I wonder what happened. If you do see that
error again it would be interesting to see the log.

Thanks for your feedback,

Scott
  

Re: miktex update has no effect

2018-01-30 Thread Scott Kostyshak
On Tue, Jan 30, 2018 at 06:31:12AM +, Ian Worthington wrote:
> I've just installed the lyx 2.3 rc on my windows 10 system.

Thanks for testing, Ian!

Did you test the bundle or the non-bundle?

> I have two problems so far:
> 1. When I do a miktex update and select packages to update, there is 
> activity, and no errors recorded in the log, but when I return to the update 
> package list nothing has changed.
> 2. The very first time I clicked VIEW on the sample document it gave an error 
> message, which I regret I neglected to make a note of.  It works fine 
> subsequently, but something to be aware of for new users maybe?

That is indeed good to know. I wonder what happened. If you do see that
error again it would be interesting to see the log.

Thanks for your feedback,

Scott


miktex update has no effect

2018-01-29 Thread Ian Worthington
I've just installed the lyx 2.3 rc on my windows 10 system.
I have two problems so far:
1. When I do a miktex update and select packages to update, there is activity, 
and no errors recorded in the log, but when I return to the update package list 
nothing has changed.
2. The very first time I clicked VIEW on the sample document it gave an error 
message, which I regret I neglected to make a note of.  It works fine 
subsequently, but something to be aware of for new users maybe?
Ian