Age | Commit message (Collapse) | Author | Files | Lines |
|
Problems found with existing distfiles:
distfiles/D6.data.ros.gz
distfiles/cstore0.2.tar.gz
distfiles/data4.tar.gz
distfiles/sphinx-2.2.7-release.tar.gz
No changes made to the cstore or mariadb55-client distinfo files.
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.
|
|
|
|
|
|
|
|
upstream Changes highlights:
- GNU v3 license update
- Buid now uses automake, and code has been adjusted to compile
properly in various environments (tested with gcc 2.95, 3.4, 4.8,
4.9, clang 3.1, 3.4, and several different versions of Linux,
FreeBSD, Solaris, OS X)
- New --global-databases-file command-line option for gnatsd and other programs
- New host/port/user/passwd command-line options for send-pr
- Many bugfixes, including:
- FreeBSD-SA-05:20.cvsbug security advisory (affected send-pr)
- Fixed PR#484: "send-pr --request-id" sends just a template
- Fixed PR#501: Safer open/fopen for gen-index (no longer installing as suid)
- Fixed PR#504: gnatsd crashes when trying to lock a nonexistent PR
- Fixed PR#508: Emacs interface gnats-change-database fails when
gnats-port isn't set
- Fixed PR#691: Portability problem with sed and tr
- Fixed PR#746: install-sid is a bash script (and not /bin/sh)
- Fixed PR#767: edit-pr returns incorect exit status
- Fixed PR#768: make install DESTDIR=/anywhere fails
- Fixed PR#771: "EXPR" queries with spaces sometimes fail
- Fixed PR#773: using responsible alias as email address for edit-pr
- "invalid query format" bug for queries that included whitespace
- edit-pr will now correctly exit with an error if it cannot lock the PR
- edit-pr will now use the email alias in the responsibles field
- Solaris 7/8/10 compilation fixed
|
|
|
|
I have no idea why the extended regexp does not catch the unsetenv declaration
but the check is redundant anyway (there is another unsetenv check below in
configure) so I don't care that much.
|
|
sysutils/user_* packages.
|
|
|
|
|
|
|
|
stop on error.
|
|
Set LICENSE
|
|
|
|
|
|
PR 42330.
|
|
the missing quote -- first half of
2006-06-30 Stephane Chazelas <Stephane@artesyncp.com>
* edit-pr.sh: missing quote on line 172 (it's OK for the
Bourne shell and AT&T ksh based sh, but not other shells), and
the tr syntax, though POSIX is causing trouble with Solaris
tr. Closes: PR#613
|
|
|
|
the owner of all installed files is a non-root user. This change
affects most packages that require special users or groups by making
them use the specified unprivileged user and group instead.
(1) Add two new variables PKG_GROUPS_VARS and PKG_USERS_VARS to
unprivileged.mk. These two variables are lists of other bmake
variables that define package-specific users and groups. Packages
that have user-settable variables for users and groups, e.g. apache
and APACHE_{USER,GROUP}, courier-mta and COURIER_{USER,GROUP},
etc., should list these variables in PKG_USERS_VARS and PKG_GROUPS_VARS
so that unprivileged.mk can know to set them to ${UNPRIVILEGED_USER}
and ${UNPRIVILEGED_GROUP}.
(2) Modify packages to use PKG_GROUPS_VARS and PKG_USERS_VARS.
|
|
|
|
syntax as specified in pkgsrc/mk/install/bsd.pkginstall.mk:1.47.
|
|
* List the info files directly in the PLIST.
|
|
|
|
makeinfo if no native makeinfo executable exists. Honor TEXINFO_REQD
when determining whether the native makeinfo can be used.
* Remove USE_MAKEINFO and replace it with USE_TOOLS+=makeinfo.
* Get rid of all the "split" argument deduction for makeinfo since
the PLIST module already handles varying numbers of split info files
correctly.
NOTE: Platforms that have "makeinfo" in the base system should check
that the makeinfo entries of pkgsrc/mk/tools.${OPSYS}.mk are
correct.
|
|
|
|
automatically detects whether we want the pkginstall machinery to be
used by the package Makefile.
|
|
CONFIGURE_ARGS.
|
|
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2180
Patch by adrianp@.
ChangeLog from gnats CSV:
* Makefile.in (install-gnats-tools, install-gnats-bin): Removed chown
and chmod entries for setting binaries suid. CAN-2005-2180 advisory.
gen-index as setuid root can overwrite any system file.
Bump PKGREVISION to 1.
|
|
Make a overhaul of the package and bring it closer to pkgsrc standards.
Addresses PR 26174 by Hauke Fath.
changes:
This is GNATS 4.1.0, a release that incorporates multiple bug fixes
and enhancements that have been committed to CVS since the release of
GNATS 4.0. Notable enhancements include:
- Upgrade to autoconf 2.59 generated configure scripts.
- New PR numbers are reported to the client upon new submissions
- Rewrite of install-sid. Now, rather than editing send-pr, which can
be installed on a read-only partition, install-sid creates or edits
user or site configuration files ~/.send-pr.conf or
/etc/gnats/send-pr.conf.
- Removal of libiberty, old manpages, and old build framework cruft
- Performance enhancements to indexing code
- Various cleanups and bugfixes. See the ChangeLog files for details.
|
|
backslashes anymore. A single backslash is enough. Changed the
definition in all affected packages. For those that are not caught, an
additional check is placed into bsd.pkginstall.mk.
|
|
that these directories will be conditionally removed (based on reference
counts), regardless of the value of PKG_CONFIG. Bump the PKGREVISION
for packages that were modified as a result.
|
|
USE_GNU_TOOLS -> USE_TOOLS
awk -> gawk
m4 -> gm4
make -> gmake
sed -> gsed
yacc -> bison
|
|
|
|
|
|
Fixes vulnerabilities described in
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0623 .
|
|
problems and is no longer supported.
|
|
|
|
|
|
|
|
Also dynamically handle the send-pr.info* files in ${PREFIX}/share/gnats/dist
|
|
|
|
|
|
|
|
|
|
Noted by Katsuhiko Fujii in PR 21832.
|
|
Should anybody feel like they could be the maintainer for any of thewe packages,
please adjust.
|
|
some directories. In the process kill PLIST @exec -except for those related
to install-info.
While here substitute some leftover `/usr/pkg' in MESSAGE.
XXX Marking this package as USE_BUILDLINK2 will make my life easier
for forthcoming changes but as it is not really necessary for the build
it self I guess it is not a good option?
|
|
|
|
Remove information that is in MESSAGE.
|
|
|