On 31/01/2024 19:14, Lester Ingber via Cygwin wrote:
Assuming we are still in /etc/postinstall/
I see no file with that name?
that is strange.
Have you tried to re-install the package ?
As the AV eaten the file ?
On my wife's system (the broken system) I see
source ca-certificates.sh
(line
On 2024-01-31 06:40, David Allsopp via Cygwin wrote:
Starting with this very trivial C program:
#include
#include
int main(void) {
printf("Zstandard v%d\n", ZSTD_versionNumber());
}
and compiling with
x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
when I then run ./test.exe, I get the
On 2024-01-31 10:36, ASSI via Cygwin wrote:
Jon Turney via Cygwin writes:
If upstream really is making multiple releases called '6.4', which
we're supposed to distinguish by some other means, then there aren't
really any good answers...
There's only one official 6.4 release, but just about ev
Assuming we are still in /etc/postinstall/
I see no file with that name?
On my wife's system (the broken system) I see
source ca-certificates.sh
(line is blank)
On my system, I see only
ca-certificates.dash.done
ca-certificates.sh.done
Lester
--
Problem reports: https://cygwin.com/proble
On 31/01/2024 18:36, Lester Ingber via Cygwin wrote:
The outcome is 1.
Lester
so you need debugging
$ set -x
$ source ./ca-certificates.sh
on my system the output is:
+ source ./ca-certificates.sh
++ '[' '!' -e /etc/pki/ca-trust/ca-legacy.conf ']'
++ '[' -f /etc/pki/ca-trust/ca-legacy.con
Jon Turney via Cygwin writes:
> If upstream really is making multiple releases called '6.4', which
> we're supposed to distinguish by some other means, then there aren't
> really any good answers...
There's only one official 6.4 release, but just about everyone packages
one of the roughly weekly s
The outcome is 1.
Lester
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
On 31/01/2024 17:40, Lester Ingber via Cygwin wrote:
I just installed the latest Cygwin on our two PCs. I was hoping this
would take care of this problem, but it did not. On just one of the PCs, I see
(in black):
Package: _/Unknown package
ca-certificates.sh exit code 1
The other PC is f
On 31/01/2024 17:36, Eliah Kagan via Cygwin wrote:
Hi,
However, I was able to make a *fairly* simple script that reliably
produces it, at least on my machine (and on GitHub Actions runners). It
seems to me that this script may give some insight. In case it's useful:
import hashlib
import
I just installed the latest Cygwin on our two PCs. I was hoping this
would take care of this problem, but it did not. On just one of the PCs, I see
(in black):
Package: _/Unknown package
ca-certificates.sh exit code 1
The other PC is fine with all installations.
--
Problem reports:
Hi,
The fastest way to produce the problem described in
https://cygwin.com/pipermail/cygwin/2024-January/255267.html and
https://cygwin.com/pipermail/cygwin/2024-January/255273.html seems to be
to run `pip install ...` on a version of `pip` that uses its vendored
`rich` dependency to draw prog
On Wed, Jan 31, 2024 at 2:41 PM David Allsopp via Cygwin wrote:
>
> Starting with this very trivial C program:
>
> #include
> #include
>
> int main(void) {
> printf("Zstandard v%d\n", ZSTD_versionNumber());
> }
>
> and compiling with
>
> x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
>
> whe
On Wed, Jan 31, 2024 at 2:39 PM Jon Turney via Cygwin wrote:
>
> On 21/01/2024 22:13, Brian Inglis via Cygwin wrote:
> > On 2024-01-21 14:12, ASSI via Cygwin wrote:
> >> Brian Inglis via Cygwin writes:
> >>> Previous maintainer added some artificial single digit release
> >>> prefixes (in a few pa
On 1/31/2024 7:40 AM, David Allsopp via Cygwin wrote:
Starting with this very trivial C program:
#include
#include
int main(void) {
printf("Zstandard v%d\n", ZSTD_versionNumber());
}
and compiling with
x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
when I then run ./test.exe, I get t
Starting with this very trivial C program:
#include
#include
int main(void) {
printf("Zstandard v%d\n", ZSTD_versionNumber());
}
and compiling with
x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
when I then run ./test.exe, I get the Windows critical-error-handler
dialog stating "The code
On 21/01/2024 22:13, Brian Inglis via Cygwin wrote:
On 2024-01-21 14:12, ASSI via Cygwin wrote:
Brian Inglis via Cygwin writes:
Previous maintainer added some artificial single digit release
prefixes (in a few packages), but we decided to drop those and use the
release date directly as used in
On 1/31/2024 3:16 AM, ASSI via Cygwin wrote:
Heiko Oberdiek via Cygwin writes:
I assume, luatex from texlive-collection-luatex
needs to be recompiled with the updated zlib
sources.
Yes, and that version check needs to actually look at the ABI and not
some random string; or at least not complai
On 30/01/2024 18:24, Bruce Jerrick wrote:
In setup.ini, python3-3.9.18-1 is [current], and depends on python39,
but python39-3.9.18-1 is [test] (python39-3.9.16-1 is [current] ).
Hi Bruce,
the python3 is almost only a stub to pull python39 in this moment,
so the mismatch should have no impact.
Heiko Oberdiek via Cygwin writes:
> I assume, luatex from texlive-collection-luatex
> needs to be recompiled with the updated zlib
> sources.
Yes, and that version check needs to actually look at the ABI and not
some random string; or at least not complain when only the minor version
changes. OTO
19 matches
Mail list logo
