** Description changed:
- [Availability]
+ In order to promote php7.0 to main, we need to drop the same universe
+ dependencies, roughly, as we did with php5.
- php7.0 is available currently in Xenial/universe.
-
- [Rationale]
-
- [Security]
-
- [Quality assurance]
-
- [Dependencies]
-
-
The attachment "php7.0.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if
** Changed in: apparmor (Ubuntu)
Importance: Undecided => Medium
** Changed in: ntp (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1546455
Bug # 1547245 filed - php7.0: remove dependencies that come from
universe
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1522422
Title:
Update to php 7.0
To manage notifications
Okay, done. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815116
Thx, Oliver
** Bug watch added: Debian Bug tracker #815116
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815116
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Thanks for submitting this bug report.
Based on the changelog entries, I would guess that this was introduced
by the fix to CVE-2015-8619.
Could you verify that downgrading to 2.0.0+dfsg-2ubuntu1.21 also fixes
it for you?
** Package changed: qemu-kvm (Ubuntu) => qemu (Ubuntu)
** CVE added:
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
--
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/1545821
Title:
Regression: spice usbredirect causes windows client to
Public bug reported:
Installed a VM with 14.04.3, did a full dist-upgrade and then installed
maas from the Trusty repos.
Since no newer maas has been SRUd yet, 1.7.6 is the only MAAS available
to trusty unless you know about the PPAs. So normal users would end up
with 1.7.6, not 1.9 by default.
[Expired for nginx (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nginx (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Changed in: juju-core (Ubuntu)
Status: Confirmed => New
--
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/1545913
Title:
[FFe] juju-core 2.0
To manage notifications about
You have been subscribed to a public bug:
Since version 1.0.8 of the lxc package in trusty it appears that it's no
longer possible to create a container with a loop backing store. To
reproduce the issue, install version 1.0.8-0ubuntu0.3 of the lxc,
liblxc1 and python3-lxc packages on trusty and
You have been subscribed to a public bug:
We have a trusty host which has 9 trusty guests running under LXC. On
the most recent reboot, 3 of the LXC processes crashed:
[ 10.912793] init: lxc-instance (nz-prod-bdbbackup-akl3) main process (3175)
terminated with status 255
[ 11.031717] init:
You have been subscribed to a public bug:
When I create a vivid lxc in trusty like this:
lxc-create -t ubuntu -n vivid-lxc -- -r vivid
I get this error at the end:
Hit http://archive.ubuntu.com vivid-updates/universe Translation-en
You have been subscribed to a public bug:
When cloning an unprivileged container with the "-s -B overlayfs" flags,
then starting this container and running a command like ``apt-get
update`` in the new container, a kernel error "Failed to whiteout" is
produced.
- Kernel error:
** No longer affects: lxc
--
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/1285850
Title:
interuppting lxc-clone can destroy source container
To manage notifications about this bug go
Nothing LXC can do about it. An unprivileged container cannot have any
more right than the user which spawned it. Your user cannot open that
many files therefore root in the container can't either.
** Changed in: lxc
Status: New => Won't Fix
--
You received this bug notification because
** Project changed: lxc => lxc (Ubuntu)
--
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/1532069
Title:
Can't create a container with a loop backing store in 1.0.8
To manage
You have been subscribed to a public bug:
trusty
lxc 1.1.2-0ubuntu3~cloud0
kernel Linux ambipom 3.13.0-55-generic #94-Ubuntu SMP Thu Jun 18 00:27:10 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
All processes running on the container:
34700 ?Ss 0:00 [lxc monitor] /var/lib/lxc
You have been subscribed to a public bug:
I have lxc installed on 14.04 , I am getting following error while
running lxc-create command
dtripathi@dtripath-x:~$ sudo lxc-create -t default -n dtripathi-lxc01
lxc-create: symbol lookup
You have been subscribed to a public bug:
I'm using lxc 1.0.7 from the stable PPA on precise.
When I use lxc-clone to copy a container running MAAS, which uses
hardlinks to manage images, each hardlinked file is created as a new
file in the cloned rootfs, increasing my file system size by
You have been subscribed to a public bug:
Developers are required to manually hack their configuration to enable
.lxc domain name resolution. This appears to be documented solely in
/etc/default/lxc-net. This documentation is incorrect, as it tells
developers to edit /etc/dnsmasq.conf and this
** Project changed: lxc => lxc (Ubuntu)
--
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/1521151
Title:
init: lxc-instance main process terminated with status 255
To manage
** No longer affects: lxc
--
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/1342960
Title:
comments in common.conf must be updated
To manage notifications about this bug go to:
** Project changed: lxc => lxc (Ubuntu)
--
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/1445539
Title:
Can't create vivid lxc on trusty
To manage notifications about this bug go to:
** Project changed: lxc => lxc (Ubuntu)
--
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/1486073
Title:
'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7
To manage
You have been subscribed to a public bug:
I know this seems like an odd bug, but I've spent all day chasing it
down.
I was seeing problems with LDAP lookups inside an LXC container, and
strace on getent lookups was showing that attempts to read from
/var/run/nslcd/socket were being closed as -1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
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/1486073
You have been subscribed to a public bug:
I want to allow multiple users to create unpriviledged containers on the
same host. And I would like each user to be assigned a different
bridge, so that each user's containers can be restricted to a sub-net.
The `/etc/init/lxc-ent` script seems to be
You have been subscribed to a public bug:
$ sudo lxc-start -d -n mongodb-server-1
[sudo] password for kapil:
lxc-start: Executing '/sbin/init' with no configuration file may crash the host
how bout just no such container exists.
** Affects: lxc (Ubuntu)
Importance: Undecided
** Project changed: lxc => lxc (Ubuntu)
--
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/1472929
Title:
undefined symbol: cgmanager_get_pid_cgroup_abs_sync
To manage notifications about
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
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/1470599
** Project changed: lxc => lxc (Ubuntu)
--
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/1436722
Title:
lxc domain setup instructions are incorrect
To manage notifications about this
** Project changed: lxc => lxc (Ubuntu)
--
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/1470599
Title:
Stuck mountall inside container
To manage notifications about this bug go to:
** Project changed: lxc => lxc (Ubuntu)
--
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/1441307
Title:
lxc-clone makes new copies of each hardlinked file
To manage notifications about
** No longer affects: lxc
--
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/1340836
Title:
error: error executing "lxc-start" when juju client runs inside kvm
To manage
** Project changed: lxc => lxc (Ubuntu)
--
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/1302053
Title:
lxc-start with bad container name gives strange err message
To manage
** Project changed: lxc => lxc (Ubuntu)
--
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/1359224
Title:
Feature request: Add support for multiple bridges
To manage notifications about
** Project changed: lxc => lxc (Ubuntu)
--
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/1428490
Title:
AppArmor vs unix socket inside LXC containers
To manage notifications about this
After reviewing the changes between -3ubuntu7.4 and -3ubuntu7.5, I have
found that the problem is caused by the removal of the file
/lib/udev/rules.d/95-multipath.rules. In -3ubuntu7.4, it contained the
following:
#
# udev rules for multipathing.
# The persistent symlinks are created with the
vim is now built for python3. added some -py2 variants for those who
need them.
** Changed in: vim (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-utils in Ubuntu.
Toby,
what distro, release and kernel are you using?
And would you be willing to try a custom test kernel?
--
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/1428490
Title:
AppArmor vs
101 - 142 of 142 matches
Mail list logo
