On 18/02/2023 17:43, Ken Brown via Cygwin-apps wrote:
On 2/18/2023 11:21 AM, Jon Turney via Cygwin-apps wrote:
You can now interact with your build jobs in some ways which require
authentication using ...
Thanks!
Currently, available sub-commands are:
cancel (request termination of an
On 2/18/2023 11:21 AM, Jon Turney via Cygwin-apps wrote:
On 05/07/2022 14:12, Jon Turney wrote:
On 22/06/2021 20:52, Jon Turney wrote:
On 09/05/2021 15:39, Jon Turney wrote:
On 23/08/2020 22:01, Jon Turney wrote:
On 27/05/2020 23:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
On 05/07/2022 14:12, Jon Turney wrote:
On 22/06/2021 20:52, Jon Turney wrote:
On 09/05/2021 15:39, Jon Turney wrote:
On 23/08/2020 22:01, Jon Turney wrote:
On 27/05/2020 23:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for
On 22/06/2021 20:52, Jon Turney wrote:
On 09/05/2021 15:39, Jon Turney wrote:
On 23/08/2020 22:01, Jon Turney wrote:
On 27/05/2020 23:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp
package upload, package maintainers
On 2021-06-22 13:52, Jon Turney wrote:
On 09/05/2021 15:39, Jon Turney wrote:
On 23/08/2020 22:01, Jon Turney wrote:
On 27/05/2020 23:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp
package upload, package maintainers
On 09/05/2021 15:39, Jon Turney wrote:
On 23/08/2020 22:01, Jon Turney wrote:
On 27/05/2020 23:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package
upload, package maintainers can now also push to git repositories,
On 23/08/2020 22:01, Jon Turney wrote:
On 27/05/2020 23:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package
upload, package maintainers can now also push to git repositories,
like so:
Package maintainers may have
Brian Inglis writes:
> Could anyone please check and advise if the attached .git/config will
> allow me to push to the playground repo and later branch for testing,
> or demo the appropriate .git/config entries or git config commands to
> do so properly?
I usually define my own repo schemes in
On 2020-11-16 15:16, Jon Turney wrote:
On 16/11/2020 21:54, Brian Inglis wrote:
On 2020-05-27 16:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package upload,
package maintainers can now also push to git repositories,
On 16/11/2020 21:54, Brian Inglis wrote:
On 2020-05-27 16:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package
upload, package maintainers can now also push to git repositories,
like so:
Package maintainers may
On 2020-05-27 16:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package upload,
package maintainers can now also push to git repositories, like so:
Package maintainers may have noticed that the output from pushing to
On 30/08/2020 16:46, Jon Turney wrote:
On 30/08/2020 16:22, Ken Brown wrote:
On 8/30/2020 11:00 AM, Jon Turney wrote:
On 26/08/2020 23:00, Ken Brown via Cygwin-apps wrote:
On 8/23/2020 5:01 PM, Jon Turney wrote:
I now have built an (opt-in) system which fetches the packages
built by this
On 04/10/2020 11:26, Achim Gratz wrote:
ASSI writes:
SCALLYWAG="notest"
It seems that if I write something like
SCALLYWAG="notest" # a comment
then the line actually gets ignored due to a somewhat restrictive regex:
match = re.search(r'^\s*SCALLYWAG=\s*"?(.*?)"?$', content, re.MULTILINE)
ASSI writes:
> SCALLYWAG="notest"
It seems that if I write something like
SCALLYWAG="notest" # a comment
then the line actually gets ignored due to a somewhat restrictive regex:
match = re.search(r'^\s*SCALLYWAG=\s*"?(.*?)"?$', content, re.MULTILINE)
Something like this might work better:
On 30/08/2020 17:44, ASSI wrote:
Jon Turney writes:
Only pushes to master are considered. You can opt-out by adding
'SCALLYWAG=nodeploy' to the cygport.
If additionally we'd not want the package to get tested, would we do
SCALLYWAG="notest nodeploy"
or
SCALLYWAG="notest"
SCALLYWAG+="
On 30/08/2020 18:25, Ken Brown via Cygwin-apps wrote:
On 8/30/2020 11:46 AM, Jon Turney wrote:
On 30/08/2020 16:22, Ken Brown wrote:
OK, I've got a test release of ghostscript ready to go. I've already
tested it on the playground branch, so I know it builds. If I put
'SCALLYWAG=deploy' in
On 8/30/2020 11:46 AM, Jon Turney wrote:
On 30/08/2020 16:22, Ken Brown wrote:
On 8/30/2020 11:00 AM, Jon Turney wrote:
On 26/08/2020 23:00, Ken Brown via Cygwin-apps wrote:
On 8/23/2020 5:01 PM, Jon Turney wrote:
I now have built an (opt-in) system which fetches the packages built by
this
Jon Turney writes:
> Only pushes to master are considered. You can opt-out by adding
> 'SCALLYWAG=nodeploy' to the cygport.
If additionally we'd not want the package to get tested, would we do
SCALLYWAG="notest nodeploy"
or
SCALLYWAG="notest"
SCALLYWAG+=" nodeploy"
is supposed to work, then?
On 30/08/2020 16:22, Ken Brown wrote:
On 8/30/2020 11:00 AM, Jon Turney wrote:
On 26/08/2020 23:00, Ken Brown via Cygwin-apps wrote:
On 8/23/2020 5:01 PM, Jon Turney wrote:
I now have built an (opt-in) system which fetches the packages built
by this into your upload area and triggers calm
On 8/30/2020 11:00 AM, Jon Turney wrote:
On 26/08/2020 23:00, Ken Brown via Cygwin-apps wrote:
On 8/23/2020 5:01 PM, Jon Turney wrote:
I now have built an (opt-in) system which fetches the packages built by this
into your upload area and triggers calm to process them, which I'm looking
for
On 26/08/2020 23:00, Ken Brown via Cygwin-apps wrote:
On 8/23/2020 5:01 PM, Jon Turney wrote:
I now have built an (opt-in) system which fetches the packages built
by this into your upload area and triggers calm to process them, which
I'm looking for a volunteer to test.
I'd be willing to
On 8/23/2020 5:01 PM, Jon Turney wrote:
On 27/05/2020 23:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package upload,
package maintainers can now also push to git repositories, like so:
Package maintainers may have
On 27/05/2020 23:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package
upload, package maintainers can now also push to git repositories,
like so:
Package maintainers may have noticed that the output from pushing to
On 07/08/2020 23:05, Ken Brown via Cygwin-apps wrote:
On 8/7/2020 3:42 PM, Achim Gratz wrote:
Jon Turney writes:
One problem I have noticed is that some packages have test suites
(which are getting run via 'cygport test' invoking src_test()) which:
- require lots of extra dependencies to run,
Ken Brown via Cygwin-apps writes:
>>> - take an inordinate amount of time to run (exceeding the resource limits)
>>
>> That is a problem that comes with CI I think and we didn't really have
>> had to consider so far. I have a few packages that I don't run tests on
>> by default because the test
On 8/7/2020 3:42 PM, Achim Gratz wrote:
Jon Turney writes:
One problem I have noticed is that some packages have test suites
(which are getting run via 'cygport test' invoking src_test()) which:
- require lots of extra dependencies to run, or
I currently subsume these in BUILD_REQUIRES as
Jon Turney writes:
> One problem I have noticed is that some packages have test suites
> (which are getting run via 'cygport test' invoking src_test()) which:
>
> - require lots of extra dependencies to run, or
I currently subsume these in BUILD_REQUIRES as they are indeed required
for a
On 8/6/2020 4:20 PM, Jon Turney wrote:
On 27/05/2020 23:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package upload,
package maintainers can now also push to git repositories, like so:
Package maintainers may have
On 27/05/2020 23:27, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package
upload, package maintainers can now also push to git repositories,
like so:
Package maintainers may have noticed that the output from pushing to
On 2020-06-09 07:26, Jon Turney wrote:
> On 04/06/2020 21:33, Brian Inglis wrote:
>> On 2020-06-04 10:01, Ken Brown via Cygwin-apps wrote:
>>> On 5/27/2020 6:27 PM, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
> To remedy this lack, using the same ssh key you use for sftp
On 04/06/2020 21:33, Brian Inglis wrote:
On 2020-06-04 10:01, Ken Brown via Cygwin-apps wrote:
On 5/27/2020 6:27 PM, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package upload,
package maintainers can now also push to
> 04.08.2019 21:08, Jon Turney wrote:
>> While a number of maintainers keep their cygwin packaging under some
>> sort of version control, there is currently no central collection of
>> these repositories.
>>
>> To remedy this lack, using the same ssh key you use for sftp package
>> upload, package
On 2020-06-04 10:01, Ken Brown via Cygwin-apps wrote:
> On 5/27/2020 6:27 PM, Jon Turney wrote:
>> On 04/08/2019 21:08, Jon Turney wrote:
>>> To remedy this lack, using the same ssh key you use for sftp package upload,
>>> package maintainers can now also push to git repositories, like so:
>>
On 5/27/2020 6:27 PM, Jon Turney wrote:
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package upload,
package maintainers can now also push to git repositories, like so:
Package maintainers may have noticed that the output from pushing to
04.08.2019 21:08, Jon Turney пишет:
>
> While a number of maintainers keep their cygwin packaging under some
> sort of version control, there is currently no central collection of
> these repositories.
>
> To remedy this lack, using the same ssh key you use for sftp package
> upload, package
On Wed, May 27, 2020 at 11:27:49PM +0100, Jon Turney wrote:
> Currently, many packages will fail to build correctly due to:
>
> (iii) resource limits imposed by AppVeyor's free service which is used to
> perform the actual builds, or
Azure Devops may worth a try.
s
On 04/08/2019 21:08, Jon Turney wrote:
To remedy this lack, using the same ssh key you use for sftp package
upload, package maintainers can now also push to git repositories, like so:
Package maintainers may have noticed that the output from pushing to
these git repositories now includes a
Jon Turney writes:
> To remedy this lack, using the same ssh key you use for sftp package
> upload, package maintainers can now also push to git repositories,
> like so:
>
> git push
> cygwin-rdbxbdvo6bxqt0dzr+a...@public.gmane.org:/git/cygwin-packages/
>
> where is a package name you are listed
On 09/08/2019 20:12, Ken Brown wrote:
On 8/9/2019 12:12 PM, Jon Turney wrote:
On 08/08/2019 18:09, Ken Brown wrote:
On 8/8/2019 10:04 AM, Andrew Schulman via cygwin-apps wrote:
These repositories are lazily created on the first push.
In my testing, git push hangs on the first push, after
On 04/08/2019 21:08, Jon Turney wrote:
These repositories are viewable via gitweb at
https://cygwin.com/git-cygwin-packages/ (URL may be subject to change),
and should be cloneable via anonymous git/http with the URLs shown there.
Please give this a test, if possible, and report any
On 2019-08-04 14:08, Jon Turney wrote:
>
> While a number of maintainers keep their cygwin packaging under some sort of
> version control, there is currently no central collection of these
> repositories.
>
> To remedy this lack, using the same ssh key you use for sftp package upload,
> package
On 8/9/2019 12:12 PM, Jon Turney wrote:
> On 08/08/2019 18:09, Ken Brown wrote:
>> On 8/8/2019 10:04 AM, Andrew Schulman via cygwin-apps wrote:
These repositories are lazily created on the first push.
>>>
>>> In my testing, git push hangs on the first push, after "Initialized empty
>>>
On 08/08/2019 18:09, Ken Brown wrote:
On 8/8/2019 10:04 AM, Andrew Schulman via cygwin-apps wrote:
These repositories are lazily created on the first push.
In my testing, git push hangs on the first push, after "Initialized empty
git repositories". After I interrupt, it finishes normally.
On 04/08/2019 21:08, Jon Turney wrote:
Since it's intended that these repositories will only contain cygport
scripts, patches, and other packaging files, and to prevent the
accidental committing of upstream archives, pushes containing large
binary files will be rejected.
Actually, it seems
On 8/8/2019 10:04 AM, Andrew Schulman via cygwin-apps wrote:
>>
>> While a number of maintainers keep their cygwin packaging under some
>> sort of version control, there is currently no central collection of
>> these repositories.
>>
>> To remedy this lack, using the same ssh key you use for sftp
>
> While a number of maintainers keep their cygwin packaging under some
> sort of version control, there is currently no central collection of
> these repositories.
>
> To remedy this lack, using the same ssh key you use for sftp package
> upload, package maintainers can now also push to git
> While a number of maintainers keep their cygwin packaging under some
> sort of version control, there is currently no central collection of
> these repositories.
>
> To remedy this lack, using the same ssh key you use for sftp package
> upload, package maintainers can now also push to git
On 8/4/2019 4:08 PM, Jon Turney wrote:
>
> While a number of maintainers keep their cygwin packaging under some sort of
> version control, there is currently no central collection of these
> repositories.
>
> To remedy this lack, using the same ssh key you use for sftp package upload,
>
While a number of maintainers keep their cygwin packaging under some
sort of version control, there is currently no central collection of
these repositories.
To remedy this lack, using the same ssh key you use for sftp package
upload, package maintainers can now also push to git
49 matches
Mail list logo
