Actually, another commit in the same Debian package release removes
the breakage that made a fix impossible. When I last tried to fix
this, around may 2nd, there was no fix that did not involve removing
code from the apache2 source package that intentionally crippled
mpm-itk. I'll try to find some time tomorrow to test the current
Debian apache2 snapshot on Ubuntu and see if mpm-itk can be modified
to install cleanly in time for trusty's .1 release.
Have you ever spent two days of your time fixing a package, only to
have the upstream maintainer say, "nah, I wanted this dead, rejecting
your patch"? Been there, done that, got the t-shirt. That's why I
wanted the breakage out before I spent even one more minute on this.
Actually, another commit in the same Debian package release removes
the breakage that made a fix impossible. When I last tried to fix
this, around may 2nd, there was no fix that did not involve removing
code from the apache2 source package that intentionally crippled
mpm-itk. I'll try to find some time tomorrow to test the current
Debian apache2 snapshot on Ubuntu and see if mpm-itk can be modified
to install cleanly in time for trusty's .1 release.
Have you ever spent two days of your time fixing a package, only to
have the upstream maintainer say, "nah, I wanted this dead, rejecting
your patch"? Been there, done that, got the t-shirt. That's why I
wanted the breakage out before I spent even one more minute on this.