Contents
What are the steps in making a Debian package?
If you are making a Debian package with an upstream program, the typical workflow of Debian package building involves generating several specifically named files for each step as follows: Get a copy of the upstream software, usually in a compressed tar format.
Are there any programs that already run in Debian?
As a side note, it’s important to point out that Debian already has packages for most kinds of programs, and the number of packages already in the Debian archive is much larger than that of contributors with upload rights.
Where can I find the executable of a process?
You can also look directly at /proc/ /exe, which may be a symlink to the appropriate executable. In the above example, this gives you much more useful information than ps: Most reliable way is to look at the /proc dir for the process. Each process has a /proc/ / directory where it keeps information like:
Where to find the proc Dir for a process?
Most reliable way is to look at the /proc dir for the process. Each process has a /proc/ / directory where it keeps information like: There’s more cool info on each process /proc, but with those above you will be able to exactly know what is going on.
How to update the upstream version of Debian?
Of course, you need to do some obvious chores: Create a copy of the upstream source as the foo_newversion.orig.tar.gz file. Update the Debian changelog file with dch -v newversion-1 . Add an entry with New upstream release .
How to prepare a package for a new upstream release?
Inspection of the new upstream release When preparing packages of a new upstream release for the Debian archive, you must check the new upstream release first. Start by reading the upstream changelog , NEWS, and whatever other documentation they may have released with the new version.
How to update the changelog in Debian?
Update the Debian changelog file with dch -v newversion-1 . Add an entry with New upstream release . Describe concisely the changes in the new upstream release that fix reported bugs and close those bugs by adding Closes: #bug_number .