launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #06170
Re: marking as dup - always use oldest bug?
-
To:
launchpad-dev@xxxxxxxxxxxxxxxxxxx
-
From:
Aaron Bentley <aaron@xxxxxxxxxxxxx>
-
Date:
Wed, 12 Jan 2011 08:57:21 -0500
-
In-reply-to:
<AANLkTi=w=teSWEAKtHo+QUZCc1uE+CD_d4=oEVkxsz4t@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11-01-10 01:35 PM, Robert Collins wrote:
> On searches:
> - the dupe finder is *meant* to search across dupes too, if its not
> thats a bug - lets confirm and file it.
I don't know about the dupe finder, but I know that the standard bug
search is not finding the authoritative bug if it doesn't have a bug
task for project you filed the dupe on.
I filed #699891 on oops-tools, and it was marked as a dupe #661266,
which was an Apache OpenID bug. Afterward, searching "openid" on
"oops-tools" found nothing.
> - to workaround such a bug we can simply edit the title and body of
> the older bug - and we should do that as part of keeping the bug
> maintained. They should be living documents.
I thought that was the issue at first, but I found that adding "openid"
to #661266 title did not make it possible to find it using a bug search
on oop-tools. So I added a bug task on oops-tools.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk0ts0EACgkQ0F+nu1YWqI0smgCeMfkqCVXoKqjnSUGhoifGzkqX
1cIAn0yvzgtwuUbSRhUqcxoyQhV7TfUJ
=OLsC
-----END PGP SIGNATURE-----
Follow ups
References