GNOME Bugzilla – Bug 626752
Improper handling of Symlinked files
Last modified: 2010-10-14 13:04:23 UTC
this report has been filed here: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/579270 "When copying a number of symlinks into Brasero, Brasero reports that the space used totals that of the actual files pointed at from the symlinks and not the symlinks themselves. After burning, it becomes evident that only the symlinks were burned and not the actual files. While it isn't necessarily a problem that it won't burn the actual file (it would be nice if there was an option to fetch the file instead if the symlink points off the disk), it shouldn't report that it will be using all the space of the actual files pointed at by the symlinks. I discovered this because I had a directory full of about 70 symlinks to photos (use the symlinks to sort out the bad ones without accidentally deleting the originals) that I wanted to burn. I decided to try to just move the symlinks over (I upload to websites by pointing the the symlinks), and when Brasero said that it would be filling about half the CD, I figured it was going to be burning the actual jpg files. After burning, I realized that the initial estimate was way off and it had only burned a few KB of data."
Thanks for the report. I checked with my version of brasero and all seems fine but maybe I did not understand what you said correctly. Let me explain how brasero deals with symlinks : there are two options (controlled in the filtered files area or a Data Project, click the Option button) either brasero uses the symlink and therefore the project size will (or should reflect the size of the symlinks) or it replaces them with the files they actually points to and therefore the size of the project reflects the size of the actual files. Could there be any confusion? Could you try how brasero reacts with: - option replace symlinks off - option replace symlinks on please? (In reply to comment #0) > "When copying a number of symlinks into Brasero, Brasero reports that the space > used totals that of the actual files pointed at from the symlinks and not the > symlinks themselves. After burning, it becomes evident that only the symlinks > were burned and not the actual files. > While it isn't necessarily a problem that it won't burn the actual file (it > would be nice if there was an option to fetch the file instead if the symlink > points off the disk), it shouldn't report that it will be using all the space > of the actual files pointed at by the symlinks. > > I discovered this because I had a directory full of about 70 symlinks to photos > (use the symlinks to sort out the bad ones without accidentally deleting the > originals) that I wanted to burn. I decided to try to just move the symlinks > over (I upload to websites by pointing the the symlinks), and when Brasero said > that it would be filling about half the CD, I figured it was going to be > burning the actual jpg files. After burning, I realized that the initial > estimate was way off and it had only burned a few KB of data."
ping pedro?
i'm closing the bug i did not get any response from the reporter on the downstream report, thanks all.