From: Dan Harkless <www@harkless.org>
To: 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 10:26:37 -0800 [thread overview]
Message-ID: <ffe5e172-7548-69b3-efe8-d80255059f8e@harkless.org> (raw)
In-Reply-To: <announce.8d9a857b-7ee1-f731-87a0-78b1f1c93c7b@dronecode.org.uk>
On 1/15/2022 9:27 AM, Jon Turney wrote:
>
> The following packages have been uploaded to the Cygwin distribution:
>
> * xorg-server-21.1.3-1
> * xorg-server-common-21.1.3-1
> * xorg-server-extra-21.1.3-1
> * xorg-server-devel-21.1.3-1
> * xorg-server-xorg-21.1.3-1
> * xwinclip-21.1.3-1
>
> These packages contain XWin and the other X.Org X11 servers.
>
> In addition to upstream fixes [1], the following cygwin-specific
> changes have been made since 21.1.2-2:
>
> * Rework display number locking to avoid left-over socket files
> causing problems.
> Addresses: https://cygwin.com/pipermail/cygwin/2022-January/250419.html
>
> [1] https://lists.x.org/archives/xorg-announce/2022-January/003127.html
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?
I tried every https mirror, but none of them have the new versions. I've
been having trouble with the X server and xwin-xdg-menu failing to start
up properly (in a semi-non-repeatable way), so I was hoping to get this
update now.
I tried upgrading setup-x86_64.exe to 2.915, in case some fix was needed
to get the new packages to show up, but like the last several versions
of the setup programs (2.909 is the last one I remember working), it
doesn't work on my Windows 8.1 system (with all available MS updates).
Running the installer from Explorer results in nothing happening
whatsoever.
Running setup from bash as Administrator results in:
Starting cygwin install, version 2.915
User has backup/restore rights
User has symlink creation right
*** --symlink-type lnk is not implemented
I've had my CYGWIN environment variable set to "wincmdln
winsymlinks:lnk" for ages, and it's always worked before. I /highly/
prefer the lnk implementation of symlinks, since it allows me to make
them from non-Admin shells, etc.
--
Dan Harkless
http://harkless.org/dan/
next prev parent reply other threads:[~2022-01-15 18:28 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 ` Dan Harkless [this message]
2022-01-15 18:31 ` [ANNOUNCEMENT] xorg-server-21.1.3-1 / recent setups not working on Win8 / winsymlinks:lnk 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
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=ffe5e172-7548-69b3-efe8-d80255059f8e@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).