Closing this out as crufty. If this is seen again, please reopen.
** Changed in: openssh (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1422919
Title:
[SRU] Ephemeral device on G5
This was fix released a long time ago. Resolving
** Also affects: walinuxagent (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-ubuntu-server
** Changed in: walinuxagent (Ubuntu)
Importance: Undecided => Medium
** Changed in: walinuxagent (Ubuntu)
Note that the attached debdiff only fixes 2 of the 3 issues:
- libecap2 dependency
- logical-not-parentheses warning
Still pending:
- headers mismatch
** Patch added: "debdiff to fix libecap dependency and logical-not-parentheses
warning"
--- Comment From cha...@us.ibm.com 2015-09-16 01:07 EDT---
I can see the multipath choices on the installation menu and able to install
the rootvg on one of the multipath disk using SAN storages. System boots up
normal after all.
--
You received this bug notification because you are a
Public bug reported:
Note: currently squid3 fails due to libecap3-dev dependency, this is
easily fixed by going back to libecap2-dev (only squid 3.5+ will build
with libecap3-dev [1]).
After libecap2-dev dependency fix, squid then fails due to "logical-not-
parentheses".
g++ -DHAVE_CONFIG_H
I can confirm that the package in trusty-proposed resolves the issue for
me in a trusty vm with the default values set. I think it should be good
to go into trusty-updates.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/928990
Title:
fsck / dirty filesystem on instance is death
You have been subscribed to a public bug:
---Problem Description---
multipath-tools is lacking the settings for IBM 2810XIV storage system
Specially, the lack of queue_if_no_path is problematic on PowerVM LPM (live
partition migration) operations,
because I/O errors will trigger filesystem
I have no objection to the lxc patches, however I do have concerns that
they could cause breakages, so we need to make sure all the testcases
pass.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: juju-core/1.25
Milestone: 1.25-beta1 => 1.25-beta2
--
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
Do you have Apache or some other service set up and running on Port 80
already?
If so, disable that service (or at least stop the service) before
running `apt-get install -f` or similar to finish configuration. You
have a "cannot bind to port" error as a result of something else being
bound to
** Package changed: ubuntu => multipath-tools (Ubuntu)
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in
** Branch linked: lp:ubuntu/ntp
--
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/1481388
Title:
NTP : Use-after-free in routing socket code after dropping root
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu Vivid)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
*** This bug is a duplicate of bug 1466992 ***
https://bugs.launchpad.net/bugs/1466992
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1466992, so is being marked as such.
Problem depends on guest. Steps to reproduce on Ubuntu 14.04 64bit
server kernel 3.19.0-28-generic and qemu-kvm.
* set up a guest with virt-manager and set up a virtio ethernet interface
* install FreeBSD 10.1 64bit as guest
* set up an usable IP address on vtnet0 (FreeBSD name of virtio
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1488815
Title:
Kernel traces with
Version 0.4.9 should work on ppc64le.
Upgrading the ubuntu package 0.4.9 to that OR including:
https://github.com/python-greenlet/greenlet/commit/9ad99fb5b9db916ca81bd3f5717c67e20384f7e0
; and
https://github.com/python-greenlet/greenlet/commit/4d0c450852a2b0cf6307cf6ca53dcdeea357cd48
should
** No longer affects: openstack-manuals
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to heat in Ubuntu.
https://bugs.launchpad.net/bugs/1453160
Title:
[SRU] missing binaries in Ubuntu heat packages
To manage notifications about
** Changed in: ply (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ply in Ubuntu.
https://bugs.launchpad.net/bugs/1491620
Title:
ply 3.4-5 ftbfs with Python 3.5
To manage notifications
Hi Anders,
this crash seems to happen regularily at yours, but so far only at
yours. At least this bug report doesn't seem to contain the information
from the screen-dbg package and the two duplicates don't contain any
stacktrace at all. Any chance to get a stacktrace with the debug package
The patch fixed the problem, I just got the environment to verify it.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-greenlet in Ubuntu.
https://bugs.launchpad.net/bugs/1446974
Title:
python-greenlet coredump on
Ah, nevermind, I was able to get in before Snappy turned off SSH. So
the code path is definately not working.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1494816
Title:
On Azure, this fails:
Sep 15 16:59:19 localhost [CLOUDINIT] util.py[DEBUG]: Running command
['snappy', 'list'] with allowed return codes [0] (shell=False, ca
pture=True)
Sep 15 16:59:19 localhost [CLOUDINIT] cc_snappy.py[DEBUG]: setting enablement
of ssh to: False
Sep 15 16:59:19 localhost
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1495805
Title:
package nginx-core 1.9.3-1ubuntu1 failed to install/upgrade:
subprocess
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
Running Puppet on Ubuntu 15.04 Vivid:
$ lsb_release -d
Description:Ubuntu 15.04
$ apt-cache policy puppet-common
puppet-common:
Installed: 3.7.2-1ubuntu2
Using the bird package as an example:
$ dpkg -L bird |
Public bug reported:
Attaching rbd devices to libvirt/qemu managed instances currently fails
with:
2015-09-15 09:47:09.369+: 31908: error :
qemuMonitorJSONCheckError:381 : internal error: unable to execute QEMU
command 'device_add': Property 'virtio-blk-device.drive' can't find
value
Resolved with 2.4.0 upload.
** Changed in: swift (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to swift in Ubuntu.
https://bugs.launchpad.net/bugs/1487609
Title:
FTBFS on wily
To manage
Note that the same scenario behaves correctly under Debian jessie, with
the patched debian service provider in version 3.7.2-3:
https://bugs.debian.org/775795
Similar example on a Debian jessie system:
$ sudo lsb_release -d
Description:Debian GNU/Linux 8.2 (jessie)
** Description changed:
Attaching rbd devices to libvirt/qemu managed instances currently fails
with:
2015-09-15 09:47:09.369+: 31908: error :
qemuMonitorJSONCheckError:381 : internal error: unable to execute QEMU
command 'device_add': Property 'virtio-blk-device.drive' can't
I wonder if this is related to bug 1457957? Ryan, as you're assigned
that bug, could you take a look at this one at the same time please?
** Changed in: puppet (Ubuntu)
Assignee: (unassigned) => Ryan Harper (raharper)
--
You received this bug notification because you are a member of
Is this related to bug 1495853?
--
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/1457957
Title:
puppet uses upstart for service status checks in vivid
To manage notifications about
** Summary changed:
- puppet service enable broken on ubuntu vivid for services shipping sysvinit
and systemd support
+ puppet service enable broken on ubuntu vivid with debian provider
** Description changed:
Running Puppet on Ubuntu 15.04 Vivid:
- $ lsb_release -d
-
python-txtftp's logging is generally too verbose. It's useful in some
situations, but more often we just want it to be quiet, or at least
allow us to redirect its logs elsewhere.
** Also affects: python-tx-tftp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: python-tx-tftp
Reviewed: https://review.openstack.org/223292
Committed:
https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=cdcfa92b8e9604b82c7c3f8aca6fb3776df56552
Submitter: Jenkins
Branch:kilo
commit cdcfa92b8e9604b82c7c3f8aca6fb3776df56552
Author: Matthew Kassawara
The attachment "qemu_system_common_depend_on_qemu_block_extra.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
Have qemu-system-common and qemu-utils depend on qemu-block-extra
otherwise the packaging change changes expected behavior; namely before
the packaging change users could install qemu-system-x86 (and others
arches) and expect to use curl or rbd as a qemu block backend. After
the packaging change
no, since you've provided the information it should be reset to New,
thanks :)
status: new
** Changed in: qemu (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
You have been subscribed to a public bug by Robie Basak (racb):
In Ubuntu 12.04 with:
# dpkg -l |egrep "pacemaker|corosync"
ii corosync 1.4.2-2ubuntu0.2
Standards-based cluster framework (daemon and modules)
ii pacemaker
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 1495529
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
The original source of this bug is incorrect configuration of the
'architecture' property in a glance image; if the standard Ubuntu/Debian
architecture names are used, then they don't match the architecture that
nova-compute/libvirt detect on the hypervisors, and instances can't be
scheduled
Nice workaround Stefan. At least I can go on now.
root@file01:~# dpkg -i iscsitarget-dkms_1.4.20.3+svn499-0ubuntu2.1_all.deb
(Reading database ... 101359 files and directories currently installed.)
Preparing to unpack iscsitarget-dkms_1.4.20.3+svn499-0ubuntu2.1_all.deb ...
Can someone please describe what work needs doing against the mongodb
task here, please? And is the juju-mongodb package relevant here? If you
need a newer version, which version do you need exactly?
It might be worth updating the bug description to describe the current
plans to fix this bug, as
** Also affects: simplestreams
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1483159
Title:
Canonical naming for non-x86 architectures
To
Thx for ACK'ing!
It's not happening in 15.10 as reported in
https://github.com/drwetter/testssl.sh/issues/134.
I filed this bug with Debian too (not visible yet). Due to limited time
however I won't be able to check whether it's in the vanilla sources or
someplace else, sorry!
--
You
** Changed in: fuel
Assignee: Registry Administrators (registry) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1316812
Title:
ubuntu qemu-kvm package
** Bug watch added: Debian Bug tracker #795315
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795315
** Also affects: ntp (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795315
Importance: Unknown
Status: Unknown
** Bug watch added: bugs.ntp.org/ #2224
** Changed in: python-glanceclient
Status: Fix Committed => Fix Released
** Changed in: python-glanceclient
Milestone: None => 1.1.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to requests in Ubuntu.
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu. Specifically you appear to have deleted bind9 configuration
files on your system, so the bind9 service cannot be expected to work.
You can find pointers to get help for this sort of problem
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Ubuntu does not ship libmysqlclient18 version 5.7.5-m15-1ubuntu14.04, so
it seems to me that this is not a bug in Ubuntu. Instead you should
report this bug with the party that provided that package to you.
Since
>From log:
Configurando sa-compile (3.4.0-3ubuntu2.1) ...
Running sa-compile (may take a long time)
Can't exec "rm": No existe el archivo o el directorio at /usr/bin/sa-compile
line 374, <$fh> line 1.
make: chmod: No se encontró el programa
make: ***
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I appreciate the quality of this bug report and I'm sure
it'll be helpful to others experiencing the same issue.
This sounds like an upstream bug to me. Please can you verify this by
building directly from the
Importance -> Low since I presume that "the environment variable
OPENSSL_CONF is defined in a certain way" applies to only a minority of
users.
** Changed in: bind9 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server Team,
You have been subscribed to a public bug by Robie Basak (racb):
On a new installation of Ubuntu 14.04.3 LTS I installed HAProxy 1.5 from
trusty-backports (1.5.4-1ubuntu2.1~ubuntu14.04.1).
When I restarted HAProxy, I got random HTTP 503 although the backend
servers were all working fine. By
Public bug reported:
In the file /etc/default/grub.d/xen.cfg, a bogus syntax is given as
example for dom0_mem=.
A proper example would be: "dom0_mem=[M],max:[M]"
The syntax is described in those two files in the xen sources:
- xen/arch/x86/domain_build.c
- docs/misc/xen-command-line.markdown
Okay, culprit found:
=== modified file 'cloudinit/config/cc_snappy.py'
--- cloudinit/config/cc_snappy.py 2015-09-11 20:52:26 +
+++ cloudinit/config/cc_snappy.py 2015-09-15 17:52:52 +
@@ -63,7 +63,7 @@
BUILTIN_CFG = {
'packages': [],
'packages_dir':
Public bug reported:
Right now the dep-8 test checks whether the daemon can be started.
Practically the daemon can even without the dkms kernel module
available, though it makes not that much sense as for being useful this
is also required. The module is already build but the outcome of that
** Also affects: trusty-backports
Importance: Undecided
Status: New
** Also affects: vivid-backports
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
Try this one. Note I omitted the Author tag. It's not clear to me that
it's intended to name the author of the upstream patch, which in any
case is available in the upstream bug, the upstream commit, and the
debian/changelog entry. I myself have no authorship stake in this
patch.
Note that
** Changed in: openhpi (Ubuntu)
Assignee: Jon Grimm (jgrimm) => (unassigned)
--
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/1488453
Title:
Package postinst always fail on first
** Changed in: corosync (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
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/1434684
Title:
Pacemaker is not started
** Changed in: openhpi (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
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/1488453
Title:
Package postinst always fail on first
** Changed in: haproxy (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
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:
HAProxy 1.5 init script
** Description changed:
Like described in #53420 [1] there is a bug in Apache 2.4.x which is
fixed in 2.4.11.
This bug leads to slow 404 responses when ProxyErrorOverride is
activated.
When setting ProxyErrorOverride to "On" to get the httpd-ErrorDocument
** Branch linked: lp:ubuntu/cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1493453
Title:
vendor_data isn't parsed properly when using the nocloud datasource
To
** Branch linked: lp:ubuntu/cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1494816
Title:
Snappy should enable SSH when credentials are provided
To manage
Public bug reported:
Like described in #53420 [1] there is a bug in Apache 2.4.x which is
fixed in 2.4.11.
This bug leads to slow 404 responses when ProxyErrorOverride is
activated.
When setting ProxyErrorOverride to "On" to get the httpd-ErrorDocument
instead of the
Looks like the rbd driver has been broken out into a separate package[1]
qemu-block-extra
If you install that does that fix your issue?
1. qemu (1:2.2+dfsg-6exp) unstable; urgency=medium
Since Debian release 2.2+dfsg-6exp, a new package named qemu-block-extra
has been created and some
Public bug reported:
[Availability]
Universe
[Rationale]
New dependency for ceilometer
[Security]
No security history
[Quality assurance]
Package builds ok, unit tests executed
[Dependencies]
All in main
[Standards compliance]
OK
[Maintenance]
ubuntu-server/ubuntu-openstack
** Affects:
https://review.openstack.org/#/c/211041/
** Changed in: nova (Ubuntu)
Status: Confirmed => Triaged
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
** Changed in: nova (Ubuntu)
Milestone: None => ubuntu-15.09
--
You received this bug notification
It sounds like this is either an upstream bug in either libedit or PHP's
libedit support, or is behaviour by design that is causing an unintended
interaction with bash completion. This should be sent upstream to reach
a resolution; I don't see that any action can be taken in Ubuntu to fix
it.
**
>From log:
Configurando spamassassin (3.4.0-6) ...
Aviso: El directorio personal /var/lib/spamassassin que especificó ya existe.
Añadiendo el usuario del sistema `debian-spamd' (UID 121) ...
Añadiendo un nuevo usuario `debian-spamd' (UID 121) con grupo `debian-spamd' ...
useradd: existing lock
** Branch linked: lp:~james-page/simplestreams/full-arch-support
** Changed in: simplestreams
Status: New => In Progress
** Changed in: simplestreams
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Server
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
This is simply user error - OpenStack has a documented list of required
architecture values
http://docs.openstack.org/cli-reference/content/chapter_cli-glance-
property.html
Nova should not have to apply workarounds for every possible way the
user can specify incorrect architecture names.
--
Looks like this all got synced. Marking as fix released.
** Changed in: plexus-compiler (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: maven-compiler-plugin (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: antlr3 (Ubuntu)
Status: Incomplete => Fix
Daniel,
Your suggestion that openstack should not be in charge of "fixing" strings does
make sense, but it should at least be configurable to reject invalid strings
for well known properties. That way the user fails the upload (or the property
set) rather than arbitrary failure further down
we're definitely missing librbd linking in wily which was present
before. Looking at the build scripts, it it appears for linux-amd64 we
emit the enable-rbd, so the next question is why we didn't actually
compile and link against it.
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Branch linked: lp:simplestreams
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1483159
Title:
Canonical naming for non-x86 architectures
To manage notifications about this bug go
Thanks for the debdiff. The patch looks good, but could you please add
proper DEP-3 patch tags, including the Origin tag?
For example:
Description: xxx
Origin: upstream, https://svn.apache.org/viewvc?view=revision=1594625
Author: xxx
See the following for more information:
This bug was fixed in the package ntp - 1:4.2.6.p5+dfsg-3ubuntu7
---
ntp (1:4.2.6.p5+dfsg-3ubuntu7) wily; urgency=medium
* Fix use-after-free in routing socket code (LP: #1481388)
- debian/patches/use-after-free-in-routing-socket.patch
fix logic in ntpd/ntp_io.c
* Fix
Wesley, have you gotten a chance to test the package in trusty-proposed?
--
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/1394403
Title:
RewriteRule of "^$" is broken
To manage
this looks ok.
Override component to main
python-jsonpath-rw-ext 0.1.7-1 in wily: universe/misc -> main
python-jsonpath-rw-ext 0.1.7-1 in wily amd64: universe/python/optional/100% ->
main
python-jsonpath-rw-ext 0.1.7-1 in wily arm64: universe/python/optional/100% ->
main
python-jsonpath-rw-ext
I don't think its unreasonable to map well know architecture names used
by distributions into something OpenStack understands - this is not
'every possible way' - its if the user makes and (somewhat
understandable) choice of using the Ubuntu/Debian architecture name for
their image.
--
You
ACK on the debdiffs, thanks!
I've slightly modified the whitespace in the changelog and have added
the bug number, and have uploaded it to wily, and to the other releases
for processing by the SRU team.
** Tags removed: verification-done
** Changed in: ntp (Ubuntu Wily)
Status: In
This bug was fixed in the package initramfs-tools - 0.120ubuntu4
---
initramfs-tools (0.120ubuntu4) wily; urgency=medium
* init: Mount /dev with "nosuid". Thanks "Daniel". (LP: #1450960)
-- Martin Pitt Tue, 15 Sep 2015 07:20:43
+0200
** Changed in:
91 matches
Mail list logo