So the main caveats as I see them are:
1) since it didn't come from an official source we flag it as such (the
mechanism was originally developed to allow developers to test out their
in-progress code changes). So your version numbers I "juju status" won't
exactly match
2) if you ever need to depl
Thanks for continued work to address bug we have log and make
jujuchrms.com and even better site. The API is also a welcome update
too.
-Antonio
On Wed, Jan 14, 2015 at 2:36 PM, Rick Harding
wrote:
> The UI Engineering team would like to let everyone know we had a release
> landslide today.
>
>
The UI Engineering team would like to let everyone know we had a release
landslide today.
First, there’s a new Juju GUI (1.3.0) release in preparation for 1.21 that
supports the new user code in 1.21. This means that when that lands the GUI
will support logging in with newly created users. The GU
Greetings,
I've been running juju 1.21-beta4 for a while now and I haven't altered any
streams information as the announcement email would suggest I need to. I'm
aware of the --upload-tools command and have used it in place of doing any
environments.yaml edits when my bootstraps fail due to findin
seafile: I ran into an unbound variable error that broke the deployment. Thanks
to a quick response from José, though, the issue has been fixed and now has my
+1.
https://code.launchpad.net/~jose/charms/precise/seafile/fixes/+merge/244636
mysql: simple backups
Works as expected. I’d like to se
+1
On Jan 14, 2015 12:54 PM, "Marco Ceppi" wrote:
> Hey everyone,
>
> There's currently quite a few version of juju available [0] from various
> sources (cloud archive, ubuntu archive, stable ppa, source). While I know
> the release team is doing a great job in making sure that versions of juju
>
Hey everyone,
There's currently quite a few version of juju available [0] from various
sources (cloud archive, ubuntu archive, stable ppa, source). While I know
the release team is doing a great job in making sure that versions of juju
are consistent across platforms, it's inevitable that users wi
Merged:
fail2ban
https://code.launchpad.net/~jose/charms/trusty/fail2ban/tag-security/+merge/245923
mysql
https://code.launchpad.net/~niedbalski/charms/precise/mysql/precise-syncup/+merge/244436
Not merged: (sent back for further work or clarification from submitter)
python-django
https://code.l
Hello,
tl;dr: We've built very *very* simple tests to spur charm authors in to
getting their charms updated and validated for trusty.
Hot on the heels of the previous email, a few of us have been working on
getting every charm from precise in to trusty. This has been no easy task
by any means and
Thanks guys for answering me.
It would be great that the generic vhost-config-relation allows lets the
related charm to require certain parameters.
Do you think that it would be a good improvement for the apache2 charm?
Regards,
On Tue, Jan 13, 2015 at 3:45 PM, Charles Butler <
charles.but...@ca
Testing is no new topic to the list and the ecosystem at large. We've
discussed and hashed out required testing for a while, over several UDS,
vUDS, and emails. Each time we discuss this testing garners a swelling
response, a large portion of +1s from charmers and community alike, and the
definitio
11 matches
Mail list logo
