The manifest entry for requirement is sequence sensitive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PlainBox (Toolkit) |
Fix Released
|
Critical
|
Zygmunt Krynicki |
Bug Description
For a job with multi-requirements, if the manifest was not placed at the first line of those requirements, for example:
id: audio/playback_
estimated_duration: 30.0
imports: from 2013.com.
requires:
device.category == 'AUDIO'
package.name == 'alsa-base'
package.name == 'gir1.2-
package.name == 'pulseaudio-utils'
manifest.
run it with plainbox with the following command (with manifest file created):
$ plainbox run -i "2013.com.
plainbox will complain about:
* missing dependency: '2013.com.
if it's written like this and it will be fine:
requires:
manifest.
device.category == 'AUDIO'
package.name == 'alsa-base'
package.name == 'gir1.2-
package.name == 'pulseaudio-utils'
Related branches
- Maciej Kisielewski (community): Approve
-
Diff: 61 lines (+23/-2)2 files modifiedplainbox/plainbox/impl/unit/job.py (+1/-1)
plainbox/plainbox/impl/unit/test_job.py (+22/-1)
Changed in plainbox: | |
status: | In Progress → Fix Committed |
Changed in plainbox: | |
status: | Fix Committed → Fix Released |
I would mark this as Low priority, since we know how to workaround it by putting the manifest requirement to the first place.
But please feel free to raise to priority.