can't propose a merge spanning projects or packages

Bug #446716 reported by Zachery Bir on 2009-10-08
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

When trying to propose the branch lp:~urbanape/bindwood/trunk.lp444022 for merging to lp:~ubuntu-dev/firefox-extensions/bindwood.ubuntu, launchpad told me that "This branch is not mergeable into lp:~ubuntu-dev/firefox-extensions/bindwood.ubuntu"

However, when I branch lp:~ubuntu-dev/firefox-extensions/bindwood.ubuntu and manually bzr merge lp:~urbanape/bindwood/trunk.lp444022, it works fine.

This seems to be a flaw or oversight in the way lp allows for merge proposals to run.

Curtis Hovey (sinzui) on 2009-12-30
affects: launchpad → launchpad-code
Changed in launchpad-code:
importance: Undecided → Low
status: New → Triaged
Tim Penhey (thumper) wrote :

This isn't an oversight, but is a flaw. This is by design as the app servers don't have direct access to the underlying branches (right now), and as an approximation we check that the branches have the same target (source package or project).

Martin Pool (mbp) on 2010-03-24
summary: - Can't target an arbitrary branch for merge
+ can't propose a merge spanning projects or packages
Martin Pool (mbp) on 2010-03-26
tags: added: code-review confusing-ui

Sorry about this 'me too!' posting but the launchpad tour currently boasts "making it easy to share code [...] across projects" (see [1]), so I am seriously disappointed by this unexpected behaviour.

I have a project to maintain a stable branch of OpenERP as the OpenERP bug fixing policy prevents community bug fixes on the stable branch of the official project (soul sucking hybrid business model). However, we among others post branches of the OpenERP project that fix such bugs on the stable version, and I would like to manage merge requests of these branches with our own project.

Indeed, the two branches in their respective projects have a recent common anchestor and bzr has no problem doing the actual merges, but due to this bug, Launchpad keeps telling me that "This branch (under openobject-addons) is not mergeable into lp:therp-backports".

For example: cannot be merged in lp:therp-backports


I would really like this flaw to be solved but of course, with only three people being affected in three years we do not stand a chance...


Vivek poddar (vivekimsit) wrote :


It seems me too is affected by this bug! I am trying to merge my change proposal of my branch: lp:~synerpgy/synerpgy-projects/synerpgy-extra-trunk into the target branch: lp:openobject-addons/extra-trunk. I am not able to understand what is going wrong.

Thanks and Regards!

Jobi Kea Carter (keacarterdev) wrote :

Unless there is a reason for this which I don't understand, I too would like to see this behavior changed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers