mirror of
https://git.launchpad.net/ubuntu-dev-tools
synced 2026-01-09 00:13:27 +00:00
9f82b26682
... and indicate which tools need it in the package description. At least on current Debian testing, `run0` is an adequate non-setuid replacement for `sudo` for typical interactive purposes. The only obstacle to me removing `sudo` from my system entirely is that `ubuntu-dev-tools` depends on it, but only for tools that I don't need any more. Given that a significant subset of this package is useful without `sudo` (e.g. `pull-debian-source` and friends, `syncpackage`, `backportpackage` provided that you aren't asking it to build using `pbuilder`, and so on), I think Recommends would be more appropriate than Depends. This won't affect Ubuntu systems at present since `sudo` is still in the minimal seed, and it also won't affect typical users who install with Recommends, but it would make it easier for some users to choose to reduce their security exposure.
Updating the ubuntu-dev-tools package
-------------------------------------
Here are the 10 steps that are recommended to take when updating the
ubuntu-dev-tools package in Ubuntu.
1) Make sure there are no new commits to the package's master branch in git:
git pull
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
https://bugs.debian.org/src: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:
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 git (where X.YY is
the new package version):
git commit -a -m "Uploaded X.YY to RELEASE."
7) Create the new source package and tag the new release in git:
gbp buildpackage -S --git-tag
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) Upload the package to Debian with dput as normal:
dput ftp-master ubuntu-dev-tools_X.YY_$arch.changes
9) Create a new blank entry with dch -i and mark it as UNRELEASED.
10) After it's been dinstalled in Debian, sync to Ubuntu:
syncpackage ubuntu-dev-tools