public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Allen Hewes <allen@decisiv.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [ANNOUNCEMENT] cygwin 3.3.4-1
Date: Tue, 1 Feb 2022 00:23:20 +0000	[thread overview]
Message-ID: <MN2PR17MB3999C6B2B1704A65BAC0DD25B8269@MN2PR17MB3999.namprd17.prod.outlook.com> (raw)
In-Reply-To: <82972d74-5395-2444-6e42-454c576ea579@comcast.net>



> -----Original Message-----
> From: Cygwin <cygwin-bounces+allen=decisiv.net@cygwin.com> On Behalf
> Of David Schuler
> Sent: Monday, January 31, 2022 7:04 PM
> To: cygwin@cygwin.com
> Subject: Re: [ANNOUNCEMENT] cygwin 3.3.4-1
>
> For those of us who are experiencing this problem, what is the actual
> method of resolving this problem?  It's not obvious to me.
>

I manually downloaded the XZ package from a mirror. Then decompressed it. Then replaced the cygwin1.dll in my Cygwin install directory (C:\Cygwin64).
http://mirrors.dotsrc.org/cygwin/x86_64/release/cygwin/cygwin-3.3.3-1.tar.xz

Then re-run Setup and choose the prior version in the drop down menu for the cygwin-* package(s).

Setup can run without Cygwin. It's the post-install bits/jobs/tasks that require a functioning Cygwin install. Which means you should be able to start Setup, then change it to "All" (from "Pending") on the "Select Packages" dialog. Then find your installed "cygwin-"  packages, then to the right is a drop down. Choose the previous version 3.3.3-1 (from 3.3.4-1).

Of course you can wait till the just released update lands on your mirror or pick-n-choose mirrors until you find one with the 3.3.4-2 version on it.

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.

  reply	other threads:[~2022-02-01  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 12:04 Corinna Vinschen via Cygwin-announce
2022-01-31 18:34 ` Jim Reisert AD1C
2022-01-31 18:38   ` David Rothenberger
2022-01-31 18:49     ` Allen Hewes
2022-01-31 22:20       ` Adam Dinwoodie
2022-02-01  0:03         ` David Schuler
2022-02-01  0:23           ` Allen Hewes [this message]
2022-02-01 17:02   ` Jim Reisert AD1C

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=MN2PR17MB3999C6B2B1704A65BAC0DD25B8269@MN2PR17MB3999.namprd17.prod.outlook.com \
    --to=allen@decisiv.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).