On Thu, Oct 21, 2004 at 01:28:41PM +1000, Brian May wrote:
> > "Joel" == Joel Baker <[EMAIL PROTECTED]> writes:
>
> Joel> It would also presumably allow you to add a filter such as
> Joel> "don't display any bug with a dependancy on any other
> Joel> still-open bug"; thus allowing
> "Joel" == Joel Baker <[EMAIL PROTECTED]> writes:
Joel> It strikes me that this problem is actually similar to a
Joel> couple of others, and all of them could be reasonably
Joel> resolved by a new concept in the BTS - bug dependancies.
Joel> All it really says is "Some part o
> "Wouter" == Wouter Verhelst <[EMAIL PROTECTED]> writes:
Wouter> Simple. When merging a bug, you claim that the two bugs
Wouter> are really the same. They're not just related, nor are
Ok, so what we need is a method of saying two bugs are related, but
not the same.
> "Colin" ==
On Tue, Oct 19, 2004 at 08:26:23AM +1000, Brian May wrote:
> > "Bernd" == Bernd Eckenfels <[EMAIL PROTECTED]> writes:
>
> Bernd> On Mon, Oct 18, 2004 at 05:54:44PM +1000, Brian May wrote:
> >> I could just close the bug against my package, but this means other
> >> people will enco
On Tue, Oct 19, 2004 at 08:14:25AM +1000, Brian May wrote:
> > "Wouter" == Wouter Verhelst <[EMAIL PROTECTED]> writes:
> >> How about merging those bugs with the bug reported against the correct
> >> package?
>
> Wouter> That's not possible. You can only merge bugs if /all/
> W
On Tue, Oct 19, 2004 at 08:16:02AM +1000, Brian May wrote:
> > "Martin" == Martin Michlmayr <[EMAIL PROTECTED]> writes:
> Martin> * Wouter Verhelst <[EMAIL PROTECTED]> [2004-10-18 13:32]:
> >> That's not possible. You can only merge bugs if /all/ properties (tags,
> >> severity, pac
On Tue, Oct 19, 2004 at 08:14:25AM +1000, Brian May wrote:
> > "Wouter" == Wouter Verhelst <[EMAIL PROTECTED]> writes:
> Wouter> That's not possible. You can only merge bugs if /all/
> Wouter> properties (tags, severity, package reported against, ...)
> Wouter> are the same.
>
> Wh
> "Adrian" == Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]>
> writes:
>> I have a number of bugs reported against my packages which are
>> actually (already reported) bugs in other packages.
Adrian> Reading the rest of the thread, I conclude that adding an
Adri
> "Adeodato" == Adeodato Simó <[EMAIL PROTECTED]> writes:
Adeodato> * Bernd Eckenfels [Mon, 18 Oct 2004 12:01:32 +0200]:
>> Perhaps we need a "read this before submitting bugs against my package"
>> function in reportbugs :)
Adeodato> such functionality exists, via the
Ade
> "Bernd" == Bernd Eckenfels <[EMAIL PROTECTED]> writes:
Bernd> On Mon, Oct 18, 2004 at 05:54:44PM +1000, Brian May wrote:
>> I could just close the bug against my package, but this means other
>> people will encounter the same problem and report the bug against my
>> package a
> "Martin" == Martin Michlmayr <[EMAIL PROTECTED]> writes:
Martin> * Wouter Verhelst <[EMAIL PROTECTED]> [2004-10-18 13:32]:
>> That's not possible. You can only merge bugs if /all/ properties (tags,
>> severity, package reported against, ...) are the same.
Martin> Just for th
> "Wouter" == Wouter Verhelst <[EMAIL PROTECTED]> writes:
Wouter> On Mon, Oct 18, 2004 at 10:19:18AM +0200, Gergely Nagy wrote:
>> > I could just close the bug against my package, but this means other
>> > people will encounter the same problem and report the bug against my
>>
On Monday 18 October 2004 06:01 am, Bernd Eckenfels wrote:
> Perhaps we need a "read this before submitting bugs against my package"
> function in reportbugs :)
I've actually seen some packages do this. For instance, try submitting a
bug against mozilla-firefox..
Daniel
--
/--
On Monday 18 October 2004 09.54, Brian May wrote:
> Hello,
>
> I have a number of bugs reported against my packages which are
> actually (already reported) bugs in other packages.
Reading the rest of the thread, I conclude that adding an explanation to the
bug and tagging it wontfix is probably t
Bernd Eckenfels wrote:
> Perhaps we need a "read this before submitting bugs against my
> package" function in reportbugs :)
That already exists: /usr/share/bug/. "reportbug galeon" provides a
reasonable example run.
* Bernd Eckenfels [Mon, 18 Oct 2004 12:01:32 +0200]:
> Perhaps we need a "read this before submitting bugs against my package"
> function in reportbugs :)
such functionality exists, via the /usr/share/bug//presubj
file. see /usr/share/doc/reportbug/README.developers.
--
Adeodato Simó
EM
* Wouter Verhelst <[EMAIL PROTECTED]> [2004-10-18 13:32]:
> That's not possible. You can only merge bugs if /all/ properties (tags,
> severity, package reported against, ...) are the same.
Just for the record, tags are an exception. They are merged when you
merge bugs.
--
Martin Michlmayr
http:/
Bernd Eckenfels <[EMAIL PROTECTED]> schrieb:
> On Mon, Oct 18, 2004 at 05:54:44PM +1000, Brian May wrote:
>> I could just close the bug against my package, but this means other
>> people will encounter the same problem and report the bug against my
>> package again (as it isn't always obvious that
On Mon, Oct 18, 2004 at 10:19:18AM +0200, Gergely Nagy wrote:
> > I could just close the bug against my package, but this means other
> > people will encounter the same problem and report the bug against my
> > package again (as it isn't always obvious that it isn't the fault of
> > my package).
>
On Mon, Oct 18, 2004 at 05:54:44PM +1000, Brian May wrote:
> I could just close the bug against my package, but this means other
> people will encounter the same problem and report the bug against my
> package again (as it isn't always obvious that it isn't the fault of
> my package).
So you do no
> I could just close the bug against my package, but this means other
> people will encounter the same problem and report the bug against my
> package again (as it isn't always obvious that it isn't the fault of
> my package).
How about merging those bugs with the bug reported against the correct
21 matches
Mail list logo
