This bug was fixed in the package juju-core - 1.20.11-0ubuntu0.14.04.1
---
juju-core (1.20.11-0ubuntu0.14.04.1) trusty; urgency=medium
* New upstream release (LP: #1386144).
* Packaging changes relating to new upstream release:
- d/control: add build dependency on lsb-release.
This bug was fixed in the package juju-core - 1.20.11-0ubuntu1
---
juju-core (1.20.11-0ubuntu1) vivid; urgency=medium
* New upstream bugfix release (LP: #1386144).
* Build with a version of libgo5 that has the 64k PAGE_SIZE fix
(LP: #1377325).
-- Robie BasakMon, 27 Oct 20
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
t
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
t
I think my test of juju-quickstart + juju-core failed because my env is
dirty. I get the same errors on trusty with the packages in release and
updates. I will retest with a clean trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
t
juju-quickstart 1.3.1 + juju-core 1.20.11 in trusty cannot connect to
the bootstraped start-server to deploy services.
18:40:09 WARNING app@connect:300 Retrying: unable to connect to the
Juju API server on wss://165.225.151.107:17070: [Errno 1] _ssl.c:510:
error:14090086:SSL routines:SSL3_GET_
Juju QA certifies that the trusty clients are suitable for local
development and production cloud deploys.
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in
i386 now accepted into trusty-proposed. Thanks Steve!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386144
Title:
juju-core 1.20.11 is not packaged in Ubuntu
To manage notifications about this bug
Thanks Curtis!
i386 is blocked on Trusty binNEW. I've asked Steve to review this for
us, but I'm not sure when he'll be able to get to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386144
Title:
Vivid testing is complete. It is suitable for local development and for
deploying to clouds.
Trusty testing is blocked by the missing juju-local package for 14.14.
The vivid local package can be forced to install, but it depends on
juju-core >= 1.20.11-0ubuntu1, but the trusty backport is
1.20.11-
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
t
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
t
Interesting "thorough verification" that completes before the package is
in the archive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386144
Title:
juju-core 1.20.11 is not packaged in Ubuntu
To
Thanks Dean! Note quite verification-done yet though - we have a couple
of other verifications we need to do first (tracked in bug whiteboard).
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
We have thoroughly tested this and it looks good. +1
** 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/1386144
Title:
juju-core 1.2
The juju-local package does not appear to have been built and published.
the i386 juju-core package was built but is not listed as published.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386144
Titl
** 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/1386144
Title:
juju-core 1.20.11 is not packaged in Ubuntu
To manage notifications about this bug
Hello Robie, or anyone else affected,
Accepted juju-core into trusty-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/juju-
core/1.20.11-0ubuntu0.14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/juju-core/vivid-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386144
Title:
juju-core 1.20.11 is not packaged in Ubuntu
To manage notif
Uploaded to vivid-proposed and trusty-proposed. Vivid is ready for
testing now. Trusty is pending SRU team approval.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386144
Title:
juju-core 1.20.11 is
21 matches
Mail list logo
