From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: two questions about new upload method
Date: Sat, 30 Nov 2013 19:40:00 -0000 [thread overview]
Message-ID: <20131130194028.GA7778@ednor.casa.cgf.cx> (raw)
In-Reply-To: <rt8k99tnu6fri16isqtsf94raiel67e362@4ax.com>
On Sat, Nov 30, 2013 at 12:48:14PM -0500, Andrew Schulman wrote:
>> On 11/30/2013 3:47 AM, Andrew Schulman wrote:
>> >> On Fri, Nov 29, 2013 at 10:06:50PM -0500, Christopher Faylor wrote:
>> >>> On Fri, Nov 29, 2013 at 01:13:30PM -0500, Christopher Faylor wrote:
>> >>>> I added you as the owner for "unison" and "unison2.45".
>> >>>
>> >>> Which didn't do anything. I'm investigating why now.
>> >>
>> >> It was because the !ready files disappeared after the previous
>> >> run. I put one in unison/unison2.45 and the files were moved.
>> >
>> > Thanks. The packages are out now.
>>
>> I see unison2.45 but not the others.
>
>Hm, you're right. Not sure why, since I am listed as maintainer of
>unison2.27, unison2.32, unison2.40 at http://cygwin.com/cygwin-pkg-maint.
>And they're all listed in !packages in my upload directory.
>
>I just recreated !ready again. In my upload directory I see that
>x86_64/release/unison/unison2.45 has been cleared out, but the uploaded
>files for unison2.27, unison2.32, and unison2.40 are still waiting there.
I just put a '!ready' file in the unison directory and everything was
transferred.
You need at least one !ready file per architecture so if you put a !ready
at your top level it won't work as expected.
From: https://sourceware.org/cygwin-apps/package-upload.html
Note: !ready files need to be created at least once for each
architecture that is uploaded, i.e., in each of the x86 and x86_64
directories or in the package directories themselves.
upset will periodically scan the upload directories for packages that
are ready, and, if there are no errors, move the packages into the real
release area. New directories in the release area will be created as
needed. If there are errors then setup.ini will not be updated and the
release area will remain pristine.
Note: The upload area is only for new files intended for the Cygwin
release. There is no reason to put older files in the upload
directories since they already exist in the main release.
cgf
next prev parent reply other threads:[~2013-11-30 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 17:27 Andrew Schulman
2013-11-29 18:13 ` Christopher Faylor
2013-11-30 3:07 ` Christopher Faylor
2013-11-30 4:46 ` Christopher Faylor
2013-11-30 8:48 ` Andrew Schulman
2013-11-30 16:18 ` Ken Brown
2013-11-30 17:48 ` Andrew Schulman
2013-11-30 19:40 ` Christopher Faylor [this message]
2013-12-01 9:28 ` Andrew Schulman
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=20131130194028.GA7778@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--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).