Hello fellow developers, this is the read-only reminder for the monotone 0.27 migration which is going to happen next week. The OE monotone repositories at Vanille.de will go READ ONLY at
0:00 MET. That is in ~9 hours from now. The OE repository at Ewi went read only already and the nslu2 repositories will follow soon as well. Please commit all your pending changesets. Sidenote: As alread announced, in order to unify all services to be hosted at openembedded.org, we will transfer the repository from vanille.de to openembedded.org. After the repository migration, we will also move the mailing lists [email protected] and [EMAIL PROTECTED] to openembedded.org. You won't have to do anything to make this happen except perhaps adjust your filter rules and post to the new list addresses which will be announced shortly. For more information, please consult http://www.openembedded.org/announcement-of-scm-conversion-to-monotone-0.27 and http://www.openembedded.org/wiki/OpenEmbeddedMigration The original announcement: I'm glad to announce that we will start the monotone migration to monotone 0.26+. Monotone 0.26 introduced many changes which makes it incompatible with earlier releases. This means once we converted to monotone 0.26 earlier versions of monotone will not be able to connect to our main servers and monotone 0.26 can not operate on earlier databases (only convert them). We do this conversation because monotone 0.26+ is better in all aspects, most noticable is the speed difference. Accompanied with the monotone conversation is the death of monotone.vanille.de and we will be glad to establish monotone.openembedded.org server as our main repository. What does this mean to the random OpenEmbedded developer: You will need to push your changes before the main repository will be marked as read-only. If you use monotone 0.24 you should get monotone 0.25 to extract your keys from the database. After the conversion you will need monotone 0.26+ to do a fresh pull. And make sure you will not lose your private key! What does this mean to the people having local changes (e.g. branches) that can not or should not be pushed: You will need to do the same conversation we will do on the servers. The OpenEmbedded team will provide documentation and some tools for your assistance to ease this operation. If needed/wished people of the OpenEmbedded team can do the transformation for you (at your wish). More about this at the bottom of this mail and in following up mails. Schedule: 2006-06-17 Announce the begin of the process to the MailingList, Wiki and other sources. To give the possibility to sync work into their database. 2006-06-24 ReAnnounce the migration 2006-07-01 ReReAnnounce the migration 2006-07-08 Get Monotone from the preferred source (release, snapshot) and place it in the special directory 2006-07-08 Compile and run the suite (make check) and only proceed if all tests are passed. and place it in the special directory 2006-07-13 Announce that we will go read only on monday 2006-07-17 Upload the OE_0_25.mtn to a special directory 2006-07-17 Save the complete list of revisions, messages 2006-07-17 Start the rosterify on two machines 2006-07-18 Compare the result of the two runs (revisions) done by a script 2006-07-18 Compare the result with the OE_0_25.mtn (#revs, logs, diffs) done by a script 2006-07-18 Check out each and every revision of the OE database done by a script 2006-07-19 Install viewmtn which can work with mtn0.26+ on the servers 2006-07-19 Update the server install of mtn0.26+, update mail hooks if necessary 2006-07-20 Open service for a selected amount of devs (read only) to do an initial pull 2006-07-21 Publish OE_0_26+.mtn in the special directory. 2006-07-21 Open service for every contributor ISV/Vendor Branches Migration: If you are a monotone user with local branches or local commits this section is targeted for you. You are asked to synchronize with the latest version from ewi or vanille when we turn them read only. Then make a backup or two of your database. Copy the database to a temporary directory. Get monotone 0.26+ from the special directory either use the binary or compile your own version. Meanwhile you could run db check on the old database (this will take some time). Once you have compiled mtn consider running make check as well. Now you will need to migrate the database as well. mtn --db OE_copy_of_your_db.mtn db migrate mtn --db OE_copy_of_your_db.mtn db rosterify Now you should have a Database that is almost the same. Run the script to compare the rev. A list of not common revs (addiotnally) should be printed. They should be the ones you have created. Please go through each revision and try to remember it. The next step will be done by a script. Basicly all common revisions will be removed from your database. The list of the common revisions will be stored in the special directory. Finally the script will set common epochs for you. The last task is pulling the revisions from the main OpenEmbedded server once available. _______________________________________________ Oe mailing list [email protected] https://www.handhelds.org/mailman/listinfo/oe -- Regards, Michael 'Mickey' Lauer | FreeLancer | http://www.Vanille-Media.de _______________________________________________ Oe mailing list [email protected] https://www.handhelds.org/mailman/listinfo/oe
