Gianfranco Costamagna writes: >>This means building the package will give different results depending >>on dietlibc-dev installed or not? That shouldn't happen... >> >>Please check via some other means that a build using dietlibc has been >>requested; don't do different things just because a package happens to >>be installed. > mmm the result is not a different library, but an additional static library > put > in a non-standard directory, built with another glibc. > I think there is nothing to worry about :) > > this is the path: > /usr/lib/*/diet/*/libgdbm.a
It is a problem as the package might provide different functionality when someone else builds and uploads it. We had problems with packages built in non-clean environments for a long time, though it has admittedly become better with most (not all) developers building packages in clean environments (sbuild, pbuilder, ...) or using source-only uploads. Ansgar
