Hello,
I had another thought about the OOo v2.0.0 situation which has probably
been mentioned before, but I'll toss it out there anyway:
What about continuing to package both v1 and v2 of OOo for the time being?
(and ideally allowing them to both be installed) That way people could
choose b
Hi Rene,
On Tue, 25 Oct 2005, Rene Engelhard wrote:
Yes, you are the fourth person now writing a bug for that
Thanks for the quick reply! I'm sorry that I reported a duplicate bug. I
did look around at some of the Debian packages but I didn't see anything
reported against the new v2.0
Package: openoffice.org-common
Version: 2.0.0-1
Severity: normal
Many of the openoffice packages have files in /usr/lib/mime/packages
that run programs ending in "2", eg oowriter2, which do not exist
(because the program is called oowriter, etc).
Andrew
-- System Information:
Debian Release: tes
Processing commands for [EMAIL PROTECTED]:
> severity 335788 normal
Bug#335788: openoffice.org: /etc/mailcap still uses oo2 instead of oo
Bug#335313: openoffice.org: MIME type entries stillrefer to the *2 programs
Severity set to `normal'.
> merge 335788 335313
Bug#335313: openoffice.org: MIME ty
Processing commands for [EMAIL PROTECTED]:
> forwarded 335720 http://www.openoffice.org/issues/show_bug.cgi?id=43547
Bug#335720: openoffice.org-impress: "Hide slide" option not renamed on hidden
slides
Noted your statement that Bug has been forwarded to
http://www.openoffice.org/issues/show_bug.
tag 335188 + moreinfo
thanks
Hi,
rich lott wrote:
> Package: openoffice.org
> Version: 1.1.4-7
> Severity: normal
>
>
> I get
>
> > The files required could not be found.
> > Please start the OpenOffice.org Setup and choose 'Repair'.
>
> in a message box when choosing AutoPilot Form from a d
Processing commands for [EMAIL PROTECTED]:
> merge 335793 335725
Bug#335725: openoffice.org-core conflicts with openoffice.org-help-en, but
alternative is not available.
Bug#335793: openoffice.org-help-en: Please upgrade to v2.0
Bug#329585: openoffice.org2: Please provide some help system
Bug#333
Processing commands for [EMAIL PROTECTED]:
> # that probably would make lesser people notice that but the 1.1.x help
> # will probably get soon removed from the ftpmasters anyway, so..
> reassign 335793 openoffice.org
Bug#335793: openoffice.org-help-en: Please upgrade to v2.0
Bug reassigned from p
# that probably would make lesser people notice that but the 1.1.x help
# will probably get soon removed from the ftpmasters anyway, so..
reassign 335793 openoffice.org
severity 335793 wishlist
merge 335793 335735
thanks
Hi,
Jason Maas wrote:
> Thanks so much for your quick work packaging the fin
Processing commands for [EMAIL PROTECTED]:
> severity 335788 normal
Bug#335788: openoffice.org: /etc/mailcap still uses oo2 instead of oo
Severity set to `normal'.
> merge 335788 335313
Bug#335313: openoffice.org: MIME type entries stillrefer to the *2 programs
Bug#335788: openoffice.org: /etc/ma
Package: openoffice.org-help-en
Severity: important
Thanks so much for your quick work packaging the final release of OOo
2.0! I installed it and everything looks really nice, except that the
online help seems to be missing. If I'm doing something wrong then I
apologize in advance.
It seems th
Package: openoffice.org
Version: 2.0.0-1
Severity: important
After openoffice.org upgrade, /etc/mailcap refers to non-existent binaries:
oobase2, oocalc2, oodraw2, ooimpress2, oomath2, ooweb2, oowriter2
Makes reading OpenOffice files from a mail client inconvenient. :)
-- System Informatio
Package: openoffice.org
Version: 2.0.0-1
Severity: important
Maybe related #210581? That one is too old.
I've two twin servers (same hardware, same Debian Sid, same 2.6.13.2
kernel, same OOo, same users _WITH SAME UIDS_, etc). Both of these
servers mount some of its /home directories via NFS from
Your message dated Tue, 25 Oct 2005 19:11:56 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reo
Processing commands for [EMAIL PROTECTED]:
> reassign 335725 openoffice.org
Bug#335725: openoffice.org-core conflicts with openoffice.org-help-en, but
alternative is not available.
Bug reassigned from package `openoffice.org-help-en' to `openoffice.org'.
> severity 335725 wishlist
Bug#335725: op
reassign 335725 openoffice.org
severity 335725 wishlist
merge 335725 329585
thanks
Hi,
Matej Cepl wrote:
> Just downloaded openoffice.org 2.0 from
> http://people.debian.org/~rene/openoffice.org/2.x/ (which is
> currently in NEW front) and it is missing help.
It isn't in NEW anymore :)
Yes, it'
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Your message dated Tue, 25 Oct 2005 09:03:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing bugs fixed in 2.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsi
Package: ftp.debian.org
Severity: normal
Please remove the following from unstable/experimental since they are
now obsolete:
- openoffice.org2 (everything)
- neon0.23 (everything)
- openoffice.org-help-*
- openoffice.org-debian-files
and (but they maybe will be rene'd anyway..):
- openoffice.or
Package: openoffice.org-help-en
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just downloaded openoffice.org 2.0 from
http://people.debian.org/~rene/openoffice.org/2.x/ (which is
currently in NEW front) and it is missing help.
openoffice.org-help-en is available only in version
Package: openoffice.org-impress
Version: 2.0.0-1
Severity: minor
I have the slide pane open in Impress, and right-clicking on a slide
brings up a menu with a "Hide Slide" option. On hidden slides, the
option still says "Hide Slide", but does in fact unhide slides. Possibly
the option should be ren
Package: openoffice.org
Version: 2.0.0-1
Followup-For: Bug #335026
Hi,
I grabbed the packages from
http://people.debian.org/~rene/openoffice.org/2.x/ and the problem still
persists.
I'm not sure how it's possible for sensible-ooomua to work without
python 2.4, since it tries t
Your message dated Tue, 25 Oct 2005 09:08:17 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#298065: openoffice.org: Printing a spreadsheet misses the
last line
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
35 matches
Mail list logo
