[Bug 510097] Review Request: python-urwid - console user interface for python

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=510097





--- Comment #24 from Mamoru Tasaka <mtasaka at ioa.s.u-tokyo.ac.jp>  2009-08-06 06:24:32 EDT ---
(In reply to comment #23)
> Sorry for the typo and 
- Well, not typo. 
  The reason you got "non-standard-executable-perm" on str_util.so was 
  because with your mock str_util.so was created with "0775" permission, 
  not "0755", which does not occur when I try local rpmbuild or mockbuild 
  for dist-f12 i686, and try koji scratch build (i.e. when I try mockbuild,
  str_util.so was created with 0755 permission)
  I don't think this is because of umask issue, because at least rawhide
  rpm always sets umask to 022 when executing %prep, %build, %install:
--------------------------------------------------------------
DEBUG: Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.MTc5VE
DEBUG: + exit 0
DEBUG: + umask 022
DEBUG: + cd /builddir/build/BUILD
DEBUG: + '[' /builddir/build/BUILDROOT/python-urwid-0.9.8.4-3.fc12.i386 '!=' /
']'
-------------------------------------------------------------

> for forgetting the debug info. But why do libs need to
> be executable?  
- Because find-debuginfo.sh tries to extract debug information
  from binaries with executable permission only.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.