Upload processor attempts to verify hashes against expired files

Bug #687662 reported by William Grant on 2010-12-09
46
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Launchpad itself
High
William Grant

Bug Description

devel r12009 altered the upload processor to use Archive.getFileByName instead of Distribution.getFileByName. The former returns expired files, while the latter does not. Expired LFAs have no LFC, so the content.md5 check fails like this:

 Unhandled exception processing upload: 'NoneType' object has no attribute 'md5'

lp:~wgrant/launchpad/bug-522800-getFileByName should fix this by preventing Archive.getFileByName from returning expired files.

Related branches

Changed in soyuz:
importance: Undecided → High
assignee: nobody → William Grant (wgrant)
status: New → In Progress
Vladimir Kolesnikov (sjinks) wrote :

Is there any workaround?

Ant upload to PPA fails with "Rejected: Unhandled exception processing upload: 'NoneType' object has no attribute 'md5'"

On Friday 10 December 2010 13:18:38 you wrote:
> Is there any workaround?
>
> Ant upload to PPA fails with "Rejected: Unhandled exception processing
> upload: 'NoneType' object has no attribute 'md5'"

You need to upload a new orig file instead of depending on one that was
previously uploaded that since expired.

tags: added: qa-needstesting
Changed in soyuz:
status: In Progress → Fix Committed
Vladimir Kolesnikov (sjinks) wrote :

> You need to upload a new orig file instead of depending on one that was previously uploaded that since expired.

Tried both debuild -S -sa and debuild -S -sd, both get rejected with that error.

Bilal Akhtar (bilalakhtar) wrote :

I tried uploading with both -sa and -sd, and the problem occurs in both the ways. Any workaround? I seem to be having the same case as vladimir.

Glen Ditchfield (gjditchfield) wrote :

> You need to upload a new orig file instead of depending on one that was previously uploaded that since expired.

I worked around the problem by renaming the orig file, which I could do because the upstream version name wasn't crucial.
* renamed alephone_20100424.orig.tar.gz to alephone_20100424x.orig.tar.gz
* changed the version line at the top of debian/changelog to
  alephone (20100424x-0~maverick3) maverick; urgency=low
* rebuilt the package with "debuild ... -S -si ..."

William Grant (wgrant) on 2010-12-13
tags: added: qa-ok
removed: qa-needstesting
Gunnar Hjalmarsson (gunnarhj) wrote :

My latest attempt a few hours ago was accepted, so it seems to be working now.

Changed in launchpad:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui) on 2011-01-11
Changed in launchpad:
milestone: none → 11.01
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers