All checksums have been double-checked against existing RMD160 and
SHA512 hashes
Unfetchable distfiles (fetched conditionally?):
./security/cyrus-sasl/distinfo cyrus-sasl-dedad73e5e7a75d01a5f3d5a6702ab8ccd2ff40d.patch.v2
Problems found locating distfiles:
Package f-prot-antivirus6-fs-bin: missing distfile fp-NetBSD.x86.32-fs-6.2.3.tar.gz
Package f-prot-antivirus6-ws-bin: missing distfile fp-NetBSD.x86.32-ws-6.2.3.tar.gz
Package libidea: missing distfile libidea-0.8.2b.tar.gz
Package openssh: missing distfile openssh-7.1p1-hpn-20150822.diff.bz2
Package uvscan: missing distfile vlp4510e.tar.Z
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
However (because of -DTW_TYPE32='int' being added to CFLAGS for an LP64 fix
in revision 1.3 of patches/patch-aa) uint32 is defined as an unsigned int.
This caused two problems:
1) The format string in include/tripwire.h was not updated to match.
2) On NetBSD, off_t is __int64_t.
I am changing the format string in tripwire.h to match uint32. I also
changed the type of the variable "size" from uint32 to off_t, and changed
its format string to match intmax_t.
This fixes the sparc64 coredump mentioned in PR 19391.
for download.
I changed MASTER_SITES to match FreeBSD's ports/security/tripwire12.
I verified that the contents of these files are identical using cmp.
The Darwin compile time configuration is easy to write, but I don't have a
Darwin box handy, and so the tw.conf.darwin is a bit difficult to write as
there tend to be a few non-standard paths.
In response to PR 22362.
Remove `-p' from mkdir arguments, it is already part of ${MKDIR}.
While here substitute a couple of ${PREFIX} by `%D' in
`@exec ${MKDIR} ...' lines and add a couple of missing `%D' in such lines too!
