Bugzilla is one example of a class of programs called "Defect Tracking
Systems", or, more commonly, "Bug-Tracking Systems". Defect Tracking
Systems allow individual or groups of developers to keep track of
outstanding bugs in their product effectively.
Bugzilla has matured immensely, and now boasts many advanced features.
These include:
* integrated, product-based granular security schema
* inter-bug dependencies and dependency graphing
* advanced reporting capabilities
* a robust, stable RDBMS back-end
* extensive configurability
* a very well-understood and well-thought-out natural bug resolution
protocol
* email, XML, console, and HTTP APIs
* available integration with automated software configuration
management systems, including Perforce and CVS (through the
Bugzilla email interface and checkin/checkout scripts)
* too many more features to list
WWW: http://www.bugzilla.org/
===> The following configuration options are available for bugzilla42-4.2.9:
DOCS=on: Build and/or install documentation
MODPERL=off: mod_perl support
====> Options available for the group UI
PATCH_VIEWER=on: Patch Viewer
MORE_HTML=on: More HTML in Product/Group Descriptions
====> Database Engine
MYSQL=off: MySQL database support
PGSQL=off: PostgreSQL database support
SQLITE=off: SQLite database support
====> Reports and Charts
GRAPHVIZ=off: Graphviz support
GRAPH_REPORTS=on: Graphical Reports
CHARTING_MODULES=on: Bug charting support
====> Attachment handling
BMP2PNG=off: BMP Attachments to PNGs
====> Email handling
INBOUND_EMAIL=off: Inbound Email
MAIL_QUEUEING=off: Mail Queueing
====> Web Services
XMLRPC=off: XML-RPC Interface
JSONRPC=off: JSON-RPC Interface
====> Alternative Authentication
LDAP=off: LDAP support
RADIUS=off: RADIUS protocol support
====> Administration
MOVE_BUGZ=off: Move Bugs Between Installations
EXPORT_IMPORT=off: Import/export bugs (via XML)
CONTRIB=on: Install user-contributed scripts
===> Use 'make config' to modify these settings
Remove expired ports:
2014-06-20 mail/sastatd: Superseded by sysutils/p5-Tail-Stat
2014-06-20 www/mod_ruby: Only for threadless ruby
2014-06-20 textproc/eruby: Only for threadless ruby, use ruby-gem erubis instead
2014-06-20 mail/p5-FuzzyOcr: Unmaintained upstream, no ports depending on it.
Use mail/p5-FuzzyOcr-devel instead
2014-06-21 devel/bugzilla40
2014-06-21 devel/bugzilla42
- distfiles where regenerated (wrong dependency list in the documentation)
- because there will no upstream fixes for CVE-2014-1517 mark bugzilla40 /
bugzilla42 forbidden and set expiration date to 2014-06-21
- fix the GRAPHVIZ OPTION
- bump PORTREVISION
MFH: 2014Q2
- update to 4.0.12, 4.2.8, 4.4.3
- move BINMODE to Makefile.common so it is also used in the language packs
Security: CVE-2014-1517
Security: 608ed765-c700-11e3-848c-20cf30e32f6d
Security: 60bfa396-c702-11e3-848c-20cf30e32f6d
- update to latest release [1]
- use PKGNAMESUFFIX instead LATEST_LINK
- whitespace cleanup
- svn mv */bugzilla to */bugzilla40
- add vuxml entry
4.4.1, 4.2.7, and 4.0.11 Security Advisory
Wednesday Oct 16th, 2013
Summary
=======
Bugzilla is a Web-based bug-tracking system used by a large number of
software projects. The following security issues have been discovered
in Bugzilla:
(Only the first 15 lines of the commit message are shown above )
- Convert to new Uses/perl5.mk framework
- Resolve issues with implicit lang/perl in extract and patch dependencies
- Trim Makefile header
Reviewed by: bapt@ (exp-run)
Approved by: bapt@ (portmrg@)
- use OPTION_GROUP in all devel/bugzilla ports
- s/CONFLICTS/CONFLICTS_INSTALL/
- use easier CONFLICT notation (future proof)
- trim Makefile.common header
- update russian/bugzilla42 language template to version 4.2.6
- update bugzilla42 to version 4.2.6 (bugfix release)
- remove RUN_DEPENDS for (already expired) perl 5.10
- update german/bugzilla42
- set expiration date for bugzilla3
The following important fixes/changes have been made in this release:
o MySQL 5.6 is now supported. (Bug 852560)
o A regression introduced in Bugzilla 4.2.4 made Oracle crash when
installing Bugzilla for the first time. (Bug 858911)
o If a custom field depends on a product, component or classification,
the "mandatory" bit was ignored on bug creation. (Bug 782210)
o Queries involving flags were broken in several ways.
These queries have been fixed. (Bug 828344)
o Tabular reports involving the empty resolution did not link bug
counts correctly. (Bug 212471)
o The Bug.search WebService method was returning all visible bugs
when called with no arguments, ignoring the max_search_results
and search_allow_no_criteria parameters. (Bug 859118)
Release Notes:
http://www.bugzilla.org/releases/4.2.6/release-notes.html
- update bugzilla ports to latest version
Bugzilla 4.0.10 and 3.6.13 are security updates for the 4.0
branch and the 3.6 branch, respectively. 4.0.10 contains several
useful bug fixes and 3.6.13 contains only security fixes.
Security: CVE-2013-0785
CVE-2013-0786
- adjust required PgSQL module for bugzilla42
From Release Notes:
PostgreSQL 9.2 requires DBD::Pg 2.19.3. (Bug 799721)
No revision bump, p5-DBD-Pg-2.19.3
a) not on per default
b) in the tree since a view months
- add deprecation message to bugzilla3
From the announcement:
Note that when Bugzilla 4.4 is released, the Bugzilla 3.6.x series
will reach end of life. If you are using that series, we encourage
you to upgrade to 4.2.4 now.
http://groups.google.com/group/mozilla.support.bugzilla/browse_thread/thread/d8dcc99be0f89421
Feature safe: yes
- bugzilla security updates to version(s)
3.6.11, 4.0.8, 4.2.4
Summary
=======
The following security issues have been discovered in Bugzilla:
* Confidential product and component names can be disclosed to
unauthorized users if they are used to control the visibility of
a custom field.
* When calling the 'User.get' WebService method with a 'groups'
argument, it is possible to check if the given group names exist
or not.
(Only the first 15 lines of the commit message are shown above )
- security update bugzilla
new Versions: 3.6.10, 4.0.7, 4.2.2
4.2.2
This release fixes two security issues. See the Security Advisory for details.
In addition, the following important fixes/changes have been made in this
release:
o A regression introduced in Bugzilla 4.0 caused some login names to be
ignored
when entered in the CC list of bugs. (Bug 756314)
o Some queries could trigger an invalid SQL query if strings entered by the
user
contained leading or trailing whitespaces. (Bug 760075)
o The auto-completion form for keywords no longer automatically selects the
first keyword in the list when the field is empty. (Bug 764517)
(Only the first 15 lines of the commit message are shown above )
- new port bugzilla42
New Features and Improvements:
- Experimental SQLite Support
- Creating an Attachment by Pasting Text Into a Text Field
- HTML Bugmail (default: on can be disabled in user preference)
- Improved Searching System
- Disabling Old Components, Versions and Milestones
- Displaying a Custom Field Value Based on Multiple Values of Another Field
- Auditing of All Changes Within Bugzilla
- Accessibility Improvements
And many other Improvements, for complete list see:
http://www.bugzilla.org/releases/4.2.1/release-notes.html
