From: Jon Turney <jon.turney@dronecode.org.uk>
To: "Schulman, Andrew" <schulman.andrew@epa.gov>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: New packages: unison2.51+4.04.2, unison2.51+4.10.0
Date: Wed, 22 Dec 2021 19:30:53 +0000 [thread overview]
Message-ID: <993edbdf-84e9-a68d-e843-98337a84280d@dronecode.org.uk> (raw)
In-Reply-To: <pps6sgpoh8n7q3bjhj2gccrk4003j9tib8@4ax.com>
On 22/12/2021 18:51, Andrew Schulman via Cygwin-apps wrote:
>> On 22.12.2021 17:21, Andrew Schulman via Cygwin-apps wrote:
>>> Please add me as maintainer of two new unison packages:
>>>
>>> unison2.51+4.04.2
>>> unison2.51+4.10.0
>>>
>>> These will obsolete the current unison2.51 package.
>>>
>>> Thanks, Andrew
>>>
>>
>> added.
>
> 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:
Yeah, this is an unfortunate side-effect of the way upload authorization
works at the moment.
> ERROR: package 'unison2.51' is at paths unison2.51 and
> unison2.51+4.10.0/unison2.51
>
> Can you help with that?
I've moved the existing unison2.51 packages to
unison2.51+4.10.0/unison2.51, which should allow this upload to succeed.
Please try again, and apologies for the inconvenience.
next prev parent reply other threads:[~2021-12-22 19:31 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 [this message]
2021-12-22 19:37 ` Marco Atzeri
2021-12-22 19:50 ` Andrew Schulman
2021-12-22 20:21 ` 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=993edbdf-84e9-a68d-e843-98337a84280d@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).