The contents of the dependencies field is wrong
Bug #35974 reported by
Matthias Klose
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Medium
|
Celso Providelo | ||
Bug Description
See https:/
python-profiler doesn't depend on libtoolbar-java. even if the information in this field is correct, what is the value of having this field?
Revision history for this message
| Celso Providelo (cprov) wrote | #1 |
| Changed in soyuz: | |
| assignee: | nobody → cprov |
| status: | Unconfirmed → Needs Info |
| Changed in soyuz: | |
| status: | Needs Info → Rejected |
To post a comment you must log in.
Currently this build is superseded, but looking to the log we can identify the 'dependencies' field was wrong, maybe cause by some experience from adconrad on slaves.
Anyway, this field store information returned from the slavedelivering a 'missing dependency' build process, pointing the possible cause of the failure, the missing packages. It's part of the current" Auto Retry" mechanism on dependency satisfaction.
I'm affraid the mentioned problem isn't there anymore, but feel free to report it again if it persists.