Requesting upload privileges

Name: Andy Li Package: mbedtls BEGIN SSH2 PUBLIC KEY Comment: "2048-bit RSA, converted by Andy@Hawk from OpenSSH" B3NzaC1yc2EDAQABAAABAQCgG2UKLvIaPrxFE/ZpmrW9L4DH2vNItTlKvIqkfo oZFFUZiqFyFuEVvqe19xv019NWe/HT4H3w5xP2/8o2rHYjJuICN/A5p/6a1B

Re: mbed TLS package

/mbedtls#example-programs Let me know if there is anything that can improve :) Best regards, Andy On Sat, Apr 29, 2017 at 5:14 AM, Marco Atzeri <marco.atz...@gmail.com> wrote: > On 28/04/2017 07:32, Andy Li wrote: >> >> Hi, >> >> This is Andy, a mem

Re: mbed TLS package

> please no TOFU > https://cygwin.com/acronyms/#TOFU Noted. Sorry about that! > Only one test is failing on both architecture, > but is not a blocking point > > $ PATH=/pub/temp/mbedtls-2.4.2-1.x86_64/build/library:$PATH > ./test_suite_timing.exe -v > Timing selftest

Re: mbed TLS package

t; ERROR: error while validating merged x86 packages for Andy Li > SUMMARY: 3 ERROR(s) Maybe it's because of "libmbedx509" having a number at the end of its name, incorrectly interpreted as its version number (0)? Its package name is "libmbedx509-0". Any tips to fix it is appreciated. Best regards, Andy

mbed TLS package

Hi, This is Andy, a member of the Haxe Foundation, which is the organization behind the Haxe programming language [1]. I would like to maintain a Cygwin package for Haxe. There are some dependencies not packaged for cygwin, so I am going to package and maintain them as well. The first one I

Neko package

Hi, Following up my quest of packaging Haxe. After creating a Cygwin package for mbed TLS, here is another one: Neko, which is a VM kind of comparable to Lua. Neko is maintained by the Haxe Foundation. More info of Neko can be found at http://nekovm.org/. The cygport file I created can be found

Re: mbed TLS package

> Using a package name containing a hyphen followed by a digit isn't actually > forbidden currently, but perhaps should be. It introduces an ambiguity > about where the version starts. > > This seems to tickle a bug somewhere in cygport as it doesn't generate the > requires: correctly > > It

Re: Neko package

> Looks ok to me. I added neko to your package list. Thanks! I will upload the package soon! >> # cygport cannot auto detect these, since the ndll files are not >> # named with .dll. > > > If these really are just .dll by another name, you might want to explore > patching cygport to teach it

Re: opam package

On Fri, May 12, 2017 at 4:21 AM, Marco Atzeri wrote: > build fine and pass the tests, however there are no manual. > This should do the trick > > src_compile() { > lndirs > cd ${B} > > # $LIBS defined by cygport interferes with OCamlMakefile > unset LIBS >

Re: adopt and update libatomic_ops and libgc

Oh, that was unexpected! Thank you :D Best, Andy On Thu, May 11, 2017 at 10:27 PM, Andrew Schulman wrote: >> I added libatomic_ops and libgc to your package list. > > Gold stars awarded! https://cygwin.com/goldstars/#AL >

Re: adopt and update libatomic_ops and libgc

> On 2017-05-08 05:54, Jon Turney wrote: >> libatomic_ops.cygport: >> A comment that we need to correct for this installing it's >> documentation into usr/share/libatomic_ops, rather that >> usr/share/doc/libatomic_ops might be nice. >> This could alternatively be written using a custom

Haxe package

Hi, Here is the Haxe package I wanted to create and maintain. Haxe is a programming language that compiles to JS, Java, C#, C++, and many more. More info can be found at https://haxe.org/. The haxe.cygport file I created can be found at: https://github.com/andyli/haxe-cygwin Please review and

opam package

Hi, I would like to create and maintain a cygwin package for OPAM, i.e. OCaml Package Manager. It would be a dependency of the next version Haxe, which I would like to package too. The initial cygport file I created can be found at: https://github.com/andyli/opam-cygwin Please review and let me

Re: Haxe package

On Mon, May 29, 2017 at 10:49 PM, Jon Turney wrote: > I think the cygport reference manual recommends an explicit "-j1" in the > cygport MAKEOPTS variable for packages which do not build properly with a > parallel make. Right, I've just added that to to MAKEOPTS. >

Re: Haxe package

I've revised according to all the comments in github. Is there any other thing you would like to adjust? Best regards, Andy

Re: Haxe package

On Fri, May 26, 2017 at 9:01 PM, Jon Turney wrote: > This fails to build for me, the first error is: > > make: *** No rule to make target 'libs/ilib/il.cmxa', needed by > 'src/context/common.cmx'. Stop. > > I wonder if I'm missing some build-dep? I've just double

adopt and update libatomic_ops and libgc

Hi, I would like to adopt and update the now orphaned libatomic_ops and libgc packages, which is a dependency of the neko package I maintained. The updated cygport files can be found at: https://github.com/andyli/libatomic_ops-cygwin https://github.com/andyli/libgc-cygwin Note that I've split

Re: Neko package

Hi Marco, Thanks for the review! > there is a double neko requires: cygwin libneko2 libneko2 neko-std-ndlls > > As libneko2 dependency is already catch by cyport you don't need to > explicitly declare it. I've removed the explicit libneko2 from neko_REQUIRES. > We usually prefer to have

Re: git 2.14.2-1 is faulty

x86_64 $ git --version git version 2.14.1 The issue is about 2.14.2 ;) Best, Andy

git 2.14.2-1 is faulty

Hi, I've just noticed that the git package 2.14.2-1 is buggy: $ git clone https://github.com/andyli/HaxeCI.git Cloning into 'HaxeCI'... fatal: Unable to find remote helper for 'https' According to

Removing a faulty package?

I made a mistake when updating libgc. The new version bumped the so version so it now ships cyggc-2.dll instead of cyggc-1.dll, but I didn't rename the libgc1 package to libgc2. Is there a way to take down the new version (7.6.2)? Sorry for the trouble. Best regards, Andy

Re: Removing a faulty package?

On Tue, Jan 16, 2018 at 12:43 AM, Jon Turney wrote: > > https://cygwin.com/package-upload.html#deleting should work. > Indeed, thanks! Another question: Is there a way to list all the packages that depends on a dll? Currently the libgc1 package contains 3 dll files:

Re: how to use opam for package builds?

Hi, On Wed, Aug 29, 2018 at 11:47 PM Andrew Schulman wrote: > (1) I can't get "opam init" to complete. It hangs after "synchronized from > https://opam.ocaml.org;, until I interrupt it: > It should work, just wait a little longer. For me, it took a bit more than three minutes to complete. I'm

Re: About the opam package

On Fri, Jul 17, 2020 at 9:08 PM Jon Turney wrote: > Please consider mirroring that repo to cygwin.com/git/cygwin-packages/ > (as detailed at [1]) > > [1] https://cygwin.com/packaging/repos.html I wasn't aware of that. Thanks for pointing it out. I have just set up auto mirroring for all my

Re: About the opam package

Hi, On Wed, Jul 15, 2020 at 7:17 AM Sora Morimoto wrote: > Now, I wanted to help with the maintenance of the opam package for Cygwin, > but after reading the documentation I still do not know what to do. > Specifically, I do not even know where the build script source is, and where > to send