Branch import from Git: AssertionError: Invalid sha for ...

Asked by Dan Garner on 2020-01-13

Hi,

Xibo uses Launchpad for translations and we've got some automatic branch imports from Git set up to keep us in Sync. Two of them have stopped syncing (a while ago) and I can't see why or clear out the errors to re-enable.

Example: https://code.launchpad.net/~xibo-maintainers/xibo/xibo-cms
Logs: http://launchpadlibrarian.net/460391239/xibo-maintainers-xibo-xibo-cms.log

```
AssertionError: Invalid sha for <Commit 27c9a32ae3499199d4f494aaf58154060a03e91f>: 237a3948ce479319535dea3359a444a4b0c9b402
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.
```

The commit it mentions doesn't exist, but i'm not clear why it ever would have.

I can't create a new branch with that import url, because of the existing one blocking it - and I can't remove the import from the existing one, or delete it. So I am stuck :-)

Any help or pointers would be appreciated.

Thanks

Question information

Language:
English Edit question
Status:
Expired
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
2020-02-06
Last reply:
2020-02-22
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Dan Garner (dangarner) said : #2

Unfortunately i'm still stuck on this if anyone has any ideas?

Thanks!

Colin Watson (cjwatson) said : #3

Fixing this is likely to require finishing one of two projects in the Launchpad codebase:

 (1) Finish migrating from Bazaar to Breezy for code imports (currently blocked on some problems with the Subversion import code)
 (2) Make translation imports work from git instead of bzr, allowing you to rely only on the fairly simple git-to-git import code rather than the inevitably complex git-to-bzr import code (I've done some initial work on this, but it needs more attention)

I'll ask around and see if any of my colleagues can suggest any hacks in the meantime ...

Dan Garner (dangarner) said : #4

Thanks for the response - as you say, Git to Git would be ideal.

I suppose an alternative option would be to make up a little CI/CD script which used the API to upload a POT file to the translation queue. The process wouldn't touch the branch import at all in that case.

I'm not sure if that is possible, but can do some digging.

Any hack suggestions in the mean time would be most appreciated.

Launchpad Janitor (janitor) said : #5

This question was expired because it remained in the 'Open' state without activity for the last 15 days.