Looking at the dependency chain to support the MIR, we're currently
pulling two versions of check into main (golang-gocheck and golang-
check.v1). This is caused by the use of golang-goyaml which depends on
the older golang-gocheck package.
golang-yaml.v2 aligns with the newer check version -
MIR review information for new -dev dependencies
>> golang-github-bmizerany-assert <<
[Availability]
In universe
[Rationale]
Dependency for golang-github-bmizerany-pat
[Security]
No security history
[Quality assurance]
Package builds OK and unit tests are executed
[Dependencies]
All in main
Tracking bug 1504821 in juju-core for yaml.v1 -> yaml.v2 switch:
** Changed in: golang-gocheck (Ubuntu)
Status: New => Incomplete
** Changed in: golang-goyaml (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team,
juju-mongodb no longer ftbfs in wily
** Changed in: juju-mongodb (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
https://bugs.launchpad.net/bugs/1267393
>> dh-golang <<
[Availability]
In universe
[Rationale]
Dependency for all other golang-* packages
[Security]
No security history
[Quality assurance]
Package builds OK but has no unit tests.
[Dependencies]
All in main or covered by this MIR
[Standards compliance]
OK
[Maintenance]
Public bug reported:
We are seeing test suite failures under ADT testing with linux, linux-
lts-utopic and linux-lts-vivid kernels:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
** Also affects: golang-check.v1 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gccgo-go in Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core, juju-mongodb,
I've investigated this issue in Willy:
Hugepages are now mounted on /dev/hugepages and not in /run/hugepages
And also libvirt wants to use /dev/hugepages and more precisely
/dev/hugepages/libvirt/qemu (so without the kvm in the middle of the
path)
This means, the apparmor rule for huge pages
They all get stuck in lxc-test-ubuntu which would indicate either a hang
in debootstrap (newly introduced debconf question) or a failure to reach
the cloud image server.
In either case, you've not actually regressed LXC, the other tests would
have failed if that was the case.
So I'd toss this
** Also affects: golang-gocheck (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gccgo-go in Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core, juju-mongodb,
Weard... On my laptop I'm also on Willy. On my laptop, I only had to
correct the apparmor profile...
Could some one check if it is enough to change apparmor or if it's also
necessary to create the folder /dev/hugrpages/libvirt/qemu?
--
You received this bug notification because you are a member
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
https://bugs.launchpad.net/bugs/51925
Title:
Wrong charset for German messages
To manage notifications about this bug go to:
** Branch linked: lp:debian/w3m
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to w3m in Ubuntu.
https://bugs.launchpad.net/bugs/265144
Title:
hardy: using provided lynx keymap in w3m reports "line 49: unknown key
''" when starting
Martin and I reviewed and tested with golang-*-dev packages that are
already in the archive; proposed packaging update is here:
https://code.launchpad.net/~james-page/ubuntu/wily/juju-core/mir-
fixes/+merge/274052
The only existing golang-dev package which we where not able to use was
If the move to golang-yaml.v2 is low risk and can be done, then I'll
include that package for MIR and drop golang-goyaml and golang-gocheck;
however if that's not the case, then I think we should *not* use golang-
goyaml-dev and fallback to the embedded code copy in juju-core for this
cycle; juju
Is this Bug #1490110 ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1504496
Title:
package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess
installed post-installation
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcgroup in Ubuntu.
https://bugs.launchpad.net/bugs/838729
Title:
x200 laptop fails to complete to suspend on second suspend after boot
To manage notifications
[Expired for nagios3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nagios3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios3 in Ubuntu.
Any news on this guys?
I'm trying to create a QCoW2 image with Cloud Init, using Packer,
everything seems t be okay but, I'm seeing the following problem:
---
2015-10-10 02:27:39,689 - url_helper.py[WARNING]: Calling
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [20/30s]:
You might be onto something there.. on my local juju host (where I run
the command) I had 2 DNS servers, one that knew about the .maas and one
that didn't. Changed over to the one that did and it worked.
Having said that, I didn't retry to see if it failed reliably without
said DNS.
--
You
I guess it depends on what you call a bug. All my Ubuntu & Lubuntu 14.04
LTS install have the error because it came from an update. I don't know
what it really is, but the config makes since. The real issue is that it
came in an update and I didn't write it or even install squid myself, it
just
The bug also still exist in Ubuntu Willy (15.10)...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1461012
Title:
Hugepage and KSM not configured correctly under systemd
To manage
22 matches
Mail list logo
