| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update:
* Catalyst
* Specify Catalyst::DispatchType::Regex explicitly
* Remove Catalyst::Plugin::Unicode::Encoding
* Catalyst::Plugin::SmartURI
* Specify URI::SmartURI explicitly
* Catalyst::Plugin::Static::Simple
* CGI
* Class::Load
* DateTime
* DateTime::TimeZone
* DBD::Pg
* DBIx::Class
* DBIx::Class::EncodedColumn.
* Email::Address.
* Email::MIME
* ExtUtils::MakeMaker
* ExtUtils::ParseXS (for Params::Classify upgrade)
* File::ChangeNotify
* Image::Size
* IO::Socket::SSL
* local::lib
* Moo
* Moose (and some related others due to deprecations)
* namespace::autoclean
* Net::Server
* Net::SSLeay
* Number::Phone
* Plack
* Starman
* Template
* Test::PostgreSQL
* Test::WWW::Mechanize::Catalyst
* Text::CSV
* YAML
carton install was run on a wheezy box, the oldest that is supported, to
make sure the required minimal vesions of core modules weren't removed
from the snapshot. Cpanel::JSON::XS, Devel::GlobalDestruction::XS, and
MooseX::NonMoose were then put back in the snapshot, in case another
system needs them (e.g. system Perl on Mac looks for MooseX::NonMoose).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Without doing this, a call to e.g. $contact->set_extra_fields(@meta)
in PopulateServiceList.pm, with an unchanged meta that contains some
Unicode values, can write to the database (and cause an unneeded row
in the history table), because the column from the database is UTF-8
decoded, whilst the new text is UTF-8 encoded.
It looks like an attempt was made in filter_from_storage to fix this
issue, but the column comparison for marking a column as dirty takes
place without this being called.
|
