Bug 175743 - directory umask problem not yet fixed
Summary: directory umask problem not yet fixed
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xscreensaver
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-14 14:46 UTC by Mamoru TASAKA
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: 4.23-1
Clone Of:
Environment:
Last Closed: 2006-01-23 13:09:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mamoru TASAKA 2005-12-14 14:46:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.8) Gecko/20051211 Fedora/1.5-1.1 Firefox/1.5

Description of problem:
In the bug 161728, I proposed the fix to have xscreensaver rpms  
own the requires directories with appropriate permission.

My patch (id=121836) is for writing out the directories name where some
files are installed (with messages like "Installing *** in the directory
***") and the messages are catched by the new list_files  
( The part "sed -e 's@.*directory.* \(/[^ ]*\)$@ \1DIR@'"  is for dealing   
with the message "in the directory ***" newly added by the patch). 
So, as of my proposal fixes, only changing list_files makes no effect.

It seems that I cannot reopen the bug 161728 (perhaps it was not me that   
opened the bug ), so I newly opened this bug.  

Version-Release number of selected component (if applicable):
xscreensaver-4.22-21

How reproducible:
Always

Steps to Reproduce:
1. check " rpm -qlpvv xscreensaver-base-4.22-21.i386.rpm"
2.
3.
  

Actual Results:  No directory is included in xscreensaver-base-4.22-21 rpm 
(and the other 2 rpms).


Expected Results:  Three xscreensaver rpms should own the required directories
correctories.

Additional info:

Comment 1 Mamoru TASAKA 2005-12-14 14:55:50 UTC
The expected results is "The xscreensaver rpms should own the
required directories correctly", sorry for my typo...

Comment 2 Mamoru TASAKA 2006-01-23 13:09:53 UTC
Verified that this is fixed in 4.23.
Thanks.


Note You need to log in before you can comment on or make changes to this bug.