Forums : Technical Issue Help

Hi,

The listing for SquirrelMail has not been updated since January. It displays the following message:

https://squirrelmail.svn.sourceforge.net/svnroot/squirrelmail/trunk
Step 1 of 3: Downloading source code history (Failed)

Could you please check this out and get SquirrelMail going again?

Thanks!
Thijs

kink almost 18 years ago

Hi Kink,

I looked into SquirrelMail's download for you. It turns out we've tried several times to download about 8 times since January. The (current) issue appears to be with the SquirrelMail svn server giving an error when asking for a log. I suspect we'll need someone from the SquirrelMail team to take a look. The error is reproducible from the svn command line

svn log https://squirrelmail.svn.sourceforge.net/svnroot/squirrelmail/trunk > log.txt
svn: REPORT request failed on '/svnroot/squirrelmail/!svn/bc/12467/trunk'

this produces a non-zero length file but gives the error shown above.

If you're a part of the SquirrelMail team and could take a look, that'd be great. Thanks in advance and thanks for using Ohloh!
Andy

Andy Verprauskus almost 18 years ago

That kind of error on svn log we had when we migrated our Blender repository from CVS to SVN. During the move cvs2svn did some bad encoding of UTF-8 and other encoding characters in commit messages (among others the polish l with dash through it). We had to do the migration five or six times before we got it right.

I guess svn log is not very often used on the entire history, I think I'm a stats junkie enough to have wanted it, so it got tested during our migration. Perhaps the SquirrelMail have similar problems. If the migration happened already looong ago, a revisit of it is probably out of order, but if the repository was created using fsfs as the backend then maybe manual hacking commit messages could solve the problem (note, untested and without any further knowledge - I used to manually hack our CVS when I did some preliminary testing of migration tools like tailor)

Anyway, good luck :)

/Nathan

Nathan Letwory ... almost 18 years ago

I can indeed reproduce that. The problem seems to be invalid UTF-8 sequence generated by cvs2svn. I'm looking into fixing that now.

kink almost 18 years ago

I found out the following.

It is possible to change the log message with propedit if a relevant hook has been enabled, or by using svnadmin directly on the repository. Since as you might have seen we are sf.net hosted, I do not have direct control over the repository. I'll ask sf.net to add the hook.

Alternatively I could do a full dump, edit, and replace, but I'm not very eager to do so as you might understand.

kink almost 18 years ago

I hope the folks of sf.net help you out here. After this one problem is fixed, make sure you do a svn log on the entire tree and fix any upcoming issues like this. As said, we had to redo our migration several times, so I can perfectly well understand that you don't want to do a full dump and reload. Again, good luck :)

/Nathan

Nathan Letwory ... almost 18 years ago

Thijs, did you have a chance to look into this?

When I try to get the log, I get the same error, although I get about a year's worth of data in the log file.

I just tried to remove and re-add our enlistment (before I found any of this information - there does not seem to be a search tool for these forums, which is less than helpful), and it claims success downloading, but then it fails trying to import the data into the database. I only saw one thread that addresses this issue, with no response from ohloh (again, a forum search tool would be nice):

http://www.ohloh.net/forums/10/topics/827

Paul Lesniewski over 17 years ago

Hi pdontthink,

Are you asking about SquirrelMail? The topic you linked to seems unrelated -- there are many reasons that downloads and imports can fail.

In our old Subversion tools, we used svn log as part of the download, so if the repository was unable to properly log, it could not be downloaded to our servers.

In our new Subversion tools, we use svnsync for the download, so a broken log doesn't impact the download portion. However, we still use svn log to move the commit history into our database, so if the repository is unable to properly log, we'll still be unable to create a report.

As long as the repository itself cannot be queried, there's little we can do on our end.

Robin Luckey over 17 years ago

BTW the search box at the top of the page can be used to search posts.

Robin Luckey over 17 years ago

Yes, I am asking about SquirrelMail. Why does it seem unrelated? As I explained above, the error on the SquirrelMail enlistments page has now changed because the SVN server returns at least a year's worth of data, although it still does give the same error. However, your import process apparently chokes on even that data too: Step 2 of 3: Importing source code into database (Failed).

Regarding your search tool, I tried searching in the box at the top for Importing failed and nothing came up in the forums at all, but, as you can see from the link I gave above, there is in fact at least one post asking about the same thing. The only thing that comes up is two project listings.

Thanks for the great tool.

Paul Lesniewski over 17 years ago

pdontthink: the main problem is that svn log does not work for our repository, that is, it will crash on some commit messages. These commit messages will have to be excised by hand. This would normally be doable with svnadmin, but sf.net does not provide svnadmin-access for us. Thus, we need to export, modify, and replace our entire repository. I'm willing to do that at some point, but it's not top priority :-)

kink over 17 years ago

kink: that the log errors out was the problem before, but as I explained twice above, it no longer spits out an empty log file, which was said to be the problem earlier in this thread - it gives data back to 2006. Furthermore, the error stated by the enlistment process is no longer the same as what it had been: it is NOT a data download error, it is a data import error. I agree that the log error (which still occurs) needs to be fixed, but it also seemed as if there was an Ohloh problem because their tool couldn't import what data it did get.

Paul Lesniewski over 17 years ago

kink: I'm the main cvs2svn maintainer. I'd be interested to know more details about the creation of invalid UTF-8 strings by cvs2svn, so that we can fix it. Best would be if you would submit a test case to the [email protected] mailing list. The cvs2svn FAQ gives some tips for creating a small but useful test case.

Michael Haggerty over 17 years ago

@pdontthink:

Don't be distracted by download vs. import. We download from SourceForge using svnsync, which succeeds in this case. This gives us a local mirror of the repository. At that point, import begins, and use use svn log to get the list of commits out of the repository and into our database. The import fails because the log is broken.

@Micheal:

I'm afraid I don't have any direct experience using cvs2svn, so I'm probably not much help, but if there's some way I can cooperate in helping you out let me know. We've found several repositories that are broken in this way. It might be user error; it might be a problem in cvs2svn; I can't say. Let me know if I can help.

Robin

Robin Luckey over 17 years ago