Before we can actually submit the tools upstream to Debian, we need to
decide which tools are relevant. I have gone through all of the scripts
and marked what scripts I feel would be useful to have in Debian (O=Good
for Debian, X=Ubuntu-only)
X 404main - used to check what components a package's deps are in, for
doing a main inclusion report for example.
X buildd - give commands to the Launchpad build daemons from the command line.
O check-symbols - will compare and give you a diff of the exported symbols of
all .so files in a binary package.
O dch-repeat - used to repeat a change log into an older release.
X dgetlp - download a source package from the Launchpad library.
X get-branches - used to branch/checkout all the bzr branches in a Launchpad
team.
O get-build-deps - install the build dependencies needed for a package
reading debian/control.
X grab-attachments - download all bug attachments from a Launchpad bug
report.
X grab-merge - grabs a merge from merges.ubuntu.com easily.
X hugdaylist - compile HugDay lists from bug list URLs.
X lp-project-upload - upload a release tarball to a Launchpad project
X lp-set-dup - sets the "duplicate of" bug of a bug and its dups.
X manage-credentials - manage Launchpad token credentials.
X massfile - fill multiple bugs using a template.
O mk-sbuild-lv - script to create LVM snapshot chroots via schroot and
sbuild.
O pbuilder-dist - pbuilder wrapper script.
X pull-debian-debdiff - attempts to find and download a specific version of
a Debian package and its immediate parent to generate a debdiff.
O pull-debian-source - downloads the lastest source package available in
Debian of a package.
X pull-lp-source - downloads lastest source package from Launchpad.
X pull-revu-source - downloads the latest source package from REVU
X requestsync - files a sync request with Debian changelog and ratione.
O reverse-build-depends - find the reverse build dependencies that a package
has.
O submittodebian - automatically send your changes to Debian as a bug report.
O suspicious-source - outputs a list of files which are not common source
files.
X ubuntu-iso - output information of an Ubuntu ISO image.
X update-maintainer - script to update maintainer field in ubuntu packages.
O what-patch - determines what patch system, if any, a source package is
using.
I must admit that I am not very familiar with some of the scripts in
ubuntu-dev-tools, so I would appreciate it if some other people would
review my list and make any necessary corrections.
Once this is done, we need to decide how we will submit the scripts.
Should we simply request for them to be included in the 'devscripts'
package? Or would it be better to try and group them with related
packages (ex pbuilder-dist with pbuilder)?
--
Push to debian the ubuntu-dev-tools that are relevant for them
https://bugs.launchpad.net/bugs/439906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
