Difference between revisions of "Create or Update a Debian package"

From Organic Design wiki
(→‎Modifying dependencies in a .deb file)
(Change source-code blocks to standard format)
 
Line 34: Line 34:
  
 
To turn the directory structure into a proper ''.deb'' package file, use:
 
To turn the directory structure into a proper ''.deb'' package file, use:
−
{{code|<pre>
+
<source>
 
cd /var/www/domains/packages
 
cd /var/www/domains/packages
 
dpkg -b source/<package-name> main/<package-name>.deb
 
dpkg -b source/<package-name> main/<package-name>.deb
−
</pre>}}
+
</source>
  
 
=== Adding to a package repository ===
 
=== Adding to a package repository ===
 
All the ''.deb'' package files must be added to the ''main'' repository on the server which is in ''/var/www/packages/main''. Ensure that this repository is included in your ''/etc/apt/sources.list'':
 
All the ''.deb'' package files must be added to the ''main'' repository on the server which is in ''/var/www/packages/main''. Ensure that this repository is included in your ''/etc/apt/sources.list'':
−
{{code|<pre>
+
<source>
 
echo "deb http://packages.organicdesign.co.nz main/" >> /etc/apt/sources.list
 
echo "deb http://packages.organicdesign.co.nz main/" >> /etc/apt/sources.list
−
</pre>}}
+
</source>
  
  
 
Whenever any of the packages in the repository change, the ''Packages.gz'' index file must be updated which can be done as follows.
 
Whenever any of the packages in the repository change, the ''Packages.gz'' index file must be updated which can be done as follows.
−
{{code|<pre>
+
<source>
 
cd /var/www/domains/packages
 
cd /var/www/domains/packages
 
dpkg-scanpackages main /dev/null | gzip > main/Packages.gz
 
dpkg-scanpackages main /dev/null | gzip > main/Packages.gz
−
</pre>}}
+
</source>
  
 
== Creating a GPG Key ==
 
== Creating a GPG Key ==
−
{{code|<pre>
+
<source>
 
gpg --gen-key
 
gpg --gen-key
−
</pre>}}
+
</source>
 
*Don't choose a password for signing, or automated package processing will not work.
 
*Don't choose a password for signing, or automated package processing will not work.
  
 
Export the public key for import into apt:
 
Export the public key for import into apt:
−
{{code|<pre>
+
<source>
 
gpg --list-public-keys
 
gpg --list-public-keys
−
</pre>}}
+
</source>
  
  
Line 67: Line 67:
  
 
We'll use my temporary key hex for this example, be sure to change it.
 
We'll use my temporary key hex for this example, be sure to change it.
−
{{code|<pre>
+
<source>
 
gpg --export 0x5F6DEDCD >repo.key
 
gpg --export 0x5F6DEDCD >repo.key
−
</pre>}}
+
</source>
  
  
 
Whenever you connect a new system to this apt repository you will need to place a copy of the key into your working directory and issue the following command:
 
Whenever you connect a new system to this apt repository you will need to place a copy of the key into your working directory and issue the following command:
−
{{code|<pre>
+
<source>
 
apt-key add repo.key
 
apt-key add repo.key
−
</pre>}}
+
</source>
  
 
== Modifying dependencies in a .deb file ==
 
== Modifying dependencies in a .deb file ==

Latest revision as of 18:11, 22 May 2015

Procedure.svg Create or Update a Debian package
Organic Design procedure

General procedure

Working directory structure

Here's an example directory structure for a package which replaces the apache default config file and sets up default php and html files in /var/www.

The control file in the DEBIAN sub-directory is where all the main configuration is done. The other three files in that sub-directory are scripts which execute on installation and removal of the package.

The rest of the directory structure outside the DEBIAN sub-directory define the directory structure which will be merged with the root of the filesystem when the package is installed.

Our packages at Organic Design are in /var/www/domains/packages and the source directory structures for them are in the sources subdirectory.

Building or updating a package

Next the source needs to be built into a .deb file, if this is being done for an existing package which is being updated, then don't forget to ensure that the version number in the control file is larger.

To turn the directory structure into a proper .deb package file, use: 

cd /var/www/domains/packages
dpkg -b source/<package-name> main/<package-name>.deb

Adding to a package repository

All the .deb package files must be added to the main repository on the server which is in /var/www/packages/main. Ensure that this repository is included in your /etc/apt/sources.list: 

echo "deb http://packages.organicdesign.co.nz main/" >> /etc/apt/sources.list


Whenever any of the packages in the repository change, the Packages.gz index file must be updated which can be done as follows. 

cd /var/www/domains/packages
dpkg-scanpackages main /dev/null | gzip > main/Packages.gz

Creating a GPG Key

gpg --gen-key
  • Don't choose a password for signing, or automated package processing will not work.

Export the public key for import into apt: 

gpg --list-public-keys


Using the line that states "pub" look for the hex numbers after the / (eg. pub 1024D/5F6DEDCD 2008-07-10)

We'll use my temporary key hex for this example, be sure to change it. 

gpg --export 0x5F6DEDCD >repo.key


Whenever you connect a new system to this apt repository you will need to place a copy of the key into your working directory and issue the following command: 

apt-key add repo.key

Modifying dependencies in a .deb file

  1. dpkg-deb -x foo.deb tmpdir
  2. dpkg-deb --control foo.deb tmpdir/DEBIAN
  3. nano tmpdir/DEBIAN/control
  4. dpkg -b tmpdir hacked.deb

See also

Retrieved from "https://organicdesign.nz/wiki/index.php?title=Create_or_Update_a_Debian_package&oldid=119820"