Reopen #35646

[Evan Carroll]

I think someone should reopen this bug. I've since clarified why I thought it was confusing with a real world example.

[Evan Carroll (evancarroll)]

https://bugs.launchpad.net/launchpad/+bug/35646

[Graham Binns (gmb)]

Hi Evan,

I noticed you commented on bug 35646 about fifteen minutes before filing this bug. Whilst I appreciate that you're eager to get it re-opened, or at least have your comment answered, there's no need to open a new bug about it just yet. We may well do that in the course of time, but having multiple bugs tracking the same issue is confusing.

[Evan Carroll (evancarroll)]

That's interesting. While I can't change the state of #35646 (https://bugs.launchpad.net/launchpad/+bug/35646), I can change the state of this bug. I went ahead and confirmed it because #35646 is certainly still "Fix Released" without any indicator that it is being worked on. That makes this bug Valid.

[Evan Carroll (evancarroll)]

I also filed a bug on why I opened this one, you can find it here (#35646) https://bugs.launchpad.net/launchpad/+bug/35646

[Evan Carroll (evancarroll)]

Actually, the bug I just filed was this one... (#787668) https://bugs.launchpad.net/launchpad/+bug/787668. Boy.. it'd be nice if we could edit comments not even a minute old.

[Evan Carroll (evancarroll)]

It appears as if there is already a bug for not being able to edit comments, (#80895) https://bugs.launchpad.net/launchpad/+bug/80895

[Gavin Panella (allenap)]

Evan, I'll reply here to your comment in bug 35646
(https://bugs.launchpad.net/launchpad/+bug/35646/comments/9).

> I still find this slightly confusing:
>
> Take this page for example:
> https://bugs.launchpad.net/chromium-browser/+bug/621786
>
> I wanted to know where are the other bugs for
> Chromium-Browser. Clicking "bugs" in the menu-major at the top takes
> me here,
>
> https://bugs.launchpad.net/chromium-browser

That's interesting. The canonical URL for bug 621786 is actually:

  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/621786

On that page, clicking the Bugs link near the top would have taken you
to:

  https://bugs.launchpad.net/ubuntu/+source/chromium-browser

That sounds like the kind of list you're looking for: a list of bugs
with the chromium-browser package in Ubuntu.

> "Chromium Browser must be configured in order for Launchpad to
> forward bugs to the project's developers." doesn't seem to apply to
> me though. I'm just looking for other peoples bugs, like
> #621786. And, even if I wanted to file bugs, why do I really care if
> it is set to work with Chromium-browser upstream. We all know 95% of
> the bugs on launchpad are for Google, and single-login. Not to
> actually get stuff done. That's why the peon-team files and tracks
> them upstream after verifying them.

I think you misunderstand how the Launchpad bug tracker works. Perhaps
https://help.launchpad.net/Bugs/MultiProjectBugs will help. It is
common practice to file a bug for an Ubuntu package in Launchpad and
for the triage teams to later discover that this is an upstream
issue. The bug report can then be linked to the upstream bug report so
that subscribers in Launchpad abreast of change.

> If that isn't clear, deleting the bug id in the URL isn't any
> better...
>
> https://bugs.launchpad.net/chromium-browser/+bugs
>
> Now I get a simple, "Chromium Browser does not use Launchpad for bug
> tracking." That still begs the question why was the original bug on
> Launchpad to begin with...

Bug 621786 was originally filed for the chromium-browser package in
Ubuntu, not for the Chromium browser itself. Ubuntu tracks bugs in
Launchpad.

>
> Alas, I'll check the overview
>
> https://launchpad.net/chromium-browser
>
> But, still not a single mention of how bug tracking works; or, how
> the original bug was filed... This behavior is not typical of
> Launchpad. Because it stands out an infobox should inform the user
> what is going on each Launchpad page in the project. Especially, the
> user's original landing page...
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/621786

Ah ha. How did you end up at:

  https://bugs.launchpad.net/chromium-browser/+bug/621786

?

If Launchpad generated that URL then that may itself be a bug.

[Launchpad Janitor (janitor)]

[Expired for Launchpad itself because there has been no activity for 60 days.]