Re: About the opam package

2020-07-19 Thread Andy Li
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 cygwin packages.

Best,
Andy


Re: About the opam package

2020-07-14 Thread Andy Li
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 the patch.

I'm the maintainer of the opam cygwin package. (FYI, you can see the
list of cygwin package maintainer at
https://cygwin.com/cygwin-pkg-maint)
The package source is at https://github.com/andyli/opam-cygwin
Feel free to send me PR.

Best,
Andy


Re: Any chance of updating the ocaml package?

2019-11-28 Thread Andy Li
On Thu, Nov 28, 2019 at 11:15 PM David Allsopp
 wrote:
>
> On 28 Nov 2019, at 15:09, Andy Li  wrote:
> >
> > Hi,
> >
> > The ocaml package is a bit dated.
> > The currently packaged version is 4.04.2, released Jun 23, 2017.
> > The latest ocaml version is 4.09.0, released Sep 18, 2019.
> > It would be great to have it updated.
> >
>
> There’s a problem which needs to be fixed in flexdll which prevents OCaml 
> working properly on Cygwin64 at the moment. When we’ve fixed that, it’ll be 
> possible to update the OCaml package. In the meantime, on Cygwin32, opam 
> works to provide the more recent versions.

Thanks for the info!
I would like to package Dune. Its latest version requires at least ocaml 4.06.
Looking forward to the eventual package update.

Best,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Any chance of updating the ocaml package?

2019-11-28 Thread Andy Li
Hi,

The ocaml package is a bit dated.
The currently packaged version is 4.04.2, released Jun 23, 2017.
The latest ocaml version is 4.09.0, released Sep 18, 2019.
It would be great to have it updated.

Best,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Update libgc?

2019-03-29 Thread Andy Li
> > Any chance you could update libgc to a later release?  I built and 
> > installed libgc-8.0.2, which
> > is the latest release available at http://www.hboehm.info/gc/gc_source/, 
> > and the
> > crash didn't occur.
>
> Yes, I will look into that. Upstream even made a PR to my cygport file
> a few days ago: https://github.com/andyli/libgc-cygwin/pull/7
> I'm checking with him about backward compatibility.

I've just uploaded libgc 8.0.4-1.

Best,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Update libgc?

2019-03-29 Thread Andy Li
Hi Ken,

On Sat, Mar 30, 2019 at 12:34 AM Ken Brown  wrote:
> I'm getting a crash in cyggc-1.dll when building asymptote.

It would be great if you can report this to the upstream because I
think the 7.x series is still being supported and there are new
releases now and then, so it would be nice to have that bug fixed in
7.x as well.

> Any chance you could update libgc to a later release?  I built and installed 
> libgc-8.0.2, which
> is the latest release available at http://www.hboehm.info/gc/gc_source/, and 
> the
> crash didn't occur.

Yes, I will look into that. Upstream even made a PR to my cygport file
a few days ago: https://github.com/andyli/libgc-cygwin/pull/7
I'm checking with him about backward compatibility.

Best,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: cygwin.com is down

2018-12-13 Thread Andy Li
I did use downforeveryoneorjustme to check before posting here, and it was
down.
But I can see that it is up again now.
Thanks anyway :)

Best,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



cygwin.com is down

2018-12-13 Thread Andy Li
Looks like the website is down :(

Best,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: how to use opam for package builds?

2018-08-29 Thread Andy Li
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 not sure why it is that slow though.


> (2) Even if I get this to work, I don't think it's the right thing to do
> because it's setting up persistent opam configuration in my home directory,
> which I don't think is the right place for packaging. Should there be some
> global opam configuration, that all packaging scripts that rely on opam
> would use? If so, where should that go?


Indeed the proper way is to package each ocaml library as cygwin packages
and then the orpie package just build depends on them instead of calling
opam.
There are several already packaged ocaml libraries. You may study their
cygport files in
https://github.com/cygwinports?utf8=%E2%9C%93=ocaml==

Hope it helps.

Best,
Andy


How portable (relocatable) is a Cygwin installation?

2018-05-09 Thread Andy Li
Hi,

We are looking for an easy way to distribute an OCaml development
enviroment based on Cygwin. Someone has an idea of installing all the
necessary packages and zip the whole Cygwin installation directory and
distribute the resulting archive.

Is it a good idea? Is the installation path written in a Cygwin
installation somewhere that may need to be updated when relocating? Is
there any registry entry or env var required for a Cygwin installation to
work?

Best regards,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with Ocaml dllunix.so, flexdll error: cannot relocate, target is too far

2018-05-03 Thread Andy Li
Hi,

On Thu, May 3, 2018 at 6:07 AM, David Conrad  wrote:
>
> Cannot load required shared library dllunix.
> Reason: /usr/lib/ocaml/stublibs/dllunix.so: flexdll error: cannot
> relocate RELOC_REL32, target is too far: 0xfffc12f78b5f
> 0x12f78b5f.


 This is a known issue. A workaround can be found in
https://cygwin.com/ml/cygwin-apps/2017-04/msg3.html

Best,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Missing dependencies for opam package

2018-01-15 Thread Andy Li
On Thu, Jan 11, 2018 at 8:50 PM, David Allsopp 
wrote:
>
> So, in summary, the following dependencies would be good to have added to
> the opam package, in descending order of importance:
>
>   flexdll
>   libX11-devel
>   diffutils
>   tar
>   patch
>   unzip
>   curl (or wget, if preferred)
>   gcc-core
>   make
>   m4
>   rsync
>   git
>   mercurial
>   ocaml


Thanks for the detailed explanation!
I've just added those in the opam 1.2.2-2 package.

Best regards,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Removing a faulty package?

2018-01-15 Thread Andy Li
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: cyggc-1.dll, cyggccpp-1.dll, and cygcord-1.dll.
The new libgc (7.6.2) bumped gc to cyggc-2.dll, while the other 2 remain at
so version 1.
My plan is to split the current (7.6.0) libgc1 into 3 packages, one for
each dll file, and let the downstream packages rebuild and depend on the
right packages before I upload a new version.
So, I would like to ping the related package maintainers to do so.

Best regards,
Andy


Removing a faulty package?

2018-01-15 Thread Andy Li
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: lftp 4.8.0-1

2017-10-11 Thread Andy Li
> lftp 4.7.8-1 is now available in test. Please try that and let me know if it
> fixes the problem for you. I'll continue to work on packaging 4.8.2.

I confirm lftp 4.7.8-1 works as expected.
Thank you!

Best regards,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Cygwin Docker image

2017-10-08 Thread Andy Li
Hi,

I'm trying to create a Cygwin Docker image, in order to have a
completely isolated Cygwin environment.

I'm able to install Cygwin in the Windows Server Core image, but the
installed bash.exe exits immediately when I run it. The exit code is
0, so I suppose it is not a crash. Do you have any idea why this
happen?

Here is the Dockerfile I have (can also be viewed in
https://gist.github.com/andyli/0fc84d60bf29b54b8213fba8ff7d8d24/44a6e02aa340baa721c2707095d7143127544fd8#file-dockerfile):

FROM microsoft/windowsservercore

SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop';"]

RUN $url = 'https://cygwin.com/setup-x86_64.exe'; \
Write-Host ('Downloading {0} ...' -f $url); \
Invoke-WebRequest -Uri $url -OutFile 'C:/setup-x86_64.exe'; \
\
Write-Host 'Installing ...'; \
New-Item -ItemType directory -Path 'C:/tmp'; \
Start-Process "C:/setup-x86_64.exe" -NoNewWindow -Wait
-PassThru -ArgumentList
@('-q','-v','-n','-B','-R','C:/cygwin64','-l','C:/tmp','-s','http://mirror.pkill.info/cygwin/','-P','default');
\
\
Write-Host 'Removing ...'; \
Remove-Item -Path 'C:/tmp' -Force -Recurse -ErrorAction Ignore; \
\
Write-Host 'Verifying install ...'; \
Start-Process "C:/cygwin64/bin/cygcheck.exe" -NoNewWindow
-Wait -PassThru -ArgumentList @('-c'); \
\
Write-Host 'Complete.';

CMD ["C:/cygwin64/bin/bash.exe"]

To build it, run
   docker build -t cygwin .

To create a container and start cmd:
   docker run -it --rm cygwin cmd

Any help is appreciated.

Best regards,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: git 2.14.2-1 is faulty

2017-09-30 Thread Andy Li
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

2017-09-30 Thread Andy Li
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
https://stackoverflow.com/questions/8329485/unable-to-find-remote-helper-for-https-during-git-clone,
probably the package was built without libcurl-devel.

I've only tested x86_64, not sure about x86.

Best regards,
Andy


Re: lftp 4.8.0-1

2017-09-27 Thread Andy Li
On Thu, Sep 28, 2017 at 10:41 AM, Andy Li <a...@onthewings.net> wrote:

>
>
>> Still getting this, but have since paid a bit more attention to the
>> output,
>> and I'm seeing:
>>
>> assertion "ptr(x.heap_index)==" failed: file
>> "/home/ASchulma/dev/cygwin/lftp/lftp-4.8.0-1.x86_64/src/lftp-4.8.0/src/xheap.h",
>> line 127, function: void xheap::remove(xheap::node&) [with T =
>> Timer]
>
>
> I've just got the same error when running cygport upload in x86.
> Interestingly, there was no error when I did the same in x86_64.
> Downgrading lftp to the previous version (4.7.7-1) "fixed" the cygport
> upload.
>

Just noticed that it has been reported upstream and fixed in lftp 4.8.2.
https://github.com/lavv17/lftp/issues/390

Andrew: Would you package that soon?

Best regards,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: lftp 4.8.0-1

2017-09-27 Thread Andy Li
> Still getting this, but have since paid a bit more attention to the output,
> and I'm seeing:
>
> assertion "ptr(x.heap_index)==" failed: file "/home/ASchulma/dev/cygwin/
> lftp/lftp-4.8.0-1.x86_64/src/lftp-4.8.0/src/xheap.h", line 127, function:
> void xheap::remove(xheap::node&) [with T = Timer]


I've just got the same error when running cygport upload in x86.
Interestingly, there was no error when I did the same in x86_64.
Downgrading lftp to the previous version (4.7.7-1) "fixed" the cygport
upload.

Best,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: libgc: problem with 7.6.0-1 version

2017-07-10 Thread Andy Li
Hi Marco,

Sorry that I missed your msg since I only subscribe to cygwin-apps but
not cygwin...


On Sat, Jul 8, 2017 at 5:29 PM, Marco Atzeri  wrote:
> Can you check for any difference between 7.6.0-1 and 7.2d-2 ?


7.2d was released in 2012, and 7.6.0 was released in 2016, so there
are quite a lot of changes...
(https://github.com/ivmai/bdwgc/blob/master/ChangeLog)

For neko, the situation is reversed, i.e. neko crashes with libgc
7.2d, but it runs fine with libgc 7.6.

You may file an issue to libgc directly, since Ivan is pretty helpful
and responsive: https://github.com/ivmai/bdwgc/issues

Best regards,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Haxe package

2017-05-29 Thread Andy Li
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.

> With that added, package looks GTG.  I added it to your uploads.

Thanks! Just uploaded the package!

Best regards,
Andy


Re: Haxe package

2017-05-28 Thread Andy Li
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 check and it still build fine on my machine...
I notice your build log contains "make: *** Waiting for unfinished
jobs", does it mean `make` was run in parallel mode somehow?
The Haxe makefile doesn't support parallel build so I set
`MAKEOPTS="-f Makefile.win"` that removes the `-j` opt. Maybe there is
some other setting that caused a parallel build?

Best,
Andy


Re: Haxe package

2017-05-25 Thread Andy Li
I've revised according to all the comments in github.
Is there any other thing you would like to adjust?

Best regards,
Andy


Haxe package

2017-05-15 Thread Andy Li
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 let me know if there is any problem.

Best regards,
Andy


Re: opam package

2017-05-12 Thread Andy Li
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
>
> cygconf
> cygmake lib-ext
> cygmake
> cd ${B}/doc
> cygmake man
> }

Thanks for the suggestion! I've added that by combining the commands into

cygmake lib-ext man all

> In addition as it is a OCaml Package Manager, may be it should require at
> least "ocaml" ?

It's a bit special here. Opam is also a OCaml version manager that
allows ppl install multiple different versions of OCaml into ~/.opam.
Though it can use the system (Cygwin) OCaml, opam can work by itself.

Best regards,
Andy


Re: adopt and update libatomic_ops and libgc

2017-05-11 Thread Andy Li
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
>


opam package

2017-05-10 Thread Andy Li
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 know if there is any problem.

Best regards,
Andy


Re: adopt and update libatomic_ops and libgc

2017-05-09 Thread Andy Li
> 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 src_install which
>> calls cyginstall then moves the directory, which might be less
>> brittle to changes in the file list?
>> This might be an upstream defect if it doesn't respect --docdir?

Right, I've just sent a PR to the upstream to fix it. See
https://github.com/ivmai/libatomic_ops/pull/25
I've included it as a patch in the cygport file, which we can remove
in the next version if the PR is merged.

>> libgc.cygport:
>> DEPEND might be better written pkgconfig(atomic_ops)
>> Again, stuff installed to usr/share/gc/ should probably be moved to
>> usr/share/doc/gc

Similarly, the PR: https://github.com/ivmai/bdwgc/pull/161

>> I note we also have libgc-7.2d-2 as non-source package, which just
>> contains usr/share/doc/Cygwin/libgc.README. That probably needs to
>> be cleaned up by being obsoleted.

What is the procedure of obsoleting packages?

Best regards,
Andy


adopt and update libatomic_ops and libgc

2017-05-07 Thread Andy Li
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 them into separated packages, since the source of
libgc no longer contains a copy of atomic_ops, and they are versioned
independently as well.

Please review and let me know if there is anything to improve.

Best regards,
Andy


camlp4o Fatal error: cannot load shared library dllunix

2017-05-05 Thread Andy Li
Hi,

I'm having issue with the camlp4 Cygwin package
(ocaml-camlp4-4.04+1-1) in the 64-bit Cygwin.
When I run camlp4o, it returns an error:

> $ camlp4o
> Fatal error: cannot load shared library dllunix
> Reason: flexdll error: cannot relocate RELOC_REL32, target is too far: 
> 0xfffc0dad8b5f  0xdad8b5f

I tried rebaseall, but it didn't help.

I notice that ocaml-camlp4 depends on ocaml-base, which is "Obsoleted
by ocaml" according to
https://cygwin.com/cgi-bin2/package-grep.cgi?grep=ocaml-base=x86_64
Could it be the source of error?

Interestingly, camlp4o works correctly in my 32-bit Cygwin, but not 64-bit one.

I wonder if anyone can reproduce the problem, or it's just my
machine's issue? Any help is appreciated.

Best regards,
Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Neko package

2017-05-03 Thread Andy Li
> 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 that (it already has to deal with some other
> non-standard extensions for DLLS)
>

Good idea! I will look into it.

Best regards,
Andy


Re: Neko package

2017-04-30 Thread Andy Li
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 at least a minimal manual, like debian
> https://packages.debian.org/sid/amd64/neko/filelist
>
> /usr/share/man/man1/neko.1.gz
> /usr/share/man/man1/nekoc.1.gz
> /usr/share/man/man1/nekoml.1.gz
> /usr/share/man/man1/nekotools.1.gz
>
> specially as the programs are not following standard expectation
>
> $ ./neko --help
> Uncaught exception - load.c(181) : Module not found : --help
>
> From this point of view, it seems a lack of Neko in general.

Yes, it is quite funny that the Neko VM doesn't even support --help...
Anyway, I've just created some manpages that are based on the Debian
ones, which are somewhat outdated.
I will update the manpages in the Debian package next time I update
it. (I'm the maintainer of the Debian package)


> Any reason to not build debuginfo and skipping strip ?

It is mainly because "nekoc", "nekoml", and "nekotools" are built in a
special way, using "nekotools boot ".
The way it works is to copy "neko.exe" and appends it with the
"file.n" Neko bytecode.
If the output file is stripped, the appended  bytecode will be removed.
I myself consider it a bad way of producing executables, and for the
next version of Neko, those exe will be built "properly", such that
they can be stripped.
For more info, see https://github.com/HaxeFoundation/neko/issues/130


Let me know if there is any remaining issue.

Best regards,
Andy


Neko package

2017-04-30 Thread Andy Li
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 at:
https://github.com/andyli/neko-cygwin

Please review and let me know if it is up to standard or not.

Best regards,
Andy


Re: mbed TLS package

2017-04-29 Thread Andy Li
> 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 would be much better if cygport just said "no" when you tried to use a
> package name with a hyphen followed by a digit.

I've just reported that to cygport at
https://github.com/cygwinports/cygport/issues/2.


> Name the package 'libmbedx509_0'

Renamed and uploaded successfully. Thanks!

Best regards,
Andy


Re: mbed TLS package

2017-04-29 Thread Andy Li
I've just tried to upload the package, and calm notified me about the
errors as follows:

> ERROR: package 'libmbedtls10' version '2.4.2-1' requires nonexistent package 
> 'libmbedx509'
> ERROR: package 'mbedtls-devel' version '2.4.2-1' requires nonexistent package 
> 'libmbedx509'
> 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


Re: mbed TLS package

2017-04-29 Thread Andy Li
> 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 ... TIMING
> tests note: will take some time!
>   TIMING test #1 (set_alarm / get_timer): passed
>   TIMING test #2 (set/get_delay): failed
> FAILED
>   mbedtls_timing_self_test( 1 ) == 0
>   at line 13,
> /cygdrive/e/cyg_pub/temp/mbedtls-2.4.2-1.x86_64/src/mbedtls-2.4.2/tests/suites/test_suite_timing.function
>
> 
>
> FAILED (0 / 1 tests (0 skipped))

Strangely, the test passed on my 2 machines, with 32-bit and 64-bit Cygwin...
Not sure what's the cause of this.


Best regards,
Andy


Requesting upload privileges

2017-04-29 Thread Andy Li
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/6a1BqwmzINMLJ0
CPWtjQgFjWtAlIzdsAdFAQZBNXpgP2ivnYcFqfqojwG9aIEOzkzZnFk/NkuK5/PYJRsM4u
WS6mfI61MEJ5jHaX1Q/MqM5wDXJb5yudMgw+lbjsULKIK2egny56vWtWUC9oZcs6YG
mWFAETHOtKVHked+cyJerFzNyG9op11ZVBiB8SFLdlYq7zQOUEWWCYV6rVfyk8zYfeZeU4
/7V0PjqkszczKGe97TQ08N
 END SSH2 PUBLIC KEY 


Re: mbed TLS package

2017-04-29 Thread Andy Li
Thanks for the review!
I've just updated the cygport file as suggested:

 * moved the dll files to /usr/bin
 * use DIFF_EXCLUDES to exclude the source changes during building
apidoc and tests
 * do not build/install the programs, which are indeed just demos
according to https://github.com/ARMmbed/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 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 worked on is mbed TLS [2], and the cygport file I
>> created can be found at:
>> https://github.com/andyli/cygwinports-mbedtls
>>
>> It would be great if you can review and let me know if it is up to
>> standard for inclusion in the cygwin.com archive. Please bear with me
>> if there is any silly mistake since this is my first time packaging
>> for Cygwin.
>> FYI, here are the Debian and Fedora packages:
>>  * https://anonscm.debian.org/cgit/collab-maint/mbedtls.git/tree/debian
>>  * http://pkgs.fedoraproject.org/cgit/rpms/mbedtls.git/tree/mbedtls.spec
>>
>> Best regards,
>> Andy
>>
>> [1]: https://haxe.org/
>> [2]: https://tls.mbed.org/
>>
>
> Hi Andy,
>
> the shared library are in the wrong place:
>
>>>> libmbedcrypto0-2.4.2-1.tar.xz
> usr/lib/cygmbedcrypto-0.dll
>
>>>> libmbedtls10-2.4.2-1.tar.xz
> usr/lib/cygmbedtls-10.dll
>
>>>> libmbedx509-0-2.4.2-1.tar.xz
> usr/lib/cygmbedx509-0.dll
>
> On cygwin the shared lib are in /usr/bin .
>
> On my build, documentation was rebuilt and most of the
> source was changed:
>
>>>> Creating source patches
>  apidoc/aes_8h.html|  813
>  apidoc/aes_8h__dep__incl.map  |5
>
>  apidoc/xtea_8h__incl.md5  |1
>  apidoc/xtea_8h_source.html|   64
>  566 files changed, 150300 insertions(+)
>
>
> use DIFF_EXCLUDES="apidoc/*" to avoid to include a source patch file.
>
>
> in the list of binaries, I see some that look as test programs;
> may be they should not be installed ?
>
> usr/bin/aescrypt2.exe
>->   usr/bin/benchmark.exe
> usr/bin/cert_app.exe
> usr/bin/cert_req.exe
> usr/bin/cert_write.exe
> usr/bin/crl_app.exe
> usr/bin/crypt_and_hash.exe
> usr/bin/dh_client.exe
> usr/bin/dh_genprime.exe
> usr/bin/dh_server.exe
> usr/bin/dtls_client.exe
> usr/bin/dtls_server.exe
> usr/bin/generic_sum.exe
> usr/bin/gen_entropy.exe
> usr/bin/gen_key.exe
> usr/bin/gen_random_ctr_drbg.exe
> usr/bin/gen_random_havege.exe
>->   usr/bin/hello.exe
> usr/bin/key_app.exe
> usr/bin/mini_client.exe
> usr/bin/mpi_demo.exe
> usr/bin/pem2der.exe
> usr/bin/pk_decrypt.exe
> usr/bin/pk_encrypt.exe
> usr/bin/pk_sign.exe
> usr/bin/pk_verify.exe
> usr/bin/req_app.exe
> usr/bin/rsa_decrypt.exe
> usr/bin/rsa_encrypt.exe
> usr/bin/rsa_genkey.exe
> usr/bin/rsa_sign.exe
> usr/bin/rsa_verify.exe
> ->  usr/bin/selftest.exe
> usr/bin/ssl_cert_test.exe
> usr/bin/ssl_client1.exe
> usr/bin/ssl_client2.exe
> usr/bin/ssl_fork_server.exe
> usr/bin/ssl_mail_client.exe
> usr/bin/ssl_pthread_server.exe
> usr/bin/ssl_server.exe
> usr/bin/strerror.exe
> usr/bin/udp_proxy.exe
>
> I have the impression that neither debian nor fedora install
> any of the programs
>
> https://apps.fedoraproject.org/packages/mbedtls/
>
>


mbed TLS package

2017-04-27 Thread Andy Li
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 worked on is mbed TLS [2], and the cygport file I
created can be found at:
https://github.com/andyli/cygwinports-mbedtls

It would be great if you can review and let me know if it is up to
standard for inclusion in the cygwin.com archive. Please bear with me
if there is any silly mistake since this is my first time packaging
for Cygwin.
FYI, here are the Debian and Fedora packages:
 * https://anonscm.debian.org/cgit/collab-maint/mbedtls.git/tree/debian
 * http://pkgs.fedoraproject.org/cgit/rpms/mbedtls.git/tree/mbedtls.spec

Best regards,
Andy

[1]: https://haxe.org/
[2]: https://tls.mbed.org/