Check presence of orig in NEW/ACCEPTED/UNAPPROVE queue

Bug #31760 reported by Celso Providelo
10
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Check the presence of implicit files in incoming uploads, mostly orig.tar.gz, additionaly in the mentioned queues, it can safe build/publication cycle of superseded packages.

Tags: lp-soyuz
Revision history for this message
Celso Providelo (cprov) wrote :

It should be done ASAP, but it's not a blocker at all

Changed in launchpad-upload-and-queue:
assignee: nobody → cprov
status: Unconfirmed → Confirmed
Revision history for this message
Philipp Kern (pkern) wrote :

It's annoying at least and I don't know how to proceed. I just uploaded the second revision of a package waiting in NEW and it got rejected because the orig could not be found. I suppose this is related to this bug. Would it be possible to upload with the same orig or will that cause trouble when the first gets accepted from NEW? Do I need to wait until the first package cleared source NEW?

Revision history for this message
Celso Providelo (cprov) wrote :

Philipp,

Uploading the same orig.tar.gz (matching checksums) is fine and workarounds this bug.

I also think that since we start publishing sources immediately after they are processed this bug became much less important. I mean, we have to draw a line between 'files' that are known and the ones that are not, and stuff in ACCEPTED is definitely good (as it already is), but NEW (specially) and UNAPPROVED, in principle are not.

Changed in soyuz:
importance: High → Low
Curtis Hovey (sinzui)
Changed in soyuz:
assignee: Celso Providelo (cprov) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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