Next | Query returned 102 messages, browsing 61 to 70 | Previous

History of commit frequency

CVS Commit History:


   2004-11-04 15:17:55 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
Changes 1.2.2:
* Eliminate a potential security vulnerability when decoding invalid compressed data
* Fix bug when decompressing dynamic blocks with no distance codes
* Do not return error when using gzread() on an empty file
   2004-10-03 02:13:34 by Todd Vierling | Files touched by this commit (908)
Log message:
Libtool fix for PR pkg/26633, and other issues.  Update libtool to 1.5.10
in the process.  (More information on tech-pkg.)

Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.

Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
   2004-09-22 10:10:08 by Johnny C. Lam | Files touched by this commit (703)
Log message:
Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:

	lib/libfoo.a
	lib/libfoo.la
	lib/libfoo.so
	lib/libfoo.so.0
	lib/libfoo.so.0.1

one simply needs:

	lib/libfoo.la

and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.

Also make LIBTOOLIZE_PLIST default to "yes".
   2004-09-01 01:16:23 by Jeremy C. Reed | Files touched by this commit (5)
Log message:
Added two patches for fixing possible security issue.
The CVS security ID is CAN-2004-0797.

The fix is same as used by OpenBSD, Debian and Gentoo.
(Didn't see any reference to issue on zlib webpages.)

The OpenBSD announcement "zlib reliabilty fix" says:
"could allow an attacker to crash programs linked
with it."

And the Gentoo announcement says "zlib contains a bug in the handling
of errors in the inflate() and inflateBack() functions. ... An
attacker could exploit this vulnerability to launch a Denial of
Service attack on any application using the zlib library."

PKGREVISION is bumped and BUILDLINK_RECOMMENDED.zlib added to
buildlink3.mk file.
   2004-07-07 00:41:17 by Thomas Klausner | Files touched by this commit (30)
Log message:
Unused.
   2004-05-26 05:20:38 by Jan Schaumann | Files touched by this commit (2)
Log message:
Use CFLAGS when creating the archive.  This fixes building under IRIX64
using gcc, as we need the ABI specific flags.
   2004-05-08 03:06:26 by Todd Vierling | Files touched by this commit (3)
Log message:
nb1: install shlib as executable.
   2004-03-29 07:43:36 by Johnny C. Lam | Files touched by this commit (24)
Log message:
Match the template builtin.mk file in bsd.builtin.mk, and make the two
packages that use builtin.mk files (graphics/xpm and pkgtools/x11-links)
use the new format correctly.
   2004-03-12 04:00:24 by Todd Vierling | Files touched by this commit (2)
Log message:
Obey CPPFLAGS.
   2004-03-10 18:57:15 by Johnny C. Lam | Files touched by this commit (46) | Package updated
Log message:
Split out the code that deals with checking whether the software is
built-in or not into a separate builtin.mk file.  The code to deal
checking for built-in software is much simpler to deal with in pkgsrc.

The buildlink3.mk file for a package will be of the usual format
regardless of the package, which makes it simpler for packagers to
update a package.

The builtin.mk file for a package must define a single yes/no variable
USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether
to use the built-in software or to use the pkgsrc software.

Next | Query returned 102 messages, browsing 61 to 70 | Previous