From: Matt B. <ma...@ma...> - 2005-06-22 10:27:23
|
On Wed, 2005-06-22 at 11:24 +0200, Reini Urban wrote: > good, just CVS HEAD would be better. OK. I can do that. > I don't know for Debian, because we don't care for specific distros, but > if the installed system pear DB is too old it is recommended to use ours. > There's no way to check the version number beforehand. pear is not well > designed. Heh, well we'll blame Debian for now and I'll keep my custom include path, that seems to work fine. > This was fixed some weeks ago. Please try current CVS instead or the > nightly snapshot from the webpage. Pleased to confirm CVS HEAD logs to postgres fine. > Oops, I'll check why ACCESS_LOG_SQL=0 fails for you. > This should not happen. Appreciated :) > cached_html is gzipped. > So postgresql has problems with binary data. I'll fix that. Cool. > These are just warnings. Diff merging is not too clever. > You may want to overwrite all or merge manually. > We just provide the basic docs and needed action pages so normally > it's safe to overwrite all. Just the HomePage should be merged. Hmm, they seem like more than warnings. Examples pasted below AFSNotes from MIME file AFSNotes content is identical to current version 1 - no new revision created AFSNotes from MIME file AFSNotes has edit conflicts - skipped Sorry, cannot merge. AFSNotes from MIME file AFSNotes has edit conflicts - skipped Sorry, cannot merge. AFSNotes from MIME file AFSNotes has edit conflicts - skipped Sorry, cannot merge. AFSNotes from MIME file AFSNotes has edit conflicts - skipped Sorry, cannot merge. AFSNotes from MIME file AFSNotes has edit conflicts - skipped Sorry, cannot merge. AFSNotes from MIME file AFSNotes has edit conflicts - skipped Sorry, cannot merge. AFSNotes from MIME file AFSNotes has edit conflicts - skipped Sorry, cannot merge. >From the page history on www.wlug.org.nz/AFSNotes you can see that there are 8 versions currently in the wiki. Exporting to zip dump and then importing into my test wiki only generates the first revision and the errors above. Are you saying that the zip dump method isn't able to import the page history correctly? Is there a better way to do this? I might try a direct database dump / import, but I thought the database fields had changed which might cause problems? Thanks for your help. Kind Regards -- Matt Brown ma...@ma... Mob +64 275 611 544 www.mattb.net.nz |