Debian Packaging
From SystemImager
The SystemImager Debian packages are up for adoption. This means that the current maintainer is still doing basic maintenance work, but is looking for someone to take over. He is hoping to smoothly transition the work to a new person (or hopefully team of persons) to take over the work.
Contents |
Accessing the Repository
Debian packaging for SystemImager is hosted on http://svn.systemimager.org. The latest bits are in the trunk directory, branches for older releases are in the branches directory.
How to contribute patches
For packages that exist in Debian, you can report issues in the Debian Bug Tracking System. If you are interested in helping prepare the next major release, please report issues to the sisuite-devel list.
Patches are greatly appreciated, and should comply with the following guidelines:
- Patches should be against the latest svn tree. The systemimager-debian repository follows the same conventions as many other group-maintained Debian packages (debian-installer, debian-kernel, etc), so if you've worked with any of these other projects you should be able to jump right in.
- Patches should be standard unified diffs (e.g., svn diff or diff -urpN systemimager-3.6.3.orig systemimager-3.6.3)
- Each patch should do one type of thing (e.g., upgrade to a new kernel version, fix a bug in si_prepareclient, add a new package, etc). Touching multiple files is perfectly ok. However, you should avoid doing multiple things with a single patch - e.g., don't upgrade to a new kernel version and a new e2fsprogs version in the same patch.
- In most cases, your patch should add a line to debian/changelog that describes your change. dch -a helps here.
If you're confused by any of the above - don't let that prevent you from sending your change! People on the list are happy to help work with you to create a clean patch.
Why aren't unstable/devel releases of SystemImager in Debian?
Upstream has requested that only "stable" versions of SystemImager enter a Debian (experimental included).
Why Debian Packages use a Different Kernel
Debian tries to restrict the number of version of kernel source that exist in a stable release to one in order to reduce duplicating maintenance work (bug fixes, security patches, legal cleanups etc). Therefore, the Debian packages try to track the official Debian kernel source.
