Move packaging to git

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

.bzr-builddeb/default.conf

@@ -1,2 +0,0 @@
-[BUILDDEB]
-native = True

.bzrignore

@@ -1,9 +0,0 @@
-/.shelf/
-/build/
-/python-build-stamp-*
-/debian/files
-/debian/ubuntu-dev-tools/
-/debian/ubuntu-dev-tools.debhelper.log
-/debian/ubuntu-dev-tools.*.debhelper
-/debian/ubuntu-dev-tools.substvars
-ubuntu_dev_tools.egg-info

README.updates

@@ -1,12 +1,12 @@
 Updating the ubuntu-dev-tools package
 -------------------------------------
 
-Here are the steps that are recommended to take when updating the
+Here are the 10 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:
+1)  Make sure there are no new commits to the package's master branch in git:
 
-    bzr pull lp:ubuntu-dev-tools
+    git pull
 
 2)  Check to make sure that all approved merges have been merged:
 
@@ -15,6 +15,7 @@ ubuntu-dev-tools package in Ubuntu.
 3)  Make sure that there is no low lying fruit that can be fixed at:
 
     https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools
+    https://bugs.debian.org/src:ubuntu-dev-tools
 
 4)  Check that the test suite passes
 
@@ -27,31 +28,27 @@ ubuntu-dev-tools package in 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://tracker.debian.org/pkg/ubuntu-dev-tools
     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
+6)  Once the target release has been changed, commit it to git (where X.YY is
     the new package version):
 
-    bzr commit -m "Uploaded X.YY to RELEASE."
+    git commit -a -m "Uploaded X.YY to RELEASE."
 
-7)  Tag the new release in Bazaar:
+7)  Create the new source package and tag the new release in git:
 
-    bzr tag
+    gbp buildpackage -S --git-tag
 
-    For a full list of tags, please see: 'bzr tags'. This is so we can track
+    For a full list of tags, please see: 'git tag -l'.  This is so we can track
-    which Bazaar revision is in which release and makes bug triaging easier.
+    which git commit is in which release and makes bug triaging easier.
 
-8)  Create the new source package:
+8)  Upload the package to Debian with dput as normal:
-
-    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.
+9)  Create a new blank entry with dch -i and mark it as UNRELEASED.
 
-11) After it's been dinstalled in Debian, sync to Ubuntu:
+10) After it's been dinstalled in Debian, sync to Ubuntu:
 
     syncpackage ubuntu-dev-tools

debian/control

@@ -4,8 +4,6 @@ Priority: optional
 Maintainer: Ubuntu Developers <ubuntu-dev-team@lists.alioth.debian.org>
 Uploaders: Benjamin Drung <bdrung@debian.org>,
            Stefano Rivera <stefanor@debian.org>
-Vcs-Bzr: lp:ubuntu-dev-tools
-Vcs-Browser: https://code.launchpad.net/~ubuntu-dev/ubuntu-dev-tools/trunk
 Build-Depends: dctrl-tools,
                debhelper (>= 9),
                devscripts (>= 2.11.0~),
@@ -34,6 +32,8 @@ Build-Depends: dctrl-tools,
                python3-setuptools
 X-Python-Version: >= 2.6
 X-Python3-Version: >= 3.2
+Vcs-Git: https://git.launchpad.net/ubuntu-dev-tools
+Vcs-Browser: https://git.launchpad.net/ubuntu-dev-tools
 Homepage: https://launchpad.net/ubuntu-dev-tools
 Standards-Version: 3.9.6
 

debian/gbp.conf

@@ -0,0 +1,4 @@
+[DEFAULT]
+debian-tag = %(version)s
+debian-branch = master
+sign-tags = True