[bts-link] source package openoffice.org

2006-06-14 Thread bts-link-upstream
# # bts-link upstream status pull for source package openoffice.org # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #244280 # * http://qa.openoffice.org/issues/show_bug.cgi?id=31053 # * remote status changed: NEW -> S

Bug#353595: openoffice.org: no orientation option in printer dialogue

2006-06-14 Thread bryan . cebuliak
Package: openoffice.org Version: 2.0.2-3 Severity: important Followup-For: Bug #353595 The bug still exists in the latest OOo package. There are no work arounds. It has been reported and fixed in Ubuntu Dapper and upstream OOo. The severity should be upgraded as it is a malfunction of a doc

Bug#373468: (no subject)

2006-06-14 Thread Rene Engelhard
tag 373468 + pending thanks Hi, Am Mittwoch, 14. Juni 2006 10:42 schrieb Python Transition Mass bug: > Package: openoffice.org > Version: 2.0.2-3 > Severity: important [...] > This bug is part of a mass bug filling, and its severity will be > raised to serious when python will default to python

Processed: Re: Bug#373468: (no subject)

2006-06-14 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tag 373468 + pending Bug#373468: Python policy transition There were no tags set. Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs da

Processed: sorry for the forgotten subject

2006-06-14 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > # sorry I forgot the Subject line for the mass bug filling > retitle 373453 Python policy transition Bug#373453: (no subject) Changed Bug title. > retitle 373454 Python policy transition Bug#373454: (no subject) Changed Bug title. > retitle 373455 Pyt

Bug#373468: (no subject)

2006-06-14 Thread Python Transition Mass bug
Package: openoffice.org Version: 2.0.2-3 Severity: important Hi, your package has been detected as generating a python module/extension that may need an upgrade to the new Python Policy[1]. A wiki page [2] explains what has to be done to upgrade your packages to the new Policy. This bug may