[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Processed: Reassigning and merging with cdebconf bug



On Thu, Mar 27, 2003 at 12:45:26AM +0100, Sebastian Ley wrote:
> * Debian Bug Tracking System wrote:
> > > clone 184859 -1 -2
> > Bug#184859: I can't correct typing errors
> > Bug 184859 cloned as bugs 186413-186414.
> > 
> > > reassign -1 cdebconf
> > Bug#186413: I can't correct typing errors
> > Bug reassigned from package `choose-mirror' to `cdebconf'.
> > 
> > > retitle -1 cdebconf: Questions with q->next != NULL fail when asked
> > > twice
> > Bug#186413: I can't correct typing errors
> > Changed Bug title.
> > 
> > > merge 182357 -1
> > Unknown command or malformed arguments to command.
> 
> Sorry, I guess, I did something stupid here...
> What I wanted to do is to make two bugs out of it, where the second
> bug be merged with the cdebconf bug, we identified lately. Obviously
> the BTS could not read my mind and made two new bug reports, and
> failed to merge the bugs in question.

There's a bug currently open against bugs.debian.org because merge
doesn't support merging just-cloned bugs. When clone was originally
implemented I don't think anyone expected people to clone and then merge
straight away.

I have a patch which should fix this but need to find time to test it.

> Perhaps someone can help me to unmess things?
> My suggestion:
> 
> merge 184859 186414

I'd just close the extra clone if I were you. Unless there's been
traffic on it since the clone there's no value in keeping it open.

> notforwarded 186413
> notforwarded 182357
> forwarded 186413 debian-boot@lists.debian.org
> forwarded 182357 debian-boot@lists.debian.org

The notforwardeds are unnecessary, and there really isn't much point
marking bugs as forwarded to the address that's already listed as the
maintainer for the assigned package. I'd just drop these four lines.

> merge 186413 182357

Yes,

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]



Reply to: