diff generation ancestry in ppa:canonical-kernel-team/ubuntu/ppa is confused

Bug #1436285 reported by Adam Conrad
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

A long time ago, someone accidentally uploaded (and subsequently deleted) a 3.8.0 linux and linux-meta to precise in the kteam PPA. Ever since then, uploads of 3.2 kernels to precise in the PPA lead to failed attempts to diff against that long-forgotten version:

diff from 3.8.0-25.36 to 3.2.0-80.116 (pending)
diff from 3.8.0.25.41 to 3.2.0.80.94 (pending)

The fact that it's trying to generate a diff it can't would be an annoying enough buglet, but the real problem is that it doesn't even attempt to do a diff against the previous 3.2 versions.

Once the packages are copied to the archive, a new diff is triggered, and pops up, but that's somewhat after when I tend to review them, so I'm stuck downloading the source and diffing by hand before I do the copies.

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.