Re: Attn: libgpg-error maintainer

[Marco Atzeri <marco.atzeri@gmail.com>]

On 25/06/2024 01:00, Brian Inglis via Cygwin-apps wrote:
> On 2024-06-24 14:52, Marco Atzeri via Cygwin-apps wrote:
>> On 24/06/2024 20:04, Brian Inglis via Cygwin-apps wrote:
>>> On 2024-06-24 11:14, Brian Inglis via Cygwin-apps wrote:
>>>> On 2024-06-23 20:37, Ken Brown via Cygwin-apps wrote:
>>>>> On 6/23/2024 7:46 PM, Brian Inglis via Cygwin-apps wrote:
>>>>>> On 2024-06-23 15:46, Marco Atzeri via Cygwin-apps wrote:
>>>>>>> On 23/06/2024 22:13, Marco Atzeri wrote:
>>>>>>>> On 22/06/2024 19:57, Brian Inglis via Cygwin-apps wrote:

>> I just upload a 1.50 test version were the errors are down to 1
>>
>> PASS: t-strerror.exe
>> fopen failed with bad code: 20
>> FAIL: t-syserror.exe
>> PASS: t-lock.exe
>> PASS: t-printf.exe
>> PASS: t-poll.exe
>> PASS: t-b64.exe
>> ..
>> PASS: t-argparse.exe
>> PASS: t-logging.exe
>> PASS: t-stringutils.exe
>> PASS: t-malloc.exe
>> =======================================
>> 1 of 11 tests failed
>>
>> let me know if libgcrypt can be built
> 
> Thanks Marco,
> 
> Great catch!
> 
> All tests pass for both libgpg-error 1.50 and libgcrypt: see attached logs.
> I installed both locally and interactive tests of gpg{,v}{,2} all pass.
> I fetched the latest Cygwin pubkey as I was getting warnings from my 
> scripts, and they are now all quiet.
> So I am now dogfooding those two until your libgpg-error is officially 
> updated, then I can officially update my libgcrypt!
> 
> I made some tweaks to your libgpg-error cygport just in case something 
> helped with the issue.
> I impertinently pushed some changes to your libgpg-error playground 
> build to see if there were any differences in there.
> Please have a look at the manifest patch and cygport updates in the 
> libgpg-error playground branch and jobs.
> My tweaked cygport seems to have passed there also; please see:
> https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=libgpg-error
> 
> I have no idea what may have made the difference.
> I updated the URIs, patched the manifest for W10, updated bld-req, added 
> -cygwin to config PACKAGE_VERSION, added reproducible build timestamp, 
> commented out test function override, added licence?
> 
> I am also adding -cygwin to config PACKAGE_VERSION and reproducible 
> build timestamp to libgcrypt (based on origsrc/.../ChangeLog as that 
> seems consistent across packages: whereas src ChangeLog and other files 
> seem to be copied or could be patched by us)!
> 

1.50-2 is up as standard
mainly around your version of cygport.
Thanks for the manifest patch

the single test is still failing on my PC but pass with some strange 
errors on Scallywag

moving out of test also libksba and gnupg2


Regards
Marco