Bazaar Package Importer stomps on my changes

Elliot Murphy elliot at canonical.com
Mon Jan 31 22:37:44 UTC 2011


Do you need to run bzr mark-uploaded before pushing? (this used to be
necessary, I don't know if it has been replaced/wrapped into the
debcommit)

On Monday, January 31, 2011, Scott Moser <smoser at ubuntu.com> wrote:
> I assume that I am either
> a.) misinformed
> b.) doing something wrong.
>
> Now to my question/problem.
>
> I was under the impression that it was an acceptable (and even commonly
> used package development model) to do something like:
>
> $ bzr init-repo cloud-init
> $ cd cloud-init
> $ bzr branch lp:ubuntu/natty/cloud-init natty.dist
> $ bzr branch natty.dist natty
> $ cd natty
> # hack and add something
> # dch -i, use 'UNRELEASED'
> # debcommit
> # hack and add something, use dch -i,
> # ...
> $ dch --release
> $ debcommit -r
> $ bzr bd -S
> $ dput ../*.changes
> $ bzr push lp:ubuntu/natty/cloud-init
>
> Maybe I'm  misinformed, and something I'm doing above is wrong or
> completely misguided.
>
> However, I happily push my changes, upload the source package, and then
> repeat the above process.
>
> The next time I go to do it, I'm informed on bzr push (or bzr pull) that I
> have missing revisions.
>
> I'll be missing something like:
>   revno: 61
>   fixes bug(s): https://launchpad.net/bugs/635188
>   author: Scott Moser <smoser at ubuntu.com>
>   committer: Bazaar Package Importer <james.westby at ubuntu.com>
>   branch nick: natty
>   timestamp: Thu 2011-01-27 11:32:44 -0500
>
>
> So it appears to me that Mr or Ms "Bazaar Package Importer" is rudely
> stomping on my changes.
>
> Am I just doing something wrong ?
>
> --
> ubuntu-distributed-devel mailing list
> ubuntu-distributed-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
>

-- 
Elliot Murphy | https://launchpad.net/~statik/



More information about the ubuntu-distributed-devel mailing list