Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
with lang/ruby18-base package.
|
|
Changes:
0.07 Thu Oct 6 02:40:16 UTC 2005
- Fixed test suite for Windows which can't rm files while opening
[cpan #14935]
0.06 Tue Aug 23 22:03:22 UTC 2005
- Now uses SQL::Abstract::Limit to allow limit SQL
(Thanks to David R. Baird)
|
|
|
|
This is security fix:
http://www.ruby-lang.org/en/news/2008/06/20/arbitrary-code-execution-vulnerabilities
Fri Jun 20 18:25:18 2008 Nobuyoshi Nakada <nobu@ruby-lang.org>
* string.c (rb_str_buf_append): should infect.
Fri Jun 20 16:33:09 2008 Nobuyoshi Nakada <nobu@ruby-lang.org>
* array.c (rb_ary_store, rb_ary_splice): not depend on unspecified
behavior at integer overflow.
* string.c (str_buf_cat): ditto.
Wed Jun 18 22:24:46 2008 URABE Shyouhei <shyouhei@ruby-lang.org>
* array.c (ary_new, rb_ary_initialize, rb_ary_store,
rb_ary_aplice, rb_ary_times): integer overflows should be
checked. based on patches from Drew Yao <ayao at apple.com>
fixed CVE-2008-2726
* string.c (rb_str_buf_append): fixed unsafe use of alloca,
which led memory corruption. based on a patch from Drew Yao
<ayao at apple.com> fixed CVE-2008-2726
* sprintf.c (rb_str_format): backported from trunk.
* intern.h: ditto.
Tue Jun 17 15:09:46 2008 Nobuyoshi Nakada <nobu@ruby-lang.org>
* file.c (file_expand_path): no need to expand root path which has no
short file name. [ruby-dev:35095]
Sun Jun 15 19:27:40 2008 Akinori MUSHA <knu@iDaemons.org>
* configure.in: Fix $LOAD_PATH. Properly expand vendor_ruby
directories; submitted by Takahiro Kambe <taca at
back-street.net> in [ruby-dev:35099].
|
|
Update RUBY18_PATCHLEVEL to 22.
|
|
|
|
|
|
Major changes since 1.9.2:
* GSL-1.10 support
* Generalized eigensystems
* Cholesky routines to complex matrices
* and more
* NDLINEAR extension support: multi-linear,
multi-parameter least squares fitting
|
|
file must set the lockfile location, and leave a comment that this
should be merged into the package.
|
|
|
|
|
|
SQL-Abstract-Limit is a portability layer for LIMIT emulation.
|
|
|
|
|
|
Changes since v3.0.14 according to the changelog:
3.0.17 Oct 4, 2007
- Fix t/11 to cope with Class::Trigger no longer supporting multiple
triggers in one shot
3.0.16 Nov 05, 2006
- Better error reporting from has_a setup failure
3.0.15 Aug 19 2006
- Fix ignorage with mutator_name and accessor_name (Ask Bjørn Hansen)
|
|
|
|
|
|
Changes since 1.06 according to the change log:
o PerlCleanupHandler doesn't get called with MP2 (fixed)
o Documentation Additions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fix CVE-2008-1377, CVE-2008-1379, CVE-2008-2360, CVE-2008-2361 and
CVE-2008-2362 based on upstream patches.
|
|
Bump pkg revision.
|
|
|
|
|
|
Make bulkbuild-rebuild over 200 times faster when running against a full
tree scan by using awk to filter out the data instead of the while read
shell builtin.
|
|
|
|
|
|
|
|
* Make pg_get_ruledef() parenthesize negative constants (Tom)
Before this fix, a negative constant in a view or rule might be
dumped as, say, -42::integer, which is subtly incorrect: it should
be (-42)::integer due to operator precedence rules. Usually this
would make little difference, but it could interact with another
recent patch to cause PostgreSQL to reject what had been a valid
"SELECT DISTINCT" view query. Since this could result in pg_dump
output failing to reload, it is being treated as a high-priority
fix. The only released versions in which dump output is actually
incorrect are 8.3.1 and 8.2.7.
* Make "ALTER AGGREGATE ... OWNER TO" update pg_shdepend (Tom)
This oversight could lead to problems if the aggregate was later
involved in a "DROP OWNED" or "REASSIGN OWNED" operation.
|
|
* Make pg_get_ruledef() parenthesize negative constants (Tom)
Before this fix, a negative constant in a view or rule might be
dumped as, say, -42::integer, which is subtly incorrect: it should
be (-42)::integer due to operator precedence rules. Usually this
would make little difference, but it could interact with another
recent patch to cause PostgreSQL to reject what had been a valid
"SELECT DISTINCT" view query. Since this could result in pg_dump
output failing to reload, it is being treated as a high-priority
fix. The only released versions in which dump output is actually
incorrect are 8.3.1 and 8.2.7.
* Make "ALTER AGGREGATE ... OWNER TO" update pg_shdepend (Tom)
This oversight could lead to problems if the aggregate was later
involved in a "DROP OWNED" or "REASSIGN OWNED" operation.
|
|
- Fix typo in configure-replication.sh (missing CR)
- Per bug 35, search the Slony share dir for scripts
before falling back to the PG share dir on 8.0+
- Change test framework to write out the test name into
$TEMPDIR/TestName
- Patch that seems to resolve a race condition with
ACCEPT_SET
- Fix bug 49 - mishandling by slony_logshipper of quotes &
backslashes.
- Fix bug 50 - slony_logshipper had a variable access *after*
memory was freed
Changes 1.2.13:
- Fixed problem with compatibility with PostgreSQL 8.3; function
typenameTypeId() has 3 arguments as of 8.3.
- Added in logic to ensure that max number of SYNCs grouped together is
actually constrained by config parameter sync_group_maxsize.
- Fix to show_slony_configuration - point to proper directory where
slon/slonik are actually installed.
- Fix to slonik Makefile + slonik.c - Change slonik build to query
Postgres for the share directory at runtime - per Dave Page
- Removed spurious NOTIFY on "_%s_Confirm"; this is no longer needed
|
|
* Make pg_get_ruledef() parenthesize negative constants (Tom)
Before this fix, a negative constant in a view or rule might be
dumped as, say, -42::integer, which is subtly incorrect: it should
be (-42)::integer due to operator precedence rules. Usually this
would make little difference, but it could interact with another
recent patch to cause PostgreSQL to reject what had been a valid
"SELECT DISTINCT" view query. Since this could result in pg_dump
output failing to reload, it is being treated as a high-priority
fix. The only released versions in which dump output is actually
incorrect are 8.3.1 and 8.2.7.
* Make "ALTER AGGREGATE ... OWNER TO" update pg_shdepend (Tom)
This oversight could lead to problems if the aggregate was later
involved in a "DROP OWNED" or "REASSIGN OWNED" operation.
|
|
|
|
|
|
New major features:
- Time zones
- Dirty tracking
- Gem Dependencies
- Named scope
- UTC-based migrations
- Better caching
|
|
|
|
Too many changes since 2.0.2. See CHANGELOG for the complete list.
|
|
|
|
Too many changes since 2.0.2. See CHANGELOG for the complete list.
pkgsrc CHANGES:
This version does not depend on ruby-tmail any longer. The dependency
should have been removed when it was switched to use rubygems.
|
|
|
|
Too many changes since 2.0.2. See CHANGELOG for the complete list.
|
|
|