** Changed in: juju-core
Importance: Medium => High
** Changed in: juju-core
Milestone: None => 1.21-alpha1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
logs are not logrotat
Reducing the security implications of running MongoDB is an important
thing for us to do. It's not quite critical, because nobody is asking
for it directly now, and the risk is still somewhat limited. But there
is a risk, and I think the general policy of treating even security --
even relativel
** Changed in: juju-core
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208430
Title:
mongodb runs as root user
To manage notifications about this bug go to:
https:/
We decided that we should land everything but HA and VLAN work this week in
a stable release to minimize the risk that either of those changes could
have on overall stability in the release. However, HA and VLAN work is
underway, and much of it has already landed, and the first HA support is
expec
** Changed in: juju-core
Milestone: None => 1.18.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208430
Title:
mongodb runs as root user
To manage notifications about this bug go to:
https://b
@all
Given the timeline and the various other bits on our roadmap, I think
main inclusion for juju core is *not* critical this cycle. We would
rather get agreement, and get this done the right way than create last
minute chaos for the release. But, it is critical that we sort this
and the MRE
@martin
"Traditionally the Tech board has nacked everything in main which pulls
code from third-party sources, i. e. "installer packages". Packages in
main must not enable any third-party PPA, pull code or binaries from an
upstream site and run it, and so on."
I think a key point here is that the
@jamie
"However, I don't feel the download size is itself a blocker. We can
perform uploads for everything at first, figure out how to be
smarter/more selective later and along the way work with upstream on
dynamic linking if that makes sense."
I think that is particularly true in *this* case whe
@gustavo
I think it is right that there are many people in the go community who
would welcome dynamic linking in golang-go, but I also think that if we
want to have it, we need to do the work to add it there. Now that we
have to have Arm64 and Power, if we are going to be investing in
improving
@adam
> I think you'd agree that the obvious and simple usecase isn't "I
> installed juju-core on my Ubuntu desktop so I can rollout charms on OSX
> and Solaris".
Don't forget it will not support: old Ubuntu versions, Arm64, or power,
other versions of Linux, Windows, or anything but the series t
@adam
We *can* build and include tools binaries in the package. And in fact
for many tools, we extract them from the builds, and upload them to a
central distribution point (which uses the same toolchain as the ubuntu
cloud images catalog -- simplestreams.
But, we don't distribute the tools bin
This bug is also impacting the juju-mongodb package, and therefore juju
on ppc64el.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294747
Title:
mongodb fails assertion on ppc64el with 64k pagesize
Since we are using 4.9, can we just delete this from Juju Core, and kill
it?
** Changed in: juju-core
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273712
Title:
juju
Dave, can you turn you hack of your working copy into a branch proposal?
** Changed in: juju-core
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273769
Title:
ppc64e
** Changed in: juju-core
Milestone: 2.0 => 1.17.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1229275
Title:
[maas] juju destroy-environment also destroys nodes that are not
controlled by ju
** Description changed:
juju-core 1.16.0 stable release is due by the 3rd October and includes
the following features over the version already in the archive:
* MAAS Tag support
* Get juju tools and cloud configuration data from a central well know
location
* support for --ssl-hostna
** Changed in: juju
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1229275
Title:
juju destroy-environment also destroys nodes that are not controlled
by juju
To ma
** Description changed:
- For Ubuntu 13.10, we will want to drop in another stable milestone of
- juju-core prior to release.
+ Currently Ubuntu saucy is tracking the inAPI only non-bootstrap
+ agentsterim releases of juju-core (1.13.x series).
- juju-core 1.16 is currently targetting the 3rd O
We are fully committed to not regressing and creating a sane upgrade
path. We have people on this, to make sure that happens. And again
this is a stand-alone package with no dependencies -- so I don't think
the risks are that significant.
But I understand that this is not my decision. I'm jus
Known broken sounds incorrect for the situation here. What we have is
known incomplete, which is significantly different both practically and
philosophically.
100% feature complete is a software myth. So that's not a real
argument.
But go juju has an upgrade path, and has a team ready to suppo
I don't believe this decision makes sense for users.
The Go port of juju is supported, maintained, and users who opt in to
using it now will be able to avoid a painful migration later.
Since this is fully opt-in, there is no advantage to waiting for
backports to pull it in. It is a stand-alone p
21 matches
Mail list logo
