Current problem reports assigned to openoffice@FreeBSD.org

FreeBSD bugmaster bugmaster at FreeBSD.org
Mon Sep 8 02:23:25 UTC 2008


The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o ports/126818 openoffice editors/openoffice.org-3 compilation fails on FreeBSD-
o ports/126308 openoffice [patch] editors/openoffice.org-2 compilation fails on 
o ports/124801 openoffice editors/openoffice.org-3 - OpenOffice fails to find li
o ports/119204 openoffice [patch] editors/OpenOffice.org-2 v2.3 loops when file 
o ports/118527 openoffice editors/openoffice.org-2 seg faults when asked to perf
o ports/118507 openoffice editors/Openoffice.org-2 2.3.1/AMD64 does not show ODB
o ports/117965 openoffice editors/openoffice.org-2 Impress crashes with multiple
o ports/117808 openoffice editors/OpenOffice.org-2 seems to be looping
o ports/116741 openoffice editors/openoffice.org-2 build errors related to java
f ports/112283 openoffice editors/openoffice-2 fails to build with "pyconfig.h: 
o ports/108313 openoffice editors/openoffice.org port build fails
f ports/107229 openoffice sysutils/coreutils: gcp fails to set default ACL which

12 problems total.


Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.

a - analyzed
The problem is understood and a solution is being sought.

f - feedback
Further work requires additional information from the
     originator or the community - possibly confirmation of
     the effectiveness of a proposed solution.

p - patched
A patch has been committed, but some issues (MFC and / or
     confirmation from originator) are still open.

r - repocopy
The resolution of the problem report is dependent on
     a repocopy operation within the CVS repository which
     is awaiting completion.

s - suspended
The problem is not being worked on, due to lack of information
     or resources.  This is a prime candidate
     for somebody who is looking for a project to do.
     If the problem cannot be solved at all,
     it will be closed, rather than suspended.

c - closed
A problem report is closed when any changes have been integrated,
     documented, and tested -- or when fixing the problem is abandoned.



More information about the freebsd-openoffice mailing list