Imagination svn imports failing
Hi,
The code import for Imagination's SVN is currently failing. I'm not sure if this is related to the previous issues with Sourceforge import due to their SSL certificate changes.
Is there any thing I can to to get this working again?
https:/
http://
Most recent failure:
2011-02-24 15:59:55 INFO [chan bzr SocketAsChannel
2011-02-24 16:00:04 INFO [chan bzr SocketAsChannel
2011-02-24 16:00:22 WARNING N changeset 577
2011-02-24 16:00:37 WARNING change 0
2011-02-24 16:00:52 WARNING change 1
2011-02-24 16:01:07 WARNING change 2
Traceback (most recent call last):
File "/srv/importd.
sys.
File "/srv/importd.
return import_worker.run()
File "/srv/importd.
return self._doImport()
File "/srv/importd.
self.
File "/srv/importd.
foreign_
File "/srv/importd.
totla.
File "/srv/importd.
take_
File "/srv/importd.
revision, logger=logger, strict=strict, summarize=
File "/srv/importd.
message = revision.
File "/srv/importd.
return self.log[
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 81: ordinal not in range(128)
Import failed:
Traceback (most recent call last):
Failure: twisted.
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Curtis Hovey
- Solved:
- 2011-02-24
- Last query:
- 2011-02-24
- Last reply:
- 2011-02-24
|
#1 |
I do not think there is anything for you to do. I reported a bug for this case I and I think I understand enough to fix it. The bug has a medium priority because that is what the similar bugs is set at.
Thanks Curtis Hovey, that solved my question.
Max Bowsher (maxb) said : | #3 |
The problem is a bug in the CSCVS importer, which is no longer used for new Subversion imports. An alternative option that may be acceptable to you is to replace the import with a new one, which will use bzr-svn. The two imports will not be compatible in the sense of merging branches based on one or the other, but this may not be a problem for you.
On Thu, Feb 24, 2011 at 6:57 PM, Max Bowsher
<email address hidden> wrote:
> The problem is a bug in the CSCVS importer, which is no longer used for
> new Subversion imports. An alternative option that may be acceptable to
> you is to replace the import with a new one, which will use bzr-svn. The
> two imports will not be compatible in the sense of merging branches
> based on one or the other, but this may not be a problem for you.
That would be great!
- Andrew
Max Bowsher (maxb) said : | #5 |
I've renamed aside the old import and commenced a new one with the name of the old.