This is an update to the latest upstream bugfix release of protobuf
21.x.
Protocol Buffers (a.k.a., protobuf) are Google's language-neutral,
platform-neutral, extensible mechanism for serializing structured data.
Note
Upstream changed their version numbering scheme to omit the leading
This is an update to the latest upstream bugfix release of protobuf
21.x.
Protocol Buffers (a.k.a., protobuf) are Google's language-neutral,
platform-neutral, extensible mechanism for serializing structured data.
Note
Upstream changed their version numbering scheme to omit the leading
The following packages have been uploaded to the Cygwin distribution:
libpkgconf-devel-2.0.0-1
libpkgconf4-2.0.0-1
pkg-config-2.0.0-1
pkgconf-2.0.0-1
pkgconf is a program which helps to configure compiler and linker flags
for development frameworks. It is an alternative to pkg-config.
The following packages have been uploaded to the Cygwin distribution:
libpkgconf-devel-2.0.0-1
libpkgconf4-2.0.0-1
pkg-config-2.0.0-1
pkgconf-2.0.0-1
pkgconf is a program which helps to configure compiler and linker flags
for development frameworks. It is an alternative to pkg-config.
ASSI via Cygwin-apps writes:
> That's true for bunzip2 and gunzip, but not for zstd (where the output
> file can be independently specified).
Ah ha. The attached patch recovers to use the `-o` option for `unzstd`.
Regards,
Yasutaka ATARASHI
src_prep_unpack_rev3.patch
Description: Binary data
Yasutaka ATARASHI via Cygwin-apps writes:
> Yeah, I also wonder why the --keep option is not used for .gz and .bz2.
> Now, I recognized the reason.
Thanks.
> `unpack()` is expected to extract the files to the current working
> directory regardless of the specified path of the input. Please see
>
Jon Turney via Cygwin-apps writes:
> Do you have an example of a cygport which fails without this fix, so I
> can add a test for this?
Anything with a SRC_URI or PATCH_URI that has .zst suffix but not
.tar.zst should suffice.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb
Sorry for the late reply.
I updated the patch to handle the case of .xz, also, and a bit
adjusted the arguments of `check_prog_req`.
Jon Turney writes:
>Do you have an example of a cygport which fails without this fix, so I
>can add a test for this?
My motivating example is far from the
On 2023-08-03 17:38, Martin Wege via Cygwin wrote:
On Fri, Aug 4, 2023 at 1:07 AM Martin Wege wrote:
On Thu, Aug 3, 2023 at 8:46 PM Martin Wege wrote:
We are working to deploy the ms-nfs41-nfs-filesystem on our Windows
machines, and encounter some issues with Cygwin (latest stable).
For
v2:
Polish instructions on adding a test
Signed-off-by: Jon Turney
---
winsup/testsuite/README | 82 +
1 file changed, 58 insertions(+), 24 deletions(-)
diff --git a/winsup/testsuite/README b/winsup/testsuite/README
index ff2df4119..511133e4d 100644
---
Use cygrun to isolate the cygload test from the current DLL, which
allows it to pass.
---
winsup/testsuite/cygrun.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/winsup/testsuite/cygrun.sh b/winsup/testsuite/cygrun.sh
index c82c1872b..bf1d5cc6b 100755
---
umask03 fails in CI due to some not understood weirdness.
---
winsup/testsuite/Makefile.am | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/winsup/testsuite/Makefile.am b/winsup/testsuite/Makefile.am
index 8f2967a6d..228955668 100644
--- a/winsup/testsuite/Makefile.am
+++
This gets us down to no permanent failures in the testsuite in CI.
When run locally, msgtest, semtest and shmtest fail because they need a running
cygserver using the test DLL,
and I haven't got a good idea about how to automate that. devdsp fails due to
a hang in child while exiting.
Jon
Add '-notimeout' option for cygrun. This is very useful when using it
to run a test standalone and under a debugger.
Also: warn about excess arguments
---
winsup/testsuite/cygrun.c | 26 ++
1 file changed, 22 insertions(+), 4 deletions(-)
diff --git
Previously, though readahead buffer handling in pty master was not
fully thread-safe, accept_input() was called from peek_pipe() thread
in select.cc. This caused the problem reported in:
https://cygwin.com/pipermail/cygwin/2023-July/253984.html
The mechanism of the problem is:
1) accept_input()
15 matches
Mail list logo