Debian package management: Difference between revisions

From wiki
Jump to navigation Jump to search
imported>Johayek
m (improved formatting)
imported>Johayek
Line 42: Line 42:


=== alien --to-deb ... ===
=== alien --to-deb ... ===
this command line creates a Debian package from an RPM package<br/>
this command line creates a Debian package from an RPM package
(using that e-mail address for the package creator (?)).<br/>
(using that e-mail address for the (local Debian) package maintainer).<br/>
CAVEAT: won't actually work, because creating a Debian package requires running this as root
CAVEAT: won't actually work, because creating a Debian package requires running this as root
<pre>$ env EMAIL='jochen.hayek@COMPANY.com' alien --to-deb --keep-version ...</pre>
<pre>$ env EMAIL='john.doe@COMPANY.com' alien --to-deb --keep-version ...</pre>
some command line parameters can only get passied to "alien" as environment variables.
some command line parameters can only get passied to "alien" as environment variables.



Revision as of 08:48, 20 April 2018

$ sudo apt-get update  # update is used to resynchronize the package index files from their sources
$ sudo apt-get upgrade # upgrade is used to install the newest versions of all packages currently installed on the system from the sources enumerated in /etc/apt/sources.list

dealing with packages files (.deb)

what's the official package name?

$ dpkg --info PACKAGE.deb

which files are included? will be created from this package file?

$ dpkg --contents PACKAGE.deb

...

$ ...

dealing with installed packages

which packages are installed (together with details)?

$ dpkg-query --list

is there an installed package, that sounds like XYZ?

$ dpkg-query --list | fgrep XYZ

details of an installed package (that you know the name of, e.g. PACKAGE)

$ dpkg-query --list PACKAGE

what's the content of an installed package (e.g. PACKAGE)?

$ dpkg-query --listfiles PACKAGE

...

$ ...

rpm2deb

alien --to-deb ...

this command line creates a Debian package from an RPM package (using that e-mail address for the (local Debian) package maintainer).
CAVEAT: won't actually work, because creating a Debian package requires running this as root

$ env EMAIL='john.doe@COMPANY.com' alien --to-deb --keep-version ...

some command line parameters can only get passied to "alien" as environment variables.

fakeroot ...

you do not have root priviliges,
but you need to pretend to have them for achieving certain goals like creating a Debian package:

$ fakeroot --unknown-is-real ...

open questions

  • how to deal with dependencies specified within the RPM package?

history of this article

The blog article got created 1st, but then the content got moved here: