Soyuz fails to bring packages out of depwait when missing builddep is later provided by a virtual package

Bug #690240 reported by Scott Kitterman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
William Grant

Bug Description

The following packages are (or were in the case of manual retries) depwait due to "Missing build dependencies: padre-plugin-api-2":

libpadre-plugin-autoformat-perl 1.22-2
libpadre-plugin-css-perl 0.14-1
libpadre-plugin-html-perl 0.13-2
libpadre-plugin-nopaste-perl 0.3.1-2
libpadre-plugin-perltidy-perl 0.16-2
libpadre-plugin-spellcheck-perl 1.21-2
libpadre-plugin-vi-perl 0.23.0-1
libpadre-plugin-xml-perl 0.10-2

This package is provided by padre:

https://launchpad.net/ubuntu/natty/i386/padre/0.76.ds1-1

It's been provided for ~9 hours now, so I suspect if Soyuz were going to notice, it would have already.

description: updated
Revision history for this message
Julian Edwards (julian-edwards) wrote :

I suspect the code that adds the dependencies to the build record when it finishes is going wrong, I can't see how this can go wrong in retry-depwait

Changed in soyuz:
status: New → Triaged
importance: Undecided → Low
assignee: nobody → William Grant (wgrant)
tags: added: bugjam2010 soyuz-build
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.