Description of problem: 14/47: lib64fuse2 ############################### 15/47: bluez ############################# failed to read link /bin/bluepin: No such file or directory after update install # symlinks -r / | grep dangling dangling: /usr/bin/bluepin -> /etc/alternatives/bluepin dangling: /etc/alternatives/bluepin -> /usr/bin/bluepin Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. script -c "urpmi --download-all --downloader wget --auto --auto-update" update.log 2. grep fail update.log 3.symlinks -r / | grep dangling
Assigning to package maintainer.
Assignee: bugsquad => shlomif
(In reply to Bit Twister from comment #0) > Description of problem: > > 14/47: lib64fuse2 ############################### > 15/47: bluez ############################# > failed to read link /bin/bluepin: No such file or directory > > after update install > # symlinks -r / | grep dangling > dangling: /usr/bin/bluepin -> /etc/alternatives/bluepin > dangling: /etc/alternatives/bluepin -> /usr/bin/bluepin > > > Version-Release number of selected component (if applicable): > > > How reproducible: > > > Steps to Reproduce: > 1. script -c "urpmi --download-all --downloader wget --auto --auto-update" > update.log > 2. grep fail update.log > 3.symlinks -r / | grep dangling The "bluepin" script appears to have been removed from the bluez package back in 2006 (although its removal is not mentioned in the ChangeLog). I removed all references of it from the package in bluez-5.41-2, and the dangling symlinks can be safely removed.
(In reply to Shlomi Fish from comment #2) > (In reply to Bit Twister from comment #0) > > Description of problem: > > > > 14/47: lib64fuse2 ############################### > > 15/47: bluez ############################# > > failed to read link /bin/bluepin: No such file or directory > The "bluepin" script appears to have been removed from the bluez package > back in 2006 (although its removal is not mentioned in the ChangeLog). I > removed all references of it from the package in bluez-5.41-2, and the > dangling symlinks can be safely removed. I remove all dangling links prior to doing updates. The new package created the dangling links.
Did you try bluez-5.41-2.mga6 which was pushed 4 hours ago?
(In reply to Rémi Verschelde from comment #4) > Did you try bluez-5.41-2.mga6 which was pushed 4 hours ago? Sorry went to bed at 2am and have been working through all the email at the moment. Newest release does not create the dangle.
Status: NEW => RESOLVEDResolution: (none) => FIXED