I'm not aware of any. As Michael and I already did this once before I am surmising that when the new repo got set up, all the file properties were lost. Either that or someone's svn client is broken and stripping all that info on commit.
Bill. 2009/1/10 Jason Martin <jason.worth.mar...@gmail.com>: > > Are there any non-text files in the MPIR source tree? I'm planning to > run a quick script to set the svn:eol-style property to native on all > the files. I think everything is text, so this should fix the EOL > problems that Bill first mentioned. However, it might mess up and > non-text files. It looks like svn:executable is already set on a fair > number of files, and that gets preserved for me across different > machines checking them out. For example, I just set svn:executable on > install-sh and it seems to be working fine (I did svn update on a > different machine and it made the change). > > --jason > > > On Fri, Jan 9, 2009 at 11:11 PM, Bill Hart <goodwillh...@googlemail.com> > wrote: >> >> I think svn:executable is the right property to set. Maybe I have >> svn:execute or something like that. Maybe that is not the same thing. >> >> This page explains anyhow: >> >> http://svnbook.red-bean.com/en/1.1/ch07s02.html >> >> Bill. >> >> 2009/1/10 Jason Martin <jason.worth.mar...@gmail.com>: >>> >>> eno is also using svn version 1.4.6, so that probably isn't the issue. >>> >>> I'm not very svn savvy, so if their are some "post commit hooks" or >>> things like that which should be running on the server, point me in >>> the right direction and I'll try to set them up. >>> >>> I personally have noticed that svn doesn't seem to preserve changes in >>> file permissions past the initial commit. For example, if I make no >>> changes on a file other than on the permissions and then do a svn >>> commit, that file does not get committed. Perhaps there is a >>> configuration option that will change that behavior, if so let me know >>> what it is. >>> >>> --jason >>> >>> >>> On Fri, Jan 9, 2009 at 10:30 PM, Bill Hart <goodwillh...@googlemail.com> >>> wrote: >>>> >>>> I mean I checked out on eno then switched to fulvia. >>>> >>>> 2009/1/10 Jason Martin <jason.worth.mar...@gmail.com>: >>>>> >>>>> The SVN running on the server is version 1.4.6 >>>>> >>>>> The most current SVN version is 1.5.5, so "no" we aren't using the >>>>> most current version. We are using the version in the standard Ubuntu >>>>> distro. >>>>> >>>>> I just looked at the subversion web page, and the native file >>>>> formatting stuff isn't mentioned in the differences between the 1.4.x >>>>> and 1.5.x series. >>>>> >>>>> If you think it would make a difference, I could get the most recent >>>>> svn sources and build it, but I usually feel better just using the >>>>> packages shipped with the distros. >>>>> >>>>> Incidentally, what is the path to the svn client you're using on fulvia? >>>>> >>>>> Jason Worth Martin >>>>> Asst. Professor of Mathematics >>>>> http://www.math.jmu.edu/~martin >>>>> >>>>> >>>>> >>>>> On Fri, Jan 9, 2009 at 9:27 PM, Bill Hart <goodwillh...@googlemail.com> >>>>> wrote: >>>>>> >>>>>> The current svn repo appears to have some issues with setting file >>>>>> properties. We went through and changed a whole load of files so that >>>>>> the line endings would be automatically set to the native format when >>>>>> checked out. But I just checked out on fulvia and the line endings for >>>>>> the Makefile in yasmbuild were all dos format (which doesn't work on >>>>>> fulvia). >>>>>> >>>>>> Also, I am wondering if the execute permissions are doing anything. I >>>>>> can set them in the Windows front end to svn that I have, but it seems >>>>>> to make no difference when the files are checked out. >>>>>> >>>>>> Are we using a recent version of svn on the server? >>>>>> >>>>>> Bill. >>>>>> > >>>>>> >>>>> >>>>> > >>>>> >>>> >>>> > >>>> >>> >>> > >>> >> >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
