On 2022-10-09 10:23, Jon Turney wrote:
> Thanks for looking into updating this. I'd like to give the existing
> maintainer first refusal, though.
>
Absolutely. It's totally OK with me if Jari would rather still maintain
this. I just figured I'd try my hand at the process in the meantime,
On 2022-10-09 14:23 UTC, Jon Turney wrote:
On 06/10/2022 02:29, Chad Dougherty wrote:
I've been using cygwin for a long time but this is my first attempt at
this process so please be gentle :)
I noticed that the current rsync package (3.2.3+20200903+git9f9240b-4)
is trailing on security
On 2022-10-09 11:09, Chad Dougherty wrote:
In the case of minisign, it uses CMake and needed to invoke cygcmake,
that's why I left src_compile() there. Is that wrong? It didn't
compile with that commented out even though I inherit cmake.
Err, disregard this. I failed to understand
On 2022-10-09 10:33, Jon Turney wrote:
Thanks.
I think I'd like to be using minisign to sign setup.ini for Cygwin's
setup, rather than the accident waiting to happen which is libgpg, but
that's a whole other project...
I admit that was an ulterior motive but I also recognize there's a
On 08/10/2022 14:52, Chad Dougherty wrote:
Hello,
I'm interested in becoming a package maintainer for minisign:
https://jedisct1.github.io/minisign/
I suspect the mailing list was blocking my original announcement about
this so I have put all of the relevant information in the README here:
On 06/10/2022 02:29, Chad Dougherty wrote:
Hello all,
I've been using cygwin for a long time but this is my first attempt at
this process so please be gentle :)
I noticed that the current rsync package (3.2.3+20200903+git9f9240b-4)
is trailing on security updates and also still using the
Hello to everyone,
I would like to package nnn for cygwin
https://github.com/jarun/nnn/
nnn is already packaged and distributed on different systems/distributions:
https://packages.debian.org/search?keywords=nnn
https://packages.gentoo.org/packages/app-misc/nnn
On Sun, 09 Oct 2022 08:58:45 +0200, ASSI wrote:
Brian Inglis writes:
After upload, noticed in calm deployment log that release current - 2
is being vaulted, but it's still showing in setup.ini.
If current - 2 is selected in setup, won't this cause setup to fail,
as as it will no longer be
Brian Inglis writes:
> After upload, noticed in calm deployment log that release current - 2
> is being vaulted, but it's still showing in setup.ini.
> If current - 2 is selected in setup, won't this cause setup to fail,
> as as it will no longer be available under release/, nor propagated on
>
