From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: headache on build repeatibility: octave vs BLODA ?
Date: Tue, 28 Jan 2020 20:04:00 -0000 [thread overview]
Message-ID: <6143b338-38ca-6157-711d-fae6ef431297@gmail.com> (raw)
In-Reply-To: <87h80febmg.fsf@Otto.invalid>
Am 28.01.2020 um 18:25 schrieb ASSI:
> Achim Gratz writes:
>> Same thing hereâ¦
>
> Since some of the discussion revolved on Windows versions: that is on
> Win10 Pro 1909, fully patched. I no longer have a system with 1809
> since the period where you could hold up the update has expired
> recently. There is an ISO image for Windows Server 2016 LTS
> (essentially 1709 I think) that you can use for free for 90 days (you
> can install it into a VHD and then boot that). To (offixcially) get other Windows
> versions for testing you'd either have to have the licenses or have some
> sort of subscription with MSDN. If you do have older install media or
> ISO, then of course you can do the install into the VHD trick again. A
> Win 10 Pro can boot the VHD in a Hyper-V instance.
>
>
> Regards,
> Achim.
>
Ok Achim,
you destroyed my theory
I just found that my W10 Home is 1909 build 18363.592 so probably was
updated as your around mid Jan
https://docs.microsoft.com/en-us/windows/release-information/
But Corporate versions have different time table and patch
the one I have is Version 1709 Build 16299.15
It seems Corporate IT is forgetting to update it at all.
May be Takashi one is also behind in update and currently free
from the new bug/behaviour.
What I found interesting is that
https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1909
This release had caused problems to some AV, so may be is changing
the play in area that are causing problems also to us.
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-01-28 20:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 16:55 Marco Atzeri
2020-01-25 18:15 ` Brian Inglis
2020-01-27 6:54 ` Marco Atzeri
2020-01-25 20:36 ` Achim Gratz
2020-01-26 6:58 ` Marco Atzeri
2020-01-26 8:05 ` ASSI
2020-01-26 8:38 ` Marco Atzeri
2020-01-27 6:45 ` Marco Atzeri
2020-01-27 11:33 ` Takashi Yano
2020-01-28 6:41 ` Marco Atzeri
2020-01-28 14:55 ` Takashi Yano
2020-01-29 9:44 ` Corinna Vinschen
2020-01-29 12:19 ` Marco Atzeri
2020-01-29 13:46 ` Takashi Yano
2020-01-29 15:11 ` Takashi Yano
2020-01-29 15:32 ` Corinna Vinschen
2020-01-29 15:34 ` Corinna Vinschen
2020-01-29 16:08 ` Takashi Yano
2020-01-29 17:57 ` Corinna Vinschen
2020-01-30 21:05 ` Brian Inglis
2020-01-30 21:34 ` Marco Atzeri
2020-01-28 17:26 ` ASSI
2020-01-28 20:04 ` Marco Atzeri [this message]
2020-01-28 20:21 ` Achim Gratz
2020-01-26 2:42 ` Takashi Yano
2020-01-26 5:11 ` Takashi Yano
2020-01-26 10:24 ` Marco Atzeri
2020-01-26 10:31 ` Takashi Yano
2020-01-29 0:03 ` Hans-Bernhard Bröker
2020-01-29 0:39 ` Hans-Bernhard Bröker
2020-01-29 5:10 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6143b338-38ca-6157-711d-fae6ef431297@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).