public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] aide 0.17.3
Date: Wed, 29 Sep 2021 18:07:38 -0600	[thread overview]
Message-ID: <04164f98-3eb7-9d68-e154-d8ffd0abb699@SystematicSw.ab.ca> (raw)
In-Reply-To: <067001d7b53e$24465d70$6cd31850$@pdinc.us>

On 2021-09-29 08: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?

Good idea for those in commercial or exposed environments.

> 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.

Normally you provide a link to a net location holding copies of the 
package cygport and any patches, source package tarball and hint, binary 
package tarballs and hints for both arches.

Now you can also add those to a local package git repo playground 
branch, and force push it to the playground branch of remote repo
ssh://cygwin@cygwin.com/git/cygwin-packages/playground and provide links 
to the CI job:

	https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=playground

and scallywag run logs:

	https://github.com/cygwin/scallywag/actions/runs/...

Have a look at my recent submissions for an idea of what is expected, 
and feel free to reply with comments and hopefully a +1! ;^>

-- 
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.]

  reply	other threads:[~2021-09-30  0:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 14:34 Jason Pyeron
2021-09-29 14:27 ` Jason Pyeron
2021-09-30  0:07   ` Brian Inglis [this message]
2021-10-31 12:47   ` Jon Turney
2021-10-31 14:37     ` Jason Pyeron
2021-11-10 12:33       ` Jason Pyeron
2021-11-10 16:24         ` Brian Inglis
2021-11-12 12:48           ` Jason Pyeron
2021-11-12 16:49             ` Brian Inglis
2021-11-14  1:37               ` Jason Pyeron
2021-11-14  8:10                 ` ASSI
2021-11-14 14:39                   ` [PATCH} cygport src_fetch.cygpart PATCH_URI doc addition Brian Inglis
2021-11-14 12:49       ` [ITP] aide 0.17.3 Jon Turney
2021-11-14 16:36         ` Jason Pyeron
2021-11-14 17:00           ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=04164f98-3eb7-9d68-e154-d8ffd0abb699@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).