severity 483350 normal thanks >> I'm not sure if I should simply label your build environment as broken, >> or if I need to move the sockets directory to some place with a shorter >> path name. > > I disagree with my build environment being broken: > /build/user-pperl_0.25-5-amd64-0uuJx5/pperl-0.25-5/sockets/pperlnPLXc7 > isn't such a long path.
There are less than 40 remaining characters for creating a unique UNIX domain socket name. Suppose we use base16(MD5(path)), we end up with 32 characters, plus the path to the sockets directory. This is a very narrow margin. If you insist on using this particular buildd configuration (which is not matched by any official buildd, AFAICT), please take this issue to the technical committee, or make it explicit in Policy. Of course, I could use a temporary directory outside the build tree, but if I honour TMPDIR, someone could still play similar games with me, so I don't see the point of doing that. (We should hash the path name because long script paths might occur in the real world, so this is still a bug.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
