Some particular cases can generate dupes

[GoogleCodeExporter]

Choose a picture A in iPhoto, copy it as A'. So A = A'.

Modify the picture A to B.
Modify the picture A' to C.

Use Phoshare to export.

Use fdupes to find duplicate file : you will find A and A'.

I can't say it's a bug. Some won't want to have duplicates in their results, 
some will, and most won't mind. Often, when B an C are in the same "event", one 
wouldn't like to have dupes in the Original directory. But when in different 
events ?

Maybe the best would be just to warn the phoshare user.

Original issue reported on code.google.com by edouard....@gmail.com on 10 May 2011 at 9:10

[GoogleCodeExporter]

I confirm it's not really a defect. 

You just have to duplicate a picture in iPhoto to get dupes with phoshare, even 
if iPhoto keeps knowing just one. But how to have it differently. Phoshare is 
there to turn a kind of database into a file tree.

I really think best solution is a warning if dupes are created. During process 
or at the end. 

Original comment by edouard....@gmail.com on 10 May 2011 at 12:51

[GoogleCodeExporter]

If you copy a picture in iPhoto, you actually end up with two pictures. They 
look exactly the same, but there are now two copies in your library. There is 
no way of telling at that point that these were the same image at one time. 
Plus, as soon as you start making changes, like edits or metadata updates, they 
aren't the same anymore.

Original comment by tsporkert on 17 May 2011 at 4:23

• Changed state: Invalid