Bug#822921: uwsgi: FTBFS with latest apache2

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#822921: uwsgi: FTBFS with latest apache2

Vincent Cheng-2
Source: uwsgi
Version: 2.0.12-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

uwsgi currently FTBFS in sid. It looks like it might have something to
do with recent changes in apache2, because uwsgi builds fine with
apache2-dev/2.4.18-2 installed, but FTBFS with apache2-dev/2.4.20-1
(currently in sid). Buildd logs show that uwsgi FTBFS after having
been binNMU-ed for the gloox transition, but uwsgi actually builds
fine with either version of gloox (1.0.13-3 or 1.0.15-2) as long as
the older version of apache2-dev is installed, so this FTBFS wasn't
caused by the gloox transition.

buildd logs can be found at [1] as usual, tail as follows:

apache2/mod_proxy_uwsgi.c:262:21: error: static declaration of
'ap_proxy_buckets_lifetime_transform' follows non-static declaration
 static apr_status_t ap_proxy_buckets_lifetime_transform(request_rec *r,
                     ^
In file included from apache2/mod_proxy_uwsgi.c:50:0:
/usr/include/apache2/mod_proxy.h:1069:29: note: previous declaration
of 'ap_proxy_buckets_lifetime_transform' was here
 PROXY_DECLARE(apr_status_t) ap_proxy_buckets_lifetime_transform(request_rec *r,
                             ^
apxs:Error: Command failed with rc=65536

Regards,
Vincent

[1] https://buildd.debian.org/status/package.php?p=uwsgi&suite=unstable

Reply | Threaded
Open this post in threaded view
|

Bug#822921: uwsgi: FTBFS with latest apache2

Jonas Smedegaard
Hi Vincent,

Thanks a lot for your analysis - and for sharing why uwsgi was binNMU'ed
(QA page didn't reveal it).

Quoting Vincent Cheng (2016-04-29 02:14:08)
> Buildd logs show that uwsgi FTBFS after having been binNMU-ed for the
> gloox transition, but uwsgi actually builds fine with either version
> of gloox (1.0.13-3 or 1.0.15-2) as long as the older version of
> apache2-dev is installed, so this FTBFS wasn't caused by the gloox
> transition.

I agree this does not look like caused by the gloox change.  It is my
headache to tackle.

Thanks again,

 - Jonas

--
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc (836 bytes) Download Attachment