This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: A couple of uploads are missing "!ready" files
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 23 Oct 2013 09:41:57 -0400
- Subject: Re: A couple of uploads are missing "!ready" files
- Authentication-results: sourceware.org; auth=none
- References: <20131023035140 dot GA4945 at ednor dot casa dot cgf dot cx> <CAGHJv4eYZnOy3jx1o7sdfHtzipQCSMGT8nUpoJADGGEjbXLV0w at mail dot gmail dot com>
- Reply-to: cygwin-apps at cygwin dot com
On Wed, Oct 23, 2013 at 07:23:02AM -0400, Chris Sutcliffe wrote:
>On 22 October 2013 23:51, Christopher Faylor wrote:
>> I notice that David Stacey and Chris Sutcliffe have .tar.* files in
>> their directories but no accompanying !ready files in the directories or
>> in the directories above them. Without those the packages won't be
>> moved. If you create a !ready in an x86_64 directory it won't apply to
>> packages in x86 directories. This only applies to packages in the same
>> directory or below.
>
>My understanding was that if I placed a "!ready" file in the root
>(i.e. the directory above x86 and x86_64) it would grab the files for
>both architectures. Since I had cppcheck ready for both architectures
>I thought this was the correct placement of the file.
>
>Please let me know if I have misunderstood something.
Your understanding was correct but I didn't think through how this is
implemented and gave incorrect instructions. Since upset runs once for
each architecture, it deletes the !ready on the first architecture and
then never notices it for the second.
So, for the foreseeable future, you need two !ready files.
Sorry for the miscommunication.
cgf