Where is FreeBSD going?
lev at FreeBSD.org
Fri Jan 9 07:15:49 PST 2004
Friday, January 9, 2004, 4:28:57 PM, you wrote:
>> DR> 3. Converting the repository. This is a tricky one - I tried the
>> DR> current version of the migration scripts and they barfed and died
>> DR> pretty quickly. Still, I'm pretty sure that the svn developers
>> DR> are planning to fix most of those problems. From mailing-list
>> DR> archives, it appears that they are using our cvs tree as test
>> DR> material for the migration scripts.
>> Did you try my (pure-perl) vatinat ``RefineCVS''?
>> But, please, read documentation carefully before reporting bugs --
>> many errors could be avoided with command-line options, sctipy is
>> paranoid by default.
>> Some parts of FreeBSD repository could not be converted, because
>> contains revisions like 1.2.1 and other `I don't know what I should
>> think about this' errors. If you have some good ideas -- let me know
N> Huh? Whats wrong with revision 1.2.1 ? This is perfectly normal cvs
N> revision number, even if you have to use a command line option to get it.
N> But it should not require any kind of special treatment.
It is NOT perfectly normal cvs revision number. WHAT TYPE of
revision number is it?
Normal numbers are (first level of branching is showed only):
x.y -- TRUNK
x.y.0.(2n) -- MAGIC for branch (in SYMBOLS only)
x.y.(2n).z -- Revision on branch
x.1.(2n+1) -- Vendor branches (in SYMBOLS only)
x.1.(2n+1).z -- Vendor imports
Ok, ok, it should be some broken vendor branch. But what do you say
about `1.1.2'? Or even simple `1' (look into sysintall's Attic).
BTW, repo from FreeBSD 4.9 is parsed almost without such errors
(sysinstall, pppd + kernel part of ppp, zoneinfo).
Some problems are with double symbols (one symbolic name marks two
revisions: MAGIC one and simple one), and with symbols, which marks
unexistent revisions (many, many such symbols over all repository).
But my computer doesn't have enough memory to finish conversion process.
More information about the freebsd-hackers