Differences between revisions 28 and 29
Revision 28 as of 2014-03-31 15:52:38
Size: 2751
Editor: ?IntRigeri
Comment: Add note about Gitweb still broken.
Revision 29 as of 2014-03-31 20:04:16
Size: 2709
Editor: ?IntRigeri
Comment: Git repos can now be browsed on the web.
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 * '''[[http://anonscm.debian.org/gitweb/?a=project_list;pf=pkg-otr|Git repositories]]''' (broken, waiting action by Alioth admins)  * '''[[http://anonscm.debian.org/gitweb/?a=project_list;pf=pkg-otr|Git repositories]]'''

Debian OTR team

Infrastructure

Interacting with the team

Task description

The Debian OTR team maintains packages related to Off-the-Record Messaging.

Get involved

Developers

Help squash bugs

Have a look on the bug tracker if you want to help squash bugs from various OTR projects. If you would like to do this long-term, we encourage you to subscribe to the mailing-list.

Bug Triagers

Triaging OTR bugs is welcome!

Users

Reporting bugs

We like to fix bugs in OTR software. If it's not Debian specific, we'll forward it to upstream. An example of a bug email can be found below.

  To: submit@bugs.debian.org
  From: diligent@testing.linux.org
  Subject: Pidgin-otr crashes when receiving "NULL" in the OTR version handler

  Package: pidgin-otr
  Version: 3.2.1-3+deb7u1

  When Bob starts an OTR conversation with Alice and sends Alice an OTR version 
  handler with a "NULL", Pidgin-OTR as a plugin crashes. 

  Here is my GDB output:

  <output>

  I suggest that "NULL" be caught in a signal handler.

  I am using Debian GNU/Linux 7, kernel 3.2.0-4-amd64
  and libc6 2.13-38+deb7u1.

Tools and processes

  • We are maintaining the packaging in Git with git-buildpackage and pristine-tar.
  • Whenever possible, use the upstream signed Git tag as the canonical upstream release, and generate the tarball ourselves.
  • We are using source format 3.0 (quilt).
  • We don't apply patches to the upstream source that have not been submitted upstream yet.