Package copy OOPS emails should report package source names if present

Bug #1618133 reported by Chris J Arges on 2016-08-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Colin Watson

Bug Description

The following OOPS was generated in response to a bad package copy between archives:
https://oops.canonical.com/?oopsid=OOPS-b6b2ad0eed760ae55eab3a931e619745

Which Colin mentioned was this bug:
https://bugs.launchpad.net/launchpad/+bug/1475358

From a user perspective it would be great to know which package caused this OOPS so that it can be retried easily. In many cases if a large copy (or a script which copies many packages) is used, it may be difficult to know which single copy failed.

Thanks

Related branches

William Grant (wgrant) on 2016-09-19
summary: - OOPS should report package source names if present
+ Package copy OOPS emails should report package source names if present
tags: added: email oops package-copies
Colin Watson (cjwatson) on 2016-10-17
Changed in launchpad:
assignee: nobody → Colin Watson (cjwatson)
importance: Undecided → Low
status: New → In Progress
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Colin Watson (cjwatson) on 2016-11-07
tags: added: qa-ok
removed: qa-needstesting
Colin Watson (cjwatson) on 2016-11-09
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers