On Tue, Jun 19, 2007 at 08:39:44AM +0200, Marc 'HE' Brockschmidt wrote: > This is a known problem with XFS (which is used as FS on the i386 > buildd) [1] - usually switching the order of the dh_fixperms and > dh_strip calls helps.
> Footnotes: > [1] I think it was something about not stripping the file is not +x or > something Actually, AFAIK it has to do with whether the *read* bit is set. I.e., the files are installed as a non-root user, readable only by the owner; then root tries to read the file in the binary target, without first changing the permissions. On Tue, Jun 19, 2007 at 12:02:15AM -0700, Russ Allbery wrote: > Er, weird. If this bug isn't going to be fixed soon, should dh_strip work > around it somehow? Getting everyone to change the order of their > debhelper calls is going to be hard. I haven't seen any reason to believe it's a bug in XFS, FWIW. If you know that the XFS behavior is a POSIX violation or something, that would be a good argument for changing the i386 buildd (though I'm not sure whether the i386 buildd that was installed with XFS is still the one in use). But even if the buildd were changed, Debian kernels support XFS and d-i supports XFS, so we can't prevent maintainers from uploading packages built in such an environment. How many packages are you seeing with this problem? I'm not keen on the idea of having dh_strip try to work around it, but maybe dh_strip could be changed to treat such failures as fatal errors at least. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
