Merge lp:~hjd/widelands/disabled-s390-patch into lp:~widelands-dev/widelands/debian
Status: | Merged |
---|---|
Merged at revision: | 20 |
Proposed branch: | lp:~hjd/widelands/disabled-s390-patch |
Merge into: | lp:~widelands-dev/widelands/debian |
Diff against target: |
8 lines (+0/-1) 1 file modified
debian/patches/series (+0/-1) |
To merge this branch: | bzr merge lp:~hjd/widelands/disabled-s390-patch |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
SirVer | Approve | ||
Review via email: mp+217293@code.launchpad.net |
Description of the change
What it says <del>on the box</del> in the commit message.
The ppa currently fails to build [1] because the s390_new_
I've scheduled a test build for this [2], which I'll probably just merge it when I've verified it builds as expected.
I wonder though, whether we should simply disable the rest of the patches in the Debian packaging too? Just in order to avoid similar issues in the future. This is the second one which has broken the build because it can't be applied, and I don't think we will have less code changes as the development cycle progresses. (Apart from the debug symbols patch, they're for obscure architectures which Ubuntu isn't even targetting so the PPA won't build on them.)
[1] https:/
[2] https:/
As mentioned, I merged this when I saw that my test build went green. I don't like to skip the review stage, but this patch is fairly minimal and non-intrusive. I also took the liberty of doing the same patch on the debian-precise branch.