** Changed in: juju-core
Milestone: 2.0-beta5 => 2.0-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570657
Title:
Bash completion needed for versioned juju commands
To manage notifications
** Changed in: juju-core
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290920
Title:
non-default lxc-dir breaks local provider
To manage notifications about
** Tags added: jujuqa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571082
Title:
autopkgtest lxd provider tests fail for 2.0
To manage notifications about this bug go to:
@Nishihama ,
This issue is caused when there is less than two unallocated sectors
between logical partitions. The Extended Boot Record is stored in the
unallocated sector area. In your situation the problem arises with sda5
and sda6 sda5.
332625887 end of sda5
332625888 start of sda6
The
** Changed in: juju-core
Milestone: 2.0-beta4 => 2.0-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
Hi Doko and Michael.
mwhudson, sinzui: juju-mongodb-tools: and vendor/src/golang.org/x/ reference a
LICENSE file which doesn't exist in the sources. Please add it
mwhudson, sinzui: rejected for now. afaics the other license information, and
the packaging seem to be okish
I apologise. I was
Hi Steve. Continuing with the conversation on the wrong bug...I prepared
the Juju2 specific packages to be 64 bit only. Neither Juju or upstream
support 32-bit servers.
But there was a change in plan that I was not privy to. Since 1.25 does
want juju-mongodb2.6, I think we could make the i386 and
Thank you Michael for improving the rules for this package. The Juju
team agreed that a universal mongo-tools is ideal, but too risky to
assume is true. That is why this package has the 3.2 in its name.
I think this package needs to be in main because "main" means supported.
Juju is supported and
** Changed in: juju-core/1.25
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To
** Tags added: packaging
** Summary changed:
- After upgrade Juju 1.X should still be the default
+ After dist upgrade Juju 1.X should still be the default
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The patch is good. arm64 passes just like amd64 and ppc64el
https://launchpadlibrarian.net/251720877/buildlog_ubuntu-xenial-arm64.juju-mongodb3.2_3.2.0-0ubuntu1~juju9_BUILDING.txt.gz
I have pushed the changes to
lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2
--
You
I am testing the patch now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557852
Title:
[needs-packaging] juju-mongodb3.2 in xenial, wily, and trusty
To manage notifications about this bug go to:
** Tags added: packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564662
Title:
Juju binaries should be stripped
To manage notifications about this bug go to:
Public bug reported:
Rhythmbox was not able to play some of my FLAC files until I installed
the gstreamer1.0-pulseaudio plug-in.
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
rhythmbox:
Installed: 3.3-1ubuntu6
Candidate: 3.3-1ubuntu6
Version table:
***
Hi Robie
Attached are my changes. that I pushed to
lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2
> Thank you for the update. I've reviewed the patches now they have
> headers so I can follow what's going on. Most look OK. I'm unhappy
> with two: 1.
Hi Robie
Attached are my changes. that I pushed to
lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2
> Thank you for the update. I've reviewed the patches now they have
> headers so I can follow what's going on. Most look OK. I'm unhappy
> with two: 1.
I pushed a small change to the changelog
* New upstream release (LP #1557830).
at
lp:~sinzui/ubuntu/xenial/juju-mongodb2.6/xenial-mongodb-2.6'
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
I pushed a small change to the changelog
* New upstream release (LP #1557830).
at
lp:~sinzui/ubuntu/xenial/juju-mongodb2.6/xenial-mongodb-2.6'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
kport?
I think this is needed to trusty.
> debian/copyright looks superficially OK to me, and I'm happy that Curtis
> can maintain these accurately. Leaving it for the AA to review once.
> Same with debian/missing-sources. Good job on identifying that this was
> required and taking care o
kport?
I think this is needed to trusty.
> debian/copyright looks superficially OK to me, and I'm happy that Curtis
> can maintain these accurately. Leaving it for the AA to review once.
> Same with debian/missing-sources. Good job on identifying that this was
> required and taking care o
Hi Robie. Juju2 will *not* support 32 bit archs. As this package is only
used to upgrade to 2.0, it will not be used on armhf and i386 archs.
Per point 2 to in comment 4, Ubuntu accepts FTBFS, where as the Juju team
prefers to be clear about what is not supported:
maybe we want
Architecture:
Hi Robie. Juju2 will *not* support 32 bit archs. As this package is only
used to upgrade to 2.0, it will not be used on armhf and i386 archs.
Per point 2 to in comment 4, Ubuntu accepts FTBFS, where as the Juju team
prefers to be clear about what is not supported:
maybe we want
Architecture:
** Changed in: juju-core
Status: Triaged => Fix Released
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184457
Title:
** Changed in: juju-core
Status: Triaged => Fix Released
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Ouch
> For completeness this is the lintian output in all its glory:
> E: juju2 changes: bad-distribution-in-changes-file xenial-amd64
I certainly could have put "xenial-amd64" in the changelog, but i do not
see in debian. my find also fails
>E: juju2: embedded-library
Ouch
> For completeness this is the lintian output in all its glory:
> E: juju2 changes: bad-distribution-in-changes-file xenial-amd64
I certainly could have put "xenial-amd64" in the changelog, but i do not
see in debian. my find also fails
>E: juju2: embedded-library
** Description changed:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
This branch introduces the juju2 package.
- bzr push lp:~sinzui/ubuntu/xenial/juju2/xenial-2.0-beta2
+
** Description changed:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
This branch introduces the juju2 package.
- bzr push lp:~sinzui/ubuntu/xenial/juju2/xenial-2.0-beta2
+
Attached is a gz diff of the changes in src/ from juju 1.25.4 to
2.0-beta2. Sorry. This is hell to read.
** Patch added: "All changes to juju and embedded deps"
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1560315/+attachment/4607608/+files/xenial-2.0-beta2.diff.gz
** Description
Attached is a gz diff of the changes in src/ from juju 1.25.4 to
2.0-beta2. Sorry. This is hell to read.
** Patch added: "All changes to juju and embedded deps"
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1560315/+attachment/4607608/+files/xenial-2.0-beta2.diff.gz
** Description
The attaches diff shows the changes to the juju embedded dependencies.
** Description changed:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
- Juju 2.0 uses a new package name, juju2. This package is co-installable
-
The attached diff shows the changes to debian/ from the 1.25.4 branch
(lp:~sinzui/ubuntu/xenial/juju-core/xenial-1.25.4). The 1.25.4 branch
is stalled. We are waiting on a 1.25.5 to fix a regressions. We do not
expect any other changes to the debian dir other than the changelog.
** Patch added:
The attached diff shows the changes to debian/ from the 1.25.4 branch
(lp:~sinzui/ubuntu/xenial/juju-core/xenial-1.25.4). The 1.25.4 branch
is stalled. We are waiting on a 1.25.5 to fix a regressions. We do not
expect any other changes to the debian dir other than the changelog.
** Patch added:
The attaches diff shows the changes to the juju embedded dependencies.
** Description changed:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
- Juju 2.0 uses a new package name, juju2. This package is co-installable
-
Public bug reported:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
Juju 2.0 uses a new package name, juju2. This package is co-installable
with juju-core.
** Affects: juju-core (Ubuntu)
Importance: Undecided
Public bug reported:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
Juju 2.0 uses a new package name, juju2. This package is co-installable
with juju-core.
** Affects: juju-core (Ubuntu)
Importance: Undecided
This was also seen by the in Juju CI on the wily hosts that pull lxd/lxc
packages from the lxd ppa. We downgrades the wily machines to packages
from wily-updates to get lxc working again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
# juju-mongo-tools3.2
The Juju team wants juju-mongo-tools3.2 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongo-tools3.2/xenial-mongo-tools3.2
This package is new. Upstream replaced the mongo tools included in
MongoDB 2.x with new tools from the mongo-tools
Public bug reported:
# juju-mongo-tools3.2
The Juju team wants juju-mongo-tools3.2 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongo-tools3.2/xenial-mongo-tools3.2
This package is new. Upstream replaced the mongo tools included in
MongoDB 2.x with new tools from the mongo-tools
A diff of the missing sources added to debian/.
** Patch added: "juju-mongo-tools3.2-missing-sources.diff"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1558336/+attachment/4601655/+files/juju-mongo-tools3.2-missing-sources.diff
--
You received this bug notification because
Hi Robie, Dimitri
Attached is a diff of my changes per the review.
1. I corrected the maintainer
2. I updated the changelog to state I synced the patches with mongodb 2.6.10.
Note I refreshed the patches so that they apply without fuzzy.
3, I then reverted the archs to match what juju-core
Thank you for the feedback Robie. Attached is a diff of my dep-3
changes. I also updated the control arch to any per Dimitri's desire to
build every where possible
** Patch added: "dep-3 and arch any"
This is the error
jenkins@wily-slave:~$ sudo lxc-start -n curtis -F
ln: failed to create symbolic link
‘/usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup/cpu/cpu,cpuacct’: Read-only file
system
lxc-start: conf.c: run_buffer: 347 Script exited with status 1
lxc-start: conf.c: lxc_setup: 3750 failed
This is the error
jenkins@wily-slave:~$ sudo lxc-start -n curtis -F
ln: failed to create symbolic link
‘/usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup/cpu/cpu,cpuacct’: Read-only file
system
lxc-start: conf.c: run_buffer: 347 Script exited with status 1
lxc-start: conf.c: lxc_setup: 3750 failed
A diff of the missing sources added to debian/.
** Patch added: "juju-mongo-tools3.2-missing-sources.diff"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1558336/+attachment/4601655/+files/juju-mongo-tools3.2-missing-sources.diff
--
You received this bug notification because
Hi Robie, Dimitri
Attached is a diff of my changes per the review.
1. I corrected the maintainer
2. I updated the changelog to state I synced the patches with mongodb 2.6.10.
Note I refreshed the patches so that they apply without fuzzy.
3, I then reverted the archs to match what juju-core
This was also seen by the in Juju CI on the wily hosts that pull lxd/lxc
packages from the lxd ppa. We downgrades the wily machines to packages
from wily-updates to get lxc working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for the feedback Robie. Attached is a diff of my dep-3
changes. I also updated the control arch to any per Dimitri's desire to
build every where possible
** Patch added: "dep-3 and arch any"
A diff of the patch changes for juju-mongodb3.2. It is easier to read
the actual patches then to read this diff of a patch.
** Patch added: "juju-mongodb3.2-patches.diff"
** Tags added: lxc xenial
--
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/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To manage notifications about this
Public bug reported:
# juju-mongodb3.2
The Juju team wants juju-mongodb3.2 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2
This package is an fork and upgrade of the juju-mongodb2.6 package
that will be used in upgrades. There is a lot of change in this
A diff of the patch changes for juju-mongodb3.2. It is easier to read
the actual patches then to read this diff of a patch.
** Patch added: "juju-mongodb3.2-patches.diff"
Public bug reported:
# juju-mongodb3.2
The Juju team wants juju-mongodb3.2 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2
This package is an fork and upgrade of the juju-mongodb2.6 package
that will be used in upgrades. There is a lot of change in this
** Tags added: lxc xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To manage notifications about this bug go to:
Public bug reported:
# juju-mongodb2.6
The Juju team wants juju-mongodb2.6 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongodb2.6/xenial-mongodb-2.6
This packaged in is a fork of juju-mongodb upgraded to version 2.6.
This package is only used to upgrade from juju-mongodb to
This diff from the mongodb_2.6 package debian/ to the juju-mongodb2.6
debian dir shows a lot of change. The crux of the diff is that it shows
the d/patches in the ne package are identical to the ubunti package.
** Patch added: "mongodb_2.6-to-juju-mongodb2.6.diff"
Public bug reported:
# juju-mongodb2.6
The Juju team wants juju-mongodb2.6 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongodb2.6/xenial-mongodb-2.6
This packaged in is a fork of juju-mongodb upgraded to version 2.6.
This package is only used to upgrade from juju-mongodb to
a diff of just the changes to d/patches. The patches are from mongodb
1:2.6.10-0ubuntu1
** Patch added: "juju-mongodb2.6-patches-from mongodb2.6.diff"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+attachment/4600661/+files/juju-mongodb2.6-patches-from%20mongodb2.6.diff
This diff from the mongodb_2.6 package debian/ to the juju-mongodb2.6
debian dir shows a lot of change. The crux of the diff is that it shows
the d/patches in the ne package are identical to the ubunti package.
** Patch added: "mongodb_2.6-to-juju-mongodb2.6.diff"
a diff of just the changes to d/patches. The patches are from mongodb
1:2.6.10-0ubuntu1
** Patch added: "juju-mongodb2.6-patches-from mongodb2.6.diff"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+attachment/4600661/+files/juju-mongodb2.6-patches-from%20mongodb2.6.diff
Public bug reported:
Juju 1.25.4 enabled maas 1.9 and fixes many bugs reported against 1.25.0
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
Since there are multiple
Public bug reported:
Juju 1.25.4 enabled maas 1.9 and fixes many bugs reported against 1.25.0
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
Since there are multiple
I stopped using LXDE on Ubuntu almost 6 years ago because this bug was
never addressed. The bug was confirmed almost a year later. I have
since moved on to Arch Linux.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can also confirm that the 3.19.0.49-generic kernel solves the problem
for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488426
Title:
High CPU usage of kworker/ksoftirqd
To manage
** Description changed:
Hello.
It seems that there is a bug in a default install of the ArpON 2.7
package. After successful install via 'apt-get' utility, user using a
DHCP method to obtain an IP address will receive a following error
(during arpon start):
$ sudo
** Summary changed:
- ArpON 2.7 bug: there should be -D (--darpi) flag for a DARPI technique
(/etc/default/arpon file).
+ ArpON 2.7 bug: use -D (--darpi) flag for the DARPI technique by default
(/etc/default/arpon file).
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Hello.
It seems that there is a bug in a default install of the ArpON 2.7
package. After successful install via 'apt-get' utility, user using a
DHCP method to obtain an IP address will receive a following error
(during arpon start):
$ sudo /etc/init.d/arpon start
* Starting
If I recall correctly this is an old problem that was fixed in newer
versions of the libparted library used by GParted.
I assume that you are running on an older version of Ubuntu. If you
only wish to use the latest version of GParted, you might try booting
from media containing GParted Live.
Hello. Bug report is not needed. According to a manpage for an ArpON
package ver. 2.7.2-1 included in e.g. Vivid release[1], there is
mentioned 'D' flag. I apologize for the confusion. I should check
mentioned manpage first (see [1]). Generally look for "DYNAMIC ARP
INSPECTION" sub-thread. There
NOTE: maybe a simple solution is to change a line responsible for a
DARPI technique from '/etc/default/arpon'? Just, make this small change,
so by default after ArpON installation user will not see:
"/usr/bin/arpon: invalid option -- 'd' [fail]" message. Solution(?):
--- DAEMON_OPTS="-q -f
** Description changed:
Hello. Because on Ubuntu 12.04 LTS an ArpON package is pretty outdated
(ver. 2.0-2.1 0) I've decided to use a version from a Vivid release -
2.7.
It seems that ArpON ver. 2.7 has a bug related to a DARPI anti Arp
Poisoning techniques. Because I am using a DHCP
** Description changed:
Hello. Because on Ubuntu 12.04 LTS an ArpON package is pretty outdated
(ver. 2.0-2.1) I've decided to use a version from a Vivid release - 2.7.
It seems that ArpON ver. 2.7 has a bug related to a DARPI anti Arp
- Poisoning techniques. Because, I am using a DHCP
Public bug reported:
Hello. Because on Ubuntu 12.04 LTS an ArpON package is pretty outdated
(ver. 2.0-2.1 0) I've decided to use a version from a Vivid release -
2.7.
It seems that ArpON ver. 2.7 has a bug related to a DARPI anti Arp
Poisoning techniques. Because I am using a DHCP method to
Change package to arpon.
** Package changed: linux (Ubuntu) => arpon (Ubuntu)
** Description changed:
Hello. Because on Ubuntu 12.04 LTS an ArpON package is pretty outdated
(ver. 2.0-2.1 0) I've decided to use a version from a Vivid release -
2.7.
It seems that ArpON ver. 2.7 has a
It's possible that a hardware error with the card/device is being
encountered. After you run one of the aformentioned tools and encounter
the problem, open a terminal window and enter the command: dmesg
Take a look at the output of dmesg to see if any errors are being
reported.
--
You
** Changed in: juju-core
Milestone: 2.0-alpha1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug go to:
** Changed in: juju-core
Milestone: 2.0-alpha1 => None
--
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/1516989
Title:
juju status broken
To manage notifications about this
Screen freezes periodically, have eight machines doing the same thing.
If I VNC into the machine, the graphics appear to be updating fine...but
the LCD panel is stuck. All applications are continuing to run normally.
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
Gen
** Changed in: juju-core/1.25
Status: Fix Committed => Fix Released
--
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/1516989
Title:
juju status broken
To manage
** Changed in: juju-core/1.25
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug
With the new package installed we see to correct GOARCH
gccgo-go env
GOARCH="ppc64le"
GOBIN=""
GOCHAR=""
GOEXE=""
GOHOSTARCH="ppc64le"
GOHOSTOS="linux"
GOOS="linux"
GOPATH=""
GORACE=""
GOROOT="/usr"
GOTOOLDIR="/usr/lib/gccgo/tool"
TERM="dumb"
CC="gcc"
GOGCCFLAGS="-g -O2 -fPIC"
CXX="g++"
With the new package installed we see to correct GOARCH
gccgo-go env
GOARCH="ppc64le"
GOBIN=""
GOCHAR=""
GOEXE=""
GOHOSTARCH="ppc64le"
GOHOSTOS="linux"
GOOS="linux"
GOPATH=""
GORACE=""
GOROOT="/usr"
GOTOOLDIR="/usr/lib/gccgo/tool"
TERM="dumb"
CC="gcc"
GOGCCFLAGS="-g -O2 -fPIC"
CXX="g++"
** Changed in: juju-core
Importance: Critical => High
** Summary changed:
- cannot build trusty ppc64el juju
+ cannot build trusty ppc64el juju without forcing GOARCH
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Similar to Bela Berczi (bberczi). This was on a new HP Envy 13t. It
works fine with Windows 10, but will only connect as "All Types", and
will not work as a mouse, on the 14.04.3 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: juju-core
Milestone: 1.23-beta1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's "Option interface-mtu 9000" is being ignored on bridge
interface br0
@Robie
The Juju QA team listed ubuntu proposed testing as a gap we would fix. I
think we can setup daily build using using proposed for each supported
series and arch to prevent regressions getting into updates
@Michael
gccgo-go env shows this on stillson-09 (which means the host that runs unit
Public bug reported:
The juju-core package cannot be built. Go thinks it is cross-compiling.
Go install native binaries to $GOPATH/bin, and non-native binaries to
$GOPATH/bin/. The juju core packaging fails when it tries to use
the juju/jujud in bin/, and does not find it.
The last successful
Public bug reported:
The juju-core package cannot be built. Go thinks it is cross-compiling.
Go install native binaries to $GOPATH/bin, and non-native binaries to
$GOPATH/bin/. The juju core packaging fails when it tries to use
the juju/jujud in bin/, and does not find it.
The last successful
This bug blocks Juju's CI testing and releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527020
Title:
cannot build trusty ppc64el juju
To manage notifications about this bug go to:
** Description changed:
The juju-core package cannot be built. Go thinks it is cross-compiling.
- Go install native binaries to $GOPATH/bin, and non-native binaries to
+ Go installs native binaries to $GOPATH/bin, and non-native binaries to
$GOPATH/bin/. The juju core packaging fails when it
I have tried the test patch provided by Mathias Nyman in http://linux-
kernel.2935.n7.nabble.com/TESTPATCH-v2-xhci-fix-usb2-resume-timing-and-
races-tc1250796.html#a1256745 and rebuilt a Wily 4.2 kernel and that has
prevented High CPU usage of kworker/ksoftirqd under all the
circumstances I have
@Aditya Thanks for the clarification. I had been trying to find out if
the patch had been merged.
The issue is not however fixed for me with 4.2 nor was it for lpuser in
#8 who tried a number of kernels. However it an improvement as I said in
#17
The following shows the problem first without BT
I have carried out some more comprehensive tests using the kernel in #4 over
the weekend and found it does improve my situation far more than my initial
quick test showed. Most of the rather bizarre behaviour has gone include the
changes with power from battery to external and the importance of
I also have a similar problem which does Not seem to be solved by the
patched kernel although the perf report looks very similar and plugging
in a USB device clears the problem. The starting and inhibiting of the
kworker spinning is very specific and rather bizare on my new Skylake
machine running
** Changed in: juju-core
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496972
Title:
juju bootstrap fails to successfully configure the bridge juju-br0
** Changed in: juju-core/1.25
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496972
Title:
juju bootstrap fails to successfully configure the bridge
Hi Phillip,
I tested growing an ext4 file system from 20 GiB to 40 GiB on Intel
Software RAID (Fake RAID) using the ubuntu-14.04.3-desktop-i386.iso
image and all worked as it should. :-)
Hence in my opinion this bug can be closed.
Curtis
--
You received this bug notification because you
I don't have 14.04 installed on this computer. I tested using the
ubuntu-14.04-desktop-i386.iso live image.
Did you change anything in libparted for ubuntu 14.04 since it was
first released?
If you like I can test using the ubuntu-14.04.3-desktop-i386.iso live
image.
--
You received this bug
I seem to have this bug with a Skylake machine where the firmware load
for i915/skl_dmc_ver1.bin failed with error -2.
I am running (or trying to) with the Ubuntu LTS Trusty/14.04 version.
Is there any way I can use the Wily versions of initramfs-tools or do
you have an estimate when it will be
15.10. :-)
Curtis
** Attachment added: "gparted_details-ubuntu1510-dm-grow.htm"
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1332139/+attachment/4517232/+files/gparted_details-ubuntu1510-dm-grow.htm
--
You received this bug notification because you are a member of Ub
401 - 500 of 5893 matches
Mail list logo
