bzr: ERROR: Parent not accessible given base

Bug #1599631 reported by Robert Bruce Park
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Invalid
Medium
Unassigned
Launchpad itself
Invalid
Undecided
Unassigned

Bug Description

Just wondering if this is an issue in launchpad that can be resolved or what is going on here exactly:

$ bzr missing --directory lp:unity8 lp:~untrusted-ci-dev-bot/unity8/unity8-ubuntu-yakkety-landing-008
bzr: ERROR: Parent not accessible given base "bzr+ssh://bazaar.launchpad.net/+branch/unity8/" and relative path "../../../~didrocks/unity8/trunk/"

Revision history for this message
Robert Bruce Park (robru) wrote :

The weird thing is that it works if you reverse them:

$ bzr missing --directory lp:~untrusted-ci-dev-bot/unity8/unity8-ubuntu-yakkety-landing-008 lp:unity8
You have 2 extra revisions:
[snip]

Other projects work both ways, so this seems to be a project-specific glitch:

$ bzr missing --directory lp:~ci-train-bot/ubuntu-keyboard/ubuntu-keyboard-ubuntu-yakkety-landing-031 lp:ubuntu-keyboard
You have 2 extra revisions:
[snip]
$ bzr missing --directory lp:ubuntu-keyboard lp:~ci-train-bot/ubuntu-keyboard/ubuntu-keyboard-ubuntu-yakkety-landing-031
You are missing 2 revisions:
[snip]

It seems this affects at least unity8 and media-hub:

$ bzr missing --directory lp:~ci-train-bot/media-hub/media-hub-ubuntu-yakkety-landing-055 lp:media-hub
You have 2 extra revisions:
[snip]
$ bzr missing --directory lp:media-hub lp:~ci-train-bot/media-hub/media-hub-ubuntu-yakkety-landing-055
bzr: ERROR: Parent not accessible given base "bzr+ssh://bazaar.launchpad.net/+branch/media-hub/" and relative path "../../../~jhodapp/media-hub/initial_branch/"

Revision history for this message
Vincent Ladeuil (vila) wrote :

Hmm, 'bzr missing' default to 'parent_location' if a single branch is provided.

That code path shouldn't be triggered here since you're providing two branches.

The workaround is to fix the bogus 'parent_location':

$ bzr config -d lp:unity8
branch:
  stacked_on_location = ""
  parent_location = ../../../~didrocks/unity8/trunk/ <== bogus
  public_branch = lp:unity8
  push_location = bzr+ssh://bazaar.launchpad.net/+branch/unity8/rtm-14.09/

$ bzr config -d lp:media-hub
branch:
  parent_location = ../../../~jhodapp/media-hub/initial_branch/ <== bogus

Those bogus 'parent_location' come from bzr push replicating them from their local value and is (generally ;) harmless.

Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Vincent Ladeuil (vila) wrote :

> The workaround is to fix the bogus 'parent_location'

I mean:

$ bzr config -d lp:unity8 --remove parent_location

which requires write access to the branch.

Revision history for this message
Robert Bruce Park (robru) wrote :

Thanks vincent, that does seem to work.

William Grant (wgrant)
Changed in launchpad:
status: New → Invalid
Vincent Ladeuil (vila)
Changed in bzr:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.