Lubuntu/ubuntu-dev-tools
3
0
Fork 0
mirror of https://git.launchpad.net/ubuntu-dev-tools synced 2025-03-12 07:31:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Move packaging to git

Browse Source 
Signed-off-by: Mattia Rizzolo <mattia@debian.org>
This commit is contained in:
Mattia Rizzolo 2017-03-30 21:13:04 +02:00
parent e55c306a90
commit 1c6b989590
5 changed files with 20 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.bzr-builddeb/default.conf
View File

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

9
.bzrignore
View File

@ -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

31
README.updates
View File

@ -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
which Bazaar revision is in which release and makes bug triaging easier.
For a full list of tags, please see: 'git tag -l'. This is so we can track
which git commit 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:
8) 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

4
debian/control vendored
View File

@ -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

4
debian/gbp.conf vendored Normal file
View File

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