On Sun, Jan 12, 2014 at 11:02:32PM +0100, Stefan Fritsch wrote:
The code is only executed when running buildconf to re-create
configure. This is not normally done during package build. Therefore
the patch to build/config-stubs is sufficient to avoid the problem in
the future if/when someone
Hi Robie,
Am Montag, 6. Januar 2014, 13:01:06 schrieb Robie Basak:
I'm wondering if there's more of a potential issue in Ubuntu than in
Debian here. Our next release will be supported for five years, so
I expect that we'll backport a number of as-yet-unknown bug fixes.
As we're team based, it
Hi Stefan,
Thank you for explaining this to me.
On Sat, Jan 04, 2014 at 07:11:58PM +0100, Stefan Fritsch wrote:
You are right, the real fix is not included. We fixed the issue by
removing the patches that touch *.m4 files. Therefore, no *.m4 file
will be created in the .pc directory.
Hi Robie,
Am Freitag, 3. Januar 2014, 16:53:26 schrieb Robie Basak:
I'm merging apache2 2.4.7-1 from Debian into Ubuntu, but I can't
find the fix in Debian for this issue. The upstream fix doesn't
seem to be present, and I tried dropping a config*.m4 file into
.pc/ and the configfiles= line
