The following packages have been uploaded to the Cygwin distribution
as test releases:
* libicu71-71.1-1
* libicu-devel-71.1-1
* icu-doc-71.1-1
ICU is a mature, widely used set of C/C++ and Java libraries providing Unicode
and Globalization support for software applications. ICU is widely
The following packages have been uploaded to the Cygwin distribution
as test releases:
* libicu71-71.1-1
* libicu-devel-71.1-1
* icu-doc-71.1-1
ICU is a mature, widely used set of C/C++ and Java libraries providing Unicode
and Globalization support for software applications. ICU is widely
On Mon, 2022-04-11 at 13:58 +0100, Jon Turney wrote:
> Historically, xorg packages were usually provided as .gz and .bz2
> compressed tarballs. The current trend is to no longer provide .bz2,
> but .gz and .xz instead. Allow the compression to be configured, with a
> backwards compatible
> Run cygport ... all with --debug flag which enables shell tracing
I'll answer it myself. If the cygport is given the filename *without*
".cygport" extension, it executes, but wrongly detects the PVR -
NAME/VERSION/RELEASE. When I provided full name, it works as I'd
expected. I think this
The following packages have been uploaded to the Cygwin distribution:
* libicu70-70.1-1
* libicu-devel-70.1-1
* icu-doc-70.1-1
ICU is a mature, widely used set of C/C++ and Java libraries providing Unicode
and Globalization support for software applications. ICU is widely portable and
gives
The following packages have been uploaded to the Cygwin distribution:
* libicu70-70.1-1
* libicu-devel-70.1-1
* icu-doc-70.1-1
ICU is a mature, widely used set of C/C++ and Java libraries providing Unicode
and Globalization support for software applications. ICU is widely portable and
gives
--- Begin Message ---
I'm working to phase out the ftp urls on my main website,
and see these files in cygwinports using the ftp urls:
byacc/byacc.cygport
dialog/dialog.cygport
diffstat/diffstat.cygport
luit/luit.cygport
ncurses/ncurses.cygport
tack/tack.cygport
xterm/xterm.cygport
The change
Hi,
Any updates regarding my Previous Email?
So I could get back with Counts and Cost.
Awaiting your response!
Regards,
Electa
From: Electa Kovacek
Sent: Friday, April 8, 2022 12:56 AM
To: 'cygwin@cygwin.com'
Subject: Certified Nursing Assistants Info.
Hi,
I'm curious to know if you'd
The following packages have been uploaded to the Cygwin distribution as test
releases:
* ghostscript-9.56.0-1
* libgs9-9.56.0-1
* libgs-devel-9.56.0-1
GNU Ghostscript is a PostScript interpreter capable of converting PS files into
a number of printer output formats. Ghostscript can also
The following packages have been uploaded to the Cygwin distribution as test
releases:
* ghostscript-9.56.0-1
* libgs9-9.56.0-1
* libgs-devel-9.56.0-1
GNU Ghostscript is a PostScript interpreter capable of converting PS files into
a number of printer output formats. Ghostscript can also
The following packages have been uploaded to the Cygwin distribution as test
releases:
* harfbuzz-4.2.0-1
* libharfbuzz0-4.2.0-1
* libharfbuzz-devel-4.2.0-1
* libharfbuzz-gobject0-4.2.0-1
* libharfbuzz-gobject-devel-4.2.0-1
* libharfbuzz-subset0-4.2.0-1
* libharfbuzz-subset-devel-4.2.0-1
*
The following packages have been uploaded to the Cygwin distribution as test
releases:
* harfbuzz-4.2.0-1
* libharfbuzz0-4.2.0-1
* libharfbuzz-devel-4.2.0-1
* libharfbuzz-gobject0-4.2.0-1
* libharfbuzz-gobject-devel-4.2.0-1
* libharfbuzz-subset0-4.2.0-1
* libharfbuzz-subset-devel-4.2.0-1
*
On 4/11/2022 3:58 PM, Ken Brown via Cygwin-announce wrote:
The following packages have been uploaded to the Cygwin distribution:
* lcms2-2.13-1
* liblcms2_2-2.13-1
* liblcms2-devel-2.13-1
Sorry this should be 2.13.1-1.
Little CMS intends to be an Open Source small-footprint color management
The following packages have been uploaded to the Cygwin distribution:
* lcms2-2.13-1
* liblcms2_2-2.13-1
* liblcms2-devel-2.13-1
Little CMS intends to be an Open Source small-footprint color management engine,
with special focus on accuracy and performance. It uses the International Color
The following packages have been uploaded to the Cygwin distribution:
* lcms2-2.13-1
* liblcms2_2-2.13-1
* liblcms2-devel-2.13-1
Little CMS intends to be an Open Source small-footprint color management engine,
with special focus on accuracy and performance. It uses the International Color
On 10/13/2021 8:01 PM, Ken Brown via Cygwin-announce via Cygwin wrote:
The following packages have been uploaded to the Cygwin distribution
as test releases:
* ghostscript-9.55.0-1
* libgs9-9.55.0-1
* libgs-devel-9.55.0-1
This has now been promoted from test to current.
Ken
--
Problem
On Mon, 11 Apr 2022, Alexey Izbyshev wrote:
> Yes, sshd is running as a service, but I'm not sure that patch is relevant. In
> my case, the problematic pipe that the hanging conhost.exe is waiting on is
> probably created for that specific conhost.exe process within the process tree
> rooted at
> On 11/04/2022 14:02, Andrew Schulman via Cygwin-apps wrote:
> > After all this time I feel that I should know the answer to this, but here
> > goes.
> >
> > I have fish-3.4.1-1, a bugfix release. I want it to replace fish-3.4.0-1,
> > leaving fish-3.3.1-1 as the previous release.
> >
> >
On 2022-04-11 08:23, Jeremy Drake wrote:
On Sat, 9 Apr 2022, Alexey Izbyshev wrote:
I don't have mintty because "make" is run via an SSH session. I
suppose
I should look into sshd in this case?
Sshd wouldn't happen to be running as a service, would it?
On 11/04/2022 14:45, Andrew Schulman via Cygwin-apps wrote:
After all this time I feel that I should know the answer to this, but here
goes.
I have fish-3.4.1-1, a bugfix release. I want it to replace fish-3.4.0-1,
leaving fish-3.3.1-1 as the previous release.
What's the best way to do this?
On 11/04/2022 14:02, Andrew Schulman via Cygwin-apps wrote:
After all this time I feel that I should know the answer to this, but here
goes.
I have fish-3.4.1-1, a bugfix release. I want it to replace fish-3.4.0-1,
leaving fish-3.3.1-1 as the previous release.
What's the best way to do this?
> After all this time I feel that I should know the answer to this, but here
> goes.
>
> I have fish-3.4.1-1, a bugfix release. I want it to replace fish-3.4.0-1,
> leaving fish-3.3.1-1 as the previous release.
>
> What's the best way to do this? Should I create override.hint, with
>
> keep:
On 2022-04-08 20:04, Brian Inglis wrote:
On 2022-04-08 02:42, Alexey Izbyshev wrote:
There is also an additional detail that I forgot to mention: in the
stack trace of all leaf processes as displayed by ProcessHacker, it
seems that the executable entry point is not reached yet. The only
After all this time I feel that I should know the answer to this, but here
goes.
I have fish-3.4.1-1, a bugfix release. I want it to replace fish-3.4.0-1,
leaving fish-3.3.1-1 as the previous release.
What's the best way to do this? Should I create override.hint, with
keep: 3.3.1-1
Historically, xorg packages were usually provided as .gz and .bz2
compressed tarballs. The current trend is to no longer provide .bz2,
but .gz and .xz instead. Allow the compression to be configured, with a
backwards compatible default.
---
cygclass/xorg.cygclass | 13 -
1 file
/x86/test/cygwin1-20220411.dll.xz
https://tyan0.yr32.net/cygwin/x86_64/test/cygwin1-20220411.dll.xz
Could you please test? To keep the hanging tree, please install
cygwin another directory, and replace cygwin1.dll with the
countermeasure version.
Thank you for providing the binaries! I've started
On Sun, 10 Apr 2022 22:23:06 -0700 (PDT)
Jeremy Drake wrote:
> On Sat, 9 Apr 2022, Alexey Izbyshev wrote:
>
> > I don't have mintty because "make" is run via an SSH session. I suppose
> > I should look into sshd in this case?
>
> Sshd wouldn't happen to be running as a service, would it?
>
>
new_owner, _write_pipe,
> 0, TRUE, DUPLICATE_SAME_ACCESS);
>
> Is it safe to create an *inheritable* handle in another process here?
> Could it be that the target process spawns a child at the wrong moment
> (e.g. before it even knows about the newly created
28 matches
Mail list logo
