File: 50-devs.txt

package info (click to toggle)
debmake-doc 1.17-7
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 24,612 kB
  • sloc: makefile: 768; sh: 690; ansic: 114; python: 99; sed: 16
file content (94 lines) | stat: -rw-r--r-- 2,576 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
Here are some notable tips about Debian packaging.

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 binary upload

[[debdiff]]
=== debdiff

You can compare file contents in two source Debian packages with the *debdiff* command.

----
$ debdiff old-package.dsc new-package.dsc
----

You can also compare file lists in two sets of binary Debian packages with the *debdiff* command.

----
$ debdiff old-package.changes new-package.changes
----

These are useful to identify what has been changed in the source packages and to check for inadvertent changes made when updating binary packages, such as unintentionally misplacing or removing files.


[[dget]]
=== dget

You can download the set of files for the Debian source package with the *dget* command.

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

[[debc]]
=== debc

You should install generated packages with the *debc* command to test it locally.

----
$ debc package_version-rev_arch.changes
----

[[piuparts]]
=== piuparts

You should install generated packages with the *piuparts* command to test it automatically.

----
$ sudo piuparts package_version-rev_arch.changes
----

NOTE: This is a very slow process with remote APT package repository access.

[[debsign]]
=== debsign

After completing the test of the package, you can sign it with the *debsign* command.

For uploading source-only package (normal):
----
$ debsign package_version-rev_source.changes
----

For uploading binary package:
----
$ debsign package_version-rev_arch.changes
----

[[dput]]
=== dput

After signing the package with the *debsign* command, you can upload the set of files for the Debian source and binary packages with the *dput* command.

For uploading source-only package (normal):
----
$ dput package_version-rev_source.changes
----

For uploading binary package:
----
$ dput package_version-rev_arch.changes
----

[[bts]]
=== 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 https://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-handling[5.8. Handling bugs] of the ``Debian Developer's Reference''.

The *bts* command is a handy tool to manage bugs on the https://www.debian.org/Bugs/[Debian Bug Tracking System].

----
$ bts severity 123123 wishlist , tags -1 pending
----