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>,
	"Schulman, Andrew" <schulman.andrew@epa.gov>
Subject: Re: New packages: unison2.51+4.04.2, unison2.51+4.10.0
Date: Wed, 22 Dec 2021 20:21:03 +0000	[thread overview]
Message-ID: <2bd7d39d-193e-669c-da4c-74f0813a80a1@dronecode.org.uk> (raw)
In-Reply-To: <rpv6sgtp5pfasja6jr927rfk83rme2rbni@4ax.com>

On 22/12/2021 19:50, Andrew Schulman via Cygwin-apps wrote:
>>> Since I marked unison2.51+4.04.2 as obsoletes: unison2.51, it seems that
>>> unison2.51 now needs to be removed as a separate package? calm says:
>>>
>>> ERROR: package 'unison2.51' is at paths unison2.51 and
>>> unison2.51+4.10.0/unison2.51
>>
>> this says that unison2.51+4.10.0 obsolets unison2.51
>> not unison2.51+4.04.
>>
>> Can you confirm ?
> 
> Sorry for the confusion. I posted the wrong error message.
> 
> Since unison2.51 can only appear in one place, it should be obsoleted by
> unison2.51+4.04.2, which uses the same OCaml version.

Yes, note that only one of unison2.51+4.04.2 and unison2.51+4.04.2 can 
obsolete unison2.51.

> So Jon, can you please move unison2.51 under unison2.51+4.04.2 ?

Done.

      reply	other threads:[~2021-12-22 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 16:21 Andrew Schulman
2021-12-22 16:40 ` Marco Atzeri
2021-12-22 17:30   ` Andrew Schulman
2021-12-22 18:51   ` Andrew Schulman
2021-12-22 19:30     ` Jon Turney
2021-12-22 19:37     ` Marco Atzeri
2021-12-22 19:50       ` Andrew Schulman
2021-12-22 20:21         ` 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=2bd7d39d-193e-669c-da4c-74f0813a80a1@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=schulman.andrew@epa.gov \
    /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).