two questions about new upload method

two questions about new upload method

[Andrew Schulman]

(1) Is there something I should sould be doing to tell upset which package
versions are old and should be purged?  I uploaded lftp, and the new
version was added to the archive, but the old one (4.4.7-1) is still there.
Do I need to add curr: and prev: lines to setup.hint?  Or will upset figure
that out and remove the old versions at some point?

(2) I uploaded the unison packages for x86_64 in subdirectories of
x86_64/release/unison:

x86_64/release/unison/unison2.27
x86_64/release/unison/unison2.32
x86_64/release/unison/unison2.40
x86_64/release/unison/unison2.45

because that's how they're organized in x86/release.  Will upset pick them
up when they're organized that way?  I only ask because it's been about 18
hours and they haven't appeared in any of the mirrors yet, although upset
seems to be running every hour.

Thanks,
Andrew.

Re: two questions about new upload method

[Christopher Faylor]

On Fri, Nov 29, 2013 at 12:27:17PM -0500, Andrew Schulman wrote:
>(1) Is there something I should sould be doing to tell upset which package
>versions are old and should be purged?

There was a long thread about how to delete packages in cygwin-apps.

http://cygwin.com/ml/cygwin-apps/2013-10/threads.html#00184

It also went into November.

>I uploaded lftp, and the new
>version was added to the archive, but the old one (4.4.7-1) is still there.
>Do I need to add curr: and prev: lines to setup.hint?  Or will upset figure
>that out and remove the old versions at some point?
>
>(2) I uploaded the unison packages for x86_64 in subdirectories of
>x86_64/release/unison:
>
>x86_64/release/unison/unison2.27
>x86_64/release/unison/unison2.32
>x86_64/release/unison/unison2.40
>x86_64/release/unison/unison2.45
>
>because that's how they're organized in x86/release.  Will upset pick them
>up when they're organized that way?  I only ask because it's been about 18
>hours and they haven't appeared in any of the mirrors yet, although upset
>seems to be running every hour.

Guess I need to add a FAQ.

Q) Why aren't my files being transferred to the release area?  I've waited
several days and don't see any movement.

A) The package updater runs every 10 minutes so, if you don't see any movement
in, e.g., 20 minutes, then your package is not going to be updated.

The main reason that this could happen is if you uploaded a package that
you are not actually responsible for.  The updater only knows what you
are responsible for based on http://cygwin.com/cygwin-pkg-maint so if
you aren't listed as an owner there your packages won't be updated.

I added you as the owner for "unison" and "unison2.45".

cgf

Re: two questions about new upload method

[Christopher Faylor]

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.

cgf

Re: two questions about new upload method

[Christopher Faylor]

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.

cgf

Re: two questions about new upload method

[Andrew Schulman]

> 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.
Andrew

Re: two questions about new upload method

[Ken Brown]

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.

Ken

Re: two questions about new upload method

[Andrew Schulman]

> 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.

Re: two questions about new upload method

[Christopher Faylor]

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

Re: two questions about new upload method

[Andrew Schulman]

> 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.

Oh - thanks.
Andrew