Hello! I've looked briefly at the amsn build failure and it looks to me like when the build failed, "make configure" got triggered when it was not supposed to. It seems the cause for this might be because the patches modifying both configure and configure.ac might cause the latter to (sometimes) get a newer modification date.
A couple of different possible solutions have been thrown in the air: a/ touch configure in debian/rules before running $(MAKE) b/ add a patch that disables the configure rebuilding rule in Makefile c/ adding build-dependencies for autoreconf and making sure it runs every time (before configure runs!) If this was my own package I'd update the packaging to use dh and use the new dh_autoreconf helper to handle updating stuff rather then manually patching configure. (ie. an elaborated version of c/) In case I need to NMU amsn to avoid it blocking the gssdp/gupnp transition further I'd likely go for option b/, which I think is more obvious and less error prone then a/. Would be great to get any input on this... otherwise I guess a NMU with option b/ will be the way forward soon. -- Andreas Henriksson
signature.asc
Description: Digital signature
