Jackson, can you please do debian-ubuntu debdiffs instead of, or in
addition to ubuntu-ubuntu ones? we want to review and minimize the delta
to debian. The attached deb.diff can't be applied to anything as it
involves a new upstream version, so it's a lot of manual work to apply
this (way more than
Uploaded, thanks!
** Changed in: golang (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
https://bugs.launchpad.net/bugs/1501651
Title:
ARM chroot issues: fatal error: rt
Package fails to build on some architectures, can you please have a
look? https://launchpad.net/ubuntu/+source/golang/2:1.5.1-0ubuntu3
Unsubscribing sponsors, please re-subscribe if/when you have a followup
patch.
** Changed in: golang (Ubuntu)
Status: Fix Committed => In Progress
--
You
The attached debdiff is for trusty, adding task. Vivid is EOL in about a
month, so let's not worry about this any more.
** Also affects: neutron (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu Trusty)
Assignee: (unassigned) => Edward Hope-Morley (ho
trusty has 2014.1.5-0ubuntu, this patch is against some 2015 "trusty-
kilo" which is not Ubuntu. Is this actually an issue in trusty? If so,
please adjust the patch and set back to new, otherwise invalidate the
trusty task.
Unsubscribing sponsors, as there is nothing to do here.
** Changed in: ne
*** This bug is a duplicate of bug 174858 ***
https://bugs.launchpad.net/bugs/174858
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: net-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubun
** Branch linked: lp:update-notifier
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/525674
Title:
apt-check hangs, preventing login via SSH
To manage notifications about this bug go t
Thank you! Uploaded.
** Changed in: update-notifier (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/525674
Title:
apt-check hangs, pr
Importance in Ubuntu -> Low since this has been filed upstream. In
Ubuntu we will follow what upstream does for this.
** Bug watch added: MySQL Bug System #70672
http://bugs.mysql.com/bug.php?id=70672
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=70672
Importance: Un
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) => Lars Tangvald (lars-tangvald)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1435709
Title:
mysql.service fail to
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) => Lars Tangvald (lars-tangvald)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1478849
Title:
infinite loop in /usr/
In mysql-5.5, we are on 5.5.46 in Precise and Trusty and this was fixed
in upstream release 5.5.41.
In mysql-5.6, we are on 5.6.27 in Trusty, Vivid, Wily and Xenial and
this was fixed in upstream release 5.6.22.
** Changed in: mysql-5.5 (Ubuntu Precise)
Status: Triaged => Fix Released
**
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) => Norvald H. Ryeng (nryeng)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1366073
Title:
Combination of CREATE, REN
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1311387
Title:
add a small default innodb_buffer
I'm looking at this with upstream right now. We can't find this in 5.6.
It does exist in 5.7 but has been fixed. If you disagree, please explain
and reopen.
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
** Changed in: mysql-5.6 (Ubuntu)
Status: New =>
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1319362
Title:
Update my.cnf keys for avoid shut
This landed in 5.6.24. We are up to 5.6.27 now in all supported
releases.
** Changed in: mysql-5.6 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) => Lars Tangvald (lars-tangvald)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1468185
Title:
Function 'innodb' alr
Public bug reported:
Fresh install of ubuntu 15.10 wily server on an amd64 machine -
everything up to date.
When installing backuppc with 'apt-get install backuppc' I get the
following error upon configuration of backuppc:
update-rc.d: warning: start and stop actions are no longer supported; fal
You are right, I have got other problems after adding the device to the
container. I see it is possible to get quota working, but it's too
tricky and unpredictrable for production use. I'm wondering why LXC is
not using real device by default for LVM (XFS etc.)?
--
You received this bug notifica
Public bug reported:
We are seeing DKMS build failures against the Ubuntu 4.3 kernel:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial-canonical-kernel-team-
unstable/xenial/amd64/i/iscsitarget/20151113_120650@/log.gz
** Affects: iscsi
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Unfortunately, we have to ship _some_ default, even if it is not the
most appropriate in all cases. I think it's most appropriate to ship the
default that upstream consider best, and for 5.6 it is 128 MB. This does
Public bug reported:
We seem to be seeing ADT test failures against the Ubuntu v4.3 kernel:
FAIL: lxc-tests: /usr/bin/lxc-test-ubuntu
Log:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial-canonical-kernel-team-
unstable/xenial/amd64/l/
I just test the proposed package version 1.0.8-0ubuntu0.1 and it fix my
issue.
Thanks a lot
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://b
Public bug reported:
When installing mysql-server-5.6, the user gets the following warning
printed to the terminal:
2014-05-14 13:54:03 0 [Warning] TIMESTAMP with implicit DEFAULT value is
deprecated. Please use --explicit_defaults_for_timestamp server option
(see documentation for more details).
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I see three separate issues in your report:
1) Deprecation warning about key_buffer. This was fixed in 5.6.25-2 in
Debian and the fix is included in the current 5.6.27-2 in Ubuntu.
2) Deprecation warning about ti
** Tags added: xenial-4.3-adt-failures
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to iscsitarget in Ubuntu.
https://bugs.launchpad.net/bugs/1516005
Title:
iscsitarget: build failures against kernel 4.3
To manage notifications abou
** Tags added: xenial-4.3-adt-failures
--
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/1516008
Title:
lxc: adt testing against v4.3 kernel failing
To manage notifications about this bug
This bug was fixed in the package update-notifier - 3.164
---
update-notifier (3.164) xenial; urgency=medium
* debian/90-updates-available
- Now directly prints the cached info if available
=> avoid login stalls due to motd updates (LP: #525674)
- Also fixes a former p
It seems like there is a missing dependency. As soon as I install
libsocket6-perl and then install backuppc, it seems to configure
correctly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to backuppc in Ubuntu.
https://bugs.launchpad.net
** Attachment added: "strace"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1516037/+attachment/4518284/+files/lxc-start.trace
--
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/15160
Public bug reported:
After upgrading to lxc 1.1.5-0ubuntu1, lxc-start fails like this:
lxc-start: start.c: preserve_ns: 149 Permission denied - failed to open
'/proc/7170/ns/mnt'
lxc-start: start.c: lxc_spawn: 993 failed to store namespace references
lxc-start: start.c: __lxc_start: 1192 failed
http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-11-current.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1458323
Title:
Asterisk crashes with default install
Pardon, I mean
http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-13-current.tar.gz
of course.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1458323
Title:
Asterisk cra
Could you post the container configuration file?
--
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/1516037
Title:
lxc-start fails with 1.1.5-0ubuntu1
To manage notifications about this bu
@faux
do you still have this issue?
--
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/1452601
Title:
vivid container's networking.service fails on boot with signal=PIPE
To manage notific
** Attachment added: "config"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1516037/+attachment/4518324/+files/config
--
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/1516037
Title
** Attachment added: "fstab"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1516037/+attachment/4518325/+files/fstab
--
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/1516037
Title:
But I should also note that the same thing happened with a freshly-
created container, using "sudo lxc-create -n trusty-test -t ubuntu -- -r
trusty". So I don't think my custom apparmor hack there can be at
fault.
--
You received this bug notification because you are a member of Ubuntu
Server Te
Hi Colin,
Could you:
- Tell us what architecture you're running on (noticed the container config
shows i386)
- Confirm that both lxc and liblxc1 are at the same version
- Tell us the exact kernel version you're running
- Look for any apparmor denials in dmesg
Thanks!
--
You received this b
What do you mean by "not using real device"? The real lvm device is
mounted into the container. However actually offering the device node
into the container would not be a safe default. In particular, it
allows the container admin to write nonsense onto the device node,
feeding garbage into the
Once Seth's work enabling mounting inside containers is complete, we'll
most likely want some way of enabling quotas, so leaving this open as a
wishlist (feature request/enhancement) item.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
My host is xenial amd64; the guest is i386 because a million lines of
Python is rather more memory-efficient that way. :-)
Yes, lxc and liblxc1 are at the same version.
Kernel is linux-image-4.2.0-17-generic 4.2.0-17.21, though this also
happened with 4.2.0-16.19 (I rebooted to see if that cleare
What does
ls -l /proc/sys/kernel/yama/
cat /proc/sys/kernel/yama/ptrace_scope
show?
--
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/1516037
Title:
lxc-start fails with 1.1.5-0ubuntu1
Nm, afaict yama should never prevent this.
--
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/1516037
Title:
lxc-start fails with 1.1.5-0ubuntu1
To manage notifications about this bug go t
I suggest that README.Debian (or Ubuntu) mention the workarounds
regarding bind9 and ipv6.
It might save some time in debugging lxc problems.
--
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/bug
How about a comment in the /etc/default/lxc-net file?
I guess the question is - when it broke for you, which files did you
first look at to try to fix it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.laun
This bug was caused by a silent apparmor denial due to a local
modification of /etc/apparmor.d/usr.bin.lxc-start (dropped
attach_disconnected flag).
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, whi
This is expected failure right now due to broken simplestream for
xenial.
Your test results match those I'd expect so you don't appear to actually
have any regression wrt the archive.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
** Also affects: simplestreams (Ubuntu)
Importance: Undecided
Status: New
--
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/1516008
Title:
lxc: adt testing against v4.3 kernel fa
** Changed in: lxc (Ubuntu Trusty)
Status: Fix Committed => In Progress
--
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/1514623
Title:
New upstream bugfix release 1.0.8 (LXC MRE)
Uploaded the fix to xenial, wily, vivid and trusty.
** Changed in: lxc (Ubuntu Vivid)
Status: Triaged => In Progress
** Changed in: lxc (Ubuntu Wily)
Status: Triaged => In Progress
** Changed in: lxc (Ubuntu Xenial)
Status: Triaged => Fix Committed
** Changed in: lxc (Ubunt
Server side issue being worked under LP: #1516105.
--
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/1516008
Title:
lxc: adt testing against v4.3 kernel failing
To manage notifications ab
What I should do is try to back out some of my changes and determine
whether I can duplicate the problem.
Then I can determine which changes matter and which ones don't.
I won't have time for a few days, but I will do my best.
--
You received this bug notification because you are a member of Ub
Hello Kevin, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Hello Martin, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Hello Martin, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello Kevin, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Hello Chris, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Hello Adam, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Hello Nick, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Hello Brad, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
Hello Adam, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
Hello Chris, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Hello Brad, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Hello Chris, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Hello Brad, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
Hello Stéphane, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
Hello Daniel, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Public bug reported:
I try to install mysql server with ubutu 15.10 but the the error
returned :
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: mysql-common 5.6.27-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
U
** Patch added: "deb.diff"
https://bugs.launchpad.net/ubuntu/+source/webtest/+bug/1515758/+attachment/4518511/+files/deb.diff
** Changed in: webtest (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is su
** Changed in: multipath-tools (Ubuntu Trusty)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: multipath-tools (Ubuntu Trusty)
Milestone: None => ubuntu-14.04.4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is s
--- Comment (attachment only) From gmgay...@us.ibm.com 2015-10-06 18:03
EDT---
** Attachment added: "dmesg file"
https://bugs.launchpad.net/bugs/1503305/+attachment/4518513/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is su
Default Comment by Bridge
** Attachment added: "dmesg file"
https://bugs.launchpad.net/bugs/1503305/+attachment/4518512/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.n
Patch to fix this and merge a bugfix release from debian attached
** Patch added: "debian to new"
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1515986/+attachment/4518530/+files/deb.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This bug was fixed in the package lxc - 1.1.5-0ubuntu2
---
lxc (1.1.5-0ubuntu2) xenial; urgency=medium
* Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
of hardcoding xz. Also update list of supported releases and use trusty
** Summary changed:
- Please update mawk to latest upstream release
+ Please update mawk to latest upstream release - mawk in Ubuntu is 16 years
old!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mawk in Ubuntu.
https://bugs.launchp
** Description changed:
- mawk in Ubuntu is 15 years old and very buggy (see
+ mawk in Ubuntu is 18 years old and very buggy (see
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mawk and
https://bugs.launchpad.net/ubuntu/+source/mawk , also bugs in other
products, like bug #1331381) :(
78 matches
Mail list logo
