calm now runs on-demand

calm now runs on-demand

[Jon Turney]

I recently deployed an update to calm which should causes it to run 
on-demand after a maintainer SFTP upload.

Hopefully this reduces the inconvenience of having to wait till the next 
scheduled run, after an upload is made which fails due to some easily 
correctable problem.

calm continues to also run on a schedule at :10 and :40 past the hour, 
so it will still note changes which have been made directly on sourceware.

If you have shell access on sourceware, and make such changes, you can 
force calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'.

Given that, it probably makes sense to consider reducing the frequency 
of scheduled runs.

Re: calm now runs on-demand

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 913 bytes --]

On Apr 17 12:34, Jon Turney wrote:
> 
> I recently deployed an update to calm which should causes it to run
> on-demand after a maintainer SFTP upload.
> 
> Hopefully this reduces the inconvenience of having to wait till the next
> scheduled run, after an upload is made which fails due to some easily
> correctable problem.
> 
> calm continues to also run on a schedule at :10 and :40 past the hour, so it
> will still note changes which have been made directly on sourceware.
> 
> If you have shell access on sourceware, and make such changes, you can force
> calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'.
> 
> Given that, it probably makes sense to consider reducing the frequency of
> scheduled runs.

👍


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: calm now runs on-demand

[Andrew Schulman]

> On Apr 17 12:34, Jon Turney wrote:
> > 
> > I recently deployed an update to calm which should causes it to run
> > on-demand after a maintainer SFTP upload.
> > 
> > Hopefully this reduces the inconvenience of having to wait till the next
> > scheduled run, after an upload is made which fails due to some easily
> > correctable problem.
> > 
> > calm continues to also run on a schedule at :10 and :40 past the hour, so it
> > will still note changes which have been made directly on sourceware.
> > 
> > If you have shell access on sourceware, and make such changes, you can force
> > calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'.
> > 
> > Given that, it probably makes sense to consider reducing the frequency of
> > scheduled runs.

I have upload access, but AFAIK not shell access. I think most maintainers
don't, unless that's changed.

Re: calm now runs on-demand

[Jon Turney]

On 01/07/2017 12:31, Andrew Schulman wrote:
>> On Apr 17 12:34, Jon Turney wrote:
>>>
>>> I recently deployed an update to calm which should causes it to run
>>> on-demand after a maintainer SFTP upload.
>>>
>>> Hopefully this reduces the inconvenience of having to wait till the next
>>> scheduled run, after an upload is made which fails due to some easily
>>> correctable problem.
>>>
>>> calm continues to also run on a schedule at :10 and :40 past the hour, so it
>>> will still note changes which have been made directly on sourceware.
>>>
>>> If you have shell access on sourceware, and make such changes, you can force
>>> calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'.
>>>
>>> Given that, it probably makes sense to consider reducing the frequency of
>>> scheduled runs.
> 
> I have upload access, but AFAIK not shell access. I think most maintainers
> don't, unless that's changed.

Correct.  But unless you have shell access to make changes by directly 
moving files around on sourceware, you don't need shell access to run calm.

Currently, calm runs (i) if a !ready file exists in your upload area 
when your sftp session closes, and (ii) at 00:10 UTC and every 4 hours 
thereafter.

Re: calm now runs on-demand

[Andrew Schulman]

> On 01/07/2017 12:31, Andrew Schulman wrote:
> >> On Apr 17 12:34, Jon Turney wrote:
> >>>
> >>> I recently deployed an update to calm which should causes it to run
> >>> on-demand after a maintainer SFTP upload.
> >>>
> >>> Hopefully this reduces the inconvenience of having to wait till the next
> >>> scheduled run, after an upload is made which fails due to some easily
> >>> correctable problem.
> >>>
> >>> calm continues to also run on a schedule at :10 and :40 past the hour, so it
> >>> will still note changes which have been made directly on sourceware.
> >>>
> >>> If you have shell access on sourceware, and make such changes, you can force
> >>> calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'.
> >>>
> >>> Given that, it probably makes sense to consider reducing the frequency of
> >>> scheduled runs.
> > 
> > I have upload access, but AFAIK not shell access. I think most maintainers
> > don't, unless that's changed.
> 
> Correct.  But unless you have shell access to make changes by directly 
> moving files around on sourceware, you don't need shell access to run calm.
> 
> Currently, calm runs (i) if a !ready file exists in your upload area 
> when your sftp session closes, and (ii) at 00:10 UTC and every 4 hours 
> thereafter.

Cool, thank you.
Andrew

Re: calm now runs on-demand

[Marco Atzeri]

On 17/04/2017 13:34, Jon Turney wrote:
>
>
> calm continues to also run on a schedule at :10 and :40 past the hour,
> so it will still note changes which have been made directly on sourceware.
>
> If you have shell access on sourceware, and make such changes, you can
> force calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'.

Jon,
I have shell access but I do not find calm anywhere.
I assume "~cygwin-admin" is more restricted than shell access.

As I did change to the relarea for gcc test, how to force the
update of setup.ini's ?

Regards
Marco

Re: calm now runs on-demand

[Jon Turney]

On 01/07/2017 06:18, Marco Atzeri wrote:
> On 17/04/2017 13:34, Jon Turney wrote:
>>
>> If you have shell access on sourceware, and make such changes, you can
>> force calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'.
> 
> Jon,
> I have shell access but I do not find calm anywhere.
> I assume "~cygwin-admin" is more restricted than shell access.
> 
> As I did change to the relarea for gcc test, how to force the
> update of setup.ini's ?

