public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dan Harkless <www@harkless.org>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] xorg-server-21.1.3-1 / recent setups not working on Win8 / winsymlinks:lnk
Date: Sat, 15 Jan 2022 19:46:35 -0800	[thread overview]
Message-ID: <7bd0e71e-cf81-260c-48e5-47ae8c17e871@harkless.org> (raw)
In-Reply-To: <0bf2a309-4449-5838-21cc-da3db34d59a4@SystematicSw.ab.ca>

On 1/15/2022 2:13 PM, Brian Inglis wrote:
> On 2022-01-15 12:06, Marco Atzeri wrote:
>> On 15.01.2022 19:26, Dan Harkless wrote:
>>> Forgive me if this is a FAQ (I tried searching), but is there a 
>>> standard timeframe in between when a package update is announced on 
>>> the list and when it's actually available on the mirrors?
>> it depends on the specific mirror sync timing.
>> Some are doing every hour, but others every day or more
>
> Check for outdated mirrors at:
>
>     https://cygwin.com/mirrors-report.html
>
> Compare the modified time stamp on your local mirror for:
>
>     $mirror/x86_64/setup.{bz2,ini,xz,zst}
>
> to that on the master for:
>
> {ftp,http,https}://cygwin.com/pub/cygwin/x86{,64}/setup.{bz2,ini,xz,zst}
>
> or just the sha512.sum at each (e.g. using curl -I).

Cool.  Thanks for that magic formula.

>> In this moment however I see on my preferred server that
>> 21.1.3-1 is marked as test.
>>
>> Jon,
>> is it intentional ?
>
> I see 21.1.3-1 as current and 21.1.0-1 as test on my local mirror
>
>     $mirror/x86_64/setup.{bz2,ini,xz,zst}
>
> and also the master
>
> {ftp,http,https}://cygwin.com/pub/cygwin/x86{,64}/setup.{bz2,ini,xz,zst}

Thank you.  I was able to update to the latest X packages this evening.  
Still having trouble with them not working properly on my Windows 8.1 
systems, but it may be related to firewalling and VPN split-tunneling 
not working as I'd expect.  I'll continue to troubleshoot, and hopefully 
someone can look at the setup programs' current failure to work on Win8 
and/or with winsymlinks:lnk set.

-- 
Dan Harkless
http://harkless.org/dan/



  reply	other threads:[~2022-01-16  3:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1444e201-33b0-42a4-08c6-73ffadd4adfc@dronecode.org.uk>
2021-11-29 16:58 ` [ANNOUNCEMENT] xorg-server-21.1.1-1 Jon Turney
2021-12-18 19:32 ` [ANNOUNCEMENT] xorg-server-21.1.2-1 Jon Turney
2021-12-28 18:05   ` Marco Atzeri
2021-12-31 13:48     ` Jon Turney
2021-12-31 22:27       ` Mark Hansen
2021-12-31 22:27         ` Mark Hansen
2022-01-04 16:16 ` [ANNOUNCEMENT] xorg-server-21.1.2-2 Jon Turney
2022-01-15 17:27 ` [ANNOUNCEMENT] xorg-server-21.1.3-1 Jon Turney
2022-01-15 18:26   ` [ANNOUNCEMENT] xorg-server-21.1.3-1 / recent setups not working on Win8 / winsymlinks:lnk Dan Harkless
2022-01-15 18:31     ` Dan Harkless
2022-01-18 15:45       ` Jon Turney
2022-01-15 19:06     ` Marco Atzeri
2022-01-15 22:13       ` Brian Inglis
2022-01-16  3:46         ` Dan Harkless [this message]
2022-01-18 15:46         ` Jon Turney
2022-08-14 11:07 ` [ANNOUNCEMENT] xorg-server-21.1.4-1 Jon Turney
2022-09-21 14:36 ` [ANNOUNCEMENT] xorg-server-21.1.4-2 Jon Turney
2023-06-19 18:06 ` [ANNOUNCEMENT] xorg-server-21.1.8-1 Jon Turney

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=7bd0e71e-cf81-260c-48e5-47ae8c17e871@harkless.org \
    --to=www@harkless.org \
    --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).