public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Apparent bug in either (1) Cygwin default Package-list or (2) Package "bzr" dependency-list
Date: Fri, 19 Jun 2020 11:39:36 +0200	[thread overview]
Message-ID: <CAB8Xom_Wob7BECz6ZGtn_0_sk5rwTxnLFCC0BBxxKtRB21+wKg@mail.gmail.com> (raw)
In-Reply-To: <45a8baf1-f636-7c03-ec1f-7c72ee73c56d@SystematicSw.ab.ca>

On Fri, Jun 19, 2020 at 8:56 AM Brian Inglis wrote:
>
> On 2020-06-18 21:33, My Name via Cygwin wrote:
> > I found an apparent dependency problem in Cygwin, and I'm not enough of a
> > Cygwin expert to know whether the bug is in Cygwin or Bazaar (Package
> > "bzr"); but if I had to guess, I'd guess it's in Cygwin, and I've already
> > reported the issue to the Bazaar forum.
> >
> > In summary, after I installed Cygwin and Cygwin-Package "bzr", bzr failed
> > as it attempted to execute "python27". A detailed description of the issue,
> > including input and output from several tests I ran, and including the
> > solution posted by someone else (solution = install Cygwin-Package
> > "python27") is here, https://answers.launchpad.net/bzr/+question/691381,
> > and it's rather concise so I'll end here and refer you to that thread.
> >
> > Per the directions here, https://cygwin.com/problems.html, I'm
> > email-attaching the output from "cygcheck -s -v -r".
>
> Looks like cygport, calm, and setup disagree about install dependencies; from
> setup.ini:
>
> bzr
> requires: python
> depends2: python
>
> python
> requires: python2
> depends2:
>
> python2
> requires: python27
> depends2:
>
> so although python requires python2, and python2 requires python27, the (newer)
> depends2 entries are not the same and are empty, so setup ignores requires and
> does not install the dependency.
>
> In these cases, either depends2 should be the same as requires, or depends2
> should be omitted, and setup should install requires.
>

it seems a glitch of the last packing of python2.
I will review the dependency and re upload them in the weeked

Regards
Marco

  reply	other threads:[~2020-06-19  9:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19  3:33 My Name
2020-06-19  6:55 ` Brian Inglis
2020-06-19  9:39   ` marco atzeri [this message]
2020-06-20 14:41   ` Jon Turney
2020-06-20 14:44     ` Marco Atzeri
2020-06-21 16:15     ` Brian Inglis
2020-06-21 18:04       ` My Name
2020-06-22  2:21         ` Allen Hewes
2020-06-22  2:45           ` My Name
     [not found]             ` <MN2PR17MB39993A62062F020FE99CA0B6B8970@MN2PR17MB3999.namprd17.prod.outlook.com>
     [not found]               ` <CAGUd5DW8vwBB3QtOLaTB1FhPVGB9ugx+xxo=CxCWFVB3hWFsMw@mail.gmail.com>
2020-06-22  5:26                 ` Allen Hewes
2020-06-22  5:20           ` Marco Atzeri
2020-06-22  5:49             ` Allen Hewes
     [not found]               ` <CAGUd5DXo=Wu1jx64OkQbjHtvC_5gcaUJF6_mnL0YH=Xmhd_x6g@mail.gmail.com>
2020-06-22  6:54                 ` Allen Hewes
2020-06-22  7:02                 ` Allen Hewes
2020-06-24 21:34       ` Jon Turney
2020-06-25 11:53         ` Brian Inglis
2020-06-25 21:48           ` Jon Turney

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=CAB8Xom_Wob7BECz6ZGtn_0_sk5rwTxnLFCC0BBxxKtRB21+wKg@mail.gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).