exporting to bzr seems broken since a few days
Bug #578331 reported by
SirVer
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Jeroen T. Vermeulen |
Bug Description
Since a few days, the daily exports of the launchpad translations to my branch no longer work.
The translations from
https:/
should be exported daily to
lp:~sirver/widelands/translations
The last time this has happened was on 2010-05-04. Could this be related to the latest launchpad rollout?
Yet again, I am unsure if this is the correct project to file this bug, but I sure hope it can be quickly fixed.
Related branches
lp:~mwhudson/launchpad/directbranchcommit-calls-branchChanged-bug-578331
- Данило Шеган (community): Approve
- Aaron Bentley (community): Approve
-
Diff: 131 lines (+26/-15)6 files modifieddatabase/schema/security.cfg (+2/-2)
lib/lp/code/model/branch.py (+1/-1)
lib/lp/code/model/directbranchcommit.py (+5/-1)
lib/lp/code/tests/test_directbranchcommit.py (+7/-0)
lib/lp/codehosting/bzrutils.py (+9/-0)
lib/lp/codehosting/vfs/branchfs.py (+2/-11)
lp:~jtv/launchpad/bug-578331
(Merged)
lp:~jtv/launchpad/devel-bug-578331
(Merged)
To post a comment you must log in.
We are seeing this in our log files as well with the following error message:
2010-05-08 03:59:11 INFO Exporting widelands trunk series. eError( 'Branch has been changed. Not committing.',)
2010-05-08 03:59:59 ERROR Failure: ConcurrentUpdat
This is likely related to branch-scanner problems just before the latest Launchpad rollout. It seems there are a bunch of branches which have remained in the "updating branch" state. Quick workaround for you should be to just push a dummy revision (try using "bzr commit --unchanged" in that branch and then pushing it back to LP), but it's definitely something for our code guys to look into.
Example branches are lp:~sirver/widelands/translations, lp:~walmis/blueman/po, lp:~menesis/schooltool.intervention/translations and so forth (we've got around 30 branches that we are trying to export to that exhibit the same problem). None of them have been changed since something like 2010-05-05.