On 2020-09-14 23:34, ASSI wrote:
> Brian Inglis writes:
>> Any changes made or needed in cygport or scallywag for mingw64 packages?
>> I've rebuilt and reuploaded both Mingw curl noarches to see if they make it.
>
> If you're just trying out things push to the playground branch and
> iterate it
Jon Turney writes:
> Unfortunately, we don't analyze the cygport in the git post-receive
> hook (since there are potential security concerns with doing that), so
> I've made it so the job gets started, but should fairly quickly
> discover it doesn't have anything to do if 'nobuild' is present.
On 15/09/2020 17:54, Andrew Schulman via Cygwin-apps wrote:
Please create a new package socat2, with me as the maintainer. It seems
that socat versions 1 and 2 are long-term different, and creating a
separate socat2 package will allow me to stop treating socat 2.x releases
as perpetually in
Please create a new package socat2, with me as the maintainer. It seems
that socat versions 1 and 2 are long-term different, and creating a
separate socat2 package will allow me to stop treating socat 2.x releases
as perpetually in test.
Thanks,
Andrew
On 15/09/2020 16:49, Ken Brown via Cygwin-apps wrote:
Is there a way to tell scallywag to ignore a commit? Maybe
"SCALLYWAG=nobuild"?
Yeah, this seems like a useful thing to have.
Unfortunately, we don't analyze the cygport in the git post-receive hook
(since there are potential security
Jon,
Is there a way to tell scallywag to ignore a commit? Maybe "SCALLYWAG=nobuild"?
Here's my use case. I've just made some maintenance updates to about 30
texlive-collection-*.cygport files. I do this every few months to reduce the
annual work when there's a new TeX Live release. I'd
