| Age | Commit message (Collapse) | Author | Files | Lines |
|
databases/phpmyadmin security update
Revisions pulled up:
- databases/phpmyadmin/Makefile 1.97-1.98
- databases/phpmyadmin/PLIST 1.25
- databases/phpmyadmin/distinfo 1.58-1.59
---
Module Name: pkgsrc
Committed By: tron
Date: Thu Feb 16 20:19:25 UTC 2012
Modified Files:
pkgsrc/databases/phpmyadmin: Makefile PLIST distinfo
Log Message:
Update "phpmyadmin" package to version 3.4.10. Changes since 3.4.9:
- bug #3460090 [interface] TextareaAutoSelect feature broken
- patch #3375984 [export] PHP Array export might generate invalid php code
- bug #3049209 [import] Import from ODS ignores cell that is the same as
cell before
- bug #3463933 [display] SELECT DISTINCT displays wrong total records found
- patch #3458944 [operations] copy table data missing
SET SQL_MODE='NO_AUTO_VALUE_ON_ZERO'
- bug #3469254 [edit] Setting data to NULL and drop-downs
- bug #3477063 [edit] Missing set fields and values in generated INSERT query
- bug #3460867 [libraries] license issue with TCPDF (updated to 5.9.145)
---
Module Name: pkgsrc
Committed By: tron
Date: Sat Feb 18 23:04:45 UTC 2012
Modified Files:
pkgsrc/databases/phpmyadmin: Makefile distinfo
Log Message:
pdatep "phpmyadmin" package to version 3.4.10.1. Changes since 3.4.10:
- [security] XSS in replication setup, see PMASA-2012-1
|
|
functions. Update that, don't declare own sys_errlist. Fixes Linux build.
PKGREVISION -> 2 as a precaution.
|
|
|
|
errors because of USE_BUILTIN.gdbm usage.
|
|
|
|
Postgresql upstream does not use libtool. pkgsrc used to change
postgresql to use libtool, and this package was written to use the
pkgsrc-added libtool support. pkgsrc no longer modifies postgresql to
use libtool, so postgis did not build.
In addition to backing out all the make-postgis-use-libtool packages,
this commit adds a patch to add rpath to the PGSQL_FE_LDFLAGS, which
upstream hand constructs from pg_config output.
PKGREVISION++, but no change in version or functionality (from the
previous state, which also didn't build) intended.
|
|
0.9.12
-----
* On windows, the default ldap library became wldap32;
* Fixed compile with ruby 1.9.2.
Thank to Hiroki Najima!
* Fixed many memory leaks;
* Added functions:
LDAP::Conn.open_uri(uri);
LDAP::explode_dn(dn, notypes);
LDAP::explode_rdn(rdn, notypes).
Thanks to Marek Veber and Antonio Terceiro!
* Fixed bug in ldap/ldif.rb (GH-6).
Thanks to bbense.
* Fixed LDAP::Mod data corruption.
Thanks to Aprotim Sanyal!
* Enable client certificate authentication for mozilla ldap 6.0 only.
Thanks to Yuri Arabadji!
|
|
|
|
|
|
|
|
- bug #3442028 [edit] Inline editing enum fields with null shows
no dropdown
- bug #3442004 [interface] DB suggestion not correct for user with
underscore
- bug #3438420 [core] Magic quotes removed in PHP 5.4
- bug #3398788 [session] No feedback when result is empty
(signon auth_type)
- bug #3384035 [display] Problems regarding ShowTooltipAliasTB
- bug #3306875 [edit] Can't rename a database that contains views
- bug #3452506 [edit] Unable to move tables with triggers
- bug #3449659 [navi] Fast filter broken with table tree
- bug #3448485 [GUI] Firefox favicon frameset regression
- [core] Better compatibility with mysql extension
- [security] Self-XSS on export options (export server/database/table),
see PMASA-2011-20
- [security] Self-XSS in setup (host parameter), see PMASA-2011-19
|
|
|
|
While here, fix some pkglint.
|
|
|
|
Changes:
* Support SpiderMonkey 1.8.5
* Add configurable maximum to the number of bytes returned by _log.
* Allow CommonJS modules to be an empty string.
* Bump minimum Erlang version to R13B02.
* Do not run deleted validate_doc_update functions.
* ETags for views include current sequence if include_docs=true.
* Fix bug where duplicates can appear in _changes feed.
* Fix bug where update handlers break after conflict resolution.
* Fix bug with _replicator where include "filter" could crash couch.
* Fix crashes when compacting large views.
* Fix file descriptor leak in _log
* Fix missing revisions in _changes?style=all_docs.
* Improve handling of compaction at max_dbs_open limit.
* JSONP responses now send "text/javascript" for Content-Type.
* Link to ICU 4.2 on Windows.
* Permit forward slashes in path to update functions.
* Reap couchjs processes that hit reduce_overflow error.
* Status code can be specified in update handlers.
* Support provides() in show functions.
* _view_cleanup when ddoc has no views now removes all index files.
* max_replication_retry_count now supports "infinity".
* Fix replication crash when source database has a document with empty ID.
* Fix deadlock when assigning couchjs processes to serve requests.
* Fixes to the document multipart PUT API.
* Fixes regarding file descriptor leaks for databases with views.
|
|
Adapt for db4 update post 4.5.
Now dies with segfault during build:
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::substr
[1] Abort trap (core dumped) ./cstoreqptest 0...
|
|
Depends on Ruby on Rails 3 and here is CHANGELOG although it would not
be complete one.
* (16 Jun 2008) Backwards Compatibility is overrated (big updates for rails 2.1)
* Use ActiveRecord 2.1's dirty attribute checking instead [Asa Calow]
* Remove last traces of #non_versioned_fields
* Remove AR::Base.find_version and AR::Base.find_versions, rely on AR association proxies and named_scope
* Remove #versions_count, rely on AR association counter caching.
* Remove #versioned_attributes, basically the same as AR::Base.versioned_columns
* (5 Oct 2006) Allow customization of #versions association options [Dan Peterson]
*0.5.1*
* (8 Aug 2006) Versioned models now belong to the unversioned model. @article_version.article.class => Article [Aslak Hellesoy]
*0.5* # do versions even matter for plugins?
* (21 Apr 2006) Added without_locking and without_revision methods.
Foo.without_revision do
@foo.update_attributes ...
end
*0.4*
* (28 March 2006) Rename non_versioned_fields to non_versioned_columns (old one is kept for compatibility).
* (28 March 2006) Made explicit documentation note that string column names are required for non_versioned_columns.
*0.3.1*
* (7 Jan 2006) explicitly set :foreign_key option for the versioned model's belongs_to assocation for STI [Caged]
* (7 Jan 2006) added tests to prove has_many :through joins work
*0.3*
* (2 Jan 2006) added ability to share a mixin with versioned class
* (2 Jan 2006) changed the dynamic version model to MyModel::Version
*0.2.4*
* (27 Nov 2005) added note about possible destructive behavior of if_changed? [Michael Schuerig]
|
|
|
|
explicitly.
Bump PKGREVISION.
|
|
|
|
databases/ruby-acts-as-versioned02.
|
|
ruby-dm-cli, ruby-dm-ferret-adapter, ruby-dm-is-list, ruby-dm-is-nested_set,
ruby-dm-is-remixable, ruby-dm-is-searchable, ruby-dm-is-state_machine,
ruby-dm-is-tree, ruby-dm-is-versioned, ruby-dm-mysql-adapter,
ruby-dm-observer, ruby-dm-postgres-adapter, ruby-dm-rest-adapter,
ruby-dm-sqlite-adapter, ruby-dm-sweatshop, ruby-dm-tags, ruby-dm-yaml-adapter,
ruby-dm-active_model and ruby-dm-rails.
|
|
Dm-rails provides the railtie that allows datamapper to hook into rails3 and
thus behave like a rails framework component. Just like activerecord does in
rails, dm-rails uses the railtie API to hook into rails. The two are actually
hooked into rails almost identically.
Creating new datamapper apps on rails3 from scratch is actually really easy.
The following will guide you through the process.
|
|
This plugin makes datamapper compliant with active_model conventions and thus
compatible with rails3.
|
|
YAML Adapter for DataMapper.
|
|
This package brings tagging to DataMapper. It is inspired by Acts As Taggable
On by Michael Bleigh, github's mbleigh. Props to him for the contextual
tagging based on Acts As Taggable on Steroids.
== Features and Problems
=== Features
* Contextual tagging using Model.has_tags_on (see below for usage)
* Traditional 'tags-only' tagging using Model.has_tags
=== Problems
* None known yet, but this is very alpha software. Sorry if it misbehaves.
Please send me a github message if you find a bug.
|
|
dm-sweatshop is a model factory for DataMapper. It makes it easy & painless
to crank out complex pseudo random models -- useful for tests and seed data.
Production Goals:
* Easy generation of random models with data that fits the application domain.
* Simple syntax for declaring and generating model patterns.
* Add context to model patterns, allowing grouping and
* Effortlessly generate or fill in associations for creating complex models
with few lines of code.
|
|
Sqlite3 Adapter for DataMapper.
|
|
A DataMapper adapter for REST Web Services.
|
|
PostgreSQL Adapter for DataMapper.
|
|
DataMapper::Observer allows you to add callback hooks to many models. This is
similar to observers in ActiveRecord.
|
|
A MySQL Adapter for DataMapper.
|
|
DataMapper plugin enabling <b>simple</b> versioning of models.
When a model is versioned, and updated, instead of the previous version being
lost in the mists of time, it is saved in a subsidiary table, so that it can
be restored later if needed.
Please Note! this gem behaves differently to how AR's :acts_as_versioned
works. There is currently no multi version storage possible.
|
|
DataMapper plugin enabling easy creation of tree structures from your DM models.
This requires a foreign key property for your model, which by default would be
called :parent_id.
|
|
DataMapper plugin that adds state machine functionality to your models.
== Why is this plugin useful?
Your DataMapper resource might benefit from a state machine if it:
* has different "modes" of operation
* has discrete behaviors
* especially if the behaviors are mutually exclusive
And you want a clean, high-level way of describing these modes / behaviors
and how the resource moves between them. This plugin allows you to
declaratively describe the states and transitions involved.
|
|
A DataMapper search plugin api to search for resources from one repository and
load from another.
Typically a full text search adapter that can only produce partial resources is
searched and the resulting resource collection is then loaded from your default
repository.
|
|
DataMapper::Is::Remixable allows you to create re-usable chunks of relational
data, its kind of like multiple inheritance for models.
|
|
DataMapper plugin allowing the creation of nested sets from data models.
Provides all the same functionality as dm-is-tree, plus tons more! Read on.
== What is a nested set?
Nested set is a clever model for storing hierarchical data in a flat table.
Instead of (only) storing the id of the parent on each node, a nested set puts
all nodes in a clever structure (see Example below). That is what makes it
possible to get the all of the descendants (not only immediate children),
ancestors, or siblings, in one single query to the database.
The only downside to nested sets (compared to trees] is that the queries it
takes to know these things, and to move nodes around in the tree are rather
complex. That is what this plugin takes care of (+ lots of other neat stuff)!
Nested sets are a good choice for most kinds of ordered trees with more than
two levels of nesting. Very good for menus, categories, and threaded posts.
|
|
DataMapper plugin for creating and organizing lists.
|
|
This is a DataMapper plugin for Ferret.
|
|
DataMapper plugin allowing interaction with models through a Command-Line
Interface (CLI).
|
|
DataMapper plugin providing ActiveRecord-style finders.
|
|
A DataObjects Adapter for DataMapper.
|
|
DataMapper plugin providing methods to increment and decrement properties.
|
|
|
|
A PostgreSQL driver for DataObjects.
This driver implements the DataObjects API for the PostgreSQL relational
database.
|
|
A MySQL driver for DataObjects.
This driver implements the DataObjects API for the MySQL relational database.
|
|
Drop ${PHP_BASE_VARS} from PKGVERSION by default.
It used to be required to support multiple php version.
But after PHP version based ${PHP_PKG_PREFIX} was introduced,
such trick is not required anymore.
In addition to this, such version name schme invokes unwanted version bump
when base php version is bumped, plus, such version scheme is hard to
use for DEPENDS pattern.
To avoid downgrading of package using such legacy version scheme,
PECL_LEGACY_VERSION_SCHEME is introduced.
If it is defined, current version scheme is still used for currently
supported PHP version (5 and 53), but instead of ${PHP_BASE_VARS},
current fixed PHP base version in pkgsrc is used to avoid unwanted version bump
from update of PHP base package.
With newer PHP (54, or so on), new version scheme will be used if
it is defined.
This trick will not be required and should be removed after php5 and php53 will
be gone away from pkgsrc.
|
|
## 0.10.7 2011-10-13
* Ruby 1.9.3 compatibility
|
|
## 0.10.7 2011-10-13
* Ruby 1.9.3 compatibility
|