*** This bug is a duplicate of bug 278630 ***
https://bugs.launchpad.net/bugs/278630
** Changed in: bzr-dbus
Product: Bazaar => bzr-dbus
** This bug has been marked a duplicate of bug 278630
[intrepid] bzr + dbus - X11 = pain
--
X11 initialization failed
https://bugs.launchpad.net/
I'm pretty sure this code is wrong:
cwd = os.getcwd()
if not (cwd == os.path.dirname(os.__file__))):
sys.path.remove(cwd)
I think you want:
cwd = os.getcwd()
if not (cwd == os.path.dirname(__file__))):
sys.path.remove(cwd)
I'm don't understand why you would want the path to the 'os' mo
I would actually prefer "bzr recommends bzrtools suggests graphviz"
since I think bzrtools does provide quite a bit of useful functionality,
and only one (rarely used) command uses graphviz.
--
Installing bzr should not pull X libraries by default
https://bugs.launchpad.net/bugs/321852
You recei
Sort of. It *does* have the logic to reinvoke itself if python ==
python2.3 and python2.4/5/6 can be found on the path.
--
bzr builds against python2.4
https://bugs.launchpad.net/bugs/120659
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Basically, bzr-gtk just needs to issue a new release which changes their
"require(1.13)" to update it to "require(1.15)".
** Summary changed:
- version is (1, 15, 0), and the maximum is (1, 15, 0)
+ bzr-gtk not updated to support the lastest bzr release
--
bzr-gtk not updated to support the la
Basically, bzr-gtk just needs to issue a new release which changes their
"require(1.13)" to update it to "require(1.15)".
--
bzr-gtk not updated to support the lastest bzr release
https://bugs.launchpad.net/bugs/381736
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Did you try something like 'bzr status' to see if it notices the file is
removed. Or maybe explicitly informing it via "bzr rm foo" ?
--
export doesn't handle files going missing from working tree
https://bugs.launchpad.net/bugs/174539
You received this bug notification because you are a member o
There is also bzrlib/smtp_connection.py, which I thought we wanted bzr-
email to use if it was available. (I could have sworn there was a patch
for this, did it just get forgotten?)
So I would say it is a bug in both.
--
Feature Request: Allow more than one attempt to enter SMTP password
https:/
I'll switch this to being a bzr(Ubuntu) bug.
** Also affects: bzr (Ubuntu)
Importance: Undecided
Status: New
** This bug is no longer a duplicate of bug 217701
attempt to add line-delta in non-delta knit
--
ERROR: bzrlib.errors.KnitCorrupt: Knit corrupt: attempt to add line-delta
This is bug #217701 which was fixed in bzr 1.4, but Hardy does not have
the latest package.
** Changed in: bzr
Status: New => Fix Released
Target: None => 1.4
--
ERROR: bzrlib.errors.KnitCorrupt: Knit corrupt: attempt to add line-delta in non-delta knit
https://bugs.launchpad.net
We just need to get 1.4 or 1.5 into backports, etc. It might also be
possible to get a 1.3.2 or something. But it isn't strictly a security
issue, so getting it into the regular update stream is difficult.
** Changed in: bzr (Ubuntu)
Status: New => Confirmed
--
ERROR: bzrlib.errors.KnitCo
This is a bug in the bzr-loom plugin, which already has been updated. I
believe it just needs to be packaged.
** Changed in: bzr-loom (Ubuntu)
Sourcepackagename: bzr => bzr-loom
** Changed in: bzr-loom (Ubuntu)
Status: New => Fix Committed
--
"bzr st" stacktraces
https://bugs.launchpad.n
My initial feeling is that it is just a limitation of weave merging. I
think if I boil down the details, it comes down to:
BASE TEXT
a
b
c
d
e
THIS TEXT
a
b /* with comment */
c
d
e
OTHER TEXT
a
c
d
b
X
e
Put in words, THIS changes a single line, while OTHER deletes the line,
and creates a si
IIRC, this happens because we stopped mangling URLs.
So in the old case we saved the bound location as "lp:%7Egm-dev-
launchpad/..." and now you are updating from "lp:~gm-dev-launchpad/..."
The simple workaround is to:
bzr unbind
bzr bind lp:~gm-dev-launchpad/...
And then it should save exact
This was fixed a while ago, though I find the original bug just yet.
** Changed in: bzr (Ubuntu)
Status: New => Fix Released
--
bzr log -p UnicodeDecodeError
https://bugs.launchpad.net/bugs/400669
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
> 09:54 for...@w038$ python /tmp/foo/test.py
> ['/tmp/foo',
> '/home/forest/usr/lib/python2.5/site-packages/setuptools-0.6c9-py2.5.egg',
> '/home/forest/usr/lib/python2.5/site-packages/Satchmo-0.9_pre-py2.5.egg',
> '/home/forest/lib/python', '
If you had it as a real branch, you could 'Add Branch' to this bug, and
Launchpad should track it.
I think you can do the same thing by just running:
bzr register-branch --project bzrk --link-bug 53479
http://my/bzrk/branch
Otherwise if the tarball is small (perhaps make it tar.bz2), probably
up
** Changed in: bzr (upstream)
Status: Fix Committed => Fix Released
** Changed in: bzr (upstream)
Target: None => 0.8
--
missing self, in def note (bzrlib/progress.py)
https://launchpad.net/bugs/38504
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
** Changed in: bzr (upstream)
Status: Fix Committed => Fix Released
Target: None => 0.8.1
--
weave merge removes text before first conflict
https://launchpad.net/bugs/35886
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
It doesn't seem like we are backporting this, but the fix exists on the
0.9 branch.
** Changed in: bzr (upstream)
Importance: Untriaged => Medium
Status: Confirmed => Fix Released
Target: None => 0.9
--
bzr workingtree interprets inventory xml as ascii incorrectly.
https://launc
*** This bug is a duplicate of bug 87934 ***
https://bugs.launchpad.net/bugs/87934
I'm marking this as a duplicate of bug #87934. The "bzr branch" should
be resumable is a different bug.
** This bug has been marked a duplicate of bug 87934
sftp rename dir1 dir2 will rename dir1 => dir2/dir
This seems to occur when you have a heavyweight checkout inside a local
shared repository.
Aaron- did your recent 'bzr info' changes help this at all?
** Changed in: bzr (upstream)
Importance: Undecided => Medium
Status: Unconfirmed => Confirmed
--
"bzr info" gives no hint that a bran
I believe the problem is that Cygwin only supports ASCII encoding. It
doesn't understand non-ascii filenames.
So if you have non-ascii filenames, you need to use the native win32
bzr, not cygwin.
I think it would be useful if we had a better way of handling errors
like this, so I'm not closing th
I don't think it is strictly invalid for bzr-svn, as we need to come up
with a way for the two to co-exist. bzr core probably needs to provide a
way for bzr-svn to know what is going on, and then bzr-svn needs to use
it.
Specifically, "BzrDir/Branch/WorkingTree.open_containing" should
probably be
Well, the fact that "bzr init" is failing is a bit odd. I guess it is
searching for a containing repository, and bzr-svn tries to connect to
the upstream svn repo and then dies with an exception rather than just
returning that this cannot be a shared repository.
Or is "bzr init" underneath a .svn
I believe this has been fixed for a while, but in 'bzr.dev' I get:
% bzr info
Repository checkout (format: pack-0.92)
Location:
repository checkout root: .
checkout of branch: http://bazaar-vcs.org/bzr/bzr.dev/
shared repository: /home/jameinel/dev/bzr
...
So it says I am a hea
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
Network Manager cannot connect to a WEP 128 network
https://bugs.launchpad.net/bugs/114605
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
This looks like you have 2 python's installed, and bzrlib installed in
one, but /usr/bin/python points to the other.
I see this:
ExecutablePath: /usr/bin/bzr
InterpreterPath: /usr/bin/python2.5
ProcCmdline: /usr/bin/python /usr/bin/bzr
Can you tell me what '/usr/bin/python' is? (I'm guessing it i
It also happened to me when I upgraded from Gutsy => Hardy. It seems
that /etc/hosts only includes my fully qualified name, while
/etc/hostname only has the short name.
I cannot "sudo" to edit /etc/hosts or /etc/hostname
--
unresolvable hostname breaks system
https://bugs.launchpad.net/bugs/1974
I wonder if a lot of this has now been addressed with pack and Branch6
formats
Care to do a timing test? I'm guessing this is actually significantly
better and this bug can be closed.
** Changed in: bzr
Status: Confirmed => Incomplete
--
empty push performance slower than needed
https://
test_weave.py doesn't need a shebang at all
I think the reason the rest of them use python2.4 is because of
python2.3 sitting around.
If we feel like 2.4+2.5 is significantly more common that 2.3+2.4, then
we can turn them back into '/usr/bin/env python' instead.
As I understand it, though, Red
Sure, but these are extra tools that not everyone who uses bzr needs. It
seems a little perverse to make all of them include the re-invoke code.
Also, bzr will reinvoke to python2.5 is 2.4 isn't available, and won't
re-invoke if it is running python2.5
I think this specific bug is that Fiesty is
Thinking about it, though. If we are using '/usr/bin/env python' anywhere, then
it should be fine to do it everywhere. Probably the differences is just because
different people have coded different tools.
So I think we would be happy to have these standardized.
** Changed in: bzr (upstream)
I
All my testing shows the progress bar does indeed move now, and has for
several versions. This bug was filed against bzr-0.7, so it has had a
long time to be fixed.
** Changed in: bzr (upstream)
Status: Unconfirmed => Fix Released
--
bzr merge from SFTP shows no progress while reading
htt
see also bug 75721
--
empty push performance slower than needed
https://bugs.launchpad.net/bugs/86392
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
I'll play around with this in the associated branch
** Changed in: bzr (upstream)
Importance: Undecided => Wishlist
Status: Unconfirmed => Confirmed
** Changed in: bzr (upstream)
Assignee: (unassigned) => John A Meinel
--
bzr log --short should indicat
I think the reason for not doing this was because you have to create the
commit on the remote machine (which means it would access remote knits
for the old data, etc). Rather than creating it locally, and copying it
across.
I understand the need for this as we get more mixed-format bindings. But
h
r-0.17-dev
So you can see that all but the last one was a merge commit.
** Changed in: bzr (upstream)
Status: Confirmed => Fix Committed
** Changed in: bzr (Ubuntu)
Assignee: (unassigned) => John A Meinel
Status: Unconfirmed => Fix Committed
--
bzr log --short sho
I would guess this is related to: bug 87934
The "lock broken while..." is bug 87934. The fact that "bzr checkout path/foo"
creates a local foo which isn't anything yet is a different bug (is it
reported?). It should either delete the target or make it into something that
could be updated.
http
Why are those files ending in .html?
If you use "make docs" in a bzr source tree it generates all of them
with .htm extensions.
Arguably whoever is generating file:///usr/share/doc/bzr/html/index.html
should be generating file:///usr/share/doc/bzr/html/index.htm
and the bug is in the packaging,
I think it could show that there was a merge, but I don't think I would
want it to show the merged commits. Is that what you are thinking?
--
bzr log --short should indicate merges
https://launchpad.net/bugs/83887
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
Public bug reported:
Binary package hint: rhythmbox
I'm streaming ogg over a samba share from another machine.
The share is mounted to /media/music
While playing an ogg stream, the player plays for approximately 1
minute, and then hangs. My connection is still working (it is over the
local netwo
** Attachment added: "Crash report"
http://librarian.launchpad.net/5578653/_usr_bin_rhythmbox.1000.crash
--
Rhythmbox crashes while playing ogg stream
https://launchpad.net/bugs/77718
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
sorry about the noise, but this is the only way I found to target the
bug at launchpad-code.
I believe it is an lp-code issue because that is where the policy of
what branches can be placed where resides. I don't think bzr itself
cares.
** Also affects: bzr
Importance: Undecided
Status:
I'm comfortable just marking this as a fixed problem. It is possibly bug
#375013, though my guess is it might actually be the 'transfer texts
introduced by ghosts' or something along those lines.
If we continue to encounter it, we can re-open.
** Changed in: bzr
Status: Confirmed => Fix Re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gordon Tyler wrote:
> ** Also affects: bzr
>Importance: Undecided
>Status: New
>
I think we would be okay with a flag that allows patches to be 'dirty',
but I think we also would like a way to force them to be pristine.
I don't remember
** Changed in: bzr
Status: Confirmed => Fix Released
--
bzr should fix timestamps on export
https://bugs.launchpad.net/bugs/515631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
Public bug reported:
Binary package hint: python-debian
The debian_bundle.changelog.Version class implements __eq__ but not
__hash__
As such, you can almost-but-not-quite use them as dict entries. Consider
v1 = Version('1.1.1-2')
v2 = Version('1.1.1-2')
assert v1 == v2
d = {v1: 'content'}
ass
Public bug reported:
Binary package hint: python-debian
The interface for Changelog.__init__ and Changelog.parse_changelog look
like you could pass in a 'file' object or any iterable of lines. (like a
list of lines).
However if you look closer, in the
if isinstance(file, basestring):
section it
Public bug reported:
Binary package hint: python-debian
I was trying to create a test case with a badly formatted changelog,
only to find out that it didn't actually care when there was only a
single entry.
Specifically I tried to do:
invalid_changelog = """\
psuedo-prog (1.1.1-2) unstable; urg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Westby wrote:
> Hi,
>
> This appears to be a bzr issue, as just trying to branch the
> lp:debian/sid/cwidget
> branch I get
>
> bzr: ERROR: bzrlib.errors.ErrorFromSmartServer: Error received from
> smart server: ('error', "Absent factory for
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
unchiujar wrote:
> An alternative method of hacking around this problem is to install
> virtualenv http://pypi.python.org/pypi/virtualenv
>
> Create virtual environment:
> virtualenv -p python2.4 /usr/share/virtual_python2.4
>
> Edit the bazaar execu
*** This bug is a duplicate of bug 437626 ***
https://bugs.launchpad.net/bugs/437626
This was fixed in bzr 2.0.2
** This bug has been marked a duplicate of bug 437626
exceptions.AssertionError: second push failed to complete a fetch set
** This bug is no longer a duplicate of bug 437626
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary van der Merwe wrote:
> Public bug reported:
>
> With bzr 2.1.1 installed from the ubuntu lucid repository:
>
> $ bzr rocks --profile-imports
> Traceback (most recent call last):
> File "/usr/bin/bzr", line 59, in
> import profile_imports
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary van der Merwe wrote:
> On 01/06/10 17:52, John A Meinel wrote:
>> We intentionally don't support it for installed bzr
>
> Why? I would like to profile imports on my installed copy.
>
We have the module as a top-leve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johan Walles wrote:
> Here's the output I get from running bzr branch -Derror
> http://bzr.savannah.gnu.org/r/gnash.
>
> ** Attachment added: "bzr branch -Derror http://bzr.savannah.gnu.org/r/gnash";
>http://launchpadlibrarian.net/49257319/Derror.
Including the traceback:
PythonVersion: 2.6.4
Traceback:
Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 842, in
exception_to_return_code
return the_callable(*args, **kwargs)
File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py",
Public bug reported:
Binary package hint: python-debian
At the moment, I have to use "Changelog._blocks" to get access to
individual blocks. The public api functions only look at the most recent
tip.
Either _blocks should be made public, or a function should be added to
iterate over the sections
Public bug reported:
Binary package hint: python-debian
If you construct a Changelog and pass it the content to parse, it always
supresses the ChangelogParseError, even when you have strict=True set.
I'm guessing this is the actual cause of bug #516798 (the except was
getting raised, but it was
*** This bug is a duplicate of bug 517104 ***
https://bugs.launchpad.net/bugs/517104
** This bug has been marked a duplicate of bug 517104
Passing changelog content in Changelog constructor suppresses
ChangelogParseError
--
Changelog parser doesn't raise a failure if the last entry is ma
I'm certain this isn't a bug in bzr, I'm not really sure which package
it should be against, or I would just redirect it.
Sounds like perhaps a gnome issue?
** Changed in: bzr (Ubuntu)
Status: New => Invalid
--
No task bar or virtual windows
https://bugs.launchpad.net/bugs/536807
You rec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Westby wrote:
> bzr-email | 0.0.1~bzr40-1 | karmic/universe | source, all
>
> % bzr revno lp:bzr-email
> 40
>
> so it seems to me the latest is packaged in karmic.
>
> Thanks,
>
> James
>
>
> ** Changed in: bzr-email (Ubuntu)
>Stat
*** This bug is a duplicate of bug 494269 ***
https://bugs.launchpad.net/bugs/494269
** This bug has been marked a duplicate of bug 494269
tree transform cannot change root id
--
bzr merge-package: ERROR: exceptions.ValueError: Cannot have multiple roots.
https://bugs.launchpad.net/bugs/5
** Also affects: bzr/2.0
Importance: Undecided
Status: New
** Changed in: bzr/2.0
Status: New => Fix Released
** Changed in: bzr/2.0
Milestone: None => 2.0.2
** Changed in: bzr/2.0
Assignee: (unassigned) => Andrew Bennetts (spiv)
--
exceptions.AssertionError: second p
That particular error is coming from here:
https://github.com/juju/juju/blob/19d6a75eea61f5021a9fa0ee8e37fe7f6e3c9d53/charmhub/download.go#L201
Given what it is downloading from, I believe it is coming from:
https://github.com/juju/juju/blob/19d6a75eea61f5021a9fa0ee8e37fe7f6e3c9d53/charmhub/downlo
>From everything I can tell this was a temporary outage (as you can again
deploy from postgresql-k8s). However, it is something we should be aware
of in case it comes back and we have the opportunity to reproduce.
** Changed in: juju
Status: New => Incomplete
--
You received this bug noti
nassigned) => John A Meinel (jameinel)
** Changed in: juju
Assignee: John A Meinel (jameinel) => Witold Krecicki (wpk)
** Changed in: juju
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Note that any time you actively need to use custom userdata is probably a
time where Juju is failing to model something important. So while it is an
outlet to getting something that works, it should still be a bug that we
don't support the underlying use case correctly.
John
=:->
On Sun, Dec 10,
I'll note that I tried just launching a bionic container using snap
3.0.0.beta5 and after "lxc launch ubuntu:x" and "lxc launch ubuntu-daily:b"
neither of them came up with an IP address.
I might have broken my networking on this machine because I was trying to
install stock Juju which tries to br
restarting my machine and disconnecting from the VPN made them work, so I
don't think it was snap Lxd or bionic at fault.
I'm not 100% sure if bionic and netplan play nicely with fan
configuration.
can you confirm if both the host machine and the containers are bionic or
is it just the containers
** Also affects: juju/2.3
Importance: Undecided
Status: New
** Changed in: juju/2.3
Status: New => Triaged
** Changed in: juju/2.3
Importance: Undecided => High
** Changed in: juju/2.3
Milestone: None => 2.3.6
** Changed in: juju
Status: New => Triaged
** Changed
Likely we should remove juju-mongodb3.2 from bionic once we actually have an
alternative and can trust that it actually works. It is my understanding that
3.2 FTBFS and nobody was willing to maintain it.
Given the option, yes we would prefer a 3.4 without the JS engine. My
understanding is that
We should also check into https://bugs.launchpad.net/juju/+bug/1751739
and see if there is a consistent issue here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756040
Title:
bionic: LXD container
We've also been seeing keyserver request failures during our CI/Build
process
** Also affects: juju
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/1777512
T
I don't believe Juju expects public addresses for all machines. It
*does* expect a public address for the controller, because you need
external access to be able to connect for things like "juju status" from
your machine.
I don't know how you would have been able to bootstrap and 'ssh' into
the ma
** Changed in: juju
Status: New => Triaged
** Changed in: juju
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777512
Title:
key retrieval timeouts cause failu
Given the Assignee: auto-github-vim-vim #851
I think what happened is that someone noticed this is also the bug in github.
However, if you read the bug in github, they closed *that* bug because they
said it was an Ubuntu bug. So I think there is no Fix Released, as upstream
said it was an Ubunt
I'm removing the direct remote watch as they said it is an Ubuntu bug.
** Changed in: vim
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/1611363
Title:
vim.gtk3 crash
*** This bug is a duplicate of bug 1628289 ***
https://bugs.launchpad.net/bugs/1628289
** This bug has been marked a duplicate of bug 1628289
snapd should depend on squashfuse (for use in containers)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
see also bug #1657850 that we probably shouldn't just be using the 'next
available 10.0.x' address. (This was the original algorithm used by LXD
when we added support, but they have changed their algorithm since
then.)
** Package changed: juju (Ubuntu) => juju
** Changed in: juju
Status: N
>From things like:
https://lists.ubuntu.com/archives/snapcraft/2016-September/001068.html
It is intended that snaps do not default to seeing /snap/bin in their path,
and instead need to use things like content interfaces to get access to
other binaries.
However, charms that are managing snapped
I'm not sure that 'snapd' is the right target for this, but not having
'/snap/bin' on your PATH inside systemd launched scripts seems to be a
snapd packaging issue.
** Changed in: juju
Importance: Undecided => Wishlist
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
*** This bug is a duplicate of bug 1660273 ***
https://bugs.launchpad.net/bugs/1660273
Agreed
** This bug has been marked a duplicate of bug 1660273
/etc/environment does not include /snap/bin in $PATH
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
*** This bug is a duplicate of bug 1660273 ***
https://bugs.launchpad.net/bugs/1660273
>From things like:
https://lists.ubuntu.com/archives/snapcraft/2016-September/001068.html
It is intended that snaps do not default to seeing /snap/bin in their path,
and instead need to use things like con
I just ran into this doing a dist upgrade from 14.04 to 16.04.3. Now,
the initial do-release-upgrade failed mid way, because of something
wrong with Postgres. (I can't remember the exact details now, but it
started popping up a dialog about postgres, which had a 'close' button,
but clicking close c
It would be good to have a clearer discussion of what issues you are
running into with routes. There are several ways that we *could* tackle the
issue. Static Routes was the mechanism that we started modeling because
that was the ask from the field (because, as-I-understand, that was the
solution t
juju-core the package is the client tools (juju), so it should *not*
depend on having mongodb locally installed.
To use the local provider, you can install "juju-local" on saucy (and from
ppa:juju/stable).
That will bring in both lxc and mongodb.
** Changed in: juju-core (Ubuntu)
Status
I don't think this is strictly a bug in 'juju-core', more of a bug in
the packaging. (Namely saucy has a package named "juju" which is a meta
package that installs juju-core, while IIRC python-juju is no longer
available on Saucy.)
If this was just 'apt-get upgrade' I would probably agree it shoul
** Summary changed:
- juju scp no longer allows multiple extra arguments to pass throug
+ juju scp no longer allows multiple extra arguments to pass through
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: juju-core
Milestone: 1.19.1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305280
Title:
juju command get_cgroup fails when creating new machines, local
provider arm32
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => High
** Changed in: juju-core
Milestone: None => 1.19.2
** Changed in: juju-core
Importance: High => Critical
--
You received this bug notification because you are a member of Ubu
** Changed in: juju-core/1.18
Importance: High => Critical
** 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/1304407
Title:
juju bootstrap de
** Changed in: juju-core/1.18
Status: Triaged => In Progress
** Changed in: juju-core/1.18
Assignee: (unassigned) => Nate Finch (natefinch)
** Changed in: juju-core
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Also affects: juju-mongodb (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: Triaged => Invalid
** Changed in: juju-core
Milestone: 1.19.1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Actually, because juju-local only supports one architecture (your local
machine), it does *not* download the jujud tools from a remote site, but
uses the one on your local machine. (It should be put into the juju-
local package, rather than being in the 'juju-core' package, but that is
just shuffli
...
> On Mon, Mar 31, 2014 at 01:30:45PM -, Mark Ramm wrote:
> > I think a key point here is that the juju package does not generally
> > install or pull down binaries from anywhere to your machine. It does
> > instruct the cloud installation of a server to use a specific ubuntu
> > image f
Michael and I played around with some different settings, and here are
my notes.
1) Package kde-runtime seems to install
/etc/sysctl.d/30-baloo-inotify-limits.conf which sets max_user_watches to
512*1024
'slabtop' says that my baseline kernel memory is 380-420MB with no containers
running.
5) Another data point, with
$ sysctl fs.inotify
fs.inotify.max_queued_events = 131072
fs.inotify.max_user_instances = 1024
fs.inotify.max_user_watches = 524288
(so max_queued_events 8x greater, and max_user_instances well above
previously established useful level), I still only get 19 containers.
With Juju in the loop, I run into whatever limit a bit faster. I was
successful at doing:
juju bootstrap test-lxd lxd
juju deploy ubuntu
juju add-unit -n 5 ubuntu # wait for status to say everything is running
juju add-unit -n 5 ubuntu # wait for status to be happy
but then after doing one mo
Note that there should be support for /etc/system/limits.d/10-juju.conf
I'm testing it now, but it may be that we can drop something in there as
well. I'll test it a bit, but if we have some tasteful defaults, maybe
we can make it work.
I think we can change from their default so instead of "* no
1 - 100 of 227 matches
Mail list logo
