This bug was fixed in the package init-system-helpers - 1.28ubuntu2
---
init-system-helpers (1.28ubuntu2) xenial; urgency=medium
* invoke-rc.d: Fix package installation failure when installing a package
with an upstart script and systemd unit, but no SysV script in a chroot.
*** This bug is a duplicate of bug 1543051 ***
https://bugs.launchpad.net/bugs/1543051
This is a duplicate of bug #1543051, for which a fix has already been
uploaded and is currently in xenial-proposed.
** Changed in: sysvinit (Ubuntu)
Status: New => Invalid
** This bug has been marke
Well, it's a problem on s390x, where they are not dedicated VMs.
wgrant has run a cleanup of loopsetup devices now, on those builders.
adding a check to test that losetup -f matches after a kpartx -a / -d
round trip.
--
You received this bug notification because you are a member of Ubuntu
Serve
Public bug reported:
I've observed in livefs build logs that with kpartx 0.5.0-7ubuntu12,
'kpartx -d' is not removing the loop mapping (losetup -d). E.g., build
log diff:
+ kpartx -v -d binary/boot/disk.ext4
del devmap : loop0p1
-loop deleted : /dev/loop0
This doesn't seem to be causing any i
Oh, good.
--
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/1543170
Title:
lxc fails to install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ini
Up until last week, cloud images were being built just fine with lxc and
lxd in them, starting this week, they fail, that seems like a regression
to me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchp
FWIW I dont' think this is a regression. I think this has always been
buggy. We just don't notice bc we don't generally debootstrap systems
with lxc any more.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs
I think this should be fixed in the golang 1.6~rc2 package, can you
confirm?
--
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/1541014
Title:
'go vet' falls over on expressions like C.f
Subscribing Martin Pitt who very recently merged init-system-helpers.
I've not yet read the diff, but this seems like a fair bet as to what
changed recently (last upload was Feb 5).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Note that the analogous upstart test, 'initctl version', does work under
chroot
sudo lxc-create -t download -n t1 -- -d ubuntu -r trusty -a amd64
sudo lxc-create -t download -n x1 -- -d ubuntu -r xenial -a amd64
chroot /var/lib/lxc/t1/rootfs initctl version
init (upstart 1.12.1)
chroot /var/lib/
This should be an easy fix, but as an alternative while a developer gets
around to it, you can also use the Monitoring Plugins PPA:
https://launchpad.net/~pkg-nagios-devel/+archive/ubuntu/plugins. See
also: https://www.monitoring-plugins.org/
Note that this will result in installing a far newer ve
I just compared the content of lxc 1.1.5-0ubuntu6 which I'm assuming was
the last working LXC version in cloud images and lxc
2.0.0~beta2-0ubuntu2 that we have now and neither provides any
/etc/init.d script nor am I seeing any packaging change on our side
which would explain this.
Packaging diff
I'm marking the lxc task invalid as no packaging change occurred on
lxc's side and this, admittedly rare, init script configuration has been
supported for years and should still be supported.
Directly subscribing the containers team though so we can help track
down the source of the regression.
-
Bug #1543399 filed - php-directory-scanner: add nocheck and stage1 build
profiles
--
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 notificatio
This bug was fixed in the package walinuxagent - 2.1.3-0ubuntu1
---
walinuxagent (2.1.3-0ubuntu1) xenial; urgency=medium
* New upstream release (LP: #1543359):
- Bug fixes for extension handling
- Feature enablement for AzureStack.
-- Ben Howard Mon, 08 Feb 2016 16:33:07
Indeed, if I do
sudo debootstrap --verbose --components=main,universe --arch=amd64
--include=lxc xenial x
pause the debootstrap after it has expanded all the packages, edit
x/usr/sbin/invoke-rc.d to change "elif test -d /run/systemd/system" on
line 278 to "elif true', then the installation succee
Bug #1543376 filed - phpab: add nocheck and stage1 build profiles
--
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 about this bu
I think the bug may be the following:
invoke-rc.d checks whether upstart or systemd is running by checking for
-d /run/systemd/system
inside the chroot, this would not be the case. Therefore it checks for
the sysvinit script, which lxc does not provide.
--
You received this bug notification b
An easy way to reproduce this is using
sudo lxc-create -t ubuntu -n x1 -- -r xenial --packages lxc
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https:/
This seems very similar to bug 1185364.
--
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/1543170
Title:
lxc fails to install
To manage notifications about this bug go to:
https://bugs.la
** Changed in: qemu (Ubuntu)
Status: Incomplete => New
** 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/1542509
Title:
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1543367
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a commen
Note that an unprivileged user on the host is able to do these mounts.
Unprivileged users inside a privileged container cannot.
--
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/1543367
Tit
*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu. As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have
*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu. As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have
Public bug reported:
Create a trusty or xenial host. Probably use ubuntu-lxc/daily ppa to
work around other bugs.
Create a privileged container (again either trusty or xenial will do),
and install ubuntu-lxc/daily ppa there.
Create an unprivileged container in that container. It will fail at
m
I'm quite certain this is not an apparmor issue, since leaving
everything unconfined does not help.
It could be something we're doing wrong in lxc, but I'm not sure what.
It could be something inherent in mounting onto an open fd.
--
You received this bug notification because you are a member o
You have been subscribed to a public bug:
Create a trusty or xenial host. Probably use ubuntu-lxc/daily ppa to
work around other bugs.
Create a privileged container (again either trusty or xenial will do),
and install ubuntu-lxc/daily ppa there.
Create an unprivileged container in that containe
Bug #1543361 filed - Rebuild packages for bootstrapping PHP7.0 in
archive
--
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 about
Public bug reported:
Microsoft has requested that we pick up 2.1.3.
** Affects: walinuxagent (Ubuntu)
Importance: Critical
Assignee: Ben Howard (utlemming)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subsc
Bug #1543349 filed - [needs-packaging] php-memcache
--
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 about this bug go to:
https
Public bug reported:
libpam-cgfs expects systemd to create the name=systemd cgroup.
However, on trusty with upstart that does not happen. So the logged-in
user doesn't get his own name=systemd cgroup.
It's not entirely clear where this should be fixed. Putting the logic
into libpam-cgfs may be
lxc currently puts 'name=systemd' into its list of controllers which
must be available for the user. That's not always the case. Again it's
not clear what the best thing to do there is.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Description changed:
The current version of src:php-memcache produces php5-memcache. As we
look to transition to PHP7.0, we need to update to the latest version.
URL: https://github.com/websupport-sk/pecl-memcache
License: PHP 3.0
Notes: This external version of php-memcache has no
Public bug reported:
The current version of src:php-memcache produces php5-memcache. As we
look to transition to PHP7.0, we need to update to the latest version.
URL: https://github.com/websupport-sk/pecl-memcache
License: PHP 3.0
Notes: This external version of php-memcache has not yet been pack
Bug #1543324 filed - [needs-packaging] php-pear
Bug #1543334 filed - [needs-packagin] pkg-php-tools
--
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
Public bug reported:
An updated pkg-php-tools is needed to bootstrap PHP7.0 dependencies
throught the archive (i.e., the dh_phppear and dh_phpcomposer tools).
URL: http://anonscm.debian.org/cgit/pkg-php/pkg-php-tools.git/log/?h=master-7.0
License: LGPL
Notes: This should result in version 1.32 be
** Tags added: needs-packaging
--
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/1543324
Title:
[needs-packaging] php-pear
To manage notifications about this bug go to:
https://bugs.laun
Public bug reported:
Upstream (Debian), the php-pear package is no longer built from
src:php5, but now from its own src:php-pear package.
URL: http://anonscm.debian.org/cgit/pkg-php/php-pear.git (debian/sid branch)
License: PHP (I believe)
Notes: Currently, src:php5 provides php-pear 5.6.16+dfsg-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: neutron (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/15
** Changed in: juju-core
Assignee: Jorge Niedbalski (niedbalski) => (unassigned)
** Tags removed: cts-cloud-review sts
--
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/1290920
T
Sure PFB outputs
$ dpkg -l | grep qemu
ii ipxe-qemu
1.0.0+git-20141004.86285d1-1ubuntu3all PXE boot firmware - ROM
images for qemu
ii qemu-block-extra:amd641:2.3+dfsg-5ubuntu9.2
amd64ext
Hello Robert, or anyone else affected,
Accepted cloud-init into wily-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.7~bzr1149-0ubuntu6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Robert, or anyone else affected,
Accepted cloud-init into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.5-0ubuntu1.16 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Changed in: curtin
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1532062
Title:
Drives mistakenly reported as removable
To manage notif
Potential packaging problem.
** Project changed: openstack-manuals => cinder (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1534065
Title:
Install and configure Cinder cont
** Tags added: sts-needs-review
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications ab
** Package changed: ubuntu => lxd (Ubuntu)
** Package changed: lxd (Ubuntu) => 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/1543170
Title:
lxc fails to install
To manag
You have been subscribed to a public bug:
After following the documented steps in the Cinder controller node
installation, running [su -s /bin/sh -c "cinder-manage db sync" cinder] fails
with error "ImportError: No module named oslo_policy". I had to manually
install "python-oslo-policy" packag
** Branch linked: lp:~smoser/curtin/trunk.lp1532062
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1532062
Title:
Drives mistakenly reported as removable
To manage notifications abo
You have been subscribed to a public bug:
LXC in Xenial fails to install. Since this is a seed package for the
cloud-images, cloud image builds are now broken.
Setting up lxc (2.0.0~beta2-0ubuntu2) ...
invoke-rc.d: unknown initscript, /etc/init.d/lxc not found.
dpkg: error processing package lxc
On Mon, Feb 8, 2016 at 3:07 AM, bhat3 wrote:
> @Nish Can you explain the changes or diff to Ondřej's packages? I run
> them in production with Typo3 7 and Drupal 8 but on trusty.
There is no alteration to Ondřej's debian packages (note, that may or
may not be the same as his PPA, but I think it i
Default Comment by Bridge
** Attachment added: "sosreport from host nulp1"
https://bugs.launchpad.net/bugs/1526984/+attachment/4567117/+files/sosreport-nulp1.134066-20151215095815.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
more info here, and I'm going to merge Robert's change.
On a system the kernel team has, the value of 'removable' changed even from
one version of a kernel to another.
$ uname -r
4.2.0-27-generic
$ cat /sys/class/block/sda/removable
0
But on 4.4.0-2-generic that same sysatem shows that drive as
This bug was fixed in the package golang - 2:1.6~rc2-0ubuntu1
---
golang (2:1.6~rc2-0ubuntu1) xenial; urgency=medium
* New upstream version. (LP: #1541660)
* Update d/patches/0001-s390x-port.patch from IBM's repo.
-- Michael Hudson-Doyle Thu, 04 Feb
2016 14:06:36 +1300
** Cha
Thanks, I'm sponsoring that one
** 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/1541660
Title:
please upload go 1.6
Ah, it looks like Colin did just cherry pick the fix for this bug; from
the backport .deb's changelog:
+dnsmasq (2.68-1ubuntu0.1ppa1) trusty; urgency=medium
+
+ * Cherry-pick from 2.73:
+- Correctly sanitise DNS header bits in answer when recreating query for
+ retry.
+
+ -- Colin Watson
Actually sorry the PPA is a backport of dnsmasq 2.68 not just the above
patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1543185
Title:
Malformed query causing timeouts due to
This patch http://lists.thekelleys.org.uk/pipermail/dnsmasq-
discuss/2015q2/009575.html appears to solve the problem, cjwatson built
a test package in his ppa which I used to test this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dn
This post to the dnsmasq-discuss list:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-
discuss/2015q2/009575.html suggests that the bug has been fixed in a
later version of dnsmasq and should be fairly easy to backport.
--
You received this bug notification because you are a member of Ubuntu
S
Override component to main
python-openvswitch 2.5.0~git20160129.46a88d9-0ubuntu1 in xenial amd64:
universe/python/extra/100% -> main
python-openvswitch 2.5.0~git20160129.46a88d9-0ubuntu1 in xenial arm64:
universe/python/extra/100% -> main
python-openvswitch 2.5.0~git20160129.46a88d9-0ubuntu1 in x
Public bug reported:
In some situations dnsmasq makes malformed upstream queries resulting in
servfail being returned after the 5s timeout built in to dnsmask.
For example asking for
foo
with athing.bar.com and bar.com in the search path and two servers
dns1.bar.com and dns1.bar.com results in
backport accepted, enjoy
** Changed in: trusty-backports
Status: In Progress => Fix Released
--
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/1494141
Title:
Please backport hapro
Ok, thanks, that might work.
I will have to think on how best to parse the log file for any error
messages that are only applicable to the actual LXC Python API call the
application is executing and pass these error messages back to the user
and present them in a meaningful manner.
--
You receiv
** Also affects: linux (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Wily)
Status: New => Fix Committed
--
You received this bug notification because you are a member o
Hello,
Here are the following verifications that were made on trusty :
1) haproxy-1.5.14-1ubuntu0.15.10.1 builds correctly
2) haproxy-1.5.14-1ubuntu0.15.10.1 installs correctly
3) when nbproc > 1 is used, all haproxy processes are stopped correctly
I am now positive that 1.5.14 fixes the probl
** Summary changed:
- HAProxy 1.5 init script does not terminate processes
+ Please backport haproxy 1.5.14-1ubuntu0.15.10.1 from wily-updates
--
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/b
This bug has been fixed by the latest upload of rsyslog :
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1539483. Marking
it fix released
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Invalid
** Changed in: rsyslog (Ubuntu)
Status: Triaged => Fix Released
** Change
Corey, oh man I missed that detail. I had blinders one, forgot to check
for that.
So this is fine then. Would be nice to see a python3 version too, but
obviously not a blocker.
** Changed in: openvswitch (Ubuntu)
Status: New => Fix Committed
** Changed in: openvswitch (Ubuntu)
Assi
@bhat3 I don't think there are any differences on src:php7.0 (as we
coordinate the changes - I just merged couple of patches), so the main
differences is in packages written in PHP (and perhaps some PECL
modules, haven't checked what has been done in ~php-ubuntu on that
front).
--
You received th
Fix committed to Debian master branch: http://anonscm.debian.org/cgit
/collab-maint/init-system-helpers.git/commit/?id=628cb4328
Will backport to xenial.
** Changed in: init-system-helpers (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are
I now downloaded the current xenial/amd64 Launchpad chroot tarball
(which is really still wily), dist-upgraded that, and installed ofono,
and I can reproduce the regression with that.
** Changed in: init-system-helpers (Ubuntu)
Status: New => In Progress
** Changed in: init-system-helpers
** Changed in: docker.io (Ubuntu)
Assignee: Ryan Harper (raharper) => Dimitri John Ledkov (xnox)
** Changed in: docker.io (Ubuntu)
Importance: High => Critical
** Also affects: docker.io (Ubuntu Xenial)
Importance: Critical
Assignee: Dimitri John Ledkov (xnox)
Status: Confi
I tried to reproduce this in a current xenial schroot (with policy-rc.d)
and VM, and apt-get install ofono works in both cases. In the build log
this happens while upgrading init-system-helpers as well, though, which
might have an influence on this.
** Changed in: init-system-helpers (Ubuntu)
@Nish Can you explain the changes or diff to Ondřej's packages? I run
them in production with Typo3 7 and Drupal 8 but on trusty.
--
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
T
Public bug reported:
On version 1.26:
invoke-rc.d: unknown initscript, /etc/init.d/ofono not found.
Running in chroot, ignoring request.
invoke-rc.d: policy-rc.d denied execution of start.
And happily continues.
On version 1.28, however:
invoke-rc.d: unknown initscript, /etc/init.d/ofono not fo
*** This bug is a duplicate of bug 1539634 ***
https://bugs.launchpad.net/bugs/1539634
Also I had the problem.
Got a working wired network using the suggestion in comment #27
and than updated NetworkManarger to proposed version 0.9.8.8-0ubuntu7.3 via
synaptic
no downgrade of libnl.
Solved
Thanks, looks like that was added upstream in 3.18 or trusty has 3.12,
closing as fixed. Unsure that's something that qualifies for a SRU but
you can follow https://wiki.ubuntu.com/StableReleaseUpdates if you think
it should
** Changed in: iproute2 (Ubuntu)
Importance: Undecided => Low
** Chan
https://bugs.launchpad.net/ubuntu/+source/iproute2/4.3.0-1ubuntu1
** Changed in: iproute2 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.ne
Brian
One of those tests is notoriously racy (so not a regression per say) -
you can see that the same test passed on the next run - as this is on
armhf, which is not a core target for OpenStack, I'd like not to hold
back the release of this SRU into Wily.
Bryan - for the UCA I've moved all of th
Public bug reported:
Dovecot errors in log:
Feb 8 10:25:26 tesla dovecot: imap(u...@example.com): Error:
chdir(/home/vmail/example.com/user) failed: No such file or directory
Feb 8 10:25:26 tesla dovecot: imap(u...@example.com): Debug: Effective
uid=5000, gid=5000, home=/home/vmail/example.com
I downloaded the current amd64 cloud image and dissected it with kpartx,
i. e. without booting. /usr/share/zoneinfo/Zulu is correct there, i. e.
127 bytes. So indeed it sounds like this file gets overwritten by cloud-
init.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
Y
I think the bug is here in cloudinit/distros/__init__.py:
def set_etc_timezone(tz, tz_file=None, tz_conf="/etc/timezone",
tz_local="/etc/localtime"):
util.write_file(tz_conf, str(tz).rstrip() + "\n")
# This ensures that the correct tz will be used for the system
if
Public bug reported:
ADT runs use cloud-images to create test VM environments. For the Xenial
cloud-images I observed a weird issue where libvirt suddenly fails its
build-time tests on a time offset test on UTC.
Looking at the prepared image (cloud-init did already run there), I found that
inde
The nbd implementation in qemu is not related to the nbd package;
reassigning
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: qemu (Ubuntu)
** Package changed: nbd (Ubuntu) => qemu (Ubuntu)
--
You received this bug notification because you are a
Public bug reported:
Since version 2.0.0beta, lxc-destroy is now verbose even when calling
with --quiet:
$ sudo lxc-clone -o adt-xenial -n foo
$ sudo lxc-destroy --quiet -n foo
Destroyed container foo
Not a biggie, but it broke some expectation in autopkgtest. I'll work
around it there, but thi
86 matches
Mail list logo
