[ITA] mhash
Sigh… some old and crusty files…. - x86 - 0.9.9.9-2 (source) from 2015-02-18 22:18 does not work... I pushed the fixed mhash https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/playground.git;a=commitdiff;h=8e7f3a747287f0263bcd1316dedf7ea974914077 https://github.com/cygwin/scallywag/actions/runs/1447027874 While trying to package AIDE for x86, In file included from /usr/include/mhash.h:6, from /cygdrive/c/projects/aide/aide-0.17.3-1.i686/src/aide-0.17.3/include/db_config.h:87, from /cygdrive/c/projects/aide/aide-0.17.3-1.i686/src/aide-0.17.3/include/aide.h:27, from /cygdrive/c/projects/aide/aide-0.17.3-1.i686/src/aide-0.17.3/src/report.c:23: /usr/include/mutils/mincludes.h:82:10: fatal error: values.h: No such file or directory 82 | #include | ^~ compilation terminated. make[1]: *** [Makefile:739: src/report.o] Error 1 make[1]: Leaving directory '/cygdrive/c/projects/aide/aide-0.17.3-1.i686/build' make: *** [Makefile:510: all] Error 2 *** ERROR: make failed So it looks like the x86 build and package of mhash found a windows development kit on the path… Rebuilding and repackaging it allows >>> Checking packages for unexpected, missing or duplicate files >>> Creating source patches include/util.h |1 + 1 file changed, 1 insertion(+) >>> Creating source package aide-0.17.3-1.src/ aide-0.17.3-1.src/aide-0.17.3-1.src.patch aide-0.17.3-1.src/aide-0.17.3.tar.gz aide-0.17.3-1.src/aide-0.17.3.tar.gz.asc aide-0.17.3-1.src/aide.cygport >>> aide requires: cygwin libmhash2 libpcre1 zlib0 cygwin libmhash2 libpcre1 >>> zlib0
RE: playground procedures and docs
> -Original Message- > From: Jason Pyeron > Sent: Wednesday, November 10, 2021 12:57 PM > > > Sent: Wednesday, November 10, 2021 11:25 AM > > That is why it is a good idea to checkout your repo on a playground > > branch, then force push your repo to: > > > > ssh://cyg...@cygwin.com/git/cygwin-packages/playground > > > > and post the jobs.cgi, run, and log links. > > I could not seem to find pages or mailing list archives on the jobs.cgi / run > / log items. https://www.cygwin.com/packaging/build.html Do not know, why I did not see: Package build service (experimental) After pushing to a package git repository, an automatic build of the package is queued: remote: scallywag: build queued remote: scallywag: https://cygwin.com/cgi-bin2/jobs.cgi?id= The results will appear (some time later) at https://cygwin.com/cgi-bin2/jobs.cgi (URL subject to change). -Jason
playground procedures and docs
> Sent: Wednesday, November 10, 2021 11:25 AM > That is why it is a good idea to checkout your repo on a playground > branch, then force push your repo to: > > ssh://cyg...@cygwin.com/git/cygwin-packages/playground > > and post the jobs.cgi, run, and log links. I could not seem to find pages or mailing list archives on the jobs.cgi / run / log items. Sorry, if I am obtuse. v/r, Jason Pyeron -- Jason Pyeron | Architect PD Inc| Certified SBA 8(a) 10 w 24th St | Certified SBA HUBZone Baltimore, MD | CAGE Code: 1WVR6 .mil: jason.j.pyeron@mail.mil .com: jpye...@pdinc.us tel : 202-741-9397
Re: [ITP] aide 0.17.3
On 2021-11-10 05:33, Jason Pyeron wrote:
On Sunday, October 31, 2021 10:37 AM, Jason Pyeron wrote:
On Sunday, October 31, 2021 8:48 AM, Jon Turney wrote:
On 29/09/2021 15:27, Jason Pyeron wrote:
On Friday, July 30, 2021 10:34 AM, Jason Pyeron wrote:
AIDE - Advanced Intrusion Detection Environment
https://github.com/aide/aide/
It is a GPL v2 tool for monitoring file system changes.
There was no (mature?) Windows open source solution until AIDE was built and
tested for
Cygwin. This fills a long standing gap in needs.
Closed source alternative - Trip Wire.
It is packaged and shipped with most Linux distributions - I am most familiar
with the
RHEL packaging.
I have built and tested the most recent stable and development versions.
I will track the development versions for test package releases.
Category Security.
Thoughts?
There has been no response. It has been in test locally for 2
months now.
May I push the cygport to git and provide a test release?
Upstream has expressed willingness to review/track patches, if
needed.
Good idea to submit patches upstream, as it reduces the number of
patches you have to maintain and rebase, and they may have a better idea
of how to achieve the same goal with more generality having their
knowledge of the package source and build.
Thanks for offering to package and maintain this package, and
apologies for the delay in responding.
Notwithstanding [1] (which needs updating), I look for 2 things
in an ITP: - a statement that the software uses an acceptable
open-source license
GPL v2, mentioned in the above original email.
- the cygport file (as an attachemnt or link) so it can be
reviewed and tested
The attached (with required patch) has been in testing on multiple
windows servers since late July. They can also be reviewed on
github [2].
Using github is an issue for some: gitlab, bitbucket, etc. may or may
not be.
That is why it is a good idea to checkout your repo on a playground
branch, then force push your repo to:
ssh://cyg...@cygwin.com/git/cygwin-packages/playground
and post the jobs.cgi, run, and log links.
You may also add this as another remote e.g. playground to your repo in
your .git/config e.g.:
[remote "playground"]
url = ssh://cyg...@cygwin.com/git/cygwin-packages/playground
fetch = +refs/heads/playground:refs/remotes/playground/*
[branch "playground"]
remote = playground
merge = refs/heads/playground
or equivalent using commands (that I never learned about).
Or copy your cygport, patches, source and both arch build hints and
tarballs, including debuginfo if generated, to a storage site folder,
and post the access link.
If you're still interested in progressing this, please provide the
cygport file for discussion.
[1] https://cygwin.com/packaging-contributors-guide.html#submitting
Interested, very interested. I am on the aide developers list to track updates,
bugs, and
patches.
2: https://github.com/pdinc-oss/aide/tree/cygport
Anyone interested in reviewing? Can I put this out there as a test
package - there are many not on this mailing list that would test but
would not build it.
You should be able to drop the explicit REQUIRES. You only need to
specify those not directly used by the executables, as cygport figures
those out and reports them at the end of your build. You should be
seeing those package names duplicated at the end of your cygport ...
{package,pkg,{,almost}all}{,-test} run e.g.:
>>> aide requires: cygwin libmhash2 libpcre1 zlib0 cygwin libmhash2
libpcre1 zlib0
Please also ensure that the package builds cleanly on both arches.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
RE: [ITP] aide 0.17.3
> -Original Message- > From: Jason Pyeron > Sent: Sunday, October 31, 2021 10:37 AM > > > -Original Message- > > From: Jon Turney > > Sent: Sunday, October 31, 2021 8:48 AM > > > > On 29/09/2021 15:27, Jason Pyeron wrote: > > >> -Original Message- > > >> From: Jason Pyeron > > >> Sent: Friday, July 30, 2021 10:34 AM > > >> > > >> AIDE - Advanced Intrusion Detection Environment > > >> > > >> https://github.com/aide/aide/ > > >> > > >> It is a GPL v2 tool for monitoring file system changes. > > >> > > >> There was no (mature?) Windows open source solution until AIDE was built > > >> and tested for > > >> Cygwin. This fills a long standing gap in needs. > > >> > > >> Closed source alternative - Trip Wire. > > >> > > >> It is packaged and shipped with most Linux distributions - I am most > > >> familiar with the > > >> RHEL packaging. > > >> > > >> I have built and tested the most recent stable and development versions. > > >> > > >> I will track the development versions for test package releases. > > >> > > >> Category Security. > > >> > > >> Thoughts? > > > > > > There has been no response. It has been in test locally for 2 months now. > > > > > > May I push the cygport to git and provide a test release? > > > > > > Upstream has expressed willingness to review/track patches, if needed. > > > > > > > Hi, > > > > Thanks for offering to package and maintain this package, and apologies > > for the delay in responding. > > > > Notwithstanding [1] (which needs updating), I look for 2 things in an ITP: > > > > - a statement that the software uses an acceptable open-source license > > GPL v2, mentioned in the above original email. > > > - the cygport file (as an attachemnt or link) so it can be reviewed and > > tested > > The attached (with required patch) has been in testing on multiple windows > servers since > late July. They can also be reviewed on github [2]. > > > > > If you're still interested in progressing this, please provide the > > cygport file for discussion. > > > > [1] https://cygwin.com/packaging-contributors-guide.html#submitting > > Interested, very interested. I am on the aide developers list to track > updates, bugs, and > patches. > > v/r, > > Jason Pyeron > > 2: https://github.com/pdinc-oss/aide/tree/cygport Anyone interested in reviewing? Can I put this out there as a test package - there are many not on this mailing list that would test but would not build it. -Jason
Re: [ITA] lua-crypto-0.3.2p4
On Tue, 9 Nov 2021 19:17:29 +0100, Marco Atzeri via Cygwin-apps > On 07.11.2021 13:07, Lemures Lemniscati via Cygwin-apps wrote: > > On Sun, 07 Nov 2021 20:46:25 +0900, Lemures Lemniscati > >> On Sat, 23 Oct 2021 19:44:25 +0200, Achim Gratz > >>> > > > > > Hi, > > > > ITA for lua-crypto-0.3.2p4, just because of necessity for rebuilding it > > with libssl1.0. > > > > Regards, > > > > Lem > > > changed to you Thank you, Marco. Lem
