flash-kernel import fails apparently mismatching maverick and natty branches
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Critical
|
Andrew Bennetts | ||
Ubuntu Distributed Development |
Fix Released
|
Undecided
|
canonical-bazaar |
Bug Description
Hi
flash-kernel was developed in a regular bzr branch which we used to overwrite the UDD branch
This then required a requeue_package.py --full flash-kernel, but this failed and currently still fails with:
Traceback (most recent call last):
File "/srv/package-
persistent_
File "/srv/package-
import_
File "/srv/package-
possible_
File "/usr/lib/
create_
File "/usr/lib/
self.cleanups, self.func, self, *args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
repository=
File "<string>", line 4, in sprout_read_locked
File "/usr/lib/
result = to_bzrdir.
File "/usr/lib/
name=name, repository=
File "/usr/lib/
% (repository.
AssertionError: repository.user_url 'bzr+ssh:
The maverick vs natty part is suspicious in this log.
Thanks,
Related branches
- Jelmer Vernooij (community): Approve
-
Diff: 88 lines (+36/-3)4 files modifiedbzrlib/remote.py (+2/-2)
bzrlib/smart/bzrdir.py (+2/-1)
bzrlib/tests/test_remote.py (+28/-0)
doc/en/release-notes/bzr-2.3.txt (+4/-0)
I think this might be something to do with reusing transports.
We are attempting to push a branch to the maverick path that we just branched from the natty
path.
Thanks,
James