Archive.syncSource doesn't correctly isolate a single copy candidate

Bug #401716 reported by Celso Providelo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Celso Providelo

Bug Description

Currently syncSource lookup the copy candidate for the given 'name' and 'version' with:

{{{
source = from_archive.getPublishedSources(
            name=source_name, version=version, exact_match=True)
}}}

The result is not a *single* source, as expected, if the specified source release was published (copied) to more than one suite.

It should always use the first element of the returned ResultSet.

Tags: api lp-soyuz ppa
Celso Providelo (cprov)
Changed in soyuz:
milestone: none → 2.2.7
Celso Providelo (cprov)
Changed in soyuz:
status: Triaged → In Progress
Revision history for this message
Celso Providelo (cprov) wrote :

r8298 (db-devel)

Changed in soyuz:
status: In Progress → Fix Committed
Celso Providelo (cprov)
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.