On Fri, Sep 16, 2016 at 2:00 PM, Marco Ceppi <marco.ce...@canonical.com> wrote:
> I am the upstream (for this charm) and this is an entire rework of the > charm including a repo change. > Ok, thanks for the info. What will become of the old repos?: https://code.launchpad.net/~charmers/charms/trusty/ubuntu/trunk lp:charms/trusty/ubuntu https://code.launchpad.net/~charmers/charms/precise/ubuntu/trunk lp:charms/ubuntu > Future mp will be against this repo https://github.com/marcoceppi/ > charm-ubuntu the readme is up to date: http://juju > charms.com/u/marcoceppi/ubuntu/1 > > I'll have the repo fixed tomorrow. > > > Marco > > On Fri, Sep 16, 2016, 1:36 PM Ryan Beisner <ryan.beis...@canonical.com> > wrote: > >> Was there a merge proposal or pull request for these changes in the >> charm's upstream repo? If not, is there a branch that can be proposed >> against the charm repo? Or, is there a new upstream repo for the charm? >> >> The candidate charm in the store is helpful to validate functionality, >> but as a contributor to the existing charm, I simply cannot determine where >> I might base future changes, or rebase existing works in progress. >> >> -1 to this moving forward, from an upstream charm code contributor >> perspective, pending clarification/completion of the upstream repo and >> review. >> >> Setting aside those issues of principle, I've confirmed that it does work >> with 1.25.6: Precise, Trusty, Xenial units. Having this in place will be a >> nice touch. >> >> Cheers, >> >> Ryan >> >> >> On Wed, Sep 14, 2016 at 4:24 PM, Tim Penhey <tim.pen...@canonical.com> >> wrote: >> >>> Marco, >>> >>> This is awesome. I use the ubuntu charm all the time for testing, and >>> seeing the workload version and workload status being set is pretty cool. >>> >>> I had hoped that seeing the "unknown" status would apply gentle pressure >>> to get people to set a workload status. >>> >>> Winning!!! >>> >>> Tim >>> >>> On 15/09/16 08:39, Marco Ceppi wrote: >>> >>>> Hi Ryan, >>>> >>>> I have granted everyone access to the candidate channel. Could you try >>>> again? >>>> >>>> Thanks, >>>> Marco Ceppi >>>> >>>> On Wed, Sep 14, 2016 at 3:26 PM Ryan Beisner < >>>> ryan.beis...@canonical.com >>>> <mailto:ryan.beis...@canonical.com>> wrote: >>>> >>>> Is there a merge proposal or pull request for the changes? I'd like >>>> to validate with 1.25.6 as the current stable release, but --channel >>>> isn't a thing there. >>>> >>>> I tried to `charm pull ubuntu --channel candidate` but received: >>>> ERROR cannot get archive: unauthorized: access denied. >>>> >>>> Thanks, >>>> >>>> Ryan >>>> >>>> >>>> On Wed, Sep 14, 2016 at 8:57 AM, Marco Ceppi >>>> <marco.ce...@canonical.com <mailto:marco.ce...@canonical.com>> >>>> wrote: >>>> >>>> Hey everyone, >>>> >>>> Normally, I wouldn't bother with an update like this, but it's >>>> slightly larger than I'd care to just push out. Today, the >>>> Ubuntu charm is a no-op, which is largely the goal of the charm. >>>> However, as juju becomes more rich this no-op charm starts to >>>> look incomplete. I know a few people depend on the Ubuntu charm >>>> for setup purposes and testing. I'd hate to be the source of >>>> breakage for that charm so I'm announcing an update here. >>>> >>>> Screenshot from 2016-09-14 09-48-31.png >>>> >>>> Other than the obvious changes to status, this also implements >>>> workload version. >>>> >>>> If you depend on the Ubuntu charm for anything I urge you to >>>> test the latest version with >>>> >>>> `juju deploy ubuntu --channel candidate` >>>> >>>> If I don't receive any negative feedback by the end of this week >>>> I'll move what's in candidate to stable. >>>> >>>> Thanks, >>>> Marco Ceppi >>>> >>>> -- >>>> Juju mailing list >>>> Juju@lists.ubuntu.com <mailto:Juju@lists.ubuntu.com> >>>> Modify settings or unsubscribe at: >>>> https://lists.ubuntu.com/mailman/listinfo/juju >>>> >>>> >>>> >>>> >>
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
