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 bugzilla-3.6.13:
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
====> 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
- 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 )
graphics/ImageMagick can change package name via PKGNAMESUFFIX.
We should not rely on this.
Reported by: Jarrod Sayers <jarrod at downtools.com.au>
Pointy hat: az@
- update to version 3.6.7
- CVE-2011-3657
- CVE-2011-3667
Summary
=======
The following security issues have been discovered in Bugzilla:
* When viewing tabular or graphical reports as well as new charts,
an XSS vulnerability is possible in debug mode.
* The User.offer_account_by_email WebService method lets you create
a new user account even if the active authentication method forbids
users to create an account.
* A CSRF vulnerability in post_bug.cgi and in attachment.cgi could
lead to the creation of unwanted bug reports and attachments.
All affected installations are encouraged to upgrade as soon as possible.
Full Release Notes:
http://www.bugzilla.org/security/3.4.12/
Approved by: skv@ (explicit)
- create missing (empty) directory (bugzilla) so checksetup does not fail
- use DIST_SUBDIR for bugzilla and all translations
- sort pkg-plist (genplist)
OK from bugzilla maintainers per PM.
PR: ports/158766
Submitted by: ohauer