Hi Vincent, Andreas, [...] > The fact is that, to my knowledge, the package successfully builds > on all Debian build machines.
That's true (with the exception of s390x, but that's a completely different issue) - it seems the buildds, according to the logs, have /sbin in the PATH. > Note that I was not arguing against the fact that this is a bug, > only about the severity. Seeing with your answer that the bug is still > there with "dpkg-buildpackage -rfakeroot" I would give it the "normal" > or "important" severity. But not more (ie not RC) as official Debian > build machine correctly work. > I'm absolutely fine with this, I'm not going to argue with the maintainer about severity. I'd just use "serious" as my default severity for FTBFS as I cannot generally tell whether the official buildds work around that problem in some way. > > Well, the change was just a proposal, you might want to go for an entirely > > different solution. (Indeed I'm not sure why ldconfig is being run at all.) > > Look at the sources, I'm not sure myself. The call has been added > by Andreas so I will wait for him to comment. > [...] So, Andreas, why was that change http://anonscm.debian.org/gitweb/?p=collab-maint/papi.git;a=commit;h=a37ddbb5f2eb6cee322ff104d9f05c4fa6127ee8 necessary? I can see what it does, but I'm not sure why that would be necessary in the first place (after all, the links ought to be correct at the end of the build process anyway). Best, Michael
pgpxx3ys2a8hd.pgp
Description: PGP signature
