Merge lp:~raof/mir/more-packaging-tweaking into lp:mir
| Status: | Merged |
|---|---|
| Merged at revision: | 4250 |
| Proposed branch: | lp:~raof/mir/more-packaging-tweaking |
| Merge into: | lp:mir |
| Diff against target: |
23 lines (+4/-2) 1 file modified
debian/control (+4/-2) |
| To merge this branch: | bzr merge lp:~raof/mir/more-packaging-tweaking |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Mir CI Bot | continuous-integration | Needs Fixing on 2017-09-14 | |
| Dimitri John Ledkov (community) | Approve on 2017-09-14 | ||
| Alan Griffiths | 2017-09-13 | Approve on 2017-09-14 | |
|
Review via email:
|
|||
Commit Message
debian/control: Fix the dependencies of libmiral-dev
This is not *quite* correct - source:Version makes the package not BinNMUable - but Launchpad doesn't support BinNMUs anyway so it's harmlessly incorrect.
Description of the Change
I'm not *entirely* sure how it currently works, but I *know* this should work :)
| Dimitri John Ledkov (xnox) wrote : | # |
Yes! this is the way to do it, I was concerned that binary:Version will end up being the wrong thing when we override the version of that binary package.
| Mir CI Bot (mir-ci-bot) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
https:/
Executed test runs:
FAILURE: https:/
None: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
| Mir CI Bot (mir-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:4248
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
ABORTED: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
ABORTED: https:/
Click here to trigger a rebuild:
https:/

Plausible