On Sat, 2016-04-09 at 11:56 +0200, Christof Koehler wrote: > Hello, > > yes, indeed the 5.0.7 source deb rebuild is very strange. I also > checked > the libraries under debian/usr/lib/... in the build directory and they > do not contain a libtirpc reference. > > I can see two possible strategies: > 1. Concentrate on the 5.1.1 deb source I grabbed from ubuntu 16.04 > and the > deb package rebuild from that. Those libraries obviously contain a > reference > to libtirpc but do not mount anything. Too old libtirpc comes to mind > then ? An old libtirpc is a possibility. And I think the best chance is to use 5.1.1 and possibly back port any changes. But I don't have an IPv6 environment I can use to help so that's a problem straight away. As I say, the only other thing we can do is add some targeted debug logging and see if we can spot what is going wrong. There have't been any changes to the RPC code since 5.1.1 (at least none that I remember, I'll check later) so that should be a good source base to use regardless of whether it's built from original source or deb package. I know there were some changes to libtirpc but I use a lower level of communication and those changes formed the bulk of the changes I made to autofs for the RPC communication. Maybe I missed some dependencies myself, hard to tell really without knowing what's going on. Ian -- To unsubscribe from this list: send the line "unsubscribe autofs" in
