setacl --add-public does nothing if any grantee has READ

Binary package hint: s3cmd

$ s3cmd info s3://smoser-test-us/smoser-rename.img.manifest.xml
s3://smoser-test-us/smoser-rename.img.manifest.xml (object):
   File size: 2140
   Last mod: Thu, 01 Jul 2010 17:25:26 GMT
   MIME type: binary/octet-stream
   MD5 sum: 7d3d3d5ddde1f2d95d84907ee85b2584
   ACL: smoser16: FULL_CONTROL
   ACL: za-team: READ
   URL: http://smoser-test-us.s3.amazonaws.com/smoser-rename.img.manifest.xml

$ s3cmd setacl --verbose --acl-public s3://smoser-test-us/smoser-rename.img.manifest.xml
INFO: Applying --exclude/--include
INFO: Summary: 1 remote files to update
INFO: s3://smoser-test-us/smoser-rename.img.manifest.xml: already Public, skipping [1 of 1]

The bug is that this is not "Public", but since one ACL has 'READ' it is read as public.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: s3cmd 0.9.9.91-1 [modified: usr/share/s3cmd/S3/S3.py usr/share/s3cmd/S3/ACL.py]
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
Architecture: amd64
Date: Tue Jul 6 11:06:34 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: s3cmd