Any chance of an update of uw-imap for Xenial to fix this issue?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834340
Title:
Regression for GMail after libssl upgrade with TLSv1.3
To
The issue is fixed on zesty amd64 for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652093
Title:
Fix include of my_stmt.h
To manage notifications about this bug go to:
I thought mariadb-client-lgpl was based on the same code, so maybe an
upgrade would be possible. The PPA solution is fine though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651736
Title:
Xenial
Public bug reported:
The mysql.h file has an #include directive as such:
#include
This causes an error in C programs that include "mysql.h", making the
library unusable. There's an upstream fix
(https://jira.mariadb.org/browse/CONC-143) that claims to have made it
into version 2.2.0 of the
Public bug reported:
Hi
It would be interesting to provide a Xenial backport of version 2.3.x of
the MariaDB Connector/C library. The currently provided version on
Xenial is 2.0.0 which doesn't support the non-blocking API, which became
available in 2.1.0, so there's no way to develop against it
** Description changed:
Philip Pettersson discovered a race condition in the af_packet
- implementation in the Linux kernel. A local unprivileged attacker could use
- this to cause a denial of service (system crash) or run arbitrary code with
- administrative privileges.
+ implementation in the
*** This bug is a security vulnerability ***
Public security bug reported:
Philip Pettersson discovered a race condition in the af_packet
implementation in the Linux kernel. A local unprivileged attacker could use
this to cause a denial of service (system crash) or run arbitrary code with
Public bug reported:
The ruby-qpid package was built for Ruby 1.8, which is not available in
trusty. I managed to build a version that works with 1.9 simply by
replacing ruby1.9 with just ruby in debian/control, so this should
be an easy fix.
1) The release of Ubuntu you are using, via
This package (0.9.0-0ubuntu3.6) fixes the bug for me.
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1227313
Title:
This package (0.9.0-0ubuntu3.6) fixes the bug for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227313
Title:
Error
1215391 is fixed now. This can now be pushed to raring-proposed, right?
--
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/1227313
Title:
Error parsing lxc-start apparmor profile
To
1215391 is fixed now. This can now be pushed to raring-proposed, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227313
Title:
Error parsing lxc-start apparmor profile
To manage
This package (0.9.0-0ubuntu3.5) fxies the bug for me.
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1215391
Title:
This package (0.9.0-0ubuntu3.5) fxies the bug for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215391
Title:
lxc-start
Public bug reported:
The lxc-start package reads its apparmor profile from
/proc/$PID/attr/current but does not remove the trailing newline
character. When trying to run an unconfined container, this causes
comparisons with the unconfined string in the source code to fail, and
the apparmor
Public bug reported:
The lxc-start package reads its apparmor profile from
/proc/$PID/attr/current but does not remove the trailing newline
character. When trying to run an unconfined container, this causes
comparisons with the unconfined string in the source code to fail, and
the apparmor
Just to confirm, the bug wrt the apparmor profile is indeed fixed.
--
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/1215386
Title:
lxc-start tries to change apparmor profile to
You are correct, the error I'm seeing comes from the fact that I have
this line on the container's fstab:
proc /var/lib/lxc/test/rootfs/proc proc ro,nodev,noexec,nosuid 0 0
That is, I was trying to mount /proc as read-only in the container. This
works for me in 12.04 but not in 13.04.
--
You
I tried it with /etc/apparmor.d/usr.bin.lxc-start both enabled and
disabled, and also with and without lxc.aa_profile = unconfined in the
configuration file and all tests worked fine in the four possible
combinations of those settings.
--
You received this bug notification because you are a
You are correct, the error I'm seeing comes from the fact that I have
this line on the container's fstab:
proc /var/lib/lxc/test/rootfs/proc proc ro,nodev,noexec,nosuid 0 0
That is, I was trying to mount /proc as read-only in the container. This
works for me in 12.04 but not in 13.04.
--
You
Just to confirm, the bug wrt the apparmor profile is indeed fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215386
Title:
lxc-start tries to change apparmor profile to unconfined
To manage
I tried it with /etc/apparmor.d/usr.bin.lxc-start both enabled and
disabled, and also with and without lxc.aa_profile = unconfined in the
configuration file and all tests worked fine in the four possible
combinations of those settings.
--
You received this bug notification because you are a
Hi
The issue is still not fixed with the patch. While there's no more
garbage in the buffer that stores the apparmor profile read from /proc,
that data is still terminated by a \n, (ie., the profile is returned
as, eg. unconfined\n instead of unconfined). This causes comparisons
with the
Hi
The issue is still not fixed with the patch. While there's no more
garbage in the buffer that stores the apparmor profile read from /proc,
that data is still terminated by a \n, (ie., the profile is returned
as, eg. unconfined\n instead of unconfined). This causes comparisons
with the
Public bug reported:
When starting a container that has 'lxc.aa_profile = unconfined' on its
configuration file, lxc-start fails with
lxc-start: Read-only file system - failed to change apparmor profile
to unconfined
This happens because the buffer used by lxc-start to read the process'
Public bug reported:
A container with an IPv6 address in its configuration (for example,
'lxc.network.ipv6 = 2001:db8:fedc:abcd::2/80') fails to start with the
error below.
lxc-start 1377083732.942 ERRORlxc_confile - No such file or
directory - invalid ipv6 address:
Public bug reported:
A container with an IPv6 address in its configuration (for example,
'lxc.network.ipv6 = 2001:db8:fedc:abcd::2/80') fails to start with the
error below.
lxc-start 1377083732.942 ERRORlxc_confile - No such file or
directory - invalid ipv6 address:
Public bug reported:
When starting a container that has 'lxc.aa_profile = unconfined' on its
configuration file, lxc-start fails with
lxc-start: Read-only file system - failed to change apparmor profile
to unconfined
This happens because the buffer used by lxc-start to read the process'
Public bug reported:
Binary package hint: puppet
Hello
There's a bug in Puppet 0.25.4 that breaks class-level dependency
handling when using the require function multiple times:
http://projects.puppetlabs.com/issues/3186
The fix is a one-liner:
Public bug reported:
Binary package hint: puppet
Hello
There's a bug in Puppet 0.25.4 that breaks class-level dependency
handling when using the require function multiple times:
http://projects.puppetlabs.com/issues/3186
The fix is a one-liner:
A fix has been commited to the upstream repository recently:
http://redmine.ruby-
lang.org/repositories/diff/ruby-18/configure.in?rev=28404
This shouldn't require any changes to the ./configure options, just a
rebuild of the package. It would be great if the fix could be added to
the
Importance: Undecided
Assignee: Andre Nathan (andre-digirati)
Status: In Progress
** Tags: needs-packaging
** Changed in: ubuntu
Status: New = In Progress
** Changed in: ubuntu
Assignee: (unassigned) = Andre Nathan (andre-digirati)
--
[needs-packaging] watchcatd
Nathan (andre-digirati)
Status: In Progress
** Tags: needs-packaging
** Changed in: ubuntu
Status: New = In Progress
** Changed in: ubuntu
Assignee: (unassigned) = Andre Nathan (andre-digirati)
--
[needs-packaging] libwcat
https://bugs.launchpad.net/bugs/397445
You received
will be
able to free its resources for other virtual hosts.
URL: http://oss.digirati.com.br/mod_watchcat/
License: GNU General Public License
Notes: Useful with LP: 397443 and LP: 397445.
** Affects: ubuntu
Importance: Undecided
Assignee: Andre Nathan (andre-digirati)
Status
Uploaded to REVU: http://revu.ubuntuwire.com/p/libwcat
--
[needs-packaging] libwcat
https://bugs.launchpad.net/bugs/397445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Uploaded to REVU: http://revu.ubuntuwire.com/p/libapache2-mod-watchcat
--
[needs-packaging] libapache2-mod-watchcat
https://bugs.launchpad.net/bugs/397453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Uploaded to REVU: http://revu.ubuntuwire.com/p/watchcatd
--
[needs-packaging] watchcatd
https://bugs.launchpad.net/bugs/397443
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
37 matches
Mail list logo
