[Shotwell] Import failed. But which files weren't copied???

[Adam Dingle]

Chris,

On Fri, Nov 26, 2010 at 5:00 AM, bigchris <chris at bigchrisrogers.com> wrote:

>
> After a new install of Ubuntu 10.04  I'm moving my files from the previous
> hard disk onto the new one.  I decided to organise my pictures and Shotwell
> looks to be just the tool.  I have about 2,800 photos.  I started shotwell
> and pointed at my old Pictures directory for import and told it to copy all
> the originals to the new disk.  I left it doing this overnight and in the
> morning it was finished, great.
>
> Shotwell reported 159 had failed to import and listed a few of them in the
> message box.
>
> Additionally it reported some non-recognised format (these were .png/.gif)
> which I moved manually and 310 non-image files which were the avi videos
> from my camera, which I moved by hand.
>
> My main problem is with the 159 failed to import jpg files.  i want to
> delete all the files from the old hard disk but don't want to loose 159
> photos, particularly when I don't know which ones will be lost.  How do I
> find out which have not been imported so that I can attend to them?
>

Several users have now requested that Shotwell log or report all files which
were not imported in the course of an import operation.  We have a ticket
for this here:

http://trac.yorba.org/ticket/2593

This shouldn't be too hard, so I hope we'll be able to implement this for
Shotwell 0.9 at the latest.


>
> I've tried the method proposed by Adam Dingle in the thread "Tracking file
> that have not successfully imported" but this doesn't seem to work.  I can
> get the two sorted lists O.K. but each include the directory path in the
> filename and different directories are used.  When I comm the files the
> result is the same as filelist1, i.e. suggesting that all the files are
> missing.
>

If different directories are involved, I hope you should still be able to
use a simple search/replace (e.g. using sed, or your favorite text editor)
to make the files match.  I know this is an awkward workaround, and I hope
the report log feature will make all this unnecessary once we implement it.

adam