public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Putting packages up for adoption
Date: Mon, 30 Mar 2020 02:01:38 -0400	[thread overview]
Message-ID: <18e379e7828050473bc8b09fd36912b14ed1b50b.camel@cygwin.com> (raw)
In-Reply-To: <36034a3d-7045-9a49-301a-79453d35839b@gmail.com>

On Sat, 2020-03-28 at 04:33 +0100, Marco Atzeri wrote:
> Am 27.03.2020 um 21:52 schrieb Yaakov Selkowitz:
> > On Fri, 2020-03-27 at 18:52 +0100, Marco Atzeri wrote:
> > > Am 26.03.2020 um 08:19 schrieb Yaakov Selkowitz:
> > > > On Thu, 2020-03-26 at 06:54 +0100, Marco Atzeri via Cygwin-apps wrote:
> > > > > Am 20.03.2020 um 04:47 schrieb Yaakov Selkowitz:
> > > > I would suggest the following:
> > > > 
> > > > * python2-2.7.z continues to provide all '2' symlinks.
> > > > 
> > > > * python38 be updated to 3.8.2, and 3.8 be designated the next default
> > > > 'python3' version (with the '3' symlinks continued to be kept
> > > > separate), and adjust python-wheel.cygclass accordingly.
> > > > 
> > > > * Similarly, a separate package (in Fedora it's called 'python-
> > > > unversioned-command') provide unversioned symlinks, pointing to 2.7 for
> > > > now (for compatibility).
> > > > 
> > > > * Anything currently dependent on 'python' or 'python2' should either
> > > > be dropped if no longer needed, switched to 3 is possible, otherwise
> > > > rebuilt.
> > > > 
> > > > * Drop 2.7 from the "default" version set in python-wheel.cygclass, and
> > > > only build those modules that are actually needed by other things by
> > > > specifying "all".
> > > > 
> > > > * Once that's done, look at what's still depending on /usr/bin/python
> > > > ('python-unversioned-command'), and based on that decide when that can
> > > > be changed to point to python3.
> > > > 
> > > > HTH,
> > > > 
> > > > --
> > > > Yaakov
> > > > 
> > > 
> > > The plan looks fine. Thanks for it
> > > 
> > > unfortunately I see unexpected segfault on the testsuite
> > > 
> > > 0:00:03 load avg: 1.65 [ 24/404] test_argparse -- test_applesingle skipped
> > > 0:00:11 load avg: 1.58 [ 25/404] test_array
> > > 0:00:12 load avg: 1.58 [ 26/404] test_ascii_formatd
> > > make: *** [Makefile:878: test] Segmentation fault (core dumped)
> > > 
> > > for both 2.7.17 and your original 2.7.16.
> > > 
> > > as I saw other segfault on other programs recently
> > > I assume that one of compiler/binutils/cygwin has some problem.
> > > 
> > > 3.8.2 seems to stall later in the test, so it is another issue.
> > 
> > In my experience, particularly on Cygwin, the first and most common
> > cause of testsuite errors are in the tests themselves.  While
> > eventually fixing these would certainly be welcome, I wouldn't block
> > progress thereon.  How does the saying go, "don't let perfection be the
> > enemy of the good"?
> > 
> > --
> > Yaakov
> > 
> 
> usually I follow the same rules, but a bit of investigation
> will be needed just to be sure.
> 
> Do you know a simple way to go on with the test or skip one ?

See https://src.fedoraproject.org/rpms/python3/blob/master/f/python3.spec#_1051

> particular useful for 3.8.2
> 
> 6:14:06 load avg: 0.31 running: test_subprocess (6 hour 13 min), 
> test_asyncio (6 hour 11 min), test_asyncore (6 hour 10 min), test_ssl (6 
> hour 13 min)
> 6:14:36 load avg: 0.30 running: test_subprocess (6 hour 13 min), 
> test_asyncio (6 hour 12 min), test_asyncore (6 hour 11 min), test_ssl (6 
> hour 14 min)
> 6:15:06 load avg: 0.41 running: test_subprocess (6 hour 14 min), 
> test_asyncio (6 hour 12 min), test_asyncore (6 hour 11 min), test_ssl (6 
> hour 14 min)

--
Yaakov



  reply	other threads:[~2020-03-30  6:01 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20  3:47 Yaakov Selkowitz
2020-03-20  5:04 ` Marco Atzeri
2020-03-20  6:05   ` ASSI
2020-03-20 10:19     ` Corinna Vinschen
2020-03-20 10:23   ` Corinna Vinschen
2020-03-20  8:13 ` Hamish McIntyre-Bhatty
2020-03-20  8:28   ` Marco Atzeri
2020-03-20  9:29 ` Jan Nijtmans
2020-03-20 10:22   ` Corinna Vinschen
2020-03-22 22:34   ` Yaakov Selkowitz
2020-03-23 12:07     ` Jan Nijtmans
2020-03-23 15:45       ` Yaakov Selkowitz
2020-03-23 21:04         ` Jan Nijtmans
2020-03-23 23:37           ` Yaakov Selkowitz
2020-03-24 11:41             ` Jan Nijtmans
2020-03-24 13:51               ` Yaakov Selkowitz
2020-03-24 14:11                 ` Jan Nijtmans
2020-03-24 14:24                   ` Yaakov Selkowitz
2020-03-24 19:27                     ` Jan Nijtmans
2020-04-01  9:10                       ` Jan Nijtmans
2020-03-20 10:19 ` Corinna Vinschen
2020-03-20 12:11   ` Jon Turney
2020-03-24 20:19   ` Andrew Schulman
2020-04-01 20:58     ` Yaakov Selkowitz
2020-04-02  7:35       ` Corinna Vinschen
2020-07-21  0:33         ` Andrew Schulman
2020-03-20 12:09 ` Jon Turney
2020-03-21 12:47   ` Thomas Wolff
2020-03-21 14:10     ` Jon Turney
2020-03-20 12:31 ` Marco Atzeri
2020-03-20 17:32   ` Achim Gratz
2020-03-20 19:16     ` Hamish McIntyre-Bhatty
2020-03-20 19:22     ` Yaakov Selkowitz
2020-03-20 20:30     ` Marco Atzeri
2020-03-22 15:34       ` ASSI
2020-03-22 16:36         ` ASSI
2020-03-22 19:49           ` Yaakov Selkowitz
2020-03-22 20:39             ` Achim Gratz
2020-03-22 19:03   ` Achim Gratz
2020-03-23 17:14     ` ASSI
2020-03-23 23:06       ` Marco Atzeri
2020-03-20 16:17 ` Doug Henderson
2020-03-21 14:12   ` Jon Turney
2020-03-26  5:54 ` Marco Atzeri
2020-03-26  7:19   ` Yaakov Selkowitz
2020-03-27 17:52     ` Marco Atzeri
2020-03-27 20:52       ` Yaakov Selkowitz
2020-03-28  3:33         ` Marco Atzeri
2020-03-30  6:01           ` Yaakov Selkowitz [this message]
2020-03-27 17:53     ` Marco Atzeri
2020-03-27 18:32       ` Hamish McIntyre-Bhatty
2020-03-27 19:10         ` Yaakov Selkowitz
2020-03-27 20:02           ` Hamish McIntyre-Bhatty
2020-04-10 12:52     ` Python - plan & execution Marco Atzeri
2020-04-23 21:54       ` Yaakov Selkowitz
2020-04-27 14:34         ` Jon Turney
2020-05-25  4:52           ` Marco Atzeri
2020-05-25 13:43             ` Jon Turney
2020-05-25 23:45             ` Yaakov Selkowitz
2020-05-26  4:31               ` Marco Atzeri
2020-06-08 19:20                 ` Jon Turney
2020-06-08 20:02                   ` Marco Atzeri
2020-06-09 13:20                     ` Jon Turney
2020-06-09 19:16                       ` Marco Atzeri
2020-06-12 14:44                         ` Jon Turney
2020-05-25  5:02       ` Marco Atzeri
2020-07-07 18:40         ` Marco Atzeri
2020-07-09 23:52           ` airplanemath
2020-07-10  5:34             ` Marco Atzeri
2020-04-04  3:17 ` Putting packages up for adoption 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=18e379e7828050473bc8b09fd36912b14ed1b50b.camel@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --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).