Merge lp://staging/~timo-jyrinki/oxide/arch_specific_replaces_lp1400275 into lp://staging/~oxide-developers/oxide/packaging.vivid
Proposed by
Timo Jyrinki
| Status: | Needs review | ||||
|---|---|---|---|---|---|
| Proposed branch: | lp://staging/~timo-jyrinki/oxide/arch_specific_replaces_lp1400275 | ||||
| Merge into: | lp://staging/~oxide-developers/oxide/packaging.vivid | ||||
| Diff against target: |
71 lines (+37/-9) 2 files modified
debian/changelog (+29/-7) debian/control (+8/-2) |
||||
| To merge this branch: | bzr merge lp://staging/~timo-jyrinki/oxide/arch_specific_replaces_lp1400275 | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Chris Coulson | Approve | ||
|
Review via email:
|
|||
Commit message
Change back the dependency order, add arch specific replaces
as a suggested fix to prevent the apt package installation problems
(LP: #1400275)
To post a comment you must log in.
Revision history for this message
| Timo Jyrinki (timo-jyrinki) wrote | # |
Revision history for this message
| Chris Coulson (chrisccoulson) | # |
review:
Approve
Revision history for this message
| Timo Jyrinki (timo-jyrinki) wrote | # |
Unmerged revisions
- 58. By Timo Jyrinki
-
Change back the dependency order, add arch specific replaces
as a suggested fix to prevent the apt package installation problems
(LP: #1400275) - 57. By Timo Jyrinki
-
* Use the new conflict arrangement still, but change the dependency
order of Oxide's own codecs packages to prefer the -extras.
This should hopefully solve the problem when setting up the
autopkgtest environment with packages that have a hard depedency
on the -extras package. (LP: #1399597)
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
This was an idea by RAOF which makes sense since the conflicts were also changed, but it has not been proven whether this solves the autopkgtests problem. Landing this would fix the dependencies back to the way they were intended, but if the autopkgtests start failing again it means no unity8/
It should be possible somehow to validate the fix by running autopkgtests for qtcreator-