Imagination svn imports failing

Asked by Andrew Starr-Bochicchio on 2011-02-24

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://code.launchpad.net/~vcs-imports/imagination/trunk
http://imagination.svn.sourceforge.net/svnroot/imagination/trunk

Most recent failure:

2011-02-24 15:59:55 INFO [chan bzr SocketAsChannelAdapter] Opened sftp connection (server version 3)
2011-02-24 16:00:04 INFO [chan bzr SocketAsChannelAdapter] Opened sftp connection (server version 3)
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.launchpad.net/production/launchpad-rev-12438/scripts/code-import-worker.py", line 82, in <module>
    sys.exit(script.main())
  File "/srv/importd.launchpad.net/production/launchpad-rev-12438/scripts/code-import-worker.py", line 77, in main
    return import_worker.run()
  File "/srv/importd.launchpad.net/production/launchpad-rev-12438/lib/lp/codehosting/codeimport/worker.py", line 452, in run
    return self._doImport()
  File "/srv/importd.launchpad.net/production/launchpad-rev-12438/lib/lp/codehosting/codeimport/worker.py", line 536, in _doImport
    self.importToBazaar(foreign_tree, bazaar_branch)
  File "/srv/importd.launchpad.net/production/launchpad-rev-12438/lib/lp/codehosting/codeimport/worker.py", line 514, in importToBazaar
    foreign_directory, "-SC", "%s::" % last_commit, bzr_directory)
  File "/srv/importd.launchpad.net/production/launchpad-rev-12438/lib/lp/codehosting/codeimport/worker.py", line 531, in _runToBaz
    totla.totla(config, self._logger, config.args, SCM.tree(source_dir))
  File "/srv/importd.launchpad.net/production/launchpad-rev-12438/lib/cscvs/cmds/totla.py", line 253, in totla
    take_action(apply, revision, target_tree, strict, logger)
  File "/srv/importd.launchpad.net/production/launchpad-rev-12438/lib/cscvs/cmds/totla.py", line 286, in take_action
    revision, logger=logger, strict=strict, summarize=apply.summary)
  File "/srv/importd.launchpad.net/production/launchpad-rev-12438/lib/cscvs/bzr.py", line 160, in commitWithAutomaticLog
    message = revision.get_log().decode('utf-8', 'replace')
  File "/srv/importd.launchpad.net/production/launchpad-rev-12438/lib/svn_oo/Revision.py", line 114, in get_log
    return self.log['message'].encode('utf8')
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.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 1.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Curtis Hovey
Solved:
2011-02-24
Last query:
2011-02-24
Last reply:
2011-02-24
Best Curtis Hovey (sinzui) said : #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.