Merge lp:~hjd/widelands/disabled-s390-patch into lp:~widelands-dev/widelands/debian

Proposed by Hans Joachim Desserud
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
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_architecture patch fails to apply cleanly due to changes in trunk. Unlike the kFreeBSD issue, this has not been applied to trunk AFAIK, so I left the patch itself alone.

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://launchpadlibrarian.net/173632745/buildlog.txt.gz
[2] https://code.launchpad.net/~hjd/+recipe/widelands-test

To post a comment you must log in.
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

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.

Revision history for this message
SirVer (sirver) wrote :

I looked through this and I wondered why you did not also delete the patch file. Unused files in a repository are usually a bad idea, since they are forgotten over time. If somebody needs it back in the future, they can reverse-cherrypick your commit.

Otherwise lgtm.

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'debian/patches/series'
2--- debian/patches/series 2014-03-11 20:57:31 +0000
3+++ debian/patches/series 2014-04-25 20:18:37 +0000
4@@ -1,4 +1,3 @@
5 mips_gcc_ICE_with-03
6-s390_new_architecture
7 hurd_PATH_MAX_missing
8 dbg_symbols

Subscribers

People subscribed via source and target branches