The real problem, of course, is that f-spot PERMANENTLY changes date information in pictures, thereby corrupting them. An example:
1. Picture 0001.JPG is taken on 29th of May 2010 (29-05-10) 2. Picture is imported into f-spot with option "Copy to image folder" Expected behaviour would be: - Place image in new folder: ~/Images/2010/05/29/0001.JPG But the real behaviour is: - Place image in new folder: ~/Images/2029/05/10/0001.JPG This will, in the cases where the corrupted year is too far in the future, crash F-spot and mess up your database. As if this isn't bad enough, f-spot will also PERMANENTLY alter the metadata information in 0001.JPG, so the date will still be corrupted even if you import your pictures into another program. Just a warning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/636819 Title: F-spot error: Value is greater than Int32.MaxValue or less than Int32.MinValue -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
