what a pity we won't have postfix 3.1 in Ubuntu 16.04 LTS ...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1561975
Title:
default configuration warnings - minor
To manage
Public bug reported:
Installed BackupPC 3.30 form repositories and ipaddress/backuppc would
not present gui. Complained "Socket6" missing. Installed
"libsocket6-perl" and accessing ipaddress/backuppc presented gui. This
package "libsocket6-perl" is missing from dependencies when installing
Public bug reported:
default configuration should match the v 2.11 -> 3.0 change:
With the default installation of Postfix 3.0.4 there are 2 warnings:
1)
Mar 25 12:45:50 mail postfix/master[4674]: /etc/postfix/master.cf: line 14:
using backwards-compatible default setting chroot=y
2) With all
** Changed in: walinuxagent (Ubuntu)
Milestone: wily-updates => ubuntu-16.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1559307
Title:
[SRU] update walinuxagent to
** Changed in: walinuxagent (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1559307
Title:
[SRU] update walinuxagent to
Importance: Critical
Assignee: Robert C Jennings (rcj)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1559307
Title:
[SRU] update walinuxagen
>From 10.0.5 to 10.0.7 the only substantive change is the addition of
'the namespace command line utility "vmware-namespace-cmd"'. The
'vmware-namespace-cmd' tool comes without documentation beyond the
cmdline usage text and I have been unable to find documentation online
for this tools on
smoser, I tested this with cloud-init
0.7.7~bzr1176+1179+441~ubuntu16.04.1 from ppa:cloud-init-dev/daily and
it added the group for the ubuntu user. I tested with and without
LX[CD] installed (installing LXD after the default user and lxd group
were created).
--
You received this bug
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
--
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/1539317
Title:
default user sho
Requesting this for 16.04 and raising priority for visibility.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Critical
** Changed in: cloud-init (Ubuntu)
Milestone: None => ubuntu-16.04
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
According to various dbus spec/docs [1][2], the "Name=" property in the
dbus service description file should be the FQDN of the app. i.e., in
usr/share/dbus-1/services/us.kirkland.terminals.byobu.service , it
should look like:
Name=us.kirkland.terminals.byobu
The current
** 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 cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1540965
Title:
Support Joyent lx-brand environment in
Oliver, we would like to keep in step with Debian. Would you mind
filing a debian bug for 10.0.7? I don't see one already. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
Public bug reported:
Description:Ubuntu 15.10
Release:15.10
mysql-server-5.6 5.6.28-0ubuntu0.15.10.1
Enabled TCP connects by changing bind-address from 127.0.0.1 to 0.0.0.0 but can
not authenticate from other hosts even
with user@% or user@%.domain in grant tables
Same grant tables
Public bug reported:
The systemd configuration for snapd to allow socket activation is in the
ubuntu-snappy package, but snapd is in the ubuntu-snappy-cli package.
This means you need install both packages to get snapd to "just work".
It seems like the systemd configuration should move into the
New trusty.debdiff based on feedback from Ben. I have cleaned up the
changelog (version and path to patch), fixed the diff to have the
correct from address, and changed dmi_data() to call
util.read_dmi_data() rather than use a local implementation of that util
function.
** Patch added:
New trusty.debdiff based on feedback from Ben. I have cleaned up the
changelog (version and path to patch), fixed the diff to have the
correct from address, and changed dmi_data() to call
util.read_dmi_data() rather than use a local implementation of that util
function.
** Patch added:
New wily.debdiff based on feedback from Ben. I have cleaned up the
changelog (version and path to patch).
** Patch added: "wily.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564782/+files/wily.debdiff
** Patch removed: "wily.debdiff"
I am going to delete the patches and post them again. I need to update
them from the final patch that was merged upstream. They were here
prematurely.
** Patch removed: "trusty.debdiff"
SRU templated added and ready for upload/sponsorship.
Scott, can you ack the upload?
Ben, can you sponsor this?
Thanks.
** Description changed:
+ [Impact]
+
+ * Cloud-init does not support the datasource presented to LX-Brand
+zones in SmartOS. Without this support cloud-init does not
Replacement patch for trusty attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Ftrusty%2Fsdc-lxbrand
I didn't need to delete this one earlier, but I did.
** Patch added: "trusty.debdiff"
The code was accepted upstream and published for Xenial in cloud-init
0.7.7~bzr1160-0ubuntu1 .
--
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/1540965
Title:
Support Joyent
Replacement patch for wily attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fwily%2Fsdc-lxbrand
Fixed python 2 testing w.r.t. strings/bytes.
** Patch added: "wily.debdiff"
Patch for trusty attached, branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Ftrusty%2Fsdc-lxbrand
** Patch added: "trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563911/+files/trusty.debdiff
--
You received this
SmartOS: Add support for Joyent LX-Brand Zones
LX-brand zones on Joyent's SmartOS use a different metadata source
(socket file) than the KVM-based SmartOS virtualization (serial port).
This patch adds support for recognizing the different flavors of
virtualization on SmartOS and setting up a
Patch for vivid attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fvivid%2Fsdc-lxbrand
** Patch added: "vivid.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563912/+files/vivid.debdiff
--
You received this
Patch for xenial attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fmaster%2Fsdc-lxbrand
** Patch added: "xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563914/+files/xenial.debdiff
--
You received
Patch for wily attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fwily%2Fsdc-lxbrand
** Patch added: "wily.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563913/+files/wily.debdiff
--
You received this bug
Assigning to Scott for patch review. I will update the description with
SRU template.
** Changed in: cloud-init (Ubuntu)
Assignee: Robert C Jennings (rcj) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
** Branch linked: lp:~rcj/cloud-init/lp1540965
--
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/1540965
Title:
Support Joyent lx-brand environment in smartos datasource
To manage
Patch for vivid attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fvivid%2Fsdc-lxbrand
** Patch removed: "vivid.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563912/+files/vivid.debdiff
** Patch added:
Replacement patch for xenial attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fmaster%2Fsdc-lxbrand
Dropped changes to test-requirements.txt
** Patch added: "xenial.debdiff"
Replacement patch for wily attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fwily%2Fsdc-lxbrand
Dropped changes to test-requirements.txt
** Patch added: "wily.debdiff"
are in a Joyent LX-brand zone is possible by looking at
'/bin/uname -v' which will report "BrandZ virtual linux" or checking for the
existence of a /native mount where '/native/usr/bin/uname -s' reports
SunOS.
** Affects: cloud-init (Ubuntu)
Importance: High
Assignee: Robert
Public bug reported:
According to the manual page, restarting libvirtd is not supposed
to interrupt running virtual machines, but it does. Thus when an
upgrade to libvirtd comes out on the host machines, if I apply it, it
frequently restarts the guest machines which is unpopular with
Public bug reported:
This is what happens if you run juju without python-novaclient
installed:
$ juju bootstrap
Bootstrap failed, cleaning up the environment.
ERROR there was an issue examining the environment: authentication failed.
Please ensure the credentials are correct. A common mistake
** Branch linked: lp:~returntoreptar/curtin/removable-drive-fixes
--
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
Public bug reported:
When starting Ubuntu a series of pop-up messages with:
"Sorry, Ubuntu 14.04 has experienced an internal error."
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libnss3 2:3.19.2.1-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic
Sure no problem! I have attached the output of sudo lshw as a file,
since it was a bit long.
** Attachment added: "Output of lshw on system with "removable" drives."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1532062/+attachment/4548195/+files/lshw-output-anakin
--
You received
Public bug reported:
I uninstalled the old vmware tools and did `sudo apt-get install open-
vm-tools`. After a reboot, `modprobe vmhgfs` fails with `modprobe:
FATAL: Module vmhgfs not found.`. Mounting also fails: `mount -t vmhgfs
.host:/ /mnt/hgfs/` fails with `Error: cannot mount filesystem: No
** Changed in: open-vm-tools (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1500581
Title:
open-vm-tools-dkms fails to build
Fixed changelog mistake in commit
3595280d8803319f71b53a22e39c386fab1577bf of the tree.
The changelog in the merge of 9.10.3-3167576 accidentally dropped
history and pulled in content from a dead development branch. This
patch fixes the changelog to reflect actual changes.
--
You received this
While bug #1482777 is being worked ([MIR] open-vm-tools 9.10.2 build
dependencies: xml-security-c and xerces-c) we will build 10.0 without
SAML-based guest authentication.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Merging upstream 9.10.3-3167576:
https://git.launchpad.net/~rcj/ubuntu/+source/open-vm-tools/commit/?id=641279a0debd198005d53de8e494a09207e2f16a
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
Package @ ppa:rcj/open-vm-tools
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1500581
Title:
open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf)
[error:
Merge from Debian 2:10.0.0-3000743-3-ubuntu-1:
https://git.launchpad.net/~rcj/ubuntu/+source/open-vm-tools/commit/?id=769eeb593ce62eec332f13db653785429a942f39
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Package @ ppa:rcj/open-vm-tools
--
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/1492429
Title:
please update open-vm-tools to version 10.0.0
To manage notifications about this bug go
** Changed in: lightdm/1.14
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1478087
Title:
Add libaudit support
To manage notifications
** Changed in: lightdm
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1478087
Title:
Add libaudit support
To manage notifications
For me in 12.04 this worked:
Adding the PPA - https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-stable
--
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/1504781
Title:
lxc-test-ubuntu
We will sync 10.0.0 for xenial
--
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/1492429
Title:
please update open-vm-tools to version 10.0.0
To manage notifications about this bug go
Debian has moved to 10.0.0. Ubuntu will update 9.10.2 to 9.10.3 for
Wily and pull in 10.0.0 for Xenial.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1500581
Title:
I agree that this shuffling around is not pretty, but we need a solution
that makes 10.0.0.0/16 routable in cloud images where lxc/lxd are not in
use as had prior to http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/ubuntu.wily/revision/2360
The current situation conflicts with how
Séphane,
When this was added to the cloud seed we changed this from "users that
install LXC will loose connectivity to a 10.0.x.0/24 network" to "all
cloud users do not have connectivity to a 10.0.x.0/24 network at boot"
and the cause/effect will not be as clear to an end user. This had come
up
Cloud images build from proposed are available.
Next action:
--
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/1509414
Title:
pre-installed lxc in cloud image produces broken lxc (and
Cloud image downloads for amd64, i386, and ppc64el are available @ http
://cloud-images.ubuntu.com/proposed/wily/20151024/
The amd64 image is also available in canonistack lcy02 region as
lp1509414/wily-proposed
--
You received this bug notification because you are a member of Ubuntu
Server
Be aware in your testing that the lxd-net's service can come up slowly
depending on the speed of your cloud instance. Without the bridge
(lxcbr0) the container's networking will function prior to that service
starting; watch out for this false positive in your testing.
--
You received this bug
Cloud images build from proposed are available.
Next action:
- Verification of proposed package.
--
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/1509414
Title:
pre-installed lxc in
My testing with the cloud image containing the proposed package has been
successful.
Just a note again that the test case detailed in the description is fine
with the understanding that network testing needs to ensure the lxc-net
service has started lxcbr0 or a false positive is possible (per
The cloud-image builder picked up the change and is building images.
They are with the LP buildds now. I will update this bug once
publication completes.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Action plan:
Stage 1 - Configure lxc-net at boot rather than at install.
* This addresses the network failure for 15.10 containers started on 15.10
hosts (patch above in comment #6)
Stage 2 - Start lxc-net through systemd on the first launch of an LXC container.
* This mitigates the unroutable
*** This bug is a duplicate of bug 1500581 ***
https://bugs.launchpad.net/bugs/1500581
** Bug watch added: Debian Bug tracker #800322
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800322
** Also affects: open-vm-tools (Debian) via
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: open-vm-tools (Ubuntu)
Milestone: None => wily-updates
** Patch removed: "0001-vmhgfs-support-linux-4.2.x-kernel.patch"
https://bugs.launchpad.net/ubuntu/+source/op
I have removed the patch from comment #4. Running with the vmhgfs
driver from the 9.10.2 code can result in data corruption. The backport
of the driver from 10.0.0 to 9.10.3 resolves the data corruption issue
as well as addressing the kernel compilation failures for 4.1 and 4.2
kernels.
As
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: open-vm-tools (Ubuntu)
Milestone: None => ubuntu-16.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug
Public bug reported:
Build with multiarch support
** Affects: libvirt (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: multiarch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Public bug reported:
Build with multiarch support
** Affects: bind9 (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: multiarch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Public bug reported:
Build with multiarch support
** Affects: netcf (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: multiarch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
Public bug reported:
Build with multiarch support
** Affects: libecap (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: multiarch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libecap in Ubuntu.
** Summary changed:
- ISST-LTE: aureport -l couldn't print out login info on ubuntu 14.04.3
+ Add libaudit support
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1478087
Title:
** Bug watch added: Debian Bug tracker #800322
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800322
** Also affects: open-vm-tools (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800322
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Changed in: lightdm/1.16
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1478087
Title:
ISST-LTE: aureport -l couldn't print out
** Changed in: lightdm/1.10
Importance: Undecided => Medium
** Changed in: lightdm/1.10
Status: New => Triaged
** Changed in: lightdm/1.10
Milestone: None => 1.10.6
** Changed in: lightdm/1.10
Status: Triaged => Fix Committed
** Changed in: lightdm/1.14
Importance:
** Also affects: lightdm
Importance: Undecided
Status: New
** Also affects: lightdm/1.10
Importance: Undecided
Status: New
** Also affects: lightdm/1.2
Importance: Undecided
Status: New
** Also affects: lightdm/1.14
Importance: Undecided
Status: New
**
Robie, can you review the patch in comment #10 for this fix? Thanks.
--
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/1406105
Title:
Broken logrotate script in
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
** Changed in: cloud-init (Ubuntu)
Assignee: Robert C Jennings (rcj) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https
Had the same problem, boot did hang for approximately 100s, bootchart
etc... showed interesting processes like hostname hanging.
Replacing libnss-ldap with libnss-ldapd finally fixed the problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Compaq 510, Ubuntu 15.04, Tried to install/reinstall
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: spamassassin 3.4.0-6
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.3
To add clarity, the debconf proposal in comment #5 is the long-term
solution. In the interim, the workaround in comment #4 to remove the
ucf registry entry is needed. For existing users, this will need to be
done by hand. For future cloud images the ufc entry will be removed
(in the short-term)
Marking as won't fix due to hardy EOL.
** Changed in: freeradius (Ubuntu)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in Ubuntu.
https://bugs.launchpad.net/bugs/315896
Title:
Updated the patch. The post-install scripts will restart the daemon so
that an upgrade will restart the daemon so that future reloads do work.
This addresses the 3rd scenario in comment #7. There would be no
regression for users on upgrade. If the service has been reloaded prior
to the upgrade
** Changed in: freeradius (Ubuntu Vivid)
Status: New = Invalid
--
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/1406105
Title:
Broken logrotate script in
Trusty)
Assignee: (unassigned) = Robert C Jennings (rcj)
--
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/1406105
Title:
Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8
** Description changed:
+ [Impact]
+
+ * freeradius can not be reloaded, upstart will lose track of the
+ process and leave the original process running (blocking future service
+ starts)
+
+ * log rotation will not function as intended. The service is not
+ reloaded and the file handles for
Back to the prior patch to reduce scope by removing changes for 'init.d'
- 'service' for force-reload operations in postinst scripts if invoke-
rc.d is not available. This is not changed as we can assume invoke-rc.d
is installed and the SRU change needs to be minimal.
** Patch added:
)
Assignee: (unassigned) = Robert C Jennings (rcj)
--
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/1406105
Title:
Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu
14.04
. Then change logrotate script in trusty to call 'service freeradius
reload' and consider removing the redirect to /dev/null.
I have run out of time today but have left these notes so that we can
pursue it further.
** Changed in: freeradius (Ubuntu)
Assignee: Robert C Jennings (rcj) = (unassigned
** Changed in: freeradius (Ubuntu)
Assignee: (unassigned) = Robert C Jennings (rcj)
--
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/1406105
Title:
Broken logrotate script
Robie / Chris,
Can you review comment #6 for the proposed patch and upgrade
issue/strategy?
The upstart config for freeradius is bad; reload(8) or restart(8) will
lose track of the process. A reload won't send SIGHUP to the right
process and a restart(8) will not stop the existing freeradius
** Changed in: subunit
Importance: High = Wishlist
** Summary changed:
- Test failures if subunit module is installed
+ Test failures if tests are run from an installed copy of subunit
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
*** This bug is a duplicate of bug 1369294 ***
https://bugs.launchpad.net/bugs/1369294
** This bug is no longer a duplicate of bug 1426994
openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module
failed to build [configure: error: Linux kernel in
*** This bug is a duplicate of bug 1369294 ***
https://bugs.launchpad.net/bugs/1369294
** This bug is no longer a duplicate of bug 1426994
openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module
failed to build [configure: error: Linux kernel in
*** This bug is a duplicate of bug 1369294 ***
https://bugs.launchpad.net/bugs/1369294
** This bug is no longer a duplicate of bug 1426994
openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module
failed to build [configure: error: Linux kernel in
*** This bug is a duplicate of bug 1369294 ***
https://bugs.launchpad.net/bugs/1369294
** This bug is no longer a duplicate of bug 1426994
openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module
failed to build [configure: error: Linux kernel in
*** This bug is a duplicate of bug 1369294 ***
https://bugs.launchpad.net/bugs/1369294
** This bug has been marked a duplicate of bug 1369294
openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module
failed to build [configure: error: Linux kernel in
I am currently affected by https://wiki.strongswan.org/issues/547 which
should be fixed in 5.1.3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to strongswan in Ubuntu.
https://bugs.launchpad.net/bugs/1330504
Title:
strongSwan 5.1.3
Public bug reported:
Debian wheezy-backports and Debian jessie contain upstream version 5.2.1
of strongswan. Please make that available on Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: strongswan (not installed)
ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
Test case #3 completed for Trusty.
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1442392
Title:
[SRU][FFE] update walinuxagent to
Verification of proposed walinuxagent completed on Utopic. Tests
passed.
** Tags removed: verification-done-trusty
** Tags added: verification-done
** Changed in: walinuxagent (Ubuntu Utopic)
Assignee: (unassigned) = Robert C Jennings (rcj)
** Changed in: walinuxagent (Ubuntu Trusty
Test cases #1 and #2 completed successfully for Trusty. Building
proposed image now and will test when available.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1442392
Title:
1 - 100 of 515 matches
Mail list logo
