On 5/12/24 17:59, Samuel Sieb wrote:
On 12/4/24 1:40 PM, Stephen Morris wrote:
Hi,
I got the message below when I ran sudo DNF Upgrade. Why are these messages appearing when I ran "sudo symlinks -r -d /" a couple of days ago? After getting the messages I ran "sudo symlinks -r / | grep -i dangling" again and it reported dangling symlinks in the ".build-id" folder again, what I didn't check was whether or not those dangling symlinks were what was shown in the DNF messages. The messages I've shown below are similar messages to what I got, not the actual messages, as I made a mistake and issued another command in the Konsole tab the messages were in, which caused Konsole to remove the messages from its display history. I think the package being cleanup up which produced the messages was binutils, but I can't be sure.
That's why it's appearing. Because you ran that command and removed files that were controlled by an rpm package.
[29/48] Removing webkitgtk6.0-0:2.46.3-1.fc41.x86_64 100% | 545.0 B/s | 90.0 B | 00m00s
>>> [RPM] file /usr/lib/.build-id/c7/ b48abe760b785ae0bb17cbc014e4cd1f0cca07: remove failed: No such file or directory
>>> [RPM] file /usr/lib/.build- id/68/87fa9a14953d0a201d994f4b5445f4f9cc8a76: remove failed: No such file or directory
The other question I have on this is are the DNF messages "real" messages or are they like the failure messages when attempting to update properties in KDE Destop icons that a links to locations owned by root, in that the DNF cleanup process attempted to delete the file/folder the symlink was pointing to which failed and it reported the failure against the symlink not again what it was actually trying to delete?
Yes, those are real. You deleted a file that it was expecting to be there. That symlink cleanup idea is not a good one. I've checked my system that has been upgraded for multiple versions and there are no dangling symlinks that should be removed. I described that finding in an earlier thread on this topic.
I saw that response but I still don't understand that functionality. It is my understanding, which could be completely wrong, that a symlink is not a physical file as such and doesn't contain any data as such, it just links to somewhere that does contain the data (be it a file or folder). If the target has actually gone, which is what I understand a dangling symlink to be, hence the symlink points to nothing (which means the symlink is broken), how is the symlink of any use and what useful purpose does it actually serve?
regards,
Steve
Attachment:
OpenPGP_0x1EBE7C07B0F7242C.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
