Cannot push to a LP project

[Andrew Bennetts]

Marius Gedminas wrote:
[...]
> You can fix that with 'bzr upgrade lp:nimrod' (slow) or through the
> Launchpad web pages (faster, but I've no clue how).

There should be a upgrade this branch link on
<https://code.launchpad.net/~nimrod-devs/nimrod/trunk> for any user that
is in the ~nimrod-devs team.

> > To make a long story short, is there a way to push my changes to this
> > project?  I don't dare to upgrade the repository myself, as I am not
> > the owner.  I can ask the owner to do the upgrade, but I don't know if
> > he is willing to do it.
> >
> > These backward compatibility issues are annoying. I don't care if my own 
> > history is lost in the merge, what I want is to push my final changes. Is 
> > there a simple way to do it, even if it needs to pull again that project?
> 
> I don't know; presumably you can bzr init-repo and explicitly select the
> repository format that upstream is using.  Although then you'll have the
> same problem of merging the branch with your changes.  Perhaps you can
> export them as a bundle and apply manually?

If the owner doesn't want to upgrade, then sadly revisions from the
current (2a) format can't be merged.  If you don't care about history
then the easiest way would be to simply make a plain diff of your
changes, and apply and commit it in a copy of the branch in the same
format as the source.

I recommend asking the owner of lp:nimrod to upgrade first though; it
should be easy to do and the benefits are considerable (e.g. much
smaller disk consumption), and the requirements are low (bzr 2.0 or
newer should be easy to install on most platforms).

-Andrew.