Elfyn McBratney <[EMAIL PROTECTED]> tapota : > On Fri, Jul 02, 2004 at 12:20:32PM +0200, Mathieu Roy wrote: >> Elfyn McBratney <[EMAIL PROTECTED]> tapota : >> >> > Hello, >> > >> > I've been really busy with work and my Savannah commitments lately, so >> > much so that I've neglected the work I've been doing on Savane, and >> > this list (which had been going to another account). >> > >> > I'm really sorry about that :( >> > >> > OK, back to why I'm here.. There's a patch in the bug tracker which >> > fixes a string format error[1]. And I'd also like to try and solicit >> > help for a Savannah CERN -> Savane 1.0.3 migration (savannah.gnu.org). >> > >> > Can anyone offer any advice, wisdom or migration scripts? 8) >> > >> >> The CERN moved several servers lately, including the CVS one where the >> scripts were included. >> >> I will make them available in savane/update/before1.0.0 as soon as >> I get them.
The CERN migration scripts are now in <http://cvs.gna.org/viewcvs/savane/savane/update/1.0.0/> To understand how to handle them, read the README file. They proved to work at Savannah and at CERN, so they can be trusted. But in fact, after re-reading your mail, I understand that you'd like a way to migrate from Savannah CERN Branch to Savane 1.0.3. In this case, you have nothing specific to do apart from - update the files - run the sql scripts of update/1.0.3 with in fact do only cosmetics changes There is a specific problem with the installation of Savane CERN branch (pre 1.0.0) and the update: changes have been made by people of the FSF USA they did not document, explain, and ask inclusion within Savane. Moreover, as far I read, they made changes that cannot be accepted within the tree without being rewritten: the changes made in the code are specific to their installation and it is not of interest ot Savane to include site-specific changes within the code. It was possible to make these changes in a configurable way (and do so without extra work) but the people that made these changes never sent a line to Savane developers asking for specific assistance or mentioning what they were planning to do. To handle such upgrade, you should ask to the people that made the changes to list their changes, explain their changes, and discuss on savane-dev how such changes could be included in Savane. Or you could determine for yourself what changes have been made, by downloading a copy of the branch DEV CERN of Savane and running diff with the copy that is running. Regards, -- Mathieu Roy +---------------------------------------------------------------------+ | General Homepage: http://yeupou.coleumes.org/ | | Computing Homepage: http://alberich.coleumes.org/ | | Not a native english speaker: | | http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english | +---------------------------------------------------------------------+
