Hi Rick: Thanks for the hints. I have (hopfully) fixed all the issues with the images. If some other binary files are corrupted, please let me know.
Martin, are we ready to roll out another release candidate? It'd be good to get this puppy released soon. Cheers, Bernard -----Original Message----- From: Rick Mohr [mailto:[EMAIL PROTECTED] Sent: Wed 20/09/2006 14:49 To: Bernard Li Cc: ganglia-developers@lists.sourceforge.net Subject: Re: [Ganglia-developers] Corrupted JPEG images ?!? I checked the props on one of the images: svn proplist -v https://svn.sourceforge.net/svnroot/ganglia/trunk/monitor-core/web/templates/default/images/cluster_0-24.jpg Properties on 'https://svn.sourceforge.net/svnroot/ganglia/trunk/monitor-core/web/templates/default/images/cluster_0-24.jpg': svn:keywords : Author Date Id Revision svn:eol-style : native These two properties need to be deleted, and the "svn:mime-type" property should be set with a value of "image/jpeg". (After replacing the corrupt image with the "good" one.) This will cause subversion to treat it as a binary file. I got bit by this when I converted all of my cvs repositories to svn. One important thing to remember when using cvs2svn is that any binary files in the cvs repository should be marked as binary. This will cause the script to set the mime-type for those files to "application/octet-stream", and svn will treat them as binary file. If you want more accurate mime-types and/or eol values set, there are some useful options for cvs2svn: --mime-types=<file> (Use list of mime types in <file> to determine type) --eol-from-mime-type (Tries to set svn:eol-style property value based on mime-type) --no-default-eol (Will prevent svn:eol-style property from being set on any file) Also, in your ~/.subversion/config file, you can add a [auto-props] section. This can be used to force certain properties to be set based on file extensions. (I had to use this when importing PDF files because subversion always thought they were text...) Hope that helps. --Rick -------------------------- Rick Mohr Systems Developer Ohio Supercomputer Center On Wed, 20 Sep 2006, Bernard Li wrote: > Initially I tried to use SF's internal CVS -> SVN migration mechanism > and it failed to work, so I think I had to run the cvs2svn script > manually and imported the files. > > Anyways, it's a moot point now, hopefully we can restore the repository > into a sane state... > > Thanks, > > Bernard > > > -----Original Message----- > > From: Jarod Wilson [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, September 20, 2006 12:04 > > To: Bernard Li > > Cc: [EMAIL PROTECTED]; ganglia-developers@lists.sourceforge.net > > Subject: Re: [Ganglia-developers] Corrupted JPEG images ?!? > > > > Bernard Li wrote: > > > Hi Martin: > > > > > > You're right, the images are corrupted - I wonder what > > happened there. > > > > I've seen that happen if the images weren't imported > > correctly. In the > > case I'm thinking of, binary files were incorrectly tagged with the > > svn:keyword and svn:eol-style properties. Dunno what was used for the > > initial move from cvs to svn, but I think it was the cvs2svn script I > > saw do that. > > > > -- > > Jarod Wilson > > [EMAIL PROTECTED] > > > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Ganglia-developers mailing list > Ganglia-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ganglia-developers > >