I think I have fixed the permissions, so this should work for you now.

Thanks for pointing out this problem.

Re: calm now runs on-demand

[Marco Atzeri]

On 01/07/2017 15:54, Jon Turney wrote:
> On 01/07/2017 06:18, Marco Atzeri wrote:
>> On 17/04/2017 13:34, Jon Turney wrote:
>>>
>>> If you have shell access on sourceware, and make such changes, you can
>>> force calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'.
>>
>> Jon,
>> I have shell access but I do not find calm anywhere.
>> I assume "~cygwin-admin" is more restricted than shell access.
>>
>> As I did change to the relarea for gcc test, how to force the
>> update of setup.ini's ?
>
> I think I have fixed the permissions, so this should work for you now.
>
> Thanks for pointing out this problem.

May be I misunderstood how I should use it

matzeri@sourceware ~
$  /home/cygwin/bin/calm scan-relarea
/home/cygwin/bin/calm: line 13: kill: (14958) - Operation not permitted

$  /home/cygwin/bin/calm scan-uploads
/home/cygwin/bin/calm: line 10: kill: (14958) - Operation not permitted

Re: calm now runs on-demand

[Jon Turney]

On 01/07/2017 15:14, Marco Atzeri wrote:
> On 01/07/2017 15:54, Jon Turney wrote:
>> On 01/07/2017 06:18, Marco Atzeri wrote:
>>> On 17/04/2017 13:34, Jon Turney wrote:
>>>>
>>>> If you have shell access on sourceware, and make such changes, you can
>>>> force calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'.
>>>
>>> Jon,
>>> I have shell access but I do not find calm anywhere.
>>> I assume "~cygwin-admin" is more restricted than shell access.
>>>
>>> As I did change to the relarea for gcc test, how to force the
>>> update of setup.ini's ?
>>
>> I think I have fixed the permissions, so this should work for you now.
>>
>> Thanks for pointing out this problem.
> 
> May be I misunderstood how I should use it
> 
> matzeri@sourceware ~
> $  /home/cygwin/bin/calm scan-relarea
> /home/cygwin/bin/calm: line 13: kill: (14958) - Operation not permitted

No, that's me being dumb.  I guess I need to think some more about how 
to make this work for other users...

Re: calm now runs on-demand

[Jon Turney]

On 01/07/2017 15:22, Jon Turney wrote:
> On 01/07/2017 15:14, Marco Atzeri wrote:
>> On 01/07/2017 15:54, Jon Turney wrote:
>>> On 01/07/2017 06:18, Marco Atzeri wrote:
>>>> On 17/04/2017 13:34, Jon Turney wrote:
>>>>>
>>>>> If you have shell access on sourceware, and make such changes, you can
>>>>> force calm to run with '~cygwin-admin/bin/calm 
>>>>> scan-(uploads|relarea)'.

calm now (finally) detects when changes have been made in the relarea 
via inotify, so this manual step is no longer required.

So, if you have shell access, and you make changes directly in the 
relarea, calm should now notice, reread it, and update the setup.ini 
package manifest automatically, without you needing to explicitly 
request that (or wait until the next scheduled rescan, if you can't 
request it due to the permission problem identified below...)

>>>> Jon,
>>>> I have shell access but I do not find calm anywhere.
>>>> I assume "~cygwin-admin" is more restricted than shell access.
>>>>
>>>> As I did change to the relarea for gcc test, how to force the
>>>> update of setup.ini's ?
>>>
>>> I think I have fixed the permissions, so this should work for you now.
>>>
>>> Thanks for pointing out this problem.
>>
>> May be I misunderstood how I should use it
>>
>> matzeri@sourceware ~
>> $  /home/cygwin/bin/calm scan-relarea
>> /home/cygwin/bin/calm: line 13: kill: (14958) - Operation not permitted
> 
> No, that's me being dumb.  I guess I need to think some more about how 
> to make this work for other users...

Re: calm now runs on-demand

[Achim Gratz]

Marco Atzeri writes:
> As I did change to the relarea for gcc test, how to force the
> update of setup.ini's ?

I guess you can just open and close an sftp session, maybe providing new
!ready cookies.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

Re: calm now runs on-demand

[Achim Gratz]

Achim Gratz writes:
> Marco Atzeri writes:
>> As I did change to the relarea for gcc test, how to force the
>> update of setup.ini's ?
>
> I guess you can just open and close an sftp session, maybe providing new
> !ready cookies.

I tried that, but got:

ERROR: not processing uploads or writing setup.ini
SUMMARY: 1 ERROR(s)

Anyway, it looks like Jon is on now, so I assume he'll gets things off
the ground again.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: calm now runs on-demand

[Jon Turney]

On 01/07/2017 15:03, Achim Gratz wrote:
> Achim Gratz writes:
>> Marco Atzeri writes:
>>> As I did change to the relarea for gcc test, how to force the
>>> update of setup.ini's ?
>>
>> I guess you can just open and close an sftp session, maybe providing new
>> !ready cookies.

No, this is not enough.  calm doesn't re-read the release area for every 
maintainer upload, as this is relatively expensive and usually pointless 
(the contents usually haven't changed)

> I tried that, but got:
> 
> ERROR: not processing uploads or writing setup.ini
> SUMMARY: 1 ERROR(s)

Heh, not a very helpful error message :(

> Anyway, it looks like Jon is on now, so I assume he'll gets things off
> the ground again.

A setup.ini with gcc test:6.3.0-2 has been generated now and should be 
mirroring out.