Merge lp:~smartboyhw/ubuntu-packaging-guide/update-packaging-new-software-pages into lp:ubuntu-packaging-guide

[Howard Chan]

1. hello's newest version is 2.9, so we will want to update it.
2. debhelper's latest version is 9. I propose to update it since we will want to enable multiarch, which is best supported in dh 9.
3. The "current" development version is saucy (as dated 15/10/2013).

[Daniel Holbach (dholbach)]

Looks good. Thanks.

review: Approve

=== modified file 'ubuntu-packaging-guide/packaging-new-software.rst'
--- ubuntu-packaging-guide/packaging-new-software.rst	2013-01-22 13:50:06 +0000
+++ ubuntu-packaging-guide/packaging-new-software.rst	2013-10-15 14:11:28 +0000
@@ -29,12 +29,12 @@
 
 Download main package::
 
-    $ wget -O hello-2.7.tar.gz "http://ftp.gnu.org/gnu/hello/hello-2.7.tar.gz"
+    $ wget -O hello-2.9.tar.gz "http://ftp.gnu.org/gnu/hello/hello-2.9.tar.gz"
 
 Now uncompress main package::
 
-    $ tar xf hello-2.7.tar.gz
-    $ cd hello-2.7
+    $ tar xf hello-2.9.tar.gz
+    $ cd hello-2.9
 
 This application uses the autoconf build system so we want to run ``./configure``
 to prepare for compilation.
@@ -66,7 +66,7 @@
 
     $ sudo apt-get install dh-make
     $ cd ..
-    $ bzr dh-make hello 2.7 hello-2.7.tar.gz
+    $ bzr dh-make hello 2.9 hello-2.9.tar.gz
 
 When it asks what type of package type ``s`` for single binary. This will import
 the code into a branch and add the ``debian/`` packaging directory.  Have a look
@@ -80,15 +80,15 @@
 You should now customise each of the files.  
 
 In ``debian/changelog`` change the
-version number to an Ubuntu version: ``2.7-0ubuntu1`` (upstream version 2.7,
+version number to an Ubuntu version: ``2.9-0ubuntu1`` (upstream version 2.9,
 Debian version 0, Ubuntu version 1).  Also change ``unstable`` to the current
-development Ubuntu release such as ``precise``.
+development Ubuntu release such as ``saucy``.
 
 Much of the package building work is done by a series of scripts
 called ``debhelper``.  The exact behaviour of ``debhelper`` changes
 with new major versions, the compat file instructs ``debhelper`` which
 version to act as.  You will generally want to set this to the most
-recent version which is ``8``.
+recent version which is ``9``.
 
 ``control`` contains all the metadata of the package.  The first paragraph
 describes the source package. The second and following paragraphs describe
@@ -96,7 +96,7 @@
 compile the application to ``Build-Depends:``. For ``hello``, make sure that it
 includes at least::
 
-    Build-Depends: debhelper (>= 8.0.0)
+    Build-Depends: debhelper (>= 9)
 
 You will also need to fill in a description of the program in the
 ``Description:`` field.
@@ -140,11 +140,11 @@
 
 You can view the contents of the package with::
 
-    $ lesspipe hello_2.7-0ubuntu1_amd64.deb
+    $ lesspipe hello_2.9-0ubuntu1_amd64.deb
 
 Install the package and check it works::
 
-    $ sudo dpkg --install hello_2.7-0ubuntu1_amd64.deb
+    $ sudo dpkg --install hello_2.9-0ubuntu1_amd64.deb
 
 Next Steps
 ----------
@@ -154,8 +154,8 @@
 ``lintian`` which can be run on both the source .dsc metadata file and
 the .deb binary package::
 
-    $ lintian hello_2.7-0ubuntu1.dsc
-    $ lintian hello_2.7-0ubuntu1_amd64.deb
+    $ lintian hello_2.9-0ubuntu1.dsc
+    $ lintian hello_2.9-0ubuntu1_amd64.deb
 
 A description of each of the problems it reports can be found on the
 `lintian website`_.
@@ -176,7 +176,7 @@
 
     $ bzr builddeb -S
     $ cd ../build-area
-    $ pbuilder-dist precise build hello_2.7-0ubuntu1.dsc
+    $ pbuilder-dist precise build hello_2.9-0ubuntu1.dsc
 
 When you are happy with your package you will want others to review it.  You
 can upload the branch to Launchpad for review::
@@ -187,7 +187,7 @@
 others to test the binary packages.  You will need to set up a PPA in Launchpad
 and then upload with ``dput``::
 
-    $ dput ppa:<lp-username> hello_2.7-0ubuntu1.changes
+    $ dput ppa:<lp-username> hello_2.9-0ubuntu1.changes
 
 See :doc:`uploading<./udd-uploading>` for more information.