doing that shows the issue in the charm that's preventing its publishing..

juju publish cs:~hazmat/precise/rack --debug
2013-08-15 14:03:08 INFO juju publish.go:125 local digest is
<email address hidden>
2013-08-15 14:03:09 INFO juju publish.go:139 charm cs:~hazmat/precise/rack
is not yet in the store
2013-08-15 14:03:09 INFO juju publish.go:151 sending charm to the charm
store...
2013-08-15 14:03:15 INFO juju publish.go:157 charm sent; waiting for it to
be published...
2013-08-15 14:04:04 ERROR juju supercommand.go:282 command failed: charm
could not be published: config: options.deploy_key.default: unexpected
value <nil>
error: charm could not be published: config: options.deploy_key.default:
unexpected value <nil>




On Thu, Aug 15, 2013 at 10:04 AM, Kapil Thangavelu <
<email address hidden>> wrote:

> one tool that might give some feedback is publishing this via the
> juju-core cli
>
> ie.
> cd ~/charms/precise/rack
> juju publish cs:~pavel-pachkovskij/precise/rack --debug
>
>
> On Thu, Aug 15, 2013 at 9:52 AM, Kapil Thangavelu <
> <email address hidden>> wrote:
>
>> The store goes by revid detection, it doesn't care about revnos. This
>> does appear to trigger a bug in the store code which needs addressing
>> regardless of a rename workaround.
>>
>>
>> On Thu, Aug 15, 2013 at 9:21 AM, Curtis Hovey <email address hidden>wrote:
>>
>>> ** Description changed:
>>>
>>> - I suspect there is an ingest issue when a file contains unicode. This
>>> - issue might be a juju store problem involving a missing revision.
>>> + This issue might be a juju store problem involving a missing revision.
>>>
>>>   cs v5, lp r5, of http://manage.jujucharms.com/~pavel-
>>>   pachkovskij/precise/rack is not showing README.md. I found a unicode
>>>   apostrophe in the file and advised pavel to remove it.  We are now
>>>   waiting for manage.jujucharms.com to show README.md. I know ingest as
>>>   seen lp r7 which has the fix, but the store does not see v5 yet.
>>>
>>>   The store sees
>>>   {
>>> -   "cs:~pavel-pachkovskij/precise/rack":{
>>> -     "revision":4,
>>> -
>>> "sha256":"3c1f949054da15ea183ee87d974a9db50e98caf5e6abd31b666ca65a194d2c37",
>>> -
>>> "digest":"<email address hidden>"
>>> -   }
>>> +   "cs:~pavel-pachkovskij/precise/rack":{
>>> +     "revision":4,
>>> +
>>>     "sha256":"3c1f949054da15ea183ee87d974a9db50e98caf5e6abd31b666ca65a194d2c37",
>>> +
>>>     "digest":"<email address hidden>
>>> "
>>> +   }
>>>   }
>>>
>>>   I do not see this revision in the branch.  staging's app.log shows
>>> -      Revision
>>> <email address hidden> not found
>>> +      Revision
>>> <email address hidden> not found
>>>
>>>   While writing this pavel pushed a new branch with a single revision.
>>>
>>>   Maybe The store finds this unacceptable and will not accept a
>>> historical
>>>   revisions. It ignores the new data, so charmworld does the same. If
>>> this
>>>   is the case, I think a new charm name is needed.
>>>
>>> --
>>> You received this bug notification because you are a member of
>>> Charmworld Developers, which is subscribed to charmworld.
>>> https://bugs.launchpad.net/bugs/1209321
>>>
>>> Title:
>>>   New revisions are missing
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/charmworld/+bug/1209321/+subscriptions
>>>
>>
>>
>