章 13. Tool usages

# 章 13. Tool usages

Here are some notable tools around Debian packaging.

| 注意
The descriptions in this section are intentionally brief. Prospective maintainers are strongly encouraged to search for and read all relevant documentation associated with these commands.

| 注意
Examples here use the gz-compression. The xz-compression may be used instead.

## 13.1. debdiff

您可以使用 debdiff 命令來對比兩個 Debian 套件組成的差別。

    [base_dir] $ debdiff old-package.dsc new-package.dsc

您也可以使用 debdiff 命令來對比兩組二進制 Debian 套件中的檔案列表。

    [base_dir] $ debdiff old-package.changes new-package.changes

當檢查原始碼套件中哪些檔案被修改時，這個命令非常有用。它還可以用來檢測二進位制包中是否有檔案在更新過程中發生變動，比如被意外替換或刪除。

Debian now enforces the source-only upload when developing packages. So there may be 2 different *.changes files:

- package_version-revision_source.changes for the normal source-only upload
- package_version-revision_arch.changes for the source+binary upload

## 13.2. dget

您可以使用 dget 命令來下載 Debian 套件原始碼的檔案集。

    [base_dir] $ dget https://www.example.org/path/to/package_version-rev.dsc

## 13.3. mk-origtargz

You can make the upstream tarball ../foo-newversion.tar.[xg]z accessible from the Debian source tree as ../foo_newversion.orig.tar.[xg]z. This command is useful for renaming and symlinking the upstream tarball to the expected Debian naming convention.

## 13.4. origtargz

You can fetch the pre-existing orig tarball of a Debian package from various sources, and unpack it with origtargz command.

This is basically for -2, -3, …​ revisions.

| 注意
When the upstream tarball is missing, debmake automatically produces a required tarball. This is a convenient feature and good enough for making a private Debian package. But when making a Debian package for the official Debian repository, you must use exactly the same upstream tarball as the -1 revision. For such case, origtargz should be used.

## 13.5. git deborig

If the upstream project is hosted in a Git repository without an official tarball release, you can generate its orig tarball from the git repository for use by the Debian source package. Execute “git deborig” from the root of the checked-out source tree.

This is basically for -1 revisions.

## 13.6. dpkg-source -b

The “dpkg-source -b” command packs the upstream source tree into the Debian source package.

It expects a series of patches in the debian/patches/ directory and their application sequence in debian/patches/series.

It is compatible with dquilt (see “節 4.4, “quilt setup””) operations and understands the patch application status from the existence of .pc/applied-patches.

The dpkg-buildpackage command invokes “dpkg-source -b”.

## 13.7. dpkg-source -x

The “dpkg-source -x” command extracts the source tree and applies the patches in the debian/patches/ directory using the sequence specified in debian/patches/series to the upstream source tree. It also adds .pc/applied-patches. (See “節 11.13, “Patch applied Git repository””.)

The “dpkg-source -x --skip-patches” command extracts source tree only. It doesn’t add .pc/applied-patches. (See “節 11.5, “Patch unapplied Git repository””.)

Both extracted source trees are ready for building Debian binary packages with dpkg-buildpackage, dbuild, sbuild, etc..

## 13.8. debc

您應該使用 debc 命令安裝生成的套件以在本地測試它。

    [base_dir] $ debc package_version-rev_arch.changes

## 13.9. bts

After uploading the package, you will receive bug reports. It is an important duty of a package maintainer to manage these bugs properly, as described in “5.8. Handling bugs” of the “Debian Developer’s Reference”.

bts 命令是一個用以處理 “Debian 缺陷追蹤系統” 上的錯誤的便捷工具。

    [~] $ bts severity 123123 wishlist , tags -1 pending

## 13.10. dpkg-depcheck

You can use dpkg-depcheck(1) to obtain a good first approximation to the Build-Depends line needed by a Debian package.

    [foo-1.0] $ dpkg-depcheck -b debian/rules build

章 12. 小技巧 |  | 章 14. 更多範例