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 un
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.
https://bugs.l
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 kpar
** 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 th
** 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 b
** 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 notification
** 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 notification
** 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 t
** 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:
http
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
T
** 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 bug
** 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
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 ha
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
Sta
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
T
** 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:
htt
** 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 notif
** 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:
https://bu
** 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 notifications
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 fil
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 hundred
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:
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 juju-machi
** 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 notification
** 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 to
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
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: http://pastebin.com/
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:
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:
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 r
** 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
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.
https://bugs.launchpad.net/bug
[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.
https://bugs.launchpad.net
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.
** 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 crash
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: htt
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 subscribe
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 about
** 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
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 you
** 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]
-
- [
17:00 If you're thinking in a weekish, then it'll be fine.
17:01 My answer approaches no as time goes on.
--
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/1528583
Title:
[FFe] Please u
** No longer affects: dh-php (Ubuntu)
** Summary changed:
- [MIR] php7.0
+ 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 dh-php in Ubuntu.
https://bugs.launchpad.net/bugs/1547245
Hello Sascha, or anyone else affected,
Accepted net-snmp into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/net-
snmp/5.7.2~dfsg-8.1ubuntu3.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
Requesting an FFe for this please. Lars has had a branch ready for a
while now, and we've already had one review round, but I haven't managed
to review again in time. I expect to get this uploaded in 1-3 weeks.
One complicating factor is that this will trigger a library transition
for libmysqlclie
Here's the output of installing without Recommends (and coreutils):
roaksoax@unleashed:~$ lxc exec xenial6 -- /bin/sh
# sudo apt-get install isc-dhcp-server --no-install-recommends
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional pac
Requesting a brief (1-3 week) FFe for this please. I have a merge ready,
but there is a transitional bug I want to fix. conffile renaming is
currently not working in some scenarios, which I believe also affects
Debian. It is complicated because of a migration in Debian of squid3 ->
squid which over
You have been subscribed to a public bug by Robie Basak (racb):
upgrade to MySQL 5.7.10 and above, ununtu 16.04
** Affects: mysql-5.6 (Ubuntu)
Importance: Wishlist
Assignee: Lars Tangvald (lars-tangvald)
Status: In Progress
** Tags: upgrade-software-version
--
[FFe] Please u
Downgrading to Medium, as I feel that Critical needs a justification.
** Changed in: isc-dhcp (Ubuntu)
Importance: Critical => Medium
--
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/15
Why is a component mismatch critical?
Looks like the original reason Debian added the dependency is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797276. Which confuses
me. Doesn't the guard stop it running?
Pierre proposed http://paste.ubuntu.com/15111754/ which looks fine to
me, except that
libkohana2-php only supports PHP 5.
** Also affects: libkohana2-php (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php-json in Ubuntu.
https://bugs.launchpad.net/bugs/1547183
Title
** Also affects: nova/liberty
Importance: Undecided
Status: New
** Changed in: nova/liberty
Status: New => In Progress
** Changed in: nova/liberty
Assignee: (unassigned) => Tony Breeds (o-tony)
--
You received this bug notification because you are a member of Ubuntu
Server
Hello Serge, or anyone else affected,
Accepted numactl into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/numactl/2.0.9~rc5-1ubuntu3.14.04.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. Se
Hello Serge, or anyone else affected,
Accepted numactl into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/numactl/2.0.10-1ubuntu6.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
** Changed in: numactl (Ubuntu Vivid)
Status: New => Won't Fix
** Also affects: numactl (Ubuntu Wily)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to numactl in Ubuntu.
https://bugs.la
how can we get a Fix for Wily ?
--
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/1263181
Title:
curtin discovers HP /dev/cciss/c0d0 incorrectly
To manage notifications about this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bind9 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/154705
same problem with HP DL380 G5 , latest MAAS and Curtin packages
--
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/1263181
Title:
curtin discovers HP /dev/cciss/c0d0 incorrectly
To mana
Public bug reported:
On Ubuntu Xenial, new release of libvirt-bin fails to cleanly install:
root@xenial-server-2016-01-18-ppc64el:~# apt-get install libvirt-bin
--snip--
Setting up libvirt-bin (1.3.1-1ubuntu1) ...
Adding group `libvirtd' (GID 119) ...
Done.
* Starting libvirt logging daemon virt
Public bug reported:
System information: Cisco UCS B200M2 blade, fnic.ko HBA. The system
boots from local storage, but mounts the following file system on an EMC
VNX during bootup:
opt_vnx (3600601603a71320022967e0a1f38e411) dm-0 DGC,VRAID
size=50G features='1 queue_if_no_path' hwhandler='1 emc'
We should be able to send this patches soon.
--
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/1541902
Title:
Enable DDW on qemu aiming GPU passthrough performance on Ubuntu KVM
To manag
The attachment "apparmor_2.10-3ubuntu2.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" t
Committed upstream: https://bazaar.launchpad.net/~apparmor-
dev/apparmor/master/revision/3375
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Importance: Undecided => Medium
** Changed in: apparmor
Status: New => Fix Committed
** Changed i
Thanks - do make sure to log back in after the update.
The xenial systemd would fail because there you must have libpam-cgfs
to get your own cgroups for lxc. In wily iirc that should not be
required.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Passed QRT's test-apparmor.py in an Xenial amd64 VM.
** Patch added: "apparmor_2.10-3ubuntu2.debdiff"
https://bugs.launchpad.net/apparmor/+bug/1546455/+attachment/4574878/+files/apparmor_2.10-3ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Tea
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.
https://bugs.launchpad.net/bu
After a rerun the neutron test did pass, so releasing that package.
--
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/1530913
Title:
[SRU] liberty point releases
To manage notifications
This bug was fixed in the package neutron - 2:7.0.1-0ubuntu1
---
neutron (2:7.0.1-0ubuntu1) wily; urgency=medium
[ Corey Bryant ]
* d/tests/neutron-agents: Give daemon 5 seconds to start to prevent race.
[ James Page ]
* New upstream point release (LP: #1530913).
-- James P
** Description changed:
+ =
+ SRU Justification
+ same justification as for bug 1358835. It would
+ be great to have the same test cases run as in that
+ bug.
+ =
+
In bug 1358835 we applied a fix to supres
Haha, indeed. I hadn't even looked at what runit was yet. Runit-
assumptions do unfortunately seem to be embedded into how this package
works.
** Changed in: vblade-persist (Ubuntu)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubu
** Branch linked: lp:~nacc/ubuntu-seeds/ubuntu.xenial
** Changed in: php5 (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
--
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/15
The verification of the Stable Release Update for autofs has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
Override component to main
libiscsi 1.12.0-2 in xenial: universe/net -> main
libiscsi-bin 1.12.0-2 in xenial amd64: universe/net/optional/100% -> main
libiscsi-bin 1.12.0-2 in xenial arm64: universe/net/optional/100% -> main
libiscsi-bin 1.12.0-2 in xenial armhf: universe/net/optional/100% -> main
This bug was fixed in the package autofs - 5.1.1-1ubuntu2.1
---
autofs (5.1.1-1ubuntu2.1) wily-proposed; urgency=medium
[ Malcolm Scott ]
* d/p/fix-lookup-ldap-crash.patch:
- Fix crash on startup due to uninitialized config. LP: #1503034
[ Michael Terry ]
* d/p/fix-looku
Bug # 1547183 filed - Remove php5 specific packages from the 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 this
This bug was fixed in the package ntp - 1:4.2.6.p3+dfsg-1ubuntu3.9
---
ntp (1:4.2.6.p3+dfsg-1ubuntu3.9) precise; urgency=medium
* ntpd rejects source UDP ports less than 123 as bogus (closes: #691412)
- d/p/reject-UDP-ports-less-than-123-as-bogus.patch (LP: #1479652)
-- Eric D
src:php5 will be the last removal from the archive.
** Also affects: php5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php-json in Ubuntu.
https://bugs.launchpad.net/bugs/1547183
This was systemd and kernel from xenial. I'll try again tomorrov with
the wily-proposed systemd and xenial 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/1533833
Title:
unprivi
Public bug reported:
As we migrate to PHP7, we can remove certain source packages from the
archive that only apply to PHP5.
** Affects: dh-php5 (Ubuntu)
Importance: Undecided
Status: New
** Affects: php-json (Ubuntu)
Importance: Undecided
Status: New
** Package chang
src:dh-php5 has been replaced by src:dh-php
src:php-json is now included in src:php7.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php-json in Ubuntu.
https://bugs.launchpad.net/bugs/1547183
Title:
Remove php5 specific packages f
** Changed in: libiscsi (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libiscsi in Ubuntu.
https://bugs.launchpad.net/bugs/1271653
Title:
[MIR] libiscsi
To manage notifications about thi
This is a non-deterministic failure error in the installation attempts
on the package. According to everything, nginx is currently running.
The only thing I can suggest is that you try and stop nginx first, then
try and load it again, and see if that resolves the issue... because it
appears that
** Changed in: postfix (Debian)
Status: Unknown => New
--
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/1546788
Title:
Fresh install of Postfix 3.0.3-1~build1 will not start wi
** Branch linked: lp:apparmor
--
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
Title:
Many instances of 'apparmor="DENIED" operation="create"
profile="/usr/sbin/ntpd" pid=15139
Confirmed, the epoch wasn't supposed to get bumped in precise.
** Also affects: nss (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: nss (Ubuntu Precise)
Status: New => Confirmed
** Changed in: nss (Ubuntu Precise)
Assignee: (unassigned) => Marc Deslauriers
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1547147
Title:
libnss3-dev adds epoch 2 to the Version in pkg-config's pc file
To manage notifications about this
Public bug reported:
Update 2:3.21-0ubuntu0.12.04.1 in Precise bumps the epoch of the
package.
However, nss.pc contains:
Version: 2:3.21
This breaks detection of the version.
for example, NetworkManager's configure.ac has
PKG_CHECK_MODULES(NSS, [nss >= 3.11])
With this change, it results in
To workaround this add
shlib_directory = no
to your main.cf.
** Bug watch added: Debian Bug tracker #815047
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815047
** Also affects: postfix (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815047
Importance: Unknown
S
Public bug reported:
Upwork Team App uses libnss3 for transferring files via HTTPS and it
starts getting unknown SSL error - something like being disconnected
from the network. After downgrading back to 2:3.19.2-1ubuntu1 things
work again.
** Affects: nss (Ubuntu)
Importance: Undecided
This was uploaded approximately two hours ago, and is now available in
the repositories.
The following is the changelog entry for the upload that has now marked
this as 'fix released':
nginx (1.9.11-0ubuntu1) xenial; urgency=low
* New upstream release (1.9.11) - see http://nginx.org/en/CHANGES
Public bug reported:
A new charm command is being created to accompany charm-tools 2.0 and
Juju 2.0 - this new command will install /usr/bin/charm (previously
managed by charm-tools 1.0.0 so this command will break charm-tools
1.0.0 and suggest charm-tools 2.0 (where charm-tools 2.0 will depend on
Blueprint changed by Thomas Ward:
Work items changed:
Work items for ubuntu-15.11:
[serge-hallyn] etckeeper: DONE
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
[raharper] : tgt merge (bug 1524982): DONE
[racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
[kic
--- Comment From mauri...@br.ibm.com 2016-02-18 12:07 EDT---
*** Bug 137290 has been marked as a duplicate of this bug. ***
--
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.net/bu
Blueprint changed by Jon Grimm:
Work items changed:
Work items for ubuntu-15.11:
[serge-hallyn] etckeeper: DONE
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
[raharper] : tgt merge (bug 1524982): DONE
[racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
[kick-
Oh, right, something with the pids controller enabled.
Still want to make sure he's using the right systemd version, since his
appears not to be fixed otherwise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bu
** Changed in: bind9 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1508620
Title:
Build with multiarch support
To manage notifications ab
** Changed in: postfix (Debian)
Status: New => Fix Released
--
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/1531801
Title:
Please update to upstream major release 3
To manage
Looking into this further (thanks to Marc on the Security Team), it
looks like your system is trying to use the rsax OpenSSL engine, which
is not shipped in Ubuntu.
Can you provide all your nginx configurations, please, so we can see
whether this is the case or not?
** Changed in: nginx (Ubuntu)
Serge Hallyn [2016-02-18 16:39 -]:
> Just to be sure, can you show the systemd version you were using here?
> The intent was to check with systemd from wily-proposed, with the
> regular wily kernel.
I thought the idea was to use a xenial kernel on wily?
--
You received this bug notification
1 - 100 of 142 matches
Mail list logo
