From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: ca-legacy wrong interpreter
Date: Sat, 20 Aug 2022 14:28:02 +0200 [thread overview]
Message-ID: <87bksf85gt.fsf@Rainer.invalid> (raw)
In-Reply-To: <1949755024.20220819124655@yandex.ru> (Andrey Repin's message of "Fri, 19 Aug 2022 12:46:55 +0300")
Andrey Repin writes:
>> /usr/bin/ca-legacy: 81: [[: not found
>> /usr/bin/ca-legacy: Unsupported command install
>> usage: /usr/bin/ca-legacy [check | default | disable | install]
>
> Please change interpreter to /bin/bash.
That's an upstream bug that's been there forever, so I don't see any
urgency to patch that up. What do you need this for, btw?
> Also the new ca-certificates postinstall script named ca-certificates.sh
> instead of .dash as in previous releases.
The dash suffix was produced by a local patch to cygport that I no
longer apply in order to be able to validate the package on the CI
(which uses an unpatched cygport obviously).
> Also, the directory /etc/pki/ca-trust/extracted/pem/directory-hash is
> missing and causes script to fail.
What script fails and how? I do have this directory and it's obviously
kept current by the postinstall script actions (specifically, running
update-ca-trust).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
prev parent reply other threads:[~2022-08-20 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 9:10 Andrey Repin
2022-08-19 9:46 ` Andrey Repin
2022-08-20 12:28 ` Achim Gratz [this message]
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=87bksf85gt.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).