Merge lp:~al-maisan/bzr-builddeb/mpdocs into lp:~bzr-builddeb-hackers/bzr-builddeb/trunk-old

Proposed by Muharem Hrnjadovic
Status: Merged
Merged at revision: not available
Proposed branch: lp:~al-maisan/bzr-builddeb/mpdocs
Merge into: lp:~bzr-builddeb-hackers/bzr-builddeb/trunk-old
Diff against target: None lines
To merge this branch: bzr merge lp:~al-maisan/bzr-builddeb/mpdocs
Reviewer Review Type Date Requested Status
James Westby Approve
Review via email: mp+11447@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

Hello there!

The branch at hand adds the documentation for the "merge-package" command. Please take a look. Thanks!

Revision history for this message
James Westby (james-w) wrote :

Merged, thank you.

James

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
=== modified file 'doc/user_manual/normal.rst'
--- doc/user_manual/normal.rst 2009-02-18 22:50:44 +0000
+++ doc/user_manual/normal.rst 2009-09-04 09:41:10 +0000
@@ -276,5 +276,38 @@
276edit the files to resolve the conflicts as normal. Once you have finished276edit the files to resolve the conflicts as normal. Once you have finished
277you should commit, and then you can carry on with your work.277you should commit, and then you can carry on with your work.
278278
279Merging a source package
280########################
281
282When merging a source package the ensuing differences will ideally be
283germane to the target packaging branch. However, on occasion the source and
284target upstream ancestry may have diverged, resulting in spurious conflicts.
285
286The 'merge-package' command can then be used to consolidate the ancestry in
287automated fashion. For example::
288
289 $ bzr branch ~/src/ubuntu/karmic/ipsec-tools/karmic/
290 $ cd karmic/
291 $ bzr merge-package ~/src/debian/sid/ipsec-tools/sid/
292
293On success ``merge-package`` will leave the branch in the same state as a
294normal merge allowing you to review and commit.
295
296In a small number of cases, however, the source `upstream` and target
297`packaging` branches will have conflicts that cause the following error
298instead::
299
300 The upstream branches for the merge source and target have diverged.
301 Unfortunately, the attempt to fix this problem resulted in conflicts.
302 Please resolve these, commit and re-run the "merge-package" command to
303 finish.
304 Alternatively, until you commit you can use "bzr revert" to restore the
305 state of the unmerged branch.
306
307Resolving the conflicts at hand, committing the changes and re-running
308``merge-package`` to finish is probably the best course of action. Having
309said that, you can return to the state before starting with ``bzr revert``
310just like with a normal merge.
311
279.. vim: set ft=rst tw=76 :312.. vim: set ft=rst tw=76 :
280313

Subscribers

People subscribed via source and target branches