Re: [leaf-devel] Re: CVS problem
On Wed, 2006-04-12 at 20:32, Charles Steinkuehler wrote: Mike Noyes wrote: The SF staff indicates CVS will coexist with SVN for the foreseeable future. Natanael Copa expressed interest in using SVN for Alpine, and the Bering-uClibc team is concerned about buildtool. I enabled SVN, so it is available, but I'm not sure how we proceed from here. We can migrate the existing CVS stuff over to subversion all at once, a project/directory at a time, or kicking and screaming once SF shuts down CVS for good (whenever that might be)...although this depends somewhat on what processes the SF staff makes available. On Tue, 2006-02-21 at 10:32, Mike Noyes wrote: Importing Data into SVN http://sourceforge.net/docs/E09#import With a local copy of the CVS archive and subversion access, it should be possible to convert any/all of our CVS content at our own pace. Agreed. :-) Regardless, it sounds like it's worth setting up a rolling backup script for the CVS archives, and it would probably be good to look into backing up our SF subversion repository. Thanks Charles. If there is anything I can do to help, please let me know. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Flash Stick Image
Hi Jorn; any success building a new image? kp Am Montag, 3. April 2006 20:48 schrieb KP Kirchdoerfer: Jorn; Am Montag, 3. April 2006 20:41 schrieb Jorn Eriksen: KP All, Did you format from Windows? Nop - Debian Sarge 2.6 kernel with msdos,fat vfat modules loaded I guess it got to late yesterday. Looking trough my notes I saw that I forgott to format it with mkfs.vfat mkdir /hd mount -t vfat /dev/sda1 /hd touch thisisatestwithreallylongfilenames.txt works fine with my image now. I have also changed the syslinux.cfg entries to /dev/sda1:vfat But, I can not get long file names with lrcfg :-( What do you test with lrcfg?? I just check on CLI. And real testcase IMHO will be modules.conf with the enhancements to load from sda... Maybe I just do this to late in the evening. I'll roll another image tomorrow morning - hopefully I get all stuff ironed out then. I guess the reformat will take care of the umbunto issue as well. Sounds good, will test again :) kp --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Re: CVS problem
On Tue, 2006-04-11 at 17:29, Mike Noyes wrote: The directories/modules below still need verification. Everyone, I'll wait until Mon. before contacting the SF staff regarding our repository corruption. The directories/modules listed below have until then to complete verification. Thanks. On Tue, 2006-04-11 at 13:17, Mike Noyes wrote: The following is a list of directories that differ: leaf/bin/bering-uclibc/ leaf/bin/config/webconf/ leaf/bin/lince/ four files leaf/bin/packages/uclibc-0.9/ subdirectory 20/ verified leaf/devel/espakman/one file usbfile.gz leaf/devel/freat/ leaf/devel/hejl/ leaf/devel/jjprieto/Attic/ one file lince.iso.bz2 leaf/devel/nangel/ leaf/devel/pstraina/ -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
bering-uclibc and cvs usage [was: Re: [leaf-devel] Re: CVS problem]
Am Mittwoch, 12. April 2006 19:22 schrieb Mike Noyes: On Wed, 2006-04-12 at 06:44, Charles Steinkuehler wrote: QUESTION: What's the status of the SF CVS archive in terms of how long it's going to continue to be in use? If everything is going into subversion soon, I'm not going to mess with generating rotating backups of the CVS repository, but if the CVS stuff is going to stay in production for a while, it's probably worth it. Charles, The SF staff indicates CVS will coexist with SVN for the foreseeable future. Natanael Copa expressed interest in using SVN for Alpine, and the Bering-uClibc team is concerned about buildtool. I enabled SVN, so it is available, but I'm not sure how we proceed from here. The Bering-uClibc team does work intensivly with cvs: - Everyone shall be able to build a developement environment and the lrpS from cvs sources. - contributions can be added almost automatically from every LEAF developer via cvs - the Bering-uClibc packages page is heavily based on cvs access. We do need a working cvs being around for some more time :) kp --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: bering-uclibc and cvs usage [was: Re: [leaf-devel] Re: CVS problem]
Hi kp, The Bering-uClibc team does work intensivly with cvs: - Everyone shall be able to build a developement environment and the lrpS from cvs sources. - contributions can be added almost automatically from every LEAF developer via cvs - the Bering-uClibc packages page is heavily based on cvs access. We do need a working cvs being around for some more time :) looking at how much work it _might_ be (I don't know for sure, and I don't have the time to find out - if somebody else wants to have a look at it, [s]he is more than welcome to do so) it's actually worse than that. My take is that changing everything to a different CVS server (should SF pull CVS support at some point) would most likely be easier than switching to subversion. That's just my take though - switching to another CVS server is a configuration change, that's easily tested. Switching to subversion is a big unknown to me, and at this point, I neither have the time, nor much of an inclination to spend time on porting all our stuff to subversion. To me, a port would bring tons of extra work, without much of a gain. Subversion might be more stable than CVS is on SF right now (there's no debating the problems SF has had with CVS in the past), but that's the only gain I see - all the other things that subversion undoubtedly brings are not terribly high on my priorities list at this point in time, since the lack of them doesn't keep me from doing what I need to do (binary diffs, versioning of directories, renaming of files, true atomic commits are all fine features, but no killer features to _me_ at this point, given the amount of work it seems it would take to switch). Again - if there's somebody familiar with perl, CVS and subversion, who wants to port buildtool and genpage, they're more than welcome to do so (and I'd do my best to help as much as I can). Martin P.S. In case somebody is wondering - I'm _NOT_ threatening to move away from SF and create a fork of LEAF on some other site. I'm just saying that at this point, there seems to be nobody available to do the work required to move from CVS to subversion, so migrating to another repository would seem easier than migrating to another SCM, if we are forced to make a decision. And before anybody blames CVS for the current problems, as far as I can tell, subversion would have taken as much of a hit from a filesystem corruption as CVS. I guess if there's something we can learn from this, it's not to rely on SF services without a good backup (and there's nobody to blame for that but all of us, myself included - SF never claimed to keep backups, as far as I recall). --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: bering-uclibc and cvs usage [was: Re: [leaf-devel] Re: CVS problem]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Hejl wrote: Again - if there's somebody familiar with perl, CVS and subversion, who wants to port buildtool and genpage, they're more than welcome to do so (and I'd do my best to help as much as I can). Subversion can generally be used as a 'superset' of CVS, and quite a bit of the command line is identical, particularly for the common uses you've probably got coded into your tools (ie: checkout, update, commit), so converting could be as simple as substituting svn for cvs (unless you're using some perl module to directly access CVS w/o using the command-line client). I'm sure there's also a 'wrapper' script available somewhere for most of the less common usages. ...of course, even if the conversion is easy, everything takes some work, and usually more time (especially regression testing!)... P.S. In case somebody is wondering - I'm _NOT_ threatening to move away from SF and create a fork of LEAF on some other site. I'm just saying that at this point, there seems to be nobody available to do the work required to move from CVS to subversion, so migrating to another repository would seem easier than migrating to another SCM, if we are forced to make a decision. Yeah, that's why I figure it's worth it to start keeping a backup rotation of our CVS directory from SF. I'm sure we'll eventually migrate to subversion, but it probably won't be until some critical need forces the issue. :) NOTE: I have overseen the conversion of a very large CVS archive into subversion (the source code for a commercial 3D graphics package), and it's fairly painless using the automated scripts provided with subversion for that purpose. So at least that part *SHOULD* be easy. :) - -- Charles Steinkuehler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEPsaILywbqEHdNFwRAhdvAKCqLElKeeaC/Hs9e4+HYOMiSXv57ACg+Mt+ EVlCG3PxvqUhYJDYyNsHrIE= =Rl/d -END PGP SIGNATURE- --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
