Bug 493125 - crda package is missing dependency for iw
Summary: crda package is missing dependency for iw
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: crda
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-31 17:52 UTC by John W. Linville
Modified: 2009-04-02 17:10 UTC (History)
1 user (show)

Fixed In Version: 1.0.1_2009.03.09-9.fc10
Doc Type: Bug Fix
Doc Text:
Clone Of: 492762
Environment:
Last Closed: 2009-04-02 17:10:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John W. Linville 2009-03-31 17:52:08 UTC
+++ This bug was initially created as a clone of Bug #492762 +++

Description of problem:

Latest crda package includes setregdomain which calls iw:

$ fgrep iw /sbin/setregdomain
        iw reg set $COUNTRY
iw reg set $COUNTRY

But crda package doesn't have a dependency on iw so it is not installed automatically:

$ rpm -q crda --requires
/bin/sh
libc.so.6()(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3.4)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libgcrypt.so.11()(64bit)
libnl.so.1()(64bit)
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rtld(GNU_HASH)
udev

Therefore setregdomain fails with an error and the regulatory domain is not set correctly.

Version-Release number of selected component (if applicable):
crda-1.0.1_2009.03.09-8.fc11.x86_64

How reproducible:
Always

Comment 1 Fedora Update System 2009-03-31 17:58:29 UTC
crda-1.0.1_2009.03.09-9.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/crda-1.0.1_2009.03.09-9.fc10

Comment 2 Fedora Update System 2009-04-02 17:10:36 UTC
crda-1.0.1_2009.03.09-9.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.


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