<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 09/12/16 06:32, John Meinel wrote:<br>
</div>
<blockquote
cite="mid:CAHE3fn6GSg6A_zHU1Eix4_BigSVsVc5o-ZiCp91Z=4Yd=KcK0A@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div>
<ol>
<li>"charm push cs:~jameinel/ubuntu-lite" fails ultimately
with a TLS timeout error:<br>
ERROR cannot post archive: Post <a moz-do-not-send="true"
href="https://api.jujucharms.com/charmstore/v5/%7Ejameinel/ubuntu-lite/archive?..">https://api.jujucharms.com/charmstore/v5/~jameinel/ubuntu-lite/archive?..</a>.:
net/http: TLS handshake timeout<br>
I thought the point of multi-series charms is that you
didn't have to publish to an explicit series.</li>
</ol>
</div>
</div>
</blockquote>
<br>
You should be validated that there are *some* relevant series, with
one as the default.<br>
<br>
<blockquote
cite="mid:CAHE3fn6GSg6A_zHU1Eix4_BigSVsVc5o-ZiCp91Z=4Yd=KcK0A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<ol>
<li>The result of a successful push tells you "unpublished".
But the command to actually publish one is "charm
release". Should we be using the verbiage of "unreleased"?
Certainly there was no indication of what I should be
doing to get the charm to a 'published' state from the
CLI.</li>
</ol>
</div>
</div>
</blockquote>
<br>
Yes, that makes sense, the feedback should use the 'release' term
and should tell you how to make that happen. It should also be
possible to have the push command also --release [channels]<br>
<br>
<blockquote
cite="mid:CAHE3fn6GSg6A_zHU1Eix4_BigSVsVc5o-ZiCp91Z=4Yd=KcK0A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<ol>
<li>ubuntu-lite does get from "pending" to "active" a fair
bit faster than the full 'ubuntu' charm (about 1-2 minutes
on my LXD provider.)</li>
</ol>
</div>
</div>
</blockquote>
<br>
Sounds like we can make reactive a little leaner.<br>
<br>
Mark<br>
</body>
</html>