resolved_upstream list does not do product / source package matching

[Daniel Holbach]

Right now https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream=resolved_upstream (Bugs fixed elsewhere) lists
 - bug 37711 (Scribus Upstream Invalid, scribus Ubuntu Invalid, scribus-qtimm Ubuntu Confirmed) - no product / source package matching.

Thanks in advance. :-)

[Björn Tillenius (bjornt)]

Daniel, are you really sure you want this behaviour? Doing this will require all packages you're interested in to be linked to upstream projects. I fear this might break things for other users.

[Daniel Holbach (dholbach)]

It would be very very very very nice (with sugar on top of it) to have some kind of list that basically gives us "Stuff that was fixed somewhere, we just need to grab from some place".

The "... bugs fixed elsewhere" link on https://bugs.launchpad.net/ubuntu to me always seemed to be that list.

Right now bugs like the one listed above turn up on that list because the source package - Launchpad product matching is not considered.

[Graham Binns (gmb)]

This isn't going to make it for 2.1.10; pushing it off for a cycle.

[Graham Binns (gmb)]

I'm unclear: are we going to push ahead with this? I'm going to untarget this for the time being.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

I would also like to see this. At least to have an option to turn on source-package/product matching would help to filter bugs more efficiently.

A good example is bug #4188 . Which turns up in the bug list when searching for gnome-panel bugs that have been resolved upstream, although only the upstream bug for the nautilus project has been resolved upstream.

Thanks.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Since I am still interested in this feature, I helped myself with the Launchpad API. It's basically the following (Example: "totem"):

>>>
LP = Launchpad.login_anonymously(...)
UBUNTU = LP.distributions["ubuntu"]

package = UBUNTU.getSourcePackage(name="totem")
project = package.upstream_product

package_col = package.searchTasks()
project_col = project.searchTasks(status=["Fix Released", "Invalid"])

# I am using the split-construct for performance, because that's the only way
# to get the bug number, without requesting a new object (t.bug.id)
package_bugnos = set([str(t).split("/")[-1] for t in package_col])
project_bugnos = set([str(t).split("/")[-1] for t in project_col])

# Now I just have to look at the intersection which is basically a
# product/source-package matching for the bugs that are fixed upstream
matches = package_bugnos.intersection(project_bugnos)
>>>

That's just an idea I had. I would appreciate feedback. Thanks.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Just a note: For further performance it's recommended to replace

  package_col = package.searchTasks()

with

  package_col = package.searchTasks(status_upstream="resolved_upstream")

[Daniel Holbach (dholbach)]

This looks like the flipside of bug 829074.

[Abel Deuring (adeuring)]

My work on bug 829074 will just implement Bryce's suggestion to optionally limit the search results to bugs that have a bugtask on the project that referenced by the packaging link. UI wise, there will be two radio buttons ,like so

  Upstream target
    (x) All possible upstream targets
    ( ) [name odf the upstream project]

But I can extend this to also present the options "select upstream project" and "select upstream source package", where you can explicitly specify any project or (Debian) source package. A search would then return only those bugs that have a bug task for the given upstream project/source package. (Or, in the case of "Show bugs that are not known to affect upstream ", bug that do not have an usptream task.)

This option would only be available for searhes on source packages and on distro source packages.

Daniel, is this roughly what you have in mind?

[Abel Deuring (adeuring)]

Set back to "Triaged" because I don't see any way to fix this without adding ca 500 or 800LOC, thus violating the new policy https://dev.launchpad.net/PolicyAndProcess/MaintenanceCosts