Bug 442141 - '/etc/mono/mconfig' folder should be owned by mono-core package
Summary: '/etc/mono/mconfig' folder should be owned by mono-core package
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: mono
Version: 10
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-12 00:41 UTC by petrosyan
Modified: 2009-06-29 23:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-29 23:28:43 UTC


Attachments (Terms of Use)

Description petrosyan 2008-04-12 00:41:26 UTC
Description of problem:
'/etc/mono/mconfig' folder should be owned by mono-core package

Version-Release number of selected component (if applicable):
mono-core-1.9-7.fc9.x86_64

Steps to Reproduce:
1. rpm -qf /etc/mono/mconfig/*
2. rpm -qf /etc/mono/mconfig

Comment 1 Bug Zapper 2008-05-14 09:20:21 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 petrosyan 2008-06-11 21:53:59 UTC
this bug is still present in mono-core-1.9.1-2.fc9

Comment 3 Paul F. Johnson 2008-10-02 23:23:50 UTC
This is certainly fixed in rawhide, so I'll close this bug. If it's in 1.9.1, please open a new bug for it.

Comment 4 petrosyan 2008-10-02 23:38:27 UTC
this bug is still present in mono-core-2.0-8.fc10.x86_64

$ rpm -qf /etc/mono/mconfig/config.xml
mono-core-2.0-8.fc10.x86_64

$ rpm -qf /etc/mono/mconfig
file /etc/mono/mconfig is not owned by any package

Comment 5 Bug Zapper 2008-11-26 02:12:20 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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