Picasa albums created have photos with the same filename

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a folder of files.
2. Enter the command: google create --title "Title" --photo ./Directory/*.*
3. All the resulting photos have the same filename on Google. Not sure if this 
will create problems in the Picasa database?

What is the expected output? What do you see instead?
I expected the command to iterate through the photos and upload them all. But 
instead it grabs the name of the first photo and applies it to all the uploaded 
photos. (I expect the above would have worked fine had I left the --photo off 
of the command.)

What version of the product are you using? On what operating system? 
(OS X 10.6.7, GoogleCL, google 0.9.13)

What
version of gdata-python-client (aka python-gdata)?
(Current version as of googlecl 0.9.13, installed at the same time)

Please provide any additional information below.

Original issue reported on code.google.com by jonathan...@gmail.com on 23 Jul 2011 at 2:38

[GoogleCodeExporter]

Addendum: I've tried this again today, with a clean install of current 
gdata-python-client and 0.9.13 of GoogleCL. It does the same thing whether I 
end the line with * or *.*
I also tried using Ubuntu instead of OS X: same result. It's perfectly possible 
to view and work with the resulting images in the web UI / GUI, but not using 
GoogleCL, since all files are identically named.
As a workaround, I'm going to post each photo individually, though that's not 
ideal.

Original comment by jonathan...@gmail.com on 23 Jul 2011 at 7:53

[GoogleCodeExporter]

Second comment: I foolishly mistyped the command in the illustration above. 
Here's what I'm actually using, and what is producing identical filenames 
within an album, for me:
google picasa create --date 2002-12-28 "2002_Gnome" ./"2002_Gnome"/*.jpg
(And it's the same if you use *.jpg, *.*, or just * on the end.)

Original comment by jonathan...@gmail.com on 23 Jul 2011 at 7:55

[GoogleCodeExporter]

Third commend: I installed GoogleCL and GData from the source links (hg / svn, 
as of 15:30pst July 23rd 2011) and find the same result. The command: 
google picasa create --date 2002-12-28 "2002_Gnome" ./"2002_Gnome"/*.jpg
Creates an album with a set of files identically named. (i.e. the "2002_Gnome" 
directory includes gnome1.jpg, gnome2,jpg, gnome3.jpg--but the album created on 
Picasa includes three different photos, all named gnome1.jpg--both in the 
"details" view on the page, and in the listing produced by google picasa list).

Original comment by jonathan...@gmail.com on 23 Jul 2011 at 7:45

[GoogleCodeExporter]

This is the workaround I'm using now:

google picasa create --date 2002-12-28 "2002_Gnome"; cd ./"2002_Gnome"; for i 
in *; do google picasa post --tags uncurated --title "2002_Gnome" $i; done; 
echo "That was 2002_Gnome"

It creates the album and then posts each image to it, and they each have 
individual filenames afterwards.

Original comment by jonathan...@gmail.com on 23 Jul 2011 at 7:56

[GoogleCodeExporter]

I can confirm the title (aka photo's filename) is wrongly set because after the 
first photo, the `photo_name` will have non-None value and cause the following 
photos to be set with same filename.

A patch is attached.

Original comment by livibet...@gmail.com on 7 Aug 2011 at 4:14

Attachments:

• fix-title-filename.diff

[GoogleCodeExporter]

Fixed in revision 561.  Sorry for the delay.

Original comment by jh...@google.com on 25 Aug 2011 at 5:02

• Changed title: Picasa albums created have photos with the same filename
• Changed state: Fixed

[GoogleCodeExporter]

That is fantastic! Thanks so much!

Original comment by jonathan...@gmail.com on 25 Aug 2011 at 12:38

[GoogleCodeExporter]

Hi, i had same problem, and i use it on WinXP; so, how i apply this revision 
561 on my google.exe? I read the help, and dont find any patch tool to windows, 
or any tool to do this

Original comment by michel.a...@gmail.com on 23 Sep 2011 at 12:22

[GoogleCodeExporter]

Michael, I believe you would have to a) download the source and then b) compile 
it. I cannot help you with compiling it, but I am sure if you do a quick google 
search there are plenty of howtos.

Original comment by dan.2...@gmail.com on 23 Sep 2011 at 2:12