public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: calm and cygport not in sync
Date: Tue, 1 Feb 2022 15:03:40 +0000	[thread overview]
Message-ID: <eaf12815-fd83-58c5-618a-6d9957658a6f@dronecode.org.uk> (raw)
In-Reply-To: <770413e1-8fad-0af5-4327-5403614cab36@gmail.com>

On 24/01/2022 04:42, Marco Atzeri wrote:
> It seems calm is now rejecting what cygport is still producing
> 
[..]
> 
> ERROR: package 'python36-sh' version '1.14.2-1' obsoletes: 'python3-sh', 
> but nothing satisfies that
> ERROR: package 'python36-straight.plugin' version '1.5.0-1' obsoletes: 
> 'python3-straight.plugin', but nothing satisfies that
> ERROR: error while validating merged x86 packages for Marco Atzeri
> ERROR: package 'python36-sh' version '1.14.2-1' obsoletes: 'python3-sh', 
> but nothing satisfies that
> ERROR: package 'python36-straight.plugin' version '1.5.0-1' obsoletes: 
> 'python3-straight.plugin', but nothing satisfies that
> ERROR: error while validating merged x86_64 packages for Marco Atzeri
> SUMMARY: 6 ERROR(s)
> -------------------------------------------
> 
> temporary solved by hand
> 

Yes, there's a disconnect here.

cygport assumes that if we are making a 'python36-' package, a 
'python3-' version of the package exists which it should obsolete.

For a new package that assumption isn't correct, which calm considers an 
error.

I'll try to adjust calm so this isn't so annoying.

But I'm not sure this is how 'python3-' packages should be handled, 
which probably needs a bit of discussion.

I think I'd like it it if 'python3-' names were retained (so then 'setup 
-q -P python-foo' gets you a working 'python3 -c 'import foo''), but not 
sure how those names should work (as a forwarding package, as a 
provides?), or how those names should work in setup (e.g. it probably 
doesn't allow obsoletes/provides names to be searched for or specified 
with -P at the moment).

      reply	other threads:[~2022-02-01 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164297570975.250866.6606456581812688116@server2.sourceware.org>
2022-01-24  4:42 ` Marco Atzeri
2022-02-01 15:03   ` Jon Turney [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=eaf12815-fd83-58c5-618a-6d9957658a6f@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).