Re: problems with latest mega-upgrade | PM utility not found?
Evan Cooch <[email protected]>
| Newsgroups | gmane.comp.tex.miktex |
|---|---|
| Message-ID | <[email protected]> |
Well, my 2 cents Canadian (1.85 cents American) On 06/23/2015 06:03 PM, Colin McLarty wrote: > I normally update every couple of days, but stagger the updates > over several computers so in the rare event that one causes a problem I am > still okay. More or less what I do -- I'm in the lucky position of having multiple machines. My 'test machine', my 'one step back' machine, and my 'mission critical machine'. I do updates on the test machine. If now smoke and flames, then after about a week, put them on my 'one step back' machine. Another week, browsing MikTeX maillist archives, then apply to mission critical. Probably overkill, especially since I can roll back out of the .zip backup I make (and have mirrored on multiple cloud servers), but LaTeX is an essential application. If it fails, I'd die...or have to use Word, which at some obvious levels is probably redundant. > > But now I hope to get advice on when to do the mega-upgrade while > travelling in China. I will be travelling well into August. I have only > one computer with me, I absolutely need to be able to run LaTeX, I have > limited web access and I have a lot of other demands on my energy and time. If LaTeX is currently working, then I'd say, do nothing. If it ain't broke, don't fix... > > On the other hand, because I especially want to get all security updates I don't see anything in the current list of upgrades that smacks of a 'security fix', but someone closer to 'source' would need to confirm. > > On Tue, Jun 23, 2015 at 9:27 AM, Evan Cooch <[email protected]> wrote: > >> 1\ make .zip or equivalent backup of my current MikTeX install. If you >> install as a single-user, this works fine. You can roll back to this >> version simply by extracting everything back out from the .zip archive. > > I know enough that I could probably do this correctly But I have never > actually done such a thing and am not *sure* I would get it right. > > So I suppose my best option is to wait until the upgrade stabilizes and the > bugs are caught and worked out. Is that right? > > Should I just wait until people stop reporting new problems on this list? > Or should I give it a couple of weeks? Or how should I judge when it is > time to do? > > Colin > ------------------------------------------------------------------------------ > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors > network devices and physical & virtual servers, alerts via email & sms > for fault. Monitor 25 devices for free with no restriction. Download now > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > _______________________________________________ > To unsubscribe from this list, please visit %(user_optionsurl)s and choose Unsubscribe > ------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o _______________________________________________ To unsubscribe from this list, please visit %(user_optionsurl)s and choose Unsubscribe