File: README.md

package info (click to toggle)
debbugs 2.6.4
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,800 kB
  • sloc: perl: 19,270; makefile: 81; sh: 75
file content (279 lines) | stat: -rw-r--r-- 9,372 bytes parent folder | download
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
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
# Debbugs #

## Debian Bug-Tracking System ##

********************************

### What is Debbugs? ###

Debbugs is a stable, scaleable bug reporting and issue tracking system. Debbugs has a web interface for viewing and searching issues in the database but unlike other bug tracking systems, Debbugs has no web interface for editing bug reports - all modification is done via email.

The most notable deployment of Debbugs is on the [Debian project](https://www.debian.org/Bugs/)

### System Requirements ###

 * GNU date
 * GNU gzip
 * Perl 5 (5.005 is known to work)
 * Mailtools and MIME-tools perl modules to manipulate email
 * Lynx 2.7 or later
 * The bug system requires its own mail domain. It comes with code
   which understands how exim, qmail and sendmail deliver mail for such a
   domain to a script.
 * A webserver. For the old system of static HTML pages generated for
   bug reports and index pages, this is easiest if the bug system can
   write directly to the webspace; for the new system of CGI scripts
   that generate web pages on the fly, write access is not required.
 * Somewhere to run CGI scripts (unless you don't need the web forms for
   searching for bugs by number, package, maintainer or submitter).

### Where do I get the Source? ###

Debbugs is managed in git. You can clone the repository into your local
workspace as follows:

        git clone http://bugs-master.debian.org/debbugs-source/debbugs.git

Additional branches are available from:

 * [Don Armstrong](http://git.donarmstrong.com/debbugs.git/)

### Installation Instructions ###

Install the Debian package and read `/usr/share/doc/debbugs/README.Debian` file.

If you can't use the `.deb`, do the following:

1.  Clone the repo

        git clone http://bugs-master.debian.org/debbugs-source/debbugs.git

2.  Create version and spool directory

        cd
        mkdir version spool

3.  Optional - Retrieve a partial database of bugs for testing

    1. Get a list of rsync targets from Debbugs

            rsync --list-only rsync://bugs-mirror.debian.org

    2. Grab bugs ending in 00

            mkdir -p spool/db-h/00;
            cd spool/db-h;
            rsync -av rsync://bugs-mirror.debian.org/bts-spool-db/00 .;

4.  Optional - Retrieve bts-versions directory for testing purposes

    The database obtained in step 3 requires associated version and index information.

    1. Pull versions directory

            rsync -av rsync://bugs-mirror.debian.org/bts-versions/ versions/

    2. Pull index directory

            rsync -av rsync://bugs-mirror.debian.org/bts-spool-index index

5.  Configure Debbugs config

    1. Create a config directory for Debbugs

            sudo mkdir /etc/debbugs

    2. Copy sample configuration to config directory

            sudo cp ~/debbugs/scripts/config.debian /etc/debbugs/config

    3. Update the following variables
		* $gConfigDir
		* $gSpoolDir
		* $gIndicesDir
		* $gWebDir
		* $gDocDir
	
	   as follows:

			70,72c70,72
			< $gConfigDir = "/org/bugs.debian.org/etc"; # directory where this file is
			< $gSpoolDir = "/org/bugs.debian.org/spool"; # working directory
			< $gIndicesDir = "/org/bugs.debian.org/indices"; # directory where the indices are
			---
			> $gConfigDir = "/etc/debbugs"; # directory where this file is
			> $gSpoolDir = "/path/to/directory/spool"; # working directory
			> $gIndicesDir = "/path/to/directory/spool/indices"; # directory  where the indices are
			
			74,75c74,75
			< $gWebDir = "/org/bugs.debian.org/www"; # base location of web pages
			< $gDocDir = "/org/ftp.debian.org/ftp/doc"; # location of text doc files
			---
			> $gWebDir = "/path/to/directory/debbugs/html"; # base location of web pages
			> $gDocDir = "/path/to/directory/debbugs/doc"; # location of text doc files

6.  Configure Webserver

    1. Copy example apache config

            sudo cp /path/to/directory/debbugs/examples/apache.conf  /etc/apache2/sites-available/debbugs.conf

    2. Update the directory entries and the DocumentRoot and ScriptAlias variables

		    5c5
		    < DocumentRoot /var/lib/debbugs/www/
			---
		    > DocumentRoot /path/to/directory/debbugs/html/
		
		    10c10
		    < <Directory /var/lib/debbugs/www>
			---
		    > <Directory /path/to/directory/debbugs/html>
		
		    16,17c16,17
		    < ScriptAlias /cgi-bin/ /var/lib/debbugs/www/cgi/
		    < <Directory "/var/lib/debbugs/www/cgi/">
			---
		    > ScriptAlias /cgi-bin/ /path/to/directory/debbugs/cgi/
		    > <Directory "/path/to/directory/debbugs/cgi/">
    
    3. Enable required apache mods
       
            sudo a2enmod rewrite
            sudo a2enmod cgid
    
    4. Install site
       
            sudo a2ensite debbugs
            
    5. Reload apache
    
			sudo service apache2 reload
            
7. Install dependencies

        sudo apt-get install libmailtools-perl ed libmime-tools-perl libio-stringy-perl libmldbm-perl liburi-perl libsoap-lite-perl libcgi-simple-perl libparams-validate-perl libtext-template-perl libsafe-hole-perl libmail-rfc822-address-perl liblist-moreutils-perl libtext-template-perl libfile-libmagic-perl libgravatar-url-perl libwww-perl imagemagick libapache2-mod-perl2
       
8. Set up libraries
   
    1. Create symlinks to link source to their expected locations
       
			sudo mkdir -p /usr/local/lib/site_perl
			sudo ln -s /path/to/directory/debbugs/Debbugs /usr/local/lib/site_perl/
    
			sudo mkdir -p /usr/share/debbugs/
			sudo ln -s /path/to/directory/debbugs/templates /usr/share/debbugs/

9. Create required files
       
    1. Create files
    
            touch /etc/debbugs/pseudo-packages.description
            touch /etc/debbugs/Source_maintainers
            touch /etc/debbugs/pseudo-packages.maintainers
            touch /etc/debbugs/Maintainers
            touch /etc/debbugs/Maintainers.override
            mkdir /etc/debbugs/indices
            touch /etc/debbugs/indices/sources
       
    2. Test
    
            cd /path/to/directory/debbugs
            perl -c cgi/bugreport.cgi
            REQUEST_METHOD=GET QUERY_STRING="bug=775300" perl cgi/bugreport.cgi; 

10. Install MTA. See README.mail for details.

Note that each line of `/etc/debbugs/Maintainers` file needs to be formatted as
follows: 

    package    maintainer name <email@address>

If you need a template, look in `/usr/share/doc/debbugs/examples/` directory.

### How do I contribute to Debbugs? ###
 
#### Debbugs bugs ####

Bugs in debbugs are tracked on the Debian bugtracker. The web interface is available at
[bugs.debian.org](https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=debbugs)

#### Start contributing ####

Make a working branch for your code and check it out to start working:

        git checkout -b example-branch

Stage and commit your changes using appropriate commit messages

        git add example-file

        git commit -m "Created an example file to demonstrate basic git commands."

#### Submitting a Patch ####

Submitting a patch can be done using git format-patch.

For example

        git format-patch origin/master

Creates `.patch` files for all commits since the branch diverged from master.

Debbugs bugs are tracked using debbugs (what else). Patches should therefore be
attached to the bug report for the issue. This can be done by emailing the
`.patch` files to `xxxx@bugs.debian.org` (where xxxx is the bug number).

Feature patches can also be emailed to the maintaining list at 
[Debugs mailing list](debian-debbugs@lists.debian.org)

### Further Information and Assistance ###

#### Email ####

* Mailing List <debian-debbugs@lists.debian.org> 

* To subscribe to the mailing list, email
  <debian-debbugs-request@lists.debian.org> with the word "subscribe" in the
  subject line.

#### Website ####

   * [Code](https://bugs.debian.org/debbugs-source/debbugs.git/)
   * [Debbugs Team](https://wiki.debian.org/Teams/Debbugs)

#### IRC ####

Join the `#debbugs` channel on `irc.oftc.net`

### Developers ###

This bug tracking system was developed by Ian Jackson from 1994-1997,
with assistance from nCipher Corporation Limited in 1997. nCipher allowed
Ian to redistribute modifications he made to the system while working as an
employee of nCipher.

Since then, it has been developed by the various administrators of
`bugs.debian.org`, including Darren Benham, Adam Heath, Josip Rodin, Anthony
Towns, and Colin Watson. As in the case of Ian, nCipher allowed Colin to
redistribute modifications he made while working as an employee of nCipher.

### Copyright and Lack-of-Warranty Notice ###

 * Copyright 1999 Darren O. Benham
 * Copyright 1994-1997 Ian Jackson
 * Copyright 1997,2003 nCipher Corporation Limited

This bug system is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the Free
Software Foundation; version 2 of the License.

This program and documentation is distributed in the hope that it will be
useful, but without any warranty; without even the implied warranty of
merchantability or fitness for a particular purpose. See the GNU General
Public License for more details.

You should have received a copy of the GNU General Public License along
with this program, or one should be available above; if not, write to the
Free Software Foundation, 59 Temple Place - Suite 330, Boston, MA
02111-1307, USA.