[Rt-devel] RTFM 2.1.20 development release

[Millard, Matt]

I also had to install YAML module to do the upgrade.  

[root at ul174 RT-FM-2.1.20]# perl -I/rt/rt3.4/lib/
./sbin/migrate-2.0-to-2.1
Can't locate YAML.pm in @INC (@INC contains: /rt/rt3.4/lib/
/usr/local/perl/pfglibs /usr/local/perl/lib/5.8.6/i686-linux
/usr/local/perl/lib/5.8.6 /usr/local/perl/lib/site_perl/5.8.6/i686-linux
/usr/local/perl/lib/site_perl/5.8.6 /usr/local/perl/lib/site_perl .) at
./sbin/migrate-2.0-to-2.1 line 7.
BEGIN failed--compilation aborted at ./sbin/migrate-2.0-to-2.1 line 7.
[root at ul174 RT-FM-2.1.20]# locate YAML.pm
[root at ul174 RT-FM-2.1.20]# locate Yaml.pm
[root at ul174 RT-FM-2.1.20]# perl -MCPAN -e'install YAML'
.
.
.
Writing
//usr/local/perl/lib/site_perl/5.8.6/i686-linux/auto/YAML/.packlist
  /usr/bin/make install -j3 -- OK
[root at ul174 RT-FM-2.1.20]# perl -I/rt/rt3.4/lib/
./sbin/migrate-2.0-to-2.1
Migrating custom field 1: ISIS
  Migrating access control
 It's tied to these classes:
 Migrated core custom field.
 Adding values
 adding classes
Importing articles       Working with article 1
Importing article custom field values
        Importing transaction 1


Deleting access control entries from old fields

Matt 

-----Original Message-----
From: rt-devel-bounces at lists.bestpractical.com
[mailto:rt-devel-bounces at lists.bestpractical.com] On Behalf Of Jesse
Vincent
Sent: Friday, June 03, 2005 12:18 PM
To: rt-devel at lists.bestpractical.com
Subject: [Rt-devel] RTFM 2.1.20 development release

As this is the first widely announced release of this branch of code,
there are likely to be bugs and we certainly want to hear about them. 


-----Message Disclaimer-----

This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect at principal.com and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.

Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act ("E-Sign")
unless a specific statement to the contrary is included in this message.