Re: Migration to Subversion complete

Quoting Victor Boctor <vboctor-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>:

> I am not sure I fully understand the problem.  Do we have a problem
> with the encoding of the language files?

I wasn't saying there was a problem - just that that we should be  
aware that it may be a snag.  I haven't personally seen encoding  
issues in migration.

> I don't think I will be re-doing the conversion, so if language files
> are messed up, then we should get the latest from CVS and re-commit
> them in SVN.  I think there was only once check-in for language files
> since migration.

This seems reasonable and easy way to fix it.

As far as the eol style, this is something we ran into when converting  
a java based project from cvs to subversion.  The project tree had  
development platforms that included windows, solaris, os-x, and linux.  
 Shortly after the conversion (but not short enough that we had about  
30 revisions since the migration) did we see that each platform was  
changing the eol on the files respective of their platform, and so  
about 200 files had completely changed (multiple times) after we hit  
our first conflict.  We ended up adding svn:eol-style property with a  
value of native to all text files to solve the issue.

> On Nov 1, 2007 8:08 AM, James Hanley 
> <jhanley-Lfn+8jyDA/ZWk0Htik3J/w@xxxxxxxxxxxxxxxx> wrote:
> > So should work continue in the CVS repo until the kinks associated
> > with migration are worked out with the SVN branch?  I guess this is
> > more of a question to Victor if there are plans to drop the SVN repo
> > and re-convert the CVS.   I know that there can be issues in migration
> > with eol style, and the encoding in your command line brings up an
> > important point about all the language strings file and if those are
> > gracefully handled in the conversion.
> >
> > BTW: I fat fingered the property, so it's actually 4702 that has the
> > correct keyword.
> >
> >
> > Quoting "David A. Desrosiers" <desrod-PoZ5/QCWMfb/2OF+hy8yCA@xxxxxxxxxxxxxxxx>:
> >
> > > On Thu, 2007-11-01 at 10:05 -0400, James Hanley wrote:
> > >> It looks as though the migrations script didn't convert the CVS
> > >> keywords to subversion keywords.
> > >
> > > My cvs2svn (using svn trunk version of cvs2svn, the packaged/distro
> > > versions have some showstopper bugs for large, multi-year repos), looks
> > > like this:
> > >
> > > cvs2svn --fs-type=fsfs --encoding=iso-8859-1 --username=desrod
> > > --cvs-revnums -s /subversion/mantis /cvs/mantis/mantis_src
> > >
> > > Just running it as 'cvs2svn /svn/proj /cvs/proj' is bound to miss a LOT
> > > of critical information you need to migrate in total.
> > >
> > >
> > > --
> > > David A. Desrosiers
> > > desrod-PoZ5/QCWMfb/2OF+hy8yCA@xxxxxxxxxxxxxxxx
> > > setuid-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx
> > > http://projects.plkr.org/
> > > Skype...: 860-967-3820
> > >
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems?  Stop.
> > > Now Search log events and configuration files using AJAX and a browser.
> > > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > > _______________________________________________
> > > mantisbt-dev mailing list
> > > mantisbt-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> > > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
> > >
> > >
> > >
> >
> >
> >
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > mantisbt-dev mailing list
> > mantisbt-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> mantisbt-dev mailing list
> mantisbt-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

binonRK3jaAFc.bin
Description: PGP Public Key

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/_______________________________________________
mantisbt-dev mailing list
mantisbt-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev