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
Cc: Federico Kircheis <federico.kircheis@gmail.com>
Subject: Re: [ITP] neomutt
Date: Fri, 02 Feb 2018 19:24:00 -0000	[thread overview]
Message-ID: <8761db24-fd08-d345-ffda-b14398b19f7e@dronecode.org.uk> (raw)
In-Reply-To: <fedd8536-09b6-eba0-4967-47c6de625b42@gmail.com>

On 31/01/2018 19:21, Federico Kircheis wrote:
> On 01/31/2018 06:55 PM, Jon Turney wrote:
>> On 30/01/2018 05:56, Federico Kircheis wrote:
>>> On 01/28/2018 03:43 PM, Jon Turney wrote:
>>>> On 28/01/2018 11:38, Federico Kircheis wrote:
>>>>> Name: Federico Kircheis
>>>>> Package: neomutt
>>>>
>>>> Done
>>>
>>> Uploaded.
>>
>> Please upload a x86 package as well.
> 
> I'm sorry, I uploaded it, too.
> 
> I thought that the previous upload would have been valid both for x64 
> and x86.
> 
> I was unsure how to proceed, so I've downloaded a x86 version of cygwin, 
> copied the cygport file in a separate directory, and so on.

This is probably the most straightforward way.

> Is there a way to update the package for x64 and x86 at once?

You don't need to do this, since the process which receives the uploads 
can tolerate x86 and x86 arriving separately.

> Without using ftp directly of course.

If you really want to ensure they are processed at once, I guess you'd 
have to use 'cygport stage' to upload the files for each arch, then 
manually upload !ready files (as described in [1])

But, I can't think of any reasons to bother doing that for a single package.

[1] https://cygwin.com/package-upload.html

      reply	other threads:[~2018-02-02 19:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-20  7:43 Federico Kircheis
2018-01-20 18:22 ` Marco Atzeri
2018-01-20 19:52   ` Federico Kircheis
2018-01-21 17:51     ` Jon Turney
2018-01-21 20:18       ` Federico Kircheis
2018-01-24 18:07         ` Federico Kircheis
2018-01-26 17:01           ` Jon Turney
2018-01-28 11:38             ` Federico Kircheis
2018-01-28 14:43               ` Jon Turney
2018-01-30  5:56                 ` Federico Kircheis
2018-01-31 17:55                   ` Jon Turney
2018-01-31 19:21                     ` Federico Kircheis
2018-02-02 19:24                       ` 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=8761db24-fd08-d345-ffda-b14398b19f7e@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=federico.kircheis@gmail.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).