Iain Lane 2861c54ad7 backportpackage: Unset DEBEMAIL when building source package.
Fixes error when building backports for packages with no Ubuntu changes. This
happens because Ubuntu has a policy of requiring that the Maintainer field of
Ubuntu-modified packages be set to an @ubuntu.com address. Normally this is a
warning, except when the uploader (determined by DEBEMAIL) is @ubuntu.com. In
that case it's an error and the source package build is aborted. We don't want
this behaviour for backports, so unset DEBEMAIL to make the error a warning
again.

LP: #1007042
2012-06-13 23:21:17 +01:00
2010-12-20 21:33:48 +02:00
2011-05-23 23:41:30 +02:00
2012-05-27 00:46:24 +02:00
2011-12-03 00:03:00 +02:00
2010-12-03 00:06:43 +01:00
2010-12-27 21:54:31 +01:00
2011-09-10 16:40:19 +02:00
2012-05-27 00:46:24 +02:00
2011-12-04 00:35:49 +02:00

Updating the ubuntu-dev-tools package
-------------------------------------

Here are the steps that are recommended to take when updating the
ubuntu-dev-tools package in Ubuntu.

1)  Make sure that there are no new revisions to the package's trunk in Bazaar:

    bzr pull lp:ubuntu-dev-tools

2)  Check to make sure that all approved merges have been merged:

    https://code.launchpad.net/ubuntu-dev-tools/+activereviews

3)  Make sure that there is no low lying fruit that can be fixed at:

    https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools

4)  Check that the test suite passes

    setup.py test

5)  Before uploading the package change the UNRELEASED field in the
    debian/changelog file to unstable. (ubuntu-dev-tools is maintained in Debian
    and synced to Ubuntu)

    If there is no UNRELEASED entry, make sure that the version for the current
    one has not been uploaded by someone else already:

    http://packages.qa.debian.org/u/ubuntu-dev-tools.html
    https://launchpad.net/ubuntu/+source/ubuntu-dev-tools/+publishinghistory

6)  Once the target release has been changed, commit it to Bazaar (where X.YY is
    the new package version):

    bzr commit -m "Uploaded X.YY to RELEASE."

7)  Tag the new release in Bazaar:

    bzr tag

    For a full list of tags, please see: 'bzr tags'. This is so we can track
    which Bazaar revision is in which release and makes bug triaging easier.

8)  Create the new source package:

    bzr bd -S

9)  Upload the package to Debian with dput as normal:

    dput ftp-master ubuntu-dev-tools_X.YY_$arch.changes

10) Create a new blank entry with dch -i and mark it as UNRELEASED.

11) After it's been dinstalled in Debian, sync to Ubuntu:

    syncpackage ubuntu-dev-tools
Description
No description provided
Readme 15 MiB
Languages
Python 89%
Shell 9.9%
Perl 1.1%