Comment 9 for bug 1058035

Yes well, I did the package as commits in the original Debian packaging
CVS module, so naturally the Ubuntu changes are “on top”. I have no idea
what a branch merge proposal is. You should really accomodate the random
Debian Developer who happens to care about his packages and even tries to
watch Launchpad bugs related to it better, not force some magic ways they
do not know on them. Please find attached a debdiff against the current
Debian version of the package and do with that whatever you must.

And of course it could be sponsored. The Ubuntu diff per sé only exists
because build profiles are not there yet, and the build dependency is
an optional one. So normally you’d do a sync from Debian on each of my
uploads to it, which all are made from that CVS module.

Although I do agree that dpkg-source randomly reordering chunks when
using single-debian-patch is annoying and introduces lots of noise in
that patch. I will file a bugreport against dpkg in Debian for that.
The relevant CVS commits are the following two; I’ve attached diffs
for them too; the first one adds the Ubuntu change, the second one
fixes this problem report. I can make a “cleaned up” debdiff, too,
by manually editing it, I guess…

Commit ID: 10050676B433400B7BD
CVSROOT: /cvs
Module name: contrib
Changes by: <email address hidden> 2012/09/29 21:42:12 UTC

Modified files:
        hosted/tg/deb/mksh/debian: changelog control

Log message:
merge: mksh (40.9.20120630-1ubuntu1) quantal; urgency=low
________________________________________________________________________

Commit ID: 10050676F947E588244
CVSROOT: /cvs
Module name: contrib
Changes by: <email address hidden> 2012/09/29 22:00:33 UTC

Modified files:
        hosted/tg/deb/mksh: Build.sh
        hosted/tg/deb/mksh/debian: changelog meat
Added files:
        hosted/tg/deb/mksh/debian: rtchecks

Log message:
move some compile-time checks to run-time (LP#1058035)