*** This bug is a duplicate of bug 1469744 ***
https://bugs.launchpad.net/bugs/1469744
This bug was fixed in the package juju-core - 1.22.6-0ubuntu1~14.04.1
---
juju-core (1.22.6-0ubuntu1~14.04.1) trusty; urgency=medium
* No change backport to 14.04 (LP: #1469744). This
*** This bug is a duplicate of bug 1469744 ***
https://bugs.launchpad.net/bugs/1469744
This bug was fixed in the package juju-core - 1.22.6-0ubuntu1~14.04.1
---
juju-core (1.22.6-0ubuntu1~14.04.1) trusty; urgency=medium
* No change backport to 14.04 (LP: #1469744). This
*** This bug is a duplicate of bug 1469744 ***
https://bugs.launchpad.net/bugs/1469744
It looks like this bug is superseded by LP: #1469744
** This bug has been marked a duplicate of bug 1469744
[needs-packaging] 1.22.6 is not packaged in trusty
--
You received this bug notification
*** This bug is a duplicate of bug 1469744 ***
https://bugs.launchpad.net/bugs/1469744
It looks like this bug is superseded by LP: #1469744
** This bug has been marked a duplicate of bug 1469744
[needs-packaging] 1.22.6 is not packaged in trusty
--
You received this bug notification
** Branch linked: lp:ubuntu/trusty-proposed/juju-core
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
juju-core 1.22.1 is not packaged in Ubuntu
To manage
** Branch linked: lp:ubuntu/trusty-proposed/juju-core
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
juju-core 1.22.1 is not packaged in Ubuntu
To manage notifications about this bug
Adding verification-failed based on #14
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
juju-core 1.22.1 is not
Adding verification-failed based on #14
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
I do not want 1.22.1 going into updates because there is a compatibility
issue. Bug 1454829 is about a case were a 1.20.11 client cannot talk to
an env bootstrapped with. 1.22.x. The certificate rules are different,
preventing the client from talking. This is not an issue for envs
upgraded from
I do not want 1.22.1 going into updates because there is a compatibility
issue. Bug 1454829 is about a case were a 1.20.11 client cannot talk to
an env bootstrapped with. 1.22.x. The certificate rules are different,
preventing the client from talking. This is not an issue for envs
upgraded from
Hi Curtis,
To my understanding juju-1.22.1 is not in -updates yet not because we
don't want this but because it needs to be in -proposed for 7 days
before reaching -updates. This is a standard practice for SRUs. I expect
to see it landed into -updates until the end of this week. If juju team
Hi Curtis,
To my understanding juju-1.22.1 is not in -updates yet not because we
don't want this but because it needs to be in -proposed for 7 days
before reaching -updates. This is a standard practice for SRUs. I expect
to see it landed into -updates until the end of this week. If juju team
Hi Oleg.
I am happy to continue with 1.22.1 going into updates first. I am a
little concerned about perception of churn in Trusty. Juju 1.22.4 will
arrive a few weeks later. What of 1.23.x? 1.23.3 is currently proposed,
but Core's desire to put 1.22.4 in means we delay the .1.23 going into
Hi Oleg.
I am happy to continue with 1.22.1 going into updates first. I am a
little concerned about perception of churn in Trusty. Juju 1.22.4 will
arrive a few weeks later. What of 1.23.x? 1.23.3 is currently proposed,
but Core's desire to put 1.22.4 in means we delay the .1.23 going into
@Oleg, et al.
I understand that there is a plan to release a 1.22.4 soon. The intent is to
support this version as well as the current 1.23. There are orgs committed to
using 1.22 for some time and that there are stability fixes that are being
backported.
If we think that Ubuntu users don't
@Oleg, et al.
I understand that there is a plan to release a 1.22.4 soon. The intent is to
support this version as well as the current 1.23. There are orgs committed to
using 1.22 for some time and that there are stability fixes that are being
backported.
If we think that Ubuntu users don't
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
I have certified juju 1.20.1 in trusty proposed is compatible with juju agent
streams and with the ecosystem of tools in trusty. I verified:
* The binary archs in proposed work with the archs in agent streams.
* Juju is suitable for local testing and charm development
* juju-deployer can deployed
I have certified juju 1.20.1 in trusty proposed is compatible with juju agent
streams and with the ecosystem of tools in trusty. I verified:
* The binary archs in proposed work with the archs in agent streams.
* Juju is suitable for local testing and charm development
* juju-deployer can deployed
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
Thanks Curtis! Adding 'verification-done' tag based on your comments.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
There was a typo in the message #8 from Curtis. Juju 1.22.1 has been certified
not 1.20.1.
sinzui strikov, oops, yes, I do mean *1.22.1*
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Thanks Curtis! Adding 'verification-done' tag based on your comments.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444037
There was a typo in the message #8 from Curtis. Juju 1.22.1 has been certified
not 1.20.1.
sinzui strikov, oops, yes, I do mean *1.22.1*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
Hello Oleg, or anyone else affected,
Accepted juju-core into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/1.22.1-0ubuntu0.14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Oleg, or anyone else affected,
Accepted juju-core into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/1.22.1-0ubuntu0.14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
In the Trusty SRU queue so In Progress.
** Changed in: juju-core (Ubuntu Trusty)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
In the Trusty SRU queue so In Progress.
** Changed in: juju-core (Ubuntu Trusty)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
juju-core 1.22.1 is
Here is the changelog for the package I'm asking SRU for:
juju-core (1.22.1-0ubuntu0.14.04.1) trusty; urgency=medium
* New upstream release (LP: #1444037).
* Packaging changes required by the new release and cherry-picked from Vivid:
- d/tests/fake-future.sh: New ability to generate fake
Here is the changelog for the package I'm asking SRU for:
juju-core (1.22.1-0ubuntu0.14.04.1) trusty; urgency=medium
* New upstream release (LP: #1444037).
* Packaging changes required by the new release and cherry-picked from Vivid:
- d/tests/fake-future.sh: New ability to generate fake
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
Ubuntu juju 1.22.1 on vivid is compatible with 1.22.x from upstream
Juju. It is suitable deploying and maintaining environments in public
and private clouds. Juju is compatible with the versions of quickstart
(and deployer) provide by Ubuntu main and proposed.
Note that 1.22.1 does not support
Ubuntu juju 1.22.1 on vivid is compatible with 1.22.x from upstream
Juju. It is suitable deploying and maintaining environments in public
and private clouds. Juju is compatible with the versions of quickstart
(and deployer) provide by Ubuntu main and proposed.
Note that 1.22.1 does not support
This bug was fixed in the package juju-core - 1.22.1-0ubuntu1
---
juju-core (1.22.1-0ubuntu1) vivid; urgency=medium
* New upstream bugfix release (LP: #1444037).
* Autopkgtests were changed to switch back to upstart before running their
workload. This is needed because juju
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
Removing 'block-proposed' flag to allow juju 1.22.1 to go into Vivid.
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools
Removing 'block-proposed' flag to allow juju 1.22.1 to go into Vivid.
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools
This bug was fixed in the package juju-core - 1.22.1-0ubuntu1
---
juju-core (1.22.1-0ubuntu1) vivid; urgency=medium
* New upstream bugfix release (LP: #1444037).
* Autopkgtests were changed to switch back to upstart before running their
workload. This is needed because juju
** Project changed: juju-core = juju-core (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
juju-core 1.22.1 is not packaged in Ubuntu
To manage notifications about this bug go
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
juju-core 1.22.1 is not packaged in Ubuntu
To
** Project changed: juju-core = juju-core (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
juju-core 1.22.1 is not packaged in Ubuntu
To manage
** Changed in: juju-core (Ubuntu)
Assignee: Curtis Hovey (sinzui) = (unassigned)
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) = Oleg Strikov (strikov)
** Changed in: juju-core (Ubuntu Trusty)
Assignee: (unassigned) = Oleg Strikov (strikov)
--
You received this bug
** Changed in: juju-core (Ubuntu)
Assignee: Curtis Hovey (sinzui) = (unassigned)
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) = Oleg Strikov (strikov)
** Changed in: juju-core (Ubuntu Trusty)
Assignee: (unassigned) = Oleg Strikov (strikov)
--
You received this bug
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
juju-core 1.22.1 is not
** Branch linked: lp:ubuntu/vivid-proposed/juju-core
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
juju-core 1.22.1 is not packaged in Ubuntu
To manage notifications about this bug
** Branch linked: lp:ubuntu/vivid-proposed/juju-core
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
juju-core 1.22.1 is not packaged in Ubuntu
To manage
48 matches
Mail list logo
