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
> 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
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|r
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
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
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 i
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 set
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 ada
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 "~c
> 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 du
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/
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 easi
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 t
13 matches
Mail list logo
