Incorrect override when uploading a package to partner

Bug #545962 reported by Michael Nelson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
William Grant

Bug Description

If a package is uploaded to the partner component, but has ancestry in the main archive, the ancestry is picked up and causes the DSCFile's component to be overridden accordingly.

Specifically, NascentUpload.getSourceAncestry() does *not* use the corresponding archive for the component when searching for ancestry. This may be as trivial as switching policy.archive to distribution.getArchiveForComponent().

Found this while QAing bug 529926.

Related branches

Changed in soyuz:
status: New → Triaged
importance: Undecided → Medium
tags: added: soyuz-upload trivial
description: updated
Curtis Hovey (sinzui)
Changed in launchpad:
importance: Medium → Low
William Grant (wgrant)
tags: added: package-overrides
Revision history for this message
William Grant (wgrant) wrote :

This is because the partner archive override is performed on the post-override component, so the override lookup searches in both the primary and partner archive. I'm going to instead perform the archive override before overrides, on just the upload component, eliminating the ambiguity.

Changed in launchpad:
assignee: nobody → William Grant (wgrant)
status: Triaged → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
William Grant (wgrant)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
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.