This was fixed by smoser and pushed to trunk.
Here is a diff if you're interested: https://pastebin.canonical.com/99718/
--
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/1159818
Title:
Public bug reported:
I had to do some source code changes to be able to run Horizon on trusty.
Here is a list of change in a form of error message followed by solution.
Can we update the package to be able to run it just from the box?
Public bug reported:
While trying to run openstack-nova/libvirt on arm64 machine we got the
following error:
libvirtd.log
2014-04-02 16:08:11.140+: 1227: error : qemuProcessWaitForMonitor:1915 :
internal error: process exited while connecting to monitor: libvirt: error :
cannot execute
Public bug reported:
ubuntu@mw01-02:~$ juju --version
1.18.1-trusty-armhf
ubuntu@mw01-02:~$ uname -a
Linux mw01-02 3.13.0-24-generic-lpae #46-Ubuntu SMP Thu Apr 10 21:01:14 UTC
2014 armv7l armv7l armv7l GNU/Linux
ubuntu@mw01-02:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
Public bug reported:
ubuntu@mw01-02:~$ juju --version
1.18.1-trusty-armhf
ubuntu@mw01-02:~$ uname -a
Linux mw01-02 3.13.0-24-generic-lpae #46-Ubuntu SMP Thu Apr 10 21:01:14 UTC
2014 armv7l armv7l armv7l GNU/Linux
ubuntu@mw01-02:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
** Description changed:
+ ubuntu@mw01-02:~$ juju --version
+ 1.18.1-trusty-armhf
+
ubuntu@mw01-02:~$ uname -a
Linux mw01-02 3.13.0-24-generic-lpae #46-Ubuntu SMP Thu Apr 10 21:01:14 UTC
2014 armv7l armv7l armv7l GNU/Linux
- ubuntu@mw01-02:~$ cat /etc/lsb-release
+ ubuntu@mw01-02:~$ cat
Public bug reported:
I'm trying to use LXC on my openstack instance which runs vivid daily:
$ sudo apt-get install lxc -y
$ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache
--stream=daily --release=vivid
$ sudo lxc-start --name vivid --logfile=lxc.log
lxc-start: lxc_start.c: main:
Hi Serge,
Many thanks for looking at the bug.
Here is information you requested.
ubuntu@vivid-lxc-bug:~$ uname -a
Linux vivid-lxc-bug 3.19.0-9-generic #9-Ubuntu SMP Wed Mar 11 17:50:03 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@vivid-lxc-bug:~$ sudo aa-status
apparmor module is loaded.
6
It seems that this bug consists of many partially independent bugs.
I found at least two:
(1)
openjdk in vivid has SSLv3 disable but tests try to use it and get 'protocol is
disabled or cipher suites are inappropriate'
as a warkaround you may enable sslv3 back by commenting the following line in
They have updated certs in trunk:
http://mail-archives.apache.org/mod_mbox/tomcat-dev/201502.mbox/%3c20150228182330.eaaabac0...@hades.apache.org%3E
We may just pick them up.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug
Some part of bugs disappear when I put updated certs (with expiration date in
2017) from here:
https://github.com/apache/tomcat/test/org/apache/tomcat/util/net/{localhost-cert.pem,
localhost-copy1.jks, localhost.jks, localhost-key.pem}
--
You received this bug notification because you are a
** Changed in: tomcat7 (Ubuntu Vivid)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1432715
Title:
tomcat7 ftbfs in vivd (test failures)
To
Shell script which reproduces the issue: http://pastebin.ubuntu.com/10712595/
Please run this script only on a disposable instance in the cloud because it
creates and adds ultimately trusted certificate to the target machine.
I was able to reproduce the issue on precise (12.04) and trusty
** Changed in: openldap (Ubuntu Precise)
Status: New = In Progress
** Changed in: openldap (Ubuntu Trusty)
Status: New = In Progress
** Changed in: openldap (Ubuntu Precise)
Assignee: (unassigned) = Oleg Strikov (strikov)
** Changed in: openldap (Ubuntu Trusty)
Assignee
/mysql.service
After running this command you (theoretically) should be able to purge and
install the package w/o any issue.
Please let us now if it helps you or not.
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) = Oleg Strikov (strikov)
--
You received this bug notification because
Hi Jacek,
Thanks for reporting the bug and providing us with the fix.
I prepared a debdiff (attached) and will be looking for sponsorship.
** Patch added: lp-1416039.debdiff
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1416039/+attachment/4333549/+files/lp-1416039.debdiff
--
You
** Changed in: squid3 (Ubuntu)
Assignee: (unassigned) = Oleg Strikov (strikov)
--
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/1416039
Title:
Broken apparmor profile
To manage
Thanks for pointing that.
Done.
** Patch added: lp-1424508-proposed-1.debdiff
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+attachment/4335313/+files/lp-1424508-proposed-1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I prepared a debdiff for vivid (attached) and currently looking for sponsorship.
My repro case can be found here: http://pastebin.ubuntu.com/10527246/
** Patch added: lp-1336742-vivid.debdiff
I prepared debdiff for vivid-release (attached) and currently looking
for sponsorship.
** Patch added: lp-1424508-released.debdiff
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+attachment/4335137/+files/lp-1424508-released.debdiff
--
You received this bug notification
I prepared debdiff for vivid-proposed (attached) and currently looking
for sponsorship.
** Patch added: lp-1424508-proposed.debdiff
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+attachment/4335136/+files/lp-1424508-proposed.debdiff
--
You received this bug notification
Updated package has been pushed to vivid-proposed.
Feel free to try it.
--
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/1336742
Title:
Caching responses with Vary header
To manage
My reprocase can be found here: http://paste.ubuntu.com/10538557/
--
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/1424508
Title:
upstartism in the maintainer script
To manage
Public bug reported:
We're now in a position to have 1.23.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general production
Verification done. Logs: http://pastebin.ubuntu.com/10880409/
** 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 the bug report.
Debdiff attached.
[SRU]
[Impact]
Bug shows up when user tries to upgrade any previous version of clamav
to the version which is currently available inside vivid repo. Apt
crashes with the following error message:
/var/lib/dpkg/info/clamav-daemon.postinst: 626:
Thanks Curtis! Adding 'verification-done' tag based on your comments.
** 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 juju-core in Ubuntu.
There was a typo in the message #8 from Curtis. Juju 1.22.1 has been certified
not 1.20.1.
sinzui strikov, oops, yes, I do mean *1.22.1*
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Hi Curtis,
To my understanding juju-1.22.1 is not in -updates yet not because we
don't want this but because it needs to be in -proposed for 7 days
before reaching -updates. This is a standard practice for SRUs. I expect
to see it landed into -updates until the end of this week. If juju team
Execution of blockdev --rereadpt simply issues a call to
ioctl(BLKRRPART) which forces kernel to re-initialize its metadata.
Kernel adds information about newly created partition here:
http://lxr.linux.no/#linux+v3.19.1/block/partition-generic.c#L269 You
can see a call to kobject_uevent() which
Adding verification-failed based on #14
** Tags removed: verification-done
** Tags added: verification-failed
--
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/1444037
Title:
** Project changed: juju-core = juju-core (Ubuntu)
--
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/1444037
Title:
juju-core 1.22.1 is not packaged in Ubuntu
To manage
** Changed in: juju-core (Ubuntu)
Assignee: Curtis Hovey (sinzui) = (unassigned)
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) = Oleg Strikov (strikov)
** Changed in: juju-core (Ubuntu Trusty)
Assignee: (unassigned) = Oleg Strikov (strikov)
--
You received this bug
Removing 'block-proposed' flag to allow juju 1.22.1 to go into Vivid.
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools
Here is the changelog for the package I'm asking SRU for:
juju-core (1.22.1-0ubuntu0.14.04.1) trusty; urgency=medium
* New upstream release (LP: #1444037).
* Packaging changes required by the new release and cherry-picked from Vivid:
- d/tests/fake-future.sh: New ability to generate fake
Tag block-proposed has been removed to be able to update the package in vivid.
We don't plan to update trusty package with 1.22.0 for now.
I'll post an update to this bug when we make decision on package update in
trusty.
** Tags removed: block-proposed
--
You received this bug notification
Juju 1.22.0 can't provision instances which run vivid because it doesn't
support systemd. Systemd support has been introduced in Juju 1.23 and we
plan to package this release when it becomes stable (now in beta).
However, I think that having 1.22 in vivid is much better than having
Juju 1.20 (what
I plan to change the status of this bug for 12.04 (precise) and 14.04 (trusty)
to Won't Fix.
In this comment I want to explain why I came to this decision.
This bug had CVE-2013-4449 linked to it. I don't think that this CVE is
relevant because the patch proposed in this bug doesn't resolve the
Hi Harry,
Thanks for the input.
Could you add more information on this please:
silently switch from a slapd that used openssl to gnutls
I just looked through the launchpad package archive and it looks like we never
had openldap linked against openssl in 12.04 and 14.04. First version of
I plan to change the status of this bug to Won't Fix and here is the
explanation for this decision. We can theoretically fix this issue in
mysql package. In the postrm handler we need to check if this
problematic symlink exists and remove it before passing control to deb-
systemd-helper. I don't
Public bug reported:
While working on mysql-5.6 package we met unusual (maybe even partially
incorrect) Alias option in systemd unit config:
Alias=mysql.service
It is unusual because mysql.service is the original name of the service which
can be found inside /lib/systemd/system/... This Alias
'I was able to reproduce the issue with upgrading the package (second part of
the bug):'
should be
'I was able to reproduce the issue with REMOVING the package (second part of
the bug):'
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Hi Argenis,
Today I tried to upgrade from 5.6.23-1~exp1~ubuntu4 to 5.6.23-1~exp1~ubuntu5
and reproduce the issue you observed.
Here is what I found:
Upgrade from ~ubuntu4 to ~ubuntu5 runs smoothly.
Mysql service starts after upgrade and automatically starts after reboot.
I can't reproduce the
43 matches
Mail list logo
