summaryrefslogtreecommitdiff
path: root/debian/control
blob: b5a7bb1222cd0e919f998a9624d8501387befd40 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
Source: bugs-everywhere
Section: devel
Priority: extra
Maintainer: Ben Finney <ben+debian@benfinney.id.au>
Homepage: http://bugseverywhere.org/
VCS-bzr: http://bzr.debian.org/bzr/collab-maint/bugs-everywhere/bugs-everywhere.debian/
VCS-Browser: http://bzr.debian.org/loggerhead/collab-maint/bugs-everywhere/bugs-everywhere.debian/
Build-Depends-Indep: debhelper (>= 7.0.50),
    docbook-to-man,
    python-support (>= 0.90),
    python-numpydoc,
    python
Standards-Version: 3.9.4

Package: bugs-everywhere
Architecture: all
Depends: ${python:Depends}, ${misc:Depends}
Provides: ${python:Provides}
Recommends:
    bzr |
    git-core |
    mercurial |
    tla | bazaar |
    rcs
Description: distributed bug tracking system using VCS storage
 Bugs Everywhere is a “distributed bug tracker”, designed to
 complement a distributed version control system (VCS). By using a
 distributed VCS as a back-end for bug state, it gains several
 convenient features:
 .
  * Bugs and code that live on branches are tracked together.
  * Users can fully modify bug state while offline.
  * When a user checks out a project’s source code, she gets the current
    bug state for free.
  * A web interface to the bug database becomes just another client that
    merges with the main repository.
 .
 Bugs Everywhere currently supports the following VCS back-ends:
 .
  * GNU Arch (tla, baz)
  * Bazaar (bzr)
  * git
  * Mercurial (hg)
  * GNU RCS