Control: forwarded 884996 https://github.com/amule-project/amule/issues/126

On Sun, May 13, 2018 at 02:00:14PM -0400, Sandro Tosi wrote:
> > there is a pending transition of libupnp (see #884635) and amule
> > currently fails to build against the new libupnp-dev that is already in
> > experimental.
> 
> > The patch below fixes that and makes amule compile against both libupnp
> > from the 1.6 branch and the 1.8 branch. Note however that the patch
> > isn't completely suitable for upstream as is because an unmodified
> > libupnp 1.6.24 doesn't ship all needed compatibility defines, but
> > Debian's 1.6.24-4 does (and I expect upstream to merge them for 1.6.25).
> 
> has this been addressed by libupnp in the meantime?

libupnp 1.6.25 is released with these compatibility defines. I didn't
package it for Debian yet because there is nothing new compared to
1:1.6.24-4 and the upstream tarball doesn't match the git release tag.

> if so, could you please forward this patch to amule upstream at
> https://github.com/amule-project/amule/issues (possibly tagging @sandrotosi ?)

Just did that, https://github.com/amule-project/amule/issues/126 .

Best regards
Uwe

Attachment: signature.asc
Description: PGP signature

Reply via email to