ubuntu-packaging-guide-team team mailing list archive
-
ubuntu-packaging-guide-team team
-
Mailing list archive
-
Message #00384
[Merge] lp:~andrewsomething/ubuntu-packaging-guide/lp-866104 into lp:ubuntu-packaging-guide
Andrew Starr-Bochicchio has proposed merging lp:~andrewsomething/ubuntu-packaging-guide/lp-866104 into lp:ubuntu-packaging-guide.
Requested reviews:
Ubuntu Packaging Guide Team (ubuntu-packaging-guide-team)
Related bugs:
Bug #866104 in Ubuntu Packaging Guide: "bzr bd is an acronym too many"
https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/866104
For more details, see:
https://code.launchpad.net/~andrewsomething/ubuntu-packaging-guide/lp-866104/+merge/79860
--
https://code.launchpad.net/~andrewsomething/ubuntu-packaging-guide/lp-866104/+merge/79860
Your team Ubuntu Packaging Guide Team is requested to review the proposed merge of lp:~andrewsomething/ubuntu-packaging-guide/lp-866104 into lp:ubuntu-packaging-guide.
=== modified file 'fixing-a-bug.rst'
--- fixing-a-bug.rst 2011-07-20 13:30:19 +0000
+++ fixing-a-bug.rst 2011-10-19 17:47:40 +0000
@@ -119,7 +119,7 @@
To build a test package with your changes, run these commands::
- $ bzr bd -- -S -us -uc
+ $ bzr builddeb -- -S -us -uc
$ pbuilder-dist <release> build ../<package>_<version>.dsc
This will create a source package from the branch contents (``-us -uc`` will
=== modified file 'udd-merging.rst'
--- udd-merging.rst 2011-09-06 21:43:16 +0000
+++ udd-merging.rst 2011-10-19 17:47:40 +0000
@@ -69,7 +69,7 @@
changelog entries since the last Ubuntu change will be included in your
``_source.changes`` file. For example::
- $ bzr bd -S --package-merge
+ $ bzr builddeb -S --package-merge
Merging a new upstream version
=== modified file 'udd-newpackage.rst'
--- udd-newpackage.rst 2011-03-13 20:39:22 +0000
+++ udd-newpackage.rst 2011-10-19 17:47:40 +0000
@@ -162,7 +162,7 @@
===========================
Now we can build the source package and publish the package as we normally
-would, with ``bzr bd -S`` and ``dput``.
+would, with ``bzr builddeb -S`` and ``dput``.
.. _PPA: https://help.launchpad.net/Packaging/PPA
=== modified file 'udd-uploading.rst'
--- udd-uploading.rst 2011-08-31 04:02:50 +0000
+++ udd-uploading.rst 2011-10-19 17:47:40 +0000
@@ -44,7 +44,7 @@
The next step is to build and test the modified source package as you normally
would::
- $ bzr bd -S
+ $ bzr builddeb -S
The last step is to mark the change as being the same as the source package
that was uploaded, bzr-builddeb will override the `tag` command to
=== modified file 'udd-working.rst'
--- udd-working.rst 2011-07-25 13:19:56 +0000
+++ udd-working.rst 2011-10-19 17:47:40 +0000
@@ -74,7 +74,7 @@
In order to build the package you can use the `bzr builddeb` command from
the `bzr-builddeb` package. You can build a source package with::
- $ bzr bd -S
+ $ bzr builddeb -S
(`bd` is an alias for `builddeb`.) You can leave the package unsigned by
appending `-- -uc -us` to the command.
@@ -88,7 +88,7 @@
tarball, check to see if there is a `.bzr-builddeb/default.conf` file
erroneously specifying the package as native. If the changelog version has a
dash in it, then it's not a native package, so remove the configuration file.
-Note that while `bzr bd` has a `--native` switch, it does not have a
+Note that while `bzr builddeb` has a `--native` switch, it does not have a
`--no-native` switch.
Once you've got the source package, you can build it as normal with
Follow ups