Closing a bug

[Ace Suares]

On Thursday 17 April 2008, Emilio Pozuelo Monfort wrote:
> Ace Suares wrote:
> > On Wednesday 16 April 2008, Brian Murray wrote:
> >> On Wed, Apr 16, 2008 at 09:07:11PM -0400, Ace Suares wrote:
> >>> Hiya
> >>>
> >>> https://bugs.launchpad.net/openoffice/+bug/70981
> >>>
> >>> How to deal with this:
> >>>
> >>> 1. it's still a bug in feisty,.
> >>> 2. it's not a bug in gutsy
> >>> 3. somehow the 'affects' lists 4 items; two of them is fix release,
> >>> one confirmed, one invalid.
> >>
> >> In this particular bug we are being shown how it affects multiple
> >> different packages and projects.  We have the following:
> >>
> >> KDE PIM
> >>  - an upstream project
> >> OpenOffice
> >>  - another upstream project
> >> kdelibs (Ubuntu)
> >>  - an Ubuntu package
> >> openoffice.org (Ubuntu)
> >>  - an Ubuntu package
> >>
> >>> What to do to close the bug !?
> >>
> >> The bug is "closed", or in an end state, for almost every thing it
> >> affects.  The only remaining open affects is the upstream OpenOffice
> >> bug and if the bug really isn't an OpenOffice bug it'd be best if we
> >> were to get that upstream bug closed too.
> >>
> >> This is a really neat question as it illustrates how a bug can
> >> affect many different things which isn't the case with every bug.  I
> >> hope my answer helps explain things.
> >>
> >> Thanks,
> >
> > Hi,
> >
> > How to close an upstream bug ? Is that a bug in another bug system
> > (i.e. not Malone/Launchpad) ?
>
> I wouldn't close it. It's a bug watch so it will be closed when the
> upstream bug is closed.
>
> Also, all the Ubuntu tasks are closed so that bug is closed 'in
> Ubuntu'. Leaving the OOo task open won't cause any harm.
>
> But for answering the question, it can be closed by changing its status
> to 'None, the status of the bug is updated manually.', then changing it
> to invalid.

Thanks! I will try to remember that. In case the OO people don't close 
their bug.

ace

>
> Emilio