Package: ejabberd Version: 1.1.2-6 This is a re-submit of bug #329721, which has already been archived. It was closed even though it hadn't really been fixed and I haven't gotten any reply to an email I sent to the maintainer concerning the bug 1.5 years ago, in which I explained why I wouldn't consider the bug resolved.
Here is a copy of what I wrote in said email: | Well, what is the 'right' umask then? It is true that the umask under | which I started dpkg-buildpackage was 077, so that is quite likely to be | the cause of this problem. I personally, however, tend to consider it a | bug if a source package builds a kindof-broken binary package when the | build is started under a certain (not completely nonsensical) umask. | | I couldn't find any hints in the Debian policy manual as to who is | responsible for providing which umask when building a package and I'm | not all that familiar with other principles applied in such cases in | the Debian project, but as I understand it, any binary package is supposed | to be possible to be built from the corresponding source package by | applying a certain procedure to the source package on a "sensibly | configured Debian System". Now, as I consider a 077 umask a completely | valid and sensible configuration, I'd expect this procedure to work | under these circumstances and to produce a package functionally | equivalent to what is in the Debian archive. | | Now, it might be sensible to make the policy manual and any build | systems guarantee a certain umask instead of making every package | independent of the umask - but that doesn't make the current behaviour a | non-bug from my point of view, rather maybe the responsibility for fixing | it would be someone else's. After all, the bug is that (I guess) most | wouldn't expect the behaviour as-is plus there doesn't seem to be a good | reason for this unexpected behaviour, so it should be changed. Meanwhile I can say that changing the umask does indeed change the permissions of the files in the package, and at least the etch package is still affected. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
