From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: Moving from python2 to python3
Date: Wed, 30 Dec 2020 10:41:42 -0500 [thread overview]
Message-ID: <e204beb2-729b-645a-9aa2-d0d311ecf0b2@cornell.edu> (raw)
In-Reply-To: <87h7o3pepx.fsf@Otto.invalid>
On 12/30/2020 9:10 AM, ASSI wrote:
> Marco Atzeri via Cygwin-apps writes:
>> it seems the appveyor is not running the postinstall scripts
>
> It does run all the other ones, though… so there's something amiss with
> the logic that triggers that script.
python38-3.8.3-1 is missing its postinstall script. All I see is a
cygport-generated /etc/postinstall/python38.sh, packaged with idle38-3.8.3-1.
Ken
next prev parent reply other threads:[~2020-12-30 15:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 18:11 Ken Brown
2020-12-04 21:04 ` Marco Atzeri
2020-12-29 10:49 ` Marco Atzeri
2020-12-29 12:04 ` Achim Gratz
2020-12-29 13:13 ` Marco Atzeri
2020-12-29 16:42 ` Achim Gratz
2020-12-29 17:02 ` Marco Atzeri
2020-12-29 20:27 ` Marco Atzeri
2020-12-29 20:57 ` Achim Gratz
2020-12-29 21:23 ` Marco Atzeri
2020-12-30 7:21 ` Achim Gratz
2020-12-30 11:14 ` Marco Atzeri
2020-12-30 14:10 ` ASSI
2020-12-30 15:41 ` Ken Brown [this message]
2020-12-30 18:13 ` Marco Atzeri
2020-12-29 15:04 ` Ken Brown
2020-12-29 15:46 ` Marco Atzeri
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=e204beb2-729b-645a-9aa2-d0d311ecf0b2@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@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).