To request membership to this group, please go on our Alioth pages:

Remember that you must have an Alioth account before requesting membership (see here to request an Alioth account).

• pkg-mono - wsvn or viewsvn;

• pkg-cli-apps - wsvn or viewsvn;

• pkg-cli-libs - wsvn or viewsvn;

To check sources out from SVN, please do:

Another way to check the sources is through the use of the debcheckout command, from the devscripts package.

The SVN repositories are structured as follows:

If you intent to work on a Debian package you should follow the normal Debian rules and file a WNPP bug report.

It is a good idea to keep the mailing list pkg-mono-devel@lists.aliothdebian.org in CC and to set it as the owner of the ITP to keep your co-workers informed. This will ensure that we notice if for some reason the package has not been uploaded, when the ITP bug is automatically closed one year later.

We use the proposed machine-readable format for the debian/copyright file. Please list yourself in the Files: debian/* section if you think that your contributions are not trivial and therefore subjected to copyright. Please chose a license that is compatible with the program you package. You can also use “same as if it were in the public domain” or “same as the packaged program itself”.

Packages hosted in our Subversion repositories, that have been modified but not uploaded must use UNRELEASED as a distribution name. This can be done automatically by declaring DEBCHANGE_RELEASE_HEURISTIC=changelog in ~/.devscripts and using dch.

Also, the first-level indentation is represented by a *. The second-level indentation starts with a +, while the third-level with a -. The indentation must be of two spaces to the right with regard to the level just above.

Debhelper uses compatibility levels to control the behaviour of its commands. The latest level is not always available in Stable or Backports. Please avoid using it unless needed until it is available, to facilitate backporting. We currently recommend to use the level 6.

The use of CDBS is welcome as it helps us to factorize our code. Nevertheless, please do not use complex CDBS for non-trivial packages, so that other developers can quickly understand the package when doing QA work.

It is technically possible to build CDBS packages using Debhelper without the debian/compat file. Please do not, and always include such a file according to the above guidelines.

To inject a new package to the SVN repositories, you must have write access to it; i.e. you must be a member of pkg-mono, pkg-cli-apps or pkg-cli-libs groups on Alioth.

You can inject a new package only after successfully building it with dpkg-buildpackage (or any wrapper around it). We use the MergeWithUpstream workflow, so please keep all the modifications in the debian directory, and use the -o of svn-buildpackage, as in the following example:

(the ... used in the URL above should be the parent directory of where other <package> directories are: that is: / for pkg-mono, and packages/ for pkg-cli-apps and pkg-cli-libs).

The svn-inject command is found in the svn-buildpackage package (just apt-get it).

To build the package, just use the tools that svn-buildpackage carries. First of all, we suggest you to define some aliases for the most common commands:

Checkout the sources (see the proper section).

Once done, you're ready to do the work. First, cd to the trunk directory, and download the upstream sources (if there is a debian/watch file):

Alternatively, you can try this, it depends on how the package was built (again, from the trunk/ directory):

Once done, edit the files you need, and then build the package with svn-b or svn-br.

If you're a team member, you can commit your changes:

(also svn ci).

Otherwise, you can ask to be added to the group (see the Membership section), or send the result of svn diff to the mailing list (gzip -9 it, if it's too large).

It may happen that a package version has been uploaded to Debian repositories, and you forgot to tag the last build with

You can tag this package also retroactively. A first step, creating the tags directory, can be achieved in two ways:

After the tags directory has been created, you're ready to tag the package:

(--svn-no-autodch avoids debian/changelog to be marked as UNRELEASED).

Often happens that the upstream code doesn't fit well into the Debian distribution: be this wrong paths, missing features, anything that implies editing the source files. When you directly edit upstream's source files, your changes will be put into a .diff.gz file, which should instead contain only debian. To better organise the patches and group the by function, please use a patch handling system which keeps patches under the debian/patches directory.

The most known are quilt, simple-patchsys (from the CDBS package) and dpatch. Please don't use any other patch system in our team, unless absolutely necessary.