ubuntu-packaging-guide-team team mailing list archive

[Jonathan Riddell <jriddell@xxxxxxxxxx>]

Jonathan Riddell has proposed merging lp:~jr/ubuntu-packaging-guide/get-orig-source into lp:ubuntu-packaging-guide.

Requested reviews:
  Ubuntu Packaging Guide Team (ubuntu-packaging-guide-team)

For more details, see:
https://code.launchpad.net/~jr/ubuntu-packaging-guide/get-orig-source/+merge/77940

Add note on new get-orig-source command
debuild works fine for building packages from branches, use it
fix typo

-- 
https://code.launchpad.net/~jr/ubuntu-packaging-guide/get-orig-source/+merge/77940
Your team Ubuntu Packaging Guide Team is requested to review the proposed merge of lp:~jr/ubuntu-packaging-guide/get-orig-source into lp:ubuntu-packaging-guide.

=== modified file 'libraries.rst'
--- libraries.rst	2011-07-29 11:10:25 +0000
+++ libraries.rst	2011-10-03 13:40:23 +0000
@@ -44,7 +44,7 @@
 
 The SONAME is ``libnova-0.12.so.2``, which matches the file name (usually the
 case but not always). Here upstream has put the upstream version number as part
-of the SONAME and given is an ABI version of ``2``.  Library package names
+of the SONAME and given it an ABI version of ``2``.  Library package names
 should follow the SONAME of the library they contain. The library binary package
 is called ``libnova-0.12-2`` where ``libnova-0.12`` is the name of the library
 and ``2`` is our ABI number.

=== modified file 'packaging-from-scratch.rst'
--- packaging-from-scratch.rst	2011-08-31 04:02:50 +0000
+++ packaging-from-scratch.rst	2011-10-03 13:40:23 +0000
@@ -125,10 +125,13 @@
 Now we need to check that our packaging successfully compiles the package and
 builds the .deb binary package::
 
-    $ bzr builddeb
-
-This should compile the package and place the result in ``../build-area``.  You
-can view the contents of the package with::
+    $ debuild -us -uc
+
+``debuild`` is a command to build the package in its current location.  The
+``-us -uc`` tell it there is not need to GPG sign the compile.  The result will
+be placed in ``..``.  
+
+You can view the contents of the package with::
 
     $ lesspipe kqrcode_0.4-0ubuntu1_amd64.deb
 
@@ -150,13 +153,11 @@
 A description of each of the problems it reports can be found on the
 `lintian website`_.
 
-After making a fix to the packaging you can rebuild without having to build
-from scratch using::
+After making a fix to the packaging you can rebuild using ``-nc`` "no clean"
+without having to build from scratch::
 
     $ debuild -nc
 
-FIXME is there a UDD equivalent? Bug https://bugs.launchpad.net/bzr-builddeb/+bug/816376
-
 Having checked that the package builds locally you should ensure it builds on a
 clean system using ``pbuilder``::
 

=== modified file 'udd-getting-the-source.rst'
--- udd-getting-the-source.rst	2011-08-31 04:02:50 +0000
+++ udd-getting-the-source.rst	2011-10-03 13:40:23 +0000
@@ -105,6 +105,22 @@
 project`_ to get the issue resolved.
 
 
+Upstream Tar
+------------
+
+You can get the upstream tar by running::
+
+    bzr get-orig-source
+
+The works from bzr-builddeb version 2.7.10.  It will try a number of methods to
+get the upstream tar, firstly by recreating it from the ``upstream-x.y`` tag in
+the bzr archive, then by downloading from the ubuntu archive, lastly by running
+``debian/rules get-orig-source``. The upstream tar will also be recreated when
+using bzr to build the package::
+
+    bzr builddeb
+
+
 Getting a branch for a particular release
 -----------------------------------------