Description of problem: dangling: /usr/lib64/samba/nss_info/rfc2307.so -> ../idmap/ad.so dangling: /usr/lib64/samba/nss_info/sfu.so -> ../idmap/ad.so dangling: /usr/lib64/samba/nss_info/sfu20.so -> ../idmap/ad.so Version-Release number of selected component (if applicable): How reproducible: Always 1 clean install, apply updates, reboot 2. click up a terminal 3. su - root 4. symlinks -r / | grep dangling
Hi, thanks for reporting this bug. Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedAssignee: bugsquad => bgmilne
Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher. Is this one still valid for Mageia 2 rc? If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. If it wasn't assigned correctly, please assign back to Bug Squad and explain.
(In reply to comment #2) > > Is this one still valid for Mageia 2 rc? Yes, dangles are still there after clean install of Mageia-2-rc-x86_64-DVD.iso + updates.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
(In reply to comment #4) > Please report whether this bug is still valid for Mageia 2. still valid.
Keywords: NEEDINFO => (none)CC: (none) => sander.lepik
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Still valid in 3_alpha3
Assignee: bgmilne => bgmilne
CC: (none) => junknospam
Hi Bit Twister, I know this bug is still valid. I have additional questions: - Does the absence of this file (ad.so) result in missing functionality within samba? - The same in reverse: Would dropping the three dangling symlinks from the package result in breakage? I think I have the problem fixed, but as I don't use samba myself, I wanted to confirm the functionality of these files before submitting the adjusted package. Thanks in advance for any insight you have on this.
CC: (none) => remco
I think nss_info as well as the (missing) idmap directory should all move to the samba-winbind package. If anyone disagrees, speak up soon or hold your silence for another three years :-)
(In reply to Remco Rijnders from comment #8) > Hi Bit Twister, > > I know this bug is still valid. I have additional questions: > > - Does the absence of this file (ad.so) result in missing functionality > within samba? > - The same in reverse: Would dropping the three dangling symlinks from the > package result in breakage? My WAG, no. > I think I have the problem fixed, but as I don't use samba myself, I wanted > to confirm the functionality of these files before submitting the adjusted > package. I have no insight and do not use the rpm. It was there because of the default install from a all package group install of a Mageia-X-x86_64-DVD.iso > Thanks in advance for any insight you have on this. In my stupid opinion, when the target of the link is installed, that rpm should create the link.
What's WAG? Google suggests "Wives And Girlfriends", but that might not be what you mean... It seems to me both the target of the link and the links themselves should be part of the same package. I'll go ahead and push the update. Thanks for reporting this :-)
QA, Can you please test samba-3.6.25-2.mga5 ? See comment #1 on how to test for the problem. Affected files have been moved to the samba-winbind package.
QA Contact: (none) => qa-bugs
(In reply to Remco Rijnders from comment #11) > What's WAG? Google suggests "Wives And Girlfriends", but that might not be > what you mean... http://www.urbandictionary.com/define.php?term=wild+ass+guess
closing bug
Status: NEW => RESOLVEDResolution: (none) => FIXED