Next | Query returned 102 messages, browsing 91 to 100 | Previous

History of commit frequency

CVS Commit History:


   2003-03-05 14:09:28 by Lubomir Sedlacik | Files touched by this commit (1)
Log message:
Oops, restore NOT_FOR_PLATFORM (commented for my local testing).
   2003-03-05 14:05:45 by Lubomir Sedlacik | Files touched by this commit (6)
Log message:
Added fix for CAN-2003-0107 -
Buffer overflow in the gzprintf function in zlib 1.1.4, when zlib is compiled
without vsnprintf or when long inputs are truncated using vsnprintf, allows
attackers to cause a denial of service or possibly execute arbitrary code.
   2003-03-01 00:29:34 by grant beattie | Files touched by this commit (1)
Log message:
mark Linux zlib as incompatible to avoid using base zlib which can
cause problems with pkgsrc libtool, eg.

libtool: link: AGE `4' is greater than the current interface number `1'
libtool: link: `1:1:4' is not valid version information
libtool: install: `libz.la' is not a valid libtool archive
   2003-03-01 00:25:21 by grant beattie | Files touched by this commit (1)
Log message:
s/LIBTOOL_VERSION/LIBTOOL_REQD/ to register correct dependency.
   2003-02-16 18:33:16 by grant beattie | Files touched by this commit (1)
Log message:
Darwin has no static libz, mark it incompatible.
   2003-02-04 19:48:24 by Johnny C. Lam | Files touched by this commit (1)
Log message:
Create a fake libtool archive so that libtool doesn't get confused since
libz.so exists in the base system, but the package creates a libz.la.
   2002-12-23 21:35:23 by Jan Schaumann | Files touched by this commit (1)
Log message:
IRIX has an old zlib version, so make it use pkgsrc's zlib.
   2002-10-10 14:25:53 by Thomas Klausner | Files touched by this commit (1)
Log message:
Unused.
   2002-09-01 20:45:47 by Johnny C. Lam | Files touched by this commit (1)
Log message:
Mirror the libtool setup in bsd.pkg.mk since we can't use USE_LIBTOOL.
   2002-08-25 20:40:51 by Johnny C. Lam | Files touched by this commit (380)
Log message:
Merge changes in packages from the buildlink2 branch that have
buildlink2.mk files back into the main trunk.  This provides sufficient
buildlink2 infrastructure to start merging other packages from the
buildlink2 branch that have already been converted to use the buildlink2
framework.

Next | Query returned 102 messages, browsing 91 to 100 | Previous