Import in place instead of copying
Submitted by an unknown user
Link to original bug (#718502)
Description
---- Reported by shotwell-maint@gnome.bugs 2012-07-30 12:42:00 -0700 ----
Original Redmine bug id: 5598
Original URL: http://redmine.yorba.org/issues/5598
Searchable id: yorba-bug-5598
Original author: rom1v -
Original description:
My shotwell photo directory should be ~/Images/albums/photos.
After a full system reinstall, I did not check, it was reset to ~/Images, and I imported photos into it.
So I had my last photos in ~/Images(/2012) and all the others in ~/Images/albums/photos(/20xx). Both were referenced in shotwell database.
For removing the ~/Images/2012 photos from database, I moved the 2012 folder to another place (let's say /tmp/myphotos). I started shotwell, it removed the photos.
Then I wanted to import the photos to the right folder, so I clicked "File, Import from Folder...", I chose /tmp/myphotos (which now contains the photos I want to import to ~/Images/albums/photos).
It asked me if I want to COPY the photos or if I want to import keeping the photos in place. I chose COPY.
And it imported the photos in place, without copying into ~/Images/albums/photos. When I click on these new photos, open in file manager, it opens /tmp/myphotos.
Therefore, the COPY button in dialog box does not behave as expected.
Version : Shotwell 0.12.3, on Debian testing.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:45:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 1 year ago
-
Target version deleted (
<strike>
_0.12.3_</strike>
)
rom1v,
thanks for the bug report. Please note that the "Target version" field indicates the version in which we plan to fix a bug, not the version in which it was observed. It's usually best to leave this field blank when filing a bug at Yorba.
Comment 2
Updated by Lucas Beeler over 1 year ago
- Status changed from Open to 5
- Resolution set to invalid
This isn't a bug. Shotwell is behaving as specified. Your wrote:
I started shotwell, it removed the photos.
Shotwell did not in fact remove the photos; it merely marked them as "offline." References to them were still present in the database and so when you re-imported the photos you didn't really re-import them, you just brought them back online at a new location. If you want this process to work, you'll need to select all the affected photos and choose "Remove from Library" from the "Edit" menu. This will expunge the backing database records for the photos and allow them to be truly re-imported, with new photo IDs, instead of merely being brought back online.
Comment 3
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Invalid
--- Bug imported by chaz@yorba.org 2013-11-25 21:57 UTC ---
This bug was previously known as bug 5598 at http://redmine.yorba.org/show_bug.cgi?id=5598
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED INVALID