Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
aboutsummaryrefslogtreecommitdiff
path: root/docs/en/html/Bugzilla-Guide.html
blob: 0cd0ae530e444698d67e35ce1be4fcdc9a6578dc (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
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
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071
5072
5073
5074
5075
5076
5077
5078
5079
5080
5081
5082
5083
5084
5085
5086
5087
5088
5089
5090
5091
5092
5093
5094
5095
5096
5097
5098
5099
5100
5101
5102
5103
5104
5105
5106
5107
5108
5109
5110
5111
5112
5113
5114
5115
5116
5117
5118
5119
5120
5121
5122
5123
5124
5125
5126
5127
5128
5129
5130
5131
5132
5133
5134
5135
5136
5137
5138
5139
5140
5141
5142
5143
5144
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163
5164
5165
5166
5167
5168
5169
5170
5171
5172
5173
5174
5175
5176
5177
5178
5179
5180
5181
5182
5183
5184
5185
5186
5187
5188
5189
5190
5191
5192
5193
5194
5195
5196
5197
5198
5199
5200
5201
5202
5203
5204
5205
5206
5207
5208
5209
5210
5211
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221
5222
5223
5224
5225
5226
5227
5228
5229
5230
5231
5232
5233
5234
5235
5236
5237
5238
5239
5240
5241
5242
5243
5244
5245
5246
5247
5248
5249
5250
5251
5252
5253
5254
5255
5256
5257
5258
5259
5260
5261
5262
5263
5264
5265
5266
5267
5268
5269
5270
5271
5272
5273
5274
5275
5276
5277
5278
5279
5280
5281
5282
5283
5284
5285
5286
5287
5288
5289
5290
5291
5292
5293
5294
5295
5296
5297
5298
5299
5300
5301
5302
5303
5304
5305
5306
5307
5308
5309
5310
5311
5312
5313
5314
5315
5316
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337
5338
5339
5340
5341
5342
5343
5344
5345
5346
5347
5348
5349
5350
5351
5352
5353
5354
5355
5356
5357
5358
5359
5360
5361
5362
5363
5364
5365
5366
5367
5368
5369
5370
5371
5372
5373
5374
5375
5376
5377
5378
5379
5380
5381
5382
5383
5384
5385
5386
5387
5388
5389
5390
5391
5392
5393
5394
5395
5396
5397
5398
5399
5400
5401
5402
5403
5404
5405
5406
5407
5408
5409
5410
5411
5412
5413
5414
5415
5416
5417
5418
5419
5420
5421
5422
5423
5424
5425
5426
5427
5428
5429
5430
5431
5432
5433
5434
5435
5436
5437
5438
5439
5440
5441
5442
5443
5444
5445
5446
5447
5448
5449
5450
5451
5452
5453
5454
5455
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484
5485
5486
5487
5488
5489
5490
5491
5492
5493
5494
5495
5496
5497
5498
5499
5500
5501
5502
5503
5504
5505
5506
5507
5508
5509
5510
5511
5512
5513
5514
5515
5516
5517
5518
5519
5520
5521
5522
5523
5524
5525
5526
5527
5528
5529
5530
5531
5532
5533
5534
5535
5536
5537
5538
5539
5540
5541
5542
5543
5544
5545
5546
5547
5548
5549
5550
5551
5552
5553
5554
5555
5556
5557
5558
5559
5560
5561
5562
5563
5564
5565
5566
5567
5568
5569
5570
5571
5572
5573
5574
5575
5576
5577
5578
5579
5580
5581
5582
5583
5584
5585
5586
5587
5588
5589
5590
5591
5592
5593
5594
5595
5596
5597
5598
5599
5600
5601
5602
5603
5604
5605
5606
5607
5608
5609
5610
5611
5612
5613
5614
5615
5616
5617
5618
5619
5620
5621
5622
5623
5624
5625
5626
5627
5628
5629
5630
5631
5632
5633
5634
5635
5636
5637
5638
5639
5640
5641
5642
5643
5644
5645
5646
5647
5648
5649
5650
5651
5652
5653
5654
5655
5656
5657
5658
5659
5660
5661
5662
5663
5664
5665
5666
5667
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
5680
5681
5682
5683
5684
5685
5686
5687
5688
5689
5690
5691
5692
5693
5694
5695
5696
5697
5698
5699
5700
5701
5702
5703
5704
5705
5706
5707
5708
5709
5710
5711
5712
5713
5714
5715
5716
5717
5718
5719
5720
5721
5722
5723
5724
5725
5726
5727
5728
5729
5730
5731
5732
5733
5734
5735
5736
5737
5738
5739
5740
5741
5742
5743
5744
5745
5746
5747
5748
5749
5750
5751
5752
5753
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764
5765
5766
5767
5768
5769
5770
5771
5772
5773
5774
5775
5776
5777
5778
5779
5780
5781
5782
5783
5784
5785
5786
5787
5788
5789
5790
5791
5792
5793
5794
5795
5796
5797
5798
5799
5800
5801
5802
5803
5804
5805
5806
5807
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820
5821
5822
5823
5824
5825
5826
5827
5828
5829
5830
5831
5832
5833
5834
5835
5836
5837
5838
5839
5840
5841
5842
5843
5844
5845
5846
5847
5848
5849
5850
5851
5852
5853
5854
5855
5856
5857
5858
5859
5860
5861
5862
5863
5864
5865
5866
5867
5868
5869
5870
5871
5872
5873
5874
5875
5876
5877
5878
5879
5880
5881
5882
5883
5884
5885
5886
5887
5888
5889
5890
5891
5892
5893
5894
5895
5896
5897
5898
5899
5900
5901
5902
5903
5904
5905
5906
5907
5908
5909
5910
5911
5912
5913
5914
5915
5916
5917
5918
5919
5920
5921
5922
5923
5924
5925
5926
5927
5928
5929
5930
5931
5932
5933
5934
5935
5936
5937
5938
5939
5940
5941
5942
5943
5944
5945
5946
5947
5948
5949
5950
5951
5952
5953
5954
5955
5956
5957
5958
5959
5960
5961
5962
5963
5964
5965
5966
5967
5968
5969
5970
5971
5972
5973
5974
5975
5976
5977
5978
5979
5980
5981
5982
5983
5984
5985
5986
5987
5988
5989
5990
5991
5992
5993
5994
5995
5996
5997
5998
5999
6000
6001
6002
6003
6004
6005
6006
6007
6008
6009
6010
6011
6012
6013
6014
6015
6016
6017
6018
6019
6020
6021
6022
6023
6024
6025
6026
6027
6028
6029
6030
6031
6032
6033
6034
6035
6036
6037
6038
6039
6040
6041
6042
6043
6044
6045
6046
6047
6048
6049
6050
6051
6052
6053
6054
6055
6056
6057
6058
6059
6060
6061
6062
6063
6064
6065
6066
6067
6068
6069
6070
6071
6072
6073
6074
6075
6076
6077
6078
6079
6080
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091
6092
6093
6094
6095
6096
6097
6098
6099
6100
6101
6102
6103
6104
6105
6106
6107
6108
6109
6110
6111
6112
6113
6114
6115
6116
6117
6118
6119
6120
6121
6122
6123
6124
6125
6126
6127
6128
6129
6130
6131
6132
6133
6134
6135
6136
6137
6138
6139
6140
6141
6142
6143
6144
6145
6146
6147
6148
6149
6150
6151
6152
6153
6154
6155
6156
6157
6158
6159
6160
6161
6162
6163
6164
6165
6166
6167
6168
6169
6170
6171
6172
6173
6174
6175
6176
6177
6178
6179
6180
6181
6182
6183
6184
6185
6186
6187
6188
6189
6190
6191
6192
6193
6194
6195
6196
6197
6198
6199
6200
6201
6202
6203
6204
6205
6206
6207
6208
6209
6210
6211
6212
6213
6214
6215
6216
6217
6218
6219
6220
6221
6222
6223
6224
6225
6226
6227
6228
6229
6230
6231
6232
6233
6234
6235
6236
6237
6238
6239
6240
6241
6242
6243
6244
6245
6246
6247
6248
6249
6250
6251
6252
6253
6254
6255
6256
6257
6258
6259
6260
6261
6262
6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
6273
6274
6275
6276
6277
6278
6279
6280
6281
6282
6283
6284
6285
6286
6287
6288
6289
6290
6291
6292
6293
6294
6295
6296
6297
6298
6299
6300
6301
6302
6303
6304
6305
6306
6307
6308
6309
6310
6311
6312
6313
6314
6315
6316
6317
6318
6319
6320
6321
6322
6323
6324
6325
6326
6327
6328
6329
6330
6331
6332
6333
6334
6335
6336
6337
6338
6339
6340
6341
6342
6343
6344
6345
6346
6347
6348
6349
6350
6351
6352
6353
6354
6355
6356
6357
6358
6359
6360
6361
6362
6363
6364
6365
6366
6367
6368
6369
6370
6371
6372
6373
6374
6375
6376
6377
6378
6379
6380
6381
6382
6383
6384
6385
6386
6387
6388
6389
6390
6391
6392
6393
6394
6395
6396
6397
6398
6399
6400
6401
6402
6403
6404
6405
6406
6407
6408
6409
6410
6411
6412
6413
6414
6415
6416
6417
6418
6419
6420
6421
6422
6423
6424
6425
6426
6427
6428
6429
6430
6431
6432
6433
6434
6435
6436
6437
6438
6439
6440
6441
6442
6443
6444
6445
6446
6447
6448
6449
6450
6451
6452
6453
6454
6455
6456
6457
6458
6459
6460
6461
6462
6463
6464
6465
6466
6467
6468
6469
6470
6471
6472
6473
6474
6475
6476
6477
6478
6479
6480
6481
6482
6483
6484
6485
6486
6487
6488
6489
6490
6491
6492
6493
6494
6495
6496
6497
6498
6499
6500
6501
6502
6503
6504
6505
6506
6507
6508
6509
6510
6511
6512
6513
6514
6515
6516
6517
6518
6519
6520
6521
6522
6523
6524
6525
6526
6527
6528
6529
6530
6531
6532
6533
6534
6535
6536
6537
6538
6539
6540
6541
6542
6543
6544
6545
6546
6547
6548
6549
6550
6551
6552
6553
6554
6555
6556
6557
6558
6559
6560
6561
6562
6563
6564
6565
6566
6567
6568
6569
6570
6571
6572
6573
6574
6575
6576
6577
6578
6579
6580
6581
6582
6583
6584
6585
6586
6587
6588
6589
6590
6591
6592
6593
6594
6595
6596
6597
6598
6599
6600
6601
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613
6614
6615
6616
6617
6618
6619
6620
6621
6622
6623
6624
6625
6626
6627
6628
6629
6630
6631
6632
6633
6634
6635
6636
6637
6638
6639
6640
6641
6642
6643
6644
6645
6646
6647
6648
6649
6650
6651
6652
6653
6654
6655
6656
6657
6658
6659
6660
6661
6662
6663
6664
6665
6666
6667
6668
6669
6670
6671
6672
6673
6674
6675
6676
6677
6678
6679
6680
6681
6682
6683
6684
6685
6686
6687
6688
6689
6690
6691
6692
6693
6694
6695
6696
6697
6698
6699
6700
6701
6702
6703
6704
6705
6706
6707
6708
6709
6710
6711
6712
6713
6714
6715
6716
6717
6718
6719
6720
6721
6722
6723
6724
6725
6726
6727
6728
6729
6730
6731
6732
6733
6734
6735
6736
6737
6738
6739
6740
6741
6742
6743
6744
6745
6746
6747
6748
6749
6750
6751
6752
6753
6754
6755
6756
6757
6758
6759
6760
6761
6762
6763
6764
6765
6766
6767
6768
6769
6770
6771
6772
6773
6774
6775
6776
6777
6778
6779
6780
6781
6782
6783
6784
6785
6786
6787
6788
6789
6790
6791
6792
6793
6794
6795
6796
6797
6798
6799
6800
6801
6802
6803
6804
6805
6806
6807
6808
6809
6810
6811
6812
6813
6814
6815
6816
6817
6818
6819
6820
6821
6822
6823
6824
6825
6826
6827
6828
6829
6830
6831
6832
6833
6834
6835
6836
6837
6838
6839
6840
6841
6842
6843
6844
6845
6846
6847
6848
6849
6850
6851
6852
6853
6854
6855
6856
6857
6858
6859
6860
6861
6862
6863
6864
6865
6866
6867
6868
6869
6870
6871
6872
6873
6874
6875
6876
6877
6878
6879
6880
6881
6882
6883
6884
6885
6886
6887
6888
6889
6890
6891
6892
6893
6894
6895
6896
6897
6898
6899
6900
6901
6902
6903
6904
6905
6906
6907
6908
6909
6910
6911
6912
6913
6914
6915
6916
6917
6918
6919
6920
6921
6922
6923
6924
6925
6926
6927
6928
6929
6930
6931
6932
6933
6934
6935
6936
6937
6938
6939
6940
6941
6942
6943
6944
6945
6946
6947
6948
6949
6950
6951
6952
6953
6954
6955
6956
6957
6958
6959
6960
6961
6962
6963
6964
6965
6966
6967
6968
6969
6970
6971
6972
6973
6974
6975
6976
6977
6978
6979
6980
6981
6982
6983
6984
6985
6986
6987
6988
6989
6990
6991
6992
6993
6994
6995
6996
6997
6998
6999
7000
7001
7002
7003
7004
7005
7006
7007
7008
7009
7010
7011
7012
7013
7014
7015
7016
7017
7018
7019
7020
7021
7022
7023
7024
7025
7026
7027
7028
7029
7030
7031
7032
7033
7034
7035
7036
7037
7038
7039
7040
7041
7042
7043
7044
7045
7046
7047
7048
7049
7050
7051
7052
7053
7054
7055
7056
7057
7058
7059
7060
7061
7062
7063
7064
7065
7066
7067
7068
7069
7070
7071
7072
7073
7074
7075
7076
7077
7078
7079
7080
7081
7082
7083
7084
7085
7086
7087
7088
7089
7090
7091
7092
7093
7094
7095
7096
7097
7098
7099
7100
7101
7102
7103
7104
7105
7106
7107
7108
7109
7110
7111
7112
7113
7114
7115
7116
7117
7118
7119
7120
7121
7122
7123
7124
7125
7126
7127
7128
7129
7130
7131
7132
7133
7134
7135
7136
7137
7138
7139
7140
7141
7142
7143
7144
7145
7146
7147
7148
7149
7150
7151
7152
7153
7154
7155
7156
7157
7158
7159
7160
7161
7162
7163
7164
7165
7166
7167
7168
7169
7170
7171
7172
7173
7174
7175
7176
7177
7178
7179
7180
7181
7182
7183
7184
7185
7186
7187
7188
7189
7190
7191
7192
7193
7194
7195
7196
7197
7198
7199
7200
7201
7202
7203
7204
7205
7206
7207
7208
7209
7210
7211
7212
7213
7214
7215
7216
7217
7218
7219
7220
7221
7222
7223
7224
7225
7226
7227
7228
7229
7230
7231
7232
7233
7234
7235
7236
7237
7238
7239
7240
7241
7242
7243
7244
7245
7246
7247
7248
7249
7250
7251
7252
7253
7254
7255
7256
7257
7258
7259
7260
7261
7262
7263
7264
7265
7266
7267
7268
7269
7270
7271
7272
7273
7274
7275
7276
7277
7278
7279
7280
7281
7282
7283
7284
7285
7286
7287
7288
7289
7290
7291
7292
7293
7294
7295
7296
7297
7298
7299
7300
7301
7302
7303
7304
7305
7306
7307
7308
7309
7310
7311
7312
7313
7314
7315
7316
7317
7318
7319
7320
7321
7322
7323
7324
7325
7326
7327
7328
7329
7330
7331
7332
7333
7334
7335
7336
7337
7338
7339
7340
7341
7342
7343
7344
7345
7346
7347
7348
7349
7350
7351
7352
7353
7354
7355
7356
7357
7358
7359
7360
7361
7362
7363
7364
7365
7366
7367
7368
7369
7370
7371
7372
7373
7374
7375
7376
7377
7378
7379
7380
7381
7382
7383
7384
7385
7386
7387
7388
7389
7390
7391
7392
7393
7394
7395
7396
7397
7398
7399
7400
7401
7402
7403
7404
7405
7406
7407
7408
7409
7410
7411
7412
7413
7414
7415
7416
7417
7418
7419
7420
7421
7422
7423
7424
7425
7426
7427
7428
7429
7430
7431
7432
7433
7434
7435
7436
7437
7438
7439
7440
7441
7442
7443
7444
7445
7446
7447
7448
7449
7450
7451
7452
7453
7454
7455
7456
7457
7458
7459
7460
7461
7462
7463
7464
7465
7466
7467
7468
7469
7470
7471
7472
7473
7474
7475
7476
7477
7478
7479
7480
7481
7482
7483
7484
7485
7486
7487
7488
7489
7490
7491
7492
7493
7494
7495
7496
7497
7498
7499
7500
7501
7502
7503
7504
7505
7506
7507
7508
7509
7510
7511
7512
7513
7514
7515
7516
7517
7518
7519
7520
7521
7522
7523
7524
7525
7526
7527
7528
7529
7530
7531
7532
7533
7534
7535
7536
7537
7538
7539
7540
7541
7542
7543
7544
7545
7546
7547
7548
7549
7550
7551
7552
7553
7554
7555
7556
7557
7558
7559
7560
7561
7562
7563
7564
7565
7566
7567
7568
7569
7570
7571
7572
7573
7574
7575
7576
7577
7578
7579
7580
7581
7582
7583
7584
7585
7586
7587
7588
7589
7590
7591
7592
7593
7594
7595
7596
7597
7598
7599
7600
7601
7602
7603
7604
7605
7606
7607
7608
7609
7610
7611
7612
7613
7614
7615
7616
7617
7618
7619
7620
7621
7622
7623
7624
7625
7626
7627
7628
7629
7630
7631
7632
7633
7634
7635
7636
7637
7638
7639
7640
7641
7642
7643
7644
7645
7646
7647
7648
7649
7650
7651
7652
7653
7654
7655
7656
7657
7658
7659
7660
7661
7662
7663
7664
7665
7666
7667
7668
7669
7670
7671
7672
7673
7674
7675
7676
7677
7678
7679
7680
7681
7682
7683
7684
7685
7686
7687
7688
7689
7690
7691
7692
7693
7694
7695
7696
7697
7698
7699
7700
7701
7702
7703
7704
7705
7706
7707
7708
7709
7710
7711
7712
7713
7714
7715
7716
7717
7718
7719
7720
7721
7722
7723
7724
7725
7726
7727
7728
7729
7730
7731
7732
7733
7734
7735
7736
7737
7738
7739
7740
7741
7742
7743
7744
7745
7746
7747
7748
7749
7750
7751
7752
7753
7754
7755
7756
7757
7758
7759
7760
7761
7762
7763
7764
7765
7766
7767
7768
7769
7770
7771
7772
7773
7774
7775
7776
7777
7778
7779
7780
7781
7782
7783
7784
7785
7786
7787
7788
7789
7790
7791
7792
7793
7794
7795
7796
7797
7798
7799
7800
7801
7802
7803
7804
7805
7806
7807
7808
7809
7810
7811
7812
7813
7814
7815
7816
7817
7818
7819
7820
7821
7822
7823
7824
7825
7826
7827
7828
7829
7830
7831
7832
7833
7834
7835
7836
7837
7838
7839
7840
7841
7842
7843
7844
7845
7846
7847
7848
7849
7850
7851
7852
7853
7854
7855
7856
7857
7858
7859
7860
7861
7862
7863
7864
7865
7866
7867
7868
7869
7870
7871
7872
7873
7874
7875
7876
7877
7878
7879
7880
7881
7882
7883
7884
7885
7886
7887
7888
7889
7890
7891
7892
7893
7894
7895
7896
7897
7898
7899
7900
7901
7902
7903
7904
7905
7906
7907
7908
7909
7910
7911
7912
7913
7914
7915
7916
7917
7918
7919
7920
7921
7922
7923
7924
7925
7926
7927
7928
7929
7930
7931
7932
7933
7934
7935
7936
7937
7938
7939
7940
7941
7942
7943
7944
7945
7946
7947
7948
7949
7950
7951
7952
7953
7954
7955
7956
7957
7958
7959
7960
7961
7962
7963
7964
7965
7966
7967
7968
7969
7970
7971
7972
7973
7974
7975
7976
7977
7978
7979
7980
7981
7982
7983
7984
7985
7986
7987
7988
7989
7990
7991
7992
7993
7994
7995
7996
7997
7998
7999
8000
8001
8002
8003
8004
8005
8006
8007
8008
8009
8010
8011
8012
8013
8014
8015
8016
8017
8018
8019
8020
8021
8022
8023
8024
8025
8026
8027
8028
8029
8030
8031
8032
8033
8034
8035
8036
8037
8038
8039
8040
8041
8042
8043
8044
8045
8046
8047
8048
8049
8050
8051
8052
8053
8054
8055
8056
8057
8058
8059
8060
8061
8062
8063
8064
8065
8066
8067
8068
8069
8070
8071
8072
8073
8074
8075
8076
8077
8078
8079
8080
8081
8082
8083
8084
8085
8086
8087
8088
8089
8090
8091
8092
8093
8094
8095
8096
8097
8098
8099
8100
8101
8102
8103
8104
8105
8106
8107
8108
8109
8110
8111
8112
8113
8114
8115
8116
8117
8118
8119
8120
8121
8122
8123
8124
8125
8126
8127
8128
8129
8130
8131
8132
8133
8134
8135
8136
8137
8138
8139
8140
8141
8142
8143
8144
8145
8146
8147
8148
8149
8150
8151
8152
8153
8154
8155
8156
8157
8158
8159
8160
8161
8162
8163
8164
8165
8166
8167
8168
8169
8170
8171
8172
8173
8174
8175
8176
8177
8178
8179
8180
8181
8182
8183
8184
8185
8186
8187
8188
8189
8190
8191
8192
8193
8194
8195
8196
8197
8198
8199
8200
8201
8202
8203
8204
8205
8206
8207
8208
8209
8210
8211
8212
8213
8214
8215
8216
8217
8218
8219
8220
8221
8222
8223
8224
8225
8226
8227
8228
8229
8230
8231
8232
8233
8234
8235
8236
8237
8238
8239
8240
8241
8242
8243
8244
8245
8246
8247
8248
8249
8250
8251
8252
8253
8254
8255
8256
8257
8258
8259
8260
8261
8262
8263
8264
8265
8266
8267
8268
8269
8270
8271
8272
8273
8274
8275
8276
8277
8278
8279
8280
8281
8282
8283
8284
8285
8286
8287
8288
8289
8290
8291
8292
8293
8294
8295
8296
8297
8298
8299
8300
8301
8302
8303
8304
8305
8306
8307
8308
8309
8310
8311
8312
8313
8314
8315
8316
8317
8318
8319
8320
8321
8322
8323
8324
8325
8326
8327
8328
8329
8330
8331
8332
8333
8334
8335
8336
8337
8338
8339
8340
8341
8342
8343
8344
8345
8346
8347
8348
8349
8350
8351
8352
8353
8354
8355
8356
8357
8358
8359
8360
8361
8362
8363
8364
8365
8366
8367
8368
8369
8370
8371
8372
8373
8374
8375
8376
8377
8378
8379
8380
8381
8382
8383
8384
8385
8386
8387
8388
8389
8390
8391
8392
8393
8394
8395
8396
8397
8398
8399
8400
8401
8402
8403
8404
8405
8406
8407
8408
8409
8410
8411
8412
8413
8414
8415
8416
8417
8418
8419
8420
8421
8422
8423
8424
8425
8426
8427
8428
8429
8430
8431
8432
8433
8434
8435
8436
8437
8438
8439
8440
8441
8442
8443
8444
8445
8446
8447
8448
8449
8450
8451
8452
8453
8454
8455
8456
8457
8458
8459
8460
8461
8462
8463
8464
8465
8466
8467
8468
8469
8470
8471
8472
8473
8474
8475
8476
8477
8478
8479
8480
8481
8482
8483
8484
8485
8486
8487
8488
8489
8490
8491
8492
8493
8494
8495
8496
8497
8498
8499
8500
8501
8502
8503
8504
8505
8506
8507
8508
8509
8510
8511
8512
8513
8514
8515
8516
8517
8518
8519
8520
8521
8522
8523
8524
8525
8526
8527
8528
8529
8530
8531
8532
8533
8534
8535
8536
8537
8538
8539
8540
8541
8542
8543
8544
8545
8546
8547
8548
8549
8550
8551
8552
8553
8554
8555
8556
8557
8558
8559
8560
8561
8562
8563
8564
8565
8566
8567
8568
8569
8570
8571
8572
8573
8574
8575
8576
8577
8578
8579
8580
8581
8582
8583
8584
8585
8586
8587
8588
8589
8590
8591
8592
8593
8594
8595
8596
8597
8598
8599
8600
8601
8602
8603
8604
8605
8606
8607
8608
8609
8610
8611
8612
8613
8614
8615
8616
8617
8618
8619
8620
8621
8622
8623
8624
8625
8626
8627
8628
8629
8630
8631
8632
8633
8634
8635
8636
8637
8638
8639
8640
8641
8642
8643
8644
8645
8646
8647
8648
8649
8650
8651
8652
8653
8654
8655
8656
8657
8658
8659
8660
8661
8662
8663
8664
8665
8666
8667
8668
8669
8670
8671
8672
8673
8674
8675
8676
8677
8678
8679
8680
8681
8682
8683
8684
8685
8686
8687
8688
8689
8690
8691
8692
8693
8694
8695
8696
8697
8698
8699
8700
8701
8702
8703
8704
8705
8706
8707
8708
8709
8710
8711
8712
8713
8714
8715
8716
8717
8718
8719
8720
8721
8722
8723
8724
8725
8726
8727
8728
8729
8730
8731
8732
8733
8734
8735
8736
8737
8738
8739
8740
8741
8742
8743
8744
8745
8746
8747
8748
8749
8750
8751
8752
8753
8754
8755
8756
8757
8758
8759
8760
8761
8762
8763
8764
8765
8766
8767
8768
8769
8770
8771
8772
8773
8774
8775
8776
8777
8778
8779
8780
8781
8782
8783
8784
8785
8786
8787
8788
8789
8790
8791
8792
8793
8794
8795
8796
8797
8798
8799
8800
8801
8802
8803
8804
8805
8806
8807
8808
8809
8810
8811
8812
8813
8814
8815
8816
8817
8818
8819
8820
8821
8822
8823
8824
8825
8826
8827
8828
8829
8830
8831
8832
8833
8834
8835
8836
8837
8838
8839
8840
8841
8842
8843
8844
8845
8846
8847
8848
8849
8850
8851
8852
8853
8854
8855
8856
8857
8858
8859
8860
8861
8862
8863
8864
8865
8866
8867
8868
8869
8870
8871
8872
8873
8874
8875
8876
8877
8878
8879
8880
8881
8882
8883
8884
8885
8886
8887
8888
8889
8890
8891
8892
8893
8894
8895
8896
8897
8898
8899
8900
8901
8902
8903
8904
8905
8906
8907
8908
8909
8910
8911
8912
8913
8914
8915
8916
8917
8918
8919
8920
8921
8922
8923
8924
8925
8926
8927
8928
8929
8930
8931
8932
8933
8934
8935
8936
8937
8938
8939
8940
8941
8942
8943
8944
8945
8946
8947
8948
8949
8950
8951
8952
8953
8954
8955
8956
8957
8958
8959
8960
8961
8962
8963
8964
8965
8966
8967
8968
8969
8970
8971
8972
8973
8974
8975
8976
8977
8978
8979
8980
8981
8982
8983
8984
8985
8986
8987
8988
8989
8990
8991
8992
8993
8994
8995
8996
8997
8998
8999
9000
9001
9002
9003
9004
9005
9006
9007
9008
9009
9010
9011
9012
9013
9014
9015
9016
9017
9018
9019
9020
9021
9022
9023
9024
9025
9026
9027
9028
9029
9030
9031
9032
9033
9034
9035
9036
9037
9038
9039
9040
9041
9042
9043
9044
9045
9046
9047
9048
9049
9050
9051
9052
9053
9054
9055
9056
9057
9058
9059
9060
9061
9062
9063
9064
9065
9066
9067
9068
9069
9070
9071
9072
9073
9074
9075
9076
9077
9078
9079
9080
9081
9082
9083
9084
9085
9086
9087
9088
9089
9090
9091
9092
9093
9094
9095
9096
9097
9098
9099
9100
9101
9102
9103
9104
9105
9106
9107
9108
9109
9110
9111
9112
9113
9114
9115
9116
9117
9118
9119
9120
9121
9122
9123
9124
9125
9126
9127
9128
9129
9130
9131
9132
9133
9134
9135
9136
9137
9138
9139
9140
9141
9142
9143
9144
9145
9146
9147
9148
9149
9150
9151
9152
9153
9154
9155
9156
9157
9158
9159
9160
9161
9162
9163
9164
9165
9166
9167
9168
9169
9170
9171
9172
9173
9174
9175
9176
9177
9178
9179
9180
9181
9182
9183
9184
9185
9186
9187
9188
9189
9190
9191
9192
9193
9194
9195
9196
9197
9198
9199
9200
9201
9202
9203
9204
9205
9206
9207
9208
9209
9210
9211
9212
9213
9214
9215
9216
9217
9218
9219
9220
9221
9222
9223
9224
9225
9226
9227
9228
9229
9230
9231
9232
9233
9234
9235
9236
9237
9238
9239
9240
9241
9242
9243
9244
9245
9246
9247
9248
9249
9250
9251
9252
9253
9254
9255
9256
9257
9258
9259
9260
9261
9262
9263
9264
9265
9266
9267
9268
9269
9270
9271
9272
9273
9274
9275
9276
9277
9278
9279
9280
9281
9282
9283
9284
9285
9286
9287
9288
9289
9290
9291
9292
9293
9294
9295
9296
9297
9298
9299
9300
9301
9302
9303
9304
9305
9306
9307
9308
9309
9310
9311
9312
9313
9314
9315
9316
9317
9318
9319
9320
9321
9322
9323
9324
9325
9326
9327
9328
9329
9330
9331
9332
9333
9334
9335
9336
9337
9338
9339
9340
9341
9342
9343
9344
9345
9346
9347
9348
9349
9350
9351
9352
9353
9354
9355
9356
9357
9358
9359
9360
9361
9362
9363
9364
9365
9366
9367
9368
9369
9370
9371
9372
9373
9374
9375
9376
9377
9378
9379
9380
9381
9382
9383
9384
9385
9386
9387
9388
9389
9390
9391
9392
9393
9394
9395
9396
9397
9398
9399
9400
9401
9402
9403
9404
9405
9406
9407
9408
9409
9410
9411
9412
9413
9414
9415
9416
9417
9418
9419
9420
9421
9422
9423
9424
9425
9426
9427
9428
9429
9430
9431
9432
9433
9434
9435
9436
9437
9438
9439
9440
9441
9442
9443
9444
9445
9446
9447
9448
9449
9450
9451
9452
9453
9454
9455
9456
9457
9458
9459
9460
9461
9462
9463
9464
9465
9466
9467
9468
9469
9470
9471
9472
9473
9474
9475
9476
9477
9478
9479
9480
9481
9482
9483
9484
9485
9486
9487
9488
9489
9490
9491
9492
9493
9494
9495
9496
9497
9498
9499
9500
9501
9502
9503
9504
9505
9506
9507
9508
9509
9510
9511
9512
9513
9514
9515
9516
9517
9518
9519
9520
9521
9522
9523
9524
9525
9526
9527
9528
9529
9530
9531
9532
9533
9534
9535
9536
9537
9538
9539
9540
9541
9542
9543
9544
9545
9546
9547
9548
9549
9550
9551
9552
9553
9554
9555
9556
9557
9558
9559
9560
9561
9562
9563
9564
9565
9566
9567
9568
9569
9570
9571
9572
9573
9574
9575
9576
9577
9578
9579
9580
9581
9582
9583
9584
9585
9586
9587
9588
9589
9590
9591
9592
9593
9594
9595
9596
9597
9598
9599
9600
9601
9602
9603
9604
9605
9606
9607
9608
9609
9610
9611
9612
9613
9614
9615
9616
9617
9618
9619
9620
9621
9622
9623
9624
9625
9626
9627
9628
9629
9630
9631
9632
9633
9634
9635
9636
9637
9638
9639
9640
9641
9642
9643
9644
9645
9646
9647
9648
9649
9650
9651
9652
9653
9654
9655
9656
9657
9658
9659
9660
9661
9662
9663
9664
9665
9666
9667
9668
9669
9670
9671
9672
9673
9674
9675
9676
9677
9678
9679
9680
9681
9682
9683
9684
9685
9686
9687
9688
9689
9690
9691
9692
9693
9694
9695
9696
9697
9698
9699
9700
9701
9702
9703
9704
9705
9706
9707
9708
9709
9710
9711
9712
9713
9714
9715
9716
9717
9718
9719
9720
9721
9722
9723
9724
9725
9726
9727
9728
9729
9730
9731
9732
9733
9734
9735
9736
9737
9738
9739
9740
9741
9742
9743
9744
9745
9746
9747
9748
9749
9750
9751
9752
9753
9754
9755
9756
9757
9758
9759
9760
9761
9762
9763
9764
9765
9766
9767
9768
9769
9770
9771
9772
9773
9774
9775
9776
9777
9778
9779
9780
9781
9782
9783
9784
9785
9786
9787
9788
9789
9790
9791
9792
9793
9794
9795
9796
9797
9798
9799
9800
9801
9802
9803
9804
9805
9806
9807
9808
9809
9810
9811
9812
9813
9814
9815
9816
9817
9818
9819
9820
9821
9822
9823
9824
9825
9826
9827
9828
9829
9830
9831
9832
9833
9834
9835
9836
9837
9838
9839
9840
9841
9842
9843
9844
9845
9846
9847
9848
9849
9850
9851
9852
9853
9854
9855
9856
9857
9858
9859
9860
9861
9862
9863
9864
9865
9866
9867
9868
9869
9870
9871
9872
9873
9874
9875
9876
9877
9878
9879
9880
9881
9882
9883
9884
9885
9886
9887
9888
9889
9890
9891
9892
9893
9894
9895
9896
9897
9898
9899
9900
9901
9902
9903
9904
9905
9906
9907
9908
9909
9910
9911
9912
9913
9914
9915
9916
9917
9918
9919
9920
9921
9922
9923
9924
9925
9926
9927
9928
9929
9930
9931
9932
9933
9934
9935
9936
9937
9938
9939
9940
9941
9942
9943
9944
9945
9946
9947
9948
9949
9950
9951
9952
9953
9954
9955
9956
9957
9958
9959
9960
9961
9962
9963
9964
9965
9966
9967
9968
9969
9970
9971
9972
9973
9974
9975
9976
9977
9978
9979
9980
9981
9982
9983
9984
9985
9986
9987
9988
9989
9990
9991
9992
9993
9994
9995
9996
9997
9998
9999
10000
10001
10002
10003
10004
10005
10006
10007
10008
10009
10010
10011
10012
10013
10014
10015
10016
10017
10018
10019
10020
10021
10022
10023
10024
10025
10026
10027
10028
10029
10030
10031
10032
10033
10034
10035
10036
10037
10038
10039
10040
10041
10042
10043
10044
10045
10046
10047
10048
10049
10050
10051
10052
10053
10054
10055
10056
10057
10058
10059
10060
10061
10062
10063
10064
10065
10066
10067
10068
10069
10070
10071
10072
10073
10074
10075
10076
10077
10078
10079
10080
10081
10082
10083
10084
10085
10086
10087
10088
10089
10090
10091
10092
10093
10094
10095
10096
10097
10098
10099
10100
10101
10102
10103
10104
10105
10106
10107
10108
10109
10110
10111
10112
10113
10114
10115
10116
10117
10118
10119
10120
10121
10122
10123
10124
10125
10126
10127
10128
10129
10130
10131
10132
10133
10134
10135
10136
10137
10138
10139
10140
10141
10142
10143
10144
10145
10146
10147
10148
10149
10150
10151
10152
10153
10154
10155
10156
10157
10158
10159
10160
10161
10162
10163
10164
10165
10166
10167
10168
10169
10170
10171
10172
10173
10174
10175
10176
10177
10178
10179
10180
10181
10182
10183
10184
10185
10186
10187
10188
10189
10190
10191
10192
10193
10194
10195
10196
10197
10198
10199
10200
10201
10202
10203
10204
10205
10206
10207
10208
10209
10210
10211
10212
10213
10214
10215
10216
10217
10218
10219
10220
10221
10222
10223
10224
10225
10226
10227
10228
10229
10230
10231
10232
10233
10234
10235
10236
10237
10238
10239
10240
10241
10242
10243
10244
10245
10246
10247
10248
10249
10250
10251
10252
10253
10254
10255
10256
10257
10258
10259
10260
10261
10262
10263
10264
10265
10266
10267
10268
10269
10270
10271
10272
10273
10274
10275
10276
10277
10278
10279
10280
10281
10282
10283
10284
10285
10286
10287
10288
10289
10290
10291
10292
10293
10294
10295
10296
10297
10298
10299
10300
10301
10302
10303
10304
10305
10306
10307
10308
10309
10310
10311
10312
10313
10314
10315
10316
10317
10318
10319
10320
10321
10322
10323
10324
10325
10326
10327
10328
10329
10330
10331
10332
10333
10334
10335
10336
10337
10338
10339
10340
10341
10342
10343
10344
10345
10346
10347
10348
10349
10350
10351
10352
10353
10354
10355
10356
10357
10358
10359
10360
10361
10362
10363
10364
10365
10366
10367
10368
10369
10370
10371
10372
10373
10374
10375
10376
10377
10378
10379
10380
10381
10382
10383
10384
10385
10386
10387
10388
10389
10390
10391
10392
10393
10394
10395
10396
10397
10398
10399
10400
10401
10402
10403
10404
10405
10406
10407
10408
10409
10410
10411
10412
10413
10414
10415
10416
10417
10418
10419
10420
10421
10422
10423
10424
10425
10426
10427
10428
10429
10430
10431
10432
10433
10434
10435
10436
10437
10438
10439
10440
10441
10442
10443
10444
10445
10446
10447
10448
10449
10450
10451
10452
10453
10454
10455
10456
10457
10458
10459
10460
10461
10462
10463
10464
10465
10466
10467
10468
10469
10470
10471
10472
10473
10474
10475
10476
10477
10478
10479
10480
10481
10482
10483
10484
10485
10486
10487
10488
10489
10490
10491
10492
10493
10494
10495
10496
10497
10498
10499
10500
10501
10502
10503
10504
10505
10506
10507
10508
10509
10510
10511
10512
10513
10514
10515
10516
10517
10518
10519
10520
10521
10522
10523
10524
10525
10526
10527
10528
10529
10530
10531
10532
10533
10534
10535
10536
10537
10538
10539
10540
10541
10542
10543
10544
10545
10546
10547
10548
10549
10550
10551
10552
10553
10554
10555
10556
10557
10558
10559
10560
10561
10562
10563
10564
10565
10566
10567
10568
10569
10570
10571
10572
10573
10574
10575
10576
10577
10578
10579
10580
10581
10582
10583
10584
10585
10586
10587
10588
10589
10590
10591
10592
10593
10594
10595
10596
10597
10598
10599
10600
10601
10602
10603
10604
10605
10606
10607
10608
10609
10610
10611
10612
10613
10614
10615
10616
10617
10618
10619
10620
10621
10622
10623
10624
10625
10626
10627
10628
10629
10630
10631
10632
10633
10634
10635
10636
10637
10638
10639
10640
10641
10642
10643
10644
10645
10646
10647
10648
10649
10650
10651
10652
10653
10654
10655
10656
10657
10658
10659
10660
10661
10662
10663
10664
10665
10666
10667
10668
10669
10670
10671
10672
10673
10674
10675
10676
10677
10678
10679
10680
10681
10682
10683
10684
10685
10686
10687
10688
10689
10690
10691
10692
10693
10694
10695
10696
10697
10698
10699
10700
10701
10702
10703
10704
10705
10706
10707
10708
10709
10710
10711
10712
10713
10714
10715
10716
10717
10718
10719
10720
10721
10722
10723
10724
10725
10726
10727
10728
10729
10730
10731
10732
10733
10734
10735
10736
10737
10738
10739
10740
10741
10742
10743
10744
10745
10746
10747
10748
10749
10750
10751
10752
10753
10754
10755
10756
10757
10758
10759
10760
10761
10762
10763
10764
10765
10766
10767
10768
10769
10770
10771
10772
10773
10774
10775
10776
10777
10778
10779
10780
10781
10782
10783
10784
10785
10786
10787
10788
10789
10790
10791
10792
10793
10794
10795
10796
10797
10798
10799
10800
10801
10802
10803
10804
10805
10806
10807
10808
10809
10810
10811
10812
10813
10814
10815
10816
10817
10818
10819
10820
10821
10822
10823
10824
10825
10826
10827
10828
10829
10830
10831
10832
10833
10834
10835
10836
10837
10838
10839
10840
10841
10842
10843
10844
10845
10846
10847
10848
10849
10850
10851
10852
10853
10854
10855
10856
10857
10858
10859
10860
10861
10862
10863
10864
10865
10866
10867
10868
10869
10870
10871
10872
10873
10874
10875
10876
10877
10878
10879
10880
10881
10882
10883
10884
10885
10886
10887
10888
10889
10890
10891
10892
10893
10894
10895
10896
10897
10898
10899
10900
10901
10902
10903
10904
10905
10906
10907
10908
10909
10910
10911
10912
10913
10914
10915
10916
10917
10918
10919
10920
10921
10922
10923
10924
10925
10926
10927
10928
10929
10930
10931
10932
10933
10934
10935
10936
10937
10938
10939
10940
10941
10942
10943
10944
10945
10946
10947
10948
10949
10950
10951
10952
10953
10954
10955
10956
10957
10958
10959
10960
10961
10962
10963
10964
10965
10966
10967
10968
10969
10970
10971
10972
10973
10974
10975
10976
10977
10978
10979
10980
10981
10982
10983
10984
10985
10986
10987
10988
10989
10990
10991
10992
10993
10994
10995
10996
10997
10998
10999
11000
11001
11002
11003
11004
11005
11006
11007
11008
11009
11010
11011
11012
11013
11014
11015
11016
11017
11018
11019
11020
11021
11022
11023
11024
11025
11026
11027
11028
11029
11030
11031
11032
11033
11034
11035
11036
11037
11038
11039
11040
11041
11042
11043
11044
11045
11046
11047
11048
11049
11050
11051
11052
11053
11054
11055
11056
11057
11058
11059
11060
11061
11062
11063
11064
11065
11066
11067
11068
11069
11070
11071
11072
11073
11074
11075
11076
11077
11078
11079
11080
11081
11082
11083
11084
11085
11086
11087
11088
11089
11090
11091
11092
11093
11094
11095
11096
11097
11098
11099
11100
11101
11102
11103
11104
11105
11106
11107
11108
11109
11110
11111
11112
11113
11114
11115
11116
11117
11118
11119
11120
11121
11122
11123
11124
11125
11126
11127
11128
11129
11130
11131
11132
11133
11134
11135
11136
11137
11138
11139
11140
11141
11142
11143
11144
11145
11146
11147
11148
11149
11150
11151
11152
11153
11154
11155
11156
11157
11158
11159
11160
11161
11162
11163
11164
11165
11166
11167
11168
11169
11170
11171
11172
11173
11174
11175
11176
11177
11178
11179
11180
11181
11182
11183
11184
11185
11186
11187
11188
11189
11190
11191
11192
11193
11194
11195
11196
11197
11198
11199
11200
11201
11202
11203
11204
11205
11206
11207
11208
11209
11210
11211
11212
11213
11214
11215
11216
11217
11218
11219
11220
11221
11222
11223
11224
11225
11226
11227
11228
11229
11230
11231
11232
11233
11234
11235
11236
11237
11238
11239
11240
11241
11242
11243
11244
11245
11246
11247
11248
11249
11250
11251
11252
11253
11254
11255
11256
11257
11258
11259
11260
11261
11262
11263
11264
11265
11266
11267
11268
11269
11270
11271
11272
11273
11274
11275
11276
11277
11278
11279
11280
11281
11282
11283
11284
11285
11286
11287
11288
11289
11290
11291
11292
11293
11294
11295
11296
11297
11298
11299
11300
11301
11302
11303
11304
11305
11306
11307
11308
11309
11310
11311
11312
11313
11314
11315
11316
11317
11318
11319
11320
11321
11322
11323
11324
11325
11326
11327
11328
11329
11330
11331
11332
11333
11334
11335
11336
11337
11338
11339
11340
11341
11342
11343
11344
11345
11346
11347
11348
11349
11350
11351
11352
11353
11354
11355
11356
11357
11358
11359
11360
11361
11362
11363
11364
11365
11366
11367
11368
11369
11370
11371
11372
11373
11374
11375
11376
11377
11378
11379
11380
11381
11382
11383
11384
11385
11386
11387
11388
11389
11390
11391
11392
11393
11394
11395
11396
11397
11398
11399
11400
11401
11402
11403
11404
11405
11406
11407
11408
11409
11410
11411
11412
11413
11414
11415
11416
11417
11418
11419
11420
11421
11422
11423
11424
11425
11426
11427
11428
11429
11430
11431
11432
11433
11434
11435
11436
11437
11438
11439
11440
11441
11442
11443
11444
11445
11446
11447
11448
11449
11450
11451
11452
11453
11454
11455
11456
11457
11458
11459
11460
11461
11462
11463
11464
11465
11466
11467
11468
11469
11470
11471
11472
11473
11474
11475
11476
11477
11478
11479
11480
11481
11482
11483
11484
11485
11486
11487
11488
11489
11490
11491
11492
11493
11494
11495
11496
11497
11498
11499
11500
11501
11502
11503
11504
11505
11506
11507
11508
11509
11510
11511
11512
11513
11514
11515
11516
11517
11518
11519
11520
11521
11522
11523
11524
11525
11526
11527
11528
11529
11530
11531
11532
11533
11534
11535
11536
11537
11538
11539
11540
11541
11542
11543
11544
11545
11546
11547
11548
11549
11550
11551
11552
11553
11554
11555
11556
11557
11558
11559
11560
11561
11562
11563
11564
11565
11566
11567
11568
11569
11570
11571
11572
11573
11574
11575
11576
11577
11578
11579
11580
11581
11582
11583
11584
11585
11586
11587
11588
11589
11590
11591
11592
11593
11594
11595
11596
11597
11598
11599
11600
11601
11602
11603
11604
11605
11606
11607
11608
11609
11610
11611
11612
11613
11614
11615
11616
11617
11618
11619
11620
11621
11622
11623
11624
11625
11626
11627
11628
11629
11630
11631
11632
11633
11634
11635
11636
11637
11638
11639
11640
11641
11642
11643
11644
11645
11646
11647
11648
11649
11650
11651
11652
11653
11654
11655
11656
11657
11658
11659
11660
11661
11662
11663
11664
11665
11666
11667
11668
11669
11670
11671
11672
11673
11674
11675
11676
11677
11678
11679
11680
11681
11682
11683
11684
11685
11686
11687
11688
11689
11690
11691
11692
11693
11694
11695
11696
11697
11698
11699
11700
11701
11702
11703
11704
11705
11706
11707
11708
11709
11710
11711
11712
11713
11714
11715
11716
11717
11718
11719
11720
11721
11722
11723
11724
11725
11726
11727
11728
11729
11730
11731
11732
11733
11734
11735
11736
11737
11738
11739
11740
11741
11742
11743
11744
11745
11746
11747
11748
11749
11750
11751
11752
11753
11754
11755
11756
11757
11758
11759
11760
11761
11762
11763
11764
11765
11766
11767
11768
11769
11770
11771
11772
11773
11774
11775
11776
11777
11778
11779
11780
11781
11782
11783
11784
11785
11786
11787
11788
11789
11790
11791
11792
11793
11794
11795
11796
11797
11798
11799
11800
11801
11802
11803
11804
11805
11806
11807
11808
11809
11810
11811
11812
11813
11814
11815
11816
11817
11818
11819
11820
11821
11822
11823
11824
11825
11826
11827
11828
11829
11830
11831
11832
11833
11834
11835
11836
11837
11838
11839
11840
11841
11842
11843
11844
11845
11846
11847
11848
11849
11850
11851
11852
11853
11854
11855
11856
11857
11858
11859
11860
11861
11862
11863
11864
11865
11866
11867
11868
11869
11870
11871
11872
11873
11874
11875
11876
11877
11878
11879
11880
11881
11882
11883
11884
11885
11886
11887
11888
11889
11890
11891
11892
11893
11894
11895
11896
11897
11898
11899
11900
11901
11902
11903
11904
11905
11906
11907
11908
11909
11910
11911
11912
11913
11914
11915
11916
11917
11918
11919
11920
11921
11922
11923
11924
11925
11926
11927
11928
11929
11930
11931
11932
11933
11934
11935
11936
11937
11938
11939
11940
11941
11942
11943
11944
11945
11946
11947
11948
11949
11950
11951
11952
11953
11954
11955
11956
11957
11958
11959
11960
11961
11962
11963
11964
11965
11966
11967
11968
11969
11970
11971
11972
11973
11974
11975
11976
11977
11978
11979
11980
11981
11982
11983
11984
11985
11986
11987
11988
11989
11990
11991
11992
11993
11994
11995
11996
11997
11998
11999
12000
12001
12002
12003
12004
12005
12006
12007
12008
12009
12010
12011
12012
12013
12014
12015
12016
12017
12018
12019
12020
12021
12022
12023
12024
12025
12026
12027
12028
12029
12030
12031
12032
12033
12034
12035
12036
12037
12038
12039
12040
12041
12042
12043
12044
12045
12046
12047
12048
12049
12050
12051
12052
12053
12054
12055
12056
12057
12058
12059
12060
12061
12062
12063
12064
12065
12066
12067
12068
12069
12070
12071
12072
12073
12074
12075
12076
12077
12078
12079
12080
12081
12082
12083
12084
12085
12086
12087
12088
12089
12090
12091
12092
12093
12094
12095
12096
12097
12098
12099
12100
12101
12102
12103
12104
12105
12106
12107
12108
12109
12110
12111
12112
12113
12114
12115
12116
12117
12118
12119
12120
12121
12122
12123
12124
12125
12126
12127
12128
12129
12130
12131
12132
12133
12134
12135
12136
12137
12138
12139
12140
12141
12142
12143
12144
12145
12146
12147
12148
12149
12150
12151
12152
12153
12154
12155
12156
12157
12158
12159
12160
12161
12162
12163
12164
12165
12166
12167
12168
12169
12170
12171
12172
12173
12174
12175
12176
12177
12178
12179
12180
12181
12182
12183
12184
12185
12186
12187
12188
12189
12190
12191
12192
12193
12194
12195
12196
12197
12198
12199
12200
12201
12202
12203
12204
12205
12206
12207
12208
12209
12210
12211
12212
12213
12214
12215
12216
12217
12218
12219
12220
12221
12222
12223
12224
12225
12226
12227
12228
12229
12230
12231
12232
12233
12234
12235
12236
12237
12238
12239
12240
12241
12242
12243
12244
12245
12246
12247
12248
12249
12250
12251
12252
12253
12254
12255
12256
12257
12258
12259
12260
12261
12262
12263
12264
12265
12266
12267
12268
12269
12270
12271
12272
12273
12274
12275
12276
12277
12278
12279
12280
12281
12282
12283
12284
12285
12286
12287
12288
12289
12290
12291
12292
12293
12294
12295
12296
12297
12298
12299
12300
12301
12302
12303
12304
12305
12306
12307
12308
12309
12310
12311
12312
12313
12314
12315
12316
12317
12318
12319
12320
12321
12322
12323
12324
12325
12326
12327
12328
12329
12330
12331
12332
12333
12334
12335
12336
12337
12338
12339
12340
12341
12342
12343
12344
12345
12346
12347
12348
12349
12350
12351
12352
12353
12354
12355
12356
12357
12358
12359
12360
12361
12362
12363
12364
12365
12366
12367
12368
12369
12370
12371
12372
12373
12374
12375
12376
12377
12378
12379
12380
12381
12382
12383
12384
12385
12386
12387
12388
12389
12390
12391
12392
12393
12394
12395
12396
12397
12398
12399
12400
12401
12402
12403
12404
12405
12406
12407
12408
12409
12410
12411
12412
12413
12414
12415
12416
12417
12418
12419
12420
12421
12422
12423
12424
12425
12426
12427
12428
12429
12430
12431
12432
12433
12434
12435
12436
12437
12438
12439
12440
12441
12442
12443
12444
12445
12446
12447
12448
12449
12450
12451
12452
12453
12454
12455
12456
12457
12458
12459
12460
12461
12462
12463
12464
12465
12466
12467
12468
12469
12470
12471
12472
12473
12474
12475
12476
12477
12478
12479
12480
12481
12482
12483
12484
12485
12486
12487
12488
12489
12490
12491
12492
12493
12494
12495
12496
12497
12498
12499
12500
12501
12502
12503
12504
12505
12506
12507
12508
12509
12510
12511
12512
12513
12514
12515
12516
12517
12518
12519
12520
12521
12522
12523
12524
12525
12526
12527
12528
12529
12530
12531
12532
12533
12534
12535
12536
12537
12538
12539
12540
12541
12542
12543
12544
12545
12546
12547
12548
12549
12550
12551
12552
12553
12554
12555
12556
12557
12558
12559
12560
12561
12562
12563
12564
12565
12566
12567
12568
12569
12570
12571
12572
12573
12574
12575
12576
12577
12578
12579
12580
12581
12582
12583
12584
12585
12586
12587
12588
12589
12590
12591
12592
12593
12594
12595
12596
12597
12598
12599
12600
12601
12602
12603
12604
12605
12606
12607
12608
12609
12610
12611
12612
12613
12614
12615
12616
12617
12618
12619
12620
12621
12622
12623
12624
12625
12626
12627
12628
12629
12630
12631
12632
12633
12634
12635
12636
12637
12638
12639
12640
12641
12642
12643
12644
12645
12646
12647
12648
12649
12650
12651
12652
12653
12654
12655
12656
12657
12658
12659
12660
12661
12662
12663
12664
12665
12666
12667
12668
12669
12670
12671
12672
12673
12674
12675
12676
12677
12678
12679
12680
12681
12682
12683
12684
12685
12686
12687
12688
12689
12690
12691
12692
12693
12694
12695
12696
12697
12698
12699
12700
12701
12702
12703
12704
12705
12706
12707
12708
12709
12710
12711
12712
12713
12714
12715
12716
12717
12718
12719
12720
12721
12722
12723
12724
12725
12726
12727
12728
12729
12730
12731
12732
12733
12734
12735
12736
12737
12738
12739
12740
12741
12742
12743
12744
12745
12746
12747
12748
12749
12750
12751
12752
12753
12754
12755
12756
12757
12758
12759
12760
12761
12762
12763
12764
12765
12766
12767
12768
12769
12770
12771
12772
12773
12774
12775
12776
12777
12778
12779
12780
12781
12782
12783
12784
12785
12786
12787
12788
12789
12790
12791
12792
12793
12794
12795
12796
12797
12798
12799
12800
12801
12802
12803
12804
12805
12806
12807
12808
12809
12810
12811
12812
12813
12814
12815
12816
12817
12818
12819
12820
12821
12822
12823
12824
12825
12826
12827
12828
12829
12830
12831
12832
12833
12834
12835
12836
12837
12838
12839
12840
12841
12842
12843
12844
12845
12846
12847
12848
12849
12850
12851
12852
12853
12854
12855
12856
12857
12858
12859
12860
12861
12862
12863
12864
12865
12866
12867
12868
12869
12870
12871
12872
12873
12874
12875
12876
12877
12878
12879
12880
12881
12882
12883
12884
12885
12886
12887
12888
12889
12890
12891
12892
12893
12894
12895
12896
12897
12898
12899
12900
12901
12902
12903
12904
12905
12906
12907
12908
12909
12910
12911
12912
12913
12914
12915
12916
12917
12918
12919
12920
12921
12922
12923
12924
12925
12926
12927
12928
12929
12930
12931
12932
12933
12934
12935
12936
12937
12938
12939
12940
12941
12942
12943
12944
12945
12946
12947
12948
12949
12950
12951
12952
12953
12954
12955
12956
12957
12958
12959
12960
12961
12962
12963
12964
12965
12966
12967
12968
12969
12970
12971
12972
12973
12974
12975
12976
12977
12978
12979
12980
12981
12982
12983
12984
12985
12986
12987
12988
12989
12990
12991
12992
12993
12994
12995
12996
12997
12998
12999
13000
13001
13002
13003
13004
13005
13006
13007
13008
13009
13010
13011
13012
13013
13014
13015
13016
13017
13018
13019
13020
13021
13022
13023
13024
13025
13026
13027
13028
13029
13030
13031
13032
13033
13034
13035
13036
13037
13038
13039
13040
13041
13042
13043
13044
13045
13046
13047
13048
13049
13050
13051
13052
13053
13054
13055
13056
13057
13058
13059
13060
13061
13062
13063
13064
13065
13066
13067
13068
13069
13070
13071
13072
13073
13074
13075
13076
13077
13078
13079
13080
13081
13082
13083
13084
13085
13086
13087
13088
13089
13090
13091
13092
13093
13094
13095
13096
13097
13098
13099
13100
13101
13102
13103
13104
13105
13106
13107
13108
13109
13110
13111
13112
13113
13114
13115
13116
13117
13118
13119
13120
13121
13122
13123
13124
13125
13126
13127
13128
13129
13130
13131
13132
13133
13134
13135
13136
13137
13138
13139
13140
13141
13142
13143
13144
13145
13146
13147
13148
13149
13150
13151
13152
13153
13154
13155
13156
13157
13158
13159
13160
13161
13162
13163
13164
13165
13166
13167
13168
13169
13170
13171
13172
13173
13174
13175
13176
13177
13178
13179
13180
13181
13182
13183
13184
13185
13186
13187
13188
13189
13190
13191
13192
13193
13194
13195
13196
13197
13198
13199
13200
13201
13202
13203
13204
13205
13206
13207
13208
13209
13210
13211
13212
13213
13214
13215
13216
13217
13218
13219
13220
13221
13222
13223
13224
13225
13226
13227
13228
13229
13230
13231
13232
13233
13234
13235
13236
13237
13238
13239
13240
13241
13242
13243
13244
13245
13246
13247
13248
13249
13250
13251
13252
13253
13254
13255
13256
13257
13258
13259
13260
13261
13262
13263
13264
13265
13266
13267
13268
13269
13270
13271
13272
13273
13274
13275
13276
13277
13278
13279
13280
13281
13282
13283
13284
13285
13286
13287
13288
13289
13290
13291
13292
13293
13294
13295
13296
13297
13298
13299
13300
13301
13302
13303
13304
13305
13306
13307
13308
13309
13310
13311
13312
13313
13314
13315
13316
13317
13318
13319
13320
13321
13322
13323
13324
13325
13326
13327
13328
13329
13330
13331
13332
13333
13334
13335
13336
13337
13338
13339
13340
13341
13342
13343
13344
13345
13346
13347
13348
13349
13350
13351
13352
13353
13354
13355
13356
13357
13358
13359
13360
13361
13362
13363
13364
13365
13366
13367
13368
13369
13370
13371
13372
13373
13374
13375
13376
13377
13378
13379
13380
13381
13382
13383
13384
13385
13386
13387
13388
13389
13390
13391
13392
13393
13394
13395
13396
13397
13398
13399
13400
13401
13402
13403
13404
13405
13406
13407
13408
13409
13410
13411
13412
13413
13414
13415
13416
13417
13418
13419
13420
13421
13422
13423
13424
13425
13426
13427
13428
13429
13430
13431
13432
13433
13434
13435
13436
13437
13438
13439
13440
13441
13442
13443
13444
13445
13446
13447
13448
13449
13450
13451
13452
13453
13454
13455
13456
13457
13458
13459
13460
13461
13462
13463
13464
13465
13466
13467
13468
13469
13470
13471
13472
13473
13474
13475
13476
13477
13478
13479
13480
13481
13482
13483
13484
13485
13486
13487
13488
13489
13490
13491
13492
13493
13494
13495
13496
13497
13498
13499
13500
13501
13502
13503
13504
13505
13506
13507
13508
13509
13510
13511
13512
13513
13514
13515
13516
13517
13518
13519
13520
13521
13522
13523
13524
13525
13526
13527
13528
13529
13530
13531
13532
13533
13534
13535
13536
13537
13538
13539
13540
13541
13542
13543
13544
13545
13546
13547
13548
13549
13550
13551
13552
13553
13554
13555
13556
13557
13558
13559
13560
13561
13562
13563
13564
13565
13566
13567
13568
13569
13570
13571
13572
13573
13574
13575
13576
13577
13578
13579
13580
13581
13582
13583
13584
13585
13586
13587
13588
13589
13590
13591
13592
13593
13594
13595
13596
13597
13598
13599
13600
13601
13602
13603
13604
13605
13606
13607
13608
13609
13610
13611
13612
13613
13614
13615
13616
13617
13618
13619
13620
13621
13622
13623
13624
13625
13626
13627
13628
13629
13630
13631
13632
13633
13634
13635
13636
13637
13638
13639
13640
13641
13642
13643
13644
13645
13646
13647
13648
13649
13650
13651
13652
13653
13654
13655
13656
13657
13658
13659
13660
13661
13662
13663
13664
13665
13666
13667
13668
13669
13670
13671
13672
13673
13674
13675
13676
13677
13678
13679
13680
13681
13682
13683
13684
13685
13686
13687
13688
13689
13690
13691
13692
13693
13694
13695
13696
13697
13698
13699
13700
13701
13702
13703
13704
13705
13706
13707
13708
13709
13710
13711
13712
13713
13714
13715
13716
13717
13718
13719
13720
13721
13722
13723
13724
13725
13726
13727
13728
13729
13730
13731
13732
13733
13734
13735
13736
13737
13738
13739
13740
13741
13742
13743
13744
13745
13746
13747
13748
13749
13750
13751
13752
13753
13754
13755
13756
13757
13758
13759
13760
13761
13762
13763
13764
13765
13766
13767
13768
13769
13770
13771
13772
13773
13774
13775
13776
13777
13778
13779
13780
13781
13782
13783
13784
13785
13786
13787
13788
13789
13790
13791
13792
13793
13794
13795
13796
13797
13798
13799
13800
13801
13802
13803
13804
13805
13806
13807
13808
13809
13810
13811
13812
13813
13814
13815
13816
13817
13818
13819
13820
13821
13822
13823
13824
13825
13826
13827
13828
13829
13830
13831
13832
13833
13834
13835
13836
13837
13838
13839
13840
13841
13842
13843
13844
13845
13846
13847
13848
13849
13850
13851
13852
13853
13854
13855
13856
13857
13858
13859
13860
13861
13862
13863
13864
13865
13866
13867
13868
13869
13870
13871
13872
13873
13874
13875
13876
13877
13878
13879
13880
13881
13882
13883
13884
13885
13886
13887
13888
13889
13890
13891
13892
13893
13894
13895
13896
13897
13898
13899
13900
13901
13902
13903
13904
13905
13906
13907
13908
13909
13910
13911
13912
13913
13914
13915
13916
13917
13918
13919
13920
13921
13922
13923
13924
13925
13926
13927
13928
13929
13930
13931
13932
13933
13934
13935
13936
13937
13938
13939
13940
13941
13942
13943
13944
13945
13946
13947
13948
13949
13950
13951
13952
13953
13954
13955
13956
13957
13958
13959
13960
13961
13962
13963
13964
13965
13966
13967
13968
13969
13970
13971
13972
13973
13974
13975
13976
13977
13978
13979
13980
13981
13982
13983
13984
13985
13986
13987
13988
13989
13990
13991
13992
13993
13994
13995
13996
13997
13998
13999
14000
14001
14002
14003
14004
14005
14006
14007
14008
14009
14010
14011
14012
14013
14014
14015
14016
14017
14018
14019
14020
14021
14022
14023
14024
14025
14026
14027
14028
14029
14030
14031
14032
14033
14034
14035
14036
14037
14038
14039
14040
14041
14042
14043
14044
14045
14046
14047
14048
14049
14050
14051
14052
14053
14054
14055
14056
14057
14058
14059
14060
14061
14062
14063
14064
14065
14066
14067
14068
14069
14070
14071
14072
14073
14074
14075
14076
14077
14078
14079
14080
14081
14082
14083
14084
14085
14086
14087
14088
14089
14090
14091
14092
14093
14094
14095
14096
14097
14098
14099
14100
14101
14102
14103
14104
14105
14106
14107
14108
14109
14110
14111
14112
14113
14114
14115
14116
14117
14118
14119
14120
14121
14122
14123
14124
14125
14126
14127
14128
14129
14130
14131
14132
14133
14134
14135
14136
14137
14138
14139
14140
14141
14142
14143
14144
14145
14146
14147
14148
14149
14150
14151
14152
14153
14154
14155
14156
14157
14158
14159
14160
14161
14162
14163
14164
14165
14166
14167
14168
14169
14170
14171
14172
14173
14174
14175
14176
14177
14178
14179
14180
14181
14182
14183
14184
14185
14186
14187
14188
14189
14190
14191
14192
14193
14194
14195
14196
14197
14198
14199
14200
14201
14202
14203
14204
14205
14206
14207
14208
14209
14210
14211
14212
14213
14214
14215
14216
14217
14218
14219
14220
14221
14222
14223
14224
14225
14226
14227
14228
14229
14230
14231
14232
14233
14234
14235
14236
14237
14238
14239
14240
14241
14242
14243
14244
14245
14246
14247
14248
14249
14250
14251
14252
14253
14254
14255
14256
14257
14258
14259
14260
14261
14262
14263
14264
14265
14266
14267
14268
14269
14270
14271
14272
14273
14274
14275
14276
14277
14278
14279
14280
14281
14282
14283
14284
14285
14286
14287
14288
14289
14290
14291
14292
14293
14294
14295
14296
14297
14298
14299
14300
14301
14302
14303
14304
14305
14306
14307
14308
14309
14310
14311
14312
14313
14314
14315
14316
14317
14318
14319
14320
14321
14322
14323
14324
14325
14326
14327
14328
14329
14330
14331
14332
14333
14334
14335
14336
14337
14338
14339
14340
14341
14342
14343
14344
14345
14346
14347
14348
14349
14350
14351
14352
14353
14354
14355
14356
14357
14358
14359
14360
14361
14362
14363
14364
14365
14366
14367
14368
14369
14370
14371
14372
14373
14374
14375
14376
14377
14378
14379
14380
14381
14382
14383
14384
14385
14386
14387
14388
14389
14390
14391
14392
14393
14394
14395
14396
14397
14398
14399
14400
14401
14402
14403
14404
14405
14406
14407
14408
14409
14410
14411
14412
14413
14414
14415
14416
14417
14418
14419
14420
14421
14422
14423
14424
14425
14426
14427
14428
14429
14430
14431
14432
14433
14434
14435
14436
14437
14438
14439
14440
14441
14442
14443
14444
14445
14446
14447
14448
14449
14450
14451
14452
14453
14454
14455
14456
14457
14458
14459
14460
14461
14462
14463
14464
14465
14466
14467
14468
14469
14470
14471
14472
14473
14474
14475
14476
14477
14478
14479
14480
14481
14482
14483
14484
14485
14486
14487
14488
14489
14490
14491
14492
14493
14494
14495
14496
14497
14498
14499
14500
14501
14502
14503
14504
14505
14506
14507
14508
14509
14510
14511
14512
14513
14514
14515
14516
14517
14518
14519
14520
14521
14522
14523
14524
14525
14526
14527
14528
14529
14530
14531
14532
14533
14534
14535
14536
14537
14538
14539
14540
14541
14542
14543
14544
14545
14546
14547
14548
14549
14550
14551
14552
14553
14554
14555
14556
14557
14558
14559
14560
14561
14562
14563
14564
14565
14566
14567
14568
14569
14570
14571
14572
14573
14574
14575
14576
14577
14578
14579
14580
14581
14582
14583
14584
14585
14586
14587
14588
14589
14590
14591
14592
14593
14594
14595
14596
14597
14598
14599
14600
14601
14602
14603
14604
14605
14606
14607
14608
14609
14610
14611
14612
14613
14614
14615
14616
14617
14618
14619
14620
14621
14622
14623
14624
14625
14626
14627
14628
14629
14630
14631
14632
14633
14634
14635
14636
14637
14638
14639
14640
14641
14642
14643
14644
14645
14646
14647
14648
14649
14650
14651
14652
14653
14654
14655
14656
14657
14658
14659
14660
14661
14662
14663
14664
14665
14666
14667
14668
14669
14670
14671
14672
14673
14674
14675
14676
14677
14678
14679
14680
14681
14682
14683
14684
14685
14686
14687
14688
14689
14690
14691
14692
14693
14694
14695
14696
14697
14698
14699
14700
14701
14702
14703
14704
14705
14706
14707
14708
14709
14710
14711
14712
14713
14714
14715
14716
14717
14718
14719
14720
14721
14722
14723
14724
14725
14726
14727
14728
14729
14730
14731
14732
14733
14734
14735
14736
14737
14738
14739
14740
14741
14742
14743
14744
14745
14746
14747
14748
14749
14750
14751
14752
14753
14754
14755
14756
14757
14758
14759
14760
14761
14762
14763
14764
14765
14766
14767
14768
14769
14770
14771
14772
14773
14774
14775
14776
14777
14778
14779
14780
14781
14782
14783
14784
14785
14786
14787
14788
14789
14790
14791
14792
14793
14794
14795
14796
14797
14798
14799
14800
14801
14802
14803
14804
14805
14806
14807
14808
14809
14810
14811
14812
14813
14814
14815
14816
14817
14818
14819
14820
14821
14822
14823
14824
14825
14826
14827
14828
14829
14830
14831
14832
14833
14834
14835
14836
14837
14838
14839
14840
14841
14842
14843
14844
14845
14846
14847
14848
14849
14850
14851
14852
14853
14854
14855
14856
14857
14858
14859
14860
14861
14862
14863
14864
14865
14866
14867
14868
14869
14870
14871
14872
14873
14874
14875
14876
14877
14878
14879
14880
14881
14882
14883
14884
14885
14886
14887
14888
14889
14890
14891
14892
14893
14894
14895
14896
14897
14898
14899
14900
14901
14902
14903
14904
14905
14906
14907
14908
14909
14910
14911
14912
14913
14914
14915
14916
14917
14918
14919
14920
14921
14922
14923
14924
14925
14926
14927
14928
14929
14930
14931
14932
14933
14934
14935
14936
14937
14938
14939
14940
14941
14942
14943
14944
14945
14946
14947
14948
14949
14950
14951
14952
14953
14954
14955
14956
14957
14958
14959
14960
14961
14962
14963
14964
14965
14966
14967
14968
14969
14970
14971
14972
14973
14974
14975
14976
14977
14978
14979
14980
14981
14982
14983
14984
14985
14986
14987
14988
14989
14990
14991
14992
14993
14994
14995
14996
14997
14998
14999
15000
15001
15002
15003
15004
15005
15006
15007
15008
15009
15010
15011
15012
15013
15014
15015
15016
15017
15018
15019
15020
15021
15022
15023
15024
15025
15026
15027
15028
15029
15030
15031
15032
15033
15034
15035
15036
15037
15038
15039
15040
15041
15042
15043
15044
15045
15046
15047
15048
15049
15050
15051
15052
15053
15054
15055
15056
15057
15058
15059
15060
15061
15062
15063
15064
15065
15066
15067
15068
15069
15070
15071
15072
15073
15074
15075
15076
15077
15078
15079
15080
15081
15082
15083
15084
15085
15086
15087
15088
15089
15090
15091
15092
15093
15094
15095
15096
15097
15098
15099
15100
15101
15102
15103
15104
15105
15106
15107
15108
15109
15110
15111
15112
15113
15114
15115
15116
15117
15118
15119
15120
15121
15122
15123
15124
15125
15126
15127
15128
15129
15130
15131
15132
15133
15134
15135
15136
15137
15138
15139
15140
15141
15142
15143
15144
15145
15146
15147
15148
15149
15150
15151
15152
15153
15154
15155
15156
15157
15158
15159
15160
15161
15162
15163
15164
15165
15166
15167
15168
15169
15170
15171
15172
15173
15174
15175
15176
15177
15178
15179
15180
15181
15182
15183
15184
15185
15186
15187
15188
15189
15190
15191
15192
15193
15194
15195
15196
15197
15198
15199
15200
15201
15202
15203
15204
15205
15206
15207
15208
15209
15210
15211
15212
15213
15214
15215
15216
15217
15218
15219
15220
15221
15222
15223
15224
15225
15226
15227
15228
15229
15230
15231
15232
15233
15234
15235
15236
15237
15238
15239
15240
15241
15242
15243
15244
15245
15246
15247
15248
15249
15250
15251
15252
15253
15254
15255
15256
15257
15258
15259
15260
15261
15262
15263
15264
15265
15266
15267
15268
15269
15270
15271
15272
15273
15274
15275
15276
15277
15278
15279
15280
15281
15282
15283
15284
15285
15286
15287
15288
15289
15290
15291
15292
15293
15294
15295
15296
15297
15298
15299
15300
15301
15302
15303
15304
15305
15306
15307
15308
15309
15310
15311
15312
15313
15314
15315
15316
15317
15318
15319
15320
15321
15322
15323
15324
15325
15326
15327
15328
15329
15330
15331
15332
15333
15334
15335
15336
15337
15338
15339
15340
15341
15342
15343
15344
15345
15346
15347
15348
15349
15350
15351
15352
15353
15354
15355
15356
15357
15358
15359
15360
15361
15362
15363
15364
15365
15366
15367
15368
15369
15370
15371
15372
15373
15374
15375
15376
15377
15378
15379
15380
15381
15382
15383
15384
15385
15386
15387
15388
15389
15390
15391
15392
15393
15394
15395
15396
15397
15398
15399
15400
15401
15402
15403
15404
15405
15406
15407
15408
15409
15410
15411
15412
15413
15414
15415
15416
15417
15418
15419
15420
15421
15422
15423
15424
15425
15426
15427
15428
15429
15430
15431
15432
15433
15434
15435
15436
15437
15438
15439
15440
15441
15442
15443
15444
15445
15446
15447
15448
15449
15450
15451
15452
15453
15454
15455
15456
15457
15458
15459
15460
15461
15462
15463
15464
15465
15466
15467
15468
15469
15470
15471
15472
15473
15474
15475
15476
15477
15478
15479
15480
15481
15482
15483
15484
15485
15486
15487
15488
15489
15490
15491
15492
15493
15494
15495
15496
15497
15498
15499
15500
15501
15502
15503
15504
15505
15506
15507
15508
15509
15510
15511
15512
15513
15514
15515
15516
15517
15518
15519
15520
15521
15522
15523
15524
15525
15526
15527
15528
15529
15530
15531
15532
15533
15534
15535
15536
15537
15538
15539
15540
15541
15542
15543
15544
15545
15546
15547
15548
15549
15550
15551
15552
15553
15554
15555
15556
15557
15558
15559
15560
15561
15562
15563
15564
15565
15566
15567
15568
15569
15570
15571
15572
15573
15574
15575
15576
15577
15578
15579
15580
15581
15582
15583
15584
15585
15586
15587
15588
15589
15590
15591
15592
15593
15594
15595
15596
15597
15598
15599
15600
15601
15602
15603
15604
15605
15606
15607
15608
15609
15610
15611
15612
15613
15614
15615
15616
15617
15618
15619
15620
15621
15622
15623
15624
15625
15626
15627
15628
15629
15630
15631
15632
15633
15634
15635
15636
15637
15638
15639
15640
15641
15642
15643
15644
15645
15646
15647
15648
15649
15650
15651
15652
15653
15654
15655
15656
15657
15658
15659
15660
15661
15662
15663
15664
15665
15666
15667
15668
15669
15670
15671
15672
15673
15674
15675
15676
15677
15678
15679
15680
15681
15682
15683
15684
15685
15686
15687
15688
15689
15690
15691
15692
15693
15694
15695
15696
15697
15698
15699
15700
15701
15702
15703
15704
15705
15706
15707
15708
15709
15710
15711
15712
15713
15714
15715
15716
15717
15718
15719
15720
15721
15722
15723
15724
15725
15726
15727
15728
15729
15730
15731
15732
15733
15734
15735
15736
15737
15738
15739
15740
15741
15742
15743
15744
15745
15746
15747
15748
15749
15750
15751
15752
15753
15754
15755
15756
15757
15758
15759
15760
15761
15762
15763
15764
15765
15766
15767
15768
15769
15770
15771
15772
15773
15774
15775
15776
15777
15778
15779
15780
15781
15782
15783
15784
15785
15786
15787
15788
15789
15790
15791
15792
15793
15794
15795
15796
15797
15798
15799
15800
15801
15802
15803
15804
15805
15806
15807
15808
15809
15810
15811
15812
15813
15814
15815
15816
15817
15818
15819
15820
15821
15822
15823
15824
15825
15826
15827
15828
15829
15830
15831
15832
15833
15834
15835
15836
15837
15838
15839
15840
15841
15842
15843
15844
15845
15846
15847
15848
15849
15850
15851
15852
15853
15854
15855
15856
15857
15858
15859
15860
15861
15862
15863
15864
15865
15866
15867
15868
15869
15870
15871
15872
15873
15874
15875
15876
15877
15878
15879
15880
15881
15882
15883
15884
15885
15886
15887
15888
15889
15890
15891
15892
15893
15894
15895
15896
15897
15898
15899
15900
15901
15902
15903
15904
15905
15906
15907
15908
15909
15910
15911
15912
15913
15914
15915
15916
15917
15918
15919
15920
15921
15922
15923
15924
15925
15926
15927
15928
15929
15930
15931
15932
15933
15934
15935
15936
15937
15938
15939
15940
15941
15942
15943
15944
15945
15946
15947
15948
15949
15950
15951
15952
15953
15954
15955
15956
15957
15958
15959
15960
15961
15962
15963
15964
15965
15966
15967
15968
15969
15970
15971
15972
15973
15974
15975
15976
15977
15978
15979
15980
15981
15982
15983
15984
15985
15986
15987
15988
15989
15990
15991
15992
15993
15994
15995
15996
15997
15998
15999
16000
16001
16002
16003
16004
16005
16006
16007
16008
16009
16010
16011
16012
16013
16014
16015
16016
16017
16018
16019
16020
16021
16022
16023
16024
16025
16026
16027
16028
16029
16030
16031
16032
16033
16034
16035
16036
16037
16038
16039
16040
16041
16042
16043
16044
16045
16046
16047
16048
16049
16050
16051
16052
16053
16054
16055
16056
16057
16058
16059
16060
16061
16062
16063
16064
16065
16066
16067
16068
16069
16070
16071
16072
16073
16074
16075
16076
16077
16078
16079
16080
16081
16082
16083
16084
16085
16086
16087
16088
16089
16090
16091
16092
16093
16094
16095
16096
16097
16098
16099
16100
16101
16102
16103
16104
16105
16106
16107
16108
16109
16110
16111
16112
16113
16114
16115
16116
16117
16118
16119
16120
16121
16122
16123
16124
16125
16126
16127
16128
16129
16130
16131
16132
16133
16134
16135
16136
16137
16138
16139
16140
16141
16142
16143
16144
16145
16146
16147
16148
16149
16150
16151
16152
16153
16154
16155
16156
16157
16158
16159
16160
16161
16162
16163
16164
16165
16166
16167
16168
16169
16170
16171
16172
16173
16174
16175
16176
16177
16178
16179
16180
16181
16182
16183
16184
16185
16186
16187
16188
16189
16190
16191
16192
16193
16194
16195
16196
16197
16198
16199
16200
16201
16202
16203
16204
16205
16206
16207
16208
16209
16210
16211
16212
16213
16214
16215
16216
16217
16218
16219
16220
16221
16222
16223
16224
16225
16226
16227
16228
16229
16230
16231
16232
16233
16234
16235
16236
16237
16238
16239
16240
16241
16242
16243
16244
16245
16246
16247
16248
16249
16250
16251
16252
16253
16254
16255
16256
16257
16258
16259
16260
16261
16262
16263
16264
16265
16266
16267
16268
16269
16270
16271
16272
16273
16274
16275
16276
16277
16278
16279
16280
16281
16282
16283
16284
16285
16286
16287
16288
16289
16290
16291
16292
16293
16294
16295
16296
16297
16298
16299
16300
16301
16302
16303
16304
16305
16306
16307
16308
16309
16310
16311
16312
16313
16314
16315
16316
16317
16318
16319
16320
16321
16322
16323
16324
16325
16326
16327
16328
16329
16330
16331
16332
16333
16334
16335
16336
16337
16338
16339
16340
16341
16342
16343
16344
16345
16346
16347
16348
16349
16350
16351
16352
16353
16354
16355
16356
16357
16358
16359
16360
16361
16362
16363
16364
16365
16366
16367
16368
16369
16370
16371
16372
16373
16374
16375
16376
16377
16378
16379
16380
16381
16382
16383
16384
16385
16386
16387
16388
16389
16390
16391
16392
16393
16394
16395
16396
16397
16398
16399
16400
16401
16402
16403
16404
16405
16406
16407
16408
16409
16410
16411
16412
16413
16414
16415
16416
16417
16418
16419
16420
16421
16422
16423
16424
16425
16426
16427
16428
16429
16430
16431
16432
16433
16434
16435
16436
16437
16438
16439
16440
16441
16442
16443
16444
16445
16446
16447
16448
16449
16450
16451
16452
16453
16454
16455
16456
16457
16458
16459
16460
16461
16462
16463
16464
16465
16466
16467
16468
16469
16470
16471
16472
16473
16474
16475
16476
16477
16478
16479
16480
16481
16482
16483
16484
16485
16486
16487
16488
16489
16490
16491
16492
16493
16494
16495
16496
16497
16498
16499
16500
16501
16502
16503
16504
16505
16506
16507
16508
16509
16510
16511
16512
16513
16514
16515
16516
16517
16518
16519
16520
16521
16522
16523
16524
16525
16526
16527
16528
16529
16530
16531
16532
16533
16534
16535
16536
16537
16538
16539
16540
16541
16542
16543
16544
16545
16546
16547
16548
16549
16550
16551
16552
16553
16554
16555
16556
16557
16558
16559
16560
16561
16562
16563
16564
16565
16566
16567
16568
16569
16570
16571
16572
16573
16574
16575
16576
16577
16578
16579
16580
16581
16582
16583
16584
16585
16586
16587
16588
16589
16590
16591
16592
16593
16594
16595
16596
16597
16598
16599
16600
16601
16602
16603
16604
16605
16606
16607
16608
16609
16610
16611
16612
16613
16614
16615
16616
16617
16618
16619
16620
16621
16622
16623
16624
16625
16626
16627
16628
16629
16630
16631
16632
16633
16634
16635
16636
16637
16638
16639
16640
16641
16642
16643
16644
16645
16646
16647
16648
16649
16650
16651
16652
16653
16654
16655
16656
16657
16658
16659
16660
16661
16662
16663
16664
16665
16666
16667
16668
16669
16670
16671
16672
16673
16674
16675
16676
16677
16678
16679
16680
16681
16682
16683
16684
16685
16686
16687
16688
16689
16690
16691
16692
16693
16694
16695
16696
16697
16698
16699
16700
16701
16702
16703
16704
16705
16706
16707
16708
16709
16710
16711
16712
16713
16714
16715
16716
16717
16718
16719
16720
16721
16722
16723
16724
16725
16726
16727
16728
16729
16730
16731
16732
16733
16734
16735
16736
16737
16738
16739
16740
16741
16742
16743
16744
16745
16746
16747
16748
16749
16750
16751
16752
16753
16754
16755
16756
16757
16758
16759
16760
16761
16762
16763
16764
16765
16766
16767
16768
16769
16770
16771
16772
16773
16774
16775
16776
16777
16778
16779
16780
16781
16782
16783
16784
16785
16786
16787
16788
16789
16790
16791
16792
16793
16794
16795
16796
16797
16798
16799
16800
16801
16802
16803
16804
16805
16806
16807
16808
16809
16810
16811
16812
16813
16814
16815
16816
16817
16818
16819
16820
16821
16822
16823
16824
16825
16826
16827
16828
16829
16830
16831
16832
16833
16834
16835
16836
16837
16838
16839
16840
16841
16842
16843
16844
16845
16846
16847
16848
16849
16850
16851
16852
16853
16854
16855
16856
16857
16858
16859
16860
16861
16862
16863
16864
16865
16866
16867
16868
16869
16870
16871
16872
16873
16874
16875
16876
16877
16878
16879
16880
16881
16882
16883
16884
16885
16886
16887
16888
16889
16890
16891
16892
16893
16894
16895
16896
16897
16898
16899
16900
16901
16902
16903
16904
16905
16906
16907
16908
16909
16910
16911
16912
16913
16914
16915
16916
16917
16918
16919
16920
16921
16922
16923
16924
16925
16926
16927
16928
16929
16930
16931
16932
16933
16934
16935
16936
16937
16938
16939
16940
16941
16942
16943
16944
16945
16946
16947
16948
16949
16950
16951
16952
16953
16954
16955
16956
16957
16958
16959
16960
16961
16962
16963
16964
16965
16966
16967
16968
16969
16970
16971
16972
16973
16974
16975
16976
16977
16978
16979
16980
16981
16982
16983
16984
16985
16986
16987
16988
16989
16990
16991
16992
16993
16994
16995
16996
16997
16998
16999
17000
17001
17002
17003
17004
17005
17006
17007
17008
17009
17010
17011
17012
17013
17014
17015
17016
17017
17018
17019
17020
17021
17022
17023
17024
17025
17026
17027
17028
17029
17030
17031
17032
17033
17034
17035
17036
17037
17038
17039
17040
17041
17042
17043
17044
17045
17046
17047
17048
17049
17050
17051
17052
17053
17054
17055
17056
17057
17058
17059
17060
17061
17062
17063
17064
17065
17066
17067
17068
17069
17070
17071
17072
17073
17074
17075
17076
17077
17078
17079
17080
17081
17082
17083
17084
17085
17086
17087
17088
17089
17090
17091
17092
17093
17094
17095
17096
17097
17098
17099
17100
17101
17102
17103
17104
17105
17106
17107
17108
17109
17110
17111
17112
17113
17114
17115
17116
17117
17118
17119
17120
17121
17122
17123
17124
17125
17126
17127
17128
17129
17130
17131
17132
17133
17134
17135
17136
17137
17138
17139
17140
17141
17142
17143
17144
17145
17146
17147
17148
17149
17150
17151
17152
17153
17154
17155
17156
17157
17158
17159
17160
17161
17162
17163
17164
17165
17166
17167
17168
17169
17170
17171
17172
17173
17174
17175
17176
17177
17178
17179
17180
17181
17182
17183
17184
17185
17186
17187
17188
17189
17190
17191
17192
17193
17194
17195
17196
17197
17198
17199
17200
17201
17202
17203
17204
17205
17206
17207
17208
17209
17210
17211
17212
17213
17214
17215
17216
17217
17218
17219
17220
17221
17222
17223
17224
17225
17226
17227
17228
17229
17230
17231
17232
17233
17234
17235
17236
17237
17238
17239
17240
17241
17242
17243
17244
17245
17246
17247
17248
17249
17250
17251
17252
17253
17254
17255
17256
17257
17258
17259
17260
17261
17262
17263
17264
17265
17266
17267
17268
17269
17270
17271
17272
17273
17274
17275
17276
17277
17278
17279
17280
17281
17282
17283
17284
17285
17286
17287
17288
17289
17290
17291
17292
17293
17294
17295
17296
17297
17298
17299
17300
17301
17302
17303
17304
17305
17306
17307
17308
17309
17310
17311
17312
17313
17314
17315
17316
17317
17318
17319
17320
17321
17322
17323
17324
17325
17326
17327
17328
17329
17330
17331
17332
17333
17334
17335
17336
17337
17338
17339
17340
17341
17342
17343
17344
17345
17346
17347
17348
17349
17350
17351
17352
17353
17354
17355
17356
17357
17358
17359
17360
17361
17362
17363
17364
17365
17366
17367
17368
17369
17370
17371
17372
17373
17374
17375
17376
17377
17378
17379
17380
17381
17382
17383
17384
17385
17386
17387
17388
17389
17390
17391
17392
17393
17394
17395
17396
17397
17398
17399
17400
17401
17402
17403
17404
17405
17406
17407
17408
17409
17410
17411
17412
17413
17414
17415
17416
17417
17418
17419
17420
17421
17422
17423
17424
17425
17426
17427
17428
17429
17430
17431
17432
17433
17434
17435
17436
17437
17438
17439
17440
17441
17442
17443
17444
17445
17446
17447
17448
17449
17450
17451
17452
17453
17454
17455
17456
17457
17458
17459
17460
17461
17462
17463
17464
17465
17466
17467
17468
17469
17470
17471
17472
17473
17474
17475
17476
17477
17478
17479
17480
17481
17482
17483
17484
17485
17486
17487
17488
17489
17490
17491
17492
17493
17494
17495
17496
17497
17498
17499
17500
17501
17502
17503
17504
17505
17506
17507
17508
17509
17510
17511
17512
17513
17514
17515
17516
17517
17518
17519
17520
17521
17522
17523
17524
17525
17526
17527
17528
17529
17530
17531
17532
17533
17534
17535
17536
17537
17538
17539
17540
17541
17542
17543
17544
17545
17546
17547
17548
17549
17550
17551
17552
17553
17554
17555
17556
17557
17558
17559
17560
17561
17562
17563
17564
17565
17566
17567
17568
17569
17570
17571
17572
17573
17574
17575
17576
17577
17578
17579
17580
17581
17582
17583
17584
17585
17586
17587
17588
17589
17590
17591
17592
17593
17594
17595
17596
17597
17598
17599
17600
17601
17602
17603
17604
17605
17606
17607
17608
17609
17610
17611
17612
17613
17614
17615
17616
17617
17618
17619
17620
17621
17622
17623
17624
17625
17626
17627
17628
17629
17630
17631
17632
17633
17634
17635
17636
17637
17638
17639
17640
17641
17642
17643
17644
17645
17646
17647
17648
17649
17650
17651
17652
17653
17654
17655
17656
17657
17658
17659
17660
17661
17662
17663
17664
17665
17666
17667
17668
17669
17670
17671
17672
17673
17674
17675
17676
17677
17678
17679
17680
17681
17682
17683
17684
17685
17686
17687
17688
17689
17690
17691
17692
17693
17694
17695
17696
17697
17698
17699
17700
17701
17702
17703
17704
17705
17706
17707
17708
17709
17710
17711
17712
17713
17714
17715
17716
17717
17718
17719
17720
17721
17722
17723
17724
17725
17726
17727
17728
17729
17730
17731
17732
17733
17734
17735
17736
17737
17738
17739
17740
17741
17742
17743
17744
17745
17746
17747
17748
17749
17750
17751
17752
17753
17754
17755
17756
17757
17758
17759
17760
17761
17762
17763
17764
17765
17766
17767
17768
17769
17770
17771
17772
17773
17774
17775
17776
17777
17778
17779
17780
17781
17782
17783
17784
17785
17786
17787
17788
17789
17790
17791
17792
17793
17794
17795
17796
17797
17798
17799
17800
17801
17802
17803
17804
17805
17806
17807
17808
17809
17810
17811
17812
17813
17814
17815
17816
17817
17818
17819
17820
17821
17822
17823
17824
17825
17826
17827
17828
17829
17830
17831
17832
17833
17834
17835
17836
17837
17838
17839
17840
17841
17842
17843
17844
17845
17846
17847
17848
17849
17850
17851
17852
17853
17854
17855
17856
17857
17858
17859
17860
17861
17862
17863
17864
17865
17866
17867
17868
17869
17870
17871
17872
17873
17874
17875
17876
17877
17878
17879
17880
17881
17882
17883
17884
17885
17886
17887
17888
17889
17890
17891
17892
17893
17894
17895
17896
17897
17898
17899
17900
17901
17902
17903
17904
17905
17906
17907
17908
17909
17910
17911
17912
17913
17914
17915
17916
17917
17918
17919
17920
17921
17922
17923
17924
17925
17926
17927
17928
17929
17930
17931
17932
17933
17934
17935
17936
17937
17938
17939
17940
17941
17942
17943
17944
17945
17946
17947
17948
17949
17950
17951
17952
17953
17954
17955
17956
17957
17958
17959
17960
17961
17962
17963
17964
17965
17966
17967
17968
17969
17970
17971
17972
17973
17974
17975
17976
17977
17978
17979
17980
17981
17982
17983
17984
17985
17986
17987
17988
17989
17990
17991
17992
17993
17994
17995
17996
17997
17998
17999
18000
18001
18002
18003
18004
18005
18006
18007
18008
18009
18010
18011
18012
18013
18014
18015
18016
18017
18018
18019
18020
18021
18022
18023
18024
18025
18026
18027
18028
18029
18030
18031
18032
18033
18034
18035
18036
18037
18038
18039
18040
18041
18042
18043
18044
18045
18046
18047
18048
18049
18050
18051
18052
18053
18054
18055
18056
18057
18058
18059
18060
18061
18062
18063
18064
18065
18066
18067
18068
18069
18070
18071
18072
18073
18074
18075
18076
18077
18078
18079
18080
18081
18082
18083
18084
18085
18086
18087
18088
18089
18090
18091
18092
18093
18094
18095
18096
18097
18098
18099
18100
18101
18102
18103
18104
18105
18106
18107
18108
18109
18110
18111

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>The Bugzilla Guide - 4.0 
    Release</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><META
NAME="KEYWORD"
CONTENT="Bugzilla"><META
NAME="KEYWORD"
CONTENT="Guide"><META
NAME="KEYWORD"
CONTENT="installation"><META
NAME="KEYWORD"
CONTENT="FAQ"><META
NAME="KEYWORD"
CONTENT="administration"><META
NAME="KEYWORD"
CONTENT="integration"><META
NAME="KEYWORD"
CONTENT="MySQL"><META
NAME="KEYWORD"
CONTENT="Mozilla"><META
NAME="KEYWORD"
CONTENT="webtools"></HEAD
><BODY
CLASS="book"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="BOOK"
><A
NAME="index"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
><A
NAME="AEN2"
>The Bugzilla Guide - 4.0 
    Release</A
></H1
><H3
CLASS="corpauthor"
>The Bugzilla Team</H3
><P
CLASS="pubdate"
>2011-02-15<BR></P
><DIV
><DIV
CLASS="abstract"
><P
></P
><A
NAME="AEN7"
></A
><P
>&#13;	      This is the documentation for Bugzilla, a 
	      bug-tracking system from mozilla.org.
	      Bugzilla is an enterprise-class piece of software
	      that tracks millions of bugs and issues for hundreds of
	      organizations around the world.
      </P
><P
>&#13;        The most current version of this document can always be found on the
        <A
HREF="http://www.bugzilla.org/docs/"
TARGET="_top"
>Bugzilla 
        Documentation Page</A
>.
      </P
><P
></P
></DIV
></DIV
><HR></DIV
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>1. <A
HREF="#about"
>About This Guide</A
></DT
><DD
><DL
><DT
>1.1. <A
HREF="#copyright"
>Copyright Information</A
></DT
><DT
>1.2. <A
HREF="#disclaimer"
>Disclaimer</A
></DT
><DT
>1.3. <A
HREF="#newversions"
>New Versions</A
></DT
><DT
>1.4. <A
HREF="#credits"
>Credits</A
></DT
><DT
>1.5. <A
HREF="#conventions"
>Document Conventions</A
></DT
></DL
></DD
><DT
>2. <A
HREF="#installing-bugzilla"
>Installing Bugzilla</A
></DT
><DD
><DL
><DT
>2.1. <A
HREF="#installation"
>Installation</A
></DT
><DT
>2.2. <A
HREF="#configuration"
>Configuration</A
></DT
><DT
>2.3. <A
HREF="#extraconfig"
>Optional Additional Configuration</A
></DT
><DT
>2.4. <A
HREF="#multiple-bz-dbs"
>Multiple Bugzilla databases with a single installation</A
></DT
><DT
>2.5. <A
HREF="#os-specific"
>OS-Specific Installation Notes</A
></DT
><DT
>2.6. <A
HREF="#nonroot"
>UNIX (non-root) Installation Notes</A
></DT
><DT
>2.7. <A
HREF="#upgrade"
>Upgrading to New Releases</A
></DT
></DL
></DD
><DT
>3. <A
HREF="#administration"
>Administering Bugzilla</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="#parameters"
>Bugzilla Configuration</A
></DT
><DT
>3.2. <A
HREF="#useradmin"
>User Administration</A
></DT
><DT
>3.3. <A
HREF="#classifications"
>Classifications</A
></DT
><DT
>3.4. <A
HREF="#products"
>Products</A
></DT
><DT
>3.5. <A
HREF="#components"
>Components</A
></DT
><DT
>3.6. <A
HREF="#versions"
>Versions</A
></DT
><DT
>3.7. <A
HREF="#milestones"
>Milestones</A
></DT
><DT
>3.8. <A
HREF="#flags-overview"
>Flags</A
></DT
><DT
>3.9. <A
HREF="#keywords"
>Keywords</A
></DT
><DT
>3.10. <A
HREF="#custom-fields"
>Custom Fields</A
></DT
><DT
>3.11. <A
HREF="#edit-values"
>Legal Values</A
></DT
><DT
>3.12. <A
HREF="#bug_status_workflow"
>Bug Status Workflow</A
></DT
><DT
>3.13. <A
HREF="#voting"
>Voting</A
></DT
><DT
>3.14. <A
HREF="#quips"
>Quips</A
></DT
><DT
>3.15. <A
HREF="#groups"
>Groups and Group Security</A
></DT
><DT
>3.16. <A
HREF="#sanitycheck"
>Checking and Maintaining Database Integrity</A
></DT
></DL
></DD
><DT
>4. <A
HREF="#security"
>Bugzilla Security</A
></DT
><DD
><DL
><DT
>4.1. <A
HREF="#security-os"
>Operating System</A
></DT
><DT
>4.2. <A
HREF="#security-webserver"
>Web server</A
></DT
><DT
>4.3. <A
HREF="#security-bugzilla"
>Bugzilla</A
></DT
></DL
></DD
><DT
>5. <A
HREF="#using"
>Using Bugzilla</A
></DT
><DD
><DL
><DT
>5.1. <A
HREF="#using-intro"
>Introduction</A
></DT
><DT
>5.2. <A
HREF="#myaccount"
>Create a Bugzilla Account</A
></DT
><DT
>5.3. <A
HREF="#bug_page"
>Anatomy of a Bug</A
></DT
><DT
>5.4. <A
HREF="#lifecycle"
>Life Cycle of a Bug</A
></DT
><DT
>5.5. <A
HREF="#query"
>Searching for Bugs</A
></DT
><DT
>5.6. <A
HREF="#bugreports"
>Filing Bugs</A
></DT
><DT
>5.7. <A
HREF="#attachments"
>Attachments</A
></DT
><DT
>5.8. <A
HREF="#hintsandtips"
>Hints and Tips</A
></DT
><DT
>5.9. <A
HREF="#timetracking"
>Time Tracking Information</A
></DT
><DT
>5.10. <A
HREF="#userpreferences"
>User Preferences</A
></DT
><DT
>5.11. <A
HREF="#reporting"
>Reports and Charts</A
></DT
><DT
>5.12. <A
HREF="#flags"
>Flags</A
></DT
><DT
>5.13. <A
HREF="#whining"
>Whining</A
></DT
></DL
></DD
><DT
>6. <A
HREF="#customization"
>Customizing Bugzilla</A
></DT
><DD
><DL
><DT
>6.1. <A
HREF="#extensions"
>Bugzilla Extensions</A
></DT
><DT
>6.2. <A
HREF="#cust-skins"
>Custom Skins</A
></DT
><DT
>6.3. <A
HREF="#cust-templates"
>Template Customization</A
></DT
><DT
>6.4. <A
HREF="#cust-change-permissions"
>Customizing Who Can Change What</A
></DT
><DT
>6.5. <A
HREF="#integration"
>Integrating Bugzilla with Third-Party Tools</A
></DT
></DL
></DD
><DT
>A. <A
HREF="#troubleshooting"
>Troubleshooting</A
></DT
><DD
><DL
><DT
>A.1. <A
HREF="#general-advice"
>General Advice</A
></DT
><DT
>A.2. <A
HREF="#trbl-testserver"
>The Apache web server is not serving Bugzilla pages</A
></DT
><DT
>A.3. <A
HREF="#trbl-perlmodule"
>I installed a Perl module, but 
      <TT
CLASS="filename"
>checksetup.pl</TT
> claims it's not installed!</A
></DT
><DT
>A.4. <A
HREF="#trbl-dbdSponge"
>DBD::Sponge::db prepare failed</A
></DT
><DT
>A.5. <A
HREF="#paranoid-security"
>cannot chdir(/var/spool/mqueue)</A
></DT
><DT
>A.6. <A
HREF="#trbl-relogin-everyone"
>Everybody is constantly being forced to relogin</A
></DT
><DT
>A.7. <A
HREF="#trbl-index"
><TT
CLASS="filename"
>index.cgi</TT
> doesn't show up unless specified in the URL</A
></DT
><DT
>A.8. <A
HREF="#trbl-passwd-encryption"
>checksetup.pl reports "Client does not support authentication protocol
      requested by server..."</A
></DT
></DL
></DD
><DT
>B. <A
HREF="#patches"
>Contrib</A
></DT
><DD
><DL
><DT
>B.1. <A
HREF="#cmdline"
>Command-line Search Interface</A
></DT
><DT
>B.2. <A
HREF="#cmdline-bugmail"
>Command-line 'Send Unsent Bug-mail' tool</A
></DT
></DL
></DD
><DT
>C. <A
HREF="#install-perlmodules-manual"
>Manual Installation of Perl Modules</A
></DT
><DD
><DL
><DT
>C.1. <A
HREF="#modules-manual-instructions"
>Instructions</A
></DT
><DT
>C.2. <A
HREF="#modules-manual-download"
>Download Locations</A
></DT
><DT
>C.3. <A
HREF="#modules-manual-optional"
>Optional Modules</A
></DT
></DL
></DD
><DT
>D. <A
HREF="#gfdl"
>GNU Free Documentation License</A
></DT
><DD
><DL
><DT
>0. <A
HREF="#gfdl-0"
>Preamble</A
></DT
><DT
>1. <A
HREF="#gfdl-1"
>Applicability and Definition</A
></DT
><DT
>2. <A
HREF="#gfdl-2"
>Verbatim Copying</A
></DT
><DT
>3. <A
HREF="#gfdl-3"
>Copying in Quantity</A
></DT
><DT
>4. <A
HREF="#gfdl-4"
>Modifications</A
></DT
><DT
>5. <A
HREF="#gfdl-5"
>Combining Documents</A
></DT
><DT
>6. <A
HREF="#gfdl-6"
>Collections of Documents</A
></DT
><DT
>7. <A
HREF="#gfdl-7"
>Aggregation with Independent Works</A
></DT
><DT
>8. <A
HREF="#gfdl-8"
>Translation</A
></DT
><DT
>9. <A
HREF="#gfdl-9"
>Termination</A
></DT
><DT
>10. <A
HREF="#gfdl-10"
>Future Revisions of this License</A
></DT
><DT
><A
HREF="#gfdl-howto"
>How to use this License for your documents</A
></DT
></DL
></DD
><DT
><A
HREF="#glossary"
>Glossary</A
></DT
></DL
></DIV
><DIV
CLASS="LOT"
><DL
CLASS="LOT"
><DT
><B
>List of Figures</B
></DT
><DT
>5-1. <A
HREF="#lifecycle-image"
>Lifecycle of a Bugzilla Bug</A
></DT
></DL
></DIV
><DIV
CLASS="LOT"
><DL
CLASS="LOT"
><DT
><B
>List of Examples</B
></DT
><DT
>A-1. <A
HREF="#trbl-relogin-everyone-share"
>Examples of urlbase/cookiepath pairs for sharing login cookies</A
></DT
><DT
>A-2. <A
HREF="#trbl-relogin-everyone-restrict"
>Examples of urlbase/cookiepath pairs to restrict the login cookie</A
></DT
></DL
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="about"
></A
>Chapter 1. About This Guide</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="copyright"
>1.1. Copyright Information</A
></H2
><P
>This document is copyright (c) 2000-2011 by the various
    Bugzilla contributors who wrote it.</P
><A
NAME="AEN26"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13;	Permission is granted to copy, distribute and/or modify this
	document under the terms of the GNU Free Documentation
	License, Version 1.1 or any later version published by the
	Free Software Foundation; with no Invariant Sections, no
	Front-Cover Texts, and with no Back-Cover Texts. A copy of
	the license is included in <A
HREF="#gfdl"
>Appendix D</A
>.
      </P
></BLOCKQUOTE
><P
>&#13;      If you have any questions regarding this document, its
      copyright, or publishing this document in non-electronic form,
      please contact the Bugzilla Team. 
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="disclaimer"
>1.2. Disclaimer</A
></H2
><P
>&#13;      No liability for the contents of this document can be accepted.
      Follow the instructions herein at your own risk.
      This document may contain errors
      and inaccuracies that may damage your system, cause your partner 
      to leave you, your boss to fire you, your cats to
      pee on your furniture and clothing, and global thermonuclear
      war. Proceed with caution.
    </P
><P
>&#13;      Naming of particular products or brands should not be seen as
      endorsements, with the exception of the term "GNU/Linux". We
      wholeheartedly endorse the use of GNU/Linux; it is an extremely 
      versatile, stable,
      and robust operating system that offers an ideal operating
      environment for Bugzilla.
    </P
><P
>&#13;      Although the Bugzilla development team has taken great care to
      ensure that all exploitable bugs have been fixed, security holes surely 
      exist in any piece of code. Great care should be taken both in 
      the installation and usage of this software. The Bugzilla development
      team members assume no liability for your use of Bugzilla. You have 
      the source code, and are responsible for auditing it yourself to ensure
      your security needs are met.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="newversions"
>1.3. New Versions</A
></H2
><P
>&#13;      This is the 4.0 version of The Bugzilla Guide. It is so named 
      to match the current version of Bugzilla. 
    </P
><P
>&#13;      The latest version of this guide can always be found at <A
HREF="http://www.bugzilla.org/docs/"
TARGET="_top"
>http://www.bugzilla.org/docs/</A
>. However, you should read
      the version which came with the Bugzilla release you are using.
    </P
><P
>  
      In addition, there are Bugzilla template localization projects in
      <A
HREF="http://www.bugzilla.org/download/#localizations"
TARGET="_top"
>several languages</A
>.
      They may have translated documentation available. If you would like to
      volunteer to translate the Guide into additional languages, please visit the
      <A
HREF="https://wiki.mozilla.org/Bugzilla:L10n"
TARGET="_top"
>Bugzilla L10n team</A
>
      page.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="credits"
>1.4. Credits</A
></H2
><P
>&#13;      The people listed below have made enormous contributions to the
      creation of this Guide, through their writing, dedicated hacking efforts,
      numerous e-mail and IRC support sessions, and overall excellent
      contribution to the Bugzilla community:
    </P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>Matthew P. Barnson <CODE
CLASS="email"
>&#60;<A
HREF="mailto:mbarnson@sisna.com"
>mbarnson@sisna.com</A
>&#62;</CODE
></DT
><DD
><P
>for the Herculean task of pulling together the Bugzilla Guide
          and shepherding it to 2.14.
          </P
></DD
><DT
>Terry Weissman <CODE
CLASS="email"
>&#60;<A
HREF="mailto:terry@mozilla.org"
>terry@mozilla.org</A
>&#62;</CODE
></DT
><DD
><P
>for initially writing Bugzilla and creating the README upon
          which the UNIX installation documentation is largely based.
          </P
></DD
><DT
>Tara Hernandez <CODE
CLASS="email"
>&#60;<A
HREF="mailto:tara@tequilarists.org"
>tara@tequilarists.org</A
>&#62;</CODE
></DT
><DD
><P
>for keeping Bugzilla development going strong after Terry left
          mozilla.org and for running landfill.
          </P
></DD
><DT
>Dave Lawrence <CODE
CLASS="email"
>&#60;<A
HREF="mailto:dkl@redhat.com"
>dkl@redhat.com</A
>&#62;</CODE
></DT
><DD
><P
>for providing insight into the key differences between Red
          Hat's customized Bugzilla.
          </P
></DD
><DT
>Dawn Endico <CODE
CLASS="email"
>&#60;<A
HREF="mailto:endico@mozilla.org"
>endico@mozilla.org</A
>&#62;</CODE
></DT
><DD
><P
>for being a hacker extraordinaire and putting up with Matthew's
          incessant questions and arguments on irc.mozilla.org in #mozwebtools
          </P
></DD
><DT
>Jacob Steenhagen <CODE
CLASS="email"
>&#60;<A
HREF="mailto:jake@bugzilla.org"
>jake@bugzilla.org</A
>&#62;</CODE
></DT
><DD
><P
>for taking over documentation during the 2.17 development
          period.
          </P
></DD
><DT
>Dave Miller <CODE
CLASS="email"
>&#60;<A
HREF="mailto:justdave@bugzilla.org"
>justdave@bugzilla.org</A
>&#62;</CODE
></DT
><DD
><P
>for taking over as project lead when Tara stepped down and
	  continually pushing for the documentation to be the best it can be.
          </P
></DD
></DL
></DIV
><P
>&#13;      Thanks also go to the following people for significant contributions 
      to this documentation:
      Kevin Brannen, Vlad Dascalu, Ben FrantzDale, Eric Hanson, Zach Lipton, Gervase Markham, Andrew Pearson, Joe Robins, Spencer Smith, Ron Teitelbaum, Shane Travis, Martin Wulffeld.
    </P
><P
>&#13;      Also, thanks are due to the members of the 
      <A
HREF="news://news.mozilla.org/mozilla.support.bugzilla"
TARGET="_top"
>&#13;      mozilla.support.bugzilla</A
>
      newsgroup (and its predecessor, netscape.public.mozilla.webtools).
      Without your discussions, insight, suggestions, and patches,
      this could never have happened.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="conventions"
>1.5. Document Conventions</A
></H2
><P
>This document uses the following conventions:</P
><DIV
CLASS="informaltable"
><P
></P
><A
NAME="AEN103"
></A
><TABLE
BORDER="0"
FRAME="void"
CLASS="CALSTABLE"
><COL><COL><THEAD
><TR
><TH
>Descriptions</TH
><TH
>Appearance</TH
></TR
></THEAD
><TBODY
><TR
><TD
>Caution</TD
><TD
>&#13;            <DIV
CLASS="caution"
><P
></P
><TABLE
CLASS="caution"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Don't run with scissors!</P
></TD
></TR
></TABLE
></DIV
>
          </TD
></TR
><TR
><TD
>Hint or Tip</TD
><TD
>&#13;            <DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>For best results... </P
></TD
></TR
></TABLE
></DIV
>
          </TD
></TR
><TR
><TD
>Note</TD
><TD
>&#13;            <DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Dear John...</P
></TD
></TR
></TABLE
></DIV
>
          </TD
></TR
><TR
><TD
>Warning</TD
><TD
>&#13;            <DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Read this or the cat gets it.</P
></TD
></TR
></TABLE
></DIV
>
          </TD
></TR
><TR
><TD
>File or directory name</TD
><TD
>&#13;            <TT
CLASS="filename"
>filename</TT
>
          </TD
></TR
><TR
><TD
>Command to be typed</TD
><TD
>&#13;            <B
CLASS="command"
>command</B
>
          </TD
></TR
><TR
><TD
>Application name</TD
><TD
>&#13;            <SPAN
CLASS="application"
>application</SPAN
>
          </TD
></TR
><TR
><TD
>&#13;          Normal user's prompt under bash shell</TD
><TD
>bash$</TD
></TR
><TR
><TD
>&#13;          Root user's prompt under bash shell</TD
><TD
>bash#</TD
></TR
><TR
><TD
>&#13;          Normal user's prompt under tcsh shell</TD
><TD
>tcsh$</TD
></TR
><TR
><TD
>Environment variables</TD
><TD
>&#13;            <CODE
CLASS="envar"
>VARIABLE</CODE
>
          </TD
></TR
><TR
><TD
>Term found in the glossary</TD
><TD
>&#13;            <A
HREF="#gloss-bugzilla"
><I
CLASS="glossterm"
>Bugzilla</I
></A
>
          </TD
></TR
><TR
><TD
>Code example</TD
><TD
>&#13;            <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
><CODE
CLASS="sgmltag"
>&#60;para&#62;</CODE
>
Beginning and end of paragraph
<CODE
CLASS="sgmltag"
>&#60;/para&#62;</CODE
></PRE
></FONT
></TD
></TR
></TABLE
>
          </TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>  
	  This documentation is maintained in DocBook 4.1.2 XML format.
    Changes are best submitted as plain text or XML diffs, attached
    to a bug filed in the <A
HREF="https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&#38;component=Documentation"
TARGET="_top"
>Bugzilla Documentation</A
> component.
  </P
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="installing-bugzilla"
></A
>Chapter 2. Installing Bugzilla</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="installation"
>2.1. Installation</A
></H2
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you just want to <EM
>use</EM
> Bugzilla, 
      you do not need to install it. None of this chapter is relevant to
      you. Ask your Bugzilla administrator for the URL to access it from
      your web browser.
      </P
></TD
></TR
></TABLE
></DIV
><P
>The Bugzilla server software is usually installed on Linux or 
    Solaris. 
    If you are installing on another OS, check <A
HREF="#os-specific"
>Section 2.5</A
>
    before you start your installation to see if there are any special
    instructions.
    </P
><P
>This guide assumes that you have administrative access to the
    Bugzilla machine. It not possible to
    install and run Bugzilla itself without administrative access except
    in the very unlikely event that every single prerequisite is
    already installed.
    </P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The installation process may make your machine insecure for
      short periods of time. Make sure there is a firewall between you
      and the Internet.
      </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;    You are strongly recommended to make a backup of your system
    before installing Bugzilla (and at regular intervals thereafter :-).
    </P
><P
>In outline, the installation proceeds as follows:
    </P
><DIV
CLASS="procedure"
><OL
TYPE="1"
><LI
CLASS="step"
><P
><A
HREF="#install-perl"
>Install Perl</A
>
        (5.8.1 or above)
        </P
></LI
><LI
CLASS="step"
><P
><A
HREF="#install-database"
>Install a Database Engine</A
>
        </P
></LI
><LI
CLASS="step"
><P
><A
HREF="#install-webserver"
>Install a Webserver</A
>
        </P
></LI
><LI
CLASS="step"
><P
><A
HREF="#install-bzfiles"
>Install Bugzilla</A
>
        </P
></LI
><LI
CLASS="step"
><P
><A
HREF="#install-perlmodules"
>Install Perl modules</A
>
        </P
></LI
><LI
CLASS="step"
><P
>&#13;          <A
HREF="#install-MTA"
>Install a Mail Transfer Agent</A
>
          (Sendmail 8.7 or above, or an MTA that is Sendmail-compatible with at least this version)
        </P
></LI
><LI
CLASS="step"
><P
>Configure all of the above.
        </P
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-perl"
>2.1.1. Perl</A
></H3
><P
>Installed Version Test: <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>perl -v</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>Any machine that doesn't have Perl on it is a sad machine indeed.
      If you don't have it and your OS doesn't provide official packages, 
      visit <A
HREF="http://www.perl.org"
TARGET="_top"
>http://www.perl.org</A
>.
      Although Bugzilla runs with Perl 5.8.1,
      it's a good idea to be using the latest stable version.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-database"
>2.1.2. Database Engine</A
></H3
><P
>&#13;        Bugzilla supports MySQL, PostgreSQL and Oracle as database servers.
        You only require one of these systems to make use of Bugzilla.
      </P
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="install-mysql"
>2.1.2.1. MySQL</A
></H4
><P
>Installed Version Test: <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>mysql -V</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>&#13;          If you don't have it and your OS doesn't provide official packages, 
          visit <A
HREF="http://www.mysql.com"
TARGET="_top"
>http://www.mysql.com</A
>. You need MySQL version
          4.1.2 or higher.
          </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Many of the binary
            versions of MySQL store their data files in 
            <TT
CLASS="filename"
>/var</TT
>.
            On some Unix systems, this is part of a smaller root partition,
            and may not have room for your bug database. To change the data
            directory, you have to build MySQL from source yourself, and
            set it as an option to <TT
CLASS="filename"
>configure</TT
>.</P
></TD
></TR
></TABLE
></DIV
><P
>If you install from something other than a packaging/installation
          system, such as .rpm (Redhat Package), .deb (Debian Package), .exe
          (Windows Executable), or .msi (Microsoft Installer), make sure the MySQL
          server is started when the machine boots.
          </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="install-pg"
>2.1.2.2. PostgreSQL</A
></H4
><P
>Installed Version Test: <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>psql -V</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>&#13;          If you don't have it and your OS doesn't provide official packages, 
          visit <A
HREF="http://www.postgresql.org/"
TARGET="_top"
>http://www.postgresql.org/</A
>. You need PostgreSQL
          version 8.00.0000 or higher.
          </P
><P
>If you install from something other than a packaging/installation
          system, such as .rpm (Redhat Package), .deb (Debian Package), .exe
          (Windows Executable), or .msi (Microsoft Installer), make sure the
          PostgreSQL server is started when the machine boots.
          </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="install-oracle"
>2.1.2.3. Oracle</A
></H4
><P
>&#13;          Installed Version Test: <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>select * from v$version</PRE
></FONT
></TD
></TR
></TABLE
>
          (you first have to log in into your DB)
        </P
><P
>&#13;          If you don't have it and your OS doesn't provide official packages,
          visit <A
HREF="http://www.oracle.com/"
TARGET="_top"
>http://www.oracle.com/</A
>. You need Oracle
          version 10.02.0 or higher.
        </P
><P
>&#13;          If you install from something other than a packaging/installation
          system, such as .rpm (Redhat Package), .deb (Debian Package), .exe
          (Windows Executable), or .msi (Microsoft Installer), make sure the
          Oracle server is started when the machine boots.
        </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-webserver"
>2.1.3. Web Server</A
></H3
><P
>Installed Version Test: view the default welcome page at
      http://&#60;your-machine&#62;/</P
><P
>You have freedom of choice here, pretty much any web server that
      is capable of running <A
HREF="#gloss-cgi"
><I
CLASS="glossterm"
>CGI</I
></A
>
      scripts will work.
       However, we strongly recommend using the Apache web server
       (either 1.3.x or 2.x), and 
       the installation instructions usually assume you are
        using it. If you have got Bugzilla working using another web server,
        please share your experiences with us by filing a bug in <A
HREF="https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&#38;component=Documentation"
TARGET="_top"
>Bugzilla Documentation</A
>.
      </P
><P
>&#13;      If you don't have Apache and your OS doesn't provide official packages, 
      visit <A
HREF="http://httpd.apache.org/"
TARGET="_top"
>http://httpd.apache.org/</A
>.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-bzfiles"
>2.1.4. Bugzilla</A
></H3
><P
>&#13;        <A
HREF="http://www.bugzilla.org/download/"
TARGET="_top"
>Download a Bugzilla tarball</A
>
        (or check it out from CVS) and place
        it in a suitable directory, accessible by the default web server user 
        (probably <SPAN
CLASS="QUOTE"
>"apache"</SPAN
> or <SPAN
CLASS="QUOTE"
>"www"</SPAN
>). 
        Good locations are either directly in the web server's document directories or
        in <TT
CLASS="filename"
>/usr/local</TT
> with a symbolic link to the web server's 
        document directories or an alias in the web server's configuration.
      </P
><DIV
CLASS="caution"
><P
></P
><TABLE
CLASS="caution"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The default Bugzilla distribution is NOT designed to be placed
        in a <TT
CLASS="filename"
>cgi-bin</TT
> directory. This
        includes any directory which is configured using the
        <CODE
CLASS="option"
>ScriptAlias</CODE
> directive of Apache.
        </P
></TD
></TR
></TABLE
></DIV
><P
>Once all the files are in a web accessible directory, make that
      directory writable by your web server's user. This is a temporary step
      until you run the 
      <TT
CLASS="filename"
>checksetup.pl</TT
>
      script, which locks down your installation.</P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-perlmodules"
>2.1.5. Perl Modules</A
></H3
><P
>Bugzilla's installation process is based
      on a script called <TT
CLASS="filename"
>checksetup.pl</TT
>. 
      The first thing it checks is whether you have appropriate 
      versions of all the required
      Perl modules. The aim of this section is to pass this check. 
      When it passes, proceed to <A
HREF="#configuration"
>Section 2.2</A
>.
      </P
><P
>&#13;      At this point, you need to <TT
CLASS="filename"
>su</TT
> to root. You should
      remain as root until the end of the install. To check you have the
      required modules, run:
      </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
><SAMP
CLASS="prompt"
>bash#</SAMP
> ./checksetup.pl --check-modules</PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;        <TT
CLASS="filename"
>checksetup.pl</TT
> will print out a list of the
        required and optional Perl modules, together with the versions
        (if any) installed on your machine.
        The list of required modules is reasonably long; however, you 
        may already have several of them installed.
      </P
><P
>&#13;        The preferred way to install missing Perl modules is to use the package
        manager provided by your operating system (e.g <SPAN
CLASS="QUOTE"
>"rpm"</SPAN
> or
        <SPAN
CLASS="QUOTE"
>"yum"</SPAN
> on Linux distros, or <SPAN
CLASS="QUOTE"
>"ppm"</SPAN
> on Windows
        if using ActivePerl, see <A
HREF="#win32-perl-modules"
>Section 2.5.1.2</A
>).
        If some Perl modules are still missing or are too old, then we recommend
        using the <TT
CLASS="filename"
>install-module.pl</TT
> script (doesn't work
        with ActivePerl on Windows). If for some reason you really need to
        install the Perl modules manually, see
        <A
HREF="#install-perlmodules-manual"
>Appendix C</A
>. For instance, on Unix,
        you invoke <TT
CLASS="filename"
>install-module.pl</TT
> as follows:
      </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
><SAMP
CLASS="prompt"
>bash#</SAMP
> perl install-module.pl &#60;modulename&#62;</PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Many people complain that Perl modules will not install for
        them. Most times, the error messages complain that they are missing a
        file in 
        <SPAN
CLASS="QUOTE"
>"@INC"</SPAN
>.
        Virtually every time, this error is due to permissions being set too
        restrictively for you to compile Perl modules or not having the
        necessary Perl development libraries installed on your system.
        Consult your local UNIX systems administrator for help solving these
        permissions issues; if you 
        <EM
>are</EM
>
        the local UNIX sysadmin, please consult the newsgroup/mailing list
        for further assistance or hire someone to help you out.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you are using a package-based system, and attempting to install the
        Perl modules from CPAN, you may need to install the "development" packages for
        MySQL and GD before attempting to install the related Perl modules. The names of
        these packages will vary depending on the specific distribution you are using,
        but are often called <TT
CLASS="filename"
>&#60;packagename&#62;-devel</TT
>.</P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        Here is a complete list of modules and their minimum versions.
        Some modules have special installation notes, which follow.
      </P
><P
>Required Perl modules:
      <P
></P
><OL
TYPE="1"
><LI
><P
>&#13;            CGI (3.51)
          </P
></LI
><LI
><P
>&#13;            Date::Format (2.21)
          </P
></LI
><LI
><P
>&#13;            DateTime (0.28)
          </P
></LI
><LI
><P
>&#13;            DateTime::TimeZone (0.71)
          </P
></LI
><LI
><P
>&#13;            DBI (1.41)
          </P
></LI
><LI
><P
>&#13;            DBD::mysql (4.00) if using MySQL
          </P
></LI
><LI
><P
>&#13;            DBD::Pg (1.45) if using PostgreSQL
          </P
></LI
><LI
><P
>&#13;            DBD::Oracle (1.19) if using Oracle
          </P
></LI
><LI
><P
>&#13;            Digest::SHA (any)
          </P
></LI
><LI
><P
>&#13;            Email::Send (2.00)
          </P
></LI
><LI
><P
>&#13;            Email::MIME (1.904)
          </P
></LI
><LI
><P
>&#13;            Template (2.22)
          </P
></LI
><LI
><P
>&#13;            URI (any)
          </P
></LI
></OL
>

      Optional Perl modules:
      <P
></P
><OL
TYPE="1"
><LI
><P
>&#13;            GD (1.20) for bug charting
          </P
></LI
><LI
><P
>&#13;            Template::Plugin::GD::Image
            (any) for Graphical Reports
          </P
></LI
><LI
><P
>&#13;            Chart::Lines (2.1) for bug charting
          </P
></LI
><LI
><P
>&#13;            GD::Graph (any) for bug charting
          </P
></LI
><LI
><P
>&#13;            GD::Text (any) for bug charting
          </P
></LI
><LI
><P
>&#13;            XML::Twig (any) for bug import/export
          </P
></LI
><LI
><P
>&#13;            MIME::Parser (5.406) for bug import/export
          </P
></LI
><LI
><P
>&#13;            LWP::UserAgent
            (any) for Automatic Update Notifications
          </P
></LI
><LI
><P
>&#13;            PatchReader (0.9.4) for pretty HTML view of patches
          </P
></LI
><LI
><P
>&#13;            Net::LDAP
            (any) for LDAP Authentication
          </P
></LI
><LI
><P
>&#13;            Authen::SASL
            (any) for SASL Authentication
          </P
></LI
><LI
><P
>&#13;            Authen::Radius
            (any) for RADIUS Authentication
          </P
></LI
><LI
><P
>&#13;            SOAP::Lite (0.712) for the web service interface
          </P
></LI
><LI
><P
>&#13;            JSON::RPC
            (any) for the JSON-RPC interface
          </P
></LI
><LI
><P
>&#13;            Test::Taint
            (any) for the web service interface
          </P
></LI
><LI
><P
>&#13;            HTML::Parser
            (3.40) for More HTML in Product/Group Descriptions
          </P
></LI
><LI
><P
>&#13;            HTML::Scrubber
            (any) for More HTML in Product/Group Descriptions
          </P
></LI
><LI
><P
>&#13;            Email::MIME::Attachment::Stripper
            (any) for Inbound Email
          </P
></LI
><LI
><P
>&#13;            Email::Reply
            (any) for Inbound Email
          </P
></LI
><LI
><P
>&#13;            TheSchwartz
            (any) for Mail Queueing
          </P
></LI
><LI
><P
>&#13;            Daemon::Generic
            (any) for Mail Queueing
          </P
></LI
><LI
><P
>&#13;            mod_perl2
            (1.999022) for mod_perl
          </P
></LI
></OL
>
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-MTA"
>2.1.6. Mail Transfer Agent (MTA)</A
></H3
><P
>&#13;        Bugzilla is dependent on the availability of an e-mail system for its 
        user authentication and for other tasks.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          This is not entirely true.  It is possible to completely disable 
          email sending, or to have Bugzilla store email messages in a 
          file instead of sending them.  However, this is mainly intended 
          for testing, as disabling or diverting email on a production 
          machine would mean that users could miss important events (such 
          as bug changes or the creation of new accounts).
        </P
><P
>&#13;          For more information, see the <SPAN
CLASS="QUOTE"
>"mail_delivery_method"</SPAN
> parameter
          in <A
HREF="#parameters"
>Section 3.1</A
>.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        On Linux, any Sendmail-compatible MTA (Mail Transfer Agent) will 
        suffice.  Sendmail, Postfix, qmail and Exim are examples of common 
        MTAs. Sendmail is the original Unix MTA, but the others are easier to 
        configure, and therefore many people replace Sendmail with Postfix or 
        Exim. They are drop-in replacements, so Bugzilla will not 
        distinguish between them.
      </P
><P
>&#13;        If you are using Sendmail, version 8.7 or higher is required.
        If you are using a Sendmail-compatible MTA, it must be congruent with 
        at least version 8.7 of Sendmail.
      </P
><P
>&#13;        Consult the manual for the specific MTA you choose for detailed 
        installation instructions. Each of these programs will have their own 
        configuration files where you must configure certain parameters to 
        ensure that the mail is delivered properly. They are implemented 
        as services, and you should ensure that the MTA is in the auto-start 
        list of services for the machine.
      </P
><P
>&#13;        If a simple mail sent with the command-line 'mail' program 
        succeeds, then Bugzilla should also be fine.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="using-mod_perl-with-bugzilla"
>2.1.7. Installing Bugzilla on mod_perl</A
></H3
><P
>It is now possible to run the Bugzilla software under <TT
CLASS="literal"
>mod_perl</TT
> on
      Apache. <TT
CLASS="literal"
>mod_perl</TT
> has some additional requirements to that of running
      Bugzilla under <TT
CLASS="literal"
>mod_cgi</TT
> (the standard and previous way).</P
><P
>Bugzilla requires <TT
CLASS="literal"
>mod_perl</TT
> to be installed, which can be
      obtained from <A
HREF="http://perl.apache.org"
TARGET="_top"
>http://perl.apache.org</A
> - Bugzilla requires
      version 1.999022 (AKA 2.0.0-RC5) to be installed.</P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="configuration"
>2.2. Configuration</A
></H2
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        Poorly-configured MySQL and Bugzilla installations have
        given attackers full access to systems in the past. Please take the
        security parts of these guidelines seriously, even for Bugzilla 
        machines hidden away behind your firewall. Be certain to read
        <A
HREF="#security"
>Chapter 4</A
> for some important security tips.
      </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="localconfig"
>2.2.1. localconfig</A
></H3
><P
>&#13;        You should now run <TT
CLASS="filename"
>checksetup.pl</TT
> again, this time
        without the <TT
CLASS="literal"
>--check-modules</TT
> switch.
      </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
><SAMP
CLASS="prompt"
>bash#</SAMP
> ./checksetup.pl</PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;        This time, <TT
CLASS="filename"
>checksetup.pl</TT
> should tell you that all
        the correct modules are installed and will display a message about, and
        write out a  file called, <TT
CLASS="filename"
>localconfig</TT
>. This file
        contains the default settings for a number of Bugzilla parameters.
      </P
><P
>&#13;        Load this file in your editor. The only two values you
        <EM
>need</EM
> to change are $db_driver and $db_pass,
        respectively the type of the database and the password for
        the user you will create for your database. Pick a strong
        password (for simplicity, it should not contain single quote
        characters) and put it here. $db_driver can be either 'mysql',
        'Pg' or 'oracle'.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          In Oracle, <TT
CLASS="literal"
>$db_name</TT
> should actually be 
          the SID name of your database (e.g. "XE" if you are using Oracle XE).
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        You may need to change the value of 
        <EM
>webservergroup</EM
> if your web server does not 
        run in the "apache" group.  On Debian, for example, Apache runs in 
        the "www-data" group.  If you are going to run Bugzilla on a 
        machine where you do not have root access (such as on a shared web 
        hosting account), you will need to leave
        <EM
>webservergroup</EM
> empty, ignoring the warnings 
        that <TT
CLASS="filename"
>checksetup.pl</TT
> will subsequently display 
        every time it is run.
      </P
><DIV
CLASS="caution"
><P
></P
><TABLE
CLASS="caution"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          If you are using suexec, you should use your own primary group
          for <EM
>webservergroup</EM
> rather than leaving it
          empty, and see the additional directions in the suexec section
          <A
HREF="#suexec"
>Section 2.6.6.1</A
>.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        The other options in the <TT
CLASS="filename"
>localconfig</TT
> file
        are documented by their accompanying comments. If you have a slightly
        non-standard database setup, you may wish to change one or more of
        the other "$db_*" parameters.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="database-engine"
>2.2.2. Database Server</A
></H3
><P
>&#13;        This section deals with configuring your database server for use
        with Bugzilla. Currently, MySQL (<A
HREF="#mysql"
>Section 2.2.2.2</A
>),
        PostgreSQL (<A
HREF="#postgresql"
>Section 2.2.2.3</A
>) and Oracle (<A
HREF="#oracle"
>Section 2.2.2.4</A
>)
        are available.
      </P
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="database-schema"
>2.2.2.1. Bugzilla Database Schema</A
></H4
><P
>&#13;          The Bugzilla database schema is available at
          <A
HREF="http://www.ravenbrook.com/project/p4dti/tool/cgi/bugzilla-schema/"
TARGET="_top"
>Ravenbrook</A
>.
          This very valuable tool can generate a written description of
          the Bugzilla database schema for any version of Bugzilla. It
          can also generate a diff between two versions to help someone
          see what has changed.
        </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="mysql"
>2.2.2.2. MySQL</A
></H4
><DIV
CLASS="caution"
><P
></P
><TABLE
CLASS="caution"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            MySQL's default configuration is insecure.
            We highly recommend to run <TT
CLASS="filename"
>mysql_secure_installation</TT
>
            on Linux or the MySQL installer on Windows, and follow the instructions.
            Important points to note are:
            <P
></P
><OL
TYPE="1"
><LI
><P
>Be sure that the root account has a secure password set.</P
></LI
><LI
><P
>Do not create an anonymous account, and if it exists, say "yes"
                to remove it.</P
></LI
><LI
><P
>If your web server and MySQL server are on the same machine,
                you should disable the network access.</P
></LI
></OL
>
          </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="mysql-max-allowed-packet"
>2.2.2.2.1. Allow large attachments and many comments</A
></H5
><P
>By default, MySQL will only allow you to insert things
          into the database that are smaller than 1MB. Attachments
          may be larger than this. Also, Bugzilla combines all comments
          on a single bug into one field for full-text searching, and the
          combination of all comments on a single bug could in some cases
          be larger than 1MB.</P
><P
>To change MySQL's default, you need to edit your MySQL
          configuration file, which is usually <TT
CLASS="filename"
>/etc/my.cnf</TT
>
          on Linux. We recommend that you allow at least 4MB packets by
          adding the "max_allowed_packet" parameter to your MySQL 
          configuration in the "[mysqld]" section, like this:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>[mysqld]
# Allow packets up to 4MB
max_allowed_packet=4M
          </PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="AEN438"
>2.2.2.2.2. Allow small words in full-text indexes</A
></H5
><P
>By default, words must be at least four characters in length
          in order to be indexed by MySQL's full-text indexes. This causes
          a lot of Bugzilla specific words to be missed, including "cc",
          "ftp" and "uri".</P
><P
>MySQL can be configured to index those words by setting the
          ft_min_word_len param to the minimum size of the words to index.
          This can be done by modifying the <TT
CLASS="filename"
>/etc/my.cnf</TT
>
          according to the example below:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>  [mysqld]
  # Allow small words in full-text indexes
  ft_min_word_len=2</PRE
></FONT
></TD
></TR
></TABLE
><P
>Rebuilding the indexes can be done based on documentation found at
          <A
HREF="http://www.mysql.com/doc/en/Fulltext_Fine-tuning.html"
TARGET="_top"
>http://www.mysql.com/doc/en/Fulltext_Fine-tuning.html</A
>.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="install-setupdatabase-adduser"
>2.2.2.2.3. Add a user to MySQL</A
></H5
><P
>&#13;            You need to add a new MySQL user for Bugzilla to use.
            (It's not safe to have Bugzilla use the MySQL root account.)
            The following instructions assume the defaults in
            <TT
CLASS="filename"
>localconfig</TT
>; if you changed those,
            you need to modify the SQL command appropriately. You will
            need the <TT
CLASS="replaceable"
><I
>$db_pass</I
></TT
> password you
            set in <TT
CLASS="filename"
>localconfig</TT
> in 
            <A
HREF="#localconfig"
>Section 2.2.1</A
>.
          </P
><P
>&#13;            We use an SQL <B
CLASS="command"
>GRANT</B
> command to create
            a <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> user. This also restricts the 
            <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
>user to operations within a database
            called <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
>, and only allows the account
            to connect from <SPAN
CLASS="QUOTE"
>"localhost"</SPAN
>. Modify it to
            reflect your setup if you will be connecting from another
            machine or as a different user.
          </P
><P
>&#13;            Run the <TT
CLASS="filename"
>mysql</TT
> command-line client and enter:
          </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>&#13;    <SAMP
CLASS="prompt"
>mysql&#62;</SAMP
> GRANT SELECT, INSERT,
           UPDATE, DELETE, INDEX, ALTER, CREATE, LOCK TABLES,
           CREATE TEMPORARY TABLES, DROP, REFERENCES ON bugs.*
           TO bugs@localhost IDENTIFIED BY '<TT
CLASS="replaceable"
><I
>$db_pass</I
></TT
>';
    <SAMP
CLASS="prompt"
>mysql&#62;</SAMP
> FLUSH PRIVILEGES;
          </PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="AEN465"
>2.2.2.2.4. Permit attachments table to grow beyond 4GB</A
></H5
><P
>&#13;            By default, MySQL will limit the size of a table to 4GB.
            This limit is present even if the underlying filesystem
            has no such limit.  To set a higher limit, follow these
            instructions.
          </P
><P
>&#13;            After you have completed the rest of the installation (or at least the
            database setup parts), you should run the <TT
CLASS="filename"
>MySQL</TT
>
            command-line client and enter the following, replacing <TT
CLASS="literal"
>$bugs_db</TT
>
            with your Bugzilla database name (<EM
>bugs</EM
> by default):
          </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>&#13;    <SAMP
CLASS="prompt"
>mysql&#62;</SAMP
> use <TT
CLASS="replaceable"
><I
>$bugs_db</I
></TT
>
    <SAMP
CLASS="prompt"
>mysql&#62;</SAMP
> ALTER TABLE attachments
           AVG_ROW_LENGTH=1000000, MAX_ROWS=20000;
          </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;            The above command will change the limit to 20GB. Mysql will have 
            to make a temporary copy of your entire table to do this. Ideally, 
            you should do this when your attachments table is still small. 
          </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;              This does not affect Big Files, attachments that are stored directly
              on disk instead of in the database.
            </P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="postgresql"
>2.2.2.3. PostgreSQL</A
></H4
><DIV
CLASS="section"
><H5
CLASS="section"
><A
NAME="AEN481"
>2.2.2.3.1. Add a User to PostgreSQL</A
></H5
><P
>You need to add a new user to PostgreSQL for the Bugzilla
          application to use when accessing the database. The following instructions
          assume the defaults in <TT
CLASS="filename"
>localconfig</TT
>; if you
          changed those, you need to modify the commands appropriately. You will
          need the <TT
CLASS="replaceable"
><I
>$db_pass</I
></TT
> password you
          set in <TT
CLASS="filename"
>localconfig</TT
> in 
          <A
HREF="#localconfig"
>Section 2.2.1</A
>.</P
><P
>On most systems, to create the user in PostgreSQL, you will need to
          login as the root user, and then</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
> <SAMP
CLASS="prompt"
>bash#</SAMP
> su - postgres</PRE
></FONT
></TD
></TR
></TABLE
><P
>As the postgres user, you then need to create a new user: </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
> <SAMP
CLASS="prompt"
>bash$</SAMP
> createuser -U postgres -dRSP bugs</PRE
></FONT
></TD
></TR
></TABLE
><P
>When asked for a password, provide the password which will be set as
          <TT
CLASS="replaceable"
><I
>$db_pass</I
></TT
> in <TT
CLASS="filename"
>localconfig</TT
>.
          The created user will not be a superuser (-S) and will not be able to create
          new users (-R). He will only have the ability to create databases (-d).</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If your are running PostgreSQL 8.0, you must replace -dRSP by -dAP.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="AEN499"
>2.2.2.3.2. Configure PostgreSQL</A
></H5
><P
>Now, you will need to edit <TT
CLASS="filename"
>pg_hba.conf</TT
> which is
          usually located in <TT
CLASS="filename"
>/var/lib/pgsql/data/</TT
>. In this file,
          you will need to add a new line to it as follows:</P
><P
>&#13;            <SAMP
CLASS="computeroutput"
>host   all    bugs   127.0.0.1    255.255.255.255  md5</SAMP
>
          </P
><P
>This means that for TCP/IP (host) connections, allow connections from
          '127.0.0.1' to 'all' databases on this server from the 'bugs' user, and use
          password authentication (md5) for that user.</P
><P
>Now, you will need to restart PostgreSQL, but you will need to fully
          stop and start the server rather than just restarting due to the possibility
          of a change to <TT
CLASS="filename"
>postgresql.conf</TT
>. After the server has
          restarted, you will need to edit <TT
CLASS="filename"
>localconfig</TT
>, finding
          the <TT
CLASS="literal"
>$db_driver</TT
> variable and setting it to
          <TT
CLASS="literal"
>Pg</TT
> and changing the password in <TT
CLASS="literal"
>$db_pass</TT
>
          to the one you picked previously, while setting up the account.</P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="oracle"
>2.2.2.4. Oracle</A
></H4
><DIV
CLASS="section"
><H5
CLASS="section"
><A
NAME="AEN515"
>2.2.2.4.1. Create a New Tablespace</A
></H5
><P
>&#13;            You can use the existing tablespace or create a new one for Bugzilla.
            To create a new tablespace, run the following command:
          </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;    CREATE TABLESPACE bugs
    DATAFILE '<TT
CLASS="replaceable"
><I
>$path_to_datafile</I
></TT
>' SIZE 500M
    AUTOEXTEND ON NEXT 30M MAXSIZE UNLIMITED
          </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;            Here, the name of the tablespace is 'bugs', but you can
            choose another name. <TT
CLASS="replaceable"
><I
>$path_to_datafile</I
></TT
> is
            the path to the file containing your database, for instance
            <TT
CLASS="filename"
>/u01/oradata/bugzilla.dbf</TT
>.
            The initial size of the database file is set in this example to 500 Mb,
            with an increment of 30 Mb everytime we reach the size limit of the file.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="AEN523"
>2.2.2.4.2. Add a User to Oracle</A
></H5
><P
>&#13;            The user name and password must match what you set in
            <TT
CLASS="filename"
>localconfig</TT
> (<TT
CLASS="literal"
>$db_user</TT
>
            and <TT
CLASS="literal"
>$db_pass</TT
>, respectively). Here, we assume that
            the user name is 'bugs' and the tablespace name is the same
            as above. 
          </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;    CREATE USER bugs
    IDENTIFIED BY "<TT
CLASS="replaceable"
><I
>$db_pass</I
></TT
>"
    DEFAULT TABLESPACE bugs
    TEMPORARY TABLESPACE TEMP
    PROFILE DEFAULT;
    -- GRANT/REVOKE ROLE PRIVILEGES
    GRANT CONNECT TO bugs;
    GRANT RESOURCE TO bugs;
    -- GRANT/REVOKE SYSTEM PRIVILEGES
    GRANT UNLIMITED TABLESPACE TO bugs;
    GRANT EXECUTE ON CTXSYS.CTX_DDL TO bugs;
          </PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="AEN531"
>2.2.2.4.3. Configure the Web Server</A
></H5
><P
>&#13;            If you use Apache, append these lines to <TT
CLASS="filename"
>httpd.conf</TT
>
            to set ORACLE_HOME and LD_LIBRARY_PATH. For instance:
          </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;    SetEnv ORACLE_HOME /u01/app/oracle/product/10.2.0/
    SetEnv LD_LIBRARY_PATH /u01/app/oracle/product/10.2.0/lib/
          </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;            When this is done, restart your web server.
          </P
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="AEN537"
>2.2.3. checksetup.pl</A
></H3
><P
>&#13;        Next, rerun <TT
CLASS="filename"
>checksetup.pl</TT
>. It reconfirms
        that all the modules are present, and notices the altered 
        localconfig file, which it assumes you have edited to your
        satisfaction. It compiles the UI templates,
        connects to the database using the 'bugs'
        user you created and the password you defined, and creates the 
        'bugs' database and the tables therein. 
      </P
><P
>&#13;        After that, it asks for details of an administrator account. Bugzilla
        can have multiple administrators - you can create more later - but
        it needs one to start off with.
        Enter the email address of an administrator, his or her full name, 
        and a suitable Bugzilla password.
      </P
><P
>&#13;        <TT
CLASS="filename"
>checksetup.pl</TT
> will then finish. You may rerun
        <TT
CLASS="filename"
>checksetup.pl</TT
> at any time if you wish.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="http"
>2.2.4. Web server</A
></H3
><P
>&#13;        Configure your web server according to the instructions in the
        appropriate section. (If it makes a difference in your choice,
        the Bugzilla Team recommends Apache.) To check whether your web server
	is correctly configured, try to access <TT
CLASS="filename"
>testagent.cgi</TT
>
	from your web server. If "OK" is displayed, then your configuration
	is successful. Regardless of which web server
        you are using, however, ensure that sensitive information is
        not remotely available by properly applying the access controls in
        <A
HREF="#security-webserver-access"
>Section 4.2.1</A
>. You can run
        <TT
CLASS="filename"
>testserver.pl</TT
> to check if your web server serves
        Bugzilla files as expected.
      </P
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="http-apache"
>2.2.4.1. Bugzilla using Apache</A
></H4
><P
>You have two options for running Bugzilla under Apache - 
          <A
HREF="#http-apache-mod_cgi"
>mod_cgi</A
> (the default) and
          <A
HREF="#http-apache-mod_perl"
>mod_perl</A
> (new in Bugzilla
          2.23)
        </P
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="http-apache-mod_cgi"
>2.2.4.1.1. Apache <SPAN
CLASS="productname"
>httpd</SPAN
> with mod_cgi</A
></H5
><P
>&#13;            To configure your Apache web server to work with Bugzilla while using
            mod_cgi, do the following:
            </P
><DIV
CLASS="procedure"
><OL
TYPE="1"
><LI
CLASS="step"
><P
>&#13;                Load <TT
CLASS="filename"
>httpd.conf</TT
> in your editor.
                In Fedora and Red Hat Linux, this file is found in
                <TT
CLASS="filename"
>/etc/httpd/conf</TT
>.
                </P
></LI
><LI
CLASS="step"
><P
>&#13;                Apache uses <SAMP
CLASS="computeroutput"
>&#60;Directory&#62;</SAMP
>
                directives to permit fine-grained permission setting. Add the
                following lines to a directive that applies to the location
                of your Bugzilla installation. (If such a section does not
                exist, you'll want to add one.) In this example, Bugzilla has
                been installed at 
                <TT
CLASS="filename"
>/var/www/html/bugzilla</TT
>.
                </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;    &#60;Directory /var/www/html/bugzilla&#62;
    AddHandler cgi-script .cgi
    Options +Indexes +ExecCGI
    DirectoryIndex index.cgi
    AllowOverride Limit FileInfo Indexes
    &#60;/Directory&#62;
                </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;                These instructions: allow apache to run .cgi files found
                within the bugzilla directory; instructs the server to look
                for a file called <TT
CLASS="filename"
>index.cgi</TT
> if someone
                only types the directory name into the browser; and allows
                Bugzilla's <TT
CLASS="filename"
>.htaccess</TT
> files to override
                global permissions.
                </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;                    It is possible to make these changes globally, or to the
                    directive controlling Bugzilla's parent directory (e.g.
                    <SAMP
CLASS="computeroutput"
>&#60;Directory /var/www/html/&#62;</SAMP
>).
                    Such changes would also apply to the Bugzilla directory...
                    but they would also apply to many other places where they
                    may or may not be appropriate. In most cases, including
                    this one, it is better to be as restrictive as possible
                    when granting extra access.
                </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;                    On Windows, you may have to also add the
                    <SAMP
CLASS="computeroutput"
>ScriptInterpreterSource Registry-Strict</SAMP
>
                    line, see <A
HREF="#win32-http"
>Windows specific notes</A
>.
                </P
></TD
></TR
></TABLE
></DIV
></LI
><LI
CLASS="step"
><P
>&#13;                <TT
CLASS="filename"
>checksetup.pl</TT
> can set tighter permissions
                on Bugzilla's files and directories if it knows what group the
                web server runs as. Find the <SAMP
CLASS="computeroutput"
>Group</SAMP
>
                line in <TT
CLASS="filename"
>httpd.conf</TT
>, place the value found
                there in the <TT
CLASS="replaceable"
><I
>$webservergroup</I
></TT
> variable
                in <TT
CLASS="filename"
>localconfig</TT
>, then rerun
                <TT
CLASS="filename"
>checksetup.pl</TT
>.
                </P
></LI
><LI
CLASS="step"
><P
>&#13;                Optional: If Bugzilla does not actually reside in the webspace
                directory, but instead has been symbolically linked there, you
                will need to add the following to the
                <SAMP
CLASS="computeroutput"
>Options</SAMP
> line of the Bugzilla 
                <SAMP
CLASS="computeroutput"
>&#60;Directory&#62;</SAMP
> directive
                (the same one as in the step above):
                </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;    +FollowSymLinks
                </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;                Without this directive, Apache will not follow symbolic links
                to places outside its own directory structure, and you will be
                unable to run Bugzilla.
                </P
></LI
></OL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="http-apache-mod_perl"
>2.2.4.1.2. Apache <SPAN
CLASS="productname"
>httpd</SPAN
> with mod_perl</A
></H5
><P
>Some configuration is required to make Bugzilla work with Apache
            and mod_perl</P
><DIV
CLASS="procedure"
><OL
TYPE="1"
><LI
CLASS="step"
><P
>&#13;                Load <TT
CLASS="filename"
>httpd.conf</TT
> in your editor.
                In Fedora and Red Hat Linux, this file is found in
                <TT
CLASS="filename"
>/etc/httpd/conf</TT
>.
                </P
></LI
><LI
CLASS="step"
><P
>Add the following information to your httpd.conf file, substituting
                where appropriate with your own local paths.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>This should be used instead of the &#60;Directory&#62; block
                shown above. This should also be above any other <TT
CLASS="literal"
>mod_perl</TT
>
                directives within the <TT
CLASS="filename"
>httpd.conf</TT
> and must be specified
                in the order as below.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>You should also ensure that you have disabled <TT
CLASS="literal"
>KeepAlive</TT
>
                support in your Apache install when utilizing Bugzilla under mod_perl</P
></TD
></TR
></TABLE
></DIV
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;    PerlSwitches -w -T
    PerlConfigRequire /var/www/html/bugzilla/mod_perl.pl
                </PRE
></FONT
></TD
></TR
></TABLE
></LI
><LI
CLASS="step"
><P
>&#13;					<TT
CLASS="filename"
>checksetup.pl</TT
> can set tighter permissions
					on Bugzilla's files and directories if it knows what group the
					web server runs as. Find the <SAMP
CLASS="computeroutput"
>Group</SAMP
>
					line in <TT
CLASS="filename"
>httpd.conf</TT
>, place the value found
					there in the <TT
CLASS="replaceable"
><I
>$webservergroup</I
></TT
> variable
					in <TT
CLASS="filename"
>localconfig</TT
>, then rerun
					<TT
CLASS="filename"
>checksetup.pl</TT
>.
				</P
></LI
></OL
></DIV
><P
>On restarting Apache, Bugzilla should now be running within the
            mod_perl environment. Please ensure you have run checksetup.pl to set
		    permissions before you restart Apache.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Please bear the following points in mind when looking at using 
                Bugzilla under mod_perl: 
            <P
></P
><UL
><LI
><P
>&#13;                    mod_perl support in Bugzilla can take up a HUGE amount of RAM. You could be
                    looking at 30MB per httpd child, easily. Basically, you just need a lot of RAM.
                    The more RAM you can get, the better. mod_perl is basically trading RAM for
                    speed. At least 2GB total system RAM is recommended for running Bugzilla under
                    mod_perl.
                </P
></LI
><LI
><P
>&#13;                    Under mod_perl, you have to restart Apache if you make any manual change to
                    any Bugzilla file. You can't just reload--you have to actually 
					<EM
>restart</EM
> the server (as in make sure it stops and starts 
					again). You <EM
>can</EM
> change localconfig and the params file 
					manually, if you want, because those are re-read every time you load a page.
                </P
></LI
><LI
><P
>&#13;                    You must run in Apache's Prefork MPM (this is the default). The Worker MPM
                    may not work--we haven't tested Bugzilla's mod_perl support under threads.
					(And, in fact, we're fairly sure it <EM
>won't</EM
> work.)
                </P
></LI
><LI
><P
>&#13;                    Bugzilla generally expects to be the only mod_perl application running on
                    your entire server. It may or may not work if there are other applications also
                    running under mod_perl. It does try its best to play nice with other mod_perl
                    applications, but it still may have conflicts.
                </P
></LI
><LI
><P
>&#13;                    It is recommended that you have one Bugzilla instance running under mod_perl
                    on your server. Bugzilla has not been tested with more than one instance running.
                </P
></LI
></UL
>
            </P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="http-iis"
>2.2.4.2. Microsoft <SPAN
CLASS="productname"
>Internet Information Services</SPAN
></A
></H4
><P
>&#13;          If you are running Bugzilla on Windows and choose to use
          Microsoft's <SPAN
CLASS="productname"
>Internet Information Services</SPAN
>
          or <SPAN
CLASS="productname"
>Personal Web Server</SPAN
> you will need
          to perform a number of other configuration steps as explained below.
          You may also want to refer to the following Microsoft Knowledge
          Base articles: 
          <A
HREF="http://support.microsoft.com/default.aspx?scid=kb;en-us;245225"
TARGET="_top"
>245225</A
> 
          <SPAN
CLASS="QUOTE"
>"HOW TO: Configure and Test a PERL Script with IIS 4.0,
          5.0, and 5.1"</SPAN
> (for <SPAN
CLASS="productname"
>Internet Information
          Services</SPAN
>) and 
          <A
HREF="http://support.microsoft.com/default.aspx?scid=kb;en-us;231998"
TARGET="_top"
>231998</A
>          
          <SPAN
CLASS="QUOTE"
>"HOW TO: FP2000: How to Use Perl with Microsoft Personal Web
          Server on Windows 95/98"</SPAN
> (for <SPAN
CLASS="productname"
>Personal Web
          Server</SPAN
>).
        </P
><P
>&#13;          You will need to create a virtual directory for the Bugzilla
          install.  Put the Bugzilla files in a directory that is named
          something <EM
>other</EM
> than what you want your
          end-users accessing.  That is, if you want your users to access
          your Bugzilla installation through 
          <SPAN
CLASS="QUOTE"
>"http://&#60;yourdomainname&#62;/Bugzilla"</SPAN
>, then do
          <EM
>not</EM
> put your Bugzilla files in a directory
          named <SPAN
CLASS="QUOTE"
>"Bugzilla"</SPAN
>.  Instead, place them in a different
          location, and then use the IIS Administration tool to create a
          Virtual Directory named "Bugzilla" that acts as an alias for the
          actual location of the files.  When creating that virtual directory,
          make sure you add the <SPAN
CLASS="QUOTE"
>"Execute (such as ISAPI applications or
          CGI)"</SPAN
> access permission.
        </P
><P
>&#13;          You will also need to tell IIS how to handle Bugzilla's
          .cgi files. Using the IIS Administration tool again, open up
          the properties for the new virtual directory and select the
          Configuration option to access the Script Mappings. Create an
          entry mapping .cgi to:
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;&#60;full path to perl.exe &#62;\perl.exe -x&#60;full path to Bugzilla&#62; -wT "%s" %s
        </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;          For example:
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;c:\perl\bin\perl.exe -xc:\bugzilla -wT "%s" %s
        </PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            The ActiveState install may have already created an entry for
            .pl files that is limited to <SPAN
CLASS="QUOTE"
>"GET,HEAD,POST"</SPAN
>. If
            so, this mapping should be <EM
>removed</EM
> as
            Bugzilla's .pl files are not designed to be run via a web server.
          </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;          IIS will also need to know that the index.cgi should be treated
          as a default document.  On the Documents tab page of the virtual
          directory properties, you need to add index.cgi as a default
          document type.  If you  wish, you may remove the other default
          document types for this particular virtual directory, since Bugzilla 
          doesn't use any of them.
        </P
><P
>&#13;          Also, and this can't be stressed enough, make sure that files
          such as <TT
CLASS="filename"
>localconfig</TT
> and your
          <TT
CLASS="filename"
>data</TT
> directory are
          secured as described in <A
HREF="#security-webserver-access"
>Section 4.2.1</A
>.
        </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-config-bugzilla"
>2.2.5. Bugzilla</A
></H3
><P
>&#13;        Your Bugzilla should now be working. Access 
        <TT
CLASS="filename"
>http://&#60;your-bugzilla-server&#62;/</TT
> - 
        you should see the Bugzilla
        front page. If not, consult the Troubleshooting section,
        <A
HREF="#troubleshooting"
>Appendix A</A
>.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          The URL above may be incorrect if you installed Bugzilla into a 
          subdirectory or used a symbolic link from your web site root to 
          the Bugzilla directory.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        Log in with the administrator account you defined in the last 
        <TT
CLASS="filename"
>checksetup.pl</TT
> run. You should go through 
        the Parameters page and see if there are any you wish to change.
        They key parameters are documented in <A
HREF="#parameters"
>Section 3.1</A
>;
        you should certainly alter 
        <B
CLASS="command"
>maintainer</B
> and <B
CLASS="command"
>urlbase</B
>; 
        you may also want to alter 
        <B
CLASS="command"
>cookiepath</B
> or <B
CLASS="command"
>requirelogin</B
>.
      </P
><P
>&#13;        Bugzilla has several optional features which require extra 
        configuration. You can read about those in
        <A
HREF="#extraconfig"
>Section 2.3</A
>.
      </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="extraconfig"
>2.3. Optional Additional Configuration</A
></H2
><P
>&#13;      Bugzilla has a number of optional features. This section describes how
      to configure or enable them.
    </P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="AEN688"
>2.3.1. Bug Graphs</A
></H3
><P
>If you have installed the necessary Perl modules you
      can start collecting statistics for the nifty Bugzilla 
      graphs.</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
><SAMP
CLASS="prompt"
>bash#</SAMP
> <B
CLASS="command"
>crontab -e</B
></PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;        This should bring up the crontab file in your editor. 
        Add a cron entry like this to run 
        <TT
CLASS="filename"
>collectstats.pl</TT
> 
        daily at 5 after midnight:
      </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>5 0 * * * cd &#60;your-bugzilla-directory&#62; ; ./collectstats.pl</PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;        After two days have passed you'll be able to view bug graphs from
        the Reports page.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          Windows does not have 'cron', but it does have the Task
          Scheduler, which performs the same duties. There are also
          third-party tools that can be used to implement cron, such as
          <A
HREF="http://www.nncron.ru/"
TARGET="_top"
>nncron</A
>.
        </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="installation-whining-cron"
>2.3.2. The Whining Cron</A
></H3
><P
>What good are
      bugs if they're not annoying? To help make them more so you
      can set up Bugzilla's automatic whining system to complain at engineers
      which leave their bugs in the CONFIRMED state without triaging them.
      </P
><P
>&#13;        This can be done by adding the following command as a daily
        crontab entry, in the same manner as explained above for bug
        graphs. This example runs it at 12.55am. 
      </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>55 0 * * * cd &#60;your-bugzilla-directory&#62; ; ./whineatnews.pl</PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          Windows does not have 'cron', but it does have the Task
          Scheduler, which performs the same duties. There are also
          third-party tools that can be used to implement cron, such as
          <A
HREF="http://www.nncron.ru/"
TARGET="_top"
>nncron</A
>.
        </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="installation-whining"
>2.3.3. Whining</A
></H3
><P
>&#13;        As of Bugzilla 2.20, users can configure Bugzilla to regularly annoy 
        them at regular intervals, by having Bugzilla execute saved searches
        at certain times and emailing the results to the user.  This is known
        as "Whining".  The process of configuring Whining is described 
        in <A
HREF="#whining"
>Section 5.13</A
>, but for it to work a Perl script must be
        executed at regular intervals.
      </P
><P
>&#13;        This can be done by adding the following command as a daily
        crontab entry, in the same manner as explained above for bug
        graphs. This example runs it every 15 minutes. 
      </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>*/15 * * * * cd &#60;your-bugzilla-directory&#62; ; ./whine.pl</PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          Whines can be executed as often as every 15 minutes, so if you specify
          longer intervals between executions of whine.pl, some users may not 
          be whined at as often as they would expect.  Depending on the person,
          this can either be a very Good Thing or a very Bad Thing.
        </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          Windows does not have 'cron', but it does have the Task
          Scheduler, which performs the same duties. There are also
          third-party tools that can be used to implement cron, such as
          <A
HREF="http://www.nncron.ru/"
TARGET="_top"
>nncron</A
>.
        </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="apache-addtype"
>2.3.4. Serving Alternate Formats with the right MIME type</A
></H3
><P
>&#13;        Some Bugzilla pages have alternate formats, other than just plain
        <ACRONYM
CLASS="acronym"
>HTML</ACRONYM
>. In particular, a few Bugzilla pages can 
        output their contents as either <ACRONYM
CLASS="acronym"
>XUL</ACRONYM
> (a special 
        Mozilla format, that looks like a program <ACRONYM
CLASS="acronym"
>GUI</ACRONYM
>) 
        or <ACRONYM
CLASS="acronym"
>RDF</ACRONYM
> (a type of structured <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> 
        that can be read by various programs).
      </P
><P
>&#13;        In order for your users to see these pages correctly, Apache must 
        send them with the right <ACRONYM
CLASS="acronym"
>MIME</ACRONYM
> type. To do this, 
        add the following lines to your Apache configuration, either in the 
        <SAMP
CLASS="computeroutput"
>&#60;VirtualHost&#62;</SAMP
> section for your
        Bugzilla, or in the <SAMP
CLASS="computeroutput"
>&#60;Directory&#62;</SAMP
>
        section for your Bugzilla:
      </P
><P
>&#13;        <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>AddType application/vnd.mozilla.xul+xml .xul
AddType application/rdf+xml .rdf</PRE
></FONT
></TD
></TR
></TABLE
>
      </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="multiple-bz-dbs"
>2.4. Multiple Bugzilla databases with a single installation</A
></H2
><P
>The previous instructions referred to a standard installation, with
      one unique Bugzilla database. However, you may want to host several
      distinct installations, without having several copies of the code. This is
      possible by using the PROJECT environment variable. When accessed,
      Bugzilla checks for the existence of this variable, and if present, uses
      its value to check for an alternative configuration file named
      <TT
CLASS="filename"
>localconfig.&#60;PROJECT&#62;</TT
> in the same location as
      the default one (<TT
CLASS="filename"
>localconfig</TT
>). It also checks for
      customized templates in a directory named
      <TT
CLASS="filename"
>&#60;PROJECT&#62;</TT
> in the same location as the
      default one (<TT
CLASS="filename"
>template/&#60;langcode&#62;</TT
>). By default
      this is <TT
CLASS="filename"
>template/en/default</TT
> so PROJECT's templates
      would be located at <TT
CLASS="filename"
>template/en/PROJECT</TT
>.</P
><P
>To set up an alternate installation, just export PROJECT=foo before
      running <B
CLASS="command"
>checksetup.pl</B
> for the first time. It will
      result in a file called <TT
CLASS="filename"
>localconfig.foo</TT
> instead of
      <TT
CLASS="filename"
>localconfig</TT
>. Edit this file as described above, with
      reference to a new database, and re-run <B
CLASS="command"
>checksetup.pl</B
>
      to populate it. That's all.</P
><P
>Now you have to configure the web server to pass this environment
      variable when accessed via an alternate URL, such as virtual host for
      instance. The following is an example of how you could do it in Apache,
      other Webservers may differ.
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;&#60;VirtualHost 212.85.153.228:80&#62;
    ServerName foo.bar.baz
    SetEnv PROJECT foo
    Alias /bugzilla /var/www/bugzilla
&#60;/VirtualHost&#62;
</PRE
></FONT
></TD
></TR
></TABLE
>
    </P
><P
>Don't forget to also export this variable before accessing Bugzilla
       by other means, such as cron tasks for instance.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="os-specific"
>2.5. OS-Specific Installation Notes</A
></H2
><P
>Many aspects of the Bugzilla installation can be affected by the
    operating system you choose to install it on. Sometimes it can be made
    easier and others more difficult. This section will attempt to help you
    understand both the difficulties of running on specific operating systems
    and the utilities available to make it easier.
    </P
><P
>If you have anything to add or notes for an operating system not
    covered, please file a bug in <A
HREF="https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&#38;component=Documentation"
TARGET="_top"
>Bugzilla Documentation</A
>. 
    </P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="os-win32"
>2.5.1. Microsoft Windows</A
></H3
><P
>&#13;        Making Bugzilla work on Windows is more difficult than making it
        work on Unix.  For that reason, we still recommend doing so on a Unix 
        based system such as GNU/Linux.  That said, if you do want to get
        Bugzilla running on Windows, you will need to make the following
        adjustments. A detailed step-by-step
        <A
HREF="https://wiki.mozilla.org/Bugzilla:Win32Install"
TARGET="_top"
>&#13;        installation guide for Windows</A
> is also available
        if you need more help with your installation.
      </P
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="win32-perl"
>2.5.1.1. Win32 Perl</A
></H4
><P
>&#13;          Perl for Windows can be obtained from 
          <A
HREF="http://www.activestate.com/"
TARGET="_top"
>ActiveState</A
>.
           You should be able to find a compiled binary at <A
HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/"
TARGET="_top"
>http://aspn.activestate.com/ASPN/Downloads/ActivePerl/</A
>.
           The following instructions assume that you are using version
           5.8.1 of ActiveState.
          </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;             These instructions are for 32-bit versions of Windows. If you are
             using a 64-bit version of Windows, you will need to install 32-bit
             Perl in order to install the 32-bit modules as described below.
            </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="win32-perl-modules"
>2.5.1.2. Perl Modules on Win32</A
></H4
><P
>&#13;          Bugzilla on Windows requires the same perl modules found in
          <A
HREF="#install-perlmodules"
>Section 2.1.5</A
>. The main difference is that
          windows uses <A
HREF="#gloss-ppm"
><I
CLASS="glossterm"
>PPM</I
></A
> instead
          of CPAN. ActiveState provides a GUI to manage Perl modules. We highly
          recommend that you use it. If you prefer to use ppm from the
          command-line, type:
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;C:\perl&#62; <B
CLASS="command"
>ppm install &#60;module name&#62;</B
>
        </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;          The best source for the Windows PPM modules needed for Bugzilla
          is probably the theory58S website, which you can add to your list
          of repositories as follows (for Perl 5.8.x):
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;<B
CLASS="command"
>ppm repo add theory58S http://theoryx5.uwinnipeg.ca/ppms/</B
>
        </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;          If you are using Perl 5.10.x, you cannot use the same PPM modules as Perl
          5.8.x as they are incompatible. In this case, you should add the following
          repository:
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;<B
CLASS="command"
>ppm repo add theory58S http://cpan.uwinnipeg.ca/PPMPackages/10xx/</B
>
        </PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            In versions prior to 5.8.8 build 819 of PPM the command is 
            <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;<B
CLASS="command"
>ppm repository add theory58S http://theoryx5.uwinnipeg.ca/ppms/</B
>
            </PRE
></FONT
></TD
></TR
></TABLE
>
          </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            The PPM repository stores modules in 'packages' that may have
            a slightly different name than the module.  If retrieving these
            modules from there, you will need to pay attention to the information
            provided when you run <B
CLASS="command"
>checksetup.pl</B
> as it will
            tell you what package you'll need to install.
          </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            If you are behind a corporate firewall, you will need to let the
            ActiveState PPM utility know how to get through it to access
            the repositories by setting the HTTP_proxy system environmental
            variable. For more information on setting that variable, see
            the ActiveState documentation.
          </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="win32-http"
>2.5.1.3. Serving the web pages</A
></H4
><P
>&#13;          As is the case on Unix based systems, any web server should
          be able to handle Bugzilla; however, the Bugzilla Team still
          recommends Apache whenever asked. No matter what web server
          you choose, be sure to pay attention to the security notes
          in <A
HREF="#security-webserver-access"
>Section 4.2.1</A
>. More
          information on configuring specific web servers can be found
          in <A
HREF="#http"
>Section 2.2.4</A
>.
        </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            The web server looks at <TT
CLASS="filename"
>/usr/bin/perl</TT
> to
            call Perl. If you are using Apache on windows, you can set the
            <A
HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
TARGET="_top"
>ScriptInterpreterSource</A
>
            directive in your Apache config file to make it look at the
            right place: insert the line
            <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>ScriptInterpreterSource Registry-Strict</PRE
></FONT
></TD
></TR
></TABLE
>
            into your <TT
CLASS="filename"
>httpd.conf</TT
> file, and create the key
            <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>HKEY_CLASSES_ROOT\.cgi\Shell\ExecCGI\Command</PRE
></FONT
></TD
></TR
></TABLE
>
            with <CODE
CLASS="option"
>C:\Perl\bin\perl.exe -T</CODE
> as value (adapt to your
            path if needed) in the registry. When this is done, restart Apache.
          </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="win32-email"
>2.5.1.4. Sending Email</A
></H4
><P
>&#13;          To enable Bugzilla to send email on Windows, the server running the
          Bugzilla code must be able to connect to, or act as, an SMTP server.
        </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="os-macosx"
>2.5.2. <SPAN
CLASS="productname"
>Mac OS X</SPAN
></A
></H3
><P
>Making Bugzilla work on Mac OS X requires the following 
      adjustments.</P
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="macosx-sendmail"
>2.5.2.1. Sendmail</A
></H4
><P
>In Mac OS X 10.3 and later, 
        <A
HREF="http://www.postfix.org/"
TARGET="_top"
>Postfix</A
> 
        is used as the built-in email server.  Postfix provides an executable
        that mimics sendmail enough to fool Bugzilla, as long as Bugzilla can 
        find it. Bugzilla is able to find the fake sendmail executable without
        any assistance.</P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="macosx-libraries"
>2.5.2.2. Libraries &#38; Perl Modules on Mac OS X</A
></H4
><P
>Apple does not include the GD library with Mac OS X. Bugzilla
        needs this for bug graphs.</P
><P
>You can use DarwinPorts (<A
HREF="http://darwinports.com/"
TARGET="_top"
>http://darwinports.com/</A
>)
        or Fink (<A
HREF="http://sourceforge.net/projects/fink/"
TARGET="_top"
>http://sourceforge.net/projects/fink/</A
>), both
        of which are similar in nature to the CPAN installer, but install
        common unix programs.</P
><P
>Follow the instructions for setting up DarwinPorts or Fink.
        Once you have one installed, you'll want to use it to install the
        <TT
CLASS="filename"
>gd2</TT
> package.
        </P
><P
>Fink will prompt you for a number of dependencies, type 'y' and hit
        enter to install all of the dependencies and then watch it work. You will
        then be able to use <A
HREF="#gloss-cpan"
><I
CLASS="glossterm"
>CPAN</I
></A
> to
        install the GD Perl module.
        </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>To prevent creating conflicts with the software that Apple
          installs by default, Fink creates its own directory tree at 
          <TT
CLASS="filename"
>/sw</TT
> where it installs most of
          the software that it installs. This means your libraries and headers
          will be at <TT
CLASS="filename"
>/sw/lib</TT
> and
          <TT
CLASS="filename"
>/sw/include</TT
> instead of
          <TT
CLASS="filename"
>/usr/lib</TT
> and
          <TT
CLASS="filename"
>/usr/include</TT
>. When the
          Perl module config script asks where your <TT
CLASS="filename"
>libgd</TT
>
          is, be sure to tell it
          <TT
CLASS="filename"
>/sw/lib</TT
>.
          </P
></TD
></TR
></TABLE
></DIV
><P
>Also available via DarwinPorts and Fink is
        <TT
CLASS="filename"
>expat</TT
>. After installing the expat package, you
        will be able to install XML::Parser using CPAN. If you use fink, there
        is one caveat. Unlike recent versions of
        the GD module, XML::Parser doesn't prompt for the location of the
        required libraries. When using CPAN, you will need to use the following
        command sequence:
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>&#13;# perl -MCPAN -e'look XML::Parser'        <A
NAME="macosx-look"
><IMG
SRC="../images/callouts/1.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(1)"></A
>
# perl Makefile.PL EXPATLIBPATH=/sw/lib EXPATINCPATH=/sw/include
# make; make test; make install           <A
NAME="macosx-make"
><IMG
SRC="../images/callouts/2.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(2)"></A
>
# exit                                    <A
NAME="macosx-exit"
><IMG
SRC="../images/callouts/3.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(3)"></A
>
        </PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="calloutlist"
><DL
COMPACT="COMPACT"
><DT
><A
HREF="#macosx-look"
><IMG
SRC="../images/callouts/1.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(1)"></A
><A
HREF="#macosx-exit"
><IMG
SRC="../images/callouts/3.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(3)"></A
></DT
><DD
>The look command will download the module and spawn a
            new shell with the extracted files as the current working directory.
            The exit command will return you to your original shell.
            </DD
><DT
><A
HREF="#macosx-make"
><IMG
SRC="../images/callouts/2.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(2)"></A
></DT
><DD
>You should watch the output from these make commands,
            especially <SPAN
CLASS="QUOTE"
>"make test"</SPAN
> as errors may prevent 
            XML::Parser from functioning correctly with Bugzilla.
            </DD
></DL
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="os-linux"
>2.5.3. Linux Distributions</A
></H3
><P
>Many Linux distributions include Bugzilla and its 
            dependencies in their native package management systems. 
            Installing Bugzilla with root access on any Linux system 
            should be as simple as finding the Bugzilla package in the 
            package management application and installing it using the 
            normal command syntax. Several distributions also perform 
            the proper web server configuration automatically on installation.
            </P
><P
>Please consult the documentation of your Linux 
            distribution for instructions on how to install packages, 
            or for specific instructions on installing Bugzilla with 
            native package management tools. There is also a 
            <A
HREF="http://wiki.mozilla.org/Bugzilla:Linux_Distro_Installation"
TARGET="_top"
>&#13;            Bugzilla Wiki Page</A
> for distro-specific installation
            notes.
            </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="nonroot"
>2.6. UNIX (non-root) Installation Notes</A
></H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN851"
>2.6.1. Introduction</A
></H3
><P
>If you are running a *NIX OS as non-root, either due
      to lack of access (web hosts, for example) or for security
      reasons, this will detail how to install Bugzilla on such
      a setup. It is recommended that you read through the
      <A
HREF="#installation"
>Section 2.1</A
>
      first to get an idea on the installation steps required.
      (These notes will reference to steps in that guide.)</P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="AEN855"
>2.6.2. MySQL</A
></H3
><P
>You may have MySQL installed as root. If you're
      setting up an account with a web host, a MySQL account
      needs to be set up for you. From there, you can create
      the bugs account, or use the account given to you.</P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>You may have problems trying to set up
        <B
CLASS="command"
>GRANT</B
> permissions to the database.
        If you're using a web host, chances are that you have a
        separate database which is already locked down (or one big
        database with limited/no access to the other areas), but you
        may want to ask your system administrator what the security
        settings are set to, and/or run the <B
CLASS="command"
>GRANT</B
>
        command for you.</P
><P
>Also, you will probably not be able to change the MySQL
        root user password (for obvious reasons), so skip that
        step.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="AEN863"
>2.6.2.1. Running MySQL as Non-Root</A
></H4
><DIV
CLASS="section"
><H5
CLASS="section"
><A
NAME="AEN865"
>2.6.2.1.1. The Custom Configuration Method</A
></H5
><P
>Create a file .my.cnf in your 
              home directory (using /home/foo in this example)
              as follows....</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;[mysqld]
datadir=/home/foo/mymysql
socket=/home/foo/mymysql/thesock
port=8081

[mysql]
socket=/home/foo/mymysql/thesock
port=8081

[mysql.server]
user=mysql
basedir=/var/lib

[safe_mysqld]
err-log=/home/foo/mymysql/the.log
pid-file=/home/foo/mymysql/the.pid
              </PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="AEN869"
>2.6.2.1.2. The Custom Built Method</A
></H5
><P
>You can install MySQL as a not-root, if you really need to.
            Build it with PREFIX set to <TT
CLASS="filename"
>/home/foo/mysql</TT
>,
            or use pre-installed executables, specifying that you want
            to put all of the data files in <TT
CLASS="filename"
>/home/foo/mysql/data</TT
>.
            If there is another MySQL server running on the system that you
            do not own, use the -P option to specify a TCP port that is not
            in use.</P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="AEN874"
>2.6.2.1.3. Starting the Server</A
></H5
><P
>After your mysqld program is built and any .my.cnf file is 
            in place, you must initialize the databases (ONCE).</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>&#13;              <SAMP
CLASS="prompt"
>bash$</SAMP
>
              <B
CLASS="command"
>mysql_install_db</B
>
            </PRE
></FONT
></TD
></TR
></TABLE
><P
>Then start the daemon with</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>&#13;              <SAMP
CLASS="prompt"
>bash$</SAMP
>
              <B
CLASS="command"
>safe_mysql &#38;</B
>
            </PRE
></FONT
></TD
></TR
></TABLE
><P
>After you start mysqld the first time, you then connect to
            it as "root" and <B
CLASS="command"
>GRANT</B
> permissions to other
            users. (Again, the MySQL root account has nothing to do with
            the *NIX root account.)</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>You will need to start the daemons yourself. You can either
              ask your system administrator to add them to system startup files, or
              add a crontab entry that runs a script to check on these daemons
              and restart them if needed.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Do NOT run daemons or other services on a server without first
              consulting your system administrator! Daemons use up system resources
              and running one may be in violation of your terms of service for any
              machine on which you are a user!</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="AEN890"
>2.6.3. Perl</A
></H3
><P
>&#13;      On the extremely rare chance that you don't have Perl on
      the machine, you will have to build the sources
      yourself. The following commands should get your system
      installed with your own personal version of Perl:
      </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>&#13;        <SAMP
CLASS="prompt"
>bash$</SAMP
>
        <B
CLASS="command"
>wget http://perl.org/CPAN/src/stable.tar.gz</B
>
        <SAMP
CLASS="prompt"
>bash$</SAMP
>
        <B
CLASS="command"
>tar zvxf stable.tar.gz</B
>
        <SAMP
CLASS="prompt"
>bash$</SAMP
>
        <B
CLASS="command"
>cd perl-5.8.1</B
> (or whatever the version of Perl is called)
        <SAMP
CLASS="prompt"
>bash$</SAMP
>
        <B
CLASS="command"
>sh Configure -de -Dprefix=/home/foo/perl</B
>
        <SAMP
CLASS="prompt"
>bash$</SAMP
>
        <B
CLASS="command"
>make &#38;&#38; make test &#38;&#38; make install</B
>
      </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;      Once you have Perl installed into a directory (probably
      in <TT
CLASS="filename"
>~/perl/bin</TT
>), you will need to
      install the Perl Modules, described below.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-perlmodules-nonroot"
>2.6.4. Perl Modules</A
></H3
><P
>&#13;      Installing the Perl modules as a non-root user is accomplished by
      running the <TT
CLASS="filename"
>install-module.pl</TT
>
      script. For more details on this script, see 
      <A
HREF="api/install-module.html"
TARGET="_top"
><TT
CLASS="filename"
>install-module.pl</TT
>
      documentation</A
>
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="AEN912"
>2.6.5. HTTP Server</A
></H3
><P
>Ideally, this also needs to be installed as root and
      run under a special web server account. As long as
      the web server will allow the running of *.cgi files outside of a
      cgi-bin, and a way of denying web access to certain files (such as a
      .htaccess file), you should be good in this department.</P
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="AEN915"
>2.6.5.1. Running Apache as Non-Root</A
></H4
><P
>You can run Apache as a non-root user, but the port will need
        to be set to one above 1024. If you type <B
CLASS="command"
>httpd -V</B
>,
        you will get a list of the variables that your system copy of httpd
        uses. One of those, namely HTTPD_ROOT, tells you where that
        installation looks for its config information.</P
><P
>From there, you can copy the config files to your own home
        directory to start editing. When you edit those and then use the -d
        option to override the HTTPD_ROOT compiled into the web server, you
        get control of your own customized web server.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>You will need to start the daemons yourself. You can either
          ask your system administrator to add them to system startup files, or
          add a crontab entry that runs a script to check on these daemons
          and restart them if needed.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Do NOT run daemons or other services on a server without first
          consulting your system administrator! Daemons use up system resources
          and running one may be in violation of your terms of service for any
          machine on which you are a user!</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="AEN924"
>2.6.6. Bugzilla</A
></H3
><P
>&#13;      When you run <B
CLASS="command"
>./checksetup.pl</B
> to create
      the <TT
CLASS="filename"
>localconfig</TT
> file, it will list the Perl
      modules it finds. If one is missing, go back and double-check the
      module installation from <A
HREF="#install-perlmodules-nonroot"
>Section 2.6.4</A
>, 
      then delete the <TT
CLASS="filename"
>localconfig</TT
> file and try again.
      </P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>One option in <TT
CLASS="filename"
>localconfig</TT
> you
        might have problems with is the web server group. If you can't
        successfully browse to the <TT
CLASS="filename"
>index.cgi</TT
> (like
        a Forbidden error), you may have to relax your permissions,
        and blank out the web server group. Of course, this may pose
        as a security risk. Having a properly jailed shell and/or
        limited access to shell accounts may lessen the security risk,
        but use at your own risk.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="suexec"
>2.6.6.1. suexec or shared hosting</A
></H4
><P
>If you are running on a system that uses suexec (most shared
        hosting environments do this), you will need to set the
        <EM
>webservergroup</EM
> value in <TT
CLASS="filename"
>localconfig</TT
>
        to match <EM
>your</EM
> primary group, rather than the one
        the web server runs under.  You will need to run the following
        shell commands after running <B
CLASS="command"
>./checksetup.pl</B
>,
        every time you run it (or modify <TT
CLASS="filename"
>checksetup.pl</TT
>
        to do them for you via the system() command).
        <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>        for i in docs graphs images js skins; do find $i -type d -exec chmod o+rx {} \; ; done
        for i in jpg gif css js png html rdf xul; do find . -name \*.$i -exec chmod o+r {} \; ; done
        find . -name .htaccess -exec chmod o+r {} \;
        chmod o+x . data data/webdot</PRE
></FONT
></TD
></TR
></TABLE
>
        Pay particular attention to the number of semicolons and dots.
        They are all important.  A future version of Bugzilla will
        hopefully be able to do this for you out of the box.</P
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="upgrade"
>2.7. Upgrading to New Releases</A
></H2
><P
>Upgrading to new Bugzilla releases is very simple. There is
      a script included with Bugzilla that will automatically
      do all of the database migration for you.</P
><P
>The following sections explain how to upgrade from one
      version of Bugzilla to another. Whether you are upgrading
      from one bug-fix version to another (such as 3.0.1 to 3.0.2)
      or from one major version to another (such as from 3.0 to 3.2),
      the instructions are always the same.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        Any examples in the following sections are written as though the
        user were updating to version 2.22.1, but the procedures are the
        same no matter what version you're updating to. Also, in the
        examples, the user's Bugzilla installation is found at
        <TT
CLASS="filename"
>/var/www/html/bugzilla</TT
>. If that is not the
        same as the location of your Bugzilla installation, simply
        substitute the proper paths where appropriate.
      </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="upgrade-before"
>2.7.1. Before You Upgrade</A
></H3
><P
>Before you start your upgrade, there are a few important
        steps to take:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;            Read the <A
HREF="http://www.bugzilla.org/releases/"
TARGET="_top"
>Release
            Notes</A
> of the version you're upgrading to,
            particularly the "Notes for Upgraders" section.
          </P
></LI
><LI
><P
>&#13;            View the Sanity Check (<A
HREF="#sanitycheck"
>Section 3.16</A
>) page
            on your installation before upgrading. Attempt to fix all warnings
            that the page produces before you go any further, or you may
            experience problems  during your upgrade.
          </P
></LI
><LI
><P
>&#13;            Shut down your Bugzilla installation by putting some HTML or
            text in the shutdownhtml parameter
            (see <A
HREF="#parameters"
>Section 3.1</A
>).
          </P
></LI
><LI
><P
>&#13;            Make a backup of the Bugzilla database.
            <EM
>THIS IS VERY IMPORTANT</EM
>. If
            anything goes wrong during the upgrade, your installation
            can be corrupted beyond recovery. Having a backup keeps you safe.
          </P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;              Upgrading is a one-way process. You cannot "downgrade" an
              upgraded Bugzilla. If you wish to revert to the old Bugzilla
              version for any reason, you will have to restore your database
              from this backup.
            </P
></TD
></TR
></TABLE
></DIV
><P
>Here are some sample commands you could use to backup
            your database, depending on what database system you're
            using. You may have to modify these commands for your
            particular setup.</P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>MySQL:</DT
><DD
><P
>&#13;                  <B
CLASS="command"
>mysqldump --opt -u bugs -p bugs &#62; bugs.sql</B
>
                </P
></DD
><DT
>PostgreSQL:</DT
><DD
><P
>&#13;                  <B
CLASS="command"
>pg_dump --no-privileges --no-owner -h localhost -U bugs
                    &#62; bugs.sql</B
>
                </P
></DD
></DL
></DIV
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="upgrade-files"
>2.7.2. Getting The New Bugzilla</A
></H3
><P
>There are three ways to get the new version of Bugzilla.
        We'll list them here briefly and then explain them
        more later.</P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>CVS (<A
HREF="#upgrade-cvs"
>Section 2.7.2.2</A
>)</DT
><DD
><P
>&#13;              If have <B
CLASS="command"
>cvs</B
> installed on your machine
              and you have Internet access, this is the easiest way to
              upgrade, particularly if you have made modifications
              to the code or templates of Bugzilla.
            </P
></DD
><DT
>Download the tarball (<A
HREF="#upgrade-tarball"
>Section 2.7.2.3</A
>)</DT
><DD
><P
>&#13;              This is a very simple way to upgrade, and good if you
              haven't made many (or any) modifications to the code or
              templates of your Bugzilla.
            </P
></DD
><DT
>Patches (<A
HREF="#upgrade-patches"
>Section 2.7.2.4</A
>)</DT
><DD
><P
>&#13;              If you have made modifications to your Bugzilla, and
              you don't have Internet access or you don't want to use
              cvs, then this is the best way to upgrade.
            </P
><P
>&#13;              You can only do minor upgrades (such as 3.0 to 3.0.1 or
              3.0.1 to 3.0.2) with patches.
            </P
></DD
></DL
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="upgrade-modified"
>2.7.2.1. If you have modified your Bugzilla</A
></H4
><P
>&#13;          If you have modified the code or templates of your Bugzilla,
          then upgrading requires a bit more thought and effort.
          A discussion of the various methods of updating compared with
          degree and methods of local customization can be found in
          <A
HREF="#template-method"
>Section 6.3.2</A
>.
        </P
><P
>&#13;          The larger the jump you are trying to make, the more difficult it
          is going to be to upgrade if you have made local customizations.
          Upgrading from 3.0 to 3.0.1 should be fairly painless even if
          you are heavily customized, but going from 2.18 to 3.0 is going
          to mean a fair bit of work re-writing your local changes to use
          the new files, logic, templates, etc. If you have done no local
          changes at all, however, then upgrading should be approximately
          the same amount of work regardless of how long it has been since
          your version was released.
        </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="upgrade-cvs"
>2.7.2.2. Upgrading using CVS</A
></H4
><P
>&#13;          This requires that you have cvs installed (most Unix machines do),
          and requires that you are able to access cvs-mirror.mozilla.org
          on port 2401, which may not be an option if you are behind a
          highly restrictive firewall or don't have Internet access.
        </P
><P
>&#13;          The following shows the sequence of commands needed to update a
          Bugzilla installation via CVS, and a typical series of results.
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;bash$ <B
CLASS="command"
>cd /var/www/html/bugzilla</B
>
bash$ <B
CLASS="command"
>cvs login</B
>
Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot
CVS password: <EM
>('anonymous', or just leave it blank)</EM
>
bash$ <B
CLASS="command"
>cvs -q update -r BUGZILLA-2_22_1 -dP</B
>
P checksetup.pl
P collectstats.pl
P docs/rel_notes.txt
P template/en/default/list/quips.html.tmpl
<EM
>(etc.)</EM
>
        </PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="caution"
><P
></P
><TABLE
CLASS="caution"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            If a line in the output from <B
CLASS="command"
>cvs update</B
> begins
            with a <SAMP
CLASS="computeroutput"
>C</SAMP
>, then that represents a
            file with local changes that CVS was unable to properly merge. You
            need to resolve these conflicts manually before Bugzilla (or at
            least the portion using that file) will be usable.
          </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="upgrade-tarball"
>2.7.2.3. Upgrading using the tarball</A
></H4
><P
>&#13;          If you are unable (or unwilling) to use CVS, another option that's
          always available is to obtain the latest tarball from the <A
HREF="http://www.bugzilla.org/download/"
TARGET="_top"
>Download Page</A
> and 
          create a new Bugzilla installation from that.
        </P
><P
>&#13;          This sequence of commands shows how to get the tarball from the
          command-line; it is also possible to download it from the site
          directly in a web browser. If you go that route, save the file
          to the <TT
CLASS="filename"
>/var/www/html</TT
>
          directory (or its equivalent, if you use something else) and 
          omit the first three lines of the example.
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;bash$ <B
CLASS="command"
>cd /var/www/html</B
>
bash$ <B
CLASS="command"
>wget http://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-2.22.1.tar.gz</B
>
<EM
>(Output omitted)</EM
>
bash$ <B
CLASS="command"
>tar xzvf bugzilla-2.22.1.tar.gz</B
>
bugzilla-2.22.1/
bugzilla-2.22.1/.cvsignore
<EM
>(Output truncated)</EM
>
bash$ <B
CLASS="command"
>cd bugzilla-2.22.1</B
>
bash$ <B
CLASS="command"
>cp ../bugzilla/localconfig* .</B
>
bash$ <B
CLASS="command"
>cp -r ../bugzilla/data .</B
>
bash$ <B
CLASS="command"
>cd ..</B
>
bash$ <B
CLASS="command"
>mv bugzilla bugzilla.old</B
>
bash$ <B
CLASS="command"
>mv bugzilla-2.22.1 bugzilla</B
>
        </PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            The <B
CLASS="command"
>cp</B
> commands both end with periods which
            is a very important detail--it means that the destination
            directory is the current working directory.
          </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;          This upgrade method will give you a clean install of Bugzilla.
          That's fine if you don't have any local customizations that you
          want to maintain. If you do have customizations, then you will 
          need to reapply them by hand to the appropriate files.
        </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="upgrade-patches"
>2.7.2.4. Upgrading using patches</A
></H4
><P
>&#13;          A patch is a collection of all the bug fixes that have been made
          since the last bug-fix release.
        </P
><P
>&#13;          If you are doing a bug-fix upgrade&#8212;that is, one where only the 
          last number of the revision changes, such as from 2.22 to
          2.22.1&#8212;then you have the option of obtaining and applying a
          patch file from the <A
HREF="http://www.bugzilla.org/download/"
TARGET="_top"
>Download Page</A
>.
        </P
><P
>&#13;          As above, this example starts with obtaining the file via the 
          command line. If you have already downloaded it, you can omit the
          first two commands.
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;bash$ <B
CLASS="command"
>cd /var/www/html/bugzilla</B
>
bash$ <B
CLASS="command"
>wget http://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-2.22-to-2.22.1.diff.gz</B
>
<EM
>(Output omitted)</EM
>
bash$ <B
CLASS="command"
>gunzip bugzilla-2.22-to-2.22.1.diff.gz</B
>
bash$ <B
CLASS="command"
>patch -p1 &#60; bugzilla-2.22-to-2.22.1.diff</B
>
patching file checksetup.pl
patching file collectstats.pl
<EM
>(etc.)</EM
>
        </PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            Be aware that upgrading from a patch file does not change the
            entries in your <TT
CLASS="filename"
>CVS</TT
> directory.
            This could make it more difficult to upgrade using CVS
            (<A
HREF="#upgrade-cvs"
>Section 2.7.2.2</A
>) in the future.
          </P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="upgrade-completion"
>2.7.3. Completing Your Upgrade</A
></H3
><P
>&#13;        Now that you have the new Bugzilla code, there are a few final
        steps to complete your upgrade.
      </P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;            If your new Bugzilla installation is in a different
            directory or on a different machine than your old Bugzilla
            installation, make sure that you have copied the
            <TT
CLASS="filename"
>data</TT
> directory and the
            <TT
CLASS="filename"
>localconfig</TT
> file from your old Bugzilla
            installation. (If you followed the tarball instructions
            above, this has already happened.)
          </P
></LI
><LI
><P
>&#13;            If this is a major update, check that the configuration
            (<A
HREF="#configuration"
>Section 2.2</A
>) for your new Bugzilla is
            up-to-date. Sometimes the configuration requirements change
            between major versions.
          </P
></LI
><LI
><P
>&#13;            If you didn't do it as part of the above configuration step,
            now you need to run <B
CLASS="command"
>checksetup.pl</B
>, which
            will do everything required to convert your existing database
            and settings for the new version:
          </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;bash$ <B
CLASS="command"
>cd /var/www/html/bugzilla</B
>
bash$ <B
CLASS="command"
>./checksetup.pl</B
>
          </PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;              The period at the beginning of the command
              <B
CLASS="command"
>./checksetup.pl</B
> is important and can not
              be omitted.
            </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="caution"
><P
></P
><TABLE
CLASS="caution"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;              If this is a major upgrade (say, 2.22 to 3.0 or similar),
              running <B
CLASS="command"
>checksetup.pl</B
> on a large
              installation (75,000 or more bugs) can take a long time,
              possibly several hours.
            </P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>&#13;            Clear any HTML or text that you put into the shutdownhtml
            parameter, to re-activate Bugzilla.
          </P
></LI
><LI
><P
>&#13;            View the Sanity Check (<A
HREF="#sanitycheck"
>Section 3.16</A
>) page in your
            upgraded Bugzilla.
          </P
><P
>&#13;            It is recommended that, if possible, you fix any problems
            you see, immediately. Failure to do this may mean that Bugzilla
            will not work correctly. Be aware that if the sanity check page
            contains more errors after an upgrade, it doesn't necessarily
            mean there are more errors in your database than there were
            before, as additional tests are added to the sanity check over
            time, and it is possible that those errors weren't being
            checked for in the old version.
          </P
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="upgrade-notifications"
>2.7.4. Automatic Notifications of New Releases</A
></H3
><P
>&#13;        Bugzilla 3.0 introduced the ability to automatically notify
        administrators when new releases are available, based on the
        <TT
CLASS="literal"
>upgrade_notification</TT
> parameter, see
        <A
HREF="#parameters"
>Section 3.1</A
>. Administrators will see these
        notifications when they access the <TT
CLASS="filename"
>index.cgi</TT
>
        page, i.e. generally when logging in. Bugzilla will check once per
        day for new releases, unless the parameter is set to
        <SPAN
CLASS="QUOTE"
>"disabled"</SPAN
>. If you are behind a proxy, you may have to set
        the <TT
CLASS="literal"
>proxy_url</TT
> parameter accordingly. If the proxy
        requires authentication, use the
        <TT
CLASS="literal"
>http://user:pass@proxy_url/</TT
> syntax.
      </P
></DIV
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="administration"
></A
>Chapter 3. Administering Bugzilla</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="parameters"
>3.1. Bugzilla Configuration</A
></H2
><P
>&#13;      Bugzilla is configured by changing various parameters, accessed
      from the "Parameters" link in the Administration page (the 
      Administration page can be found by clicking the "Administration"
      link in the footer). The parameters are divided into several categories,
      accessed via the menu on the left. Following is a description of the 
      different categories and important parameters within those categories. 
    </P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-requiredsettings"
>3.1.1. Required Settings</A
></H3
><P
>&#13;          The core required parameters for any Bugzilla installation are set
          here. These parameters must be set before a new Bugzilla installation
          can be used. Administrators should review this list before 
          deploying a new Bugzilla installation.
        </P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>maintainer</DT
><DD
><P
> 
              Email address of the person 
              responsible for maintaining this Bugzilla installation.
              The address need not be that of a valid Bugzilla account.
            </P
></DD
><DT
>urlbase</DT
><DD
><P
>&#13;                Defines the fully qualified domain name and web 
                server path to this Bugzilla installation.
              </P
><P
>&#13;                For example, if the Bugzilla query page is
                <TT
CLASS="filename"
>http://www.foo.com/bugzilla/query.cgi</TT
>, 
                the <SPAN
CLASS="QUOTE"
>"urlbase"</SPAN
> should be set
                to <TT
CLASS="filename"
>http://www.foo.com/bugzilla/</TT
>.
              </P
></DD
><DT
>docs_urlbase</DT
><DD
><P
>&#13;                Defines path to the Bugzilla documentation. This can be a fully
                qualified domain name, or a path relative to "urlbase".
              </P
><P
>&#13;                For example, if the "Bugzilla Configuration" page 
                of the documentation is
                <TT
CLASS="filename"
>http://www.foo.com/bugzilla/docs/html/parameters.html</TT
>, 
                set the <SPAN
CLASS="QUOTE"
>"docs_urlbase"</SPAN
>
                to <TT
CLASS="filename"
>http://www.foo.com/bugzilla/docs/html/</TT
>.
              </P
></DD
><DT
>sslbase</DT
><DD
><P
>&#13;                Defines the fully qualified domain name and web 
                server path for HTTPS (SSL) connections to this Bugzilla installation.
              </P
><P
>&#13;                For example, if the Bugzilla main page is
                <TT
CLASS="filename"
>https://www.foo.com/bugzilla/index.cgi</TT
>, 
                the <SPAN
CLASS="QUOTE"
>"sslbase"</SPAN
> should be set
                to <TT
CLASS="filename"
>https://www.foo.com/bugzilla/</TT
>.
              </P
></DD
><DT
>ssl_redirect</DT
><DD
><P
>&#13;                If enabled, Bugzilla will force HTTPS (SSL) connections, by
                automatically redirecting any users who try to use a non-SSL
                connection.
              </P
></DD
><DT
>cookiedomain</DT
><DD
><P
>&#13;               Defines the domain for Bugzilla cookies. This is typically left blank.
               If there are multiple hostnames that point to the same webserver, which
               require the same cookie, then this parameter can be utilized. For
               example, If your website is at 
               <TT
CLASS="filename"
>https://www.foo.com/</TT
>, setting this to 
               <TT
CLASS="filename"
>.foo.com/</TT
> will also allow 
               <TT
CLASS="filename"
>bar.foo.com/</TT
> to access Bugzilla cookies.
              </P
></DD
><DT
>cookiepath</DT
><DD
><P
>&#13;                Defines a path, relative to the web server root, that Bugzilla
                cookies will be restricted to. For example, if the 
                <B
CLASS="command"
>urlbase</B
> is set to
                <TT
CLASS="filename"
>http://www.foo.com/bugzilla/</TT
>, the 
                <B
CLASS="command"
>cookiepath</B
> should be set to 
                <TT
CLASS="filename"
>/bugzilla/</TT
>. Setting it to "/" will allow all sites 
                served by this web server or virtual host to read Bugzilla cookies.
              </P
></DD
><DT
>utf8</DT
><DD
><P
>&#13;               Determines whether to use UTF-8 (Unicode) encoding for all text in 
               Bugzilla. New installations should set this to true to avoid character 
               encoding problems. Existing databases should set this to true only 
               after the data has been converted from existing legacy character 
               encoding to UTF-8, using the 
               <TT
CLASS="filename"
>contrib/recode.pl</TT
> script.
              </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;                  If you turn this parameter from "off" to "on", you must re-run 
                  <TT
CLASS="filename"
>checksetup.pl</TT
> immediately afterward.
                </P
></TD
></TR
></TABLE
></DIV
></DD
><DT
>shutdownhtml</DT
><DD
><P
>&#13;                If there is any text in this field, this Bugzilla installation will
                be completely disabled and this text will appear instead of all
                Bugzilla pages for all users, including Admins. Used in the event 
                of site maintenance or outage situations. 
              </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;                  Although regular log-in capability is disabled while 
                  <B
CLASS="command"
>shutdownhtml</B
>
                  is enabled, safeguards are in place to protect the unfortunate 
                  admin who loses connection to Bugzilla. Should this happen to you,
                  go directly to the <TT
CLASS="filename"
>editparams.cgi</TT
> (by typing
                  the URL in manually, if necessary). Doing this will prompt you to
                  log in, and your name/password will be accepted here (but nowhere
                  else). 
                </P
></TD
></TR
></TABLE
></DIV
></DD
><DT
>announcehtml</DT
><DD
><P
>&#13;                Any text in this field will be displayed at the top of every HTML
                page in this Bugzilla installation. The text is not wrapped in any
                tags. For best results, wrap the text in a <SPAN
CLASS="QUOTE"
>"&#60;div&#62;"</SPAN
>
                tag. Any style attributes from the CSS can be applied. For example,
                to make the text green inside of a red box, add <SPAN
CLASS="QUOTE"
>"id=message"</SPAN
>
                to the <SPAN
CLASS="QUOTE"
>"&#60;div&#62;"</SPAN
> tag.
              </P
></DD
><DT
>proxy_url</DT
><DD
><P
>&#13;                If this Bugzilla installation is behind a proxy, enter the proxy 
                information here to enable Bugzilla to access the Internet. Bugzilla
                requires Internet access to utilize the 
                <B
CLASS="command"
>upgrade_notification</B
> parameter (below). If the 
                proxy requires authentication, use the syntax:
                <TT
CLASS="filename"
>http://user:pass@proxy_url/</TT
>.
              </P
></DD
><DT
>upgrade_notification</DT
><DD
><P
>&#13;                Enable or disable a notification on the homepage of this Bugzilla
                installation when a newer version of Bugzilla is available. This
                notification is only visible to administrators. Choose "disabled",
                to turn off the notification. Otherwise, choose which version of
                Bugzilla you want to be notified about: "development_snapshot" is the
                latest release on the trunk; "latest_stable_release" is the most 
                recent release available on the most recent stable branch; 
                "stable_branch_release" the most recent release on the branch 
                this installation is based on.
              </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-admin-policies"
>3.1.2. Administrative Policies</A
></H3
><P
>&#13;            This page contains parameters for basic administrative functions.
            Options include whether to allow the deletion of bugs and users,
            and whether to allow users to change their email address.
          </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-user-authentication"
>3.1.3. User Authentication</A
></H3
><P
>&#13;            This page contains the settings that control how this Bugzilla
            installation will do its authentication. Choose what authentication
            mechanism to use (the Bugzilla database, or an external source such
            as LDAP), and set basic behavioral parameters. For example, choose
            whether to require users to login to browse bugs, the management
            of authentication cookies, and the regular expression used to
            validate email addresses. Some parameters are highlighted below.
          </P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>emailregexp</DT
><DD
><P
>&#13;                Defines the regular expression used to validate email addresses
                used for login names. The default attempts to match fully
                qualified email addresses (i.e. 'user@example.com'). Some
                Bugzilla installations allow only local user names (i.e 'user' 
                instead of 'user@example.com'). In that case, the 
                <B
CLASS="command"
>emailsuffix</B
> parameter should be used to define
                the email domain.    
              </P
></DD
><DT
>emailsuffix</DT
><DD
><P
>&#13;                This string is appended to login names when actually sending 
                email to a user. For example,
                If <B
CLASS="command"
>emailregexp</B
> has been set to allow
                local usernames,
                then this parameter would contain the email domain for all users
                (i.e. '@example.com').   
              </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-attachments"
>3.1.4. Attachments</A
></H3
><P
>&#13;            This page allows for setting restrictions and other parameters
            regarding attachments to bugs. For example, control size limitations
            and whether to allow pointing to external files via a URI.
          </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-bug-change-policies"
>3.1.5. Bug Change Policies</A
></H3
><P
>&#13;            Set policy on default behavior for bug change events. For example,
            choose which status to set a bug to when it is marked as a duplicate,
            and choose whether to allow bug reporters to set the priority or
            target milestone. Also allows for configuration of what changes
            should require the user to make a comment, described below.    
          </P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>commenton*</DT
><DD
><P
>&#13;                All these fields allow you to dictate what changes can pass
                without comment, and which must have a comment from the
                person who changed them.  Often, administrators will allow
                users to add themselves to the CC list, accept bugs, or
                change the Status Whiteboard without adding a comment as to
                their reasons for the change, yet require that most other
                changes come with an explanation.
              </P
><P
>&#13;                Set the "commenton" options according to your site policy. It
                is a wise idea to require comments when users resolve, reassign, or
                reopen bugs at the very least. 
              </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;                  It is generally far better to require a developer comment
                  when resolving bugs than not. Few things are more annoying to bug
                  database users than having a developer mark a bug "fixed" without
                  any comment as to what the fix was (or even that it was truly
                  fixed!)
                </P
></TD
></TR
></TABLE
></DIV
></DD
><DT
>noresolveonopenblockers</DT
><DD
><P
>&#13;                This option will prevent users from resolving bugs as FIXED if
                they have unresolved dependencies. Only the FIXED resolution
                is affected. Users will be still able to resolve bugs to
                resolutions other than FIXED if they have unresolved dependent
                bugs.
              </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-bugfields"
>3.1.6. Bug Fields</A
></H3
><P
>&#13;            The parameters in this section determine the default settings of
            several Bugzilla fields for new bugs, and also control whether
            certain fields are used. For example, choose whether to use the
            "target milestone" field or the "status whiteboard" field.
          </P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>useqacontact</DT
><DD
><P
>&#13;                This allows you to define an email address for each component, 
                in addition to that of the default assignee, who will be sent
                carbon copies of incoming bugs.
              </P
></DD
><DT
>usestatuswhiteboard</DT
><DD
><P
>&#13;                This defines whether you wish to have a free-form, overwritable field
                associated with each bug. The advantage of the Status Whiteboard is
                that it can be deleted or modified with ease, and provides an
                easily-searchable field for indexing some bugs that have some trait
                in common.         
              </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-bugmoving"
>3.1.7. Bug Moving</A
></H3
><P
>&#13;            This page controls whether this Bugzilla installation allows certain
            users to move bugs to an external database. If bug moving is enabled,
            there are a number of parameters that control bug moving behaviors. 
            For example, choose which users are allowed to move bugs, the location
            of the external database, and the default product and component that
            bugs moved <EM
>from</EM
> other bug databases to this 
            Bugzilla installation are assigned to. 
          </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-dependency-graphs"
>3.1.8. Dependency Graphs</A
></H3
><P
>&#13;            This page has one parameter that sets the location of a Web Dot
            server, or of the Web Dot binary on the local system, that is used
            to generate dependency graphs. Web Dot is a CGI program that creates
            images from <TT
CLASS="filename"
>.dot</TT
> graphic description files. If
            no Web Dot server or binary is specified, then dependency graphs will
            be disabled.
          </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-group-security"
>3.1.9. Group Security</A
></H3
><P
>&#13;              Bugzilla allows for the creation of different groups, with the
              ability to restrict the visibility of bugs in a group to a set of 
              specific users. Specific products can also be associated with
              groups, and users restricted to only see products in their groups.
              Several parameters are described in more detail below. Most of the
              configuration of groups and their relationship to products is done
              on the "Groups" and "Product" pages of the "Administration" area.
              The options on this page control global default behavior. 
              For more information on Groups and Group Security, see
              <A
HREF="#groups"
>Section 3.15</A
> 
            </P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>makeproductgroups</DT
><DD
><P
>&#13;                Determines whether or not to automatically create groups
                when new products are created. If this is on, the groups will be
                used for querying bugs.
              </P
></DD
><DT
>usevisibilitygroups</DT
><DD
><P
>&#13;                If selected, user visibility will be restricted to members of
                groups, as selected in the group configuration settings. 
                Each user-defined group can be allowed to see members of selected
                other groups. 
                For details on configuring groups (including the visibility 
                restrictions) see <A
HREF="#edit-groups"
>Section 3.15.2</A
>. 
              </P
></DD
><DT
>querysharegroup</DT
><DD
><P
>&#13;                The name of the group of users who are allowed to share saved
                searches with one another. For more information on using 
                saved searches, see <A
HREF="#savedsearches"
>Saved Searches</A
>.
              </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="bzldap"
>3.1.10. LDAP Authentication</A
></H3
><P
>LDAP authentication is a module for Bugzilla's plugin 
          authentication architecture. This page contains all the parameters
          necessary to configure Bugzilla for use with LDAP authentication.
          </P
><P
>&#13;          The existing authentication
          scheme for Bugzilla uses email addresses as the primary user ID, and a
          password to authenticate that user. All places within Bugzilla that
          require a user ID (e.g assigning a bug) use the email
          address. The LDAP authentication builds on top of this scheme, rather
          than replacing it. The initial log-in is done with a username and
          password for the LDAP directory. Bugzilla tries to bind to LDAP using
          those credentials and, if successful, tries to map this account to a
          Bugzilla account. If an LDAP mail attribute is defined, the value of this
          attribute is used, otherwise the "emailsuffix" parameter is appended to LDAP
          username to form a full email address. If an account for this address
          already exists in the Bugzilla installation, it will log in to that account.
          If no account for that email address exists, one is created at the time
          of login. (In this case, Bugzilla will attempt to use the "displayName"
          or "cn" attribute to determine the user's full name.) After
          authentication, all other user-related tasks are still handled by email
          address, not LDAP username. For example, bugs are still assigned by
          email address and users are still queried by email address.
          </P
><DIV
CLASS="caution"
><P
></P
><TABLE
CLASS="caution"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Because the Bugzilla account is not created until the first time
            a user logs in, a user who has not yet logged is unknown to Bugzilla.
            This means they cannot be used as an assignee or QA contact (default or
            otherwise), added to any CC list, or any other such operation. One
            possible workaround is the <TT
CLASS="filename"
>bugzilla_ldapsync.rb</TT
>
            script in the
            <A
HREF="#gloss-contrib"
><I
CLASS="glossterm"
>&#13;            <TT
CLASS="filename"
>contrib</TT
></I
></A
> 
            directory. Another possible solution is fixing
            <A
HREF="https://bugzilla.mozilla.org/show_bug.cgi?id=201069"
TARGET="_top"
>bug
            201069</A
>.
            </P
></TD
></TR
></TABLE
></DIV
><P
>Parameters required to use LDAP Authentication:</P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><A
NAME="param-user_verify_class_for_ldap"
></A
>user_verify_class</DT
><DD
><P
>If you want to list <SPAN
CLASS="QUOTE"
>"LDAP"</SPAN
> here,
                make sure to have set up the other parameters listed below.
                Unless you have other (working) authentication methods listed as
                well, you may otherwise not be able to log back in to Bugzilla once
                you log out.
                If this happens to you, you will need to manually edit
                <TT
CLASS="filename"
>data/params</TT
> and set user_verify_class to
                <SPAN
CLASS="QUOTE"
>"DB"</SPAN
>.
                </P
></DD
><DT
><A
NAME="param-LDAPserver"
></A
>LDAPserver</DT
><DD
><P
>This parameter should be set to the name (and optionally the
                port) of your LDAP server. If no port is specified, it assumes
                the default LDAP port of 389.
                </P
><P
>For example: <SPAN
CLASS="QUOTE"
>"ldap.company.com"</SPAN
>
                 or <SPAN
CLASS="QUOTE"
>"ldap.company.com:3268"</SPAN
>
                </P
><P
>You can also specify a LDAP URI, so as to use other
                protocols, such as LDAPS or LDAPI. If port was not specified in
                the URI, the default is either 389 or 636 for 'LDAP' and 'LDAPS'
                schemes respectively.
                </P
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;                    In order to use SSL with LDAP, specify a URI with "ldaps://".
                    This will force the use of SSL over port 636.
                  </P
></TD
></TR
></TABLE
></DIV
><P
>For example, normal LDAP: 
                <SPAN
CLASS="QUOTE"
>"ldap://ldap.company.com"</SPAN
>, LDAP over SSL:
                <SPAN
CLASS="QUOTE"
>"ldaps://ldap.company.com"</SPAN
> or LDAP over a UNIX 
                domain socket <SPAN
CLASS="QUOTE"
>"ldapi://%2fvar%2flib%2fldap_sock"</SPAN
>.
                </P
></DD
><DT
><A
NAME="param-LDAPbinddn"
></A
>LDAPbinddn [Optional]</DT
><DD
><P
>Some LDAP servers will not allow an anonymous bind to search
                 the directory. If this is the case with your configuration you
                 should set the LDAPbinddn parameter to the user account Bugzilla
                 should use instead of the anonymous bind.
                 </P
><P
>Ex. <SPAN
CLASS="QUOTE"
>"cn=default,cn=user:password"</SPAN
></P
></DD
><DT
><A
NAME="param-LDAPBaseDN"
></A
>LDAPBaseDN</DT
><DD
><P
>The LDAPBaseDN parameter should be set to the location in
                 your LDAP tree that you would like to search for email addresses.
                 Your uids should be unique under the DN specified here.
                 </P
><P
>Ex. <SPAN
CLASS="QUOTE"
>"ou=People,o=Company"</SPAN
></P
></DD
><DT
><A
NAME="param-LDAPuidattribute"
></A
>LDAPuidattribute</DT
><DD
><P
>The LDAPuidattribute parameter should be set to the attribute
                 which contains the unique UID of your users. The value retrieved
                 from this attribute will be used when attempting to bind as the
                 user to confirm their password.
                 </P
><P
>Ex. <SPAN
CLASS="QUOTE"
>"uid"</SPAN
></P
></DD
><DT
><A
NAME="param-LDAPmailattribute"
></A
>LDAPmailattribute</DT
><DD
><P
>The LDAPmailattribute parameter should be the name of the
                 attribute which contains the email address your users will enter
                 into the Bugzilla login boxes.
                 </P
><P
>Ex. <SPAN
CLASS="QUOTE"
>"mail"</SPAN
></P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="bzradius"
>3.1.11. RADIUS Authentication</A
></H3
><P
>&#13;          RADIUS authentication is a module for Bugzilla's plugin 
          authentication architecture. This page contains all the parameters
          necessary for configuring Bugzilla to use RADIUS authentication.
          </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;              Most caveats that apply to LDAP authentication apply to RADIUS
              authentication as well. See <A
HREF="#bzldap"
>Section 3.1.10</A
> for details.
            </P
></TD
></TR
></TABLE
></DIV
><P
>Parameters required to use RADIUS Authentication:</P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><A
NAME="param-user_verify_class_for_radius"
></A
>user_verify_class</DT
><DD
><P
>If you want to list <SPAN
CLASS="QUOTE"
>"RADIUS"</SPAN
> here,
                make sure to have set up the other parameters listed below.
                Unless you have other (working) authentication methods listed as
                well, you may otherwise not be able to log back in to Bugzilla once
                you log out.
                If this happens to you, you will need to manually edit
                <TT
CLASS="filename"
>data/params</TT
> and set user_verify_class to
                <SPAN
CLASS="QUOTE"
>"DB"</SPAN
>.
                </P
></DD
><DT
><A
NAME="param-RADIUS_server"
></A
>RADIUS_server</DT
><DD
><P
>This parameter should be set to the name (and optionally the
                port) of your RADIUS server.
                </P
></DD
><DT
><A
NAME="param-RADIUS_secret"
></A
>RADIUS_secret</DT
><DD
><P
>This parameter should be set to the RADIUS server's secret.
                </P
></DD
><DT
><A
NAME="param-RADIUS_email_suffix"
></A
>RADIUS_email_suffix</DT
><DD
><P
>Bugzilla needs an e-mail address for each user account.
                Therefore, it needs to determine the e-mail address corresponding
                to a RADIUS user.
                Bugzilla offers only a simple way to do this: it can concatenate
                a suffix to the RADIUS user name to convert it into an e-mail
                address.
                You can specify this suffix in the RADIUS_email_suffix parameter.
                </P
><P
>If this simple solution does not work for you, you'll
                probably need to modify
                <TT
CLASS="filename"
>Bugzilla/Auth/Verify/RADIUS.pm</TT
> to match your
                requirements.
                </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-email"
>3.1.12. Email</A
></H3
><P
>&#13;            This page contains all of the parameters for configuring how
            Bugzilla deals with the email notifications it sends. See below
            for a summary of important options. 
          </P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>mail_delivery_method</DT
><DD
><P
>&#13;                This is used to specify how email is sent, or if it is sent at 
                all.  There are several options included for different MTAs, 
                along with two additional options that disable email sending.  
                "Test" does not send mail, but instead saves it in 
                <TT
CLASS="filename"
>data/mailer.testfile</TT
> for later review.  
                "None" disables email sending entirely.
              </P
></DD
><DT
>mailfrom</DT
><DD
><P
>&#13;                This is the email address that will appear in the "From" field
                of all emails sent by this Bugzilla installation. Some email
                servers require mail to be from a valid email address, therefore
                it is recommended to choose a valid email address here.
              </P
></DD
><DT
>whinedays</DT
><DD
><P
>&#13;                Set this to the number of days you want to let bugs go
                in the CONFIRMED state before notifying people they have
                untouched new bugs. If you do not plan to use this feature, simply 
                do not set up the whining cron job described in the installation
                instructions, or set this value to "0" (never whine).
              </P
></DD
><DT
>globalwatcher</DT
><DD
><P
>&#13;                This allows you to define specific users who will
                receive notification each time a new bug in entered, or when
                an existing bug changes, according to the normal groupset
                permissions. It may be useful for sending notifications to a
                mailing-list, for instance.
              </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-patchviewer"
>3.1.13. Patch Viewer</A
></H3
><P
>&#13;            This page contains configuration parameters for the CVS server, 
            Bonsai server and LXR server that Bugzilla will use to enable the
            features of the Patch Viewer. Bonsai is a tool that enables queries 
            to a CVS tree. LXR is a tool that can cross reference and index source
            code.
          </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-querydefaults"
>3.1.14. Query Defaults</A
></H3
><P
>&#13;            This page controls the default behavior of Bugzilla in regards to 
            several aspects of querying bugs. Options include what the default
            query options are, what the "My Bugs" page returns, whether users
            can freely add bugs to the quip list, and how many duplicate bugs are 
            needed to add a bug to the "most frequently reported" list.
          </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="param-shadowdatabase"
>3.1.15. Shadow Database</A
></H3
><P
>&#13;            This page controls whether a shadow database is used, and all the
            parameters associated with the shadow database. Versions of Bugzilla
            prior to 3.2 used the MyISAM table type, which supports
            only table-level write locking. With MyISAM, any time someone is making a change to 
            a bug, the entire table is locked until the write operation is complete.
            Locking for write also blocks reads until the write is complete.
          </P
><P
>&#13;            The <SPAN
CLASS="QUOTE"
>"shadowdb"</SPAN
> parameter was designed to get around
            this limitation. While only a single user is allowed to write to
            a table at a time, reads can continue unimpeded on a read-only
            shadow copy of the database.
          </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;              As of version 3.2, Bugzilla no longer uses the MyISAM table type.
              Instead, InnoDB is used, which can do transaction-based locking.
              Therefore, the limitations the Shadow Database feature was designed
              to workaround no longer exist.
            </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="admin-usermatching"
>3.1.16. User Matching</A
></H3
><P
>&#13;            The settings on this page control how users are selected and queried
            when adding a user to a bug. For example, users need to be selected
            when choosing who the bug is assigned to, adding to the CC list or 
            selecting a QA contact. With the "usemenuforusers" parameter, it is 
            possible to configure Bugzilla to 
            display a list of users in the fields instead of an empty text field.
            This should only be used in Bugzilla installations with a small number
            of users. If users are selected via a text box, this page also
            contains parameters for how user names can be queried and matched
            when entered.
          </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="useradmin"
>3.2. User Administration</A
></H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="defaultuser"
>3.2.1. Creating the Default User</A
></H3
><P
>When you first run checksetup.pl after installing Bugzilla, it
      will prompt you for the administrative username (email address) and
      password for this "super user". If for some reason you delete
      the "super user" account, re-running checksetup.pl will again prompt
      you for this username and password.</P
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you wish to add more administrative users, add them to 
        the "admin" group and, optionally, edit the tweakparams, editusers,
        creategroups, editcomponents, and editkeywords groups to add the
        entire admin group to those groups (which is the case by default).
        </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="manageusers"
>3.2.2. Managing Other Users</A
></H3
><DIV
CLASS="section"
><H4
CLASS="section"
><A
NAME="user-account-search"
>3.2.2.1. Searching for existing users</A
></H4
><P
>&#13;          If you have <SPAN
CLASS="QUOTE"
>"editusers"</SPAN
> privileges or if you are allowed
          to grant privileges for some groups, the <SPAN
CLASS="QUOTE"
>"Users"</SPAN
> link
          will appear in the Administration page.
        </P
><P
>&#13;          The first screen is a search form to search for existing user
          accounts. You can run searches based either on the user ID, real
          name or login name (i.e. the email address, or just the first part
          of the email address if the "emailsuffix" parameter is set).
          The search can be conducted
          in different ways using the listbox to the right of the text entry
          box. You can match by case-insensitive substring (the default),
          regular expression, a <EM
>reverse</EM
> regular expression
          match (which finds every user name which does NOT match the regular
          expression), or the exact string if you know exactly who you are
          looking for. The search can be restricted to users who are in a
          specific group. By default, the restriction is turned off.
        </P
><P
>&#13;          The search returns a list of
          users matching your criteria. User properties can be edited by clicking
          the login name. The Account History of a user can be viewed by clicking
          the "View" link in the Account History column. The Account History
          displays changes that have been made to the user account, the time of
          the change and the user who made the change. For example, the Account
          History page will display details of when a user was added or removed
          from a group.
        </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="createnewusers"
>3.2.2.2. Creating new users</A
></H4
><DIV
CLASS="section"
><H5
CLASS="section"
><A
NAME="self-registration"
>3.2.2.2.1. Self-registration</A
></H5
><P
>&#13;            By default, users can create their own user accounts by clicking the
            <SPAN
CLASS="QUOTE"
>"New Account"</SPAN
> link at the bottom of each page (assuming
            they aren't logged in as someone else already). If you want to disable
            this self-registration, or if you want to restrict who can create his
            own user account, you have to edit the <SPAN
CLASS="QUOTE"
>"createemailregexp"</SPAN
>
            parameter in the <SPAN
CLASS="QUOTE"
>"Configuration"</SPAN
> page, see
            <A
HREF="#parameters"
>Section 3.1</A
>.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="user-account-creation"
>3.2.2.2.2. Accounts created by an administrator</A
></H5
><P
>&#13;            Users with <SPAN
CLASS="QUOTE"
>"editusers"</SPAN
> privileges, such as administrators,
            can create user accounts for other users:
          </P
><P
></P
><OL
TYPE="1"
><LI
><P
>After logging in, click the "Users" link at the footer of
              the query page, and then click "Add a new user".</P
></LI
><LI
><P
>Fill out the form presented. This page is self-explanatory.
              When done, click "Submit".</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Adding a user this way will <EM
>not</EM
>
                send an email informing them of their username and password.
                While useful for creating dummy accounts (watchers which
                shuttle mail to another system, for instance, or email
                addresses which are a mailing list), in general it is
                preferable to log out and use the <SPAN
CLASS="QUOTE"
>"New Account"</SPAN
>
                button to create users, as it will pre-populate all the
                required fields and also notify the user of her account name
                and password.</P
></TD
></TR
></TABLE
></DIV
></LI
></OL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="modifyusers"
>3.2.2.3. Modifying Users</A
></H4
><P
>Once you have found your user, you can change the following
        fields:</P
><P
></P
><UL
><LI
><P
>&#13;            <EM
>Login Name</EM
>: 
            This is generally the user's full email address. However, if you
            have are using the <SPAN
CLASS="QUOTE"
>"emailsuffix"</SPAN
> parameter, this may
            just be the user's login name. Note that users can now change their
            login names themselves (to any valid email address).
            </P
></LI
><LI
><P
>&#13;            <EM
>Real Name</EM
>: The user's real name. Note that
            Bugzilla does not require this to create an account.</P
></LI
><LI
><P
>&#13;            <EM
>Password</EM
>: 
            You can change the user's password here. Users can automatically
            request a new password, so you shouldn't need to do this often.
            If you want to disable an account, see Disable Text below.
            </P
></LI
><LI
><P
>&#13;              <EM
>Bugmail Disabled</EM
>:
              Mark this checkbox to disable bugmail and whinemail completely
              for this account. This checkbox replaces the data/nomail file
              which existed in older versions of Bugzilla.
            </P
></LI
><LI
><P
>&#13;              <EM
>Disable Text</EM
>: 
              If you type anything in this box, including just a space, the
              user is prevented from logging in, or making any changes to 
              bugs via the web interface. 
              The HTML you type in this box is presented to the user when
              they attempt to perform these actions, and should explain
              why the account was disabled.
            </P
><P
>&#13;              Users with disabled accounts will continue to receive
              mail from Bugzilla; furthermore, they will not be able
              to log in themselves to change their own preferences and
              stop it. If you want an account (disabled or active) to
              stop receiving mail, simply check the
              <SPAN
CLASS="QUOTE"
>"Bugmail Disabled"</SPAN
> checkbox above.
            </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;                Even users whose accounts have been disabled can still
                submit bugs via the e-mail gateway, if one exists.
                The e-mail gateway should <EM
>not</EM
> be
                enabled for secure installations of Bugzilla.
              </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;                Don't disable all the administrator accounts!
              </P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>&#13;            <EM
>&#60;groupname&#62;</EM
>: 
            If you have created some groups, e.g. "securitysensitive", then
            checkboxes will appear here to allow you to add users to, or
            remove them from, these groups. The first checkbox gives the
            user the ability to add and remove other users as members of
            this group. The second checkbox adds the user himself as a member
            of the group.
            </P
></LI
><LI
><P
>&#13;            <EM
>canconfirm</EM
>: 
            This field is only used if you have enabled the "unconfirmed"
            status. If you enable this for a user,
            that user can then move bugs from "Unconfirmed" to a "Confirmed"
            status (e.g.: "New" status).</P
></LI
><LI
><P
>&#13;            <EM
>creategroups</EM
>: 
            This option will allow a user to create and destroy groups in
            Bugzilla.</P
></LI
><LI
><P
>&#13;            <EM
>editbugs</EM
>: 
            Unless a user has this bit set, they can only edit those bugs
            for which they are the assignee or the reporter. Even if this
            option is unchecked, users can still add comments to bugs.
            </P
></LI
><LI
><P
>&#13;            <EM
>editcomponents</EM
>: 
            This flag allows a user to create new products and components,
            as well as modify and destroy those that have no bugs associated
            with them. If a product or component has bugs associated with it,
            those bugs must be moved to a different product or component
            before Bugzilla will allow them to be destroyed.
            </P
></LI
><LI
><P
>&#13;            <EM
>editkeywords</EM
>: 
            If you use Bugzilla's keyword functionality, enabling this
            feature allows a user to create and destroy keywords. As always,
            the keywords for existing bugs containing the keyword the user
            wishes to destroy must be changed before Bugzilla will allow it
            to die.</P
></LI
><LI
><P
>&#13;            <EM
>editusers</EM
>: 
            This flag allows a user to do what you're doing right now: edit
            other users. This will allow those with the right to do so to
            remove administrator privileges from other users or grant them to
            themselves. Enable with care.</P
></LI
><LI
><P
>&#13;            <EM
>tweakparams</EM
>: 
            This flag allows a user to change Bugzilla's Params 
            (using <TT
CLASS="filename"
>editparams.cgi</TT
>.)</P
></LI
><LI
><P
> 
            <EM
>&#60;productname&#62;</EM
>:
            This allows an administrator to specify the products 
            in which a user can see bugs. If you turn on the 
            <SPAN
CLASS="QUOTE"
>"makeproductgroups"</SPAN
> parameter in
            the Group Security Panel in the Parameters page, 
            then Bugzilla creates one group per product (at the time you create 
            the product), and this group has exactly the same name as the 
            product itself. Note that for products that already exist when
            the parameter is turned on, the corresponding group will not be
            created. The user must still have the <SPAN
CLASS="QUOTE"
>"editbugs"</SPAN
> 
            privilege to edit bugs in these products.</P
></LI
></UL
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="user-account-deletion"
>3.2.2.4. Deleting Users</A
></H4
><P
>&#13;          If the <SPAN
CLASS="QUOTE"
>"allowuserdeletion"</SPAN
> parameter is turned on, see
          <A
HREF="#parameters"
>Section 3.1</A
>, then you can also delete user accounts.
          Note that this is most of the time not the best thing to do. If only
          a warning in a yellow box is displayed, then the deletion is safe.
          If a warning is also displayed in a red box, then you should NOT try
          to delete the user account, else you will get referential integrity
          problems in your database, which can lead to unexpected behavior,
          such as bugs not appearing in bug lists anymore, or data displaying
          incorrectly. You have been warned!
        </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="impersonatingusers"
>3.2.2.5. Impersonating Users</A
></H4
><P
>&#13;        There may be times when an administrator would like to do something as
        another user.  The <B
CLASS="command"
>sudo</B
> feature may be used to do 
        this.
        </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          To use the sudo feature, you must be in the
          <EM
>bz_sudoers</EM
> group.  By default, all
          administrators are in this group.</P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        If you have access to this feature, you may start a session by
        going to the Edit Users page, Searching for a user and clicking on 
        their login.  You should see a link below their login name titled 
        "Impersonate this user".  Click on the link.  This will take you 
        to a page where you will see a description of the feature and 
        instructions for using it.  After reading the text, simply 
        enter the login of the user you would like to impersonate, provide 
        a short message explaining why you are doing this, and press the 
        button.</P
><P
>&#13;        As long as you are using this feature, everything you do will be done 
        as if you were logged in as the user you are impersonating.</P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          The user you are impersonating will not be told about what you are 
          doing.  If you do anything that results in mail being sent, that 
          mail will appear to be from the user you are impersonating.  You 
          should be extremely careful while using this feature.</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="classifications"
>3.3. Classifications</A
></H2
><P
>Classifications tend to be used in order to group several related
    products into one distinct entity.</P
><P
>The classifications layer is disabled by default; it can be turned
    on or off using the useclassification parameter,
    in the <EM
>Bug Fields</EM
> section of the edit parameters screen.</P
><P
>Access to the administration of classifications is controlled using
    the <EM
>editclassifications</EM
> system group, which defines
    a privilege for creating, destroying, and editing classifications.</P
><P
>When activated, classifications will introduce an additional
    step when filling bugs (dedicated to classification selection), and they
    will also appear in the advanced search form.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="products"
>3.4. Products</A
></H2
><P
>&#13;    <A
HREF="#gloss-product"
><I
CLASS="glossterm"
>&#13;    Products</I
></A
> typically represent real-world
    shipping products. Products can be given 
    <A
HREF="#classifications"
>Classifications</A
>. 
    For example, if a company makes computer games, 
    they could have a classification of "Games", and a separate
    product for each game. This company might also have a 
    <SPAN
CLASS="QUOTE"
>"Common"</SPAN
> product for units of technology used 
    in multiple games, and perhaps a few special products that
    represent items that are not actually shipping products 
    (for example, "Website", or "Administration").
    </P
><P
>&#13;    Many of Bugzilla's settings are configurable on a per-product
    basis. The number of <SPAN
CLASS="QUOTE"
>"votes"</SPAN
> available to 
    users is set per-product, as is the number of votes
    required to move a bug automatically from the UNCONFIRMED 
    status to the CONFIRMED status.
    </P
><P
>&#13;    When creating or editing products the following options are
    available: 
    </P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>Product</DT
><DD
><P
> 
            The name of the product
          </P
></DD
><DT
>Description</DT
><DD
><P
> 
            A brief description of the product
          </P
></DD
><DT
>Default milestone</DT
><DD
><P
> 
            Select the default milestone for this product.
          </P
></DD
><DT
>Closed for bug entry</DT
><DD
><P
> 
            Select this box to prevent new bugs from being
            entered against this product.
          </P
></DD
><DT
>Maximum votes per person</DT
><DD
><P
> 
            Maximum votes a user is allowed to give for this 
            product
          </P
></DD
><DT
>Maximum votes a person can put on a single bug</DT
><DD
><P
> 
            Maximum votes a user is allowed to give for this 
            product in a single bug
          </P
></DD
><DT
>Confirmation threshold</DT
><DD
><P
> 
            Number of votes needed to automatically remove any
            bug against this product from the UNCONFIRMED state
          </P
></DD
><DT
>Version</DT
><DD
><P
> 
            Specify which version of the product bugs will be
            entered against.
          </P
></DD
><DT
>Create chart datasets for this product</DT
><DD
><P
> 
            Select to make chart datasets available for this product.
          </P
></DD
></DL
></DIV
><P
>&#13;    When editing a product there is also a link to edit Group Access Controls,
    see <A
HREF="#product-group-controls"
>Section 3.4.4</A
>.
    </P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="create-product"
>3.4.1. Creating New Products</A
></H3
><P
>&#13;    To create a new product:
    </P
><P
></P
><OL
TYPE="1"
><LI
><P
> 
        Select <SPAN
CLASS="QUOTE"
>"Administration"</SPAN
> from the footer and then
        choose <SPAN
CLASS="QUOTE"
>"Products"</SPAN
> from the main administration page.
        </P
></LI
><LI
><P
>&#13;        Select the <SPAN
CLASS="QUOTE"
>"Add"</SPAN
> link in the bottom right.
        </P
></LI
><LI
><P
>&#13;        Enter the name of the product and a description. The
        Description field may contain HTML.
        </P
></LI
><LI
><P
>&#13;        When the product is created, Bugzilla will give a message
        stating that a component must be created before any bugs can
        be entered against the new product. Follow the link to create
        a new component. See <A
HREF="#components"
>Components</A
> for more
        information.
        </P
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="edit-products"
>3.4.2. Editing Products</A
></H3
><P
>&#13;      To edit an existing product, click the "Products" link from the 
      "Administration" page. If the 'useclassification' parameter is
      turned on, a table of existing classifications is displayed,
      including an "Unclassified" category. The table indicates how many products
      are in each classification. Click on the classification name to see its
      products. If the 'useclassification' parameter is not in use, the table 
      lists all products directly. The product table summarizes the information 
      about the product defined
      when the product was created. Click on the product name to edit these
      properties, and to access links to other product attributes such as the
      product's components, versions, milestones, and group access controls.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="comps-vers-miles-products"
>3.4.3. Adding or Editing Components, Versions and Target Milestones</A
></H3
><P
>&#13;          To edit existing, or add new, Components, Versions or Target Milestones 
          to a Product, select the "Edit Components", "Edit Versions" or "Edit
          Milestones" links from the "Edit Product" page. A table of existing 
          Components, Versions or Milestones is displayed. Click on a item name 
          to edit the properties of that item. Below the table is a link to add 
          a new Component, Version or Milestone. 
        </P
><P
>&#13;          For more information on components, see <A
HREF="#components"
>Components</A
>.
        </P
><P
>&#13;          For more information on versions, see <A
HREF="#versions"
>Section 3.6</A
>.
        </P
><P
>&#13;          For more information on milestones, see <A
HREF="#milestones"
>Section 3.7</A
>.
        </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="product-group-controls"
>3.4.4. Assigning Group Controls to Products</A
></H3
><P
> 
        On the <SPAN
CLASS="QUOTE"
>"Edit Product"</SPAN
> page, there is a link called 
        <SPAN
CLASS="QUOTE"
>"Edit Group Access Controls"</SPAN
>. The settings on this page 
        control the relationship of the groups to the product being edited.
        </P
><P
>&#13;        Group Access Controls are an important aspect of using groups for 
        isolating products and restricting access to bugs filed against those
        products. For more information on groups, including how to create, edit
        add users to, and alter permission of, see <A
HREF="#groups"
>Section 3.15</A
>.
        </P
><P
>&#13;        After selecting the "Edit Group Access Controls" link from the "Edit
        Product" page, a table containing all user-defined groups for this 
        Bugzilla installation is displayed. The system groups that are created
        when Bugzilla is installed are not applicable to Group Access Controls.
        Below is description of what each of these fields means.
        </P
><P
>&#13;        Groups may be applicable (e.g bugs in this product can be associated
        with this group) , default (e.g. bugs in this product are in this group
        by default), and mandatory (e.g. bugs in this product must be associated
        with this group) for each product. Groups can also control access 
        to bugs for a given product, or be used to make bugs for a product 
        totally read-only unless the group restrictions are met. The best way to
        understand these relationships is by example. See 
        <A
HREF="#group-control-examples"
>Section 3.4.4.1</A
> for examples of 
        product and group relationships.
        </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            Products and Groups are not limited to a one-to-one relationship. 
            Multiple groups can be associated with the same product, and groups
            can be associated with more than one product. 
          </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        If any group has <EM
>Entry</EM
> selected, then the 
        product will restrict bug entry to only those users 
        who are members of <EM
>all</EM
> the groups with 
        <EM
>Entry</EM
> selected.
        </P
><P
>&#13;        If any group has <EM
>Canedit</EM
> selected, 
        then the product will be read-only for any users 
        who are not members of <EM
>all</EM
> of the groups with
        <EM
>Canedit</EM
> selected. <EM
>Only</EM
> users who 
        are members of all the <EM
>Canedit</EM
> groups 
        will be able to edit bugs for this product. This is an additional 
        restriction that enables finer-grained control over products rather 
        than just all-or-nothing access levels.
        </P
><P
>&#13;        The following settings let you 
        choose privileges on a <EM
>per-product basis</EM
>.
        This is a convenient way to give privileges to 
        some users for some products only, without having 
        to give them global privileges which would affect 
        all products.
        </P
><P
>&#13;        Any group having <EM
>editcomponents</EM
> 
        selected  allows users who are in this group to edit all 
        aspects of this product, including components, milestones 
        and versions.
        </P
><P
>&#13;        Any group having <EM
>canconfirm</EM
> selected 
        allows users who are in this group to confirm bugs 
        in this product.
        </P
><P
>&#13;        Any group having <EM
>editbugs</EM
> selected allows 
        users who are in this group to edit all fields of 
        bugs in this product.
        </P
><P
>&#13;        The <EM
>MemberControl</EM
> and 
        <EM
>OtherControl</EM
> are used in tandem to determine which 
        bugs will be placed in this group. The only allowable combinations of
        these two parameters are listed in a table on the "Edit Group Access Controls"
        page. Consult this table for details on how these fields can be used.
        Examples of different uses are described below.
        </P
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="group-control-examples"
>3.4.4.1. Common Applications of Group Controls</A
></H4
><P
>&#13;        The use of groups is best explained by providing examples that illustrate
        configurations for common use cases. The examples follow a common syntax:
        <EM
>Group: Entry, MemberControl, OtherControl, CanEdit,
        EditComponents, CanConfirm, EditBugs</EM
>. Where "Group" is the name
        of the group being edited for this product. The other fields all
        correspond to the table on the "Edit Group Access Controls" page. If any
        of these options are not listed, it means they are not checked.      
      </P
><P
>&#13;            Basic Product/Group Restriction
          </P
><P
>&#13;          Suppose there is a product called "Bar". The 
          "Bar" product can only have bugs entered against it by users in the
          group "Foo". Additionally, bugs filed against product "Bar" must stay
          restricted to users to "Foo" at all times. Furthermore, only members
          of group "Foo" can edit bugs filed against product "Bar", even if other
          users could see the bug. This arrangement would achieved by the
          following:
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;Product Bar: 
foo: ENTRY, MANDATORY/MANDATORY, CANEDIT
        </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;          Perhaps such strict restrictions are not needed for product "Bar". A 
          more lenient way to configure product "Bar" and group "Foo" would be:
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;Product Bar: 
foo: ENTRY, SHOWN/SHOWN, EDITCOMPONENTS, CANCONFIRM, EDITBUGS
        </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;          The above indicates that for product "Bar", members of group "Foo" can
          enter bugs. Any one with permission to edit a bug against product "Bar"
          can put the bug
          in group "Foo", even if they themselves are not in "Foo". Anyone in group
          "Foo" can edit all aspects of the components of product "Bar", can confirm
          bugs against product "Bar", and can edit all fields of any bug against
          product "Bar".
        </P
><P
>&#13;            General User Access With Security Group
          </P
><P
>&#13;               To permit any user to file bugs against "Product A",
               and to permit any user to submit those bugs into a
               group called "Security":  
            </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> 
Product A:
security: SHOWN/SHOWN
      </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;            General User Access With A Security Product
          </P
><P
>&#13;            To permit any user to file bugs against product called "Security"
            while keeping those bugs from becoming visible to anyone
            outside the group "SecurityWorkers" (unless a member of the
            "SecurityWorkers" group removes that restriction):
          </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> 
Product Security:
securityworkers: DEFAULT/MANDATORY
          </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;            Product Isolation With a Common Group
          </P
><P
>&#13;            To permit users of "Product A" to access the bugs for
            "Product A", users of "Product B" to access the bugs for 
            "Product B", and support staff, who are members of the "Support 
            Group" to access both, three groups are needed:
          </P
><P
></P
><OL
TYPE="1"
><LI
><P
>Support Group: Contains members of the support staff.</P
></LI
><LI
><P
>AccessA Group: Contains users of product A and the Support group.</P
></LI
><LI
><P
>AccessB Group: Contains users of product B and the Support group.</P
></LI
></OL
><P
>&#13;            Once these three groups are defined, the product group controls
            can be set to:
          </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;Product A:
AccessA: ENTRY, MANDATORY/MANDATORY
Product B:
AccessB: ENTRY, MANDATORY/MANDATORY
        </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;         Perhaps the "Support Group" wants more control. For example, 
         the "Support Group"  could be permitted to make bugs inaccessible to 
         users of both groups "AccessA" and "AccessB". 
         Then, the "Support Group" could be permitted to publish
         bugs relevant to all users in a third product (let's call it 
         "Product Common") that is read-only
         to anyone outside the "Support Group". In this way the "Support Group" 
         could control bugs that should be seen by both groups. 
         That configuration would be:
        </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;Product A:
AccessA: ENTRY, MANDATORY/MANDATORY
Support: SHOWN/NA
Product B:
AccessB: ENTRY, MANDATORY/MANDATORY
Support: SHOWN/NA
Product Common:
Support: ENTRY, DEFAULT/MANDATORY, CANEDIT
      </PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13;            Make a Product Read Only
          </P
><P
>&#13;            Sometimes a product is retired and should no longer have
            new bugs filed against it (for example, an older version of a software
            product that is no longer supported). A product can be made read-only
            by creating a group called "readonly" and adding products to the
            group as needed:
          </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;Product A:
ReadOnly: ENTRY, NA/NA, CANEDIT
         </PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            For more information on Groups outside of how they relate to products
            see <A
HREF="#groups"
>Section 3.15</A
>.
          </P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="components"
>3.5. Components</A
></H2
><P
>Components are subsections of a Product. E.g. the computer game 
    you are designing may have a "UI"
    component, an "API" component, a "Sound System" component, and a
    "Plugins" component, each overseen by a different programmer. It
    often makes sense to divide Components in Bugzilla according to the
    natural divisions of responsibility within your Product or
    company.</P
><P
>&#13;    Each component has a default assignee and (if you turned it on in the parameters),
    a QA Contact. The default assignee should be the primary person who fixes bugs in
    that component. The QA Contact should be the person who will ensure
    these bugs are completely fixed. The Assignee, QA Contact, and Reporter
    will get email when new bugs are created in this Component and when
    these bugs change. Default Assignee and Default QA Contact fields only
    dictate the 
    <EM
>default assignments</EM
>; 
    these can be changed on bug submission, or at any later point in
    a bug's life.</P
><P
>To create a new Component:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>Select the <SPAN
CLASS="QUOTE"
>"Edit components"</SPAN
> link 
        from the <SPAN
CLASS="QUOTE"
>"Edit product"</SPAN
> page</P
></LI
><LI
><P
>Select the <SPAN
CLASS="QUOTE"
>"Add"</SPAN
> link in the bottom right.</P
></LI
><LI
><P
>Fill out the <SPAN
CLASS="QUOTE"
>"Component"</SPAN
> field, a 
        short <SPAN
CLASS="QUOTE"
>"Description"</SPAN
>, the 
        <SPAN
CLASS="QUOTE"
>"Default Assignee"</SPAN
>, <SPAN
CLASS="QUOTE"
>"Default CC List"</SPAN
> 
        and <SPAN
CLASS="QUOTE"
>"Default QA Contact"</SPAN
> (if enabled). 
        The <SPAN
CLASS="QUOTE"
>"Component Description"</SPAN
> field may contain a 
        limited subset of HTML tags. The <SPAN
CLASS="QUOTE"
>"Default Assignee"</SPAN
> 
        field must be a login name already existing in the Bugzilla database. 
        </P
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="versions"
>3.6. Versions</A
></H2
><P
>Versions are the revisions of the product, such as "Flinders
    3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select
    field; the usual practice is to select the earliest version known to have
    the bug.
    </P
><P
>To create and edit Versions:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>From the "Edit product" screen, select "Edit Versions"</P
></LI
><LI
><P
>You will notice that the product already has the default
        version "undefined". Click the "Add" link in the bottom right.</P
></LI
><LI
><P
>Enter the name of the Version. This field takes text only. 
        Then click the "Add" button.</P
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="milestones"
>3.7. Milestones</A
></H2
><P
>Milestones are "targets" that you plan to get a bug fixed by. For
    example, you have a bug that you plan to fix for your 3.0 release, it
    would be assigned the milestone of 3.0.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Milestone options will only appear for a Product if you turned
      on the "usetargetmilestone" parameter in the "Bug Fields" tab of the
      "Parameters" page.
      </P
></TD
></TR
></TABLE
></DIV
><P
>To create new Milestones, and set Default Milestones:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>Select "Edit milestones" from the "Edit product" page.</P
></LI
><LI
><P
>Select "Add" in the bottom right corner.</P
></LI
><LI
><P
>Enter the name of the Milestone in the "Milestone" field. You
        can optionally set the "sortkey", which is a positive or negative
        number (-32768 to 32767) that defines where in the list this particular
        milestone appears. This is because milestones often do not 
        occur in alphanumeric order For example, "Future" might be
        after "Release 1.2". Select "Add".</P
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="flags-overview"
>3.8. Flags</A
></H2
><P
>&#13;     Flags are a way to attach a specific status to a bug or attachment, 
     either <SPAN
CLASS="QUOTE"
>"+"</SPAN
> or <SPAN
CLASS="QUOTE"
>"-"</SPAN
>. The meaning of these symbols depends on the text
     the flag itself, but contextually they could mean pass/fail, 
     accept/reject, approved/denied, or even a simple yes/no. If your site
     allows requestable flags, then users may set a flag to <SPAN
CLASS="QUOTE"
>"?"</SPAN
> as a 
     request to another user that they look at the bug/attachment, and set
     the flag to its correct status.
   </P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="flags-simpleexample"
>3.8.1. A Simple Example</A
></H3
><P
>&#13;       A developer might want to ask their manager, 
       <SPAN
CLASS="QUOTE"
>"Should we fix this bug before we release version 2.0?"</SPAN
> 
       They might want to do this for a <EM
>lot</EM
> of bugs,
       so it would be nice to streamline the process...
     </P
><P
>&#13;       In Bugzilla, it would work this way:
       <P
></P
><OL
TYPE="1"
><LI
><P
>&#13;             The Bugzilla administrator creates a flag type called 
             <SPAN
CLASS="QUOTE"
>"blocking2.0"</SPAN
> that shows up on all bugs in 
             your product.
           </P
><P
>&#13;             It shows up on the <SPAN
CLASS="QUOTE"
>"Show Bug"</SPAN
> screen
             as the text <SPAN
CLASS="QUOTE"
>"blocking2.0"</SPAN
> with a drop-down box next
             to it. The drop-down box contains four values: an empty space,
             <SPAN
CLASS="QUOTE"
>"?"</SPAN
>, <SPAN
CLASS="QUOTE"
>"-"</SPAN
>, and <SPAN
CLASS="QUOTE"
>"+"</SPAN
>.
           </P
></LI
><LI
><P
>The developer sets the flag to <SPAN
CLASS="QUOTE"
>"?"</SPAN
>.</P
></LI
><LI
><P
>&#13;             The manager sees the <SAMP
CLASS="computeroutput"
>blocking2.0</SAMP
>
             flag with a <SPAN
CLASS="QUOTE"
>"?"</SPAN
> value.
           </P
></LI
><LI
><P
>&#13;             If the manager thinks the feature should go into the product
             before version 2.0 can be released, he sets the flag to 
             <SPAN
CLASS="QUOTE"
>"+"</SPAN
>. Otherwise, he sets it to <SPAN
CLASS="QUOTE"
>"-"</SPAN
>.
           </P
></LI
><LI
><P
>&#13;             Now, every Bugzilla user who looks at the bug knows whether or 
             not the bug needs to be fixed before release of version 2.0.
           </P
></LI
></OL
>
     </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="flags-about"
>3.8.2. About Flags</A
></H3
><DIV
CLASS="section"
><H4
CLASS="section"
><A
NAME="flag-values"
>3.8.2.1. Values</A
></H4
><P
>&#13;         Flags can have three values:
         <P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><SAMP
CLASS="computeroutput"
>?</SAMP
></DT
><DD
><P
>&#13;               A user is requesting that a status be set. (Think of it as 'A question is being asked'.)
             </P
></DD
><DT
><SAMP
CLASS="computeroutput"
>-</SAMP
></DT
><DD
><P
>&#13;               The status has been set negatively. (The question has been answered <SPAN
CLASS="QUOTE"
>"no"</SPAN
>.)
             </P
></DD
><DT
><SAMP
CLASS="computeroutput"
>+</SAMP
></DT
><DD
><P
>&#13;               The status has been set positively.
               (The question has been answered <SPAN
CLASS="QUOTE"
>"yes"</SPAN
>.)
             </P
></DD
></DL
></DIV
>
       </P
><P
>&#13;         Actually, there's a fourth value a flag can have -- 
         <SPAN
CLASS="QUOTE"
>"unset"</SPAN
> -- which shows up as a blank space. This 
         just means that nobody has expressed an opinion (or asked
         someone else to express an opinion) about this bug or attachment.
       </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="flag-askto"
>3.8.3. Using flag requests</A
></H3
><P
>&#13;       If a flag has been defined as 'requestable', and a user has enough privileges
       to request it (see below), the user can set the flag's status to <SPAN
CLASS="QUOTE"
>"?"</SPAN
>.
       This status indicates that someone (a.k.a. <SPAN
CLASS="QUOTE"
>"the requester"</SPAN
>) is asking
       someone else to set the flag to either <SPAN
CLASS="QUOTE"
>"+"</SPAN
> or <SPAN
CLASS="QUOTE"
>"-"</SPAN
>.
     </P
><P
>&#13;       If a flag has been defined as 'specifically requestable', 
       a text box will appear next to the flag into which the requester may
       enter a Bugzilla username. That named person (a.k.a. <SPAN
CLASS="QUOTE"
>"the requestee"</SPAN
>)
       will receive an email notifying them of the request, and pointing them
       to the bug/attachment in question.
     </P
><P
>&#13;       If a flag has <EM
>not</EM
> been defined as 'specifically requestable',
       then no such text-box will appear. A request to set this flag cannot be made of
       any specific individual, but must be asked <SPAN
CLASS="QUOTE"
>"to the wind"</SPAN
>.
       A requester may <SPAN
CLASS="QUOTE"
>"ask the wind"</SPAN
> on any flag simply by leaving the text-box blank.
     </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="flag-types"
>3.8.4. Two Types of Flags</A
></H3
><P
>&#13;       Flags can go in two places: on an attachment, or on a bug.
     </P
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="flag-type-attachment"
>3.8.4.1. Attachment Flags</A
></H4
><P
>&#13;         Attachment flags are used to ask a question about a specific 
         attachment on a bug.
       </P
><P
>&#13;         Many Bugzilla installations use this to 
         request that one developer <SPAN
CLASS="QUOTE"
>"review"</SPAN
> another 
         developer's code before they check it in. They attach the code to
         a bug report, and then set a flag on that attachment called
         <SPAN
CLASS="QUOTE"
>"review"</SPAN
> to 
         <SAMP
CLASS="computeroutput"
>review?boss@domain.com</SAMP
>.
         boss@domain.com is then notified by email that
         he has to check out that attachment and approve it or deny it.
       </P
><P
>&#13;         For a Bugzilla user, attachment flags show up in three places:
         <P
></P
><OL
TYPE="1"
><LI
><P
>&#13;               On the list of attachments in the <SPAN
CLASS="QUOTE"
>"Show Bug"</SPAN
>
               screen, you can see the current state of any flags that
               have been set to ?, +, or -. You can see who asked about 
               the flag (the requester), and who is being asked (the 
               requestee).
             </P
></LI
><LI
><P
>&#13;              When you <SPAN
CLASS="QUOTE"
>"Edit"</SPAN
> an attachment, you can 
              see any settable flag, along with any flags that have 
              already been set. This <SPAN
CLASS="QUOTE"
>"Edit Attachment"</SPAN
> 
              screen is where you set flags to ?, -, +, or unset them.
             </P
></LI
><LI
><P
>&#13;               Requests are listed in the <SPAN
CLASS="QUOTE"
>"Request Queue"</SPAN
>, which
               is accessible from the <SPAN
CLASS="QUOTE"
>"My Requests"</SPAN
> link (if you are
               logged in) or <SPAN
CLASS="QUOTE"
>"Requests"</SPAN
> link (if you are logged out)
               visible in the footer of all pages.
             </P
></LI
></OL
>
       </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="flag-type-bug"
>3.8.4.2. Bug Flags</A
></H4
><P
>&#13;         Bug flags are used to set a status on the bug itself. You can 
         see Bug Flags in the <SPAN
CLASS="QUOTE"
>"Show Bug"</SPAN
> and <SPAN
CLASS="QUOTE"
>"Requests"</SPAN
>
         screens, as described above.
       </P
><P
>&#13;         Only users with enough privileges (see below) may set flags on bugs.
         This doesn't necessarily include the assignee, reporter, or users with the
         <SAMP
CLASS="computeroutput"
>editbugs</SAMP
> permission.
       </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="flags-admin"
>3.8.5. Administering Flags</A
></H3
><P
>&#13;       If you have the <SPAN
CLASS="QUOTE"
>"editcomponents"</SPAN
> permission, you can
       edit Flag Types from the main administration page. Clicking the
       <SPAN
CLASS="QUOTE"
>"Flags"</SPAN
> link will bring you to the <SPAN
CLASS="QUOTE"
>"Administer
       Flag Types"</SPAN
> page. Here, you can select whether you want 
       to create (or edit) a Bug flag, or an Attachment flag.
     </P
><P
>&#13;       No matter which you choose, the interface is the same, so we'll 
       just go over it once.
     </P
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="flags-edit"
>3.8.5.1. Editing a Flag</A
></H4
><P
>&#13;         To edit a flag's properties, just click the flag's name.
         That will take you to the same
         form as described below (<A
HREF="#flags-create"
>Section 3.8.5.2</A
>).
       </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="flags-create"
>3.8.5.2. Creating a Flag</A
></H4
><P
>&#13;          When you click on the <SPAN
CLASS="QUOTE"
>"Create a Flag Type for..."</SPAN
>
          link, you will be presented with a form. Here is what the fields in 
          the form mean:
        </P
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="flags-create-field-name"
>3.8.5.2.1. Name</A
></H5
><P
>&#13;            This is the name of the flag. This will be displayed 
            to Bugzilla users who are looking at or setting the flag. 
            The name may contain any valid Unicode characters except commas
            and spaces.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="flags-create-field-description"
>3.8.5.2.2. Description</A
></H5
><P
>&#13;            The description describes the flag in more detail. It is visible
            in a tooltip when hovering over a flag either in the <SPAN
CLASS="QUOTE"
>"Show Bug"</SPAN
>
            or <SPAN
CLASS="QUOTE"
>"Edit Attachment"</SPAN
> pages. This field can be as
            long as you like, and can contain any character you want.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="flags-create-field-category"
>3.8.5.2.3. Category</A
></H5
><P
>&#13;            Default behaviour for a newly-created flag is to appear on
            products and all components, which is why <SPAN
CLASS="QUOTE"
>"__Any__:__Any__"</SPAN
>
            is already entered in the <SPAN
CLASS="QUOTE"
>"Inclusions"</SPAN
> box.
            If this is not your desired behaviour, you must either set some
            exclusions (for products on which you don't want the flag to appear),
            or you must remove <SPAN
CLASS="QUOTE"
>"__Any__:__Any__"</SPAN
> from the Inclusions box
            and define products/components specifically for this flag.
          </P
><P
>&#13;            To create an Inclusion, select a Product from the top drop-down box.
            You may also select a specific component from the bottom drop-down box.
            (Setting <SPAN
CLASS="QUOTE"
>"__Any__"</SPAN
> for Product translates to, 
            <SPAN
CLASS="QUOTE"
>"all the products in this Bugzilla"</SPAN
>.
            Selecting  <SPAN
CLASS="QUOTE"
>"__Any__"</SPAN
> in the Component field means
            <SPAN
CLASS="QUOTE"
>"all components in the selected product."</SPAN
>) 
            Selections made, press <SPAN
CLASS="QUOTE"
>"Include"</SPAN
>, and your
            Product/Component pairing will show up in the <SPAN
CLASS="QUOTE"
>"Inclusions"</SPAN
> box on the right.
          </P
><P
>&#13;            To create an Exclusion, the process is the same; select a Product from the
            top drop-down box, select a specific component if you want one, and press
            <SPAN
CLASS="QUOTE"
>"Exclude"</SPAN
>. The Product/Component pairing will show up in the 
            <SPAN
CLASS="QUOTE"
>"Exclusions"</SPAN
> box on the right.
          </P
><P
>&#13;            This flag <EM
>will</EM
> and <EM
>can</EM
> be set for any
            products/components that appearing in the <SPAN
CLASS="QUOTE"
>"Inclusions"</SPAN
> box 
            (or which fall under the appropriate <SPAN
CLASS="QUOTE"
>"__Any__"</SPAN
>). 
            This flag <EM
>will not</EM
> appear (and therefore cannot be set) on
            any products appearing in the <SPAN
CLASS="QUOTE"
>"Exclusions"</SPAN
> box.
            <EM
> IMPORTANT: Exclusions override inclusions.</EM
>
          </P
><P
>&#13;            You may select a Product without selecting a specific Component,
            but you can't select a Component without a Product, or to select a
            Component that does not belong to the named Product. If you do so,
            Bugzilla will display an error message, even if all your products
            have a component by that name.
          </P
><P
><EM
>Example:</EM
> Let's say you have a product called 
            <SPAN
CLASS="QUOTE"
>"Jet Plane"</SPAN
> that has thousands of components. You want
            to be able to ask if a problem should be fixed in the next model of 
            plane you release. We'll call the flag <SPAN
CLASS="QUOTE"
>"fixInNext"</SPAN
>.
            But, there's one component in <SPAN
CLASS="QUOTE"
>"Jet Plane,"</SPAN
> 
            called <SPAN
CLASS="QUOTE"
>"Pilot."</SPAN
> It doesn't make sense to release a 
            new pilot, so you don't want to have the flag show up in that component.
            So, you include <SPAN
CLASS="QUOTE"
>"Jet Plane:__Any__"</SPAN
> and you exclude 
            <SPAN
CLASS="QUOTE"
>"Jet Plane:Pilot"</SPAN
>.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="flags-create-field-sortkey"
>3.8.5.2.4. Sort Key</A
></H5
><P
>&#13;            Flags normally show up in alphabetical order. If you want them to 
            show up in a different order, you can use this key set the order on each flag. 
            Flags with a lower sort key will appear before flags with a higher
            sort key. Flags that have the same sort key will be sorted alphabetically,
            but they will still be after flags with a lower sort key, and before flags
            with a higher sort key.
          </P
><P
>&#13;            <EM
>Example:</EM
> I have AFlag (Sort Key 100), BFlag (Sort Key 10), 
            CFlag (Sort Key 10), and DFlag (Sort Key 1). These show up in
            the order: DFlag, BFlag, CFlag, AFlag.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="flags-create-field-active"
>3.8.5.2.5. Active</A
></H5
><P
>&#13;            Sometimes, you might want to keep old flag information in the 
            Bugzilla database, but stop users from setting any new flags of this type.
            To do this, uncheck <SPAN
CLASS="QUOTE"
>"active"</SPAN
>. Deactivated
            flags will still show up in the UI if they are ?, +, or -, but they
            may only be cleared (unset), and cannot be changed to a new value.
            Once a deactivated flag is cleared, it will completely disappear from a 
            bug/attachment, and cannot be set again.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="flags-create-field-requestable"
>3.8.5.2.6. Requestable</A
></H5
><P
>&#13;            New flags are, by default, <SPAN
CLASS="QUOTE"
>"requestable"</SPAN
>, meaning that they
            offer users the <SPAN
CLASS="QUOTE"
>"?"</SPAN
> option, as well as <SPAN
CLASS="QUOTE"
>"+"</SPAN
>
            and <SPAN
CLASS="QUOTE"
>"-"</SPAN
>.
            To remove the ? option, uncheck <SPAN
CLASS="QUOTE"
>"requestable"</SPAN
>.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="flags-create-field-specific"
>3.8.5.2.7. Specifically Requestable</A
></H5
><P
>&#13;            By default this box is checked for new flags, meaning that users may make
            flag requests of specific individuals. Unchecking this box will remove the
            text box next to a flag; if it is still requestable, then requests may
            only be made <SPAN
CLASS="QUOTE"
>"to the wind."</SPAN
> Removing this after specific
            requests have been made will not remove those requests; that data will
            stay in the database (though it will no longer appear to the user).
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="flags-create-field-multiplicable"
>3.8.5.2.8. Multiplicable</A
></H5
><P
>&#13;            Any flag with <SPAN
CLASS="QUOTE"
>"Multiplicable"</SPAN
> set (default for new flags is 'on')
            may be set more than once. After being set once, an unset flag
            of the same type will appear below it with <SPAN
CLASS="QUOTE"
>"addl."</SPAN
> (short for 
            <SPAN
CLASS="QUOTE"
>"additional"</SPAN
>) before the name. There is no limit to the number of
            times a Multiplicable flags may be set on the same bug/attachment.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="flags-create-field-cclist"
>3.8.5.2.9. CC List</A
></H5
><P
>&#13;            If you want certain users to be notified every time this flag is 
            set to ?, -, +, or unset, add them here. This is a comma-separated 
            list of email addresses that need not be restricted to Bugzilla usernames.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="flags-create-grant-group"
>3.8.5.2.10. Grant Group</A
></H5
><P
>&#13;            When this field is set to some given group, only users in the group
            can set the flag to <SPAN
CLASS="QUOTE"
>"+"</SPAN
> and <SPAN
CLASS="QUOTE"
>"-"</SPAN
>. This
            field does not affect who can request or cancel the flag. For that,
            see the <SPAN
CLASS="QUOTE"
>"Request Group"</SPAN
> field below. If this field
            is left blank, all users can set or delete this flag. This field is
            useful for restricting which users can approve or reject requests.
          </P
></DIV
><DIV
CLASS="section"
><HR><H5
CLASS="section"
><A
NAME="flags-create-request-group"
>3.8.5.2.11. Request Group</A
></H5
><P
>&#13;            When this field is set to some given group, only users in the group
            can request or cancel this flag. Note that this field has no effect
            if the <SPAN
CLASS="QUOTE"
>"grant group"</SPAN
> field is empty. You can set the
            value of this field to a different group, but both fields have to be
            set to a group for this field to have an effect.
          </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="flags-delete"
>3.8.5.3. Deleting a Flag</A
></H4
><P
>&#13;          When you are at the <SPAN
CLASS="QUOTE"
>"Administer Flag Types"</SPAN
> screen,
          you will be presented with a list of Bug flags and a list of Attachment
          Flags.
        </P
><P
>&#13;          To delete a flag, click on the <SPAN
CLASS="QUOTE"
>"Delete"</SPAN
> link next to
          the flag description.
        </P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            Once you delete a flag, it is <EM
>gone</EM
> from
            your Bugzilla. All the data for that flag will be deleted.
            Everywhere that flag was set, it will disappear,
            and you cannot get that data back. If you want to keep flag data,
            but don't want anybody to set any new flags or change current flags,
            unset <SPAN
CLASS="QUOTE"
>"active"</SPAN
> in the flag Edit form.
          </P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="keywords"
>3.9. Keywords</A
></H2
><P
>&#13;    The administrator can define keywords which can be used to tag and
    categorise bugs. For example, the keyword "regression" is commonly used.
    A company might have a policy stating all regressions
    must be fixed by the next release - this keyword can make tracking those
    bugs much easier.
    </P
><P
>&#13;    Keywords are global, rather than per-product. If the administrator changes
    a keyword currently applied to any bugs, the keyword cache must be rebuilt
    using the <A
HREF="#sanitycheck"
>Section 3.16</A
> script. Currently keywords can not
    be marked obsolete to prevent future usage.
    </P
><P
>&#13;    Keywords can be created, edited or deleted by clicking the "Keywords"
    link in the admin page. There are two fields for each keyword - the keyword
    itself and a brief description. Once created, keywords can be selected
    and applied to individual bugs in that bug's "Details" section.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="custom-fields"
>3.10. Custom Fields</A
></H2
><P
>&#13;      The release of Bugzilla 3.0 added the ability to create Custom Fields. 
      Custom Fields are treated like any other field - they can be set in bugs
      and used for search queries. Administrators should keep in mind that
      adding too many fields can make the user interface more complicated and
      harder to use. Custom Fields should be added only when necessary and with 
      careful consideration.
    </P
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        Before adding a Custom Field, make sure that Bugzilla can not already
        do the desired behavior. Many Bugzilla options are not enabled by 
        default, and many times Administrators find that simply enabling
        certain options that already exist is sufficient. 
      </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;      Administrators can manage Custom Fields using the
      <SPAN
CLASS="QUOTE"
>"Custom Fields"</SPAN
> link on the Administration page. The Custom
      Fields administration page displays a list of Custom Fields, if any exist,
      and a link to "Add a new custom field". 
    </P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="add-custom-fields"
>3.10.1. Adding Custom Fields</A
></H3
><P
>&#13;        To add a new Custom Field, click the "Add a new custom field" link. This
        page displays several options for the new field, described below.
      </P
><P
>&#13;        The following attributes must be set for each new custom field:
        <P
></P
><UL
><LI
><P
>&#13;              <EM
>Name:</EM
>
              The name of the field in the database, used internally. This name 
              MUST begin with <SPAN
CLASS="QUOTE"
>"cf_"</SPAN
> to prevent confusion with 
              standard fields. If this string is omitted, it will
              be automatically added to the name entered. 
            </P
></LI
><LI
><P
>&#13;              <EM
>Description:</EM
>
              A brief string which is used as the label for this Custom Field.
              That is the string that users will see, and should be
              short and explicit.
            </P
></LI
><LI
><P
>&#13;              <EM
>Type:</EM
>
              The type of field to create. There are
              several types available:
               <P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;                   Large Text Box: A multiple line box for entering free text.
                 </TD
></TR
><TR
><TD
>&#13;                   Free Text: A single line box for entering free text.
                 </TD
></TR
><TR
><TD
>&#13;                   Multiple-Selection Box: A list box where multiple options 
                   can be selected. After creating this field, it must be edited
                   to add the selection options. See 
                   <A
HREF="#edit-values-list"
>Section 3.11.1</A
> for information about 
                   editing legal values.
                 </TD
></TR
><TR
><TD
>&#13;                   Drop Down: A list box where only one option can be selected.
                   After creating this field, it must be edited to add the
                   selection options. See 
                   <A
HREF="#edit-values-list"
>Section 3.11.1</A
> for information about 
                   editing legal values.
                 </TD
></TR
><TR
><TD
>&#13;                   Date/Time: A date field. This field appears with a 
                   calendar widget for choosing the date.
                 </TD
></TR
></TBODY
></TABLE
><P
></P
>
            </P
></LI
><LI
><P
>&#13;              <EM
>Sortkey:</EM
>
              Integer that determines in which order Custom Fields are
              displayed in the User Interface, especially when viewing a bug. 
              Fields with lower values are displayed first.
            </P
></LI
><LI
><P
>&#13;              <EM
>Can be set on bug creation:</EM
>
              Boolean that determines whether this field can be set on
              bug creation. If not selected, then a bug must be created 
              before this field can be set. See <A
HREF="#bugreports"
>Section 5.6</A
> 
              for information about filing bugs.
            </P
></LI
><LI
><P
>&#13;              <EM
>Displayed in bugmail for new bugs:</EM
>
              Boolean that determines whether the value set on this field
              should appear in bugmail when the bug is filed. This attribute
              has no effect if the field cannot be set on bug creation.
            </P
></LI
><LI
><P
>&#13;              <EM
>Is obsolete:</EM
>
              Boolean that determines whether this field should
              be displayed at all. Obsolete Custom Fields are hidden.
            </P
></LI
></UL
>
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="edit-custom-fields"
>3.10.2. Editing Custom Fields</A
></H3
><P
>&#13;        As soon as a Custom Field is created, its name and type cannot be
        changed. If this field is a drop down menu, its legal values can
        be set as described in <A
HREF="#edit-values-list"
>Section 3.11.1</A
>. All
        other attributes can be edited as described above.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="delete-custom-fields"
>3.10.3. Deleting Custom Fields</A
></H3
><P
>&#13;        Only custom fields which are marked as obsolete, and which never
        have been used, can be deleted completely (else the integrity
        of the bug history would be compromised). For custom fields marked
        as obsolete, a "Delete" link will appear in the <SPAN
CLASS="QUOTE"
>"Action"</SPAN
>
        column. If the custom field has been used in the past, the deletion
        will be rejected. But marking the field as obsolete is sufficient
        to hide it from the user interface entirely.
      </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="edit-values"
>3.11. Legal Values</A
></H2
><P
>&#13;      Since Bugzilla 2.20 RC1, legal values for Operating Systems, platforms,
      bug priorities and severities can be edited from the User Interface
      directly. This means that it is no longer required to manually edit
      <TT
CLASS="filename"
>localconfig</TT
>. Starting with Bugzilla 2.23.3, 
      the list of valid resolutions can be customized from the same interface.
      Since Bugzilla 3.1.1 the list of valid bug statuses can be customized
      as well.
    </P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="edit-values-list"
>3.11.1. Viewing/Editing legal values</A
></H3
><P
>&#13;        Editing legal values requires <SPAN
CLASS="QUOTE"
>"admin"</SPAN
> privileges.
        Select "Legal Values" from the Administration page. A list of all
        fields, both system fields and Custom Fields, for which legal values
        can be edited appears. Click a field name to edit its legal values.
      </P
><P
>&#13;        There is no limit to how many values a field can have, but each value 
        must be unique to that field. The sortkey is important to display these
        values in the desired order.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="edit-values-delete"
>3.11.2. Deleting legal values</A
></H3
><P
>&#13;        Legal values from Custom Fields can be deleted, but only if the 
        following two conditions are respected:
      </P
><P
></P
><OL
TYPE="1"
><LI
><P
>The value is not used by default for the field.</P
></LI
><LI
><P
>No bug is currently using this value.</P
></LI
></OL
><P
>&#13;        If any of these conditions is not respected, the value cannot be deleted.
	The only way to delete these values is to reassign bugs to another value
	and to set another value as default for the field.
      </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="bug_status_workflow"
>3.12. Bug Status Workflow</A
></H2
><P
>&#13;      The bug status workflow is no longer hardcoded but can be freely customized
      from the web interface. Only one bug status cannot be renamed nor deleted,
      UNCONFIRMED, but the workflow involving it is free. The configuration
      page displays all existing bug statuses twice, first on the left for bug
      statuses we come from and on the top for bug statuses we move to.
      If the checkbox is checked, then the transition between the two bug statuses
      is legal, else it's forbidden independently of your privileges. The bug status
      used for the "duplicate_or_move_bug_status" parameter must be part of the
      workflow as that is the bug status which will be used when duplicating or
      moving a bug, so it must be available from each bug status.
    </P
><P
>&#13;      When the workflow is set, the "View Current Triggers" link below the table
      lets you set which transitions require a comment from the user.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="voting"
>3.13. Voting</A
></H2
><P
>Voting allows users to be given a pot of votes which they can allocate
    to bugs, to indicate that they'd like them fixed. 
    This allows developers to gauge
    user need for a particular enhancement or bugfix. By allowing bugs with
    a certain number of votes to automatically move from "UNCONFIRMED" to
    "CONFIRMED", users of the bug system can help high-priority bugs garner
    attention so they don't sit for a long time awaiting triage.</P
><P
>To modify Voting settings:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>Navigate to the "Edit product" screen for the Product you
        wish to modify</P
></LI
><LI
><P
><EM
>Maximum Votes per person</EM
>:
        Setting this field to "0" disables voting.</P
></LI
><LI
><P
><EM
>Maximum Votes a person can put on a single
         bug</EM
>: 
         It should probably be some number lower than the
        "Maximum votes per person". Don't set this field to "0" if
        "Maximum votes per person" is non-zero; that doesn't make
        any sense.</P
></LI
><LI
><P
><EM
>Number of votes a bug in this product needs to
        automatically get out of the UNCONFIRMED state</EM
>: 
        Setting this field to "0" disables the automatic move of
        bugs from UNCONFIRMED to CONFIRMED. 
        </P
></LI
><LI
><P
>Once you have adjusted the values to your preference, click
        "Update".</P
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="quips"
>3.14. Quips</A
></H2
><P
>&#13;      Quips are small text messages that can be configured to appear
      next to search results. A Bugzilla installation can have its own specific
      quips. Whenever a quip needs to be displayed, a random selection
      is made from the pool of already existing quips.
    </P
><P
>&#13;      Quips are controlled by the <EM
>enablequips</EM
> parameter.
      It has several possible values: on, approved, frozen or off.
      In order to enable quips approval you need to set this parameter
      to "approved". In this way, users are free to submit quips for
      addition but an administrator must explicitly approve them before
      they are actually used.
    </P
><P
>&#13;      In order to see the user interface for the quips, it is enough to click
      on a quip when it is displayed together with the search results. Or
      it can be seen directly in the browser by visiting the quips.cgi URL
      (prefixed with the usual web location of the Bugzilla installation).
      Once the quip interface is displayed, it is enough to click the
      "view and edit the whole quip list" in order to see the administration
      page. A page with all the quips available in the database will
      be displayed.
    </P
><P
>&#13;      Next to each tip there is a checkbox, under the
      "Approved" column. Quips who have this checkbox checked are
      already approved and will appear next to the search results.
      The ones that have it unchecked are still preserved in the
      database but they will not appear on search results pages.
      User submitted quips have initially the checkbox unchecked.
    </P
><P
>&#13;      Also, there is a delete link next to each quip,
      which can be used in order to permanently delete a quip.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="groups"
>3.15. Groups and Group Security</A
></H2
><P
>&#13;    Groups allow for separating bugs into logical divisions.
    Groups are typically used
    to isolate bugs that should only be seen by certain people. For
    example, a company might create a different group for each one of its customers
    or partners. Group permissions could be set so that each partner or customer would
    only have access to their own bugs. Or, groups might be used to create
    variable access controls for different departments within an organization.
    Another common use of groups is to associate groups with products,
    creating isolation and access control on a per-product basis.
    </P
><P
>&#13;    Groups and group behaviors are controlled in several places:
    </P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;             The group configuration page. To view or edit existing groups, or to
             create new groups, access the "Groups" link from the "Administration"
             page. This section of the manual deals primarily with the aspect of
             group controls accessed on this page.  
           </P
></LI
><LI
><P
>&#13;            Global configuration parameters. Bugzilla has several parameters 
            that control the overall default group behavior and restriction
            levels. For more information on the parameters that control 
            group behavior globally, see <A
HREF="#param-group-security"
>Section 3.1.9</A
>.
          </P
></LI
><LI
><P
>&#13;            Product association with groups. Most of the functionality of groups
            and group security is controlled at the product level. Some aspects
            of group access controls for products are discussed in this section,
            but for more detail see <A
HREF="#product-group-controls"
>Section 3.4.4</A
>.
          </P
></LI
><LI
><P
>&#13;            Group access for users. See <A
HREF="#users-and-groups"
>Section 3.15.3</A
> for
            details on how users are assigned group access.
          </P
></LI
></OL
><P
>&#13;      Group permissions are such that if a bug belongs to a group, only members
      of that group can see the bug. If a bug is in more than one group, only
      members of <EM
>all</EM
> the groups that the bug is in can see
      the bug. For information on granting read-only access to certain people and
      full edit access to others, see <A
HREF="#product-group-controls"
>Section 3.4.4</A
>.
     </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        By default, bugs can also be seen by the Assignee, the Reporter, and 
        by everyone on the CC List, regardless of whether or not the bug would 
        typically be viewable by them. Visibility to the Reporter and CC List can 
        be overridden (on a per-bug basis) by bringing up the bug, finding the 
        section that starts with <SPAN
CLASS="QUOTE"
>"Users in the roles selected below..."</SPAN
>
        and un-checking the box next to either 'Reporter' or 'CC List' (or both).
      </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="create-groups"
>3.15.1. Creating Groups</A
></H3
><P
>&#13;        To create a new group, follow the steps below:
      </P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;            Select the <SPAN
CLASS="QUOTE"
>"Administration"</SPAN
> link in the page footer, 
            and then select the <SPAN
CLASS="QUOTE"
>"Groups"</SPAN
> link from the 
            Administration page.
          </P
></LI
><LI
><P
>&#13;            A table of all the existing groups is displayed. Below the table is a
            description of all the fields. To create a new group, select the 
            <SPAN
CLASS="QUOTE"
>"Add Group"</SPAN
> link under the table of existing groups.
          </P
></LI
><LI
><P
>&#13;            There are five fields to fill out. These fields are documented below
            the form. Choose a name and description for the group. Decide whether
            this group should be used for bugs (in all likelihood this should be
            selected). Optionally, choose a regular expression that will
            automatically add any matching users to the group, and choose an
            icon that will help identify user comments for the group. The regular
            expression can be useful, for example, to automatically put all users
            from the same company into one group (if the group is for a specific
            customer or partner). 
          </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;               If <SPAN
CLASS="QUOTE"
>"User RegExp"</SPAN
> is filled out, users whose email 
               addresses match the regular expression will automatically be 
               members of the group as long as their email addresses continue 
               to match the regular expression. If their email address changes
               and no longer matches the regular expression, they will be removed
               from the group. Versions 2.16 and older of Bugzilla did not automatically
               remove users who's email addresses no longer matched the RegExp.
             </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;               If specifying a domain in the regular expression, end
               the regexp with a "$". Otherwise, when granting access to 
               "@mycompany\.com", access will also be granted to 
               'badperson@mycompany.com.cracker.net'. Use the syntax,
               '@mycompany\.com$' for the regular expression.
             </P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>&#13;          After the new group is created, it can be edited for additional options. 
          The "Edit Group" page allows for specifying other groups that should be included
          in this group and which groups should be permitted to add and delete
          users from this group. For more details, see <A
HREF="#edit-groups"
>Section 3.15.2</A
>.
          </P
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="edit-groups"
>3.15.2. Editing Groups and Assigning Group Permissions</A
></H3
><P
>&#13;        To access the "Edit Groups" page, select the 
        <SPAN
CLASS="QUOTE"
>"Administration"</SPAN
> link in the page footer, 
        and then select the <SPAN
CLASS="QUOTE"
>"Groups"</SPAN
> link from the Administration page.
        A table of all the existing groups is displayed. Click on a group name
        you wish to edit or control permissions for.
      </P
><P
>&#13;       The "Edit Groups" page contains the same five fields present when 
       creating a new group. Below that are two additional sections, "Group
       Permissions," and "Mass Remove". The "Mass Remove" option simply removes
       all users from the group who match the regular expression entered. The
       "Group Permissions" section requires further explanation.
      </P
><P
>&#13;       The "Group Permissions" section on the "Edit Groups" page contains four sets
       of permissions that control the relationship of this group to other
       groups. If the 'usevisibilitygroups' parameter is in use (see
       <A
HREF="#parameters"
>Section 3.1</A
>) two additional sets of permissions are displayed. 
       Each set consists of two select boxes. On the left, a select box
       with a list of all existing groups. On the right, a select box listing
       all groups currently selected for this permission setting (this box will
       be empty for new groups). The way these controls allow groups to relate
       to one another is called <EM
>inheritance</EM
>. 
       Each of the six permissions is described below.
      </P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><EM
>Groups That Are a Member of This Group</EM
></DT
><DD
><P
> 
              Members of any groups selected here will automatically have 
              membership in this group. In other words, members of any selected 
              group will inherit membership in this group. 
            </P
></DD
><DT
><EM
>Groups That This Group Is a Member Of</EM
></DT
><DD
><P
>&#13;              Members of this group will inherit membership to any group 
              selected here. For example, suppose the group being edited is
              an Admin group. If there are two products  (Product1 and Product2) 
              and each product has its
              own group (Group1 and Group2), and the Admin group 
              should have access to both products, 
              simply select both Group1 and Group2 here. 
           </P
></DD
><DT
><EM
>Groups That Can Grant Membership in This Group</EM
></DT
><DD
><P
>&#13;             The members of any group selected here will be able add users
             to this group, even if they themselves are not in this group.
           </P
></DD
><DT
><EM
>Groups That This Group Can Grant Membership In</EM
></DT
><DD
><P
>&#13;             Members of this group can add users to any group selected here,
             even if they themselves are not in the selected groups.  
           </P
></DD
><DT
><EM
>Groups That Can See This Group</EM
></DT
><DD
><P
>&#13;             Members of any selected group can see the users in this group.
             This setting is only visible if the 'usevisibilitygroups' parameter
             is enabled on the Bugzilla Configuration page. See
             <A
HREF="#parameters"
>Section 3.1</A
> for information on configuring Bugzilla.
           </P
></DD
><DT
><EM
>Groups That This Group Can See</EM
></DT
><DD
><P
>&#13;             Members of this group can see members in any of the selected groups.
             This setting is only visible if the 'usevisibilitygroups' parameter
             is enabled on the the Bugzilla Configuration page. See
             <A
HREF="#parameters"
>Section 3.1</A
> for information on configuring Bugzilla.               
           </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="users-and-groups"
>3.15.3. Assigning Users to Groups</A
></H3
><P
>&#13;        A User can become a member of a group in several ways:
      </P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;            The user can be explicitly placed in the group by editing
            the user's profile. This can be done by accessing the "Users" page
            from the "Administration" page. Use the search form to find the user
            you want to edit group membership for, and click on their email
            address in the search results to edit their profile. The profile
            page lists all the groups, and indicates if the user is a member of
            the group either directly or indirectly. More information on indirect
            group membership is below. For more details on User administration,
            see <A
HREF="#useradmin"
>Section 3.2</A
>.
          </P
></LI
><LI
><P
>&#13;           The group can include another group of which the user is
           a member. This is indicated by square brackets around the checkbox  
           next to the group name in the user's profile. 
           See <A
HREF="#edit-groups"
>Section 3.15.2</A
> for details on group inheritance.
          </P
></LI
><LI
><P
>&#13;            The user's email address can match the regular expression
            that has been specified to automatically grant membership to
            the group. This is indicated by "*" around the check box by the
            group name in the user's profile.
            See <A
HREF="#create-groups"
>Section 3.15.1</A
> for details on 
            the regular expression option when creating groups.
           </P
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="AEN2110"
>3.15.4. Assigning Group Controls to Products</A
></H3
><P
>&#13;     The primary functionality of groups is derived from the relationship of 
     groups to products. The concepts around segregating access to bugs with
     product group controls can be confusing. For details and examples on this
     topic, see <A
HREF="#product-group-controls"
>Section 3.4.4</A
>.
     </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sanitycheck"
>3.16. Checking and Maintaining Database Integrity</A
></H2
><P
>&#13;    Over time it is possible for the Bugzilla database to become corrupt
    or to have anomalies.
    This could happen through normal usage of Bugzilla, manual database
    administration outside of the Bugzilla user interface, or from some
    other unexpected event. Bugzilla includes a "Sanity Check" script that
    can perform several basic database checks, and repair certain problems or
    inconsistencies. 
    </P
><P
>&#13;    To run the "Sanity Check" script, log in as an Administrator and click the
    "Sanity Check" link in the admin page. Any problems that are found will be
    displayed in red letters. If the script is capable of fixing a problem,
    it will present a link to initiate the fix. If the script can not
    fix the problem it will require manual database administration or recovery.
    </P
><P
>&#13;    The "Sanity Check" script can also be run from the command line via the perl
    script <TT
CLASS="filename"
>sanitycheck.pl</TT
>. The script can also be run as
    a <B
CLASS="command"
>cron</B
> job. Results will be delivered by email.
    </P
><P
>&#13;    The "Sanity Check" script should be run on a regular basis as a matter of
    best practice.
    </P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;      The "Sanity Check" script is no substitute for a competent database
      administrator. It is only designed to check and repair basic database
      problems.
      </P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="security"
></A
>Chapter 4. Bugzilla Security</H1
><P
>While some of the items in this chapter are related to the operating
  system Bugzilla is running on or some of the support software required to
  run Bugzilla, it is all related to protecting your data. This is not
  intended to be a comprehensive guide to securing Linux, Apache, MySQL, or
  any other piece of software mentioned. There is no substitute for active
  administration and monitoring of a machine. The key to good security is
  actually right in the middle of the word: <EM
>U R It</EM
>.
  </P
><P
>While programmers in general always strive to write secure code,
  accidents can and do happen. The best approach to security is to always
  assume that the program you are working with isn't 100% secure and restrict
  its access to other parts of your machine as much as possible.
  </P
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="security-os"
>4.1. Operating System</A
></H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="security-os-ports"
>4.1.1. TCP/IP Ports</A
></H3
><P
>The TCP/IP standard defines more than 65,000 ports for sending
      and receiving traffic. Of those, Bugzilla needs exactly one to operate
      (different configurations and options may require up to 3). You should
      audit your server and make sure that you aren't listening on any ports
      you don't need to be. It's also highly recommended that the server
      Bugzilla resides on, along with any other machines you administer, be
      placed behind some kind of firewall.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="security-os-accounts"
>4.1.2. System User Accounts</A
></H3
><P
>Many <A
HREF="#gloss-daemon"
><I
CLASS="glossterm"
>daemons</I
></A
>, such
      as Apache's <TT
CLASS="filename"
>httpd</TT
> or MySQL's
      <TT
CLASS="filename"
>mysqld</TT
>, run as either <SPAN
CLASS="QUOTE"
>"root"</SPAN
> or
      <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
>. This is even worse on Windows machines where the
      majority of <A
HREF="#gloss-service"
><I
CLASS="glossterm"
>services</I
></A
>
      run as <SPAN
CLASS="QUOTE"
>"SYSTEM"</SPAN
>. While running as <SPAN
CLASS="QUOTE"
>"root"</SPAN
> or
      <SPAN
CLASS="QUOTE"
>"SYSTEM"</SPAN
> introduces obvious security concerns, the
      problems introduced by running everything as <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
> may
      not be so obvious. Basically, if you run every daemon as
      <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
> and one of them gets compromised it can
      compromise every other daemon running as <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
> on your
      machine. For this reason, it is recommended that you create a user
      account for each daemon.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>You will need to set the <CODE
CLASS="option"
>webservergroup</CODE
> option
        in <TT
CLASS="filename"
>localconfig</TT
> to the group your web server runs
        as. This will allow <TT
CLASS="filename"
>./checksetup.pl</TT
> to set file
        permissions on Unix systems so that nothing is world-writable.
        </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="security-os-chroot"
>4.1.3. The <TT
CLASS="filename"
>chroot</TT
> Jail</A
></H3
><P
>&#13;        If your system supports it, you may wish to consider running
        Bugzilla inside of a <TT
CLASS="filename"
>chroot</TT
> jail. This option
        provides unprecedented security by restricting anything running
        inside the jail from accessing any information outside of it. If you
        wish to use this option, please consult the documentation that came
        with your system.
      </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="security-webserver"
>4.2. Web server</A
></H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="security-webserver-access"
>4.2.1. Disabling Remote Access to Bugzilla Configuration Files</A
></H3
><P
>&#13;        There are many files that are placed in the Bugzilla directory
        area that should not be accessible from the web server. Because of the way
        Bugzilla is currently layed out, the list of what should and should not
        be accessible is rather complicated. A quick way is to run
        <TT
CLASS="filename"
>testserver.pl</TT
> to check if your web server serves
        Bugzilla files as expected. If not, you may want to follow the few
        steps below.
      </P
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Bugzilla ships with the ability to create
        <A
HREF="#gloss-htaccess"
><I
CLASS="glossterm"
><TT
CLASS="filename"
>.htaccess</TT
></I
></A
>
        files that enforce these rules. Instructions for enabling these
        directives in Apache can be found in <A
HREF="#http-apache"
>Section 2.2.4.1</A
>
        </P
></TD
></TR
></TABLE
></DIV
><P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>In the main Bugzilla directory, you should:</P
><P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>Block:
              <TT
CLASS="filename"
>*.pl</TT
>, <TT
CLASS="filename"
>*localconfig*</TT
>
              </P
></LI
></UL
></LI
><LI
><P
>In <TT
CLASS="filename"
>data</TT
>:</P
><P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>Block everything</P
></LI
></UL
></LI
><LI
><P
>In <TT
CLASS="filename"
>data/webdot</TT
>:</P
><P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>If you use a remote webdot server:</P
><P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>Block everything</P
></LI
><LI
><P
>But allow
                  <TT
CLASS="filename"
>*.dot</TT
>
                  only for the remote webdot server</P
></LI
></UL
></LI
><LI
><P
>Otherwise, if you use a local GraphViz:</P
><P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>Block everything</P
></LI
><LI
><P
>But allow:
                  <TT
CLASS="filename"
>*.png</TT
>, <TT
CLASS="filename"
>*.gif</TT
>, <TT
CLASS="filename"
>*.jpg</TT
>, <TT
CLASS="filename"
>*.map</TT
>
                  </P
></LI
></UL
></LI
><LI
><P
>And if you don't use any dot:</P
><P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>Block everything</P
></LI
></UL
></LI
></UL
></LI
><LI
><P
>In <TT
CLASS="filename"
>Bugzilla</TT
>:</P
><P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>Block everything</P
></LI
></UL
></LI
><LI
><P
>In <TT
CLASS="filename"
>template</TT
>:</P
><P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>Block everything</P
></LI
></UL
></LI
></UL
><P
>Be sure to test that data that should not be accessed remotely is
      properly blocked. Of particular interest is the localconfig file which
      contains your database password. Also, be aware that many editors
      create temporary and backup files in the working directory and that
      those should also not be accessible. For more information, see
      <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
TARGET="_top"
>bug 186383</A
>
      or
      <A
HREF="http://online.securityfocus.com/bid/6501"
TARGET="_top"
>Bugtraq ID 6501</A
>.
      To test, simply run <TT
CLASS="filename"
>testserver.pl</TT
>, as said above.
      </P
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Be sure to check <A
HREF="#http"
>Section 2.2.4</A
> for instructions
        specific to the web server you use.
        </P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="security-bugzilla"
>4.3. Bugzilla</A
></H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="security-bugzilla-charset"
>4.3.1. Prevent users injecting malicious Javascript</A
></H3
><P
>If you installed Bugzilla version 2.22 or later from scratch,
      then the <EM
>utf8</EM
> parameter is switched on by default.
      This makes Bugzilla explicitly set the character encoding, following
      <A
HREF="http://www.cert.org/tech_tips/malicious_code_mitigation.html#3"
TARGET="_top"
>a
      CERT advisory</A
> recommending exactly this.
      The following therefore does not apply to you; just keep
      <EM
>utf8</EM
> turned on.
      </P
><P
>If you've upgraded from an older version, then it may be possible
      for a Bugzilla user to take advantage of character set encoding
      ambiguities to inject HTML into Bugzilla comments.
      This could include malicious scripts. 
      This is because due to internationalization concerns, we are unable to
      turn the <EM
>utf8</EM
> parameter on by default for upgraded
      installations.
      Turning it on manually will prevent this problem.
      </P
></DIV
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="using"
></A
>Chapter 5. Using Bugzilla</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="using-intro"
>5.1. Introduction</A
></H2
><P
>This section contains information for end-users of Bugzilla.  There
    is a Bugzilla test installation, called
    <A
HREF="http://landfill.bugzilla.org/"
TARGET="_top"
>Landfill</A
>, which you are
    welcome to play with (if it's up). However, not all of the Bugzilla
    installations there will necessarily have all Bugzilla features enabled,
    and different installations run different versions, so some things may not
    quite work as this document describes.</P
><P
>&#13;      Frequently Asked Questions (FAQ) are available and answered on
      <A
HREF="http://wiki.mozilla.org/Bugzilla:FAQ"
TARGET="_top"
>wiki.mozilla.org</A
>.
      They may cover some questions you have which are left unanswered.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="myaccount"
>5.2. Create a Bugzilla Account</A
></H2
><P
>If you want to use Bugzilla, first you need to create an account.
    Consult with the administrator responsible for your installation of
    Bugzilla for the URL you should use to access it. If you're
    test-driving Bugzilla, use this URL: 
    <A
HREF="http://landfill.bugzilla.org/bugzilla-4.0-branch/"
TARGET="_top"
>http://landfill.bugzilla.org/bugzilla-4.0-branch/</A
>.
    </P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;          On the home page <TT
CLASS="filename"
>index.cgi</TT
>, click the
          <SPAN
CLASS="QUOTE"
>"Open a new Bugzilla account"</SPAN
> link, or the
          <SPAN
CLASS="QUOTE"
>"New Account"</SPAN
> link available in the footer of pages.
          Now enter your email address, then click the <SPAN
CLASS="QUOTE"
>"Send"</SPAN
>
          button.
        </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            If none of these links is available, this means that the
            administrator of the installation has disabled self-registration.
            This means that only an administrator can create accounts
            for other users. One reason could be that this installation is
            private.
          </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;            Also, if only some users are allowed to create an account on
            the installation, you may see these links but your registration
            may fail if your email address doesn't match the ones accepted
            by the installation. This is another way to restrict who can
            access and edit bugs in this installation.
          </P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>&#13;          Within moments, and if your registration is accepted, you should
          receive an email to the address you provided, which contains your
          login name (generally the same as the email address), and two URLs
          with a token (a random string generated by the installation) to
          confirm, respectively cancel, your registration. This is a way to
          prevent users from abusing the generation of user accounts, for
          instance by entering inexistent email addresses, or email addresses
          which do not belong to them.
        </P
></LI
><LI
><P
>&#13;          By default, you have 3 days to confirm your registration. Past this
          timeframe, the token is invalidated and the registration is
          automatically canceled. You can also cancel this registration sooner
          by using the appropriate URL in the email you got.
        </P
></LI
><LI
><P
>&#13;          If you confirm your registration, Bugzilla will ask you your real name
          (optional, but recommended) and your password, which must be between
          3 and 16 characters long.
        </P
></LI
><LI
><P
>&#13;          Now all you need to do is to click the <SPAN
CLASS="QUOTE"
>"Log In"</SPAN
>
          link in the footer at the bottom of the page in your browser,
          enter your email address and password you just chose into the
          login form, and click the <SPAN
CLASS="QUOTE"
>"Log in"</SPAN
> button.
        </P
></LI
></OL
><P
>&#13;      You are now logged in. Bugzilla uses cookies to remember you are
      logged in so, unless you have cookies disabled or your IP address changes,
      you should not have to log in again during your session.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="bug_page"
>5.3. Anatomy of a Bug</A
></H2
><P
>The core of Bugzilla is the screen which displays a particular
    bug. It's a good place to explain some Bugzilla concepts. 
    <A
HREF="http://landfill.bugzilla.org/bugzilla-4.0-branch/show_bug.cgi?id=1"
TARGET="_top"
>&#13;    Bug 1 on Landfill</A
>

    is a good example. Note that the labels for most fields are hyperlinks;
    clicking them will take you to context-sensitive help on that
    particular field. Fields marked * may not be present on every
    installation of Bugzilla.</P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;        <EM
>Product and Component</EM
>: 
        Bugs are divided up by Product and Component, with a Product
        having one or more Components in it. For example,
        bugzilla.mozilla.org's "Bugzilla" Product is composed of several
        Components: 
        <P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;        <EM
>Administration:</EM
>
        Administration of a Bugzilla installation.</TD
></TR
><TR
><TD
>&#13;        <EM
>Bugzilla-General:</EM
>
        Anything that doesn't fit in the other components, or spans
        multiple components.</TD
></TR
><TR
><TD
>&#13;        <EM
>Creating/Changing Bugs:</EM
>
        Creating, changing, and viewing bugs.</TD
></TR
><TR
><TD
>&#13;        <EM
>Documentation:</EM
>
        The Bugzilla documentation, including The Bugzilla Guide.</TD
></TR
><TR
><TD
>&#13;        <EM
>Email:</EM
>
        Anything to do with email sent by Bugzilla.</TD
></TR
><TR
><TD
>&#13;        <EM
>Installation:</EM
>
        The installation process of Bugzilla.</TD
></TR
><TR
><TD
>&#13;        <EM
>Query/Buglist:</EM
>
        Anything to do with searching for bugs and viewing the
        buglists.</TD
></TR
><TR
><TD
>&#13;        <EM
>Reporting/Charting:</EM
>
        Getting reports from Bugzilla.</TD
></TR
><TR
><TD
>&#13;        <EM
>User Accounts:</EM
>
        Anything about managing a user account from the user's perspective.
        Saved queries, creating accounts, changing passwords, logging in,
        etc.</TD
></TR
><TR
><TD
>&#13;        <EM
>User Interface:</EM
>
        General issues having to do with the user interface cosmetics (not
        functionality) including cosmetic issues, HTML templates,
        etc.</TD
></TR
></TBODY
></TABLE
><P
></P
>
        </P
></LI
><LI
><P
>&#13;        <EM
>Status and Resolution:</EM
>

        These define exactly what state the bug is in - from not even
        being confirmed as a bug, through to being fixed and the fix
        confirmed by Quality Assurance. The different possible values for
        Status and Resolution on your installation should be documented in the
        context-sensitive help for those items.</P
></LI
><LI
><P
>&#13;        <EM
>Assigned To:</EM
>
        The person responsible for fixing the bug.</P
></LI
><LI
><P
>&#13;        <EM
>*QA Contact:</EM
>
        The person responsible for quality assurance on this bug.</P
></LI
><LI
><P
>&#13;        <EM
>*URL:</EM
>
        A URL associated with the bug, if any.</P
></LI
><LI
><P
>&#13;        <EM
>Summary:</EM
>
        A one-sentence summary of the problem.</P
></LI
><LI
><P
>&#13;        <EM
>*Status Whiteboard:</EM
>
        (a.k.a. Whiteboard) A free-form text area for adding short notes
        and tags to a bug.</P
></LI
><LI
><P
>&#13;        <EM
>*Keywords:</EM
>
        The administrator can define keywords which you can use to tag and
        categorise bugs - e.g. The Mozilla Project has keywords like crash
        and regression.</P
></LI
><LI
><P
>&#13;        <EM
>Platform and OS:</EM
>
        These indicate the computing environment where the bug was
        found.</P
></LI
><LI
><P
>&#13;        <EM
>Version:</EM
>
        The "Version" field is usually used for versions of a product which
        have been released, and is set to indicate which versions of a
        Component have the particular problem the bug report is
        about.</P
></LI
><LI
><P
>&#13;        <EM
>Priority:</EM
>
        The bug assignee uses this field to prioritize his or her bugs.
        It's a good idea not to change this on other people's bugs.</P
></LI
><LI
><P
>&#13;        <EM
>Severity:</EM
>
        This indicates how severe the problem is - from blocker
        ("application unusable") to trivial ("minor cosmetic issue"). You
        can also use this field to indicate whether a bug is an enhancement
        request.</P
></LI
><LI
><P
>&#13;        <EM
>*Target:</EM
>
        (a.k.a. Target Milestone) A future version by which the bug is to
        be fixed. e.g. The Bugzilla Project's milestones for future
        Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not
        restricted to numbers, thought - you can use any text strings, such
        as dates.</P
></LI
><LI
><P
>&#13;        <EM
>Reporter:</EM
>
        The person who filed the bug.</P
></LI
><LI
><P
>&#13;        <EM
>CC list:</EM
>
        A list of people who get mail when the bug changes.</P
></LI
><LI
><P
>&#13;        <EM
>*Time Tracking:</EM
>
        This form can be used for time tracking.
        To use this feature, you have to be blessed group membership
        specified by the <SPAN
CLASS="QUOTE"
>"timetrackinggroup"</SPAN
> parameter.
        <P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;        <EM
>Orig. Est.:</EM
>
        This field shows the original estimated time.</TD
></TR
><TR
><TD
>&#13;        <EM
>Current Est.:</EM
>
        This field shows the current estimated time.
        This number is calculated from <SPAN
CLASS="QUOTE"
>"Hours Worked"</SPAN
>
        and <SPAN
CLASS="QUOTE"
>"Hours Left"</SPAN
>.</TD
></TR
><TR
><TD
>&#13;        <EM
>Hours Worked:</EM
>
        This field shows the number of hours worked.</TD
></TR
><TR
><TD
>&#13;        <EM
>Hours Left:</EM
>
        This field shows the <SPAN
CLASS="QUOTE"
>"Current Est."</SPAN
> -
        <SPAN
CLASS="QUOTE"
>"Hours Worked"</SPAN
>.
        This value + <SPAN
CLASS="QUOTE"
>"Hours Worked"</SPAN
> will become the
        new Current Est.</TD
></TR
><TR
><TD
>&#13;        <EM
>%Complete:</EM
>
        This field shows what percentage of the task is complete.</TD
></TR
><TR
><TD
>&#13;        <EM
>Gain:</EM
>
        This field shows the number of hours that the bug is ahead of the
        <SPAN
CLASS="QUOTE"
>"Orig. Est."</SPAN
>.</TD
></TR
><TR
><TD
>&#13;        <EM
>Deadline:</EM
>
        This field shows the deadline for this bug.</TD
></TR
></TBODY
></TABLE
><P
></P
>
        </P
></LI
><LI
><P
>&#13;        <EM
>Attachments:</EM
>
          You can attach files (e.g. testcases or patches) to bugs. If there
          are any attachments, they are listed in this section.  Attachments are
          normally stored in the Bugzilla database, unless they are marked as
          Big Files, which are stored directly on disk.
        </P
></LI
><LI
><P
>&#13;        <EM
>*Dependencies:</EM
>
        If this bug cannot be fixed unless other bugs are fixed (depends
        on), or this bug stops other bugs being fixed (blocks), their
        numbers are recorded here.</P
></LI
><LI
><P
>&#13;        <EM
>*Votes:</EM
>
        Whether this bug has any votes.</P
></LI
><LI
><P
>&#13;        <EM
>Additional Comments:</EM
>
        You can add your two cents to the bug discussion here, if you have
        something worthwhile to say.</P
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="lifecycle"
>5.4. Life Cycle of a Bug</A
></H2
><P
>&#13;      The life cycle of a bug, also known as workflow, is customizable to match
      the needs of your organization, see <A
HREF="#bug_status_workflow"
>Section 3.12</A
>.
      <A
HREF="#lifecycle-image"
>Figure 5-1</A
> contains a graphical representation of
      the default workflow using the default bug statuses. If you wish to
      customize this image for your site, the
      <A
HREF="../images/bzLifecycle.xml"
TARGET="_top"
>diagram file</A
>
      is available in <A
HREF="http://www.gnome.org/projects/dia"
TARGET="_top"
>Dia's</A
>
      native XML format.
    </P
><DIV
CLASS="figure"
><A
NAME="lifecycle-image"
></A
><P
><B
>Figure 5-1. Lifecycle of a Bugzilla Bug</B
></P
><DIV
CLASS="mediaobject"
><P
><IMG
SRC="../images/bzLifecycle.png"></P
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="query"
>5.5. Searching for Bugs</A
></H2
><P
>The Bugzilla Search page is the interface where you can find
    any bug report, comment, or patch currently in the Bugzilla system. You
    can play with it here: 
    <A
HREF="http://landfill.bugzilla.org/bugzilla-4.0-branch/query.cgi"
TARGET="_top"
>http://landfill.bugzilla.org/bugzilla-4.0-branch/query.cgi</A
>.</P
><P
>The Search page has controls for selecting different possible
    values for all of the fields in a bug, as described above. For some
    fields, multiple values can be selected. In those cases, Bugzilla
    returns bugs where the content of the field matches any one of the selected
    values. If none is selected, then the field can take any value.</P
><P
>&#13;      After a search is run, you can save it as a Saved Search, which
      will appear in the page footer. If you are in the group defined 
      by the "querysharegroup" parameter, you may share your queries 
      with other users, see <A
HREF="#savedsearches"
>Saved Searches</A
> for more details.
    </P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="boolean"
>5.5.1. Boolean Charts</A
></H3
><P
>&#13;        Highly advanced querying is done using Boolean Charts.
      </P
><P
>&#13;        The boolean charts further restrict the set of results
        returned by a query. It is possible to search for bugs
        based on elaborate combinations of criteria.
      </P
><P
>&#13;        The simplest boolean searches have only one term. These searches
        permit the selected left <EM
>field</EM
>
        to be compared using a
        selectable <EM
>operator</EM
> to a
        specified <EM
>value.</EM
>
        Using the "And," "Or," and "Add Another Boolean Chart" buttons, 
        additional terms can be included in the query, further
        altering the list of bugs returned by the query.
      </P
><P
>&#13;        There are three fields in each row of a boolean search. 
      </P
><P
></P
><UL
><LI
><P
>&#13;            <EM
>Field:</EM
>
            the items being searched 
          </P
></LI
><LI
><P
>&#13;            <EM
>Operator:</EM
>
            the comparison operator 
          </P
></LI
><LI
><P
>&#13;            <EM
>Value:</EM
>
            the value to which the field is being compared
          </P
></LI
></UL
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="pronouns"
>5.5.1.1. Pronoun Substitution</A
></H4
><P
>&#13;          Sometimes, a query needs to compare a user-related field
          (such as ReportedBy) with a role-specific user (such as the
          user running the query or the user to whom each bug is assigned).
          When the operator is either "equals" or "notequals", the value
          can be "%reporter%", "%assignee%", "%qacontact%", or "%user%".
          The user pronoun
          refers to the user who is executing the query or, in the case
          of whining reports, the user who will be the recipient
          of the report. The reporter, assignee, and qacontact
          pronouns refer to the corresponding fields in the bug.
        </P
><P
>&#13;          Boolean charts also let you type a group name in any user-related
          field if the operator is either "equals", "notequals" or "anyexact".
          This will let you query for any member belonging (or not) to the
          specified group. The group name must be entered following the
          "%group.foo%" syntax, where "foo" is the group name.
          So if you are looking for bugs reported by any user being in the
          "editbugs" group, then you can type "%group.editbugs%".
        </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="negation"
>5.5.1.2. Negation</A
></H4
><P
>&#13;          At first glance, negation seems redundant. Rather than
          searching for
          <A
NAME="AEN2438"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13;              NOT("summary" "contains the string" "foo"),
            </P
></BLOCKQUOTE
>
          one could search for 
          <A
NAME="AEN2440"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13;              ("summary" "does not contain the string" "foo").
            </P
></BLOCKQUOTE
>
          However, the search 
          <A
NAME="AEN2442"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13;              ("CC" "does not contain the string" "@mozilla.org")
            </P
></BLOCKQUOTE
>
          would find every bug where anyone on the CC list did not contain 
          "@mozilla.org" while
          <A
NAME="AEN2444"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13;              NOT("CC" "contains the string" "@mozilla.org")
            </P
></BLOCKQUOTE
>
          would find every bug where there was nobody on the CC list who
          did contain the string. Similarly, the use of negation also permits
          complex expressions to be built using terms OR'd together and then
          negated. Negation permits queries such as
          <A
NAME="AEN2446"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13;              NOT(("product" "equals" "update") OR 
            ("component" "equals" "Documentation"))
            </P
></BLOCKQUOTE
>
          to find bugs that are neither 
          in the update product or in the documentation component or
          <A
NAME="AEN2448"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13;              NOT(("commenter" "equals" "%assignee%") OR 
              ("component" "equals" "Documentation"))
            </P
></BLOCKQUOTE
>
          to find non-documentation
          bugs on which the assignee has never commented.
        </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="multiplecharts"
>5.5.1.3. Multiple Charts</A
></H4
><P
>&#13;          The terms within a single row of a boolean chart are all
          constraints on a single piece of data. If you are looking for
          a bug that has two different people cc'd on it, then you need 
          to use two boolean charts. A search for
          <A
NAME="AEN2453"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13;              ("cc" "contains the string" "foo@") AND
              ("cc" "contains the string" "@mozilla.org")
            </P
></BLOCKQUOTE
>
          would return only bugs with "foo@mozilla.org" on the cc list.
          If you wanted bugs where there is someone on the cc list
          containing "foo@" and someone else containing "@mozilla.org",
          then you would need two boolean charts.
          <A
NAME="AEN2455"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13;              First chart: ("cc" "contains the string" "foo@")
            </P
><P
>&#13;              Second chart: ("cc" "contains the string" "@mozilla.org")
            </P
></BLOCKQUOTE
>
          The bugs listed will be only the bugs where ALL the charts are true.
        </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="quicksearch"
>5.5.2. Quicksearch</A
></H3
><P
>&#13;        Quicksearch is a single-text-box query tool which uses
        metacharacters to indicate what is to be searched. For example, typing
        "<TT
CLASS="literal"
>foo|bar</TT
>"
        into Quicksearch would search for "foo" or "bar" in the
        summary and status whiteboard of a bug; adding
        "<TT
CLASS="literal"
>:BazProduct</TT
>" would
        search only in that product.
        You can use it to find a bug by its number or its alias, too.
      </P
><P
>&#13;        You'll find the Quicksearch box in Bugzilla's footer area.
        On Bugzilla's front page, there is an additional
        <A
HREF="../../page.cgi?id=quicksearch.html"
TARGET="_top"
>Help</A
>
        link which details how to use it.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="casesensitivity"
>5.5.3. Case Sensitivity in Searches</A
></H3
><P
>&#13;      Bugzilla queries are case-insensitive and accent-insensitive, when
      used with either MySQL or Oracle databases. When using Bugzilla with
      PostgreSQL, however, some queries are case-sensitive. This is due to
      the way PostgreSQL handles case and accent sensitivity. 
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="list"
>5.5.4. Bug Lists</A
></H3
><P
>If you run a search, a list of matching bugs will be returned.
      </P
><P
>The format of the list is configurable. For example, it can be
      sorted by clicking the column headings. Other useful features can be
      accessed using the links at the bottom of the list:
      <P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;        <EM
>Long Format:</EM
>

        this gives you a large page with a non-editable summary of the fields
        of each bug.</TD
></TR
><TR
><TD
>&#13;        <EM
>XML:</EM
>

        get the buglist in the XML format.</TD
></TR
><TR
><TD
>&#13;        <EM
>CSV:</EM
>

        get the buglist as comma-separated values, for import into e.g.
        a spreadsheet.</TD
></TR
><TR
><TD
>&#13;        <EM
>Feed:</EM
>

        get the buglist as an Atom feed.  Copy this link into your
        favorite feed reader.  If you are using Firefox, you can also
        save the list as a live bookmark by clicking the live bookmark
        icon in the status bar.  To limit the number of bugs in the feed,
        add a limit=n parameter to the URL.</TD
></TR
><TR
><TD
>&#13;        <EM
>iCalendar:</EM
>

        Get the buglist as an iCalendar file. Each bug is represented as a
        to-do item in the imported calendar.</TD
></TR
><TR
><TD
>&#13;        <EM
>Change Columns:</EM
>

        change the bug attributes which appear in the list.</TD
></TR
><TR
><TD
>&#13;        <EM
>Change several bugs at once:</EM
>

        If your account is sufficiently empowered, and more than one bug
        appear in the bug list, this link is displayed which lets you make
        the same change to all the bugs in the list - for example, changing
        their assignee.</TD
></TR
><TR
><TD
>&#13;        <EM
>Send mail to bug assignees:</EM
>

        If more than one bug appear in the bug list and there are at least
        two distinct bug assignees, this links is displayed which lets you
        easily send a mail to the assignees of all bugs on the list.</TD
></TR
><TR
><TD
>&#13;        <EM
>Edit Search:</EM
>

        If you didn't get exactly the results you were looking for, you can
        return to the Query page through this link and make small revisions
        to the query you just made so you get more accurate results.</TD
></TR
><TR
><TD
>&#13;        <EM
>Remember Search As:</EM
>

        You can give a search a name and remember it; a link will appear
        in your page footer giving you quick access to run it again later.
        </TD
></TR
></TBODY
></TABLE
><P
></P
>
      </P
><P
>&#13;        If you would like to access the bug list from another program
        it is often useful to have the list returned in something other
        than HTML. By adding the ctype=type parameter into the bug list URL
        you can specify several alternate formats. Besides the types described
        above, the following formats are also supported: ECMAScript, also known
        as JavaScript (ctype=js), and Resource Description Framework RDF/XML
        (ctype=rdf).
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="individual-buglists"
>5.5.5. Adding/removing tags to/from bugs</A
></H3
><P
>&#13;        You can add and remove tags from individual bugs, which let you find and
        manage them more easily. Creating a new tag automatically generates a saved
        search - whose name is the name of the tag - which lists bugs with this tag.
        This saved search will be displayed in the footer of pages by default, as
        all other saved searches. The main difference between tags and normal saved
        searches is that saved searches, as described in the previous section, are
        stored in the form of a list of matching criteria, while the saved search
        generated by tags is a list of bug numbers. Consequently, you can easily
        edit this list by either adding or removing tags from bugs. To enable this
        feature, you have to turn on the <SPAN
CLASS="QUOTE"
>"Enable tags for bugs"</SPAN
> user
        preference, see <A
HREF="#userpreferences"
>Section 5.10</A
>. This feature is disabled
        by default.
      </P
><P
>&#13;        This feature is useful when you want to keep track of several bugs, but
        for different reasons. Instead of adding yourself to the CC list of all
        these bugs and mixing all these reasons, you can now store these bugs in
        separate lists, e.g. <SPAN
CLASS="QUOTE"
>"Keep in mind"</SPAN
>, <SPAN
CLASS="QUOTE"
>"Interesting bugs"</SPAN
>,
        or <SPAN
CLASS="QUOTE"
>"Triage"</SPAN
>. One big advantage of this way to manage bugs
        is that you can easily add or remove bugs one by one, which is not
        possible to do with saved searches without having to edit the search
        criteria again.
      </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="bugreports"
>5.6. Filing Bugs</A
></H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="fillingbugs"
>5.6.1. Reporting a New Bug</A
></H3
><P
>Years of bug writing experience has been distilled for your
      reading pleasure into the 
      <A
HREF="http://landfill.bugzilla.org/bugzilla-4.0-branch/page.cgi?id=bug-writing.html"
TARGET="_top"
>&#13;      Bug Writing Guidelines</A
>. 
      While some of the advice is Mozilla-specific, the basic principles of
      reporting Reproducible, Specific bugs, isolating the Product you are
      using, the Version of the Product, the Component which failed, the
      Hardware Platform, and Operating System you were using at the time of
      the failure go a long way toward ensuring accurate, responsible fixes
      for the bug that bit you.</P
><P
>The procedure for filing a bug is as follows:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;            Click the <SPAN
CLASS="QUOTE"
>"New"</SPAN
> link available in the footer
            of pages, or the <SPAN
CLASS="QUOTE"
>"Enter a new bug report"</SPAN
> link
            displayed on the home page of the Bugzilla installation.
          </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;              If you want to file a test bug to see how Bugzilla works,
              you can do it on one of our test installations on
              <A
HREF="http://landfill.bugzilla.org/bugzilla-4.0-branch/"
TARGET="_top"
>Landfill</A
>.
            </P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>&#13;            You first have to select the product in which you found a bug.
          </P
></LI
><LI
><P
>&#13;            You now see a form where you can specify the component (part of
            the product which is affected by the bug you discovered; if you have
            no idea, just select <SPAN
CLASS="QUOTE"
>"General"</SPAN
> if such a component exists),
            the version of the program you were using, the Operating System and
            platform your program is running on and the severity of the bug (if the
            bug you found crashes the program, it's probably a major or a critical
            bug; if it's a typo somewhere, that's something pretty minor; if it's
            something you would like to see implemented, then that's an enhancement).
          </P
></LI
><LI
><P
>&#13;            You now have to give a short but descriptive summary of the bug you found.
            <SPAN
CLASS="QUOTE"
>"My program is crashing all the time"</SPAN
> is a very poor summary
            and doesn't help developers at all. Try something more meaningful or
            your bug will probably be ignored due to a lack of precision.
            The next step is to give a very detailed list of steps to reproduce
            the problem you encountered. Try to limit these steps to a minimum set
            required to reproduce the problem. This will make the life of
            developers easier, and the probability that they consider your bug in
            a reasonable timeframe will be much higher.
          </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;              Try to make sure that everything in the summary is also in the first
              comment. Summaries are often updated and this will ensure your original
              information is easily accessible.
            </P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>&#13;            As you file the bug, you can also attach a document (testcase, patch,
            or screenshot of the problem).
          </P
></LI
><LI
><P
>&#13;            Depending on the Bugzilla installation you are using and the product in
            which you are filing the bug, you can also request developers to consider
            your bug in different ways (such as requesting review for the patch you
            just attached, requesting your bug to block the next release of the
            product, and many other product specific requests).
          </P
></LI
><LI
><P
>&#13;            Now is a good time to read your bug report again. Remove all misspellings,
            otherwise your bug may not be found by developers running queries for some
            specific words, and so your bug would not get any attention.
            Also make sure you didn't forget any important information developers
            should know in order to reproduce the problem, and make sure your
            description of the problem is explicit and clear enough.
            When you think your bug report is ready to go, the last step is to
            click the <SPAN
CLASS="QUOTE"
>"Commit"</SPAN
> button to add your report into the database.
          </P
></LI
></OL
><P
>&#13;      You do not need to put "any" or similar strings in the URL field.
      If there is no specific URL associated with the bug, leave this 
      field blank.
      </P
><P
>If you feel a bug you filed was incorrectly marked as a
      DUPLICATE of another, please question it in your bug, not      
      the bug it was duped to. Feel free to CC the person who duped it 
      if they are not already CCed.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="cloningbugs"
>5.6.2. Clone an Existing Bug</A
></H3
><P
>&#13;        Starting with version 2.20, Bugzilla has a feature that allows you
        to clone an existing bug. The newly created bug will inherit
        most settings from the old bug. This allows you to track more
        easily similar concerns in a new bug. To use this, go to the bug
        that you want to clone, then click the <SPAN
CLASS="QUOTE"
>"Clone This Bug"</SPAN
>
        link on the bug page. This will take you to the <SPAN
CLASS="QUOTE"
>"Enter Bug"</SPAN
>
        page that is filled with the values that the old bug has.
        You can change those values and/or texts if needed.
      </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="attachments"
>5.7. Attachments</A
></H2
><P
>&#13;      You should use attachments, rather than comments, for large chunks of ASCII
      data, such as trace, debugging output files, or log files. That way, it
      doesn't bloat the bug for everyone who wants to read it, and cause people to
      receive fat, useless mails.
    </P
><P
>You should make sure to trim screenshots. There's no need to show the
      whole screen if you are pointing out a single-pixel problem.
    </P
><P
>Bugzilla stores and uses a Content-Type for each attachment
      (e.g. text/html). To download an attachment as a different
      Content-Type (e.g. application/xhtml+xml), you can override this
      using a 'content_type' parameter on the URL, e.g.
      <TT
CLASS="filename"
>&#38;content_type=text/plain</TT
>.
    </P
><P
>&#13;      If you have a really large attachment, something that does not need to
      be recorded forever (as most attachments are), or something that is too
      big for your database, you can mark your attachment as a
      <SPAN
CLASS="QUOTE"
>"Big File"</SPAN
>, assuming the administrator of the installation
      has enabled this feature.  Big Files are stored directly on disk instead
      of in the database.  The maximum size of a <SPAN
CLASS="QUOTE"
>"Big File"</SPAN
> is
      normally larger than the maximum size of a regular attachment. Independently
      of the storage system used, an administrator can delete these attachments
      at any time. Nevertheless, if these files are stored in the database, the
      <SPAN
CLASS="QUOTE"
>"allow_attachment_deletion"</SPAN
> parameter (which is turned off
      by default) must be enabled in order to delete them.
    </P
><P
>&#13;      Also, if the administrator turned on the <SPAN
CLASS="QUOTE"
>"allow_attach_url"</SPAN
>
      parameter, you can enter the URL pointing to the attachment instead of
      uploading the attachment itself. For example, this is useful if you want to
      point to an external application, a website or a very large file. Note that
      there is no guarantee that the source file will always be available, nor
      that its content will remain unchanged.
    </P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="patchviewer"
>5.7.1. Patch Viewer</A
></H3
><P
>Viewing and reviewing patches in Bugzilla is often difficult due to
      lack of context, improper format and the inherent readability issues that
      raw patches present.  Patch Viewer is an enhancement to Bugzilla designed
      to fix that by offering increased context, linking to sections, and
      integrating with Bonsai, LXR and CVS.</P
><P
>Patch viewer allows you to:</P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>View patches in color, with side-by-side view rather than trying
        to interpret the contents of the patch.</TD
></TR
><TR
><TD
>See the difference between two patches.</TD
></TR
><TR
><TD
>Get more context in a patch.</TD
></TR
><TR
><TD
>Collapse and expand sections of a patch for easy
        reading.</TD
></TR
><TR
><TD
>Link to a particular section of a patch for discussion or
        review</TD
></TR
><TR
><TD
>Go to Bonsai or LXR to see more context, blame, and
        cross-references for the part of the patch you are looking at</TD
></TR
><TR
><TD
>Create a rawtext unified format diff out of any patch, no
        matter what format it came from</TD
></TR
></TBODY
></TABLE
><P
></P
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="patchviewer_view"
>5.7.1.1. Viewing Patches in Patch Viewer</A
></H4
><P
>The main way to view a patch in patch viewer is to click on the
        "Diff" link next to a patch in the Attachments list on a bug. You may
        also do this within the edit window by clicking the "View Attachment As
        Diff" button in the Edit Attachment screen.</P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="patchviewer_diff"
>5.7.1.2. Seeing the Difference Between Two Patches</A
></H4
><P
>To see the difference between two patches, you must first view the
        newer patch in Patch Viewer.  Then select the older patch from the
        dropdown at the top of the page ("Differences between [dropdown] and
        this patch") and click the "Diff" button. This will show you what
        is new or changed in the newer patch.</P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="patchviewer_context"
>5.7.1.3. Getting More Context in a Patch</A
></H4
><P
>To get more context in a patch, you put a number in the textbox at
        the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
        This will give you that many lines of context before and after each
        change. Alternatively, you can click on the "File" link there and it
        will show each change in the full context of the file. This feature only
        works against files that were diffed using "cvs diff".</P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="patchviewer_collapse"
>5.7.1.4. Collapsing and Expanding Sections of a Patch</A
></H4
><P
>To view only a certain set of files in a patch (for example, if a
        patch is absolutely huge and you want to only review part of it at a
        time), you can click the "(+)" and "(-)" links next to each file (to
        expand it or collapse it). If you want to collapse all files or expand
        all files, you can click the "Collapse All" and "Expand All" links at the
        top of the page.</P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="patchviewer_link"
>5.7.1.5. Linking to a Section of a Patch</A
></H4
><P
>To link to a section of a patch (for example, if you want to be
        able to give someone a URL to show them which part you are talking
        about) you simply click the "Link Here" link on the section header. The
        resulting URL can be copied and used in discussion.</P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="patchviewer_bonsai_lxr"
>5.7.1.6. Going to Bonsai and LXR</A
></H4
><P
>To go to Bonsai to get blame for the lines you are interested in,
        you can click the "Lines XX-YY" link on the section header you are
        interested in. This works even if the patch is against an old
        version of the file, since Bonsai stores all versions of the file.</P
><P
>To go to LXR, you click on the filename on the file header
        (unfortunately, since LXR only does the most recent version, line
        numbers are likely to rot).</P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="patchviewer_unified_diff"
>5.7.1.7. Creating a Unified Diff</A
></H4
><P
>If the patch is not in a format that you like, you can turn it
        into a unified diff format by clicking the "Raw Unified" link at the top
        of the page.</P
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="hintsandtips"
>5.8. Hints and Tips</A
></H2
><P
>This section distills some Bugzilla tips and best practices
    that have been developed.</P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="AEN2591"
>5.8.1. Autolinkification</A
></H3
><P
>Bugzilla comments are plain text - so typing &#60;U&#62; will
      produce less-than, U, greater-than rather than underlined text.
      However, Bugzilla will automatically make hyperlinks out of certain
      sorts of text in comments. For example, the text 
      "http://www.bugzilla.org" will be turned into a link:
      <A
HREF="http://www.bugzilla.org"
TARGET="_top"
>http://www.bugzilla.org</A
>.
      Other strings which get linkified in the obvious manner are:
      <P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>bug 12345</TD
></TR
><TR
><TD
>comment 7</TD
></TR
><TR
><TD
>bug 23456, comment 53</TD
></TR
><TR
><TD
>attachment 4321</TD
></TR
><TR
><TD
>mailto:george@example.com</TD
></TR
><TR
><TD
>george@example.com</TD
></TR
><TR
><TD
>ftp://ftp.mozilla.org</TD
></TR
><TR
><TD
>Most other sorts of URL</TD
></TR
></TBODY
></TABLE
><P
></P
>
      </P
><P
>A corollary here is that if you type a bug number in a comment,
      you should put the word "bug" before it, so it gets autolinkified
      for the convenience of others.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="commenting"
>5.8.2. Comments</A
></H3
><P
>If you are changing the fields on a bug, only comment if
      either you have something pertinent to say, or Bugzilla requires it.
      Otherwise, you may spam people unnecessarily with bug mail.
      To take an example: a user can set up their account to filter out messages
      where someone just adds themselves to the CC field of a bug
      (which happens a lot.) If you come along, add yourself to the CC field,
      and add a comment saying "Adding self to CC", then that person
      gets a pointless piece of mail they would otherwise have avoided.
      </P
><P
>&#13;      Don't use sigs in comments. Signing your name ("Bill") is acceptable,
      if you do it out of habit, but full mail/news-style
      four line ASCII art creations are not.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="comment-wrapping"
>5.8.3. Server-Side Comment Wrapping</A
></H3
><P
>&#13;      Bugzilla stores comments unwrapped and wraps them at display time. This
      ensures proper wrapping in all browsers. Lines beginning with the "&#62;" 
      character are assumed to be quotes, and are not wrapped.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="dependencytree"
>5.8.4. Dependency Tree</A
></H3
><P
>&#13;        On the <SPAN
CLASS="QUOTE"
>"Dependency tree"</SPAN
> page linked from each bug
        page, you can see the dependency relationship from the bug as a
        tree structure.
      </P
><P
>&#13;        You can change how much depth to show, and you can hide resolved bugs
        from this page. You can also collaps/expand dependencies for
        each bug on the tree view, using the [-]/[+] buttons that appear
        before its summary. This option is not available for terminal
        bugs in the tree (that don't have further dependencies).
      </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="timetracking"
>5.9. Time Tracking Information</A
></H2
><P
>&#13;      Users who belong to the group specified by the <SPAN
CLASS="QUOTE"
>"timetrackinggroup"</SPAN
>
      parameter have access to time-related fields. Developers can see
      deadlines and estimated times to fix bugs, and can provide time spent
      on these bugs.
    </P
><P
>&#13;      At any time, a summary of the time spent by developers on bugs is
      accessible either from bug lists when clicking the <SPAN
CLASS="QUOTE"
>"Time Summary"</SPAN
>
      button or from individual bugs when clicking the <SPAN
CLASS="QUOTE"
>"Summarize time"</SPAN
>
      link in the time tracking table. The <TT
CLASS="filename"
>summarize_time.cgi</TT
>
      page lets you view this information either per developer or per bug,
      and can be split on a month basis to have greater details on how time
      is spent by developers.
    </P
><P
>&#13;      As soon as a bug is marked as RESOLVED, the remaining time expected
      to fix the bug is set to zero. This lets QA people set it again for
      their own usage, and it will be set to zero again when the bug will
      be marked as CLOSED.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="userpreferences"
>5.10. User Preferences</A
></H2
><P
>&#13;    Once logged in, you can customize various aspects of
    Bugzilla via the "Preferences" link in the page footer.
    The preferences are split into five tabs:</P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="generalpreferences"
>5.10.1. General Preferences</A
></H3
><P
>&#13;        This tab allows you to change several default settings of Bugzilla.
      </P
><P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>&#13;            Bugzilla's general appearance (skin) - select which skin to use.
            Bugzilla supports adding custom skins.
          </P
></LI
><LI
><P
>&#13;            Quote the associated comment when you click on its reply link - sets
            the behavior of the comment "Reply" link. Options include quoting the
            full comment, just reference the comment number, or turn the link off.
          </P
></LI
><LI
><P
>&#13;            Language used in email - select which language email will be sent in,
            from the list of available languages.
          </P
></LI
><LI
><P
>&#13;            After changing a bug - This controls what page is displayed after
            changes to a bug are submitted. The options include to show the bug
            just modified, to show the next bug in your list, or to do nothing.
          </P
></LI
><LI
><P
>&#13;            Enable tags for bugs - turn bug tagging on or off.
          </P
></LI
><LI
><P
>&#13;            Zoom textareas large when in use (requires JavaScript) - enable or
            disable the automatic expanding of text areas when  text is being
            entered into them. 
          </P
></LI
><LI
><P
>&#13;            Field separator character for CSV files -
            Select between a comma and semi-colon for exported CSV bug lists.
          </P
></LI
><LI
><P
>&#13;            Automatically add me to the CC list of bugs I change - set default
            behavior of CC list. Options include "Always", "Never", and "Only
            if I have no role on them". 
          </P
></LI
><LI
><P
>&#13;            When viewing a bug, show comments in this order -
            controls the order of comments. Options include "Oldest
            to Newest", "Newest to Oldest" and "Newest to Oldest, but keep the
            bug description at the top".
          </P
></LI
><LI
><P
>&#13;            Show a quip at the top of each bug list - controls
            whether a quip will be shown on the Bug list page.
          </P
></LI
></UL
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="emailpreferences"
>5.10.2. Email Preferences</A
></H3
><P
>&#13;        This tab allows you to enable or disable email notification on
        specific events.
      </P
><P
>&#13;        In general, users have almost complete control over how much (or
        how little) email Bugzilla sends them. If you want to receive the
        maximum amount of email possible, click the <SPAN
CLASS="QUOTE"
>"Enable All 
        Mail"</SPAN
> button. If you don't want to receive any email from
        Bugzilla at all, click the <SPAN
CLASS="QUOTE"
>"Disable All Mail"</SPAN
> button.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          A Bugzilla administrator can stop a user from receiving
          bugmail by clicking the <SPAN
CLASS="QUOTE"
>"Bugmail Disabled"</SPAN
> checkbox
          when editing the user account. This is a drastic step
          best taken only for disabled accounts, as it overrides 
          the user's individual mail preferences.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        There are two global options -- <SPAN
CLASS="QUOTE"
>"Email me when someone
        asks me to set a flag"</SPAN
> and <SPAN
CLASS="QUOTE"
>"Email me when someone
        sets a flag I asked for"</SPAN
>. These define how you want to
        receive bugmail with regards to flags. Their use is quite
        straightforward; enable the checkboxes if you want Bugzilla to
        send you mail under either of the above conditions.
      </P
><P
>&#13;        If you'd like to set your bugmail to something besides
        'Completely ON' and 'Completely OFF', the
        <SPAN
CLASS="QUOTE"
>"Field/recipient specific options"</SPAN
> table
        allows you to do just that. The rows of the table
        define events that can happen to a bug -- things like
        attachments being added, new comments being made, the
        priority changing, etc. The columns in the table define
        your relationship with the bug:
      </P
><P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>&#13;            Reporter - Where you are the person who initially
            reported the bug. Your name/account appears in the
            <SPAN
CLASS="QUOTE"
>"Reporter:"</SPAN
> field.
          </P
></LI
><LI
><P
>&#13;            Assignee - Where you are the person who has been
            designated as the one responsible for the bug. Your
            name/account appears in the <SPAN
CLASS="QUOTE"
>"Assigned To:"</SPAN
>
            field of the bug.
          </P
></LI
><LI
><P
>&#13;            QA Contact - You are one of the designated
            QA Contacts for the bug. Your account appears in the 
            <SPAN
CLASS="QUOTE"
>"QA Contact:"</SPAN
> text-box of the bug.
          </P
></LI
><LI
><P
>&#13;            CC - You are on the list CC List for the bug.
            Your account appears in the <SPAN
CLASS="QUOTE"
>"CC:"</SPAN
> text box
            of the bug.
          </P
></LI
><LI
><P
>&#13;            Voter - You have placed one or more votes for the bug.
            Your account appears only if someone clicks on the 
            <SPAN
CLASS="QUOTE"
>"Show votes for this bug"</SPAN
> link on the bug.
          </P
></LI
></UL
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          Some columns may not be visible for your installation, depending
          on your site's configuration.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        To fine-tune your bugmail, decide the events for which you want
        to receive bugmail; then decide if you want to receive it all
        the time (enable the checkbox for every column), or only when
        you have a certain relationship with a bug (enable the checkbox
        only for those columns). For example: if you didn't want to
        receive mail when someone added themselves to the CC list, you
        could uncheck all the boxes in the <SPAN
CLASS="QUOTE"
>"CC Field Changes"</SPAN
>
        line. As another example, if you never wanted to receive email
        on bugs you reported unless the bug was resolved, you would
        un-check all boxes in the <SPAN
CLASS="QUOTE"
>"Reporter"</SPAN
> column
        except for the one on the <SPAN
CLASS="QUOTE"
>"The bug is resolved or
        verified"</SPAN
> row.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          Bugzilla adds the <SPAN
CLASS="QUOTE"
>"X-Bugzilla-Reason"</SPAN
> header to
          all bugmail it sends, describing the recipient's relationship
          (AssignedTo, Reporter, QAContact, CC, or Voter) to the bug.
          This header can be used to do further client-side filtering.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        Bugzilla has a feature called <SPAN
CLASS="QUOTE"
>"Users Watching"</SPAN
>.
        When you enter one or more comma-delineated user accounts (usually email
        addresses) into the text entry box, you will receive a copy of all the
        bugmail those users are sent (security settings permitting).
        This powerful functionality enables seamless transitions as developers
        change projects or users go on holiday.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          The ability to watch other users may not be available in all
          Bugzilla installations. If you don't see this feature, and feel
          that you need it, speak to your administrator.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        Each user listed in the <SPAN
CLASS="QUOTE"
>"Users watching you"</SPAN
> field
        has you listed in their <SPAN
CLASS="QUOTE"
>"Users to watch"</SPAN
> list
        and can get bugmail according to your relationship to the bug and
        their <SPAN
CLASS="QUOTE"
>"Field/recipient specific options"</SPAN
> setting.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="savedsearches"
>5.10.3. Saved Searches</A
></H3
><P
>&#13;      On this tab you can view and run any Saved Searches that you have
      created, and also any Saved Searches that other members of the group
      defined in the "querysharegroup" parameter have shared. 
      Saved Searches can be added to the page footer from this screen. 
      If somebody is sharing a Search with a group she or he is allowed to
      <A
HREF="#groups"
>assign users to</A
>, the sharer may opt to have
      the Search show up in the footer of the group's direct members by default.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="accountpreferences"
>5.10.4. Name and Password</A
></H3
><P
>On this tab, you can change your basic account information,
      including your password, email address and real name. For security
      reasons, in order to change anything on this page you must type your
      <EM
>current</EM
> password into the <SPAN
CLASS="QUOTE"
>"Password"</SPAN
>
      field at the top of the page.
      If you attempt to change your email address, a confirmation
      email is sent to both the old and new addresses, with a link to use to
      confirm the change. This helps to prevent account hijacking.</P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="permissionsettings"
>5.10.5. Permissions</A
></H3
><P
>&#13;      This is a purely informative page which outlines your current
      permissions on this installation of Bugzilla.
      </P
><P
>&#13;      A complete list of permissions is below. Only users with 
      <EM
>editusers</EM
> privileges can change the permissions 
      of other users.
      </P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>admin</DT
><DD
><P
> 
             Indicates user is an Administrator.
            </P
></DD
><DT
>bz_canusewhineatothers</DT
><DD
><P
> 
             Indicates user can configure whine reports for other users.
            </P
></DD
><DT
>bz_canusewhines</DT
><DD
><P
> 
             Indicates user can configure whine reports for self.
            </P
></DD
><DT
>bz_sudoers</DT
><DD
><P
> 
             Indicates user can perform actions as other users.
            </P
></DD
><DT
>bz_sudo_protect</DT
><DD
><P
> 
             Indicates user can not be impersonated by other users.
            </P
></DD
><DT
>canconfirm</DT
><DD
><P
> 
             Indicates user can confirm a bug or mark it a duplicate.
            </P
></DD
><DT
>creategroups</DT
><DD
><P
> 
             Indicates user can create and destroy groups.
            </P
></DD
><DT
>editbugs</DT
><DD
><P
> 
             Indicates user can edit all bug fields.
            </P
></DD
><DT
>editclassifications</DT
><DD
><P
> 
             Indicates user can create, destroy, and edit classifications.
            </P
></DD
><DT
>editcomponents</DT
><DD
><P
> 
             Indicates user can create, destroy, and edit components.
            </P
></DD
><DT
>editkeywords</DT
><DD
><P
> 
             Indicates user can create, destroy, and edit keywords.
            </P
></DD
><DT
>editusers</DT
><DD
><P
> 
             Indicates user can edit or disable users.
            </P
></DD
><DT
>tweakparams</DT
><DD
><P
> 
             Indicates user can change Parameters.
            </P
></DD
></DL
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        For more information on how permissions work in Bugzilla (i.e. who can
        change what), see  <A
HREF="#cust-change-permissions"
>Section 6.4</A
>. 
        </P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="reporting"
>5.11. Reports and Charts</A
></H2
><P
>As well as the standard buglist, Bugzilla has two more ways of
    viewing sets of bugs. These are the reports (which give different
    views of the current state of the database) and charts (which plot
    the changes in particular sets of bugs over time.)</P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="reports"
>5.11.1. Reports</A
></H3
><P
>&#13;        A report is a view of the current state of the bug database.
      </P
><P
>&#13;        You can run either an HTML-table-based report, or a graphical
        line/pie/bar-chart-based one. The two have different pages to
        define them, but are close cousins - once you've defined and
        viewed a report, you can switch between any of the different
        views of the data at will.
      </P
><P
>&#13;        Both report types are based on the idea of defining a set of bugs
        using the standard search interface, and then choosing some
        aspect of that set to plot on the horizontal and/or vertical axes.
        You can also get a form of 3-dimensional report by choosing to have
        multiple images or tables.
      </P
><P
>&#13;        So, for example, you could use the search form to choose "all
        bugs in the WorldControl product", and then plot their severity
        against their component to see which component had had the largest
        number of bad bugs reported against it. 
      </P
><P
>&#13;        Once you've defined your parameters and hit "Generate Report",
        you can switch between HTML, CSV, Bar, Line and Pie. (Note: Pie
        is only available if you didn't define a vertical axis, as pie
        charts don't have one.) The other controls are fairly self-explanatory;
        you can change the size of the image if you find text is overwriting
        other text, or the bars are too thin to see.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="charts"
>5.11.2. Charts</A
></H3
><P
>&#13;        A chart is a view of the state of the bug database over time.
      </P
><P
>&#13;        Bugzilla currently has two charting systems - Old Charts and New 
        Charts. Old Charts have been part of Bugzilla for a long time; they
        chart each status and resolution for each product, and that's all.
        They are deprecated, and going away soon - we won't say any more 
        about them.
        New Charts are the future - they allow you to chart anything you
        can define as a search.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          Both charting forms require the administrator to set up the
          data-gathering script. If you can't see any charts, ask them whether
          they have done so.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        An individual line on a chart is called a data set.
        All data sets are organised into categories and subcategories. The 
        data sets that Bugzilla defines automatically use the Product name 
        as a Category and Component names as Subcategories, but there is no 
        need for you to follow that naming scheme with your own charts if 
        you don't want to.
      </P
><P
>&#13;        Data sets may be public or private. Everyone sees public data sets in
        the list, but only their creator sees private data sets. Only 
        administrators can make data sets public.
        No two data sets, even two private ones, can have the same set of 
        category, subcategory and name. So if you are creating private data 
        sets, one idea is to have the Category be your username.
      </P
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="AEN2788"
>5.11.2.1. Creating Charts</A
></H4
><P
>&#13;          You create a chart by selecting a number of data sets from the
          list, and pressing Add To List for each. In the List Of Data Sets
          To Plot, you can define the label that data set will have in the
          chart's legend, and also ask Bugzilla to Sum a number of data sets 
          (e.g. you could Sum data sets representing RESOLVED, VERIFIED and 
          CLOSED in a particular product to get a data set representing all 
          the resolved bugs in that product.)
        </P
><P
>&#13;          If you've erroneously added a data set to the list, select it
          using the checkbox and click Remove. Once you add more than one 
          data set, a "Grand Total" line
          automatically appears at the bottom of the list. If you don't want
          this, simply remove it as you would remove any other line.
        </P
><P
>&#13;          You may also choose to plot only over a certain date range, and
          to cumulate the results - that is, to plot each one using the 
          previous one as a baseline, so the top line gives a sum of all 
          the data sets. It's easier to try than to explain :-)
        </P
><P
>&#13;          Once a data set is in the list, one can also perform certain 
          actions on it. For example, one can edit the
          data set's parameters (name, frequency etc.) if it's one you
          created or if you are an administrator.
        </P
><P
>&#13;           Once you are happy, click Chart This List to see the chart.
        </P
></DIV
><DIV
CLASS="section"
><HR><H4
CLASS="section"
><A
NAME="charts-new-series"
>5.11.2.2. Creating New Data Sets</A
></H4
><P
>&#13;          You may also create new data sets of your own. To do this,
          click the "create a new data set" link on the Create Chart page.
          This takes you to a search-like interface where you can define
          the search that Bugzilla will plot. At the bottom of the page,
          you choose the category, sub-category and name of your new
          data set. 
        </P
><P
>&#13;          If you have sufficient permissions, you can make the data set public,
          and reduce the frequency of data collection to less than the default
          seven days.
        </P
></DIV
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="flags"
>5.12. Flags</A
></H2
><P
>&#13;      A flag is a kind of status that can be set on bugs or attachments
      to indicate that the bugs/attachments are in a certain state.
      Each installation can define its own set of flags that can be set
      on bugs or attachments.
    </P
><P
>&#13;      If your installation has defined a flag, you can set or unset that flag,
      and if your administrator has enabled requesting of flags, you can submit
      a request for another user to set the flag.
    </P
><P
>&#13;      To set a flag, select either "+" or "-" from the drop-down menu next to
      the name of the flag in the "Flags" list.  The meaning of these values are
      flag-specific and thus cannot be described in this documentation,
      but by way of example, setting a flag named "review" to "+" may indicate
      that the bug/attachment has passed review, while setting it to "-"
      may indicate that the bug/attachment has failed review.
    </P
><P
>&#13;      To unset a flag, click its drop-down menu and select the blank value.
      Note that marking an attachment as obsolete automatically cancels all
      pending requests for the attachment.
    </P
><P
>&#13;      If your administrator has enabled requests for a flag, request a flag
      by selecting "?" from the drop-down menu and then entering the username
      of the user you want to set the flag in the text field next to the menu.
    </P
><P
>&#13;      A set flag appears in bug reports and on "edit attachment" pages with the
      abbreviated username of the user who set the flag prepended to the
      flag name. For example, if Jack sets a "review" flag to "+", it appears
      as Jack: review [ + ]
    </P
><P
>&#13;      A requested flag appears with the user who requested the flag prepended
      to the flag name and the user who has been requested to set the flag
      appended to the flag name within parentheses.  For example, if Jack
      asks Jill for review, it appears as Jack: review [ ? ] (Jill).
    </P
><P
>&#13;      You can browse through open requests made of you and by you by selecting
      'My Requests' from the footer. You can also look at open requests limited
      by other requesters, requestees, products, components, and flag names from
      this page. Note that you can use '-' for requestee to specify flags with
      'no requestee' set.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="whining"
>5.13. Whining</A
></H2
><P
>&#13;      Whining is a feature in Bugzilla that can regularly annoy users at 
      specified times.  Using this feature, users can execute saved searches 
      at specific times (i.e. the 15th of the month at midnight) or at 
      regular intervals (i.e. every 15 minutes on Sundays).  The results of the
      searches are sent to the user, either as a single email or as one email 
      per bug, along with some descriptive text.
    </P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        Throughout this section it will be assumed that all users are members 
        of the bz_canusewhines group, membership in which is required in order 
        to use the Whining system.  You can easily make all users members of 
        the bz_canusewhines group by setting the User RegExp to ".*" (without 
        the quotes).
      </P
><P
>&#13;        Also worth noting is the bz_canusewhineatothers group.  Members of this
        group can create whines for any user or group in Bugzilla using a 
        extended form of the whining interface.  Features only available to 
        members of the bz_canusewhineatothers group will be noted in the 
        appropriate places.
      </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        For whining to work, a special Perl script must be executed at regular
        intervals.  More information on this is available in 
        <A
HREF="#installation-whining"
>Section 2.3.3</A
>.
      </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        This section does not cover the whineatnews.pl script.  See
        <A
HREF="#installation-whining-cron"
>Section 2.3.2</A
> for more information on 
        The Whining Cron.
      </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="whining-overview"
>5.13.1. The Event</A
></H3
><P
>&#13;        The whining system defines an "Event" as one or more queries being 
        executed at regular intervals, with the results of said queries (if
        there are any) being emailed to the user.  Events are created by 
        clicking on the "Add new event" button.
      </P
><P
>&#13;        Once a new event is created, the first thing to set is the "Email 
        subject line".  The contents of this field will be used in the subject
        line of every email generated by this event.  In addition to setting a 
        subject, space is provided to enter some descriptive text that will be 
        included at the top of each message (to help you in understanding why 
        you received the email in the first place).
      </P
><P
>&#13;        The next step is to specify when the Event is to be run (the Schedule) 
        and what searches are to be performed (the Searches).
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="whining-schedule"
>5.13.2. Whining Schedule</A
></H3
><P
>&#13;         Each whining event is associated with zero or more schedules.  A 
         schedule is used to specify when the query (specified below) is to be
         run.  A new event starts out with no schedules (which means it will 
         never run, as it is not scheduled to run).  To add a schedule, press
         the "Add a new schedule" button.
      </P
><P
>&#13;         Each schedule includes an interval, which you use to tell Bugzilla 
         when the event should be run.  An event can be run on certain days of
         the week, certain days of the month, during weekdays (defined as 
         Monday through Friday), or every day.
      </P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          Be careful if you set your event to run on the 29th, 30th, or 31st of
          the month, as your event may not run exactly when expected.  If you 
          want your event to run on the last day of the month, select "Last day
          of the month" as the interval.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        Once you have specified the day(s) on which the event is to be run, you
        should now specify the time at which the event is to be run.  You can 
        have the event run at a certain hour on the specified day(s), or 
        every hour, half-hour, or quarter-hour on the specified day(s).
      </P
><P
>&#13;        If a single schedule does not execute an event as many times as you 
        would want, you can create another schedule for the same event.  For 
        example, if you want to run an event on days whose numbers are
        divisible by seven, you would need to add four schedules to the event,
        setting the schedules to run on the 7th, 14th, 21st, and 28th (one day 
        per schedule) at whatever time (or times) you choose.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          If you are a member of the bz_canusewhineatothers group, then you
          will be presented with another option: "Mail to".  Using this you 
          can control who will receive the emails generated by this event.  You
          can choose to send the emails to a single user (identified by email 
          address) or a single group (identified by group name).  To send to 
          multiple users or groups, create a new schedule for each additional 
          user/group.
        </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="whining-query"
>5.13.3. Whining Searches</A
></H3
><P
>&#13;        Each whining event is associated with zero or more searches.  A search
        is any saved search to be run as part of the specified schedule (see
        above).  You start out without any searches associated with the event
        (which means that the event will not run, as there will never be any
        results to return).  To add a search, press the "Include search" button.
      </P
><P
>&#13;        The first field to examine in your newly added search is the Sort field.
        Searches are run, and results included, in the order specified by the
        Sort field.  Searches with smaller Sort values will run before searches
        with bigger Sort values.
      </P
><P
>&#13;        The next field to examine is the Search field.  This is where you 
        choose the actual search that is to be run.  Instead of defining search
        parameters here, you are asked to choose from the list of saved 
        searches (the same list that appears at the bottom of every Bugzilla 
        page).  You are only allowed to choose from searches that you have 
        saved yourself (the default saved search, "My Bugs", is not a valid 
        choice).  If you do not have any saved searches, you can take this 
        opportunity to create one (see <A
HREF="#list"
>Section 5.5.4</A
>).
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          When running queries, the whining system acts as if you are the user
          executing the query.  This means that the whining system will ignore
          bugs that match your query, but that you can not access.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        Once you have chosen the saved search to be executed, give the query a 
        descriptive title.  This title will appear in the email, above the 
        results of the query.  If you choose "One message per bug", the query 
        title will appear at the top of each email that contains a bug matching
        your query.
      </P
><P
>&#13;        Finally, decide if the results of the query should be sent in a single
        email, or if each bug should appear in its own email.
      </P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          Think carefully before checking the "One message per bug" box.  If
          you create a query that matches thousands of bugs, you will receive 
          thousands of emails!
        </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="AEN2848"
>5.13.4. Saving Your Changes</A
></H3
><P
>&#13;        Once you have defined at least one schedule, and created at least one 
        query, go ahead and "Update/Commit".  This will save your Event and make
        it available for immediate execution.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          If you ever feel like deleting your event, you may do so using the 
          "Remove Event" button in the upper-right corner of each Event.  You 
          can also modify an existing event, so long as you "Update/Commit" 
          after completing your modifications.
        </P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="customization"
></A
>Chapter 6. Customizing Bugzilla</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="extensions"
>6.1. Bugzilla Extensions</A
></H2
><P
>&#13;      One of the best ways to customize Bugzilla is by writing a Bugzilla
      Extension. Bugzilla Extensions let you modify both the code and
      UI of Bugzilla in a way that can be distributed to other Bugzilla
      users and ported forward to future versions of Bugzilla with minimal
      effort.
    </P
><P
>&#13;      See the <A
HREF="api/Bugzilla/Extension.html"
TARGET="_top"
>Bugzilla Extension
      documentation</A
> for information on how to write an Extension.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="cust-skins"
>6.2. Custom Skins</A
></H2
><P
>&#13;      Bugzilla allows you to have multiple skins. These are custom CSS and possibly
      also custom images for Bugzilla. To create a new custom skin, you have two
      choices:
      <P
></P
><UL
><LI
><P
>&#13;            Make a single CSS file, and put it in the 
            <TT
CLASS="filename"
>skins/contrib</TT
> directory.
          </P
></LI
><LI
><P
>&#13;            Make a directory that contains all the same CSS file
            names as <TT
CLASS="filename"
>skins/standard/</TT
>, and put
            your directory in <TT
CLASS="filename"
>skins/contrib/</TT
>.
          </P
></LI
></UL
>
    </P
><P
>&#13;      After you put the file or the directory there, make sure to run checksetup.pl
      so that it can reset the file permissions correctly.
    </P
><P
>&#13;      After you have installed the new skin, it will show up as an option in the
      user's General Preferences. If you would like to force a particular skin on all
      users, just select it in the Default Preferences and then uncheck "Enabled" on
      the preference.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="cust-templates"
>6.3. Template Customization</A
></H2
><P
>&#13;      Administrators can configure the look and feel of Bugzilla without
      having to edit Perl files or face the nightmare of massive merge
      conflicts when they upgrade to a newer version in the future.
    </P
><P
>&#13;      Templatization also makes localized versions of Bugzilla possible, 
      for the first time. It's possible to have Bugzilla's UI language 
      determined by the user's browser. More information is available in
      <A
HREF="#template-http-accept"
>Section 6.3.6</A
>.
    </P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="template-directory"
>6.3.1. Template Directory Structure</A
></H3
><P
>&#13;        The template directory structure starts with top level directory 
        named <TT
CLASS="filename"
>template</TT
>, which contains a directory
        for each installed localization. The next level defines the
        language used in the templates. Bugzilla comes with English
        templates, so the directory name is <TT
CLASS="filename"
>en</TT
>,
        and we will discuss <TT
CLASS="filename"
>template/en</TT
> throughout
        the documentation. Below <TT
CLASS="filename"
>template/en</TT
> is the
        <TT
CLASS="filename"
>default</TT
> directory, which contains all the
        standard templates shipped with Bugzilla.
      </P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          A directory <TT
CLASS="filename"
>data/templates</TT
> also exists;
          this is where Template Toolkit puts the compiled versions of
          the templates from either the default or custom directories.
          <EM
>Do not</EM
> directly edit the files in this
          directory, or all your changes will be lost the next time
          Template Toolkit recompiles the templates.
        </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="template-method"
>6.3.2. Choosing a Customization Method</A
></H3
><P
>&#13;        If you want to edit Bugzilla's templates, the first decision
        you must make is how you want to go about doing so. There are two
        choices, and which you use depends mainly on the scope of your 
        modifications, and the method you plan to use to upgrade Bugzilla.
      </P
><P
>&#13;        The first method of making customizations is to directly edit the
        templates found in <TT
CLASS="filename"
>template/en/default</TT
>.
        This is probably the best way to go about it if you are going to
        be upgrading Bugzilla through CVS, because if you then execute
        a <B
CLASS="command"
>cvs update</B
>, any changes you have made will
        be merged automagically with the updated versions.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          If you use this method, and CVS conflicts occur during an
          update, the conflicted templates (and possibly other parts
          of your installation) will not work until they are resolved.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        The second method is to copy the templates to be modified
        into a mirrored directory structure under 
        <TT
CLASS="filename"
>template/en/custom</TT
>. Templates in this
        directory structure automatically override any identically-named
        and identically-located templates in the 
        <TT
CLASS="filename"
>default</TT
> directory. 
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          The <TT
CLASS="filename"
>custom</TT
> directory does not exist
          at first and must be created if you want to use it.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        The second method of customization should be used if you 
        use the overwriting method of upgrade, because otherwise 
        your changes will be lost.  This method may also be better if
        you are using the CVS method of upgrading and are going to make major
        changes, because it is guaranteed that the contents of this directory
        will not be touched during an upgrade, and you can then decide whether
        to continue using your own templates, or make the effort to merge your
        changes into the new versions by hand.
      </P
><P
>&#13;        Using this method, your installation may break if incompatible
        changes are made to the template interface.  Such changes should
        be documented in the release notes, provided you are using a
        stable release of Bugzilla.  If you use using unstable code, you will
        need to deal with this one yourself, although if possible the changes
        will be mentioned before they occur in the deprecations section of the
        previous stable release's release notes.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          Regardless of which method you choose, it is recommended that
          you run <B
CLASS="command"
>./checksetup.pl</B
> after 
          editing any templates in the <TT
CLASS="filename"
>template/en/default</TT
>
          directory, and after creating or editing any templates in the 
          <TT
CLASS="filename"
>custom</TT
> directory.
        </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          It is <EM
>required</EM
> that you run 
          <B
CLASS="command"
>./checksetup.pl</B
> after creating a new
          template in the <TT
CLASS="filename"
>custom</TT
> directory. Failure
          to do so will raise an incomprehensible error message.
        </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="template-edit"
>6.3.3. How To Edit Templates</A
></H3
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          If you are making template changes that you intend on submitting back
          for inclusion in standard Bugzilla, you should read the relevant
          sections of the 
          <A
HREF="http://www.bugzilla.org/docs/developer.html"
TARGET="_top"
>Developers'
          Guide</A
>.
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        The syntax of the Template Toolkit language is beyond the scope of
        this guide. It's reasonably easy to pick up by looking at the current 
        templates; or, you can read the manual, available on the
        <A
HREF="http://www.template-toolkit.org"
TARGET="_top"
>Template Toolkit home
        page</A
>.
      </P
><P
>&#13;        One thing you should take particular care about is the need
        to properly HTML filter data that has been passed into the template.
        This means that if the data can possibly contain special HTML characters
        such as &#60;, and the data was not intended to be HTML, they need to be
        converted to entity form, i.e. &#38;lt;.  You use the 'html' filter in the
        Template Toolkit to do this.  If you forget, you may open up
        your installation to cross-site scripting attacks.
      </P
><P
>&#13;        Also note that Bugzilla adds a few filters of its own, that are not
        in standard Template Toolkit.  In particular, the 'url_quote' filter
        can convert characters that are illegal or have special meaning in URLs,
        such as &#38;, to the encoded form, i.e. %26.  This actually encodes most
        characters (but not the common ones such as letters and numbers and so
        on), including the HTML-special characters, so there's never a need to
        HTML filter afterwards.
      </P
><P
>&#13;        Editing templates is a good way of doing a <SPAN
CLASS="QUOTE"
>"poor man's custom
        fields"</SPAN
>.
        For example, if you don't use the Status Whiteboard, but want to have
        a free-form text entry box for <SPAN
CLASS="QUOTE"
>"Build Identifier"</SPAN
>,
        then you can just
        edit the templates to change the field labels. It's still be called
        status_whiteboard internally, but your users don't need to know that.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="template-formats"
>6.3.4. Template Formats and Types</A
></H3
><P
>&#13;        Some CGI's have the ability to use more than one template. For example,
        <TT
CLASS="filename"
>buglist.cgi</TT
> can output itself as RDF, or as two 
        formats of HTML (complex and simple). The mechanism that provides this 
        feature is extensible.
      </P
><P
>&#13;        Bugzilla can support different types of output, which again can have 
        multiple formats. In order to request a certain type, you can append 
        the &#38;ctype=&#60;contenttype&#62; (such as rdf or html) to the 
        <TT
CLASS="filename"
>&#60;cginame&#62;.cgi</TT
> URL. If you would like to 
        retrieve a certain format, you can use the &#38;format=&#60;format&#62; 
        (such as simple or complex) in the URL.
      </P
><P
>&#13;        To see if a CGI supports multiple output formats and types, grep the
        CGI for <SPAN
CLASS="QUOTE"
>"get_format"</SPAN
>. If it's not present, adding
        multiple format/type support isn't too hard - see how it's done in
        other CGIs, e.g. config.cgi.
      </P
><P
>&#13;        To make a new format template for a CGI which supports this, 
        open a current template for
        that CGI and take note of the INTERFACE comment (if present.) This 
        comment defines what variables are passed into this template. If 
        there isn't one, I'm afraid you'll have to read the template and
        the code to find out what information you get. 
      </P
><P
>&#13;        Write your template in whatever markup or text style is appropriate.
      </P
><P
>&#13;        You now need to decide what content type you want your template
        served as. The content types are defined in the
        <TT
CLASS="filename"
>Bugzilla/Constants.pm</TT
> file in the 
        <TT
CLASS="filename"
>contenttypes</TT
>
        constant. If your content type is not there, add it. Remember
        the three- or four-letter tag assigned to your content type. 
        This tag will be part of the template filename.
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          After adding or changing a content type, it's suitable to edit
          <TT
CLASS="filename"
>Bugzilla/Constants.pm</TT
> in order to reflect
          the changes. Also, the file should be kept up to date after an
          upgrade if content types have been customized in the past. 
        </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        Save the template as <TT
CLASS="filename"
>&#60;stubname&#62;-&#60;formatname&#62;.&#60;contenttypetag&#62;.tmpl</TT
>. 
        Try out the template by calling the CGI as 
        <TT
CLASS="filename"
>&#60;cginame&#62;.cgi?format=&#60;formatname&#62;&#38;ctype=&#60;type&#62;</TT
> .
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="template-specific"
>6.3.5. Particular Templates</A
></H3
><P
>&#13;        There are a few templates you may be particularly interested in
        customizing for your installation.
      </P
><P
>&#13;        <B
CLASS="command"
>index.html.tmpl</B
>:
        This is the Bugzilla front page.
      </P
><P
>&#13;        <B
CLASS="command"
>global/header.html.tmpl</B
>:
        This defines the header that goes on all Bugzilla pages.
        The header includes the banner, which is what appears to users
        and is probably what you want to edit instead.  However the
        header also includes the HTML HEAD section, so you could for
        example add a stylesheet or META tag by editing the header.
      </P
><P
>&#13;        <B
CLASS="command"
>global/banner.html.tmpl</B
>:
        This contains the <SPAN
CLASS="QUOTE"
>"banner"</SPAN
>, the part of the header
        that appears
        at the top of all Bugzilla pages.  The default banner is reasonably
        barren, so you'll probably want to customize this to give your
        installation a distinctive look and feel.  It is recommended you
        preserve the Bugzilla version number in some form so the version 
        you are running can be determined, and users know what docs to read.
      </P
><P
>&#13;        <B
CLASS="command"
>global/footer.html.tmpl</B
>:
        This defines the footer that goes on all Bugzilla pages.  Editing
        this is another way to quickly get a distinctive look and feel for
        your Bugzilla installation.
      </P
><P
>&#13;        <B
CLASS="command"
>global/variables.none.tmpl</B
>:
        This defines a list of terms that may be changed in order to
        <SPAN
CLASS="QUOTE"
>"brand"</SPAN
> the Bugzilla instance In this way, terms
        like <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> can be replaced with <SPAN
CLASS="QUOTE"
>"issues"</SPAN
>
        across the whole Bugzilla installation. The name
        <SPAN
CLASS="QUOTE"
>"Bugzilla"</SPAN
> and other words can be customized as well.
      </P
><P
>&#13;        <B
CLASS="command"
>list/table.html.tmpl</B
>:
        This template controls the appearance of the bug lists created
        by Bugzilla. Editing this template allows per-column control of 
        the width and title of a column, the maximum display length of
        each entry, and the wrap behaviour of long entries.
        For long bug lists, Bugzilla inserts a 'break' every 100 bugs by
        default; this behaviour is also controlled by this template, and
        that value can be modified here.
       </P
><P
>&#13;        <B
CLASS="command"
>bug/create/user-message.html.tmpl</B
>:
        This is a message that appears near the top of the bug reporting page.
        By modifying this, you can tell your users how they should report
        bugs.
      </P
><P
>&#13;        <B
CLASS="command"
>bug/process/midair.html.tmpl</B
>:
        This is the page used if two people submit simultaneous changes to the
        same bug.  The second person to submit their changes will get this page
        to tell them what the first person did, and ask if they wish to
        overwrite those changes or go back and revisit the bug.  The default
        title and header on this page read "Mid-air collision detected!"  If
        you work in the aviation industry, or other environment where this
        might be found offensive (yes, we have true stories of this happening)
        you'll want to change this to something more appropriate for your
        environment.
      </P
><P
>&#13;        <B
CLASS="command"
>bug/create/create.html.tmpl</B
> and
        <B
CLASS="command"
>bug/create/comment.txt.tmpl</B
>:
        You may not wish to go to the effort of creating custom fields in
        Bugzilla, yet you want to make sure that each bug report contains
        a number of pieces of important information for which there is not
        a special field. The bug entry system has been designed in an
        extensible fashion to enable you to add arbitrary HTML widgets,
        such as drop-down lists or textboxes, to the bug entry page
        and have their values appear formatted in the initial comment.
        A hidden field that indicates the format should be added inside
        the form in order to make the template functional. Its value should
        be the suffix of the template filename. For example, if the file
        is called <TT
CLASS="filename"
>create-cust.html.tmpl</TT
>, then
        <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#60;input type="hidden" name="format" value="cust"&#62;</PRE
></FONT
></TD
></TR
></TABLE
>
        should be used inside the form.
      </P
><P
>  
        An example of this is the mozilla.org 
        <A
HREF="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi?product=WorldControl&#38;format=guided"
TARGET="_top"
>guided 
        bug submission form</A
>. The code for this comes with the Bugzilla
        distribution as an example for you to copy. It can be found in the
        files 
        <TT
CLASS="filename"
>create-guided.html.tmpl</TT
> and
        <TT
CLASS="filename"
>comment-guided.html.tmpl</TT
>.
      </P
><P
>&#13;        So to use this feature, create a custom template for 
        <TT
CLASS="filename"
>enter_bug.cgi</TT
>. The default template, on which you
        could base it, is 
        <TT
CLASS="filename"
>custom/bug/create/create.html.tmpl</TT
>.
        Call it <TT
CLASS="filename"
>create-&#60;formatname&#62;.html.tmpl</TT
>, and
        in it, add widgets for each piece of information you'd like
        collected - such as a build number, or set of steps to reproduce.
      </P
><P
>&#13;        Then, create a template like 
        <TT
CLASS="filename"
>custom/bug/create/comment.txt.tmpl</TT
>, and call it 
        <TT
CLASS="filename"
>comment-&#60;formatname&#62;.txt.tmpl</TT
>. This 
        template should reference the form fields you have created using
        the syntax <TT
CLASS="filename"
>[% form.&#60;fieldname&#62; %]</TT
>. When a 
        bug report is
        submitted, the initial comment attached to the bug report will be
        formatted according to the layout of this template.
      </P
><P
>&#13;        For example, if your custom enter_bug template had a field
        <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#60;input type="text" name="buildid" size="30"&#62;</PRE
></FONT
></TD
></TR
></TABLE
>
        and then your comment.txt.tmpl had
        <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>BuildID: [% form.buildid %]</PRE
></FONT
></TD
></TR
></TABLE
>
        then something like
        <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>BuildID: 20020303</PRE
></FONT
></TD
></TR
></TABLE
>
        would appear in the initial comment.
      </P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="template-http-accept"
>6.3.6. Configuring Bugzilla to Detect the User's Language</A
></H3
><P
>Bugzilla honours the user's Accept: HTTP header. You can install
      templates in other languages, and Bugzilla will pick the most appropriate
      according to a priority order defined by you. Many
      language templates can be obtained from <A
HREF="http://www.bugzilla.org/download.html#localizations"
TARGET="_top"
>http://www.bugzilla.org/download.html#localizations</A
>. Instructions
      for submitting new languages are also available from that location.
      </P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="cust-change-permissions"
>6.4. Customizing Who Can Change What</A
></H2
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        This feature should be considered experimental; the Bugzilla code you
        will be changing is not stable, and could change or move between 
        versions. Be aware that if you make modifications as outlined here, 
        you may have
        to re-make them or port them if Bugzilla changes internally between
        versions, and you upgrade.
      </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;      Companies often have rules about which employees, or classes of employees,
      are allowed to change certain things in the bug system. For example, 
      only the bug's designated QA Contact may be allowed to VERIFY the bug.
      Bugzilla has been
      designed to make it easy for you to write your own custom rules to define
      who is allowed to make what sorts of value transition.
    </P
><P
>&#13;     By default, assignees, QA owners and users
     with <EM
>editbugs</EM
> privileges can edit all fields of bugs, 
     except group restrictions (unless they are members of the groups they 
     are trying to change). Bug reporters also have the ability to edit some 
     fields, but in a more restrictive manner. Other users, without 
     <EM
>editbugs</EM
> privileges, can not edit 
     bugs, except to comment and add themselves to the CC list.
    </P
><P
>&#13;      For maximum flexibility, customizing this means editing Bugzilla's Perl 
      code. This gives the administrator complete control over exactly who is
      allowed to do what. The relevant method is called
      <TT
CLASS="filename"
>check_can_change_field()</TT
>,
      and is found in <TT
CLASS="filename"
>Bug.pm</TT
> in your
      Bugzilla/ directory. If you open that file and search for
      <SPAN
CLASS="QUOTE"
>"sub check_can_change_field"</SPAN
>, you'll find it.
    </P
><P
>&#13;      This function has been carefully commented to allow you to see exactly
      how it works, and give you an idea of how to make changes to it.
      Certain marked sections should not be changed - these are
      the <SPAN
CLASS="QUOTE"
>"plumbing"</SPAN
> which makes the rest of the function work.
      In between those sections, you'll find snippets of code like:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>    # Allow the assignee to change anything.
    if ($ownerid eq $whoid) {
        return 1;
    }</PRE
></FONT
></TD
></TR
></TABLE
>
      It's fairly obvious what this piece of code does.
    </P
><P
>&#13;      So, how does one go about changing this function? Well, simple changes
      can be made just by removing pieces - for example, if you wanted to 
      prevent any user adding a comment to a bug, just remove the lines marked
      <SPAN
CLASS="QUOTE"
>"Allow anyone to change comments."</SPAN
> If you don't want the
      Reporter to have any special rights on bugs they have filed, just
      remove the entire section that deals with the Reporter.
    </P
><P
>&#13;      More complex customizations are not much harder. Basically, you add
      a check in the right place in the function, i.e. after all the variables
      you are using have been set up. So, don't look at $ownerid before 
      $ownerid has been obtained from the database. You can either add a
      positive check, which returns 1 (allow) if certain conditions are true,
      or a negative check, which returns 0 (deny.) E.g.:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>    if ($field eq "qacontact") {
        if (Bugzilla-&#62;user-&#62;in_group("quality_assurance")) {
            return 1;
        } 
        else {
            return 0;
        }
    }</PRE
></FONT
></TD
></TR
></TABLE
>
      This says that only users in the group "quality_assurance" can change
      the QA Contact field of a bug.
    </P
><P
>&#13;      Getting more weird:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>    if (($field eq "priority") &#38;&#38;
        (Bugzilla-&#62;user-&#62;email =~ /.*\@example\.com$/))
    {
        if ($oldvalue eq "P1") {
            return 1;
        } 
        else {
            return 0;
        }
    }</PRE
></FONT
></TD
></TR
></TABLE
>
      This says that if the user is trying to change the priority field,
      and their email address is @example.com, they can only do so if the
      old value of the field was "P1". Not very useful, but illustrative.
    </P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        If you are modifying <TT
CLASS="filename"
>process_bug.cgi</TT
> in any
        way, do not change the code that is bounded by DO_NOT_CHANGE blocks.
        Doing so could compromise security, or cause your installation to
        stop working entirely.
      </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;      For a list of possible field names, look at the bugs table in the 
      database. If you need help writing custom rules for your organization,
      ask in the newsgroup.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="integration"
>6.5. Integrating Bugzilla with Third-Party Tools</A
></H2
><P
>&#13;      Many utilities and applications can integrate with Bugzilla,
      either on the client- or server-side. None of them are maintained
      by the Bugzilla community, nor are they tested during our
      QA tests, so use them at your own risk. They are listed at
      <A
HREF="https://wiki.mozilla.org/Bugzilla:Addons"
TARGET="_top"
>https://wiki.mozilla.org/Bugzilla:Addons</A
>.
    </P
></DIV
></DIV
><DIV
CLASS="appendix"
><HR><H1
><A
NAME="troubleshooting"
></A
>Appendix A. Troubleshooting</H1
><P
>This section gives solutions to common Bugzilla installation
  problems. If none of the section headings seems to match your
  problem, read the general advice.
  </P
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="general-advice"
>A.1. General Advice</A
></H2
><P
>If you can't get <TT
CLASS="filename"
>checksetup.pl</TT
> to run to 
    completion, it normally explains what's wrong and how to fix it.
    If you can't work it out, or if it's being uncommunicative, post 
    the errors in the 
    <A
HREF="news://news.mozilla.org/mozilla.support.bugzilla"
TARGET="_top"
>mozilla.support.bugzilla</A
>
    newsgroup.
    </P
><P
>If you have made it all the way through
    <A
HREF="#installation"
>Section 2.1</A
> (Installation) and
    <A
HREF="#configuration"
>Section 2.2</A
> (Configuration) but accessing the Bugzilla
    URL doesn't work, the first thing to do is to check your web server error
    log. For Apache, this is often located at
    <TT
CLASS="filename"
>/etc/logs/httpd/error_log</TT
>. The error messages
    you see may be self-explanatory enough to enable you to diagnose and
    fix the problem. If not, see below for some commonly-encountered 
    errors. If that doesn't help, post the errors to the newsgroup.
    </P
><P
>&#13;      Bugzilla can also log all user-based errors (and many code-based errors)
      that occur, without polluting the web server's error log.  To enable
      Bugzilla error logging, create a file that Bugzilla can write to, named
      <TT
CLASS="filename"
>errorlog</TT
>, in the Bugzilla <TT
CLASS="filename"
>data</TT
>
      directory.  Errors will be logged as they occur, and will include the type
      of the error, the IP address and username (if available) of the user who
      triggered the error, and the values of all environment variables; if a
      form was being submitted, the data in the form will also be included.
      To disable error logging, delete or rename the
      <TT
CLASS="filename"
>errorlog</TT
> file.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="trbl-testserver"
>A.2. The Apache web server is not serving Bugzilla pages</A
></H2
><P
>After you have run <B
CLASS="command"
>checksetup.pl</B
> twice,
    run <B
CLASS="command"
>testserver.pl http://yoursite.yourdomain/yoururl</B
>
    to confirm that your web server is configured properly for
    Bugzilla.
    </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;<SAMP
CLASS="prompt"
>bash$</SAMP
> ./testserver.pl http://landfill.bugzilla.org/bugzilla-tip
TEST-OK Webserver is running under group id in $webservergroup.
TEST-OK Got ant picture.
TEST-OK Webserver is executing CGIs.
TEST-OK Webserver is preventing fetch of http://landfill.bugzilla.org/bugzilla-tip/localconfig.
</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="trbl-perlmodule"
>A.3. I installed a Perl module, but 
      <TT
CLASS="filename"
>checksetup.pl</TT
> claims it's not installed!</A
></H2
><P
>This could be caused by one of two things:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>You have two versions of Perl on your machine. You are installing
        modules into one, and Bugzilla is using the other. Rerun the CPAN
        commands (or manual compile) using the full path to Perl from the 
        top of <TT
CLASS="filename"
>checksetup.pl</TT
>. This will make sure you 
        are installing the modules in the right place.
        </P
></LI
><LI
><P
>The permissions on your library directories are set incorrectly.
        They must, at the very least, be readable by the web server user or
        group. It is recommended that they be world readable.
        </P
></LI
></OL
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="trbl-dbdSponge"
>A.4. DBD::Sponge::db prepare failed</A
></H2
><P
>The following error message may appear due to a bug in DBD::mysql
    (over which the Bugzilla team have no control):
    </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> DBD::Sponge::db prepare failed: Cannot determine NUM_OF_FIELDS at D:/Perl/site/lib/DBD/mysql.pm line 248.
  SV = NULL(0x0) at 0x20fc444
  REFCNT = 1
  FLAGS = (PADBUSY,PADMY)
</PRE
></FONT
></TD
></TR
></TABLE
><P
>To fix this, go to 
    <TT
CLASS="filename"
>&#60;path-to-perl&#62;/lib/DBD/sponge.pm</TT
> 
    in your Perl installation and replace
    </P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> my $numFields;
 if ($attribs-&#62;{'NUM_OF_FIELDS'}) {
     $numFields = $attribs-&#62;{'NUM_OF_FIELDS'};
 } elsif ($attribs-&#62;{'NAME'}) {
     $numFields = @{$attribs-&#62;{NAME}};
</PRE
></FONT
></TD
></TR
></TABLE
><P
>with</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> my $numFields;
 if ($attribs-&#62;{'NUM_OF_FIELDS'}) {
     $numFields = $attribs-&#62;{'NUM_OF_FIELDS'};
 } elsif ($attribs-&#62;{'NAMES'}) {
     $numFields = @{$attribs-&#62;{NAMES}};
</PRE
></FONT
></TD
></TR
></TABLE
><P
>(note the S added to NAME.)</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="paranoid-security"
>A.5. cannot chdir(/var/spool/mqueue)</A
></H2
><P
>If you are installing Bugzilla on SuSE Linux, or some other
    distributions with <SPAN
CLASS="QUOTE"
>"paranoid"</SPAN
> security options, it is
    possible that the checksetup.pl script may fail with the error: 
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>cannot chdir(/var/spool/mqueue): Permission denied
</PRE
></FONT
></TD
></TR
></TABLE
>
    </P
><P
>This is because your <TT
CLASS="filename"
>/var/spool/mqueue</TT
>
    directory has a mode of <SAMP
CLASS="computeroutput"
>drwx------</SAMP
>.
    Type <B
CLASS="command"
>chmod 755 <TT
CLASS="filename"
>/var/spool/mqueue</TT
></B
>
    as root to fix this problem. This will allow any process running on your
    machine the ability to <EM
>read</EM
> the
    <TT
CLASS="filename"
>/var/spool/mqueue</TT
> directory.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="trbl-relogin-everyone"
>A.6. Everybody is constantly being forced to relogin</A
></H2
><P
>The most-likely cause is that the <SPAN
CLASS="QUOTE"
>"cookiepath"</SPAN
> parameter
  is not set correctly in the Bugzilla configuration.  You can change this (if
  you're a Bugzilla administrator) from the editparams.cgi page via the web interface.
  </P
><P
>The value of the cookiepath parameter should be the actual directory
  containing your Bugzilla installation, <EM
>as seen by the end-user's
  web browser</EM
>. Leading and trailing slashes are mandatory. You can
  also set the cookiepath to any directory which is a parent of the Bugzilla
  directory (such as '/', the root directory). But you can't put something
  that isn't at least a partial match or it won't work. What you're actually
  doing is restricting the end-user's browser to sending the cookies back only
  to that directory.
  </P
><P
>How do you know if you want your specific Bugzilla directory or the
  whole site?
  </P
><P
>If you have only one Bugzilla running on the server, and you don't
  mind having other applications on the same server with it being able to see
  the cookies (you might be doing this on purpose if you have other things on
  your site that share authentication with Bugzilla), then you'll want to have
  the cookiepath set to "/", or to a sufficiently-high enough directory that
  all of the involved apps can see the cookies.
  </P
><DIV
CLASS="example"
><A
NAME="trbl-relogin-everyone-share"
></A
><P
><B
>Example A-1. Examples of urlbase/cookiepath pairs for sharing login cookies</B
></P
><A
NAME="AEN3090"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;urlbase&nbsp;is&nbsp;<A
HREF="http://bugzilla.mozilla.org/"
TARGET="_top"
>http://bugzilla.mozilla.org/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cookiepath&nbsp;is&nbsp;/<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;urlbase&nbsp;is&nbsp;<A
HREF="http://tools.mysite.tld/bugzilla/"
TARGET="_top"
>http://tools.mysite.tld/bugzilla/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;but&nbsp;you&nbsp;have&nbsp;http://tools.mysite.tld/someotherapp/&nbsp;which&nbsp;shares<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;authentication&nbsp;with&nbsp;your&nbsp;Bugzilla<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cookiepath&nbsp;is&nbsp;/<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
></BLOCKQUOTE
></DIV
><P
>On the other hand, if you have more than one Bugzilla running on the
   server (some people do - we do on landfill) then you need to have the
   cookiepath restricted enough so that the different Bugzillas don't
   confuse their cookies with one another.
   </P
><DIV
CLASS="example"
><A
NAME="trbl-relogin-everyone-restrict"
></A
><P
><B
>Example A-2. Examples of urlbase/cookiepath pairs to restrict the login cookie</B
></P
><A
NAME="AEN3097"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;urlbase&nbsp;is&nbsp;<A
HREF="http://landfill.bugzilla.org/bugzilla-tip/"
TARGET="_top"
>http://landfill.bugzilla.org/bugzilla-tip/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cookiepath&nbsp;is&nbsp;/bugzilla-tip/<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;urlbase&nbsp;is&nbsp;<A
HREF="http://landfill.bugzilla.org/bugzilla-2.16-branch/"
TARGET="_top"
>http://landfill.bugzilla.org/bugzilla-2.16-branch/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cookiepath&nbsp;is&nbsp;/bugzilla-2.16-branch/<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
></BLOCKQUOTE
></DIV
><P
>If you had cookiepath set to <SPAN
CLASS="QUOTE"
>"/"</SPAN
> at any point in the
    past and need to set it to something more restrictive
    (i.e. <SPAN
CLASS="QUOTE"
>"/bugzilla/"</SPAN
>), you can safely do this without
    requiring users to delete their Bugzilla-related cookies in their
    browser (this is true starting with Bugzilla 2.18 and Bugzilla 2.16.5).
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="trbl-index"
>A.7. <TT
CLASS="filename"
>index.cgi</TT
> doesn't show up unless specified in the URL</A
></H2
><P
>&#13;      You probably need to set up your web server in such a way that it
      will serve the index.cgi page as an index page.
    </P
><P
>&#13;      If you are using Apache, you can do this by adding 
      <TT
CLASS="filename"
>index.cgi</TT
> to the end of the 
      <SAMP
CLASS="computeroutput"
>DirectoryIndex</SAMP
> line
      as mentioned in <A
HREF="#http-apache"
>Section 2.2.4.1</A
>.
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="trbl-passwd-encryption"
>A.8. checksetup.pl reports "Client does not support authentication protocol
      requested by server..."</A
></H2
><P
>&#13;      This error is occurring because you are using the new password
      encryption that comes with MySQL 4.1, while your
      <TT
CLASS="filename"
>DBD::mysql</TT
> module was compiled against an
      older version of MySQL. If you recompile <TT
CLASS="filename"
>DBD::mysql</TT
>
      against the current MySQL libraries (or just obtain a newer version
      of this module) then the error may go away.
    </P
><P
>&#13;      If that does not fix the problem, or if you cannot recompile the
      existing module (e.g. you're running Windows) and/or don't want to
      replace it (e.g. you want to keep using a packaged version), then a
      workaround is available from the MySQL docs:
      <A
HREF="http://dev.mysql.com/doc/mysql/en/Old_client.html"
TARGET="_top"
>http://dev.mysql.com/doc/mysql/en/Old_client.html</A
>
    </P
></DIV
></DIV
><DIV
CLASS="appendix"
><HR><H1
><A
NAME="patches"
></A
>Appendix B. Contrib</H1
><P
>&#13;    There are a number of unofficial Bugzilla add-ons in the 
    <TT
CLASS="filename"
>$BUGZILLA_ROOT/contrib/</TT
>
    directory. This section documents them.
  </P
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="cmdline"
>B.1. Command-line Search Interface</A
></H2
><P
>&#13;      There are a suite of Unix utilities for searching Bugzilla from the 
      command line. They live in the 
      <TT
CLASS="filename"
>contrib/cmdline</TT
> directory.
      There are three files - <TT
CLASS="filename"
>query.conf</TT
>,
      <TT
CLASS="filename"
>buglist</TT
> and <TT
CLASS="filename"
>bugs</TT
>.
    </P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        These files pre-date the templatization work done as part of the
        2.16 release, and have not been updated.
      </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;      <TT
CLASS="filename"
>query.conf</TT
> contains the mapping from
      options to field names and comparison types. Quoted option names
      are <SPAN
CLASS="QUOTE"
>"grepped"</SPAN
> for, so it should be easy to edit this
      file. Comments (#) have no effect; you must make sure these lines
      do not contain any quoted <SPAN
CLASS="QUOTE"
>"option"</SPAN
>.
    </P
><P
>&#13;      <TT
CLASS="filename"
>buglist</TT
> is a shell script that submits a
      Bugzilla query and writes the resulting HTML page to stdout.
      It supports both short options, (such as <SPAN
CLASS="QUOTE"
>"-Afoo"</SPAN
>
      or <SPAN
CLASS="QUOTE"
>"-Rbar"</SPAN
>) and long options (such
      as <SPAN
CLASS="QUOTE"
>"--assignedto=foo"</SPAN
> or <SPAN
CLASS="QUOTE"
>"--reporter=bar"</SPAN
>).
      If the first character of an option is not <SPAN
CLASS="QUOTE"
>"-"</SPAN
>, it is
      treated as if it were prefixed with <SPAN
CLASS="QUOTE"
>"--default="</SPAN
>.
    </P
><P
>&#13;      The column list is taken from the COLUMNLIST environment variable.
      This is equivalent to the <SPAN
CLASS="QUOTE"
>"Change Columns"</SPAN
> option
      that is available when you list bugs in buglist.cgi. If you have
      already used Bugzilla, grep for COLUMNLIST in your cookies file
      to see your current COLUMNLIST setting.
    </P
><P
>&#13;      <TT
CLASS="filename"
>bugs</TT
> is a simple shell script which calls
      <TT
CLASS="filename"
>buglist</TT
> and extracts the
      bug numbers from the output. Adding the prefix
      <SPAN
CLASS="QUOTE"
>"http://bugzilla.mozilla.org/buglist.cgi?bug_id="</SPAN
>
      turns the bug list into a working link if any bugs are found.
      Counting bugs is easy. Pipe the results through 
      <B
CLASS="command"
>sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</B
>
    </P
><P
>&#13;      Akkana Peck says she has good results piping 
      <TT
CLASS="filename"
>buglist</TT
> output through 
      <B
CLASS="command"
>w3m -T text/html -dump</B
>
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="cmdline-bugmail"
>B.2. Command-line 'Send Unsent Bug-mail' tool</A
></H2
><P
>&#13;      Within the <TT
CLASS="filename"
>contrib</TT
> directory
      exists a utility with the descriptive (if compact) name
      of <TT
CLASS="filename"
>sendunsentbugmail.pl</TT
>. The purpose of this
      script is, simply, to send out any bug-related mail that should
      have been sent by now, but for one reason or another has not.
    </P
><P
>&#13;      To accomplish this task, <TT
CLASS="filename"
>sendunsentbugmail.pl</TT
> uses
      the same mechanism as the <TT
CLASS="filename"
>sanitycheck.cgi</TT
> script;
      it scans through the entire database looking for bugs with changes that
      were made more than 30 minutes ago, but where there is no record of
      anyone related to that bug having been sent mail. Having compiled a list,
      it then uses the standard rules to determine who gets mail, and sends it
      out.
    </P
><P
>&#13;      As the script runs, it indicates the bug for which it is currently
      sending mail; when it has finished, it gives a numerical count of how
      many mails were sent and how many people were excluded. (Individual
      user names are not recorded or displayed.) If the script produces
      no output, that means no unsent mail was detected.
    </P
><P
>&#13;      <EM
>Usage</EM
>: move the sendunsentbugmail.pl script
      up into the main directory, ensure it has execute permission, and run it
      from the command line (or from a cron job) with no parameters.
    </P
></DIV
></DIV
><DIV
CLASS="appendix"
><HR><H1
><A
NAME="install-perlmodules-manual"
></A
>Appendix C. Manual Installation of Perl Modules</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="modules-manual-instructions"
>C.1. Instructions</A
></H2
><P
>&#13;      If you need to install Perl modules manually, here's how it's done.
      Download the module using the link given in the next section, and then
      apply this magic incantation, as root:
    </P
><P
>  
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
><SAMP
CLASS="prompt"
>bash#</SAMP
> tar -xzvf &#60;module&#62;.tar.gz
<SAMP
CLASS="prompt"
>bash#</SAMP
> cd &#60;module&#62;
<SAMP
CLASS="prompt"
>bash#</SAMP
> perl Makefile.PL
<SAMP
CLASS="prompt"
>bash#</SAMP
> make
<SAMP
CLASS="prompt"
>bash#</SAMP
> make test
<SAMP
CLASS="prompt"
>bash#</SAMP
> make install</PRE
></FONT
></TD
></TR
></TABLE
>
    </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        In order to compile source code under Windows you will need to obtain
        a 'make' utility.  The <B
CLASS="command"
>nmake</B
> utility provided with
        Microsoft Visual C++ may be used.  As an alternative, there is a
        utility called <B
CLASS="command"
>dmake</B
> available from CPAN which is
        written entirely in Perl.
      </P
><P
>&#13;        As described in <A
HREF="#modules-manual-download"
>Section C.2</A
>, however, most
        packages already exist and are available from ActiveState or theory58S.
        We highly recommend that you install them using the ppm GUI available with
        ActiveState and to add the theory58S repository to your list of repositories.
      </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="modules-manual-download"
>C.2. Download Locations</A
></H2
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;        Running Bugzilla on Windows requires the use of ActiveState
        Perl 5.8.1 or higher. Many modules already exist in the core
        distribution of ActiveState Perl. Additional modules can be downloaded
        from <A
HREF="http://theoryx5.uwinnipeg.ca/ppms/"
TARGET="_top"
>http://theoryx5.uwinnipeg.ca/ppms/</A
> if you use
        Perl 5.8.x or from <A
HREF="http://cpan.uwinnipeg.ca/PPMPackages/10xx/"
TARGET="_top"
>http://cpan.uwinnipeg.ca/PPMPackages/10xx/</A
>
        if you use Perl 5.10.x.
      </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;      CGI:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/CGI.pm/"
TARGET="_top"
>http://search.cpan.org/dist/CGI.pm/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://perldoc.perl.org/CGI.html"
TARGET="_top"
>http://perldoc.perl.org/CGI.html</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      Data-Dumper:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/Data-Dumper/"
TARGET="_top"
>http://search.cpan.org/dist/Data-Dumper/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://search.cpan.org/dist/Data-Dumper/Dumper.pm"
TARGET="_top"
>http://search.cpan.org/dist/Data-Dumper/Dumper.pm</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      Date::Format (part of TimeDate):
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/TimeDate/"
TARGET="_top"
>http://search.cpan.org/dist/TimeDate/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://search.cpan.org/dist/TimeDate/lib/Date/Format.pm"
TARGET="_top"
>http://search.cpan.org/dist/TimeDate/lib/Date/Format.pm</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      DBI:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/DBI/"
TARGET="_top"
>http://search.cpan.org/dist/DBI/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://dbi.perl.org/docs/"
TARGET="_top"
>http://dbi.perl.org/docs/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      DBD::mysql:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/DBD-mysql/"
TARGET="_top"
>http://search.cpan.org/dist/DBD-mysql/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://search.cpan.org/dist/DBD-mysql/lib/DBD/mysql.pm"
TARGET="_top"
>http://search.cpan.org/dist/DBD-mysql/lib/DBD/mysql.pm</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      DBD::Pg:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/DBD-Pg/"
TARGET="_top"
>http://search.cpan.org/dist/DBD-Pg/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://search.cpan.org/dist/DBD-Pg/Pg.pm"
TARGET="_top"
>http://search.cpan.org/dist/DBD-Pg/Pg.pm</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      Template-Toolkit:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/Template-Toolkit/"
TARGET="_top"
>http://search.cpan.org/dist/Template-Toolkit/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://www.template-toolkit.org/docs.html"
TARGET="_top"
>http://www.template-toolkit.org/docs.html</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      GD:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/GD/"
TARGET="_top"
>http://search.cpan.org/dist/GD/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://search.cpan.org/dist/GD/GD.pm"
TARGET="_top"
>http://search.cpan.org/dist/GD/GD.pm</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      Template::Plugin::GD:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/Template-GD/"
TARGET="_top"
>http://search.cpan.org/dist/Template-GD/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://www.template-toolkit.org/docs/aqua/Modules/index.html"
TARGET="_top"
>http://www.template-toolkit.org/docs/aqua/Modules/index.html</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      MIME::Parser (part of MIME-tools):
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/MIME-tools/"
TARGET="_top"
>http://search.cpan.org/dist/MIME-tools/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://search.cpan.org/dist/MIME-tools/lib/MIME/Parser.pm"
TARGET="_top"
>http://search.cpan.org/dist/MIME-tools/lib/MIME/Parser.pm</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="modules-manual-optional"
>C.3. Optional Modules</A
></H2
><P
>&#13;      Chart::Lines:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/Chart/"
TARGET="_top"
>http://search.cpan.org/dist/Chart/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://search.cpan.org/dist/Chart/Chart.pod"
TARGET="_top"
>http://search.cpan.org/dist/Chart/Chart.pod</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      GD::Graph:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/GDGraph/"
TARGET="_top"
>http://search.cpan.org/dist/GDGraph/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://search.cpan.org/dist/GDGraph/Graph.pm"
TARGET="_top"
>http://search.cpan.org/dist/GDGraph/Graph.pm</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      GD::Text::Align (part of GD::Text::Util):
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/GDTextUtil/"
TARGET="_top"
>http://search.cpan.org/dist/GDTextUtil/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://search.cpan.org/dist/GDTextUtil/Text/Align.pm"
TARGET="_top"
>http://search.cpan.org/dist/GDTextUtil/Text/Align.pm</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      XML::Twig:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/XML-Twig/"
TARGET="_top"
>http://search.cpan.org/dist/XML-Twig/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://standards.ieee.org/resources/spasystem/twig/twig_stable.html"
TARGET="_top"
>http://standards.ieee.org/resources/spasystem/twig/twig_stable.html</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
><P
>&#13;      PatchReader:
      <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/author/JKEISER/PatchReader/"
TARGET="_top"
>http://search.cpan.org/author/JKEISER/PatchReader/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://www.johnkeiser.com/mozilla/Patch_Viewer.html"
TARGET="_top"
>http://www.johnkeiser.com/mozilla/Patch_Viewer.html</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
>
    </P
></DIV
></DIV
><DIV
CLASS="appendix"
><HR><H1
><A
NAME="gfdl"
></A
>Appendix D. GNU Free Documentation License</H1
><P
>Version 1.1, March 2000</P
><A
NAME="AEN3255"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
    Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and
    distribute verbatim copies of this license document, but changing it is
    not allowed.</P
></BLOCKQUOTE
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-0"
>0. Preamble</A
></H2
><P
>The purpose of this License is to make a manual, textbook, or other
    written document "free" in the sense of freedom: to assure everyone the
    effective freedom to copy and redistribute it, with or without modifying
    it, either commercially or noncommercially. Secondarily, this License
    preserves for the author and publisher a way to get credit for their
    work, while not being considered responsible for modifications made by
    others.</P
><P
>This License is a kind of "copyleft", which means that derivative
    works of the document must themselves be free in the same sense. It
    complements the GNU General Public License, which is a copyleft license
    designed for free software.</P
><P
>We have designed this License in order to use it for manuals for
    free software, because free software needs free documentation: a free
    program should come with manuals providing the same freedoms that the
    software does. But this License is not limited to software manuals; it
    can be used for any textual work, regardless of subject matter or whether
    it is published as a printed book. We recommend this License principally
    for works whose purpose is instruction or reference.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-1"
>1. Applicability and Definition</A
></H2
><P
>This License applies to any manual or other work that contains a
    notice placed by the copyright holder saying it can be distributed under
    the terms of this License. The "Document", below, refers to any such
    manual or work. Any member of the public is a licensee, and is addressed
    as "you".</P
><P
>A "Modified Version" of the Document means any work containing the
    Document or a portion of it, either copied verbatim, or with
    modifications and/or translated into another language.</P
><P
>A "Secondary Section" is a named appendix or a front-matter section
    of the Document that deals exclusively with the relationship of the
    publishers or authors of the Document to the Document's overall subject
    (or to related matters) and contains nothing that could fall directly
    within that overall subject. (For example, if the Document is in part a
    textbook of mathematics, a Secondary Section may not explain any
    mathematics.) The relationship could be a matter of historical connection
    with the subject or with related matters, or of legal, commercial,
    philosophical, ethical or political position regarding them.</P
><P
>The "Invariant Sections" are certain Secondary Sections whose
    titles are designated, as being those of Invariant Sections, in the
    notice that says that the Document is released under this License.</P
><P
>The "Cover Texts" are certain short passages of text that are
    listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says
    that the Document is released under this License.</P
><P
>A "Transparent" copy of the Document means a machine-readable copy,
    represented in a format whose specification is available to the general
    public, whose contents can be viewed and edited directly and
    straightforwardly with generic text editors or (for images composed of
    pixels) generic paint programs or (for drawings) some widely available
    drawing editor, and that is suitable for input to text formatters or for
    automatic translation to a variety of formats suitable for input to text
    formatters. A copy made in an otherwise Transparent file format whose
    markup has been designed to thwart or discourage subsequent modification
    by readers is not Transparent. A copy that is not "Transparent" is called
    "Opaque".</P
><P
>Examples of suitable formats for Transparent copies include plain
    ASCII without markup, Texinfo input format, LaTeX input format, SGML or
    XML using a publicly available DTD, and standard-conforming simple HTML
    designed for human modification. Opaque formats include PostScript, PDF,
    proprietary formats that can be read and edited only by proprietary word
    processors, SGML or XML for which the DTD and/or processing tools are not
    generally available, and the machine-generated HTML produced by some word
    processors for output purposes only.</P
><P
>The "Title Page" means, for a printed book, the title page itself,
    plus such following pages as are needed to hold, legibly, the material
    this License requires to appear in the title page. For works in formats
    which do not have any title page as such, "Title Page" means the text
    near the most prominent appearance of the work's title, preceding the
    beginning of the body of the text.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-2"
>2. Verbatim Copying</A
></H2
><P
>You may copy and distribute the Document in any medium, either
    commercially or noncommercially, provided that this License, the
    copyright notices, and the license notice saying this License applies to
    the Document are reproduced in all copies, and that you add no other
    conditions whatsoever to those of this License. You may not use technical
    measures to obstruct or control the reading or further copying of the
    copies you make or distribute. However, you may accept compensation in
    exchange for copies. If you distribute a large enough number of copies
    you must also follow the conditions in section 3.</P
><P
>You may also lend copies, under the same conditions stated above,
    and you may publicly display copies.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-3"
>3. Copying in Quantity</A
></H2
><P
>If you publish printed copies of the Document numbering more than
    100, and the Document's license notice requires Cover Texts, you must
    enclose the copies in covers that carry, clearly and legibly, all these
    Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts
    on the back cover. Both covers must also clearly and legibly identify you
    as the publisher of these copies. The front cover must present the full
    title with all words of the title equally prominent and visible. You may
    add other material on the covers in addition. Copying with changes
    limited to the covers, as long as they preserve the title of the Document
    and satisfy these conditions, can be treated as verbatim copying in other
    respects.</P
><P
>If the required texts for either cover are too voluminous to fit
    legibly, you should put the first ones listed (as many as fit reasonably)
    on the actual cover, and continue the rest onto adjacent pages.</P
><P
>If you publish or distribute Opaque copies of the Document
    numbering more than 100, you must either include a machine-readable
    Transparent copy along with each Opaque copy, or state in or with each
    Opaque copy a publicly-accessible computer-network location containing a
    complete Transparent copy of the Document, free of added material, which
    the general network-using public has access to download anonymously at no
    charge using public-standard network protocols. If you use the latter
    option, you must take reasonably prudent steps, when you begin
    distribution of Opaque copies in quantity, to ensure that this
    Transparent copy will remain thus accessible at the stated location until
    at least one year after the last time you distribute an Opaque copy
    (directly or through your agents or retailers) of that edition to the
    public.</P
><P
>It is requested, but not required, that you contact the authors of
    the Document well before redistributing any large number of copies, to
    give them a chance to provide you with an updated version of the
    Document.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-4"
>4. Modifications</A
></H2
><P
>You may copy and distribute a Modified Version of the Document
    under the conditions of sections 2 and 3 above, provided that you release
    the Modified Version under precisely this License, with the Modified
    Version filling the role of the Document, thus licensing distribution and
    modification of the Modified Version to whoever possesses a copy of it.
    In addition, you must do these things in the Modified Version:</P
><P
></P
><OL
TYPE="A"
><LI
><P
>Use in the Title Page (and on the covers, if any) a title
        distinct from that of the Document, and from those of previous
        versions (which should, if there were any, be listed in the History
        section of the Document). You may use the same title as a previous
        version if the original publisher of that version gives
        permission.</P
></LI
><LI
><P
>List on the Title Page, as authors, one or more persons or
        entities responsible for authorship of the modifications in the
        Modified Version, together with at least five of the principal
        authors of the Document (all of its principal authors, if it has less
        than five).</P
></LI
><LI
><P
>State on the Title page the name of the publisher of the
        Modified Version, as the publisher.</P
></LI
><LI
><P
>Preserve all the copyright notices of the Document.</P
></LI
><LI
><P
>Add an appropriate copyright notice for your modifications
        adjacent to the other copyright notices.</P
></LI
><LI
><P
>Include, immediately after the copyright notices, a license
        notice giving the public permission to use the Modified Version under
        the terms of this License, in the form shown in the Addendum
        below.</P
></LI
><LI
><P
>Preserve in that license notice the full lists of Invariant
        Sections and required Cover Texts given in the Document's license
        notice.</P
></LI
><LI
><P
>Include an unaltered copy of this License.</P
></LI
><LI
><P
>Preserve the section entitled "History", and its title, and add
        to it an item stating at least the title, year, new authors, and
        publisher of the Modified Version as given on the Title Page. If
        there is no section entitled "History" in the Document, create one
        stating the title, year, authors, and publisher of the Document as
        given on its Title Page, then add an item describing the Modified
        Version as stated in the previous sentence.</P
></LI
><LI
><P
>Preserve the network location, if any, given in the Document
        for public access to a Transparent copy of the Document, and likewise
        the network locations given in the Document for previous versions it
        was based on. These may be placed in the "History" section. You may
        omit a network location for a work that was published at least four
        years before the Document itself, or if the original publisher of the
        version it refers to gives permission.</P
></LI
><LI
><P
>In any section entitled "Acknowledgements" or "Dedications",
        preserve the section's title, and preserve in the section all the
        substance and tone of each of the contributor acknowledgements and/or
        dedications given therein.</P
></LI
><LI
><P
>Preserve all the Invariant Sections of the Document, unaltered
        in their text and in their titles. Section numbers or the equivalent
        are not considered part of the section titles.</P
></LI
><LI
><P
>Delete any section entitled "Endorsements". Such a section may
        not be included in the Modified Version.</P
></LI
><LI
><P
>Do not retitle any existing section as "Endorsements" or to
        conflict in title with any Invariant Section.</P
></LI
></OL
><P
>If the Modified Version includes new front-matter sections or
    appendices that qualify as Secondary Sections and contain no material
    copied from the Document, you may at your option designate some or all of
    these sections as invariant. To do this, add their titles to the list of
    Invariant Sections in the Modified Version's license notice. These titles
    must be distinct from any other section titles.</P
><P
>You may add a section entitled "Endorsements", provided it contains
    nothing but endorsements of your Modified Version by various parties--for
    example, statements of peer review or that the text has been approved by
    an organization as the authoritative definition of a standard.</P
><P
>You may add a passage of up to five words as a Front-Cover Text,
    and a passage of up to 25 words as a Back-Cover Text, to the end of the
    list of Cover Texts in the Modified Version. Only one passage of
    Front-Cover Text and one of Back-Cover Text may be added by (or through
    arrangements made by) any one entity. If the Document already includes a
    cover text for the same cover, previously added by you or by arrangement
    made by the same entity you are acting on behalf of, you may not add
    another; but you may replace the old one, on explicit permission from the
    previous publisher that added the old one.</P
><P
>The author(s) and publisher(s) of the Document do not by this
    License give permission to use their names for publicity for or to assert
    or imply endorsement of any Modified Version.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-5"
>5. Combining Documents</A
></H2
><P
>You may combine the Document with other documents released under
    this License, under the terms defined in section 4 above for modified
    versions, provided that you include in the combination all of the
    Invariant Sections of all of the original documents, unmodified, and list
    them all as Invariant Sections of your combined work in its license
    notice.</P
><P
>The combined work need only contain one copy of this License, and
    multiple identical Invariant Sections may be replaced with a single copy.
    If there are multiple Invariant Sections with the same name but different
    contents, make the title of each such section unique by adding at the end
    of it, in parentheses, the name of the original author or publisher of
    that section if known, or else a unique number. Make the same adjustment
    to the section titles in the list of Invariant Sections in the license
    notice of the combined work.</P
><P
>In the combination, you must combine any sections entitled
    "History" in the various original documents, forming one section entitled
    "History"; likewise combine any sections entitled "Acknowledgements", and
    any sections entitled "Dedications". You must delete all sections
    entitled "Endorsements."</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-6"
>6. Collections of Documents</A
></H2
><P
>You may make a collection consisting of the Document and other
    documents released under this License, and replace the individual copies
    of this License in the various documents with a single copy that is
    included in the collection, provided that you follow the rules of this
    License for verbatim copying of each of the documents in all other
    respects.</P
><P
>You may extract a single document from such a collection, and
    distribute it individually under this License, provided you insert a copy
    of this License into the extracted document, and follow this License in
    all other respects regarding verbatim copying of that document.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-7"
>7. Aggregation with Independent Works</A
></H2
><P
>A compilation of the Document or its derivatives with other
    separate and independent documents or works, in or on a volume of a
    storage or distribution medium, does not as a whole count as a Modified
    Version of the Document, provided no compilation copyright is claimed for
    the compilation. Such a compilation is called an "aggregate", and this
    License does not apply to the other self-contained works thus compiled
    with the Document, on account of their being thus compiled, if they are
    not themselves derivative works of the Document.</P
><P
>If the Cover Text requirement of section 3 is applicable to these
    copies of the Document, then if the Document is less than one quarter of
    the entire aggregate, the Document's Cover Texts may be placed on covers
    that surround only the Document within the aggregate. Otherwise they must
    appear on covers around the whole aggregate.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-8"
>8. Translation</A
></H2
><P
>Translation is considered a kind of modification, so you may
    distribute translations of the Document under the terms of section 4.
    Replacing Invariant Sections with translations requires special
    permission from their copyright holders, but you may include translations
    of some or all Invariant Sections in addition to the original versions of
    these Invariant Sections. You may include a translation of this License
    provided that you also include the original English version of this
    License. In case of a disagreement between the translation and the
    original English version of this License, the original English version
    will prevail.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-9"
>9. Termination</A
></H2
><P
>You may not copy, modify, sublicense, or distribute the Document
    except as expressly provided for under this License. Any other attempt to
    copy, modify, sublicense or distribute the Document is void, and will
    automatically terminate your rights under this License. However, parties
    who have received copies, or rights, from you under this License will not
    have their licenses terminated so long as such parties remain in full
    compliance.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-10"
>10. Future Revisions of this License</A
></H2
><P
>The Free Software Foundation may publish new, revised versions of
    the GNU Free Documentation License from time to time. Such new versions
    will be similar in spirit to the present version, but may differ in
    detail to address new problems or concerns. See 
    <A
HREF="http://www.gnu.org/copyleft/"
TARGET="_top"
>http://www.gnu.org/copyleft/</A
>.</P
><P
>Each version of the License is given a distinguishing version
    number. If the Document specifies that a particular numbered version of
    this License "or any later version" applies to it, you have the option of
    following the terms and conditions either of that specified version or of
    any later version that has been published (not as a draft) by the Free
    Software Foundation. If the Document does not specify a version number of
    this License, you may choose any version ever published (not as a draft)
    by the Free Software Foundation.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="gfdl-howto"
>How to use this License for your documents</A
></H2
><P
>To use this License in a document you have written, include a copy
    of the License in the document and put the following copyright and
    license notices just after the title page:</P
><A
NAME="AEN3345"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
      distribute and/or modify this document under the terms of the GNU Free
      Documentation License, Version 1.1 or any later version published by
      the Free Software Foundation; with the Invariant Sections being LIST
      THEIR TITLES, with the Front-Cover Texts being LIST, and with the
      Back-Cover Texts being LIST. A copy of the license is included in the
      section entitled "GNU Free Documentation License".</P
></BLOCKQUOTE
><P
>If you have no Invariant Sections, write "with no Invariant
    Sections" instead of saying which ones are invariant. If you have no
    Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover
    Texts being LIST"; likewise for Back-Cover Texts.</P
><P
>If your document contains nontrivial examples of program code, we
    recommend releasing these examples in parallel under your choice of free
    software license, such as the GNU General Public License, to permit their
    use in free software.</P
></DIV
></DIV
><DIV
CLASS="GLOSSARY"
><H1
><A
NAME="glossary"
></A
>Glossary</H1
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="AEN3350"
>0-9, high ascii</A
></H1
><DL
><DT
><A
NAME="gloss-htaccess"
></A
><B
>.htaccess</B
></DT
><DD
><P
>Apache web server, and other NCSA-compliant web servers,
        observe the convention of using files in directories called 
        <TT
CLASS="filename"
>.htaccess</TT
>

        to restrict access to certain files. In Bugzilla, they are used
        to keep secret files which would otherwise
        compromise your installation - e.g. the 
        <TT
CLASS="filename"
>localconfig</TT
>
        file contains the password to your database.
        curious.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-a"
>A</A
></H1
><DL
><DT
><A
NAME="gloss-apache"
></A
><B
>Apache</B
></DT
><DD
><P
>In this context, Apache is the web server most commonly used
        for serving up Bugzilla 
        pages. Contrary to popular belief, the apache web server has nothing
        to do with the ancient and noble Native American tribe, but instead
        derived its name from the fact that it was 
        <SPAN
CLASS="QUOTE"
>"a patchy"</SPAN
>
        version of the original 
        <ACRONYM
CLASS="acronym"
>NCSA</ACRONYM
>
        world-wide-web server.</P
><P
></P
><DIV
CLASS="variablelist"
><P
><B
>Useful Directives when configuring Bugzilla</B
></P
><DL
><DT
><SAMP
CLASS="computeroutput"
><A
HREF="http://httpd.apache.org/docs-2.0/mod/core.html#addhandler"
TARGET="_top"
>AddHandler</A
></SAMP
></DT
><DD
><P
>Tell Apache that it's OK to run CGI scripts.</P
></DD
><DT
><SAMP
CLASS="computeroutput"
><A
HREF="http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride"
TARGET="_top"
>AllowOverride</A
></SAMP
>, <SAMP
CLASS="computeroutput"
><A
HREF="http://httpd.apache.org/docs-2.0/mod/core.html#options"
TARGET="_top"
>Options</A
></SAMP
></DT
><DD
><P
>These directives are used to tell Apache many things about
              the directory they apply to. For Bugzilla's purposes, we need
              them to allow script execution and <TT
CLASS="filename"
>.htaccess</TT
>
              overrides.
              </P
></DD
><DT
><SAMP
CLASS="computeroutput"
><A
HREF="http://httpd.apache.org/docs-2.0/mod/mod_dir.html#directoryindex"
TARGET="_top"
>DirectoryIndex</A
></SAMP
></DT
><DD
><P
>Used to tell Apache what files are indexes. If you can
              not add <TT
CLASS="filename"
>index.cgi</TT
> to the list of valid files,
              you'll need to set <SAMP
CLASS="computeroutput"
>$index_html</SAMP
> to
              1 in <TT
CLASS="filename"
>localconfig</TT
> so
              <B
CLASS="command"
>./checksetup.pl</B
> will create an
              <TT
CLASS="filename"
>index.html</TT
> that redirects to
              <TT
CLASS="filename"
>index.cgi</TT
>.
              </P
></DD
><DT
><SAMP
CLASS="computeroutput"
><A
HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
TARGET="_top"
>ScriptInterpreterSource</A
></SAMP
></DT
><DD
><P
>Used when running Apache on windows so the shebang line
              doesn't have to be changed in every Bugzilla script.
              </P
></DD
></DL
></DIV
><P
>For more information about how to configure Apache for Bugzilla,
        see <A
HREF="#http-apache"
>Section 2.2.4.1</A
>.
        </P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-b"
>B</A
></H1
><DL
><DT
><B
>Bug</B
></DT
><DD
><P
>A 
        <SPAN
CLASS="QUOTE"
>"bug"</SPAN
>

        in Bugzilla refers to an issue entered into the database which has an
        associated number, assignments, comments, etc. Some also refer to a 
        <SPAN
CLASS="QUOTE"
>"tickets"</SPAN
>
        or 
        <SPAN
CLASS="QUOTE"
>"issues"</SPAN
>; 
        in the context of Bugzilla, they are synonymous.</P
></DD
><DT
><B
>Bug Number</B
></DT
><DD
><P
>Each Bugzilla bug is assigned a number that uniquely identifies
        that bug. The bug associated with a bug number can be pulled up via a
        query, or easily from the very front page by typing the number in the
        "Find" box.</P
></DD
><DT
><A
NAME="gloss-bugzilla"
></A
><B
>Bugzilla</B
></DT
><DD
><P
>Bugzilla is the world-leading free software bug tracking system.
        </P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-c"
>C</A
></H1
><DL
><DT
><A
NAME="gloss-cgi"
></A
><B
>Common Gateway Interface</B
></DT
> (CGI)<DD
><P
><ACRONYM
CLASS="acronym"
>CGI</ACRONYM
> is an acronym for Common Gateway Interface. This is
        a standard for interfacing an external application with a web server. Bugzilla
        is an example of a <ACRONYM
CLASS="acronym"
>CGI</ACRONYM
> application.
        </P
></DD
><DT
><A
NAME="gloss-component"
></A
><B
>Component</B
></DT
><DD
><P
>A Component is a subsection of a Product. It should be a narrow
        category, tailored to your organization. All Products must contain at
        least one Component (and, as a matter of fact, creating a Product
        with no Components will create an error in Bugzilla).</P
></DD
><DT
><A
NAME="gloss-cpan"
></A
><B
>Comprehensive Perl Archive Network</B
></DT
> (CPAN)<DD
><P
>&#13;        <ACRONYM
CLASS="acronym"
>CPAN</ACRONYM
>

        stands for the 
        <SPAN
CLASS="QUOTE"
>"Comprehensive Perl Archive Network"</SPAN
>. 
        CPAN maintains a large number of extremely useful 
        <I
CLASS="glossterm"
>Perl</I
>
        modules - encapsulated chunks of code for performing a
        particular task.</P
></DD
><DT
><A
NAME="gloss-contrib"
></A
><B
><TT
CLASS="filename"
>contrib</TT
></B
></DT
><DD
><P
>The <TT
CLASS="filename"
>contrib</TT
> directory is
        a location to put scripts that have been contributed to Bugzilla but
        are not a part of the official distribution. These scripts are written
        by third parties and may be in languages other than perl. For those
        that are in perl, there may be additional modules or other requirements
        than those of the official distribution.
        <DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Scripts in the <TT
CLASS="filename"
>contrib</TT
>
          directory are not officially supported by the Bugzilla team and may
          break in between versions.
          </P
></TD
></TR
></TABLE
></DIV
>
        </P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-d"
>D</A
></H1
><DL
><DT
><A
NAME="gloss-daemon"
></A
><B
>daemon</B
></DT
><DD
><P
>A daemon is a computer program which runs in the background. In
        general, most daemons are started at boot time via System V init
        scripts, or through RC scripts on BSD-based systems. 
        <I
CLASS="glossterm"
>mysqld</I
>, 
        the MySQL server, and 
        <I
CLASS="glossterm"
>apache</I
>, 
        a web server, are generally run as daemons.</P
></DD
><DT
><A
NAME="gloss-dos"
></A
><B
>DOS Attack</B
></DT
><DD
><P
>A DOS, or Denial of Service attack, is when a user attempts to
        deny access to a web server by repeatedly accessing a page or sending
        malformed requests to a webserver. A D-DOS, or
        Distributed Denial of Service attack, is when these requests come
        from multiple sources at the same time. Unfortunately, these are much
        more difficult to defend against.
        </P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-g"
>G</A
></H1
><DL
><DT
><A
NAME="gloss-groups"
></A
><B
>Groups</B
></DT
><DD
><P
>The word 
        <SPAN
CLASS="QUOTE"
>"Groups"</SPAN
>

        has a very special meaning to Bugzilla. Bugzilla's main security
        mechanism comes by placing users in groups, and assigning those
        groups certain privileges to view bugs in particular
        <I
CLASS="glossterm"
>Products</I
>
        in the 
        <I
CLASS="glossterm"
>Bugzilla</I
>
        database.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-j"
>J</A
></H1
><DL
><DT
><A
NAME="gloss-javascript"
></A
><B
>JavaScript</B
></DT
><DD
><P
>JavaScript is cool, we should talk about it.
        </P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-m"
>M</A
></H1
><DL
><DT
><A
NAME="gloss-mta"
></A
><B
>Message Transport Agent</B
></DT
> (MTA)<DD
><P
>A Message Transport Agent is used to control the flow of email on a system.
        The <A
HREF="http://search.cpan.org/dist/Email-Send/lib/Email/Send.pm"
TARGET="_top"
>Email::Send</A
>
        Perl module, which Bugzilla uses to send email, can be configured to
        use many different underlying implementations for actually sending the
        mail using the <CODE
CLASS="option"
>mail_delivery_method</CODE
> parameter.
        </P
></DD
><DT
><A
NAME="gloss-mysql"
></A
><B
>MySQL</B
></DT
><DD
><P
>MySQL is currently the required
        <A
HREF="#gloss-rdbms"
><I
CLASS="glossterm"
>RDBMS</I
></A
> for Bugzilla. MySQL
        can be downloaded from <A
HREF="http://www.mysql.com"
TARGET="_top"
>http://www.mysql.com</A
>. While you
        should familiarize yourself with all of the documentation, some high
        points are:
        </P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><A
HREF="http://www.mysql.com/doc/en/Backup.html"
TARGET="_top"
>Backup</A
></DT
><DD
><P
>Methods for backing up your Bugzilla database.
              </P
></DD
><DT
><A
HREF="http://www.mysql.com/doc/en/Option_files.html"
TARGET="_top"
>Option Files</A
></DT
><DD
><P
>Information about how to configure MySQL using
              <TT
CLASS="filename"
>my.cnf</TT
>.
              </P
></DD
><DT
><A
HREF="http://www.mysql.com/doc/en/Privilege_system.html"
TARGET="_top"
>Privilege System</A
></DT
><DD
><P
>Information about how to protect your MySQL server.
              </P
></DD
></DL
></DIV
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-p"
>P</A
></H1
><DL
><DT
><A
NAME="gloss-ppm"
></A
><B
>Perl Package Manager</B
></DT
> (PPM)<DD
><P
><A
HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/PPM/"
TARGET="_top"
>http://aspn.activestate.com/ASPN/Downloads/ActivePerl/PPM/</A
>
        </P
></DD
><DT
><B
>Product</B
></DT
><DD
><P
>A Product is a broad category of types of bugs, normally
        representing a single piece of software or entity. In general,
        there are several Components to a Product. A Product may define a
        group (used for security) for all bugs entered into
        its Components.</P
></DD
><DT
><B
>Perl</B
></DT
><DD
><P
>First written by Larry Wall, Perl is a remarkable program
        language. It has the benefits of the flexibility of an interpreted
        scripting language (such as shell script), combined with the speed
        and power of a compiled language, such as C. 
        <I
CLASS="glossterm"
>Bugzilla</I
>

        is maintained in Perl.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-q"
>Q</A
></H1
><DL
><DT
><B
>QA</B
></DT
><DD
><P
>&#13;        <SPAN
CLASS="QUOTE"
>"QA"</SPAN
>, 
        <SPAN
CLASS="QUOTE"
>"Q/A"</SPAN
>, and 
        <SPAN
CLASS="QUOTE"
>"Q.A."</SPAN
>
        are short for 
        <SPAN
CLASS="QUOTE"
>"Quality Assurance"</SPAN
>. 
        In most large software development organizations, there is a team
        devoted to ensuring the product meets minimum standards before
        shipping. This team will also generally want to track the progress of
        bugs over their life cycle, thus the need for the 
        <SPAN
CLASS="QUOTE"
>"QA Contact"</SPAN
>

        field in a bug.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-r"
>R</A
></H1
><DL
><DT
><A
NAME="gloss-rdbms"
></A
><B
>Relational DataBase Management System</B
></DT
> (RDBMS)<DD
><P
>A relational database management system is a database system
        that stores information in tables that are related to each other.
        </P
></DD
><DT
><A
NAME="gloss-regexp"
></A
><B
>Regular Expression</B
></DT
> (regexp)<DD
><P
>A regular expression is an expression used for pattern matching.
              <A
HREF="http://perldoc.com/perl5.6/pod/perlre.html#Regular-Expressions"
TARGET="_top"
>Documentation</A
>
        </P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-s"
>S</A
></H1
><DL
><DT
><A
NAME="gloss-service"
></A
><B
>Service</B
></DT
><DD
><P
>In Windows NT environment, a boot-time background application
        is referred to as a service. These are generally managed through the
        control panel while logged in as an account with
        <SPAN
CLASS="QUOTE"
>"Administrator"</SPAN
> level capabilities. For more
        information, consult your Windows manual or the MSKB.
        </P
></DD
><DT
><B
>&#13;        <ACRONYM
CLASS="acronym"
>SGML</ACRONYM
>
      </B
></DT
><DD
><P
>&#13;        <ACRONYM
CLASS="acronym"
>SGML</ACRONYM
>

        stands for 
        <SPAN
CLASS="QUOTE"
>"Standard Generalized Markup Language"</SPAN
>. 
        Created in the 1980's to provide an extensible means to maintain
        documentation based upon content instead of presentation, 
        <ACRONYM
CLASS="acronym"
>SGML</ACRONYM
>

        has withstood the test of time as a robust, powerful language. 
        <I
CLASS="glossterm"
>&#13;          <ACRONYM
CLASS="acronym"
>XML</ACRONYM
>
        </I
>

        is the 
        <SPAN
CLASS="QUOTE"
>"baby brother"</SPAN
>

        of SGML; any valid 
        <ACRONYM
CLASS="acronym"
>XML</ACRONYM
>

        document it, by definition, a valid 
        <ACRONYM
CLASS="acronym"
>SGML</ACRONYM
>

        document. The document you are reading is written and maintained in 
        <ACRONYM
CLASS="acronym"
>SGML</ACRONYM
>, 
        and is also valid 
        <ACRONYM
CLASS="acronym"
>XML</ACRONYM
>

        if you modify the Document Type Definition.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-t"
>T</A
></H1
><DL
><DT
><A
NAME="gloss-target-milestone"
></A
><B
>Target Milestone</B
></DT
><DD
><P
>Target Milestones are Product goals. They are configurable on a
        per-Product basis. Most software development houses have a concept of
        
        <SPAN
CLASS="QUOTE"
>"milestones"</SPAN
>

        where the people funding a project expect certain functionality on
        certain dates. Bugzilla facilitates meeting these milestones by
        giving you the ability to declare by which milestone a bug will be
        fixed, or an enhancement will be implemented.</P
></DD
><DT
><A
NAME="gloss-tcl"
></A
><B
>Tool Command Language</B
></DT
> (TCL)<DD
><P
>TCL is an open source scripting language available for Windows,
        Macintosh, and Unix based systems. Bugzilla 1.0 was written in TCL but
        never released. The first release of Bugzilla was 2.0, which was when
        it was ported to perl.
        </P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-z"
>Z</A
></H1
><DL
><DT
><A
NAME="gloss-zarro"
></A
><B
>Zarro Boogs Found</B
></DT
><DD
><P
>This is just a goofy way of saying that there were no bugs
        found matching your query. When asked to explain this message,
        Terry had the following to say:
        </P
><A
NAME="AEN3591"
></A
><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
CELLPADDING="0"
CLASS="BLOCKQUOTE"
><TR
><TD
WIDTH="10%"
VALIGN="TOP"
>&nbsp;</TD
><TD
VALIGN="TOP"
><P
>I've been asked to explain this ... way back when, when
          Netscape released version 4.0 of its browser, we had a release
          party.  Naturally, there had been a big push to try and fix every
          known bug before the release. Naturally, that hadn't actually
          happened.  (This is not unique to Netscape or to 4.0; the same thing
          has happened with every software project I've ever seen.)  Anyway,
          at the release party, T-shirts were handed out that said something
          like "Netscape 4.0: Zarro Boogs". Just like the software, the
          T-shirt had no known bugs.  Uh-huh.
          </P
><P
>So, when you query for a list of bugs, and it gets no results,
          you can think of this as a friendly reminder.  Of *course* there are
          bugs matching your query, they just aren't in the bugsystem yet...
          </P
></TD
><TD
WIDTH="10%"
VALIGN="TOP"
>&nbsp;</TD
></TR
><TR
><TD
COLSPAN="2"
ALIGN="RIGHT"
VALIGN="TOP"
>--<SPAN
CLASS="attribution"
>Terry Weissman</SPAN
></TD
><TD
WIDTH="10%"
>&nbsp;</TD
></TR
></TABLE
></DD
></DL
></DIV
></DIV
></DIV
></BODY
></HTML
>