Soyuz needs to be able to process and publish ddebs

Bug #285205 reported by Adam Conrad
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Celso Providelo

Bug Description

Soyuz needs to be able to handle "ddebs" (debug debs) being present in .changes, and needs to be able to export/publish them. This can be fleshed out further with me (Adam Conrad) and pitti (Martin Pitt) as the bug is worked on.

Can probably be achieved in 2 stages, where the first stage involves accepting the ddebs in uploads and then dumping them to an export directory where pitti's magic scripts can download them and build an archive, and then the second stage, where soyuz actually does the archive publishing itself.

Tags: lp-soyuz
Changed in soyuz:
importance: Undecided → Medium
status: New → Triaged
Celso Providelo (cprov)
Changed in soyuz:
assignee: nobody → cprov
milestone: none → 2.2.3
status: Triaged → In Progress
Celso Providelo (cprov)
Changed in soyuz:
milestone: 2.2.3 → 2.2.4
Revision history for this message
Celso Providelo (cprov) wrote :

ddebs will be processed as normal debs after r8244, i.e. will end up in the primary archive which is not necessarily what we want to do. Next take on this bug will be properly identifying ddebs and publish them in a separate archive.

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

r8268, ddebs will be published in a separate main_archive (DEBUG) and does not cause binary uploads to be held in NEW queue (because all ddebs will be 'unknown' the first time they get generated).

The last branch on this area will be changing the publisher to allow the creation of a separate repository for the DEBUG archive.

Celso Providelo (cprov)
Changed in soyuz:
milestone: 2.2.4 → 2.2.5
Revision history for this message
Celso Providelo (cprov) wrote :

r8451 (stable)

Changed in soyuz:
status: In Progress → Fix Committed
Celso Providelo (cprov)
Changed in soyuz:
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.